Technical and Organisational Measures
Annex to the DPA · Art. 32 GDPR · Art. 3 FADO
SCMC Swiss Cybersecurity Management Center GmbH
As of 20 November 2026
This page describes the technical and organisational measures (TOMs) SCMC uses to protect personal data on the SCMC platform. It forms part of the Data Processing Agreement (DPA) under Art. 9 revFADP and Art. 28 GDPR and describes data security under Art. 3 FADO (DSV) and Art. 32 GDPR.
SCMC develops the measures further and may change them as long as the level of protection does not drop. The version on this page is the one that applies.
The most important point first: The platform runs on services of Amazon Web Services (AWS) and stores all data in Zurich. The database, invoices and the application logs are encrypted with SCMC's own key, which is also kept in Zurich. The customer decides who may see or edit a project through the roles in the project. The server checks this role on every request for data of the project.
1. How the platform is built
SCMC runs no servers of its own. The platform consists of services operated by AWS:
| Part of the platform | Service | Location |
|---|---|---|
| Database | Amazon DynamoDB | Zurich |
| Processing and interface | AWS Lambda, Amazon API Gateway | Zurich |
| Sign-in and user accounts | Amazon Cognito | Zurich |
| Invoices as files | Amazon S3 | Zurich |
| Sending emails | Amazon SES | Zurich |
| Encryption key | AWS Key Management Service (KMS) | Zurich |
| Access to the website | Amazon CloudFront with Web Application Firewall | nearest access point, content and logs in Zurich |
| Live update | AWS IoT Core | Frankfurt, identifiers only, no content (section 3.2) |
Where data only passes through and which providers are involved is governed by section 7 of the DPA.
The entire infrastructure is described as code (AWS Cloud Development Kit) and deployed from a versioned repository. Development, test and production run in three separate AWS accounts.
2. Confidentiality
2.1 Physical access to data centres
SCMC has no office or server rooms of its own. The data centres in Zurich are operated by AWS. AWS controls physical access to buildings and hardware. The AWS infrastructure is certified to ISO 27001, SOC 2 and PCI DSS; AWS provides the reports through AWS Artifact.
2.2 Sign-in
- Sign-in runs through Amazon Cognito in Zurich. Cognito checks and stores the passwords; SCMC's database holds no passwords.
- Every account can set up a second factor: MFA with an authenticator app, or a passkey. SCMC does not offer codes by SMS.
- The protected part of the interface accepts only requests with a valid token from Cognito. A token is valid for 60 minutes.
MFA requirement in a project. Owners and administrators can require MFA in the settings of a project, either for owners and administrators or for all members.
- A member the requirement covers who has not switched on MFA cannot open the project. The server refuses every request for this project.
- Only someone who has switched on MFA themselves can switch the requirement on. When it is switched on, all members receive an email.
- The requirement counts MFA with an authenticator app. A passkey alone is not enough, because signing in with the password remains possible beside it.
- Course seats in training projects are exempt.
2.3 Permissions in a project
All content, that is assessments, answers, measures and registers, belongs to exactly one project. Every person in a project has a role:
| Role | Permission |
|---|---|
| Owner | as administrator, plus deleting the project and transferring ownership. Every project has exactly one owner |
| Administrator | as write access, plus managing members, billing address and invoices, MFA requirement |
| Write access | answering questions, recording measures, importing and duplicating assessments |
| Read access | reading assessments and reports without changing anything |
On every request for data of a project, the server checks the role of the signed-in account in exactly this project. If the role is missing or not sufficient for the request, the server refuses it. The customer invites members themselves.
2.4 Access by SCMC
Administrative functions are open only to accounts that belong to the group Admin or SuperAdmin in Cognito. Every administrative route of the interface is restricted to these groups. An account cannot add itself to a group. Three people at SCMC belong to the group Admin, and only one of them to the group SuperAdmin.
People sign in to the platform's AWS accounts only through the AWS access portal (AWS IAM Identity Center), with their personal account at Microsoft Entra ID. Entra ID requires two-factor sign-in, which is remembered on known devices for at most 7 days.
SCMC opens a customer's project for support only in a support session. SCMC does not become a member of the project.
- Only an account of the group SuperAdmin can open a session. The server checks the group directly with Cognito when the session is opened.
- The account needs a passkey or MFA.
- A session applies to a single project and ends after 8 hours at the latest.
- At first, only reading is possible. Editing is a separate step. Deleting a project, buying or switching the payment method is never possible in a session.
- Start, end, the switch to editing and every writing request are recorded in a log that SCMC keeps for 2 years.
2.5 Encryption
SCMC's key is kept in the AWS Key Management Service in Zurich and is rotated automatically by AWS every year.
| What | Encryption |
|---|---|
| Database, all tables | SCMC's own key |
| Invoices as files | SCMC's own key |
| Logs of the application and the interface | SCMC's own key |
| Configuration of the functions | SCMC's own key |
| Access logs of the website and firewall logs | key of AWS (SSE-S3) |
| Connection between browser and platform | HTTPS only, with TLS 1.2 or higher. A request over HTTP is redirected to HTTPS, and the browser remembers this for one year (HSTS) |
| Connection from the access point to the interface | HTTPS only |
The storage for invoices and for the files of the website is not publicly accessible and refuses unencrypted connections.
3. Integrity and traceability
3.1 Tracing changes
- A change history records changes to answers, measures and risks with person, time and the changed values. It can be viewed in the platform. Consecutive changes by the same person are combined into one entry.
- The answers, measures and risks of an assessment can be locked. While they are locked, the server accepts no changes to them.
- Records carry a version number. If two people change the same record at the same time, the database refuses the later change instead of silently overwriting the earlier one.
- The server checks a change to an answer against the form the answer belongs to.
3.2 Logs and transfer
- The interface logs every request with time, path, result and the identifier of the signed-in account. The application writes the identifier of the account to every line of its log. Both logs are kept in Zurich.
- Credentials do not end up in the logs. Tokens, session cookies and confirmation codes are masked before writing, and automated tests check this. The access logs of the website contain no cookies, and in the firewall logs cookies and credentials are redacted.
- Reports as Word, PDF and Excel, as well as invoices, are released by the platform only through the interface, with a check of the role in the project.
- Live update: When several people have the same assessment open, SCMC tells their browsers through AWS in Frankfurt that something has changed. The message holds only identifiers and the kind of change, no content. The browsers load the new state from Zurich. Frankfurt does not store the messages.
- The website loads no third-party scripts and sets no cookies for analytics or advertising. A Content Security Policy restricts where the browser may load content from.
4. Availability and resilience
- The platform runs on managed services of AWS. The database adjusts its capacity to the load by itself.
- Requests through the website are checked by a Web Application Firewall (AWS WAF). It blocks known attack patterns with the rule sets of AWS, for example against SQL injection and malicious input, blocks addresses on lists of known attackers and anonymisation services, and limits the number of requests per IP address. Public forms have a tighter limit.
- Alarms report errors, throttling and slow responses of the interface, errors at sign-in and database bottlenecks. In addition, every error message in the log of the interface is emailed to SCMC immediately.
5. Recoverability
| Measure | Scope |
|---|---|
| Point-in-time recovery | every table of the database, to any point in time within the last 15 days |
| Daily backup (AWS Backup) | all tables, kept for 35 days |
| Monthly backup (AWS Backup) | all tables, kept for 12 months |
| Versioning of invoice files | an overwritten or deleted file is kept as an earlier version |
The backups are kept in an AWS Backup vault in Zurich. Because the infrastructure exists as code, the environment can be rebuilt from the repository.
6. Regular review
- Dependencies: An automated service (Renovate) proposes new versions of the libraries in use every week, and security advisories at once. SCMC reviews and applies them by hand.
- Infrastructure: On every deployment, a tool (cdk-nag) checks the description of the infrastructure against security rules of AWS.
- Security reviews: SCMC also reviews code and configuration of the platform when there is a reason to. In October 2026, access paths, permissions and logging of all parts of the platform were reviewed. The findings are kept in a list of measures and tracked there. Implemented since then, among others:
- Access keys and tokens no longer end up in logs.
- Changes to an answer are bound to its form.
- The live update no longer carries content.
- Tests: Automated tests cover, among others, the MFA requirement, the rights of the administration and the masking of credentials in logs.
7. Data minimisation, retention and deletion
7.1 Data minimisation
For an account, SCMC records first name, last name, display name and email address. A phone number is not needed. For statistics, SCMC analyses only the access logs of the website, without cookies (privacy policy, section 6).
7.2 Retention
| Data | Retention |
|---|---|
| Projects with assessments, answers and measures | until the owner deletes the project or their account. For the end of the contract, section 5 of the DPA applies |
| Invoices and payments | 10 years (Art. 958f Swiss Code of Obligations), also after the project is deleted |
| Logs of the application and the interface | 60 days |
| Access logs of the website | 60 days, analysis by Munot 6 months |
| Firewall logs | 30 days |
| Log of support sessions | 2 years |
| Database backups | point-in-time recovery 15 days, daily backups 35 days, monthly backups 12 months |
7.3 Deletion and return
- Return: Assessments can be downloaded as Word, PDF or Excel at any time.
- Deleting a project: When the owner deletes a project, the platform deletes its assessments, answers, measures and memberships. While an invoice for the project is open, the platform refuses the deletion.
- Deleting an account: When a person deletes their account, the platform deletes the projects they own and the account at Cognito. Name and email address are anonymised. While an invoice for one of their own projects is open, the platform refuses the deletion. The identifier of the account remains as a pseudonym in the change histories of other projects.
- Deletion by SCMC: Through the administration, SCMC can delete projects and accounts completely, for example after the end of the contract.
- Backups: Deleted data remains in the backups until they expire, at most 12 months.
The obligations for deletion and return after the end of the contract are set out in sections 5 and 8 of the DPA.
8. Sub-processors
SCMC uses sub-processors only under section 7 of the DPA. That section lists the providers, their tasks, where the data is kept and the contractual safeguards. If SCMC wants to add or replace a provider, SCMC informs the customer beforehand, and the customer can object.
9. Security incidents
The alarms from section 4 go to SCMC. SCMC notifies the customer of a personal data breach under section 9 of the DPA, at the latest within 72 hours of becoming aware of it.
Further legal information:
Data Processing Agreement (DPA) · Privacy Policy · Legal Notice · Terms & Conditions