Dora Operational Ict Compliance
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.

Dual-hub financial groups operating both a Canary Wharf entity supervised by the UK Financial Conduct Authority and Prudential Regulation Authority and an Amsterdam, Paris, or Dublin entity supervised by DNB, ACPR, or ECB faced twin statutory deadlines just ten weeks apart in Q1 2025: January 17, 2025 (EU DORA) and March 31, 2025 (UK FCA PS21/3 / SYSC 15A & PRA SS2/21 end of transition)! Anchored by EU DORA Core Rules, 2026 DORA Benchmark Controls, and UK FCA Consumer Duty Outcomes, cross-Channel brokers and platforms such as CMC Markets, Interactive Investor, ICAP, and Coinbase avoid maintaining two conflicting CMDBs by engineering a Superset Resilience Taxonomy. Review our EU DORA Compliance Master Guide 2026 inside the DORA operational compliance hub.
Granular Crosswalk: UK FCA SYSC 15A / PRA SS2/21 vs EU DORA (2022/2554)#
Use this architectural mapping table to build one unified resilience operating model satisfying both London and Brussels/Frankfurt:
| Resilience Dimension | UK Regime (FCA SYSC 15A / PRA SS2/21 / PS16/24) | EU DORA (Reg 2022/2554 + RTS/ITS) | Superset Harmonization Rule (Run Both Cleanly!) |
|---|---|---|---|
| 1. Hazard Scope | All-Hazards Operational (People, Premises, Processes, Physical Power, AND ICT/Third-Parties) | ICT & Cyber Specific (Digital systems, data, cloud & ICT third-party chains) | Map 4-Pillar UK Resource Graph (People+Premises+Process+ICT) where the ICT branch equals your DORA asset inventory! |
| 2. Service Unit | Important Business Services (IBS) — strictly external user/market services (typically 5–15 IBSs) | Critical or Important Functions (CIFs) — external plus internal risk/recon/AML (typically 15–35 CIFs) | Tag every UK IBS as CIF_External = True inside a unified CIF + IBS service registry! |
| 3. Outage Ceiling | Impact Tolerance (Max tolerable disruption time + optional volume before intolerable harm/instability) | RTO & RPO (Art. 11–12 + B_06.01 RoI fields) | Enforce mathematical rule: System_RTO_Sum < Service_Impact_Tolerance (e.g. 45m RTO inside 2h Impact Tolerance!) |
| 4. Scenario Testing | Severe-But-Plausible Scenarios (SYSC 15A.5) proving firm stays within Impact Tolerance post-Mar 2025! | Annual Art. 25 ICT tests + 3-year TIBER-EU TLPT (Art. 26) (vs UK CBEST) | Execute joint Severe-But-Plausible + Ransomware/Cloud-Region-Loss live failover tests! |
| 5. Vendor & Incident | UK Critical Third Parties (CTP, PS16/24) + SUP 15.3 / CP24/28 Phased Incident & Outsourcing Register | EU CTPPs (Art. 31), 15-table xBRL-CSV RoI, & 4h/72h/1m Art. 19 SLA | Maintain 15-table DORA RoI covering UK+EU entities & run <=4h SOAR triage for both FCA/PRA and EU NCAs! |
Crucial Dual-Regulated Trap: Why FCA and PRA Require Two Separate Impact Tolerances on the Same IBS!#
If your London entity is dual-regulated by both the PRA and FCA (such as a bank or PRA-designated investment firm), setting one generic Impact Tolerance per Important Business Service fails SS2/21 and PS21/3! Why? Because the FCA tests intolerable harm to consumers or market integrity (which on retail card/margin close-outs might breach at 2 hours!), whereas the PRA tests threat to firm safety & soundness / UK financial stability (which might breach at 6 hours when liquidity outflows spike). You must set both tolerances and engineer systems to meet the tighter (minimum) of the two!
End-to-End Impact Tolerance vs Component DORA RTO Margin Equation#
Site reliability engineers (SREs) prove compliance with the UK March 31, 2025 enforcement gate by verifying a positive Resilience Headroom Margin ($M_{\text{ibs}} > 0$) across every severe-but-plausible scenario $s$:
- TotalRecoveryPath(ibs, s) = TDetect(s) + TDecisionFailover(s) + max(c in CriticalPathComponents) RTOTested(c, s) + TDataReconCatchup(s)
- ResilienceHeadroom(ibs, s) = EffectiveIBSTolerance(ibs) - TotalRecovery_Path(ibs, s)
- March2025ComplianceGate : Require ResilienceHeadroom(ibs, s) >= 0.20 * EffectiveIBSTolerance(ibs) across ALL Severe-Plausible Scenarios s!
- Worked Check ("Client Position Close-Out" IBS: FCA Tol = 120m; Detect=8m + Failover=12m + DB_RTO=35m + Recon=20m = 75m -> Headroom = +45m PASS!)
Grounding Impact Tolerances in Empirical FCA Consumer Duty Harm Data#
In its operational resilience thematic reviews, the FCA criticized firms that arbitrarily wrote "24-hour Impact Tolerance" on trading or withdrawal portals solely because their legacy backup tape took 20 hours to restore! *Impact Tolerances must be set based on when intolerable client/market harm* occurs—NOT what your legacy IT can currently achieve** (and if legacy IT takes 20 hours while intolerable client margin-liquidation harm hits at 2 hours, SYSC 15A mandated re-architecting IT before March 31, 2025!).
Connecting UK SYSC 15A Resilience to EU DORA, APAC CPS 230 & Cloud Failover#
Link cross-Channel resilience governance directly to EU DORA 4-hour incident classification & SLAs, Singapore MAS TRM & Australian APRA CPS 230 mapping, and multi-cloud active-active RTO/RPO engineering.
Frequently asked questions
What is the difference between a UK "Important Business Service (IBS)" and an EU DORA "Critical or Important Function (CIF)"?
A UK Important Business Service (SYSC 15A.1) MUST be an external-facing service delivered to end clients or the market (e.g., "Retail Client Cash Withdrawal" or "Equity Order Execution"—internal HR/Payroll is NEVER an IBS!). An EU DORA Critical or Important Function (Art. 3(22)) encompasses both external client services AND internal risk/compliance/treasury functions whose disruption materially impairs licensing conditions or soundness!
How does a UK "Impact Tolerance" differ from traditional IT Disaster Recovery RTO (Recovery Time Objective)?
An IT RTO measures how fast a single server or database recovers; a UK Impact Tolerance (SYSC 15A.2) sets the maximum tolerable level of disruption to an entire end-to-end Important Business Service (expressed ALWAYS with a time-duration metric—e.g., "maximum 2 hours inability to close out leveraged CFD positions"—plus optional volume/value metrics) beyond which intolerable consumer harm or market instability occurs!
Are small UK FCA Core SM&CR investment brokers captured by full SYSC 15A Operational Resilience rules?
No! Unlike EU DORA (which captures nearly all MiFID firms and CASPs directly, offering Art. 16 simplified rules to smaller ones), full FCA SYSC 15A applies specifically to UK banks, building societies, PRA-designated investment firms, Enhanced-scope SM&CR firms, RIEs, and authorised EMI/payment firms—though SYSC 4/8 and Consumer Duty still bind all firms!
Can a dual-regulated London + Frankfurt/Dublin group maintain one unified resilience governance pack?
Yes, provided you map the superset! Treat every UK Important Business Service (IBS) as a customer-facing subset of your broader EU DORA Critical or Important Function (CIF) catalog, apply DORA’s stricter 4-hour incident clock and ITS 2024/2956 RoI schema group-wide, and attach annual UK SYSC 15A.6 Self-Assessment Board sign-offs!
Publication record
- Published
- 13 November 2026
- Updated
- 14 November 2026
- Author
- Victoria Ashworth, LL.M, CAMS
- Review
- Review not recorded
- Automated fact check
- Passed in the stored pipeline record
- Source URLs
- 3 recorded
AI assistance recorded: anthropic/claude-opus-4.6. This field does not establish human review or source verification.
Academic & Institutional Attribution
Cite This Research & Embed Live Data Card
Standard academic & institutional research paper citation format.
Victoria Ashworth, LL.M, CAMS. (2026, November 14). UK Operational Resilience (FCA PS21/3 & PRA SS2/21) vs EU DORA: Cross-Mapping Dual Programs. RegTech Codex. https://regtechcodex.org/briefings/uk-fca-ps21-3-pra-ss2-21-impact-tolerances-vs-eu-dora-mappingRelated Dora Operational Ict Compliance & Institutional Briefings
Explore Dora Operational Ict Compliance Hub (20) →Dora Operational Ict Compliance
EU DORA Regulation (EU) 2022/2554 Master Guide: ICT Risk, 4h/72h Reporting, RoI & TLPT (2026)Dora Operational Ict Compliance
US SEC Regulation S-P Amendments (2024–2026) & Form 8-K Item 1.05: 4-Day & 30-Day Cyber ClocksDora Operational Ict Compliance
DORA vs NIS2 Directive (Article 1(2) Lex Specialis): Dual-Scope Financial Groups & CSIRT SyncDora Operational Ict Compliance
DORA Subcontracting RTS (EU) 2025/532: Nth-Party ICT Supply-Chain Monitoring & Exit TriggersDora Operational Ict Compliance
AI & LLM Governance in Trade Surveillance & AML: EU AI Act (2024/1689), DORA & SR 11-7Dora Operational Ict Compliance
DORA Article 29 Cloud Concentration Risk: Multi-Region vs Multi-Cloud RTO/RPO EngineeringDora Operational Ict Compliance
DORA RTS (EU) 2024/1774 Articles 6 & 7: Encryption, HSM Key Lifecycle & Post-Quantum ReadinessDora Operational Ict Compliance
DORA Article 16 Simplified ICT Risk Framework & Microenterprise Proportionality Carve-OutsRegulatory Compliance
After 900 IT Incidents, BaFin Expands Cybersecurity Oversight, Sets 2030 Encryption Target - Finance MagnatesRegulatory Compliance
‘Defiance’ politics risks trapping billions in capital, French regulator warns - TheBanker.comRegulatory Compliance
Bowman, Supervisory Modernization After Silicon Valley BankRegulatory Compliance
FSB urgest Turkey to tighten crypto oversight, set stablecoin rules
RegTech Codex Data, Benchmarks & Contributor Records
CC BY 4.0 Open Data
Open Institutional Datasets (CSV / JSON) →
Download desk-compiled quantitative series & schemas.
2026 Reference Matrix
2026 Institutional Benchmarks & Thresholds →
Statutory capital, clearing, margin & rate conventions.
Editorial Records
Authors & Review Records →
View named contributors where those records are available.
Complete Index
Master Research & Dossier Archive →
Browse all published briefings by topic pillar & date.
