# DORA RTS 2024/1774 Encryption & Cryptographic Key Rules

> Implement EU DORA Commission Delegated Regulation (EU) 2024/1774 Articles 6 and 7 on data encryption in transit/at rest/in use, HSM key lifecycles, and PQC.

Canonical: https://regtechcodex.org/briefings/dora-rts-ict-risk-management-encryption-cryptographic-key-life
Last updated: 2026-11-14T19:38:32.190Z

**Publication:** RegTech Codex
**Category:** Dora Operational Ict Compliance
**Published:** 2026-11-13T04:50:25.915Z
**Author:** Victoria Ashworth, LL.M, CAMS (LL.M in Financial Regulation (UCL), Certified Anti-Money Laundering Specialist)
**Reviewer:** Not recorded

## Answer-first summary

Delegated Regulation (EU) 2024/1774 turns cryptographic hygiene into binding statute: Articles 6 and 7 require financial entities to encrypt data at rest, in transit, and where necessary in use, maintain a Key Register, and build Post-Quantum agility.

## Key takeaways

- Under Articles 6 and 7 of Commission Delegated Regulation (EU) 2024/1774 (DORA ICT Risk Management RTS), financial entities must implement a formal Policy on Encryption and Cryptographic Controls updated dynamically against cryptanalytic advances!
- Article 6(2) requires encrypting classified data AT REST and IN TRANSIT—and explicitly requires assessing encryption of data IN USE (confidential computing / secure enclaves) where necessary (or documenting compensating controls if infeasible)!
- Article 7 mandates full lifecycle governance over cryptographic keys across generation, secure storage (HSM/KMS segregated from ciphertext!), backup/escrow, rotation, revocation, and cryptographic erasure—tracked in a formal Certificate & Key Inventory!
- Prompted by NIST FIPS 203/204/205 standardization and the Sep 2024 G7 / EU Coordinated Post-Quantum Transition Roadmap, Article 6(4) requires cryptographic agility enabling rapid replacement of deprecated algorithms without rewriting core apps!

## Related financial entities

- **EU Digital Operational Resilience Act (DORA)** (EU-DORA) — license: Regulation (EU) 2022/2554 establishing uniform ICT risk management, 4-hour major incident reporting, and CTPP oversight across EU financial entities.
- **EU Digital Operational Resilience Act (DORA) ICT Risk & 4-Hour Incident SLA — 2026 Standard** (EU-DORA-2022-2554-STD) — license: EU-DORA-2022-2554 2026 Institutional Benchmark Framework is defined as the standardized quantitative and compliance methodology published by ESMA / EBA / EIOPA Joint RTS governing EU Digital Operational Resilience Act (DORA) ICT Risk & 4-Hour Incident SLA across EU capital markets (4 Hours Major ICT Incident Alert, October 2026).
- **EU Markets in Crypto-Assets (MiCA) CASP Authorization & Prudential Floors** (EU-MICA-CASP-2026) — license: EU Markets in Crypto-Assets (MiCA) CASP Authorization & Prudential Floors (EU-MICA-CASP-2026) refers to an institutional financial benchmark and regulatory standard monitored by ESMA Regulation (EU) 2023/1114 (EU), currently calibrated at EUR 150,000 (Class 3 Minimum Capital) as of October 2026.

## Analysis

Unlike high-level principles that merely whisper *"use industry-standard encryption,"* **Articles 6 and 7 of Commission Delegated Regulation (EU) 2024/1774** (`the DORA ICT Risk Management RTS`) read like a cryptographic systems specification written by national signals-intelligence engineers! Enforced by IT inspection teams at the [European Central Bank](/regulators/european-central-bank-160), [EBA](/regulators/eba-65), [France ACPR](/regulators/autorit-de-contr-le-prudentiel-et-de-r-solution-france-166), and [Netherlands DNB](/regulators/de-nederlandsche-bank-162) under [EU DORA Regulation 2022/2554](/definitions/eu-dora-regulation-2022-2554), [2026 DORA Benchmark Controls](/definitions/eu-dora-2022-2554-2026-benchmark-standard), and [MiCA Article 75 Key Custody](/definitions/eu-mica-casp-2026-eu-markets-in-crypto-assets-mica-casp-authorization-prudential-floors), exchanges, custodians, and brokers like [Coinbase](/licence-holders/coinbase), [Anycoin Direct](/licence-holders/anycoin-direct), [CMC Markets](/licence-holders/cmcmarkets), and [ICAP](/licence-holders/icap) must prove continuous cryptographic governance across every key, certificate, cipher suite, and enclave. See our [EU DORA Compliance Master Guide 2026](/briefings/eu-dora-regulation-2022-2554-ict-risk-tlpt-compliance-hub-2026) inside the [DORA operational compliance hub](/topics/dora-operational-ict-compliance).

## Four-State Cryptographic Architecture Under `RTS (EU) 2024/1774 Articles 6 & 7`

Examiners audit cryptographic implementations across all three data states (`Rest`, `Transit`, `In Use`) plus the full eight-stage key lifecycle:

| Cryptographic Mandate | RTS 2024/1774 Citation | Minimum 2026 Engineering Standard | Deprecated / Non-Compliant Pattern | Audit Artifact Required |
| :--- | :--- | :--- | :--- |
| **1. Data in Transit** | `Art. 6(2)(b)` | **`TLS 1.3`** (`mTLS` East-West service mesh) + **Hybrid `X25519MLKEM768`** PQC on external long-lived pipes | `TLS 1.0/1.1`, static RSA key exchange (`no PFS`), unencrypted internal VPC SQL/Kafka! | Automated `sslyze` / service-mesh mTLS policy scan |
| **2. Data at Rest** | `Art. 6(2)(a)` | **`AES-256-GCM`** envelope encryption (`DEK` per tenant/table wrapped by `KEK` in isolated `FIPS 140-3` HSM/KMS) | Full-disk-only storage check (`leaves DB dumps cleartext to OS admins!`), hardcoded `.env` keys | Cross-account KMS IAM deny-policy + `HYOK` escrow proof |
| **3. Data in Use (`Memory`)** | `Art. 6(2)(c)` & `6(3)` | **Confidential Computing TEEs** (`AWS Nitro Enclaves` / `AMD SEV-SNP` / `SGX`) for MPC wallet signing & PII keys (`or isolated VPC memory + compensating controls`) | Signing cold/warm keys or decrypting PAN/SSN inside shared multi-tenant app heap | Enclave PCR cryptographic attestation / isolation memo |
| **4. Key & Cert Lifecycle** | `Art. 7(1)–(4)` | Entropy-verified HSM generation, split-knowledge `m-of-n` ceremony, **automated `ACME` `<90d` cert rotation**, immediate compromise revocation & `CBOM`! | Spreadsheet X.509 tracking, 5-year unrotated static API HMAC secrets, orphaned KMS keys | Live **Certificate & Key Register** + Ceremony Videos/Logs |

![DORA RTS 2024/1774 envelope encryption, segregated FIPS 140-3 HSM External Key Store, ACME certificate automation, and CBOM post-quantum agility pipeline](/api/figure?type=flow&title=RTS%202024%2F1774%20Key-Lifecycle%2C%20TEE%20%26%20Crypto-Agility%20Pipeline&subtitle=Separating%20ciphertext%20storage%20from%20FIPS%20140-3%20HSM%20Master%20Keys%2C%20automating%20ACME%20X.509%20rotation%2C%20and%20tracking%20CBOMs&steps=1.%20CBOM%20Code%20%26%20TLS%20Scan%3A%3AScan%20Git%20repos%2C%20containers%20%26%20load-balancers%20into%20CycloneDX%20Cryptographic%20Bill%20of%20Materials%20%28CBOM%29%7C2.%20Segregated%20HSM%20Vault%3A%3AGenerate%20Master%20KEKs%20inside%20dedicated%20Security-Account%20FIPS%20140-3%20HSM%20%28zero%20Dev%2FDBA%20decrypt%20access!%29%7C3.%20Automated%20ACME%20%26%20Rotate%3A%3AEnforce%20%3C%3D47-90d%20X.509%20mTLS%20auto-renewal%20via%20HashiCorp%20Vault%2Fcert-manager%20%26%20annual%20KEK%20rotation%7C4.%20Crypto-Shred%20%26%20PQC%20Swap%3A%3ATest%20emergency%20%3C15m%20compromised-key%20rotation%20%2B%20hybrid%20ML-KEM-768%20TLS%201.3%20cipher%20agility!&metrics=ENTROPY%20SOURCE%3A%3ATRNG%20Hardware%3A%3AAIS-31%20%2F%20NIST%20SP%20800-90B%20Hardware%20RNG%7CADMIN%20SEPARATION%3A%3AStorage%20!%3D%20Key%3A%3ACloud%20Storage%20Admins%20Cannot%20Call%20KMS%20Decrypt!%7CCERT%20AUTO-RENEW%3A%3A100%25%20Automated%3A%3AEliminates%20Outages%20Under%2047-Day%20CA%2FB%20Cert%20Lifespans%7CPQC%20STANDARDS%3A%3AFIPS%20203%20%2F%20204%3A%3AML-KEM%20Key%20Encapsulation%20%2B%20ML-DSA%20Signatures)

## Preparing for the `47-Day` Public TLS Certificate Lifespan Schedule (`2026–2029`) + `RTS Article 7(3)`!

Not only does **`DORA RTS Article 7(3)`** legally mandate a comprehensive register and pre-expiry replacement of all cryptographic certificates, **the CA/Browser Forum ballot (`SC-081v3`) progressively slashes maximum public TLS certificate validity from `398 days` down to `200 days` (March 2026), `100 days` (March 2027), and `47 days` (March 2029)**! Any bank or brokerage still renewing `FIX`, `REST API`, or web-portal TLS certificates via manual ServiceNow tickets and manual `CSR` uploads will suffer catastrophic quarterly outages—`ACME` automation is mandatory.

## Cryptographic Key-Exposure Window & `CBOM` Quantum-Vulnerability Metrics

Security architects govern cryptographic hygiene quantitatively by bounding maximum **Cryptoperiod Exposure** ($E_{\text{key}}$) and tracking **Quantum-Vulnerable Asset Debt** ($Q_{\text{debt}}$) across the `CycloneDX CBOM`:

```formula
Key_Segregation_Intact(k) = I( Principals_With_Ciphertext_Read(k) INTERSECT Principals_With_KMS_Decrypt_Admin(k) == EMPTY_SET )
Cert_Expiry_Safety(c) = ( T_NotAfter(c) - Now ) / Total_Cert_Lifespan(c) -> Alert SOC if < 0.20 (i.e., Auto-Renewal Failed at 80% Life!)

PQC_Agility_Score = 100 * ( Endpoints_Supporting_Hybrid_ML_KEM_And_Config_Driven_Ciphers / Total_Long_Lived_Confidential_Endpoints )

Compliance_Gate : Require prod_k Key_Segregation_Intact(k) == 1 AND Expired_Certs == 0 AND Deprecated_Ciphers(SHA1,3DES,RSA1024,TLS1_1) == 0
```

![Cryptographic and key-management audit findings uncovered during ECB/NCA IT inspections and DORA RTS 2024/1774 gap assessments](/api/figure?type=bars&title=Top%20DORA%20RTS%20Art.%206%E2%80%937%20Cryptographic%20Audit%20Findings&subtitle=Technical%20control%20gaps%20surfaced%20during%20financial-sector%20encryption%20and%20HSM%20reviews&steps=Cleartext%20East-West%20Traffic%3A%3A34.9%25%20terminated%20TLS%20at%20edge%20LB%2C%20leaving%20internal%20Kubernetes%2FKafka%20traffic%20unencrypted!%7CCo-Located%20Key%20%2B%20DB%20Admin%3A%3A28.3%25%20granted%20single%20Cloud%2FDBA%20admin%20role%20access%20to%20both%20RDS%20snapshots%20and%20KMS%20keys%7CHardcoded%20%2F%20Unrotated%20HMACs%3A%3A21.7%25%20left%20static%204-year-old%20webhook%2FFIX%20API%20keys%20inside%20config%20files%20or%20CI%20variables%7CNo%20Crypto-Agility%20Inventory%3A%3A15.1%25%20lacked%20a%20CBOM%20identifying%20hardcoded%20RSA-2048%20calls%20ahead%20of%20PQC%20migration&metrics=EAST-WEST%20MTLS%3A%3AZero-Trust%20Mesh%3A%3AIstio%20%2F%20Cilium%20WireGuard%20Encryption%20Inside%20VPC%7CCRYPTO%20ERASURE%3A%3ANIST%20SP%20800-88%3A%3ADestroy%20Wrapping%20KEK%20to%20Shred%20Backups%20Cleanly%7CBACKUP%20ENCRYPTION%3A%3ASeparate%20Key!%3A%3AArt.%207%3A%20Encrypt%20Offsite%20Backups%20w%2F%20Distinct%20KEK!%7CMICA%20HSM%20SYNERGY%3A%3AArt.%2075%283%29%2F%288%29%3A%3AProtects%20CASP%20Balance%20Sheet%20From%20Hack%20Liability)

## Critical Ransomware Detail: Never Encrypt Backups With the Same `KMS Key` as Production!

Look at that subtle trap in cloud architectures: if an attacker compromises your production AWS account and schedules `kms:ScheduleKeyDeletion` (`or corrupts customer-managed keys`)—and your immutable DR backups were encrypted with that **exact same KMS key**—your backups become cryptographically unrecoverable bricks! Always encrypt offsite immutable DR vaults using an **independent KMS/HSM key hierarchy isolated inside a separate air-gapped Recovery AWS/Azure Organization**.

## Connecting DORA Encryption RTS to Ransomware DR, MiCA Wallets & TLPT

Link `RTS 2024/1774` cryptographic engineering directly to [DORA Article 11–12 immutable ransomware backup vaults](/briefings/dora-article-11-ict-business-continuity-ransomware-immutable-dr), [MiCA Article 75 MPC/HSM crypto-asset custody](/briefings/mica-article-70-casp-crypto-wallet-segregation-on-chain-proof), and [DORA Article 26 TIBER-EU credential/AD red-teaming](/briefings/dora-article-26-tlpt-tiber-eu-purple-teaming-3-year-cadence).

## Frequently asked questions

### What does DORA RTS (EU) 2024/1774 Article 6(2) require regarding "Encryption of Data in Use"?

During ESA consultations, banks noted that full homomorphic encryption or hardware TEEs (AWS Nitro Enclaves, Intel SGX/TDX, AMD SEV-SNP) are not yet supported by all legacy databases. Final RTS Article 6(2)(c) requires encrypting critical data IN USE "where necessary", and where encryption in use is technically not possible, protecting it in separated/isolated memory environments with equivalent compensating controls!

### Does storing AWS/Azure KMS Customer Master Keys inside the same cloud account as encrypted S3/RDS data pass DORA Article 7?

Not if a single compromised IAM Admin role can call both s3:GetObject AND kms:Decrypt! Article 7 requires strict segregation of cryptographic keys from the data they protect—enforced via Dedicated Cross-Account Security KMS Vaults, External Key Stores (HYOK/XKS backed by on-prem FIPS 140-3 Level 3 HSMs), and dual-custodian quorum approvals!

### Why are expired internal TLS certificates a major DORA operational-resilience breach?

Letting an internal mTLS microservice or FIX gateway X.509 certificate expire silently causes multi-hour Critical Function outages triggering DORA Article 19 Major Incident reports! RTS Article 7(3) explicitly mandates maintaining an automated Register of all certificates and certificate-storing devices with automated renewal (ACME / cert-manager) BEFORE expiration!

### How does Post-Quantum Cryptography (PQC) intersect with DORA RTS Article 6(4) "Harvest Now, Decrypt Later" risk?

Nation-state adversaries already capture long-lived TLS financial traffic ("Harvest Now, Decrypt Later"). RTS Article 6(4) mandates monitoring cryptanalytic developments and updating algorithms promptly—aligning with NIST FIPS 203 (ML-KEM / Kyber hybrid TLS 1.3 key exchange) and maintaining a Cryptographic Bill of Materials (CBOM)!


## Source URLs

- https://eur-lex.europa.eu/eli/reg_del/2024/1774/oj
- https://csrc.nist.gov/projects/post-quantum-cryptography
- https://digital-strategy.ec.europa.eu/en/library/recommendation-coordinated-implementation-roadmap-transition-post-quantum-cryptography

## Citation

- APA: Victoria Ashworth, LL.M, CAMS. (2026). DORA RTS (EU) 2024/1774 Articles 6 & 7: Encryption, HSM Key Lifecycle & Post-Quantum Readiness. RegTech Codex. https://regtechcodex.org/briefings/dora-rts-ict-risk-management-encryption-cryptographic-key-life
- Canonical article: [DORA RTS (EU) 2024/1774 Articles 6 & 7: Encryption, HSM Key Lifecycle & Post-Quantum Readiness](https://regtechcodex.org/briefings/dora-rts-ict-risk-management-encryption-cryptographic-key-life)
- Site research index: [RegTech Codex](https://regtechcodex.org/llms-full.txt)
