Cross-Framework Mapping

Australia My Health Records Act 2012vsNIST Cybersecurity Framework 2.0

See exactly how Australia My Health Records Act 2012 controls map to NIST Cybersecurity Framework 2.0. Pre-computed mappings, identified gaps, and coverage analysis.

46
Controls Mapped
0
Gaps Found
50%
Coverage

A reviewed coverage crosswalk for this pair is available. See which NIST Cybersecurity Framework 2.0 controls you already evidence.

According to the TheArtOfService Compliance Knowledge Graph:

Australia My Health Records Act 2012 maps to NIST Cybersecurity Framework 2.0 with 50% coverage across 20 directly mapped controls. Analysis of 40 Australia My Health Records Act 2012 controls identifies 20 compliance gaps, primarily concentrated in Registration and Participation.

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

Control Mappings

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

Collection, Use and Disclosure(3 mappings)

MYHR-CUD-4Records not held or taken outside Australia2 targets
→NIST-CSF-PR.DS-01The confidentiality, integrity, and availability of data-at-rest are protected
→NIST-CSF-PR.DS-02The confidentiality, integrity, and availability of data-in-transit are protected
MYHR-CUD-5Interaction with the Privacy Act 1988
→NIST-CSF-GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed

Breach and Enforcement(8 mappings)

MYHR-ENF-1Mandatory data breach notification6 targets
→NIST-CSF-DE.AE-06Information on adverse events is provided to authorized staff and tools
→NIST-CSF-DE.AE-08Incidents are declared when adverse events meet the defined incident criteria
→NIST-CSF-ID.IM-04Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
→NIST-CSF-RS.CO-02Internal and external stakeholders are notified of incidents
→NIST-CSF-RS.CO-03Information is shared with designated internal and external stakeholders
→NIST-CSF-RS.MA-04Incidents are escalated or elevated as needed
MYHR-ENF-2Civil penalty compliance
→NIST-CSF-GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed
MYHR-ENF-3Criminal offences and sanctions
→NIST-CSF-GV.RR-04Cybersecurity is included in human resources practices

Governance(2 mappings)

MYHR-GOV-1System Operator functions and oversight
→NIST-CSF-GV.OC-02Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and considered
MYHR-GOV-6The Register of participants
→NIST-CSF-GV.SC-04Suppliers are known and prioritized by criticality

Registration and Participation(7 mappings)

MYHR-REG-1Registration as a participant
→NIST-CSF-GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced
MYHR-REG-11Ensuring required information is given to the System Operator2 targets
→NIST-CSF-PR.AA-01Identities and credentials for authorized users, services, and hardware are managed by the organization
→NIST-CSF-PR.AA-02Identities are proofed and bound to credentials based on the context of interactions
MYHR-REG-2Healthcare recipient registration and identity verification2 targets
→NIST-CSF-PR.AA-02Identities are proofed and bound to credentials based on the context of interactions
→NIST-CSF-PR.AA-03Users, services, and hardware are authenticated
MYHR-REG-3Conditions of registration and participation
→NIST-CSF-GV.PO-02Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission
MYHR-REG-4Contracted service provider oversight
→NIST-CSF-DE.CM-06External service provider activities and services are monitored to find potentially adverse events

+26 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 Australia My Health Records Act 2012 to NIST Cybersecurity Framework 2.0 crosswalk

The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which NIST Cybersecurity Framework 2.0 controls your existing Australia My Health Records Act 2012 work already satisfies, which are real gaps, and the reasoning behind every claim so you can check it. One pair, $299, one time.

Australia My Health Records Act 2012 into NIST Cybersecurity Framework 2.0
17%

18 of 106 NIST Cybersecurity Framework 2.0 controls are evidenced by work you have already done for Australia My Health Records Act 2012. 88 are genuine gaps.

NIST Cybersecurity Framework 2.0 into Australia My Health Records Act 2012
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.

Australia My Health Records Act 2012 to NIST Cybersecurity Framework 2.0
$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 50% in the header counts how many Australia My Health Records Act 2012 controls carry at least one candidate mapping in the graph, before any review. The crosswalk percentage counts something stricter: how many NIST Cybersecurity Framework 2.0 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 Australia My Health Records Act 2012 and NIST Cybersecurity Framework 2.0?

Australia My Health Records Act 2012 has 40 controls across its framework, while NIST Cybersecurity Framework 2.0 covers 106 controls. Direct mapping analysis identifies 20 overlapping controls (50% coverage). The frameworks diverge most significantly in Registration and Participation, where 6 Australia My Health Records Act 2012 controls have no direct NIST Cybersecurity Framework 2.0 equivalent.

How many controls map between Australia My Health Records Act 2012 and NIST Cybersecurity Framework 2.0?

Of 40 total Australia My Health Records Act 2012 controls, 20 map directly to NIST Cybersecurity Framework 2.0 controls, representing 50% 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 NIST Cybersecurity Framework 2.0?

20 Australia My Health Records Act 2012 controls have no direct equivalent in NIST Cybersecurity Framework 2.0. The highest concentration of gaps is in Registration and Participation with 6 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 NIST Cybersecurity Framework 2.0?

The domain with the highest gap count is Registration and Participation (6 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.