GoToCertifyCompliance Self-Assessment

Mapping table · free · CSV download

NIS2 to ISO/IEC 27001:2022 mapping

This table links 69 NIS2 requirements, each with its legal reference, to the clauses and controls of ISO/IEC 27001:2022: 107 distinct clauses and controls are involved. Use it to see what an existing management system already covers and what NIS2 adds on top.

Requirements checked against the official texts on 13/11/2026 · version 1.0 · reviewed by GoToCertify's Subject Matter Expert

NIS2 requirements and the related ISO/IEC 27001:2022 clauses and controls

IdLegal referenceRequirementISO/IEC 27001:2022
SCO – Scope, registration and legal framework
SCO-01Art. 2; Art. 3; Annex I; Annex II
Recommendation 2003/361/EC (SME definition); national transposition law
The organisation has determined whether it is an essential or important entity (Annex I / Annex II sector, medium or large size under Recommendation 2003/361/EC, or inclusion by designation or special rules of Art. 2(2)-(4)) and documented the conclusion.Clause 4 Context of the organization
A.5.31 Legal, statutory, regulatory and contractual requirements
SCO-02Art. 26(1)-(3)
Commission NIS2 FAQ (jurisdiction and main establishment); ENISA registry of entities (Art. 27)
Jurisdiction and main establishment are determined for entities operating in several Member States (place where cybersecurity decisions are predominantly taken; EU representative for non-EU entities).Clause 4 Context of the organization
A.5.31 Legal, statutory, regulatory and contractual requirements
SCO-03Art. 3(4); Art. 27
National registration portals and deadlines; ENISA registry of entities under Art. 27(2)
The entity has registered with the competent national authority within the national deadline and keeps its identification data (name, address, sector, contact details, IP ranges, Member States of service) up to date.A.5.5 Contact with authorities
A.5.31 Legal, statutory, regulatory and contractual requirements
SCO-04Art. 4; Art. 2(12); Art. 21(1)
Reg. (EU) 2022/2554 (DORA); Directive (EU) 2022/2557 (CER); Reg. (EU) 2024/2847 (CRA)
A register of legal, regulatory and contractual cybersecurity requirements is maintained, including the applicable national transposition law, sector-specific lex specialis (Art. 4) and related EU acts (GDPR, DORA, CER, CRA, eIDAS).A.5.31 Legal, statutory, regulatory and contractual requirements
A.5.32 Intellectual property rights
A.5.34 Privacy and protection of personal identifiable information (PII)
Clause 4 Context of the organization
SCO-05Art. 28
GDPR (lawful basis for publication and disclosure)
TLD name registries and entities providing domain name registration services maintain an accurate and complete database of domain name registration data, publish non-personal registration data and respond to lawful access requests within 72 hours.A.5.33 Protection of records
A.5.34 Privacy and protection of personal identifiable information (PII)
A.5.31 Legal, statutory, regulatory and contractual requirements
GOV – Governance and management-body accountability
GOV-01Art. 20(1); Art. 21(1)
Implementing Reg. (EU) 2024/2690 Annex, point 1.1 (policy approved by management bodies)
The management body has formally approved the cybersecurity risk-management measures taken to comply with Art. 21 and oversees their implementation.Clause 5 Leadership
Clause 5.2 (Leadership)
Clause 9.3 (Performance evaluation)
A.5.1 Policies for information security
A.5.4 Management responsibilities
A.5.36 Compliance with policies, rules and standards for information security
GOV-02Art. 20(1); Art. 32(6)
Implementing Reg. (EU) 2024/2690 Annex, point 1.2 (roles and responsibilities)
Cybersecurity roles, responsibilities and accountability are defined and assigned, including a senior accountable manager (CISO or equivalent), with segregation of duties between operation, control and audit, and the management body's liability for infringements is documented and understood.Clause 5 Leadership
Clause 5.3 (Leadership)
A.5.2 Information security roles and responsibilities
A.5.3 Segregation of duties
A.5.4 Management responsibilities
GOV-03Art. 20(2)
ENISA Technical Implementation Guidance v1.0 (training and awareness); national requirements (some Member States prescribe frequency)
Members of the management body follow regular cybersecurity training enabling them to identify risks and assess risk-management practices and their impact on services; offering similar training to employees on a regular basis is encouraged (Art. 20(2)).A.6.3 Information security awareness, education and training
Clause 7 Support
GOV-04Art. 20(1); Art. 21(1)
ISO/IEC 27001 Cl. 4.3, 6.2, 7.1-7.2
Cybersecurity objectives, budget, resources and competent personnel are allocated; the scope of the management system covers all services and systems within NIS2 scope.Clause 6 Planning
Clause 7 Support
A.5.2 Information security roles and responsibilities
GOV-05Art. 23(1); Art. 29
Implementing Reg. (EU) 2024/2690 Annex, point 3.1 (incident handling policy: communication with authorities)
Contacts with the competent authority, the national CSIRT, sector regulators and relevant special interest groups (ISACs, CERT communities) are established and maintained.A.5.5 Contact with authorities
A.5.6 Contact with special interest groups
GOV-06Art. 21(1); Art. 32(2)(e)-(g); Art. 33(2)(d)-(f) (information and evidence requested by authorities)
ISO/IEC 27001 Cl. 7.5
Policies, procedures, records and operating procedures are documented, version-controlled, approved and retained as evidence of compliance.A.5.37 Documented operating procedures
A.5.33 Protection of records
A.5.36 Compliance with policies, rules and standards for information security
Clause 7 Support
RSK – Risk analysis and security policies
RSK-01Art. 21(1)-(2)(a)
Implementing Reg. (EU) 2024/2690 Annex, point 2.1; ENISA Technical Implementation Guidance (June 2025)
An all-hazards cybersecurity risk management framework (methodology, criteria, risk appetite, roles) is established and documented, covering network and information systems, their physical environment and dependencies on suppliers.Clause 6.1 (Planning)
Clause 6.2 (Planning)
A.5.7 Threat intelligence
A.5.19 Information security in supplier relationships
A.5.20 Addressing information security within supplier agreements
A.5.21 Managing information security in the information and communication technology (ICT) supply chain
RSK-02Art. 21(1)-(2)(a); Art. 21(4)
Implementing Reg. (EU) 2024/2690 Annex, point 2.1 (risk management framework)
Risk assessments are carried out and documented, risk treatment plans are implemented and monitored, residual risks are formally accepted, and the assessment is reviewed at planned intervals (at least yearly) and after significant incidents or major changes.Clause 6.1 (Planning)
Clause 6.2 (Planning)
A.5.7 Threat intelligence
A.5.19 Information security in supplier relationships
A.5.20 Addressing information security within supplier agreements
A.5.21 Managing information security in the information and communication technology (ICT) supply chain
RSK-03Art. 21(2)(a); Art. 20(1)
Implementing Reg. (EU) 2024/2690 Annex, point 1.1-1.2
A policy on the security of network and information systems is approved by the management body, communicated to staff and suppliers, sets objectives and the risk approach, assigns responsibilities and is reviewed at least yearly.Clause 5.2 (Leadership)
Clause 9.3 (Performance evaluation)
A.5.1 Policies for information security
A.5.2 Information security roles and responsibilities
A.5.4 Management responsibilities
A.5.36 Compliance with policies, rules and standards for information security
RSK-04Art. 21(2)(a) and (f)
Implementing Reg. (EU) 2024/2690 Annex, point 2.2 (compliance monitoring) and 2.3 (independent review)
Compliance with the security policies is monitored and independently reviewed at planned intervals, with results reported to the management body.Clause 9 Performance evaluation
Clause 9.2 (Performance evaluation)
A.5.31 Legal, statutory, regulatory and contractual requirements
A.5.35 Independent review of information security
A.5.36 Compliance with policies, rules and standards for information security
RSK-05Art. 21(2)(a) and (e); Art. 29 (information sharing)
ENISA threat landscape; national CSIRT advisories
Threat intelligence is collected and analysed, and security requirements are integrated into project management for new systems, services and major changes.A.5.7 Threat intelligence
A.5.8 Information security in project management
INC – Incident handling
INC-01Art. 21(2)(b); Art. 23
Implementing Reg. (EU) 2024/2690 Annex, point 3.1; ISO/IEC 27035
An incident handling policy and process define roles, categories, severity levels, escalation paths, communication (including with the CSIRT/competent authority) and the interface with business continuity and reporting.A.5.24 Information security incident management planning and preparation
A.5.2 Information security roles and responsibilities
INC-02Art. 21(2)(b)
Implementing Reg. (EU) 2024/2690 Annex, point 3.2 (monitoring and logging)
Logging and monitoring are implemented for relevant systems (network, authentication, privileged activity, security tools), logs are protected and retained, systems are time-synchronised, and events are reviewed to detect incidents.A.5.28 Collection of evidence
A.8.15 Logging
A.8.16 Monitoring activities
A.8.17 Clock synchronization
INC-03Art. 21(2)(b); Art. 23(3)
Implementing Reg. (EU) 2024/2690 Annex, point 3.3 (event reporting) and 3.4 (event assessment and classification)
Staff, suppliers and users can report events through a simple mechanism; events are assessed, classified and recorded, and a decision whether they constitute an incident (and a significant incident) is documented.A.5.25 Assessment and decision on information security events
A.6.8 Information security event reporting
INC-04Art. 21(2)(b)
Implementing Reg. (EU) 2024/2690 Annex, point 3.5 (incident response)
Incidents are contained, eradicated and recovered according to documented procedures; evidence is collected and preserved in a forensically sound manner; internal and external communications follow a plan.A.5.26 Response to information security incidents
A.5.28 Collection of evidence
INC-05Art. 21(2)(b); Art. 21(4)
Implementing Reg. (EU) 2024/2690 Annex, point 3.6 (post-incident reviews)
Post-incident reviews are performed after significant incidents, root causes identified, lessons learned captured and improvements to controls, procedures and training implemented.Clause 10 Improvement
A.5.27 Learning from information security incidents
BCM – Business continuity, backup and crisis management
BCM-01Art. 21(2)(c)
Implementing Reg. (EU) 2024/2690 Annex, point 4.1 (business continuity and disaster recovery plan); ISO 22301
Business continuity and disaster recovery plans are established for critical services and systems, based on a business impact analysis with defined RTO/RPO, roles and recovery procedures.Clause 8 Operation
A.5.29 Information security during disruption
A.5.30 ICT readiness for business continuity
BCM-02Art. 21(2)(c)
Implementing Reg. (EU) 2024/2690 Annex, point 4.2 (backup and redundancy management)
Backups are performed, protected (including offline or immutable copies), tested for restorability, and redundancy and capacity of information processing facilities are planned to meet availability requirements.A.8.6 Capacity management
A.8.13 Information backup
A.8.14 Redundancy of information processing facilities
BCM-03Art. 21(2)(c); Art. 23(1)
Implementing Reg. (EU) 2024/2690 Annex, point 4.3 (crisis management)
A crisis management process defines roles, decision rights, activation criteria, internal and external communication (authorities, customers, media) and the link with incident response and business continuity.A.5.5 Contact with authorities
A.5.26 Response to information security incidents
A.5.29 Information security during disruption
A.5.30 ICT readiness for business continuity
BCM-04Art. 21(2)(c) and (f)
Implementing Reg. (EU) 2024/2690 Annex, point 4.1 (testing of business continuity and disaster recovery plans)
Continuity, recovery and crisis plans are tested and exercised at planned intervals (at least yearly), results are evaluated and plans updated.Clause 9 Performance evaluation
A.5.29 Information security during disruption
A.5.30 ICT readiness for business continuity
SCM – Supply chain security
SCM-01Art. 21(2)(d); Art. 21(3); Art. 22
Implementing Reg. (EU) 2024/2690 Annex, point 5.1; EU 5G Toolbox; EU coordinated risk assessments (Art. 22)
A supply chain security policy is in place; direct suppliers and service providers are inventoried, classified by criticality and assessed for cybersecurity risk (including their vulnerabilities, secure development practices and the results of EU coordinated risk assessments).A.5.19 Information security in supplier relationships
A.5.20 Addressing information security within supplier agreements
A.5.21 Managing information security in the information and communication technology (ICT) supply chain
A.8.30 Outsourced development
SCM-02Art. 21(2)(d); Art. 21(3)
Implementing Reg. (EU) 2024/2690 Annex, point 5.1 (supply chain security policy: selection criteria and contractual requirements)
Supplier agreements include cybersecurity requirements proportionate to criticality: security measures, incident notification without undue delay, vulnerability handling, audit and information rights, subcontracting rules, data location, exit and termination assistance.A.5.19 Information security in supplier relationships
A.5.20 Addressing information security within supplier agreements
A.5.21 Managing information security in the information and communication technology (ICT) supply chain
A.8.30 Outsourced development
SCM-03Art. 21(2)(d)
Implementing Reg. (EU) 2024/2690 Annex, point 5.1 (monitoring and review of supplier practices) and 5.2 (directory of suppliers and service providers)
Supplier services and their security performance are monitored and reviewed; changes in supplier services, ownership or risk profile trigger re-assessment.A.5.19 Information security in supplier relationships
A.5.20 Addressing information security within supplier agreements
A.5.21 Managing information security in the information and communication technology (ICT) supply chain
A.5.22 Monitoring, review and change management of supplier services
A.8.30 Outsourced development
SCM-04Art. 21(2)(d) and (e)
Implementing Reg. (EU) 2024/2690 Annex, point 5 and 6.2; ENISA cloud security guidance
Use of cloud services and outsourced development is governed: shared responsibility is defined, security requirements and exit strategies are documented, and outsourced code is reviewed and tested before acceptance.A.5.23 Information security for use of cloud services
A.8.30 Outsourced development
SDV – Secure acquisition, development and vulnerability handling
SDV-01Art. 21(2)(e)
Implementing Reg. (EU) 2024/2690 Annex, point 6.1 (security in acquisition) and 6.2 (secure development life cycle)
A secure development life cycle is applied to systems developed in-house or acquired: security requirements, secure architecture and engineering principles, secure coding standards and protection of source code.A.5.21 Managing information security in the information and communication technology (ICT) supply chain
A.5.23 Information security for use of cloud services
A.8.25 Secure development life cycle
A.8.26 Application security requirements
A.8.27 Secure system architecture and engineering principles
A.8.28 Secure coding
SDV-02Art. 21(2)(e)
Implementing Reg. (EU) 2024/2690 Annex, point 6.2 (secure development life cycle) and 6.5 (security testing)
Security testing is performed in development and acceptance, development, test and production environments are separated, and test data is protected.A.8.25 Secure development life cycle
A.8.29 Security testing in development and acceptance
A.8.31 Separation of development, test and production environments
A.8.33 Test information
SDV-03Art. 21(2)(e)
Implementing Reg. (EU) 2024/2690 Annex, point 6.3 (configuration management) and 6.4 (change management, repairs and maintenance)
Configuration management and change management are implemented: secure baseline configurations are defined, documented and monitored, and changes to systems are assessed, approved, tested and recorded, with emergency change procedures.A.8.9 Configuration management
A.8.19 Installation of software on operational systems
A.8.32 Change management
SDV-04Art. 21(2)(e)
Implementing Reg. (EU) 2024/2690 Annex, point 6.6 (security patch management) and 6.10 (vulnerability handling)
Technical vulnerabilities are identified, assessed and remediated within defined timeframes according to risk; patch management covers all in-scope assets including network devices, OT and third-party components.A.8.8 Management of technical vulnerabilities
A.8.31 Separation of development, test and production environments
A.8.32 Change management
SDV-05Art. 21(2)(e); Art. 12
Implementing Reg. (EU) 2024/2690 Annex, point 6.10; ISO/IEC 29147 and 30111; Reg. (EU) 2024/2847 (CRA) Art. 13-14 for manufacturers
A procedure for handling and disclosing vulnerabilities is established in line with the national coordinated vulnerability disclosure (CVD) policy; reports from researchers and users on the entity's products and services are handled, fixed and disclosed in coordination with the national CSIRT where appropriate.A.5.5 Contact with authorities
A.8.8 Management of technical vulnerabilities
SDV-06Art. 21(2)(e)
Implementing Reg. (EU) 2024/2690 Annex, point 6.7 (network security), 6.8 (network segmentation) and 6.9 (protection against malicious and unauthorised software)
Network security is implemented: documented network architecture, segmentation of critical systems and administration networks, secure configuration of network services, filtering of traffic and protection against malicious software and malicious web content.A.8.7 Protection against malware
A.8.16 Monitoring activities
A.8.20 Networks security
A.8.21 Security of network services
A.8.22 Segregation of networks
A.8.23 Web filtering
EFF – Assessing the effectiveness of measures
EFF-01Art. 21(2)(f)
Implementing Reg. (EU) 2024/2690 Annex, point 7 (policies and procedures to assess effectiveness)
Policies and procedures to assess the effectiveness of cybersecurity risk-management measures are established, with indicators, measurement methods, frequency and responsibilities.Clause 9 Performance evaluation
A.5.36 Compliance with policies, rules and standards for information security
EFF-02Art. 21(2)(f); Art. 32(2)(b)-(d); Art. 33(2)(b)-(c)
Implementing Reg. (EU) 2024/2690 Annex, point 6.5 and 7; ISO/IEC 27001 Cl. 9.2
Internal audits, independent reviews and technical security testing (vulnerability scans, penetration tests, red teaming where appropriate) are planned and performed, and systems are protected during audit testing.Clause 9 Performance evaluation
A.5.35 Independent review of information security
A.8.29 Security testing in development and acceptance
A.8.33 Test information
A.8.34 Protection of information systems during audit testing
EFF-03Art. 20(1); Art. 21(4)
ISO/IEC 27001 Cl. 9.3, 10.1-10.2
Top management reviews the management system at planned intervals (results of monitoring, audits, incidents, risks, supplier performance, legal changes) and decides on improvements; nonconformities are corrected and recurrence prevented.Clause 9 Performance evaluation
Clause 10 Improvement
HYG – Cyber hygiene and training
HYG-01Art. 21(2)(g); Recital 89
Implementing Reg. (EU) 2024/2690 Annex, point 8.1 (awareness raising and basic cyber hygiene practices)
Basic cyber hygiene practices are implemented as a documented baseline: secure configuration and hardening of endpoints and servers, timely updates, least privilege, anti-malware, MFA, backups, secure remote access and removal of unsupported software.Clause 7.3 (Support)
A.6.3 Information security awareness, education and training
A.8.1 User end point devices
A.8.7 Protection against malware
A.8.9 Configuration management
HYG-02Art. 21(2)(g); Art. 20(2)
Implementing Reg. (EU) 2024/2690 Annex, point 8.2 (security training)
All employees and relevant contractors receive cybersecurity awareness training at onboarding and regularly thereafter, with role-based modules for administrators, developers, incident responders and management.Clause 7.2 (Support)
A.6.3 Information security awareness, education and training
HYG-03Art. 21(2)(g) and (i)
Implementing Reg. (EU) 2024/2690 Annex, point 8.1 (basic cyber hygiene practices) and 12.2 (handling of assets)
Rules for acceptable use of assets, remote working and clear desk and clear screen are defined, communicated and enforced.Clause 7.3 (Support)
A.5.10 Acceptable use of information and other associated assets
A.6.3 Information security awareness, education and training
A.6.7 Remote working
A.7.7 Clear desk and clear screen
A.8.7 Protection against malware
CRY – Cryptography and encryption
CRY-01Art. 21(2)(h)
Implementing Reg. (EU) 2024/2690 Annex, point 9 (cryptography); ENISA and national agency cryptographic recommendations; NIS Cooperation Group, Coordinated Implementation Roadmap for the Transition to Post-Quantum Cryptography (23/06/2025)
A cryptography policy defines where encryption is required (data at rest, in transit, backups, removable media), approved algorithms, protocols and key lengths, and a roadmap for deprecating weak algorithms and migrating to post-quantum cryptography.A.8.24 Use of cryptography
CRY-02Art. 21(2)(h)
Implementing Reg. (EU) 2024/2690 Annex, point 9.2 (key management)
Cryptographic keys and certificates are managed throughout their life cycle (generation, storage, distribution, rotation, revocation, destruction) with protection of private keys and segregation of duties.A.8.24 Use of cryptography
A.5.14 Information transfer
HRA – Human resources, access control, assets and physical security
HRA-01Art. 21(2)(i)
Implementing Reg. (EU) 2024/2690 Annex, point 10 (human resources security)
Human resources security covers the employment life cycle: background screening proportionate to role, security responsibilities in contracts, confidentiality agreements, a disciplinary process and responsibilities after termination or change of role.A.6.1 Screening
A.6.2 Terms and conditions of employment
A.6.4 Disciplinary process
A.6.5 Responsibilities after termination or change of employment
A.6.6 Confidentiality or non-disclosure agreements
HRA-02Art. 21(2)(i)
Implementing Reg. (EU) 2024/2690 Annex, point 11.1 (access control policy), 11.2 (management of access rights), 11.5 (identification)
An access control policy based on business and security requirements governs identity management and the life cycle of access rights (provisioning, review, removal), applying need-to-know and least privilege.A.5.15 Access control
A.5.16 Identity management
A.5.18 Access rights
A.7.2 Physical entry
A.8.3 Information access restriction
A.8.21 Security of network services
HRA-03Art. 21(2)(i) and (j)
Implementing Reg. (EU) 2024/2690 Annex, point 11.3 (privileged accounts and system administration accounts) and 11.4 (administration systems)
Privileged and system administration accounts are restricted, individually assigned, monitored and used only for administrative tasks; administration systems are dedicated and segregated; privileged utility programs are controlled.A.8.2 Privileged access rights
A.8.3 Information access restriction
A.8.18 Use of privileged utility programs
HRA-04Art. 21(2)(i)-(j)
Implementing Reg. (EU) 2024/2690 Annex, point 11.6 (authentication)
Authentication information (passwords, keys, tokens, secrets in code and configuration) is allocated and managed securely, with strong requirements and protection against disclosure.A.5.17 Authentication information
HRA-05Art. 21(2)(i)
Implementing Reg. (EU) 2024/2690 Annex, point 12 (asset management: classification, handling, removable media, inventory, deposit/return/deletion of assets)
Assets are managed: an inventory of information, hardware, software, services and data flows with owners is maintained; information is classified and labelled; handling rules cover storage media, assets off-premises and return of assets.A.5.9 Inventory of information and other associated assets
A.5.11 Return of assets
A.5.12 Classification of information
A.5.13 Labelling of information
A.7.9 Security of assets off-premises
A.7.10 Storage media
HRA-06Art. 21(2)(i); Art. 2(12) and (14) (GDPR applies); Art. 35
GDPR Art. 5, 25, 32
Data protection controls support confidentiality: secure deletion of information no longer required, masking of sensitive data, data leakage prevention on relevant channels, protection of records and privacy-by-design for personal data.A.8.10 Information deletion
A.8.11 Data masking
A.8.12 Data leakage prevention
A.5.33 Protection of records
A.5.34 Privacy and protection of personal identifiable information (PII)
HRA-07Art. 21(1) (all-hazards approach); Art. 21(2)(i)
Implementing Reg. (EU) 2024/2690 Annex, point 13.3 (perimeter and physical access control)
Physical access to premises hosting network and information systems is controlled: defined security perimeters, entry controls, secured rooms and facilities, physical security monitoring and rules for working in secure areas.A.7.1 Physical security perimeters
A.7.2 Physical entry
A.7.3 Securing offices, rooms and facilities
A.7.4 Physical security monitoring
A.7.6 Working in secure areas
HRA-08Art. 21(1); Art. 21(2)(c) and (i)
Implementing Reg. (EU) 2024/2690 Annex, point 13.1 (supporting utilities) and 13.2 (protection against physical and environmental threats)
Equipment and facilities are protected against environmental threats and failures: equipment siting, supporting utilities (power, cooling, connectivity) with redundancy, cabling security, equipment maintenance and secure disposal or re-use.A.7.5 Protecting against physical and environmental threats
A.7.8 Equipment siting and protection
A.7.11 Supporting utilities
A.7.12 Cabling security
A.7.13 Equipment maintenance
A.7.14 Secure disposal or re-use of equipment
MFA – Multi-factor authentication and secure communications
MFA-01Art. 21(2)(j)
Implementing Reg. (EU) 2024/2690 Annex, point 11.7 (multi-factor authentication)
Multi-factor or continuous authentication is used where appropriate and at least for remote access, privileged accounts, administration interfaces, cloud consoles and access to critical systems.A.5.17 Authentication information
A.8.5 Secure authentication
MFA-02Art. 21(2)(j)
No dedicated point in Implementing Reg. (EU) 2024/2690 (point 9, cryptography, applies by analogy); ENISA Technical Implementation Guidance v1.0 (cryptography and network security sections)
Voice, video and text communications used by the entity are secured (encrypted in transit, authenticated, protected against unauthorised interception), and security requirements for the underlying network services are defined and enforced.A.5.14 Information transfer
A.8.21 Security of network services
MFA-03Art. 21(2)(j); Art. 21(2)(c)
Implementing Reg. (EU) 2024/2690 Annex, point 4.3 (crisis management: communication)
Secured emergency communication systems are available within the entity, independent of primary infrastructure, to coordinate response when normal channels are unavailable or compromised.A.5.14 Information transfer
A.5.26 Response to information security incidents
A.5.29 Information security during disruption
A.5.30 ICT readiness for business continuity
REP – Incident reporting and information sharing
REP-01Art. 23(3); Art. 6(6) (definition of incident)
Implementing Reg. (EU) 2024/2690 Art. 3-14 (general and sector-specific criteria, recurring incidents); national guidance on significance thresholds
Criteria to classify an incident as significant are defined and embedded in triage: severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other persons; entities under Implementing Reg. 2024/2690 apply its quantitative thresholds.A.5.25 Assessment and decision on information security events
A.5.24 Information security incident management planning and preparation
REP-02Art. 23(4)(a)
National reporting portal and templates; Art. 23(11) implementing acts on notification format and procedure, where adopted; Commission NIS2 FAQ
An early warning is submitted to the CSIRT or competent authority within 24 hours of becoming aware of a significant incident, indicating whether it is suspected to be caused by unlawful or malicious acts and whether it could have cross-border impact.A.5.26 Response to information security incidents
A.5.5 Contact with authorities
REP-03Art. 23(4)(b)-(e); Art. 23(4), second subparagraph (trust service providers: 24 hours)
Implementing Reg. (EU) 2024/2690 Annex, point 3.6 (post-incident review supports the final report)
An incident notification with initial assessment (severity, impact, indicators of compromise) is submitted within 72 hours, intermediate status reports are provided on request, and a final report (description, root cause, mitigation, cross-border impact) is submitted within one month of the notification, or a progress report if the incident is ongoing.A.5.5 Contact with authorities
A.5.26 Response to information security incidents
A.5.27 Learning from information security incidents
A.5.28 Collection of evidence
REP-04Art. 23(1)-(2)
Consumer and contract law; sector rules on customer communication
Recipients of services are notified without undue delay of significant incidents likely to adversely affect the provision of the service, and of significant cyber threats together with measures or remedies they can take.A.5.26 Response to information security incidents
A.5.14 Information transfer
REP-05Art. 23; Art. 4; Art. 35
Reg. (EU) 2024/2847 Art. 14 (CRA reporting from 11/09/2026); Reg. (EU) 2022/2554 Art. 19 (DORA); GDPR Art. 33-34; proposal COM(2025) 837 - Digital Omnibus (single entry point for incident reporting, under negotiation)
Reporting obligations under overlapping regimes are mapped and coordinated: NIS2 (24 h / 72 h / 1 month), GDPR Art. 33 (72 h), DORA (financial entities), CER (critical entities), eIDAS (trust services), CRA (manufacturers, via the ENISA Single Reporting Platform) and any cross-border notifications.A.5.31 Legal, statutory, regulatory and contractual requirements
A.5.24 Information security incident management planning and preparation
REP-06Art. 29; Art. 30
National information-sharing arrangements; sector ISACs
The entity participates in cybersecurity information-sharing arrangements where available and makes use of voluntary notification of near misses, non-significant incidents and cyber threats to the CSIRT; it notifies the competent authority when it joins or leaves an information-sharing arrangement (Art. 29(4)).A.5.6 Contact with special interest groups
A.5.7 Threat intelligence
REP-07Art. 21(5); Art. 23(11)
Implementing Reg. (EU) 2024/2690 Art. 3-14 and Annex; ENISA Technical Implementation Guidance v1.0 (26/06/2025) and mapping table (v1.2, 21/08/2025)
Entities within the scope of Implementing Regulation (EU) 2024/2690 (DNS, TLD registries, cloud, data centre, CDN, managed service and managed security service providers, online marketplaces, search engines, social networks, trust service providers) implement the technical and methodological requirements of its Annex and apply its sector-specific significance criteria.A.5.31 Legal, statutory, regulatory and contractual requirements
A.5.25 Assessment and decision on information security events
Clause 8 Operation
SUP – Supervision, enforcement and interplay with other EU acts
SUP-01Art. 32(2); Art. 33(2); Art. 31
National supervisory guidance and self-assessment questionnaires
The entity is prepared for supervision: it can respond to requests for information, on-site inspections, security audits, security scans and requests for evidence of implementation of Art. 21 measures within the deadlines set by the competent authority.A.5.35 Independent review of information security
A.5.36 Compliance with policies, rules and standards for information security
A.8.34 Protection of information systems during audit testing
Clause 9 Performance evaluation
SUP-02Art. 32(4)-(6)
National transposition law (procedural details)
Essential entities understand the ex ante supervisory regime (regular and targeted audits, inspections, binding instructions) and the enforcement measures specific to them: temporary suspension of certifications or authorisations and temporary prohibition of natural persons at CEO or legal representative level from exercising managerial functions in case of non-compliance with orders.A.5.31 Legal, statutory, regulatory and contractual requirements
Clause 5 Leadership
SUP-03Art. 34; Art. 35; Art. 36
National law setting the actual maximum fines and periodic penalty payments
The penalty regime is understood and reflected in risk appetite: maximum administrative fines of at least EUR 10 000 000 or 2% of the total worldwide annual turnover of the undertaking to which the entity belongs (essential entities) and of at least EUR 7 000 000 or 1.4% (important entities), whichever is higher (national law may set higher maxima), plus liability of natural persons and coordination with GDPR fines.A.5.31 Legal, statutory, regulatory and contractual requirements
Clause 5 Leadership
SUP-04Art. 4; Recital 28
Reg. (EU) 2022/2554 (DORA) Art. 1(2), Art. 19; NIS2 Recital 28
Financial entities covered by DORA apply DORA's ICT risk management, incident reporting and third-party risk requirements instead of Art. 21 and 23 NIS2 (lex specialis), while remaining subject to NIS2 scoping and information-sharing provisions; the mapping is documented.A.5.31 Legal, statutory, regulatory and contractual requirements
SUP-05Art. 3(1)(f); Art. 2(3); Art. 13(5)
Directive (EU) 2022/2557 (CER) Art. 6, 13, 15
Entities identified as critical entities under the CER Directive are treated as essential entities under NIS2; physical resilience measures (CER) and cybersecurity measures (NIS2) are coordinated and authorities cooperate.A.5.31 Legal, statutory, regulatory and contractual requirements
A.5.29 Information security during disruption
SUP-06Art. 21(2)(e); Art. 24 (certification and standards)
Reg. (EU) 2024/2847 (CRA) Art. 13-14, Art. 16, Art. 71(2); ENISA Single Reporting Platform; Commission CRA reporting guidance
Manufacturers of products with digital elements comply with the Cyber Resilience Act: reporting of actively exploited vulnerabilities and severe incidents via the ENISA Single Reporting Platform (24 h early warning, 72 h notification, final report within 14 days of a corrective measure for vulnerabilities and within one month of the notification for severe incidents) from 11/09/2026, and essential cybersecurity requirements from 11/12/2027; users of such products factor CRA conformity into procurement.A.5.21 Managing information security in the information and communication technology (ICT) supply chain
A.8.8 Management of technical vulnerabilities
SUP-07Art. 24; Art. 25
Reg. (EU) 2019/881 (Cybersecurity Act) and the Commission proposal for its revision (20/01/2026, under negotiation); ISO/IEC 27001:2022
European and international standards and certification schemes are used to demonstrate compliance: ISO/IEC 27001 certification of the ISMS, European cybersecurity certification schemes (EUCC, EUCS when adopted) for products and services, and sector schemes where required nationally.A.5.31 Legal, statutory, regulatory and contractual requirements
Clause 4 Context of the organization
SUP-08Art. 40 (review); Art. 41 (transposition)
Commission NIS2 FAQ; ENISA publications; proposals COM(2026) 13 (procedure 2026/0012(COD)) and COM(2025) 837 (procedure 2025/0360(COD)), both under negotiation
Regulatory developments are monitored and assessed: national transposition updates and infringement proceedings, the targeted NIS2 amendments (COM(2026) 13), the Digital Omnibus incident-reporting proposals, the Cybersecurity Act revision, ENISA guidance and the Commission review due by 17/10/2027.A.5.31 Legal, statutory, regulatory and contractual requirements
A.5.6 Contact with special interest groups

Reverse table: ISO/IEC 27001:2022 clauses and controls and the NIS2 provisions they support

Clause or controlLegal referencesRequirement ids
Clause 4 Context of the organizationArt. 2; Art. 3; Annex I; Annex II; Art. 26(1)-(3); Art. 4; Art. 2(12); Art. 21(1); Art. 24; Art. 25SCO-01, SCO-02, SCO-04, SUP-07
Clause 5 LeadershipArt. 20(1); Art. 21(1); Art. 20(1); Art. 32(6); Art. 32(4)-(6); Art. 34; Art. 35; Art. 36GOV-01, GOV-02, SUP-02, SUP-03
Clause 5.2 (Leadership)Art. 20(1); Art. 21(1); Art. 21(2)(a); Art. 20(1)GOV-01, RSK-03
Clause 5.3 (Leadership)Art. 20(1); Art. 32(6)GOV-02
Clause 6 PlanningArt. 20(1); Art. 21(1)GOV-04
Clause 6.1 (Planning)Art. 21(1)-(2)(a); Art. 21(1)-(2)(a); Art. 21(4)RSK-01, RSK-02
Clause 6.2 (Planning)Art. 21(1)-(2)(a); Art. 21(1)-(2)(a); Art. 21(4)RSK-01, RSK-02
Clause 7 SupportArt. 20(2); Art. 20(1); Art. 21(1); Art. 21(1); Art. 32(2)(e)-(g); Art. 33(2)(d)-(f) (information and evidence requested by authorities)GOV-03, GOV-04, GOV-06
Clause 7.2 (Support)Art. 21(2)(g); Art. 20(2)HYG-02
Clause 7.3 (Support)Art. 21(2)(g); Recital 89; Art. 21(2)(g) and (i)HYG-01, HYG-03
Clause 8 OperationArt. 21(2)(c); Art. 21(5); Art. 23(11)BCM-01, REP-07
Clause 9 Performance evaluationArt. 21(2)(a) and (f); Art. 21(2)(c) and (f); Art. 21(2)(f); Art. 21(2)(f); Art. 32(2)(b)-(d); Art. 33(2)(b)-(c); Art. 20(1); Art. 21(4); Art. 32(2); Art. 33(2); Art. 31RSK-04, BCM-04, EFF-01, EFF-02, EFF-03, SUP-01
Clause 9.2 (Performance evaluation)Art. 21(2)(a) and (f)RSK-04
Clause 9.3 (Performance evaluation)Art. 20(1); Art. 21(1); Art. 21(2)(a); Art. 20(1)GOV-01, RSK-03
Clause 10 ImprovementArt. 21(2)(b); Art. 21(4); Art. 20(1); Art. 21(4)INC-05, EFF-03
A.5.1 Policies for information securityArt. 20(1); Art. 21(1); Art. 21(2)(a); Art. 20(1)GOV-01, RSK-03
A.5.2 Information security roles and responsibilitiesArt. 20(1); Art. 32(6); Art. 20(1); Art. 21(1); Art. 21(2)(a); Art. 20(1); Art. 21(2)(b); Art. 23GOV-02, GOV-04, RSK-03, INC-01
A.5.3 Segregation of dutiesArt. 20(1); Art. 32(6)GOV-02
A.5.4 Management responsibilitiesArt. 20(1); Art. 21(1); Art. 20(1); Art. 32(6); Art. 21(2)(a); Art. 20(1)GOV-01, GOV-02, RSK-03
A.5.5 Contact with authoritiesArt. 3(4); Art. 27; Art. 23(1); Art. 29; Art. 21(2)(c); Art. 23(1); Art. 21(2)(e); Art. 12; Art. 23(4)(a); Art. 23(4)(b)-(e); Art. 23(4), second subparagraph (trust service providers: 24 hours)SCO-03, GOV-05, BCM-03, SDV-05, REP-02, REP-03
A.5.6 Contact with special interest groupsArt. 23(1); Art. 29; Art. 29; Art. 30; Art. 40 (review); Art. 41 (transposition)GOV-05, REP-06, SUP-08
A.5.7 Threat intelligenceArt. 21(1)-(2)(a); Art. 21(1)-(2)(a); Art. 21(4); Art. 21(2)(a) and (e); Art. 29 (information sharing); Art. 29; Art. 30RSK-01, RSK-02, RSK-05, REP-06
A.5.8 Information security in project managementArt. 21(2)(a) and (e); Art. 29 (information sharing)RSK-05
A.5.9 Inventory of information and other associated assetsArt. 21(2)(i)HRA-05
A.5.10 Acceptable use of information and other associated assetsArt. 21(2)(g) and (i)HYG-03
A.5.11 Return of assetsArt. 21(2)(i)HRA-05
A.5.12 Classification of informationArt. 21(2)(i)HRA-05
A.5.13 Labelling of informationArt. 21(2)(i)HRA-05
A.5.14 Information transferArt. 21(2)(h); Art. 21(2)(j); Art. 21(2)(j); Art. 21(2)(c); Art. 23(1)-(2)CRY-02, MFA-02, MFA-03, REP-04
A.5.15 Access controlArt. 21(2)(i)HRA-02
A.5.16 Identity managementArt. 21(2)(i)HRA-02
A.5.17 Authentication informationArt. 21(2)(i)-(j); Art. 21(2)(j)HRA-04, MFA-01
A.5.18 Access rightsArt. 21(2)(i)HRA-02
A.5.19 Information security in supplier relationshipsArt. 21(1)-(2)(a); Art. 21(1)-(2)(a); Art. 21(4); Art. 21(2)(d); Art. 21(3); Art. 22; Art. 21(2)(d); Art. 21(3); Art. 21(2)(d)RSK-01, RSK-02, SCM-01, SCM-02, SCM-03
A.5.20 Addressing information security within supplier agreementsArt. 21(1)-(2)(a); Art. 21(1)-(2)(a); Art. 21(4); Art. 21(2)(d); Art. 21(3); Art. 22; Art. 21(2)(d); Art. 21(3); Art. 21(2)(d)RSK-01, RSK-02, SCM-01, SCM-02, SCM-03
A.5.21 Managing information security in the information and communication technology (ICT) supply chainArt. 21(1)-(2)(a); Art. 21(1)-(2)(a); Art. 21(4); Art. 21(2)(d); Art. 21(3); Art. 22; Art. 21(2)(d); Art. 21(3); Art. 21(2)(d); Art. 21(2)(e); Art. 21(2)(e); Art. 24 (certification and standards)RSK-01, RSK-02, SCM-01, SCM-02, SCM-03, SDV-01, SUP-06
A.5.22 Monitoring, review and change management of supplier servicesArt. 21(2)(d)SCM-03
A.5.23 Information security for use of cloud servicesArt. 21(2)(d) and (e); Art. 21(2)(e)SCM-04, SDV-01
A.5.24 Information security incident management planning and preparationArt. 21(2)(b); Art. 23; Art. 23(3); Art. 6(6) (definition of incident); Art. 23; Art. 4; Art. 35INC-01, REP-01, REP-05
A.5.25 Assessment and decision on information security eventsArt. 21(2)(b); Art. 23(3); Art. 23(3); Art. 6(6) (definition of incident); Art. 21(5); Art. 23(11)INC-03, REP-01, REP-07
A.5.26 Response to information security incidentsArt. 21(2)(b); Art. 21(2)(c); Art. 23(1); Art. 21(2)(j); Art. 21(2)(c); Art. 23(4)(a); Art. 23(4)(b)-(e); Art. 23(4), second subparagraph (trust service providers: 24 hours); Art. 23(1)-(2)INC-04, BCM-03, MFA-03, REP-02, REP-03, REP-04
A.5.27 Learning from information security incidentsArt. 21(2)(b); Art. 21(4); Art. 23(4)(b)-(e); Art. 23(4), second subparagraph (trust service providers: 24 hours)INC-05, REP-03
A.5.28 Collection of evidenceArt. 21(2)(b); Art. 23(4)(b)-(e); Art. 23(4), second subparagraph (trust service providers: 24 hours)INC-02, INC-04, REP-03
A.5.29 Information security during disruptionArt. 21(2)(c); Art. 21(2)(c); Art. 23(1); Art. 21(2)(c) and (f); Art. 21(2)(j); Art. 21(2)(c); Art. 3(1)(f); Art. 2(3); Art. 13(5)BCM-01, BCM-03, BCM-04, MFA-03, SUP-05
A.5.30 ICT readiness for business continuityArt. 21(2)(c); Art. 21(2)(c); Art. 23(1); Art. 21(2)(c) and (f); Art. 21(2)(j); Art. 21(2)(c)BCM-01, BCM-03, BCM-04, MFA-03
A.5.31 Legal, statutory, regulatory and contractual requirementsArt. 2; Art. 3; Annex I; Annex II; Art. 26(1)-(3); Art. 3(4); Art. 27; Art. 4; Art. 2(12); Art. 21(1); Art. 28; Art. 21(2)(a) and (f); Art. 23; Art. 4; Art. 35; Art. 21(5); Art. 23(11); Art. 32(4)-(6); Art. 34; Art. 35; Art. 36; Art. 4; Recital 28; Art. 3(1)(f); Art. 2(3); Art. 13(5); Art. 24; Art. 25; Art. 40 (review); Art. 41 (transposition)SCO-01, SCO-02, SCO-03, SCO-04, SCO-05, RSK-04, REP-05, REP-07, SUP-02, SUP-03, SUP-04, SUP-05, SUP-07, SUP-08
A.5.32 Intellectual property rightsArt. 4; Art. 2(12); Art. 21(1)SCO-04
A.5.33 Protection of recordsArt. 28; Art. 21(1); Art. 32(2)(e)-(g); Art. 33(2)(d)-(f) (information and evidence requested by authorities); Art. 21(2)(i); Art. 2(12) and (14) (GDPR applies); Art. 35SCO-05, GOV-06, HRA-06
A.5.34 Privacy and protection of personal identifiable information (PII)Art. 4; Art. 2(12); Art. 21(1); Art. 28; Art. 21(2)(i); Art. 2(12) and (14) (GDPR applies); Art. 35SCO-04, SCO-05, HRA-06
A.5.35 Independent review of information securityArt. 21(2)(a) and (f); Art. 21(2)(f); Art. 32(2)(b)-(d); Art. 33(2)(b)-(c); Art. 32(2); Art. 33(2); Art. 31RSK-04, EFF-02, SUP-01
A.5.36 Compliance with policies, rules and standards for information securityArt. 20(1); Art. 21(1); Art. 21(1); Art. 32(2)(e)-(g); Art. 33(2)(d)-(f) (information and evidence requested by authorities); Art. 21(2)(a); Art. 20(1); Art. 21(2)(a) and (f); Art. 21(2)(f); Art. 32(2); Art. 33(2); Art. 31GOV-01, GOV-06, RSK-03, RSK-04, EFF-01, SUP-01
A.5.37 Documented operating proceduresArt. 21(1); Art. 32(2)(e)-(g); Art. 33(2)(d)-(f) (information and evidence requested by authorities)GOV-06
A.6.1 ScreeningArt. 21(2)(i)HRA-01
A.6.2 Terms and conditions of employmentArt. 21(2)(i)HRA-01
A.6.3 Information security awareness, education and trainingArt. 20(2); Art. 21(2)(g); Recital 89; Art. 21(2)(g); Art. 20(2); Art. 21(2)(g) and (i)GOV-03, HYG-01, HYG-02, HYG-03
A.6.4 Disciplinary processArt. 21(2)(i)HRA-01
A.6.5 Responsibilities after termination or change of employmentArt. 21(2)(i)HRA-01
A.6.6 Confidentiality or non-disclosure agreementsArt. 21(2)(i)HRA-01
A.6.7 Remote workingArt. 21(2)(g) and (i)HYG-03
A.6.8 Information security event reportingArt. 21(2)(b); Art. 23(3)INC-03
A.7.1 Physical security perimetersArt. 21(1) (all-hazards approach); Art. 21(2)(i)HRA-07
A.7.2 Physical entryArt. 21(2)(i); Art. 21(1) (all-hazards approach); Art. 21(2)(i)HRA-02, HRA-07
A.7.3 Securing offices, rooms and facilitiesArt. 21(1) (all-hazards approach); Art. 21(2)(i)HRA-07
A.7.4 Physical security monitoringArt. 21(1) (all-hazards approach); Art. 21(2)(i)HRA-07
A.7.5 Protecting against physical and environmental threatsArt. 21(1); Art. 21(2)(c) and (i)HRA-08
A.7.6 Working in secure areasArt. 21(1) (all-hazards approach); Art. 21(2)(i)HRA-07
A.7.7 Clear desk and clear screenArt. 21(2)(g) and (i)HYG-03
A.7.8 Equipment siting and protectionArt. 21(1); Art. 21(2)(c) and (i)HRA-08
A.7.9 Security of assets off-premisesArt. 21(2)(i)HRA-05
A.7.10 Storage mediaArt. 21(2)(i)HRA-05
A.7.11 Supporting utilitiesArt. 21(1); Art. 21(2)(c) and (i)HRA-08
A.7.12 Cabling securityArt. 21(1); Art. 21(2)(c) and (i)HRA-08
A.7.13 Equipment maintenanceArt. 21(1); Art. 21(2)(c) and (i)HRA-08
A.7.14 Secure disposal or re-use of equipmentArt. 21(1); Art. 21(2)(c) and (i)HRA-08
A.8.1 User end point devicesArt. 21(2)(g); Recital 89HYG-01
A.8.2 Privileged access rightsArt. 21(2)(i) and (j)HRA-03
A.8.3 Information access restrictionArt. 21(2)(i); Art. 21(2)(i) and (j)HRA-02, HRA-03
A.8.5 Secure authenticationArt. 21(2)(j)MFA-01
A.8.6 Capacity managementArt. 21(2)(c)BCM-02
A.8.7 Protection against malwareArt. 21(2)(e); Art. 21(2)(g); Recital 89; Art. 21(2)(g) and (i)SDV-06, HYG-01, HYG-03
A.8.8 Management of technical vulnerabilitiesArt. 21(2)(e); Art. 21(2)(e); Art. 12; Art. 21(2)(e); Art. 24 (certification and standards)SDV-04, SDV-05, SUP-06
A.8.9 Configuration managementArt. 21(2)(e); Art. 21(2)(g); Recital 89SDV-03, HYG-01
A.8.10 Information deletionArt. 21(2)(i); Art. 2(12) and (14) (GDPR applies); Art. 35HRA-06
A.8.11 Data maskingArt. 21(2)(i); Art. 2(12) and (14) (GDPR applies); Art. 35HRA-06
A.8.12 Data leakage preventionArt. 21(2)(i); Art. 2(12) and (14) (GDPR applies); Art. 35HRA-06
A.8.13 Information backupArt. 21(2)(c)BCM-02
A.8.14 Redundancy of information processing facilitiesArt. 21(2)(c)BCM-02
A.8.15 LoggingArt. 21(2)(b)INC-02
A.8.16 Monitoring activitiesArt. 21(2)(b); Art. 21(2)(e)INC-02, SDV-06
A.8.17 Clock synchronizationArt. 21(2)(b)INC-02
A.8.18 Use of privileged utility programsArt. 21(2)(i) and (j)HRA-03
A.8.19 Installation of software on operational systemsArt. 21(2)(e)SDV-03
A.8.20 Networks securityArt. 21(2)(e)SDV-06
A.8.21 Security of network servicesArt. 21(2)(e); Art. 21(2)(i); Art. 21(2)(j)SDV-06, HRA-02, MFA-02
A.8.22 Segregation of networksArt. 21(2)(e)SDV-06
A.8.23 Web filteringArt. 21(2)(e)SDV-06
A.8.24 Use of cryptographyArt. 21(2)(h)CRY-01, CRY-02
A.8.25 Secure development life cycleArt. 21(2)(e)SDV-01, SDV-02
A.8.26 Application security requirementsArt. 21(2)(e)SDV-01
A.8.27 Secure system architecture and engineering principlesArt. 21(2)(e)SDV-01
A.8.28 Secure codingArt. 21(2)(e)SDV-01
A.8.29 Security testing in development and acceptanceArt. 21(2)(e); Art. 21(2)(f); Art. 32(2)(b)-(d); Art. 33(2)(b)-(c)SDV-02, EFF-02
A.8.30 Outsourced developmentArt. 21(2)(d); Art. 21(3); Art. 22; Art. 21(2)(d); Art. 21(3); Art. 21(2)(d); Art. 21(2)(d) and (e)SCM-01, SCM-02, SCM-03, SCM-04
A.8.31 Separation of development, test and production environmentsArt. 21(2)(e)SDV-02, SDV-04
A.8.32 Change managementArt. 21(2)(e)SDV-03, SDV-04
A.8.33 Test informationArt. 21(2)(e); Art. 21(2)(f); Art. 32(2)(b)-(d); Art. 33(2)(b)-(c)SDV-02, EFF-02
A.8.34 Protection of information systems during audit testingArt. 21(2)(f); Art. 32(2)(b)-(d); Art. 33(2)(b)-(c); Art. 32(2); Art. 33(2); Art. 31EFF-02, SUP-01

Frequently asked questions

Does ISO/IEC 27001:2022 certification make an organisation NIS2 compliant?

No. The standard covers a large part of the organisational and technical measures, but NIS2 adds legal obligations that a management-system standard does not contain, such as notifications to authorities, legal deadlines and sector-specific duties. The table shows, requirement by requirement, which clauses and controls help and where the legal reference goes beyond them.

How was the mapping built?

The links follow the mapping table published by ENISA for the points of Implementing Regulation (EU) 2024/2690 where one exists, and GoToCertify's editorial analysis elsewhere. It is an aid for gap analysis, not an official mapping issued by ISO or by an EU institution.

Can I reuse the table?

Yes: the CSV file can be downloaded from this page and reused with a link to the source. To score your own organisation against each row, use the free NIS2 Directive self-assessment.

The links follow the mapping table published by ENISA for the points of Implementing Regulation (EU) 2024/2690 where one exists, and GoToCertify's editorial analysis elsewhere. Control titles are short identifiers of the controls of the standard; the standard itself is published by ISO and must be obtained from ISO or a national standards body. Self-assessment tool for information purposes only; it does not constitute legal advice. NIS2 is a directive: the applicable obligations, deadlines, registration procedures and penalties are those of the national transposition law of each Member State. References and dates must be verified against the official texts (EUR-Lex, national gazettes). No data from this assessment is transmitted to GoToCertify. © 2026 GoToCertify.