{
  "slug": "encryption",
  "topic": "Encryption and key management",
  "status": "published",
  "order": 25,
  "capability": "data/encryption",
  "title": "Encryption: who can decrypt your data, and what must you start for post-quantum?",
  "short": "Automate certificate renewal before the 100-day limit on 15 March 2027, and inventory your cryptography for the post-quantum move.",
  "answer": "Automate renewal of every public TLS certificate before the maximum lifetime drops to 100 days on 15 March 2027[^br], and inventory your cryptography this quarter so data that must stay secret for ten years or more gets hybrid post-quantum key exchange first. Then judge each measure by who can use the key, and whether you could still decrypt if it were deleted.",
  "audience": "IT, security and platform teams in EU organizations that run TLS, certificates, disk and database encryption, cloud key management and secrets",
  "version": "1.0",
  "lastReviewed": "2026-11-04",
  "reviewEveryDays": 30,
  "blocks": [
    {
      "type": "ranked",
      "id": "first",
      "title": "If you only do five things",
      "navTitle": "Five things",
      "items": [
        {
          "title": "Automate certificate renewal by March 2027.",
          "text": "Public TLS certificates issued from 15 March 2027 may last at most 100 days[^br]. Renew with ACME and let ACME Renewal Information (ARI) set the timing, not a fixed interval[^le45]. Alert a week before any expiry."
        },
        {
          "title": "Inventory your cryptography.",
          "text": "List TLS endpoints, certificates, keys and who holds them, algorithms and trust stores. The EU roadmap calls this a no-regret first step that needn't be complete before you set priorities[^eufaq]."
        },
        {
          "title": "Turn on hybrid post-quantum key exchange.",
          "text": "Recorded traffic can be decrypted once a large quantum computer exists, so BSI recommends hybrid key agreement for long-term secrets[^tr1] and accepts `X25519MLKEM768` in TLS 1.3[^bsitr]. Chrome, Firefox and Apple's version 26 systems offer it[^chrome][^ffpq][^apple]."
        },
        {
          "title": "Separate who manages keys from who uses them.",
          "text": "AWS KMS key administrators can't use a key but can rewrite its policy to grant themselves access[^kmspol]. Activate key admin roles just in time, with approval[^akvsec]."
        },
        {
          "title": "Get secrets out of code and into a vault.",
          "text": "Give apps managed identities, not stored credentials, and one vault per app and environment[^akvsec]. Rotate any exposed secret at once. For CI tokens, see the supply-chain sheet."
        }
      ]
    },
    {
      "type": "steps",
      "id": "inventory",
      "title": "Build a first cryptographic inventory",
      "navTitle": "Inventory",
      "items": [
        {
          "title": "Which data must stay secret for ten years or more?",
          "text": "The EU roadmap counts it as high-risk and wants it protected from quantum attacks by the end of 2030[^euroadmap]. Think of health and HR records, contracts, designs and their backups."
        },
        {
          "title": "Where does it travel and where is it stored?",
          "text": "Follow it through load balancers, VPNs, SSH, APIs, databases and backups, including systems your managed service providers run."
        },
        {
          "title": "What protects it, and who holds the key?",
          "text": "Record the protocol and key exchange, the certificate and issuer, where the key lives (HSM, cloud KMS or a file) and who can use it. AWS load balancer connection logs record the negotiated key exchange[^albpol]."
        },
        {
          "title": "Which trust stores do your systems rely on?",
          "text": "List the CA bundle in each runtime, container image and appliance, and how each one gets updated. For Python, see the secure-python sheet."
        },
        {
          "title": "What can't be upgraded?",
          "text": "Ask suppliers when they will support ML-KEM. BSI strongly recommends that products expected to run beyond 2030 can be upgraded to quantum-safe methods[^tr1]."
        }
      ]
    },
    {
      "type": "list",
      "id": "tls",
      "title": "TLS baseline",
      "items": [
        "**Offer TLS 1.3 and 1.2 only.** BSI prefers TLS 1.3, recommends TLS 1.2 only until the end of 2031 and doesn't recommend TLS 1.0 or 1.1[^tr2].",
        "**Put hybrid groups first.** List `X25519MLKEM768` ahead of `X25519`, as OpenSSL 3.5 does by default[^ossl35]. Recent Windows 11 and Server 2025 builds support it in Schannel but leave it off; enable it with the ECC Curve Order group policy[^schannel]. On AWS load balancers, pick `ELBSecurityPolicy-TLS13-1-2-Res-PQ-2025-09`[^albpol].",
        "**Meet BSI key lengths.** Prefer ECDSA P-256 keys. BSI wants RSA keys of at least 3000 bits, so the usual RSA 2048 falls short[^tr2]."
      ]
    },
    {
      "type": "list",
      "id": "keys",
      "title": "Who holds the keys",
      "navTitle": "Keys",
      "items": [
        "**Encryption at rest stops disk thieves, not logins.** It protects against someone with the hardware but not the key[^azrest]. S3 decrypts for any authenticated request with permission[^s3sse].",
        "**Platform-managed keys suit most data,** Microsoft says[^azrest]. Choose customer-managed keys for specific regulatory or security needs; their availability becomes your job.",
        "**Make deletion slow and keep backups.** Turn on Key Vault soft delete and purge protection, back up keys that can't be recreated and test the restore[^akvsec]."
      ]
    },
    {
      "type": "list",
      "id": "changed",
      "title": "What changed in 2026",
      "navTitle": "What changed",
      "span": "full",
      "items": [
        "**A certificate authority lost its keys.** In October 2026 eight eMudhra intermediate CA keys proved recoverable. Mozilla dropped trust in eMudhra's emSign ECC Root CA - G3 and Chrome committed to do the same[^emudhra]. Update the trust store in every runtime and image, and keep a second ACME CA ready.",
        "**Public certificates are becoming server-only.** Chrome requires public certificates issued from 15 March 2027 to be for server authentication only[^crp]. Move mutual TLS to a private CA.",
        "**BSI and NIST set end dates for classical cryptography** in TR-02102 2026-01 and the final IR 8547 (dates below)[^tr1][^ir8547]."
      ]
    },
    {
      "type": "timelines",
      "id": "deadlines",
      "title": "Dates that set your schedule",
      "navTitle": "Deadlines",
      "span": "full",
      "items": [
        {
          "name": "Public TLS certificates",
          "scope": "Maximum lifetime and domain validation reuse, binding on every public CA[^br].",
          "steps": [
            {
              "at": "15 Mar 2026",
              "what": "200 days; reuse 200 days"
            },
            {
              "at": "15 Mar 2027",
              "what": "100 days; reuse 100 days"
            },
            {
              "at": "15 Mar 2029",
              "what": "47 days; reuse 10 days"
            }
          ]
        },
        {
          "name": "Post-quantum migration",
          "scope": "EU roadmap milestones[^euroadmap], with BSI and NIST dates.",
          "steps": [
            {
              "at": "End 2026",
              "what": "Plans and pilots started[^euroadmap]"
            },
            {
              "at": "End 2030",
              "what": "High-risk uses migrated[^euroadmap][^tr1]"
            },
            {
              "at": "End 2031",
              "what": "BSI: TLS 1.2 and classical-only key exchange end[^tr1][^tr2]"
            },
            {
              "at": "End 2035",
              "what": "Medium-risk migrated[^euroadmap]; NIST bars RSA and ECC[^ir8547]"
            }
          ]
        }
      ]
    },
    {
      "type": "list",
      "id": "skip",
      "title": "What you can skip",
      "items": [
        "**Re-keying everything to AES-256 for quantum.** NIST believes approved symmetric algorithms with at least 128-bit security meet its lowest post-quantum security category[^ir8547]. Use AES-256 for new long-term secrets, as BSI advises[^tr1].",
        "**Post-quantum TLS certificates now.** Classical signatures stay trustworthy until a quantum computer exists, and BSI recommends them until the end of 2035[^tr1]. Firmware signing can't wait that long[^euroadmap].",
        "**Cloud keys in an external key store.** AWS says their availability and latency risks exceed the perceived benefit for most customers[^xks].",
        "**Rotating KMS keys more than yearly.** Wrapping keys are almost never used enough to wear out[^kmsrot]."
      ]
    },
    {
      "type": "list",
      "id": "mistakes",
      "title": "Mistakes that cost the most",
      "navTitle": "Mistakes",
      "items": [
        "**Deleting a key something still uses.** A deleted AWS KMS key leaves its data unrecoverable. Disable it first and alarm on use during the 7 to 30 day waiting period[^kmsdel].",
        "**Trusting infrastructure-as-code defaults.** AWS load balancer listeners created from the CLI, CloudFormation or CDK without a named policy get `ELBSecurityPolicy-2016-08`, which allows TLS 1.0 and 1.1[^albpol].",
        "**Turning off post-quantum key exchange for a middlebox.** Firefox warns this removes protection against later decryption of recorded traffic[^ffpq], and Chrome's policy to do so ended with version 146[^chrome]. Fix the middlebox."
      ]
    },
    {
      "type": "columns",
      "id": "by-size",
      "title": "What this looks like at your size",
      "navTitle": "By team size",
      "span": "full",
      "columns": [
        {
          "title": "Small team, no security staff",
          "items": [
            "Use your host's or CDN's managed certificates, or an ACME client with ARI, and turn on expiry alerts.",
            "Keep the cloud's default encryption, and keep passwords and API keys in a vault, not in code.",
            "Ask your IT provider and SaaS vendors when they will support hybrid post-quantum TLS."
          ]
        },
        {
          "title": "Growing, with IT or security staff",
          "items": [
            "Build the inventory from load balancer logs, certificate transparency and config scans; give every certificate and key an owner.",
            "Enable hybrid ML-KEM on internet-facing TLS and SSH, and watch logs for clients that fall back.",
            "Run a private CA for client certificates and put key admin roles behind just-in-time access."
          ]
        },
        {
          "title": "Enterprise or regulated",
          "items": [
            "Write the cryptography policy NIS2 requires. For cloud and other digital providers, Regulation 2024/2690 sets its content, from algorithms to key destruction[^enisa].",
            "Keep the inventory in a standard format such as CBOM[^euroadmap] and report quantum risk to the board.",
            "Start with the PKI, the slowest to migrate, and put PQC support into supplier contracts."
          ]
        }
      ]
    }
  ],
  "changes": [
    {
      "date": "2026-11-04",
      "version": "1.0",
      "text": "Published after a copy edit and a source-by-source fact check, which fixed the AWS policy name and narrowed 10 statements to what the sources say."
    },
    {
      "date": "2026-11-04",
      "version": "0.1",
      "text": "First draft, based on CA/Browser Forum rules, BSI TR-02102 2026-01, the EU PQC roadmap, NIST IR 8547 and cloud KMS documentation."
    }
  ],
  "sources": [
    {
      "id": "br",
      "title": "Baseline Requirements, v2.3.1",
      "publisher": "CA/Browser Forum",
      "date": "4 Oct 2026",
      "url": "https://cabforum.org/working-groups/server/baseline-requirements/requirements/"
    },
    {
      "id": "le45",
      "title": "Decreasing Certificate Lifetimes to 45 Days",
      "publisher": "Let's Encrypt",
      "date": "2 Dec 2025",
      "url": "https://letsencrypt.org/2025/12/02/from-90-to-45"
    },
    {
      "id": "crp",
      "title": "Chrome Root Program Policy, v1.8",
      "publisher": "Google",
      "date": "5 Feb 2026",
      "url": "https://googlechrome.github.io/chromerootprogram/crp/policy"
    },
    {
      "id": "emudhra",
      "title": "Bug 2083449: eMudhra: Private key compromise of Intermediate Certificates",
      "publisher": "Mozilla",
      "date": "opened 18 Oct 2026",
      "url": "https://bugzilla.mozilla.org/show_bug.cgi?id=2083449"
    },
    {
      "id": "tr1",
      "title": "TR-02102-1, version 2026-01",
      "publisher": "BSI",
      "date": "23 Jan 2026",
      "url": "https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/TechGuidelines/TG02102/BSI-TR-02102-1.pdf?__blob=publicationFile"
    },
    {
      "id": "tr2",
      "title": "TR-02102-2 (TLS), version 2026-01",
      "publisher": "BSI",
      "date": "27 Jan 2026",
      "url": "https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/TechGuidelines/TG02102/BSI-TR-02102-2.pdf?__blob=publicationFile"
    },
    {
      "id": "bsitr",
      "title": "TR-02102 page, note on TLS 1.3",
      "publisher": "BSI",
      "date": "checked 4 Nov 2026",
      "url": "https://www.bsi.bund.de/EN/Themen/Unternehmen-und-Organisationen/Standards-und-Zertifizierung/Technische-Richtlinien/TR-nach-Thema-sortiert/tr02102/tr02102_node.html"
    },
    {
      "id": "euroadmap",
      "title": "Coordinated Implementation Roadmap for the Transition to PQC",
      "publisher": "NIS Cooperation Group",
      "date": "23 Jun 2025",
      "url": "https://digital-strategy.ec.europa.eu/en/library/coordinated-implementation-roadmap-transition-post-quantum-cryptography"
    },
    {
      "id": "eufaq",
      "title": "EU Roadmap on PQC: FAQ",
      "publisher": "NIS Cooperation Group",
      "date": "15 Apr 2026",
      "url": "https://ec.europa.eu/newsroom/dae/redirection/document/132120"
    },
    {
      "id": "ir8547",
      "title": "IR 8547: Transition to PQC Standards",
      "publisher": "NIST",
      "date": "Oct 2026",
      "url": "https://csrc.nist.gov/pubs/ir/8547/final"
    },
    {
      "id": "chrome",
      "title": "Chrome Enterprise policy list: PostQuantumKeyAgreementEnabled",
      "publisher": "Google",
      "date": "checked 4 Nov 2026",
      "url": "https://chromeenterprise.google/policies/#PostQuantumKeyAgreementEnabled"
    },
    {
      "id": "ffpq",
      "title": "PostQuantumKeyAgreementEnabled",
      "publisher": "Mozilla",
      "date": "updated 4 Nov 2026",
      "url": "https://firefox-admin-docs.mozilla.org/reference/policies/postquantumkeyagreementenabled/"
    },
    {
      "id": "apple",
      "title": "Prepare your network for quantum-secure encryption in TLS",
      "publisher": "Apple",
      "date": "18 Jun 2026",
      "url": "https://support.apple.com/en-us/122756"
    },
    {
      "id": "ossl35",
      "title": "OpenSSL 3.5 release notes",
      "publisher": "OpenSSL",
      "date": "8 Apr 2025",
      "url": "https://openssl-library.org/news/openssl-3.5-notes/"
    },
    {
      "id": "schannel",
      "title": "TLS Supported Groups in Windows",
      "publisher": "Microsoft Learn",
      "date": "20 May 2026",
      "url": "https://learn.microsoft.com/en-us/windows/win32/secauthn/tls-supported-groups-in-windows-11-24h2-and-later"
    },
    {
      "id": "albpol",
      "title": "Security policies for your Application Load Balancer",
      "publisher": "AWS",
      "date": "checked 4 Nov 2026",
      "url": "https://docs.aws.amazon.com/elasticloadbalancing/latest/application/describe-ssl-policies.html"
    },
    {
      "id": "akvsec",
      "title": "Secure your Azure Key Vault",
      "publisher": "Microsoft Learn",
      "date": "10 Jul 2026",
      "url": "https://learn.microsoft.com/en-us/azure/key-vault/general/secure-key-vault"
    },
    {
      "id": "azrest",
      "title": "Azure data encryption at rest",
      "publisher": "Microsoft Learn",
      "date": "8 Jul 2026",
      "url": "https://learn.microsoft.com/en-us/azure/security/fundamentals/encryption-atrest"
    },
    {
      "id": "kmspol",
      "title": "Default key policy",
      "publisher": "AWS",
      "date": "checked 4 Nov 2026",
      "url": "https://docs.aws.amazon.com/kms/latest/developerguide/key-policy-default.html"
    },
    {
      "id": "kmsdel",
      "title": "Delete an AWS KMS key",
      "publisher": "AWS",
      "date": "checked 4 Nov 2026",
      "url": "https://docs.aws.amazon.com/kms/latest/developerguide/deleting-keys.html"
    },
    {
      "id": "kmsrot",
      "title": "Rotate AWS KMS keys",
      "publisher": "AWS",
      "date": "checked 4 Nov 2026",
      "url": "https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html"
    },
    {
      "id": "xks",
      "title": "External key stores",
      "publisher": "AWS",
      "date": "checked 4 Nov 2026",
      "url": "https://docs.aws.amazon.com/kms/latest/developerguide/keystore-external.html"
    },
    {
      "id": "s3sse",
      "title": "Protecting data with server-side encryption",
      "publisher": "AWS",
      "date": "checked 4 Nov 2026",
      "url": "https://docs.aws.amazon.com/AmazonS3/latest/userguide/serv-side-encryption.html"
    },
    {
      "id": "enisa",
      "title": "NIS2 technical implementation guidance, v1.0",
      "publisher": "ENISA",
      "date": "26 Jun 2025",
      "url": "https://www.enisa.europa.eu/sites/default/files/2025-06/ENISA_Technical_implementation_guidance_on_cybersecurity_risk_management_measures_version_1.0.pdf"
    }
  ]
}