Cross-Framework Mapping

Australia My Health Records Act 2012vsEU NIS2 Directive — Transport Sector Requirements

See exactly how Australia My Health Records Act 2012 controls map to EU NIS2 Directive — Transport Sector Requirements. Pre-computed mappings, identified gaps, and coverage analysis.

10
Controls Mapped
12
Gaps Found
18%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

Australia My Health Records Act 2012 maps to EU NIS2 Directive — Transport Sector Requirements with 18% coverage across 4 directly mapped controls. Analysis of 22 Australia My Health Records Act 2012 controls identifies 18 compliance gaps — primarily concentrated in Part 1 — Preliminary.

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

Control Mappings

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

Part 7 — Data Governance Board(2 mappings)

MHR-10Establishment and Functions (Division 1)2 targets
Art. 2Consent Definition
Art. 8Data Categories

Part 1 — Preliminary(8 mappings)

POFMA-1.1Definitions and Interpretation (Sections 2-3)2 targets
Art. 2Consent Definition
Art. 8Data Categories
Sec. 2Interpretation4 targets
Art. 2Consent Definition
Art. 34Notification of Personal Information Breach
Art. 8Data Categories
Sec. 40Right to Object
Sec. 3Scope and Application2 targets
Art. 2Consent Definition
Art. 8Data Categories

Related Comparisons

Other Australia My Health Records Act 2012 comparisons

Other EU NIS2 Directive — Transport Sector Requirements 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 EU NIS2 Directive — Transport Sector Requirements?

Australia My Health Records Act 2012 has 22 controls across its framework, while EU NIS2 Directive — Transport Sector Requirements covers 36 controls. Direct mapping analysis identifies 4 overlapping controls (18% coverage). The frameworks diverge most significantly in Part 1 — Preliminary, where 7 Australia My Health Records Act 2012 controls have no direct EU NIS2 Directive — Transport Sector Requirements equivalent.

How many controls map between Australia My Health Records Act 2012 and EU NIS2 Directive — Transport Sector Requirements?

Of 22 total Australia My Health Records Act 2012 controls, 4 map directly to EU NIS2 Directive — Transport Sector Requirements controls — representing 18% coverage. The remaining 18 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 EU NIS2 Directive — Transport Sector Requirements?

18 Australia My Health Records Act 2012 controls have no direct equivalent in EU NIS2 Directive — Transport Sector Requirements. The highest concentration of gaps is in Part 1 — Preliminary with 7 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 EU NIS2 Directive — Transport Sector Requirements?

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