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 11: Para 11 Key principles: manage operational risk, keep critical operations within tolerance, manage service provider risk

The entity is bound by three overarching principles: run effective operational risk management while setting and upholding suitable conduct and compliance standards; keep its critical operations inside their tolerance levels even when a severe disruption hits; and control the risks that come from relying on service providers. Every later paragraph elaborates one of these three.

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.

  • F-3.1 Maintain sound, effective and comprehensive strategies, processes and systems for operational resilience

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 11 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.

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.

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.