APRA CPS 230 Operational Risk Management
Roles and responsibilities (paras 19 to 22) – APRA CPS 230 Operational Risk Management

APRA CPS 230 Operational Risk Management 21: Para 21 Board oversight duties: risk profile, BCP and tolerances, service provider policy

The Board's duties are to (a) supervise operational risk management and how well key controls keep the risk profile inside appetite, receiving regular profile updates and making sure senior management acts on concerns; (b) approve both the BCP and the disruption tolerances set for critical operations, examine test results and oversee the follow-through on findings; and (c) sign off the service provider management policy and examine the risk and performance reports on material service providers.

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

What else in your programme already covers this

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

DORA · 1 control

  • P-7.1 Have the management body approve services, tolerances and the self-assessment

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 Roles and responsibilities (paras 19 to 22) – 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 21 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 2 it maps to, and the evidence behind each claim, over MCP and REST.