Australia Consumer Data Right — Banking (CDR)vsUS Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements
See exactly how Australia Consumer Data Right — Banking (CDR) controls map to US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements. Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
Australia Consumer Data Right — Banking (CDR) maps to US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements with 14% coverage across 7 directly mapped controls. Analysis of 50 Australia Consumer Data Right — Banking (CDR) controls identifies 43 compliance gaps — primarily concentrated in Compliance and Enforcement.
Source: TheArtOfService Knowledge Graph | 50 controls analysed | 693 frameworks | 819K+ cross-framework mappings
Control Mappings
Showing 11 of 11 mapped controls across 2 domains. Sign up to explore all 819K+ mappings across 693 frameworks.
Privacy and Security Safeguards(2 mappings)
Compliance and Enforcement(9 mappings)
Related Comparisons
Other Australia Consumer Data Right — Banking (CDR) comparisons
Other US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 693 frameworks — at a fraction of consulting costs.
Free
- ✓ 693 framework browser
- ✓ Cross-framework mappings (819K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between Australia Consumer Data Right — Banking (CDR) and US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements?
Australia Consumer Data Right — Banking (CDR) has 50 controls across its framework, while US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements covers 21 controls. Direct mapping analysis identifies 7 overlapping controls (14% coverage). The frameworks diverge most significantly in Compliance and Enforcement, where 32 Australia Consumer Data Right — Banking (CDR) controls have no direct US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements equivalent.
How many controls map between Australia Consumer Data Right — Banking (CDR) and US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements?
Of 50 total Australia Consumer Data Right — Banking (CDR) controls, 7 map directly to US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements controls — representing 14% coverage. The remaining 43 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 US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements?
43 Australia Consumer Data Right — Banking (CDR) controls have no direct equivalent in US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements. The highest concentration of gaps is in Compliance and Enforcement with 32 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 US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements?
The domain with the highest gap count is Compliance and Enforcement (32 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
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.