Technical and Organisational Measures (TOMs)
This is a convenience translation. Only the German version is legally binding: German version.
Measures pursuant to Art. 32 GDPR for the security of processing. Annex to the data processing agreement.
1. Confidentiality
Encryption
- Backups can be end-to-end encrypted on the client side; the client-side keys remain exclusively with the customer.
- Objects are additionally stored with server-side encryption.
- All data traffic between the zones (backup zone ↔ storage zones) runs over strongly encrypted, mutually authenticated connections.
- Customer transfers to the Citadels use TLS (HTTPS).
- Pseudonymisation: internal processing and logging refer to customers, projects and objects by technical identifiers rather than by plain names wherever possible.
Physical access, system access and data access control
- Physical access control: operation exclusively in professional data centres; physical access is controlled by the respective data centre provider and restricted to authorised personnel.
- Sign-in exclusively via single sign-on of a central identity platform with mandatory multi-factor authentication (TOTP).
- Role-based access control in organisations and projects (least privilege).
- Internal services bind only to private network addresses; administrative services are not publicly reachable. Administrative access is via secured jump hosts/VPN.
- Database access via service-specific accounts with the minimum rights required; secrets are managed and rotated centrally.
- Protection against automated attacks (e.g. automatic blocking of source addresses after repeated failed sign-in attempts).
Separation control
- Tenant separation at application level (organisations/projects).
- Strict network and zone segmentation: separate private subnets per zone; zones are isolated from each other, cross traffic only via defined, encrypted paths.
- Separate environments for development, testing and production.
- Control of outbound data traffic (egress filtering via proxy/NAT gateway).
2. Integrity
Transfer and input control
- Immutable, write-protected storage (WORN, “Write Once, Read Never”) for configured projects: the platform ensures that objects can be neither changed nor deleted during the retention period; reading requires a separate token with read permission.
- Audit-proof logging of security-relevant events; central collection and analysis in an access-protected analysis system.
- Authentication of every request via project-specific tokens; checking of permissions and quotas at the Citadels.
- Automated anomaly detection (including token misuse, indications of unencrypted uploads or low entropy, volume and throughput outliers) with notifications to the customer.
3. Availability, resilience and recoverability
- Storage zones in professional data centres; zones currently available: de01-1 (Nuremberg, data centre provider Hetzner), de02-1 (Frankfurt am Main, IONOS) and it01-1 (Ponte San Pietro, Aruba). Further zones at additional locations and with further providers are in preparation.
- Several storage endpoints (Citadels) per zone with automatic endpoint switching by the client software in the event of disruptions.
- Replication of administrative data and metadata between the zones; zone-local continued operation if the backup zone fails.
- 24/7 monitoring of the endpoints (availability, latency, TLS) with alerting; scheduled maintenance window (see service level).
- Hardened host configuration and regular updates and patches.
- Central administrative data and metadata are backed up automatically every day; restoration follows documented recovery plans and is tested regularly. Customer data is held immutably (WORN) with a customer-defined retention period.
4. Procedures for regular testing, assessment and evaluation
- Central, automated observability (monitoring, logging, alerting).
- Infrastructure as code: traceable, versioned configuration as the single source of truth; no host-local special configurations.
- Order control: sub-processors are engaged only under a contractual commitment to equivalent obligations (see DPA).
- The effectiveness of the measures is monitored continuously and automatically and is reviewed and assessed internally at least once a year; the results feed into further development.
This description sets out the intended framework of measures. Individual measures may differ by environment, zone and provider and are continuously developed further.