Cross-Framework Mapping

AML/CTF Act 2006 (Australia)vsIACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems

See exactly how AML/CTF Act 2006 (Australia) controls map to IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems. Pre-computed mappings, identified gaps, and coverage analysis.

2
Controls Mapped
39
Gaps Found
5%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

AML/CTF Act 2006 (Australia) maps to IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems with 5% coverage across 2 directly mapped controls. Analysis of 41 AML/CTF Act 2006 (Australia) controls identifies 39 compliance gaps — primarily concentrated in Reporting Obligations.

Source: TheArtOfService Knowledge Graph | 41 controls analysed | 693 frameworks | 819K+ cross-framework mappings

Control Mappings

Showing 2 of 2 mapped controls across 2 domains. Sign up to explore all 819K+ mappings across 693 frameworks.

Customer Identification (KYC)(1 mappings)

AMLCTF-35Identity Verification Standard
E27-R3User authentication

AML/CTF Program Requirements(1 mappings)

AMLCTF-PartA-RiskAssessML/TF Risk Assessment
E26-R3Risk assessment

Related Comparisons

Other AML/CTF Act 2006 (Australia) comparisons

Other IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems comparisons

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 693 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 693 framework browser
  • Cross-framework mappings (819K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$49/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 AML/CTF Act 2006 (Australia) and IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems?

AML/CTF Act 2006 (Australia) has 41 controls across its framework, while IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems covers 22 controls. Direct mapping analysis identifies 2 overlapping controls (5% coverage). The frameworks diverge most significantly in Reporting Obligations, where 17 AML/CTF Act 2006 (Australia) controls have no direct IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems equivalent.

How many controls map between AML/CTF Act 2006 (Australia) and IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems?

Of 41 total AML/CTF Act 2006 (Australia) controls, 2 map directly to IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems controls — representing 5% 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 AML/CTF Act 2006 (Australia) to IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems?

39 AML/CTF Act 2006 (Australia) controls have no direct equivalent in IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems. The highest concentration of gaps is in Reporting Obligations with 17 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 AML/CTF Act 2006 (Australia) and IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems?

The domain with the highest gap count is Reporting Obligations (17 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.