Cross-Framework Mapping

NIST SP 800-39vsAML/CTF Act 2006 (Australia)

See exactly how NIST SP 800-39 controls map to AML/CTF Act 2006 (Australia). Pre-computed mappings, identified gaps, and coverage analysis.

3
Controls Mapped
5
Gaps Found
38%
Coverage

Need this as a report you can hand to an assessor? A coverage crosswalk for this pair can be built to order.

According to the TheArtOfService Compliance Knowledge Graph:

NIST SP 800-39 maps to AML/CTF Act 2006 (Australia) with 38% coverage across 3 directly mapped controls. Analysis of 8 NIST SP 800-39 controls identifies 5 compliance gaps, primarily concentrated in Supply Chain, Sharing, Strategy Maintenance.

Source: TheArtOfService Knowledge Graph | 8 controls analysed | 686 frameworks | 310K+ cross-framework mappings

Control Mappings

Showing 3 of 3 mapped controls across 3 domains. Sign up to explore all 310K+ mappings across 686 frameworks.

Assess Step (Risk Assessing)(1 mappings)

NISTSP39-3Risk Assessing: Organisation, Mission, and System Level Assessments
AMLCTF-PartA-RiskAssessML/TF Risk Assessment

Respond Step (Risk Responding)(1 mappings)

NISTSP39-4Risk Responding: Identify, Evaluate, Decide, Implement
AMLCTF-82Part A Compliance

Monitor Step (Risk Monitoring)(1 mappings)

NISTSP39-5Risk Monitoring: Effectiveness, Changes, Compliance, and Reassessment Triggers
AMLCTF-82Part A Compliance
Coverage crosswalk

A NIST SP 800-39 to AML/CTF Act 2006 (Australia) crosswalk, built to order

The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which AML/CTF Act 2006 (Australia) controls your existing NIST SP 800-39 work already satisfies, which are real gaps, and the reasoning behind every claim so you can check it. One pair, $299, one time.

NIST SP 800-39 into AML/CTF Act 2006 (Australia)
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.

AML/CTF Act 2006 (Australia) into NIST SP 800-39
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.

NIST SP 800-39 to AML/CTF Act 2006 (Australia) (built to order)
$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 38% in the header counts how many NIST SP 800-39 controls carry at least one candidate mapping in the graph, before any review. The crosswalk percentage counts something stricter: how many AML/CTF Act 2006 (Australia) 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

AI-powered compliance intelligence across 686 frameworks, at a fraction of consulting costs.

$0/forever

Free

  • 686 framework browser
  • Cross-framework mappings (310K+)
  • 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 NIST SP 800-39 and AML/CTF Act 2006 (Australia)?

NIST SP 800-39 has 8 controls across its framework, while AML/CTF Act 2006 (Australia) covers 39 controls. Direct mapping analysis identifies 3 overlapping controls (38% coverage). The frameworks diverge most significantly in Supply Chain, Sharing, Strategy Maintenance, where 1 NIST SP 800-39 controls have no direct AML/CTF Act 2006 (Australia) equivalent.

How many controls map between NIST SP 800-39 and AML/CTF Act 2006 (Australia)?

Of 8 total NIST SP 800-39 controls, 3 map directly to AML/CTF Act 2006 (Australia) controls, representing 38% coverage. The remaining 5 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping NIST SP 800-39 to AML/CTF Act 2006 (Australia)?

5 NIST SP 800-39 controls have no direct equivalent in AML/CTF Act 2006 (Australia). The highest concentration of gaps is in Supply Chain, Sharing, Strategy Maintenance with 1 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 NIST SP 800-39 and AML/CTF Act 2006 (Australia)?

The domain with the highest gap count is Supply Chain, Sharing, Strategy Maintenance (1 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.