TheArtOfService
Cross-Framework Mapping

Australia Consumer Data Right - Banking (CDR)vsPCI DSS 4.0

See exactly how Australia Consumer Data Right - Banking (CDR) controls map to PCI DSS 4.0. Pre-computed mappings, identified gaps, and coverage analysis.

35
Controls Mapped
0
Gaps Found
50%
Coverage

A reviewed coverage crosswalk for this pair is available. See which PCI DSS 4.0 controls you already evidence.

According to the TheArtOfService Compliance Knowledge Graph:

Australia Consumer Data Right - Banking (CDR) maps to PCI DSS 4.0 with 50% coverage across 12 directly mapped controls. Analysis of 24 Australia Consumer Data Right - Banking (CDR) controls identifies 12 compliance gaps, primarily concentrated in Privacy Safeguards.

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

Control Mappings

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

Information Security (Schedule 2)(20 mappings)

AUCDR-IS-1Limit risk of unauthorised access to the CDR data environment7 targets
→10.2.1Audit logs enabled on system components
→7.2.1An access control model is defined and includes granting access as follows: • Appropriate access depending on the entity's business and access needs. • Access to system components and data resources that is based
→7.2.2Access is assigned to users, including privileged users, based on: • Job classification and function. • Least privileges necessary to perform job responsibilities
→8.2.1All users are assigned a unique ID before access to system components or cardholder data is allowed
→8.3.1All user access to system components for users and administrators is authenticated via at least one of the following authentication factors: • Something you know, such as a password or passphrase. • Something you
→8.4.2MFA is implemented for all non-console access into the CDE
→9.1.1All security policies and operational procedures that are identified in Requirement 9 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
AUCDR-IS-2Secure the network and systems within the data environment3 targets
→1.2.1NSC configuration standards defined
→1.4.1NSCs between trusted and untrusted networks
→2.2.1Configuration standards are developed, implemented, and maintained to: • Cover all system components. • Address all known security vulnerabilities. • Be consistent with industry-accepted system hardening standards or vendor hardening recommendations. • Be updated
AUCDR-IS-3Securely manage information assets over their lifecycle2 targets
→12.5.1Inventory of system components in scope
→6.5.5Live PANs not used in pre-production
AUCDR-IS-4Formal vulnerability management program3 targets
→11.3.1Internal vulnerability scans quarterly
→6.2.4Coding practices prevent common attacks
→pci-dss-4-0::6.3.3All system components are protected from known vulnerabilities by installing applicable security patches/updates as follows: • Patches/updates for critical vulnerabilities (identified according to the risk ranking process at Requirement 6.3.1) are installed within one
AUCDR-IS-5Limit, prevent, detect and remove malware4 targets
→5.4.1Processes and automated mechanisms are in place to detect and protect personnel against phishing attacks
→pci-dss-4-0::5.2.1An anti-malware solution(s) is deployed on all system components, except for those system components identified in periodic evaluations per Requirement 5.2.3 that concludes the system components are not at risk from malware
→pci-dss-4-0::5.2.2The deployed anti-malware solution(s): • Detects all known types of malware. • Removes, blocks, or contains all known types of malware
→pci-dss-4-0::5.3.1The anti-malware solution(s) is kept current via automatic updates
AUCDR-IS-6Information security training and awareness program
→12.6.1Formal security awareness program implemented

+15 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 Australia Consumer Data Right - Banking (CDR) 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 Australia Consumer Data Right - Banking (CDR) work already satisfies, which are real gaps, and the reasoning behind every claim so you can check it. One pair, $299, one time.

Australia Consumer Data Right - Banking (CDR) into PCI DSS 4.0
9.6%

24 of 249 PCI DSS 4.0 controls are evidenced by work you have already done for Australia Consumer Data Right - Banking (CDR). 225 are genuine gaps.

29.7%Req 12: Information Security Policies
23.1%Req 5: Anti-Malware
10.5%Req 1: Network Security Controls
9.5%Req 11: Test Security Regularly
Machine verified. Claude Code on the Max plan, judged in context, signed off 2026-08-19. 35 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: 1.2.1 NSC configuration standards defined

Control 2 requires firewalls be configured to secure the data environment network.

Grounded in AUCDR-IS-2 Secure the network and systems within the data environment. Confidence high, survived the refutation pass.

Gap: 1.1.1 NSC policies and procedures documented

All security policies and operational procedures for Requirement 1 are documented, kept current, in use, and known to affected parties.

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

PCI DSS 4.0 into Australia Consumer Data Right - Banking (CDR)
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.

Australia Consumer Data Right - Banking (CDR) to PCI DSS 4.0
$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 50% in the header counts how many Australia Consumer Data Right - Banking (CDR) 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.

Related Comparisons

Other Australia Consumer Data Right - Banking (CDR) comparisons

Australia Consumer Data Right - Banking (CDR) vs GDPR24 mappingsAustralia Consumer Data Right - Banking (CDR) vs APEC Cross-Border Privacy Rules (CBPR) System23 mappingsAustralia Consumer Data Right - Banking (CDR) vs ISO 27701:201923 mappingsAustralia Consumer Data Right - Banking (CDR) vs NIST SP 800-53 Rev 521 mappingsAustralia Consumer Data Right - Banking (CDR) vs SOC 220 mappingsAustralia Consumer Data Right - Banking (CDR) vs FedRAMP Moderate18 mappingsAustralia Consumer Data Right - Banking (CDR) vs FedRAMP High18 mappingsAustralia Consumer Data Right - Banking (CDR) vs NIST SP 800-53 Rev 5 MODERATE17 mappings

Other PCI DSS 4.0 comparisons

SOC 2 vs PCI DSS 4.0247 mappingsISO 27002:2022 vs PCI DSS 4.0247 mappingsNIST SP 800-53 Rev 5 vs PCI DSS 4.0246 mappingsISO 27001:2022 vs PCI DSS 4.0246 mappingsFedRAMP Moderate vs PCI DSS 4.0245 mappingsFedRAMP High vs PCI DSS 4.0245 mappingsNIST SP 800-53 Revision 5.1 HIGH vs PCI DSS 4.0240 mappingsCloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 vs PCI DSS 4.0240 mappings

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 →

Popular framework comparisons

NIST CSF vs NIST 800-53ISO 27001 vs NIST CSFCMMC vs NIST 800-53FedRAMP vs NIST 800-53NIST CSF vs SOC 2HIPAA vs NIST 800-53ISO 27001 vs SOC 2ISO 27001 vs ISO 27701

What are the key differences between Australia Consumer Data Right - Banking (CDR) and PCI DSS 4.0?

Australia Consumer Data Right - Banking (CDR) has 24 controls across its framework, while PCI DSS 4.0 covers 249 controls. Direct mapping analysis identifies 12 overlapping controls (50% coverage). The frameworks diverge most significantly in Privacy Safeguards, where 12 Australia Consumer Data Right - Banking (CDR) controls have no direct PCI DSS 4.0 equivalent.

How many controls map between Australia Consumer Data Right - Banking (CDR) and PCI DSS 4.0?

Of 24 total Australia Consumer Data Right - Banking (CDR) controls, 12 map directly to PCI DSS 4.0 controls, representing 50% coverage. The remaining 12 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping Australia Consumer Data Right - Banking (CDR) to PCI DSS 4.0?

12 Australia Consumer Data Right - Banking (CDR) controls have no direct equivalent in PCI DSS 4.0. The highest concentration of gaps is in Privacy Safeguards with 12 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 Australia Consumer Data Right - Banking (CDR) and PCI DSS 4.0?

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

Related Resources

How to Map Controls Across Frameworks|Multi-Framework Compliance Guide|Compliance Glossary

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.