Cross-Framework Mapping

AWS Well-Architected Security PillarvsAustralia Consumer Data Right - Banking (CDR)

See exactly how AWS Well-Architected Security Pillar controls map to Australia Consumer Data Right - Banking (CDR). Pre-computed mappings, identified gaps, and coverage analysis.

29
Controls Mapped
34
Gaps Found
38%
Coverage

A reviewed coverage crosswalk for this pair is available. See which Australia Consumer Data Right - Banking (CDR) controls you already evidence.

According to the TheArtOfService Compliance Knowledge Graph:

AWS Well-Architected Security Pillar maps to Australia Consumer Data Right - Banking (CDR) with 38% coverage across 24 directly mapped controls. Analysis of 63 AWS Well-Architected Security Pillar controls identifies 39 compliance gaps, primarily concentrated in Identity & Access Management.

Source: TheArtOfService Knowledge Graph | 63 controls analysed | 868 frameworks | 315K+ cross-framework mappings

Control Mappings

Showing 20 of 29 mapped controls across 7 domains. Sign up to explore all 315K+ mappings across 868 frameworks.

Security Foundations(5 mappings)

SEC01-BP01Separate workloads using accounts
→AUCDR-IS-STEP2Step 2 - Define the boundaries of the CDR data environment
SEC01-BP03Identify and validate control objectives2 targets
→AUCDR-IS-STEP1Step 1 - Define and implement security governance for CDR data
→AUCDR-IS-STEP4Step 4 - Implement a formal controls assessment program
SEC01-BP04Stay up to date with security threats and recommendations
→AUCDR-IS-STEP3Step 3 - Have and maintain an information security capability
SEC01-BP08Evaluate and implement new security services and features regularly
→AUCDR-IS-STEP3Step 3 - Have and maintain an information security capability

Identity & Access Management(3 mappings)

SEC02-BP01Use strong sign-in mechanisms
→AUCDR-IS-1Limit risk of unauthorised access to the CDR data environment
SEC02-BP06Employ user groups and attributes
→AUCDR-IS-1Limit risk of unauthorised access to the CDR data environment
SEC03-BP02Grant least privilege access
→AUCDR-IS-1Limit risk of unauthorised access to the CDR data environment

Detection(2 mappings)

SEC04-BP01Configure service and application logging
→AUCDR-IS-1Limit risk of unauthorised access to the CDR data environment
SEC04-BP03Correlate and enrich security alerts
→AUCDR-IS-STEP5Step 5 - Manage and report security incidents

Infrastructure Protection(6 mappings)

SEC05-BP02Control traffic flow within your network layers
→AUCDR-IS-2Secure the network and systems within the data environment
SEC05-BP03Implement inspection-based protection
→AUCDR-IS-5Limit, prevent, detect and remove malware
SEC06-BP01Perform vulnerability management
→AUCDR-IS-4Formal vulnerability management program
SEC06-BP02Provision compute from hardened images2 targets
→AUCDR-IS-2Secure the network and systems within the data environment
→AUCDR-IS-5Limit, prevent, detect and remove malware
SEC06-BP05Automate compute protection
→AUCDR-IS-4Formal vulnerability management program

Data Protection(4 mappings)

SEC07-BP01Understand your data classification scheme
→AUCDR-IS-STEP2Step 2 - Define the boundaries of the CDR data environment
SEC07-BP04Define scalable data lifecycle management2 targets
→AUCDR-IS-3Securely manage information assets over their lifecycle
→AUCDR-PS-12Privacy Safeguard 12 - Security of CDR data and destruction or de-identification of redundant CDR data
SEC08-BP02Enforce encryption at rest
→AUCDR-IS-2Secure the network and systems within the data environment

+9 more mappings

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

Create Free Account →

Free forever, no credit card required

Coverage crosswalk

The AWS Well-Architected Security Pillar to Australia Consumer Data Right - Banking (CDR) crosswalk

The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which Australia Consumer Data Right - Banking (CDR) controls your existing AWS Well-Architected Security Pillar work already satisfies, which are real gaps, and the reasoning behind every claim so you can check it. One pair, $299, one time.

AWS Well-Architected Security Pillar into Australia Consumer Data Right - Banking (CDR)
37.5%

9 of 24 Australia Consumer Data Right - Banking (CDR) controls are evidenced by work you have already done for AWS Well-Architected Security Pillar. 15 are genuine gaps.

Australia Consumer Data Right - Banking (CDR) into AWS Well-Architected Security Pillar
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.

AWS Well-Architected Security Pillar to Australia Consumer Data Right - Banking (CDR)
$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 38% in the header counts how many AWS Well-Architected Security Pillar controls carry at least one candidate mapping in the graph, before any review. The crosswalk percentage counts something stricter: how many Australia Consumer Data Right - Banking (CDR) 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

Cross-framework mappings across 868 frameworks, at a fraction of consulting costs.

$0/forever

Free

  • ✓ 868 framework browser
  • ✓ Cross-framework mappings (315K+)
  • ✓ 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 AWS Well-Architected Security Pillar and Australia Consumer Data Right - Banking (CDR)?

AWS Well-Architected Security Pillar has 63 controls across its framework, while Australia Consumer Data Right - Banking (CDR) covers 24 controls. Direct mapping analysis identifies 24 overlapping controls (38% coverage). The frameworks diverge most significantly in Identity & Access Management, where 12 AWS Well-Architected Security Pillar controls have no direct Australia Consumer Data Right - Banking (CDR) equivalent.

How many controls map between AWS Well-Architected Security Pillar and Australia Consumer Data Right - Banking (CDR)?

Of 63 total AWS Well-Architected Security Pillar controls, 24 map directly to Australia Consumer Data Right - Banking (CDR) controls, representing 38% coverage. The remaining 39 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping AWS Well-Architected Security Pillar to Australia Consumer Data Right - Banking (CDR)?

39 AWS Well-Architected Security Pillar controls have no direct equivalent in Australia Consumer Data Right - Banking (CDR). The highest concentration of gaps is in Identity & Access Management 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 AWS Well-Architected Security Pillar and Australia Consumer Data Right - Banking (CDR)?

The domain with the highest gap count is Identity & Access Management (12 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.