Clock: as soon as possible, and at the latest 72 hours from the time the entity becomes aware. Trigger: an operational risk incident the entity has determined is likely to cause a material financial impact, or to materially affect its ability to keep its critical operations running. An information security incident already notified to APRA under CPS 234 need not be notified again under this paragraph.
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.
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.
APRA CPS 230 Operational Risk Management 32 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.
The graph holds this control, the 2 it maps to, and the evidence behind each claim, over MCP and REST.