Australia Consumer Data Right - Banking (CDR)CIS Controls v8

Australia Consumer Data Right - Banking (CDR) covers 17% of CIS Controls v8

26 of the 153 controls in CIS Controls v8 are already satisfied by evidence you collected for Australia Consumer Data Right - Banking (CDR). 127 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.

17%
of the target already covered
26
controls evidenced
127
genuine gaps
0
claims rejected in review

This number is directional. It says how much of CIS Controls v8 your Australia Consumer Data Right - Banking (CDR) 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.

48 candidate mappings were examined and 0 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.

CIS Control 3: Data Protection7 of 14 evidenced, 7 to do
CIS Control 18: Penetration Testing2 of 5 evidenced, 3 to do
CIS Control 14: Security Awareness and Skills Training3 of 9 evidenced, 6 to do
CIS Control 17: Incident Response Management3 of 9 evidenced, 6 to do
CIS Control 7: Continuous Vulnerability Management2 of 7 evidenced, 5 to do
CIS Control 6: Access Control Management2 of 8 evidenced, 6 to do
CIS Control 5: Account Management1 of 6 evidenced, 5 to do
CIS Control 16: Application Software Security2 of 14 evidenced, 12 to do
CIS Control 10: Malware Defenses1 of 7 evidenced, 6 to do
CIS Control 2: Inventory and Control of Software Assets1 of 7 evidenced, 6 to do
CIS Control 9: Email and Web Browser Protections1 of 7 evidenced, 6 to do
CIS Control 4: Secure Configuration of Enterprise Assets and Software1 of 12 evidenced, 11 to do
CIS Control 1: Inventory and Control of Enterprise Assets0 of 5 evidenced, 5 to do
CIS Control 11: Data Recovery0 of 5 evidenced, 5 to do
CIS Control 12: Network Infrastructure Management0 of 8 evidenced, 8 to do
CIS Control 13: Network Monitoring and Defense0 of 11 evidenced, 11 to do
CIS Control 15: Service Provider Management0 of 7 evidenced, 7 to do
CIS Control 8: Audit Log Management0 of 12 evidenced, 12 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.

AUCDR-IS-5CIS-10.1argued against and upheld
Deploy and Maintain Anti-Malware Software

Control 5 requires anti-malware to limit, prevent, detect and remove malware.

AUCDR-IS-6CIS-14.1argued against and upheld
Establish and Maintain a Security Awareness Program

Control 6 requires a formal security training and awareness program for all personnel.

AUCDR-IS-6CIS-14.4argued against and upheld
Train Workforce on Data Handling Best Practices

Control 6 requires training on handling CDR data and acceptable use of technology.

AUCDR-IS-6CIS-14.9argued against and upheld
Conduct Role-Specific Security Awareness and Skills Training

Control 6 requires training tuned to personnel who interact with CDR data.

AUCDR-IS-4CIS-16.1argued against and upheld
Establish and Maintain a Secure Application Development Process

Control 4 requires secure coding within the vulnerability management program.

AUCDR-IS-3CIS-16.8argued against and upheld
Separate Production and Non-Production Systems

Control 3 requires controls over CDR data used in non-production environments.

AUCDR-IS-STEP5CIS-17.1argued against and upheld
Designate Personnel to Manage Incident Handling

Step 5 requires named responsibilities within the CDR data security response plans.

AUCDR-IS-STEP5CIS-17.3argued against and upheld
Establish and Maintain an Enterprise Process for Reporting Incidents

Step 5 requires procedures to record and report information security incidents.

Claims that did not hold

Nothing proposed for this pair was rejected in review. That is unusual and worth knowing rather than hiding: it means the candidate set was small and every candidate held.

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