APRA CPS 234NIST Cybersecurity Framework 2.0

APRA CPS 234 covers 23.6% of NIST Cybersecurity Framework 2.0

25 of the 106 controls in NIST Cybersecurity Framework 2.0 are already satisfied by evidence you collected for APRA CPS 234. 81 are genuine gaps. Every claim below was judged against both control sets and then argued against; the ones that did not survive are published further down with the reason each failed.

23.6%
of the target already covered
25
controls evidenced
81
genuine gaps
3
claims rejected in review

What this leaves you to do

NIST Cybersecurity Framework 2.0 has 106 controls. Holding APRA CPS 234 already evidences 25 of them, so the work in front of you is 81 controls, not 106, which is 76% of the standard rather than all of it.

That is the whole claim. We do not know your hourly rate, how long a control takes you, or how many people you have, so there is no figure here in dollars or weeks. Every number in that sentence comes from the two counts above it and can be re-derived from the free tools without taking our word for any of it.

This number is directional. It says how much of NIST Cybersecurity Framework 2.0 your APRA CPS 234 evidence satisfies. The reverse pair is a different number, often very different, because a security standard has enormous depth for access control and almost none for lawful basis or data subject rights.

49 candidate mappings were examined and 3 were removed. Signed off 2026-08-19, review level machine verified. Mappings were judged by Claude Code rather than read line by line by a practitioner. Every claim shows its reasoning so you can check it. Ask and a practitioner will review this pair.

Where the gaps are

Coverage is never evenly spread. A source standard usually satisfies one part of a target almost completely and barely touches another, and which part is which is the thing worth knowing before you plan the work.

GV - Govern10 of 28 evidenced, 18 to do
ID - Identify7 of 21 evidenced, 14 to do
Govern1 of 3 evidenced, 2 to do
RS - Respond4 of 13 evidenced, 9 to do
DE - Detect3 of 11 evidenced, 8 to do
PR - Protect0 of 22 evidenced, 22 to do
RC - Recover0 of 8 evidenced, 8 to do

Theme level, not control level, deliberately. The per-control list of what is evidenced and what is a gap is the report itself, so publishing it here would be publishing the thing being sold.

Claims that held

A sample. Each one names the control whose evidence does the work, the control it satisfies, and why.

CPS 234 para 23NIST-CSF-DE.AE-02argued against and upheld
Potentially adverse events are analyzed to better understand associated activities

Robust detection mechanisms must identify and interpret information security incidents.

CPS 234 para 25NIST-CSF-DE.AE-06argued against and upheld
Information on adverse events is provided to authorized staff and tools

Plans must define escalation and reporting of incidents to those responsible for managing them.

CPS 234 para 23NIST-CSF-DE.AE-08argued against and upheld
Incidents are declared when adverse events meet the defined incident criteria

Detection mechanisms must determine that an event is an information security incident.

CPS 234 para 27NIST-CSF-GV.OV-03argued against and upheld
Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed

Systematic testing of control effectiveness is how security risk management performance is evaluated.

CPS 234 para 31NIST-CSF-GV.OV-03argued against and upheld
Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed

Sufficiency of the testing programme is reviewed annually and on material change, adjusting the approach.

CPS 234 para 18NIST-CSF-GV.PO-01argued against and upheld
Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced

An information security policy framework proportionate to vulnerabilities and threats must be maintained.

CPS 234 para 19NIST-CSF-GV.PO-02argued against and upheld
Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission

Policy must direct and be communicated to every party obliged to maintain information security.

CPS 234 para 29NIST-CSF-GV.RM-05argued against and upheld
Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third parties

Escalation of unremediated deficiencies to Board or senior management establishes the reporting line.

Claims that did not hold

3 proposed mappings for this pair were rejected. They are kept in the graph rather than deleted, so what was thrown out is as inspectable as what survived. A crosswalk that never rejects anything is not being judged.

CPS 234 para 28NIST-CSF-GV.SC-07
The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritized, assessed, responded to, and monitored over the course of the relationship

NIST CSF 2.0 GV.SC-07 held a different requirement when this was judged: understanding, recording, prioritising and monitoring supplier risk, not verifying supply chain risk management. Corrected against the issued core 2026-08-21. A judgement made against different text is void whatever its outcome.

Claimed at high confidence before it was rejected.

CPS 234 para 34NIST-CSF-GV.SC-07
The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritized, assessed, responded to, and monitored over the course of the relationship

NIST CSF 2.0 GV.SC-07 held a different requirement when this was judged: understanding, recording, prioritising and monitoring supplier risk, not verifying supply chain risk management. Corrected against the issued core 2026-08-21. A judgement made against different text is void whatever its outcome.

Claimed at high confidence before it was rejected.

CPS 234 para 27NIST-CSF-ID.RA-08
Processes for receiving, analyzing, and responding to vulnerability disclosures are established

NIST CSF 2.0 ID.RA-08 held a different requirement when this was judged: vulnerability disclosure processes, not effectiveness of risk responses. Corrected against the issued core 2026-08-21. A judgement made against different text is void whatever its outcome.

Claimed at high confidence before it was rejected.

The full report

Everything above is a sample. The report is every evidenced control and every gap, with the reasoning and the source document behind each one, in a form you can hand to an assessor. $299, emailed immediately.

Buy this crosswalk