Cross-Framework Mapping

Australia My Health Records Act 2012vsITU-T X.805 — Security Architecture for End-to-End Communications

See exactly how Australia My Health Records Act 2012 controls map to ITU-T X.805 — Security Architecture for End-to-End Communications. Pre-computed mappings, identified gaps, and coverage analysis.

2
Controls Mapped
20
Gaps Found
9%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

Australia My Health Records Act 2012 maps to ITU-T X.805 — Security Architecture for End-to-End Communications with 9% coverage across 2 directly mapped controls. Analysis of 22 Australia My Health Records Act 2012 controls identifies 20 compliance gaps — primarily concentrated in Part 1 — Preliminary.

Source: TheArtOfService Knowledge Graph | 22 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.

Part 3 — Registration and Access(1 mappings)

MHR-4Access Controls
X805-D1Access Control

Part 1 — Preliminary(1 mappings)

Sec. 2Interpretation
X805-D8Privacy

Related Comparisons

Other Australia My Health Records Act 2012 comparisons

Other ITU-T X.805 — Security Architecture for End-to-End Communications 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 Australia My Health Records Act 2012 and ITU-T X.805 — Security Architecture for End-to-End Communications?

Australia My Health Records Act 2012 has 22 controls across its framework, while ITU-T X.805 — Security Architecture for End-to-End Communications covers 14 controls. Direct mapping analysis identifies 2 overlapping controls (9% coverage). The frameworks diverge most significantly in Part 1 — Preliminary, where 9 Australia My Health Records Act 2012 controls have no direct ITU-T X.805 — Security Architecture for End-to-End Communications equivalent.

How many controls map between Australia My Health Records Act 2012 and ITU-T X.805 — Security Architecture for End-to-End Communications?

Of 22 total Australia My Health Records Act 2012 controls, 2 map directly to ITU-T X.805 — Security Architecture for End-to-End Communications controls — representing 9% coverage. The remaining 20 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping Australia My Health Records Act 2012 to ITU-T X.805 — Security Architecture for End-to-End Communications?

20 Australia My Health Records Act 2012 controls have no direct equivalent in ITU-T X.805 — Security Architecture for End-to-End Communications. The highest concentration of gaps is in Part 1 — Preliminary with 9 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 My Health Records Act 2012 and ITU-T X.805 — Security Architecture for End-to-End Communications?

The domain with the highest gap count is Part 1 — Preliminary (9 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.