Cross-Framework Mapping

ISO 27799vsNIST SP 800-146

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

11
Controls Mapped
35
Gaps Found
17%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

ISO 27799 maps to NIST SP 800-146 with 17% coverage across 8 directly mapped controls. Analysis of 46 ISO 27799 controls identifies 38 compliance gaps — primarily concentrated in ISO 27799: Administrative Safeguards.

Source: TheArtOfService Knowledge Graph | 46 controls analysed | 700 frameworks | 323K+ cross-framework mappings

Control Mappings

Showing 11 of 11 mapped controls across 3 domains. Sign up to explore all 323K+ mappings across 700 frameworks.

ISO 27799: Patient Data Protection(8 mappings)

ISO27799-01ePHI access controls and authorization
NISTSP146-6Cloud Security and Privacy Recommendations
ISO27799-02ePHI encryption at rest and in transit
NISTSP146-6Cloud Security and Privacy Recommendations
ISO27799-03Minimum necessary standard enforcement2 targets
NISTSP146-6Cloud Security and Privacy Recommendations
NISTSP146-7Service Level, Performance, Reliability, Interoperability, and Portability
ISO27799-04Patient data de-identification procedures2 targets
NISTSP146-6Cloud Security and Privacy Recommendations
NISTSP146-7Service Level, Performance, Reliability, Interoperability, and Portability
ISO27799-05Audit trail for ePHI access2 targets
NISTSP146-6Cloud Security and Privacy Recommendations
NISTSP146-7Service Level, Performance, Reliability, Interoperability, and Portability

ISO 27799: Administrative Safeguards(1 mappings)

ISO27799-06Security management process and risk analysis
NISTSP146-1Cloud Adoption Strategy, Workload Suitability, and Decision Framework

ISO 27799: Technical Safeguards(2 mappings)

ISO27799-12Unique user identification and authentication
NISTSP146-6Cloud Security and Privacy Recommendations
ISO27799-16Transmission security and encryption
NISTSP146-6Cloud Security and Privacy Recommendations

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 700 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 700 framework browser
  • Cross-framework mappings (323K+)
  • 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 ISO 27799 and NIST SP 800-146?

ISO 27799 has 46 controls across its framework, while NIST SP 800-146 covers 8 controls. Direct mapping analysis identifies 8 overlapping controls (17% coverage). The frameworks diverge most significantly in ISO 27799: Administrative Safeguards, where 5 ISO 27799 controls have no direct NIST SP 800-146 equivalent.

How many controls map between ISO 27799 and NIST SP 800-146?

Of 46 total ISO 27799 controls, 8 map directly to NIST SP 800-146 controls — representing 17% coverage. The remaining 38 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping ISO 27799 to NIST SP 800-146?

38 ISO 27799 controls have no direct equivalent in NIST SP 800-146. The highest concentration of gaps is in ISO 27799: Administrative Safeguards 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 ISO 27799 and NIST SP 800-146?

The domain with the highest gap count is ISO 27799: Administrative Safeguards (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.