APRA CPS 230 Operational Risk Management
Key principles and operational risk management framework (paras 11 to 18) – APRA CPS 230 Operational Risk Management

APRA CPS 230 Operational Risk Management 13: Para 13 Prevent disruption, adapt within tolerance and return to normal promptly

So far as practicable the entity must stop disruptions to critical operations from happening, must be able to adjust its processes and systems to keep operating inside tolerance when one does happen, and must restore normal operations quickly once the disruption ends.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

UK FCA/PRA Operational Resilience Framework · 1 control

  • F-2.9 Be able to remain within impact tolerance in severe but plausible disruption (by 31 March 2025)

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Key principles and operational risk management framework (paras 11 to 18) – APRA CPS 230 Operational Risk Management

You are reading one control. How much of APRA CPS 230 Operational Risk Management have you already done?

APRA CPS 230 Operational Risk Management 13 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of APRA CPS 230 Operational Risk Management your existing evidence covers. Hold NIST Cybersecurity Framework 2.0 and 30 of 87 APRA CPS 230 Operational Risk Management controls already carry evidence.

If you hold NIST Cybersecurity Framework 2.034.5% covered · 57 gapsIf you hold DORA31% covered · 60 gapsIf you hold NIST SP 800-53 Rev 528.7% covered · 62 gapsIf you hold FedRAMP Moderate27.6% covered · 63 gapsIf you hold SOC 224.1% covered · 66 gapsIf you hold ISO 27001:202221.8% covered · 68 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 4 were rejected on the NIST Cybersecurity Framework 2.0 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll APRA CPS 230 Operational Risk Management controls