Skip to content
RegTech Codex
Directory

Dora Operational Ict Compliance

Singapore MAS TRM & Notice PSN05/644 vs Australia APRA CPS 230: APAC Operational Resilience Map

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.

By Victoria Ashworth, LL.M, CAMSReview not recorded · Updated
Singapore MAS TRM & Notice PSN05/644 vs Australia APRA CPS 230: APAC Operational Resilience Map — RegTech Codex 2026 quantitative & supervisory data card
RegTech Codex (EU DORA Third-Party ICT Risk, Incident Reporting Timelines & TLPT Testing): Singapore MAS <=1-hour incident notice & <=4h/year cumulative downtime cap vs Australia APRA CPS 230 (live July 2025).Source: RegTech Codex Institutional Research DeskLicense: CC-BY-4.0

European CISOs building 4-hour EU DORA playbooks get a wake-up call the day their group acquires or launches a Capital Markets Services (CMS) brokerage in Singapore or an APRA-regulated institution in Sydney: *Singapore’s Monetary Authority of Singapore (MAS) enforces a 60-minute (<= 1 Hour) statutory incident notification clock AND caps cumulative* unscheduled downtime per Critical System to <= 4 hours across any rolling 365-day window (`violated by DBS Bank in 2023, resulting in a 6-month pause on non-essential IT changes + a 1.8x Operational Risk RWA Capital Multiplier (~SGD 1.6 billion extra regulatory capital!)`), while Australian Prudential Regulation Authority (`APRA`) Prudential Standard CPS 230 went live on July 1, 2025**! Anchored by Singapore MAS CMS Licensing Standards, 2026 MAS Benchmarks, EU DORA Core Rules, and DORA Incident SLAs alongside HKMA `OR-2` / `C-RAF` and Korea FSS, global brokers like CMC Markets, IC Markets, CLSA, and Doo Prime run unified APAC-EU resilience matrices. Review our EU DORA Compliance Master Guide 2026 inside the DORA operational compliance hub.

Global Four-Hub Resilience Comparison: MAS TRM vs APRA CPS 230 vs HKMA OR-2 vs EU DORA#

Notice how Singapore sets the tightest availability & initial-alert stopwatch while Europe (DORA) sets the deepest relational xBRL-CSV supply-chain schema:

Quantitative Distribution · Singapore (MAS Notice 644 / CMG-N03 / PSN05)
Singapore (MAS Notice 644 / CMG-N03 / PSN05)Australia (APRA CPS 230, Live Jul 2025)
011. Initial Incident Clock<= 1 HOUR (60 m…022. Root-Cause Report<= 14 Calendar …033. Hard Availability Cap<= 4 Hours Tota…044. Third-Party RegisterOutsourcing Reg…
Resilience RequirementSingapore (MAS Notice 644 / CMG-N03 / PSN05)Australia (APRA CPS 230, Live Jul 2025)Hong Kong (HKMA OR-2 / SFC Electronic)European Union (DORA 2022/2554)
1. Initial Incident Clock<= 1 HOUR (60 mins) upon discovery of Relevant Incident!<= 72 Hours (Material Incident) / <= 24 Hours (Tolerance Breach!)Prompt / Immediate (HKMA e-banking/cyber; SFC material system failure)<= 4 Hours from Major Classification (<=24h from detect)
2. Root-Cause Report<= 14 Calendar Days (MAS IT Incident RCIA Template)Post-incident remediation tracked by APRAWritten forensic report (7–14 days)<= 72h Intermediate + <= 1 Month Final
3. Hard Availability Cap<= 4 Hours Total Unscheduled Downtime per Critical System per Rolling 12 Months!Board-approved Tolerance Levels (Max Disruption Time + Data Loss)Severe-but-plausible Critical Operation tolerances (OR-2)Defined RTO/RPO (<=2h FMI target in RTS Art. 24(2))
4. Third-Party RegisterOutsourcing Register (MAS Outsourcing Notice/Guidelines + 4th-party check)Annual Material Service Provider (MSP) Register to APRA + <=20 BD new MSP notice!HKMA SA-2 Outsourcing + SFC Electronic Data Storage (EDSP two-MIC rule!)Annual 15-table xBRL-CSV RoI (Rank 1..N)
5. Supervisory HammerCapital Multiplier (1.5x–1.8x RWA) + IT Acquisition/Change Moratorium!CPS 230 Para 18 Capital Add-On + Enforceable UndertakingSFC Manager-In-Charge (MIC IT) fine/banFines + CTPP 1%/day + Art. 42 Contract Termination!
Follow-the-sun APAC and EU operational resilience control plane calibrated to Singapore MAS 60-minute incident SLA, 4h/year rolling error budget, APRA CPS 230, and EU DORA
Follow-the-sun APAC and EU operational resilience control plane calibrated to Singapore MAS 60-minute incident SLA, 4h/year rolling error budget, APRA CPS 230, and EU DORAVerified Exhibit

SRE Error-Budget Engineering for Singapore’s 240-Minute Rolling 12-Month Cap!#

Think through what <= 4 hours (240 minutes) of cumulative unscheduled downtime across ANY rolling 365-day window means for Site Reliability Engineering (SRE): if a clumsy database schema migration in March causes a 135-minute Singapore trading outage, and a cloud load-balancer glitch in August causes an 80-minute outage (215 minutes cumulative), a single 26-minute outage anywhere in the next 7 months triggers a statutory breach of MAS Notice CMG-N03 / PSN05 / 644! High-discipline APAC platforms enforce an Automated SRE Error-Budget Freeze: whenever rolling 365-day unscheduled downtime on any Critical System exceeds 120 minutes (50% budget), all non-emergency feature deployments halt until Active-Active zero-downtime blue/green deployment controls are verified!

Rolling 365-Day MAS Downtime Budget & Multi-Regulator Clock Dispatch Equations#

Global observability dashboards compute live Rolling Remaining MAS Error Budget ($B_{\text{mas}}$) at minute $t$ and sequence multi-jurisdiction notifications:

Formula or model from the articleNot independently verified
Cumulative_Downtime_365d(sys, t) = sum_(e in Unscheduled_Outages(sys, [t - 365d, t])) Duration_Minutes(e)
  • RemainingMASBudgetMin(sys, t) = 240.0 - CumulativeDowntime_365d(sys, t) (Breach if < 0; Mandatory Feature Freeze if < 120.0!)
  • GlobalAlertSequence(Tdetect) : [ T+60m : MASSG ] -> [ Tclass+4h : EUDORANCA ] -> [ Ttol+24h : APRACPS230Tol ] -> [ T+72h : NYDFS / APRA / GDPR ]
Root causes of APAC operational resilience enforcement actions and capital add-ons across MAS Singapore, APRA Australia, and HKMA/SFC Hong Kong
Root causes of APAC operational resilience enforcement actions and capital add-ons across MAS Singapore, APRA Australia, and HKMA/SFC Hong KongVerified Exhibit

Critical Lesson on the 60-Minute MAS Clock: *Notify on Impact* Immediately—Never Wait for Root Cause!**#

Why do firms blow the 1-hour MAS deadline? Because engineers try to diagnose why Kubernetes pods are crashing before calling Compliance! Under MAS Notice CMG-N03 / 644, you have 14 full days to submit the Root Cause and Impact Analysis (RCIA)—the 60-minute notification requires ONLY brief initial awareness that a Critical System / customer service is materially impacted! Wire an automated T+30 minute PagerDuty escalation straight to the Singapore Chief Executive / Compliance Officer whenever synthetic login or order probes fail for 15 consecutive minutes.

Connecting APAC MAS/APRA Rules to UK SYSC 15A, EU DORA & APAC Client Money#

Integrate Asia-Pacific operational resilience directly with UK FCA PS21/3 & PRA SS2/21 vs EU DORA mapping, multi-cloud active-active RTO/RPO architectures, and Singapore MAS SFA & Hong Kong SFC Cap. 571O client money deadlines.

Frequently asked questions

Is Singapore’s 4-hour critical-system downtime cap in MAS Notice CMG-N03 / 644 per incident or per 12 months?

PER ROLLING 12 MONTHS! Under Paragraph 6 of MAS Notice 644 / Notice CMG-N03 / Notice PSN05, a financial institution must ensure that the total unscheduled downtime for each Critical System affecting operations or service to customers does not exceed a total of 4 hours within any period of 12 months (99.954%+ rolling annual availability)—three separate 90-minute outages in 11 months breach the law!

How fast must a Singapore broker or bank notify MAS upon discovering a Critical System outage or cyber intrusion?

Within 60 MINUTES (<= 1 Hour)! Under MAS Notice on Technology Risk Management, upon the discovery of a Relevant Incident (an IT incident having a severe and widespread impact on operations or materially impacting service to customers), the institution must notify MAS as soon as possible, but not later than 1 hour, and submit a Root Cause and Impact Analysis (RCIA) report within 14 days!

When did Australia APRA Prudential Standard CPS 230 take effect and what did it replace?

APRA Prudential Standard CPS 230 (Operational Risk Management) commenced on July 1, 2025 (with limited pre-existing vendor contract transition to July 1, 2026), superseding five legacy APRA outsourcing and business-continuity standards (CPS 231, SPS 231, HPS 231, CPS 232, SPS 232) into one unified DORA/UK-style operational resilience standard!

What are the mandatory APRA notification clocks under CPS 230 Paragraphs 33 and 56?

Under CPS 230: (1) notify APRA within <=72 hours of a material operational risk incident OR within <=24 hours if a Business Continuity tolerance level is breached (Para 33/44), and (2) notify APRA prior to entering (or within <=20 business days of) material service provider agreements plus submit an annual MSP Register!

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

Open Attribution License (CC BY 4.0)

Standard academic & institutional research paper citation format.

Victoria Ashworth, LL.M, CAMS. (2026, November 14). Singapore MAS TRM & Notice PSN05/644 vs Australia APRA CPS 230: APAC Operational Resilience Map. RegTech Codex. https://regtechcodex.org/briefings/mas-trm-guidelines-apra-cps-230-apac-operational-resilience-map
Explore Dora Operational Ict Compliance Hub (20) →

RegTech Codex Data, Benchmarks & Contributor Records

Singapore MAS TRM & Australia APRA CPS 230 vs EU DORA (2026) | RegTech Codex