Cross-Framework Mapping

ISO 22320:2018vsIAEA Nuclear Security Series - Computer Security at Nuclear Facilities (NSS-17-T Rev 1)

See exactly how ISO 22320:2018 controls map to IAEA Nuclear Security Series - Computer Security at Nuclear Facilities (NSS-17-T Rev 1). Pre-computed mappings, identified gaps, and coverage analysis.

12
Controls Mapped
25
Gaps Found
16%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

ISO 22320:2018 maps to IAEA Nuclear Security Series - Computer Security at Nuclear Facilities (NSS-17-T Rev 1) with 16% coverage across 6 directly mapped controls. Analysis of 37 ISO 22320:2018 controls identifies 31 compliance gaps — primarily concentrated in Clause 4: Principles of Incident Management.

Source: TheArtOfService Knowledge Graph | 37 controls analysed | 718 frameworks | 332K+ cross-framework mappings

Control Mappings

Showing 12 of 12 mapped controls across 2 domains. Sign up to explore all 332K+ mappings across 718 frameworks.

Clause 5: Basic Components - Process and Structure(10 mappings)

ISO-22320-5.1General process requirements3 targets
IAEA-NSS17-AccessControl-OT-IT-Authentication-AuthorizationIAEA NSS-17 - Access Control + Authentication + Authorization + IAM + Privileged Access for OT and IT
IAEA-NSS17-Architecture-Zones-DefenceInDepth-SegmentationIAEA NSS-17 - Computer Security Architecture + Zone Model + Defence in Depth + Network Segmentation + Boundary
IAEA-NSS17-SupplyChain-ThirdParty-OEM-TrustIAEA NSS-17 - Supply Chain + Third Party + OEM + Vendor Security + Trustworthy Components
ISO-22320-5.2Incident management process
IAEA-NSS17-Detect-Monitor-Logging-IR-Recovery-ExercisesIAEA NSS-17 - Detection + Monitoring + Logging + Incident Response + Recovery + Computer Security Exercises
ISO-22320-5.3Incident management structure (command)3 targets
IAEA-NSS17-AccessControl-OT-IT-Authentication-AuthorizationIAEA NSS-17 - Access Control + Authentication + Authorization + IAM + Privileged Access for OT and IT
IAEA-NSS17-Architecture-Zones-DefenceInDepth-SegmentationIAEA NSS-17 - Computer Security Architecture + Zone Model + Defence in Depth + Network Segmentation + Boundary
IAEA-NSS17-SupplyChain-ThirdParty-OEM-TrustIAEA NSS-17 - Supply Chain + Third Party + OEM + Vendor Security + Trustworthy Components
ISO-22320-5.4Roles and responsibilities3 targets
IAEA-NSS17-AccessControl-OT-IT-Authentication-AuthorizationIAEA NSS-17 - Access Control + Authentication + Authorization + IAM + Privileged Access for OT and IT
IAEA-NSS17-Architecture-Zones-DefenceInDepth-SegmentationIAEA NSS-17 - Computer Security Architecture + Zone Model + Defence in Depth + Network Segmentation + Boundary
IAEA-NSS17-SupplyChain-ThirdParty-OEM-TrustIAEA NSS-17 - Supply Chain + Third Party + OEM + Vendor Security + Trustworthy Components

Annexes: Guidance on Incident Management Planning(2 mappings)

ISO-22320-BAnnex B: Incident management plan structure
IAEA-NSS17-Detect-Monitor-Logging-IR-Recovery-ExercisesIAEA NSS-17 - Detection + Monitoring + Logging + Incident Response + Recovery + Computer Security Exercises
ISO-22320-CAnnex C: Incident management task examples
IAEA-NSS17-Detect-Monitor-Logging-IR-Recovery-ExercisesIAEA NSS-17 - Detection + Monitoring + Logging + Incident Response + Recovery + Computer Security Exercises

Related Comparisons

Other ISO 22320:2018 comparisons

Other IAEA Nuclear Security Series - Computer Security at Nuclear Facilities (NSS-17-T Rev 1) comparisons

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • 718 framework browser
  • Cross-framework mappings (332K+)
  • 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 22320:2018 and IAEA Nuclear Security Series - Computer Security at Nuclear Facilities (NSS-17-T Rev 1)?

ISO 22320:2018 has 37 controls across its framework, while IAEA Nuclear Security Series - Computer Security at Nuclear Facilities (NSS-17-T Rev 1) covers 11 controls. Direct mapping analysis identifies 6 overlapping controls (16% coverage). The frameworks diverge most significantly in Clause 4: Principles of Incident Management, where 8 ISO 22320:2018 controls have no direct IAEA Nuclear Security Series - Computer Security at Nuclear Facilities (NSS-17-T Rev 1) equivalent.

How many controls map between ISO 22320:2018 and IAEA Nuclear Security Series - Computer Security at Nuclear Facilities (NSS-17-T Rev 1)?

Of 37 total ISO 22320:2018 controls, 6 map directly to IAEA Nuclear Security Series - Computer Security at Nuclear Facilities (NSS-17-T Rev 1) controls — representing 16% coverage. The remaining 31 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping ISO 22320:2018 to IAEA Nuclear Security Series - Computer Security at Nuclear Facilities (NSS-17-T Rev 1)?

31 ISO 22320:2018 controls have no direct equivalent in IAEA Nuclear Security Series - Computer Security at Nuclear Facilities (NSS-17-T Rev 1). The highest concentration of gaps is in Clause 4: Principles of Incident Management with 8 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 22320:2018 and IAEA Nuclear Security Series - Computer Security at Nuclear Facilities (NSS-17-T Rev 1)?

The domain with the highest gap count is Clause 4: Principles of Incident Management (8 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.