Security
Access control on every request, a complete audit trail, and encryption for secrets, backups and connections. Each mechanism below is part of the product you use.
Access control
One policy engine for every request
The console, the API, the CLI, MCP, Git, the registries and the S3 gateway ask the same IAM evaluator. An explicit deny wins and nothing is allowed by default. The account owner holds a policy like everyone else.
Conditions that fail closed
Policies can require a source network, a time window or a two-factor sign-in. When a request cannot supply the value, an allow does not apply and a deny does.
Single sign-on and two-factor sign-in
Connect an OIDC or SAML 2.0 identity provider and enforce it for your verified domains. Authenticator-app codes with recovery codes, and an organization-wide requirement for two-factor sign-in.
Credentials that expire
The CLI’s key expires after 90 days. CI exchanges an OIDC token from GitHub Actions for short-lived access instead of storing a key. An AI assistant connected over MCP never exceeds the permissions of the person who approved it.
Audit log
Each write, and each read of secret material or source code, is recorded at the moment it is allowed or denied, with the principal, the action, the resource and the source address.
Data protection
Secrets under your key
Secrets are encrypted with AES-256-GCM under a customer-managed key, versioned, granted only to the services that use them, and every reveal is logged.
Encrypted disks
Every database, cache and file system created since 12 November 2026 has encrypted disks, and volumes are encrypted by default: LUKS2 with AES-256, one key per disk, wrapped by your own key if you choose one and released only to the machine the disk is attached to. The console shows each database’s encryption. A database created before that date keeps plain disks; restore it into a new database to move it onto encrypted ones.
Encrypted backups
Backups and archived WAL of new databases are encrypted on the database machine before they are uploaded, with a key for that database alone. A restore into a new database moves an older one onto encrypted backups too.
TLS for every connection
Certificates for the console and your apps are issued automatically. Databases require TLS by default, with certificates from our own CA so sslmode=verify-full works.
Private networks
Databases and caches are private to your VPC by default. People reach them through Client VPN, one granted target at a time.
Data in Germany
Your machines, disks, databases and buckets are in Falkenstein and Nuremberg, Germany, unless your organization allows Helsinki, Finland, and someone picks it for a resource. The compliance page has the sub-processors, the technical and organisational measures and the certificates.
Platform
Images scanned on push
Every image pushed to the container registry is scanned with Trivy for known vulnerabilities, with findings next to the tag.
Dependencies watched
Dependency updates for the platform are automated, and its dependencies are checked for known vulnerabilities every six hours.
Hardened web console
Content Security Policy, HSTS and frame denial on the console, and a published security.txt.
Isolated builds and CI runs
Each build and each CI run gets a fresh machine that is deleted afterwards, with credentials scoped to that run.
Report a vulnerability
Write to security@platform.deutschecloud.app. Please include what you found, how to reproduce it and how to reach you.
Do not access other customers’ data, and do not run load or denial-of-service tests.
Start building on Deutsche Cloud
Create an account with your company details, install the command line and deploy your first app. Pay only for what runs.