ISO/IEC 27010:2015vsIAEA Nuclear Security Series - Computer Security at Nuclear Facilities (NSS-17-T Rev 1)
See exactly how ISO/IEC 27010:2015 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.
According to the TheArtOfService Compliance Knowledge Graph:
ISO/IEC 27010:2015 maps to IAEA Nuclear Security Series - Computer Security at Nuclear Facilities (NSS-17-T Rev 1) with 18% coverage across 10 directly mapped controls. Analysis of 28 ISO/IEC 27010:2015 controls identifies 36 compliance gaps — primarily concentrated in Clause 17-18 and Annexes: Continuity and Compliance.
Source: TheArtOfService Knowledge Graph | 28 controls analysed | 718 frameworks | 330K+ cross-framework mappings
Control Mappings
Showing 10 of 10 mapped controls across 7 domains. Sign up to explore all 330K+ mappings across 718 frameworks.
Physical(1 mappings)
Clause 11-13: Physical, Operations, and Communications Security(1 mappings)
Incidents(1 mappings)
Clause 14-16: System Development, Supplier Relations, and Incident Management(2 mappings)
Continuity(1 mappings)
Access Control(2 mappings)
Clause 9-10: Access Control and Cryptography(2 mappings)
Related Comparisons
Other ISO/IEC 27010:2015 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.
Free
- ✓ 718 framework browser
- ✓ Cross-framework mappings (330K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between ISO/IEC 27010:2015 and IAEA Nuclear Security Series - Computer Security at Nuclear Facilities (NSS-17-T Rev 1)?
ISO/IEC 27010:2015 has 28 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 10 overlapping controls (18% coverage). The frameworks diverge most significantly in Clause 17-18 and Annexes: Continuity and Compliance, where 6 ISO/IEC 27010:2015 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/IEC 27010:2015 and IAEA Nuclear Security Series - Computer Security at Nuclear Facilities (NSS-17-T Rev 1)?
Of 28 total ISO/IEC 27010:2015 controls, 10 map directly to IAEA Nuclear Security Series - Computer Security at Nuclear Facilities (NSS-17-T Rev 1) controls — representing 18% coverage. The remaining 36 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping ISO/IEC 27010:2015 to IAEA Nuclear Security Series - Computer Security at Nuclear Facilities (NSS-17-T Rev 1)?
36 ISO/IEC 27010:2015 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 17-18 and Annexes: Continuity and Compliance 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 ISO/IEC 27010:2015 and IAEA Nuclear Security Series - Computer Security at Nuclear Facilities (NSS-17-T Rev 1)?
The domain with the highest gap count is Clause 17-18 and Annexes: Continuity and Compliance (6 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
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.