PCI DSS 4.0APRA CPS 234

PCI DSS 4.0 covers 54.2% of APRA CPS 234

13 of the 24 controls in APRA CPS 234 are already satisfied by evidence you collected for PCI DSS 4.0. 11 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.

54.2%
of the target already covered
13
controls evidenced
11
genuine gaps
0
claims rejected in review

This number is directional. It says how much of APRA CPS 234 your PCI DSS 4.0 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 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.

Third Party Arrangements3 of 3 evidenced
Incident Management3 of 3 evidenced
Policy Framework2 of 2 evidenced
Testing Control Effectiveness2 of 4 evidenced, 2 to do
Roles and Responsibilities1 of 2 evidenced, 1 to do
Implementation of Controls1 of 2 evidenced, 1 to do
Internal Audit1 of 3 evidenced, 2 to do
Information Security Capability0 of 2 evidenced, 2 to do
Information Asset Identification and Classification0 of 1 evidenced, 1 to do
APRA Notification0 of 2 evidenced, 2 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.

12.1.4CPS 234 para 14argued against and upheld
Definition of Information Security Roles and Responsibilities

Formal assignment of security responsibility to a CISO or equivalent names the accountable executive.

12.1.3CPS 234 para 14argued against and upheld
Definition of Information Security Roles and Responsibilities

Security roles and responsibilities defined and formally acknowledged is the same requirement.

12.8.4CPS 234 para 16argued against and upheld
Assessment of Related Party and Third Party Capability

Monitoring provider compliance status at least annually sustains that assessment.

12.8.3CPS 234 para 16argued against and upheld
Assessment of Related Party and Third Party Capability

Due diligence before engaging a third party is the capability assessment required.

12.1.2CPS 234 para 18argued against and upheld
Information Security Policy Framework

Review at least annually and update on change keeps the framework proportionate.

12.1.1CPS 234 para 18argued against and upheld
Information Security Policy Framework

An overall information security policy established, published and maintained is the policy framework.

12.1.1CPS 234 para 19argued against and upheld
Policy Direction to All Responsible Parties

Dissemination of the policy to all relevant personnel is the direction to responsible parties.

12.8.5CPS 234 para 22argued against and upheld
Evaluation of Third Party Control Design

Recording which requirements each provider manages is the design evaluation basis.

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