APRA CPS 230 Operational Risk Management
Operational risk management, controls and incidents (paras 23 to 32) – APRA CPS 230 Operational Risk Management

APRA CPS 230 Operational Risk Management 29: Para 29 Monitor, review and test controls; report results; rectify gaps promptly

On a regular basis the entity must monitor, review and test its controls for both design and operating effectiveness, at a frequency matched to how material the controlled risk is. Test results must go to senior management, and gaps or deficiencies found in the control environment must be fixed promptly.

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

NIST SP 800-53 Rev 5 · 2 controls

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 Operational risk management, controls and incidents (paras 23 to 32) – 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 29 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.