Skip to content
RegTech Codex
Directory

ศูนย์รวมเนื้อหาหลัก · 20 บทวิเคราะห์ที่เผยแพร่

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.

ประเด็นสำคัญระดับสถาบัน — Dora Operational Ict Compliance

  • Entered into full application on January 17, 2025, EU DORA binds 21 categories of financial entities—including banks, MiFID investment firms, CCPs, Trade Repositories, EMIs, and MiCA CASPs!
  • DORA rests on five statutory pillars: ICT Risk Management (Arts. 5–16), Major Incident Reporting (Arts. 17–23), TLPT Testing (Arts. 24–27), Third-Party Risk & RoI (Arts. 28–44), and CTI Sharing (Art. 45).
  • Delegated Regulation (EU) 2024/2956 enforces a 4-hour Initial Notification and 72-hour Intermediate Report stopwatch from the moment an ICT incident is classified as Major!
  • Joint ESA Lead Overseers (EBA, ESMA, EIOPA) hold direct investigatory and penalty powers (up to 1% of average daily worldwide turnover per day for up to 6 months!) over designated Critical ICT Third-Party Providers (CTPPs)!
  • Implementing Regulation (EU) 2024/2956 standardizes the DORA Article 28(3) Register of Information (RoI) into 15 relational tables (B_01.01 through B_99.01) submitted in EBA Data Point Model xBRL-CSV format!
  • Every non-EU ICT third-party service provider (and critical nth-party subcontractor) MUST be identified by an active 20-character GLEIF LEI, while EU-domiciled providers may use either an LEI or official EUID!

เอนทิตีกราฟความรู้ที่เชื่อมโยง (11)

เอนทิตีทั้งหมด →

บทวิเคราะห์ทั้งหมดในคลัสเตอร์ — Dora Operational Ict Compliance (20)

2026-11-14Victoria Ashworth, LL.M, CAMS

EU DORA Regulation (EU) 2022/2554 Master Guide: ICT Risk, 4h/72h Reporting, RoI & TLPT (2026)

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.

2026-11-13Victoria Ashworth, LL.M, CAMS

DORA Article 28 & ITS (EU) 2024/2956: 15-Template xBRL-CSV Register of Information Guide

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.

2026-11-13Victoria Ashworth, LL.M, CAMS

DORA Article 19 Major ICT Incident Reporting: RTS 2024/1772 Thresholds & 4h/72h/1m SLAs

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.

2026-11-13Victoria Ashworth, LL.M, CAMS

DORA Article 26 Threat-Led Penetration Testing (TLPT): TIBER-EU Live Production & Purple Teaming

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.

2026-11-13Victoria Ashworth, LL.M, CAMS

DORA Article 30 ICT Contractual Clauses: Two-Tier SaaS Repapering, Audit Rights & Exit Plans

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.

2026-11-13Victoria Ashworth, LL.M, CAMS

UK Operational Resilience (FCA PS21/3 & PRA SS2/21) vs EU DORA: Cross-Mapping Dual Programs

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.

2026-11-13Victoria Ashworth, LL.M, CAMS

US SEC Regulation S-P Amendments (2024–2026) & Form 8-K Item 1.05: 4-Day & 30-Day Cyber Clocks

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.

2026-11-13Victoria Ashworth, LL.M, CAMS

DORA vs NIS2 Directive (Article 1(2) Lex Specialis): Dual-Scope Financial Groups & CSIRT Sync

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!

2026-11-13Victoria Ashworth, LL.M, CAMS

DORA Subcontracting RTS (EU) 2025/532: Nth-Party ICT Supply-Chain Monitoring & Exit Triggers

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.

2026-11-13Victoria Ashworth, LL.M, CAMS

DORA Article 29 Cloud Concentration Risk: Multi-Region vs Multi-Cloud RTO/RPO Engineering

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.

2026-11-13Victoria Ashworth, LL.M, CAMS

DORA Article 16 Simplified ICT Risk Framework & Microenterprise Proportionality Carve-Outs

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!

2026-11-13Victoria Ashworth, LL.M, CAMS

DORA Articles 11 & 12 Ransomware Recovery: Immutable Air-Gapped Vaults & Clean-Room Restore

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.

2026-11-13Victoria Ashworth, LL.M, CAMS

NYDFS 23 NYCRR Part 500 (Second Amendment): Class A Audits, 72h Cyber & 24h Extortion Notices

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.

2026-11-13Victoria Ashworth, LL.M, CAMS

DORA Article 45 Cyber Threat Intelligence Sharing: STIX 2.1, TAXII, MISP & GDPR/Antitrust Guardrails

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.

2026-11-13Victoria Ashworth, LL.M, CAMS

MiFID II RTS 6 Algorithmic Trading & DORA Resilience: Kill Switches, Collars & Order-to-Trade Ratios

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.

2026-11-13Victoria Ashworth, LL.M, CAMS

DORA Article 5 Management Body Liability: Board ICT Training, Budgets & CISO Independence

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.

สถาบันการเงินและโบรกเกอร์ภายใต้การกำกับดูแล

หน่วยงานกำกับดูแลและกรอบใบอนุญาตที่เกี่ยวข้อง

หน่วยงานกำกับดูแลทั้งหมด →

คำถามที่พบบ่อย (FAQ) — Dora Operational Ict Compliance

Which financial entities fall within the mandatory scope of EU DORA Article 2?

Article 2(1) captures 21 regulated entity types operating in the EU: credit institutions, payment and e-money institutions, MiFID investment firms, MiCA crypto-asset service providers (CASPs), CSDs, CCPs, trading venues, trade repositories, AIFMs, UCITS management companies, insurers, credit rating agencies, and statutory crowdfunding providers.

Does the 4-hour DORA initial incident notification clock start at detection or at Major classification?

Under Commission Delegated Regulation (EU) 2025/301 (RTS on incident reporting timelines), the 4-hour countdown starts from the moment the financial entity CLASSIFIES the incident as Major (provided classification happens promptly upon detection, and no later than 24 hours after initial detection when automated data collection requires validation).

What is the DORA Register of Information (RoI) and how do NCAs collect it?

Under DORA Article 28(3) and Commission Implementing Regulation (EU) 2024/2956 (ITS), every financial entity must maintain a relational 15-template Register of Information (RT.01 to RT.99) mapping all ICT third-party contracts, LEIs, critical functions, and nth-party subcontractors, submitted annually to NCAs in xBRL-CSV plain-CSV packages.

How does EU DORA interact with NIS2 Directive (EU) 2022/2555 for banks and brokers?

Under DORA Article 1(2) and NIS2 Article 4, DORA operates as lex specialis (sector-specific overriding law) for in-scope financial entities—meaning financial firms comply with DORA’s ICT risk, incident reporting, and supervisory rules instead of duplicative general NIS2 provisions.

Why did the European Commission reject draft RoI rules in late 2024 before adopting ITS (EU) 2024/2956?

The original Joint ESA draft mandated EXCLUSIVELY GLEIF LEIs for every ICT supplier worldwide, sparking pushback that small EU software vendors lacked LEIs; final ITS (EU) 2024/2956 allows EU-established ICT legal entities to use either an LEI or their free national business-registry European Unique Identifier (EUID), while keeping LEIs mandatory for third-country (non-EU) vendors!

Must intra-group IT shared-service subsidiaries be recorded inside the DORA Register of Information?

Yes! DORA Article 2(21) and Article 28 define "ICT third-party service provider" to INCLUDE intra-group ICT service entities (such as a UK, US, or Polish group technology hub providing trading, cloud, or SOC services to an EU regulated subsidiary)—explicitly differentiated via intra-group flags in B_02.02!

สำรวจคลัสเตอร์หัวข้อวิจัยที่เกี่ยวข้อง (RegTech Codex)

Dora Operational Ict Compliance — ศูนย์รวมเนื้อหาหลัก | RegTech Codex | RegTech Codex