Cross-Framework Mapping

APRA CPS 234vsPCI DSS 4.0

See exactly how APRA CPS 234 controls map to PCI DSS 4.0. Pre-computed mappings, identified gaps, and coverage analysis.

56
Controls Mapped
0
Gaps Found
96%
Coverage

A reviewed coverage crosswalk for this pair is available. See which APRA CPS 234 controls you already evidence.

According to the TheArtOfService Compliance Knowledge Graph:

APRA CPS 234 maps to PCI DSS 4.0 with 96% coverage across 23 directly mapped controls. Analysis of 24 APRA CPS 234 controls identifies 1 compliance gaps, primarily concentrated in APRA Notification.

Source: TheArtOfService Knowledge Graph | 24 controls analysed | 686 frameworks | 309K+ cross-framework mappings

Control Mappings

Showing 20 of 56 mapped controls across 10 domains. Sign up to explore all 309K+ mappings across 686 frameworks.

Roles and Responsibilities(5 mappings)

CPS234-13Board Responsibility for Information Security2 targets
12.1.4CISO or equivalent responsibility
12.4.1Executive management responsibility for the PCI DSS compliance program (service providers)
CPS234-14Definition of Information Security Roles and Responsibilities3 targets
1.1.2Roles and responsibilities for Requirement 1
12.1.3Information security roles and responsibilities defined and acknowledged
12.1.4CISO or equivalent responsibility

Information Security Capability(4 mappings)

CPS234-15Information Security Capability
12.6.1Formal security awareness program implemented
CPS234-P17Active Maintenance of Capability Against Change3 targets
11.3.1Internal vulnerability scans quarterly
12.1.2The information security policy is: • Reviewed at least once every 12 months. • Updated as needed to reflect changes to business objectives or risks to the environment
12.3.4Hardware and software technologies reviewed annually

Third Party Arrangements(9 mappings)

CPS234-16Assessment of Related Party and Third Party Capability4 targets
12.8.1Third-party service provider inventory
12.8.3TPSP due diligence
12.8.4TPSP compliance monitored
12.8.5Responsibility matrix with TPSPs
CPS234-P22Evaluation of Third Party Control Design3 targets
12.8.3TPSP due diligence
12.8.4TPSP compliance monitored
12.8.5Responsibility matrix with TPSPs
CPS234-P28Assessment of Reliance on Third Party Control Testing2 targets
12.8.4TPSP compliance monitored
12.9.2TPSP supports customer requests for compliance info (SP)

Policy Framework(2 mappings)

CPS234-19Information Security Policy Framework2 targets
12.1.1An overall information security policy is: • Established. • Published. • Maintained. • Disseminated to all relevant personnel, as well as to relevant vendors and business partners
12.1.2The information security policy is: • Reviewed at least once every 12 months. • Updated as needed to reflect changes to business objectives or risks to the environment

+36 more mappings

Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 686 frameworks.

Create Free Account →

Free forever, no credit card required

Coverage crosswalk

The APRA CPS 234 to PCI DSS 4.0 crosswalk

The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which PCI DSS 4.0 controls your existing APRA CPS 234 work already satisfies, which are real gaps, and the reasoning behind every claim so you can check it. One pair, $299, one time.

APRA CPS 234 into PCI DSS 4.0
Not published yet

This direction has not been through crosswalk review and sign off, so no coverage figure is published for it. Reporting an unreviewed number would be worse than reporting none. It can be built to order at the same price as a pair that is already on the shelf.

If the two frameworks turn out to have too little in common for a crosswalk to help you, we say so and refund it rather than send a number worth nothing.

PCI DSS 4.0 into APRA CPS 234
54.2%

13 of 24 APRA CPS 234 controls are evidenced by work you have already done for PCI DSS 4.0. 11 are genuine gaps.

100%Third Party Arrangements
100%Incident Management
100%Policy Framework
50%Testing Control Effectiveness
Machine verified. Claude Code on the Max plan, judged in context, signed off 2026-08-19. 49 candidate mappings were examined and 0 were removed by a pass whose job was to argue against them.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.

A sample of what the report says

Evidenced: CPS 234 para 14 Definition of Information Security Roles and Responsibilities

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

Grounded in 12.1.3 Information security roles and responsibilities defined and acknowledged. Confidence high, survived the refutation pass.

Gap: CPS 234 para 13 Board Responsibility for Information Security

The Board carries ultimate responsibility for the entity information security and must ensure it is maintained in proportion to the threats facing the information assets.

Every one of the 13 evidenced controls and 11 gaps in the report carries this much reasoning, so you can check the claim rather than take it on trust.

PCI DSS 4.0 to APRA CPS 234
$299
per framework pair, one time
  • Every evidenced control, with the reasoning behind it
  • Every gap, with what it requires
  • Its level of review stated plainly, not a bare number

Why this page shows two different percentages. The 96% in the header counts how many APRA CPS 234 controls carry at least one candidate mapping in the graph, before any review. The crosswalk percentage counts something stricter: how many PCI DSS 4.0 controls are actually evidenced, after a pass that argued against each mapping and kept only what survived. They answer different questions and they are not meant to agree.

A crosswalk narrows the work. It does not replace an audit, and your assessor may take a different view on individual controls. Mappings between frameworks are judgements, not text printed in either standard, which is why every claim in the report shows its reasoning. Questions go to support@theartofservice.com.

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 686 frameworks, at a fraction of consulting costs.

$0/forever

Free

  • 686 framework browser
  • Cross-framework mappings (309K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$149/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between APRA CPS 234 and PCI DSS 4.0?

APRA CPS 234 has 24 controls across its framework, while PCI DSS 4.0 covers 249 controls. Direct mapping analysis identifies 23 overlapping controls (96% coverage). The frameworks diverge most significantly in APRA Notification, where 1 APRA CPS 234 controls have no direct PCI DSS 4.0 equivalent.

How many controls map between APRA CPS 234 and PCI DSS 4.0?

Of 24 total APRA CPS 234 controls, 23 map directly to PCI DSS 4.0 controls, representing 96% coverage. The remaining 1 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping APRA CPS 234 to PCI DSS 4.0?

1 APRA CPS 234 controls have no direct equivalent in PCI DSS 4.0. The highest concentration of gaps is in APRA Notification with 1 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between APRA CPS 234 and PCI DSS 4.0?

The domain with the highest gap count is APRA Notification (1 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.