# Dora Operational Ict Compliance | RegTech Codex

> Dora Operational Ict Compliance research topics and source records from RegTech Codex. Fully applicable across 22,000+ European financial entities since January 17, 2025, Regulation (EU) 2022/2554 (DORA) replaces fragmented national IT outsourcing guidance with a binding five-pillar law backed by Joint ESA Regulatory Technical Standards and direct CTPP oversight.

Canonical: https://regtechcodex.org/topics/dora-operational-ict-compliance
Last updated: 2026-11-14T19:38:15.144Z

## Dora Operational Ict Compliance

Dora Operational Ict Compliance research topics and source records from RegTech Codex. Fully applicable across 22,000+ European financial entities since January 17, 2025, Regulation (EU) 2022/2554 (DORA) replaces fragmented national IT outsourcing guidance with a binding five-pillar law backed by Joint ESA Regulatory Technical Standards and direct CTPP oversight.

Last updated: 2026-11-14T19:38:15.144Z

### Research briefings (20)

- [EU DORA Regulation (EU) 2022/2554 Master Guide: ICT Risk, 4h/72h Reporting, RoI & TLPT (2026)](https://regtechcodex.org/briefings/eu-dora-regulation-2022-2554-ict-risk-tlpt-compliance-hub-2026) — Dora Operational Ict Compliance. Fully applicable across 22,000+ European financial entities since January 17, 2025, Regulation (EU) 2022/2554 (DORA) replaces fragmented national IT outsourcing guidance with a binding five-pillar law backed by Joint ESA Regulatory Technical Standards and direct CTPP oversight.
- [DORA Article 28 & ITS (EU) 2024/2956: 15-Template xBRL-CSV Register of Information Guide](https://regtechcodex.org/briefings/dora-article-28-its-2024-2956-register-of-information-templates) — Dora Operational Ict Compliance. Under DORA Article 28(3) and Commission Implementing Regulation (EU) 2024/2956, financial entities must submit a relational 15-table Register of Information in xBRL-CSV format—feeding the Joint ESAs’ quantitative engine that designates Critical ICT Third-Party Providers.
- [DORA Article 19 Major ICT Incident Reporting: RTS 2024/1772 Thresholds & 4h/72h/1m SLAs](https://regtechcodex.org/briefings/dora-article-19-major-ict-incident-4-hour-72-hour-reporting-sla) — Dora Operational Ict Compliance. When a production outage, DDoS wave, or ransomware intrusion strikes an EU financial entity, DORA Articles 18 and 19 start two unforgiving regulatory clocks: quantitative Major classification under RTS 2024/1772 followed by a 4-hour Initial Notification and 72-hour Intermediate Report.
- [DORA Article 26 Threat-Led Penetration Testing (TLPT): TIBER-EU Live Production & Purple Teaming](https://regtechcodex.org/briefings/dora-article-26-tlpt-tiber-eu-purple-teaming-3-year-cadence) — Dora Operational Ict Compliance. Standard staging-environment penetration tests do not satisfy DORA Article 26: systemically important banks, CCPs, trading venues, and top-tier brokers/CASPs must undergo intelligence-led TIBER-EU Red and Purple Team exercises directly against live production systems every three years.
- [DORA Critical ICT Third-Party Providers (CTPPs): Designation Math, Lead Overseers & 1% Daily Fines](https://regtechcodex.org/briefings/critical-ict-third-party-providers-ctpp-lead-overseer-powers) — Dora Operational Ict Compliance. For the first time in European regulatory history, DORA Articles 31 through 44 place hyperscale cloud, market-data, and core-ledger tech giants under direct on-site inspection and penalty jurisdiction of EBA, ESMA, and EIOPA Lead Overseers.
- [DORA Article 30 ICT Contractual Clauses: Two-Tier SaaS Repapering, Audit Rights & Exit Plans](https://regtechcodex.org/briefings/dora-article-30-ict-contractual-clauses-audit-exit-strategies) — Dora Operational Ict Compliance. Every single ICT service agreement signed by an EU financial entity—from core matching engines down to standard non-critical HR SaaS—must contain explicit written clauses mandated under DORA Article 30(2), expanding dramatically under Article 30(3) for Critical Functions.
- [UK Operational Resilience (FCA PS21/3 & PRA SS2/21) vs EU DORA: Cross-Mapping Dual Programs](https://regtechcodex.org/briefings/uk-fca-ps21-3-pra-ss2-21-impact-tolerances-vs-eu-dora-mapping) — Dora Operational Ict Compliance. March 31, 2025 ended the UK’s three-year operational resilience transition period—requiring FCA and PRA firms to remain strictly within Impact Tolerances across all Important Business Services just ten weeks after EU DORA took full legal effect across the Channel.
- [US SEC Regulation S-P Amendments (2024–2026) & Form 8-K Item 1.05: 4-Day & 30-Day Cyber Clocks](https://regtechcodex.org/briefings/sec-regulation-s-p-amendments-form-8-k-item-1-05-cyber-rules) — Dora Operational Ict Compliance. US broker-dealers, Registered Investment Advisers, and public financial issuers face an interlocking triad of SEC cyber clocks: Form 8-K Item 1.05 (4 business days), amended Regulation S-P (72-hour service-provider notice & 30-day customer notice), and proposed/adopted Reg SCI & Rule 10.
- [DORA vs NIS2 Directive (Article 1(2) Lex Specialis): Dual-Scope Financial Groups & CSIRT Sync](https://regtechcodex.org/briefings/dora-nis2-lex-specialis-article-1-2-csirt-nca-reporting-sync) — Dora Operational Ict Compliance. While DORA acts as sector-specific lex specialis overriding NIS2 for regulated banks, brokers, and CASPs, mixed corporate groups containing unregulated IT holding companies, data centers, or cloud subsidiaries frequently trigger BOTH DORA and NIS2 simultaneously!
- [DORA Subcontracting RTS (EU) 2025/532: Nth-Party ICT Supply-Chain Monitoring & Exit Triggers](https://regtechcodex.org/briefings/nth-party-ict-subcontracting-rts-critical-function-chain-risk) — Dora Operational Ict Compliance. Adopted on March 24, 2025 as Commission Delegated Regulation (EU) 2025/532, DORA’s Subcontracting RTS closes the fourth-party blind spot—forcing financial entities to assess chain complexity before contract signature and hold contractual termination rights over material subcontractor changes.
- [AI & LLM Governance in Trade Surveillance & AML: EU AI Act (2024/1689), DORA & SR 11-7](https://regtechcodex.org/briefings/ai-ml-model-governance-trade-surveillance-eu-ai-act-dora-audit) — Dora Operational Ict Compliance. Deploying machine-learning anomaly detectors and generative-AI SAR narrative copilots inside banks and brokerages triggers overlapping mandates across EU AI Act Regulation (EU) 2024/1689, ESMA’s MiFID II AI Statement, DORA third-party ICT rules, and US SR 11-7.
- [DORA Article 29 Cloud Concentration Risk: Multi-Region vs Multi-Cloud RTO/RPO Engineering](https://regtechcodex.org/briefings/multi-cloud-concentration-risk-active-active-failover-rto-rpo) — Dora Operational Ict Compliance. Does EU DORA Article 29 force every bank and broker to run simultaneous active-active workloads across AWS AND Azure? No—but claiming "easy substitutability" on paper without container portability, DNS decoupling, and live region-evacuation drills fails supervisory scrutiny.
- [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) — Dora Operational Ict Compliance. 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.
- [DORA Article 16 Simplified ICT Risk Framework & Microenterprise Proportionality Carve-Outs](https://regtechcodex.org/briefings/dora-simplified-ict-risk-framework-article-16-exempt-entities) — Dora Operational Ict Compliance. Small and non-interconnected MiFID Class-3 investment firms, exempt payment institutions, and microenterprises (<10 staff and <EUR 2M turnover) do NOT face the exact same DORA burden as global universal banks—provided they map Article 2(3), Article 4, and Article 16 accurately!
- [DORA Articles 11 & 12 Ransomware Recovery: Immutable Air-Gapped Vaults & Clean-Room Restore](https://regtechcodex.org/briefings/dora-article-11-ict-business-continuity-ransomware-immutable-dr) — Dora Operational Ict Compliance. Modern ransomware crews delete cloud snapshots, poison Active Directory domain controllers, and lurk inside backup catalogs for 45 days before detonating—which is why DORA Article 12 mandates physically and logically segregated immutable backups tested via clean-room restoration.
- [NYDFS 23 NYCRR Part 500 (Second Amendment): Class A Audits, 72h Cyber & 24h Extortion Notices](https://regtechcodex.org/briefings/nydfs-23-nycrr-500-ciso-attestation-72h-ransom-extortion-rules) — Dora Operational Ict Compliance. New York’s Department of Financial Services enforces the strictest prescriptive cybersecurity code in the US: 23 NYCRR Part 500 Second Amendment binds NY branches, banks, and BitLicense exchanges with personal CEO + CISO certifications and 24-hour extortion alerts.
- [DORA Article 45 Cyber Threat Intelligence Sharing: STIX 2.1, TAXII, MISP & GDPR/Antitrust Guardrails](https://regtechcodex.org/briefings/dora-article-45-cyber-threat-intelligence-sharing-tlp-stix-taxii) — Dora Operational Ict Compliance. Pillar 5 of EU DORA (Article 45) creates a clear statutory safe-harbor framework encouraging financial entities to exchange Indicators of Compromise, TTPs, and cyber alerts via trusted FS-ISAC, CIISI-EU, and MISP communities—subject to strict GDPR, TLP, and NCA notification rules.
- [MiFID II RTS 6 Algorithmic Trading & DORA Resilience: Kill Switches, Collars & Order-to-Trade Ratios](https://regtechcodex.org/briefings/algorithmic-trading-rts-6-dora-article-17-kill-switch-resilience) — Dora Operational Ict Compliance. Runaway trading algorithms can bankrupt an investment firm in 45 minutes (Knight Capital’s $440M loss)—which is why European supervisors now audit MiFID II RTS 6 kill switches, pre-trade risk collars, and Direct Electronic Access gates jointly with EU DORA ICT resilience.
- [Singapore MAS TRM & Notice PSN05/644 vs Australia APRA CPS 230: APAC Operational Resilience Map](https://regtechcodex.org/briefings/mas-trm-guidelines-apra-cps-230-apac-operational-resilience-map) — Dora Operational Ict Compliance. Singapore MAS Notices 644, CMG-N03, and PSN05 enforce a 60-minute initial incident alert and a strict 4-hour rolling 12-month critical-system downtime cap, while Australia’s APRA CPS 230 went live July 1, 2025 alongside EU DORA.
- [DORA Article 5 Management Body Liability: Board ICT Training, Budgets & CISO Independence](https://regtechcodex.org/briefings/dora-article-5-management-body-ict-liability-budget-governance) — Dora Operational Ict Compliance. Under EU DORA Article 5, the Management Body (Board of Directors) cannot delegate away ultimate legal accountability for ICT risk: directors must personally approve digital resilience strategies, ring-fence sufficient ICT budgets, and complete ongoing mandatory cybersecurity training.

### Related entities (11)

- [EU Digital Operational Resilience Act (DORA)](https://regtechcodex.org/definitions/eu-dora-regulation-2022-2554) — 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](https://regtechcodex.org/definitions/eu-dora-2022-2554-eu-digital-operational-resilience-act-dora-ict-risk-4-hour-incident-sla) — EU Digital Operational Resilience Act (DORA) ICT Risk & 4-Hour Incident SLA (EU-DORA-2022-2554) refers to an institutional financial benchmark and regulatory standard monitored by ESMA / EBA / EIOPA Joint RTS (EU), currently calibrated at 4 Hours (Major ICT Incident Alert) as of October 2026.
- [EU Digital Operational Resilience Act (DORA) ICT Risk & 4-Hour Incident SLA — 2026 Standard](https://regtechcodex.org/definitions/eu-dora-2022-2554-2026-benchmark-standard) — 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](https://regtechcodex.org/definitions/eu-mica-casp-2026-eu-markets-in-crypto-assets-mica-casp-authorization-prudential-floors) — 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.
- [UK FCA Consumer Duty (PRIN 2A) & Section 21 Financial Promotions Gateway](https://regtechcodex.org/definitions/fca-consumer-duty-uk-fca-consumer-duty-prin-2a-section-21-financial-promotions-gateway) — UK FCA Consumer Duty (PRIN 2A) & Section 21 Financial Promotions Gateway (FCA-CONSUMER-DUTY) refers to an institutional financial benchmark and regulatory standard monitored by UK Financial Conduct Authority (UK), currently calibrated at 2 Years (Max s21 Statutory Penalty) as of October 2026.
- [SEC Rule 17a-4 & Rule 204-2 Off-Channel Communications Recordkeeping](https://regtechcodex.org/definitions/sec-rule-17a4-2042-sec-rule-17a-4-rule-204-2-off-channel-communications-recordkeeping) — SEC Rule 17a-4 & Rule 204-2 Off-Channel Communications Recordkeeping (SEC-RULE-17A4-2042) refers to an institutional financial benchmark and regulatory standard monitored by U.S. Securities and Exchange Commission (US), currently calibrated at $2.3B (Cumulative SEC Fines (95 Actions)) as of October 2026.
- [FATF Recommendation 16 & EU TFR (2023/1113) Crypto Wire Travel Rule](https://regtechcodex.org/definitions/fatf-travel-rule-fatf-recommendation-16-eu-tfr-2023-1113-crypto-wire-travel-rule) — FATF Recommendation 16 & EU TFR (2023/1113) Crypto Wire Travel Rule (FATF-TRAVEL-RULE) refers to an institutional financial benchmark and regulatory standard monitored by FATF / European Banking Authority (INTL), currently calibrated at EUR 0 (Zero De Minimis CASP Threshold) as of October 2026.
- [MiFID II Annex II Elective Professional vs. Retail Client Categorization](https://regtechcodex.org/definitions/mifid2-client-cat-mifid-ii-annex-ii-elective-professional-vs-retail-client-categorization) — MiFID II Annex II Elective Professional vs. Retail Client Categorization (MIFID2-CLIENT-CAT) refers to an institutional financial benchmark and regulatory standard monitored by ESMA Directive 2014/65/EU (EU), currently calibrated at EUR 500,000 (Portfolio Size Criterion (2 of 3)) as of October 2026.
- [EU EMIR Refit & UK EMIR ISO 20022 UPI/UTI Derivatives Trade Reporting](https://regtechcodex.org/definitions/emir-refit-2026-eu-emir-refit-uk-emir-iso-20022-upi-uti-derivatives-trade-reporting) — EU EMIR Refit & UK EMIR ISO 20022 UPI/UTI Derivatives Trade Reporting (EMIR-REFIT-2026) refers to an institutional financial benchmark and regulatory standard monitored by ESMA / Bank of England (EU), currently calibrated at T+1 (Trade Repository Reporting SLA) as of October 2026.
- [Singapore MAS Capital Markets Services (CMS) & FAA Licensing Standards](https://regtechcodex.org/definitions/mas-cms-sfa-2026-singapore-mas-capital-markets-services-cms-faa-licensing-standards) — Singapore MAS Capital Markets Services (CMS) & FAA Licensing Standards (MAS-CMS-SFA-2026) refers to an institutional financial benchmark and regulatory standard monitored by Monetary Authority of Singapore (SG), currently calibrated at SGD 150,000 (Statutory Fine Ceiling) as of October 2026.
- [Singapore MAS Capital Markets Services (CMS) & FAA Licensing Standards — 2026 Standard](https://regtechcodex.org/definitions/mas-cms-sfa-2026-2026-benchmark-standard) — MAS-CMS-SFA-2026 2026 Institutional Benchmark Framework is defined as the standardized quantitative and compliance methodology published by Monetary Authority of Singapore governing Singapore MAS Capital Markets Services (CMS) & FAA Licensing Standards across SG capital markets (SGD 150,000 Statutory Fine Ceiling, October 2026).
