Cross-Framework Mapping

NIST SP 800-39vsISO 27005

See exactly how NIST SP 800-39 controls map to ISO 27005. Pre-computed mappings, identified gaps, and coverage analysis.

19
Controls Mapped
1
Gaps Found
35%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

NIST SP 800-39 maps to ISO 27005 with 35% coverage across 7 directly mapped controls. Analysis of 20 NIST SP 800-39 controls identifies 13 compliance gaps — primarily concentrated in NIST SP 800-39: Risk Framework & Governance.

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

Control Mappings

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

NIST SP 800-39: Risk Assessment(9 mappings)

NIST39-06Risk identification methods3 targets
ISO27005-06Risk identification methods
ISO27005-08Risk criteria and thresholds
ISO27005-10Risk interdependency analysis
NIST39-09Risk scenario development3 targets
ISO27005-06Risk identification methods
ISO27005-08Risk criteria and thresholds
ISO27005-10Risk interdependency analysis
NIST39-10Risk interdependency analysis3 targets
ISO27005-06Risk identification methods
ISO27005-08Risk criteria and thresholds
ISO27005-10Risk interdependency analysis

NIST SP 800-39: Risk Treatment(6 mappings)

NIST39-11Risk treatment options and selection3 targets
ISO27005-01Risk management policy and scope
ISO27005-05Risk management integration
ISO27005-18Risk register maintenance
NIST39-14Risk transfer and insurance3 targets
ISO27005-01Risk management policy and scope
ISO27005-05Risk management integration
ISO27005-18Risk register maintenance

NIST SP 800-39: Risk Monitoring & Review(4 mappings)

NIST39-18Risk register maintenance3 targets
ISO27005-01Risk management policy and scope
ISO27005-05Risk management integration
ISO27005-18Risk register maintenance
NIST39-19Continuous improvement of risk processes
ISO27005-19Continuous improvement of risk processes

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 NIST SP 800-39 and ISO 27005?

NIST SP 800-39 has 20 controls across its framework, while ISO 27005 covers 20 controls. Direct mapping analysis identifies 7 overlapping controls (35% coverage). The frameworks diverge most significantly in NIST SP 800-39: Risk Framework & Governance, where 5 NIST SP 800-39 controls have no direct ISO 27005 equivalent.

How many controls map between NIST SP 800-39 and ISO 27005?

Of 20 total NIST SP 800-39 controls, 7 map directly to ISO 27005 controls — representing 35% coverage. The remaining 13 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 ISO 27005?

13 NIST SP 800-39 controls have no direct equivalent in ISO 27005. The highest concentration of gaps is in NIST SP 800-39: Risk Framework & Governance with 5 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 ISO 27005?

The domain with the highest gap count is NIST SP 800-39: Risk Framework & Governance (5 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.