CER vs NIS2
Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.
At a Glance
They differ on 18 of 32 topics. Each verdict names what it rests on; read the wording before relying on it.
- CER Asks more on 1 topic Alone on 1 topic More detailed on 2 topics
- NIS2 Asks more on 0 topics Alone on 13 topics More detailed on 1 topic
| Topic | CER | NIS2 | Verdict |
|---|---|---|---|
| Governance | |||
| Management accountability | CER: – | NIS2: 1 | Only NIS2no specific requirement on the other side in the acts covered |
| Roles and independence | CER: 1 | NIS2: 1 | Both cover itread the wording below |
| Security policy | CER: 1 | NIS2: 2 | Both cover itread the wording below |
| Awareness and training | CER: 1 | NIS2: 2 | Both cover itread the wording below |
| Risk management | |||
| Risk management framework | CER: 2 | NIS2: 3 | Both cover itread the wording below |
| Risk assessment | CER: 2 | NIS2: 2 | Both cover itread the wording below |
| Review, audit and improvement | CER: 2 | NIS2: 3 | Both cover itread the wording below |
| Asset management | CER: – | NIS2: 2 | Only NIS2no specific requirement on the other side in the acts covered |
| Protection | |||
| Access control | CER: 1 | NIS2: 2 | Both cover itread the wording below |
| Authentication | CER: – | NIS2: 2 | Only NIS2no specific requirement on the other side in the acts covered |
| Cryptography and encryption | CER: – | NIS2: 1 | Only NIS2no specific requirement on the other side in the acts covered |
| Network security | CER: – | NIS2: 1 | Only NIS2no specific requirement on the other side in the acts covered |
| Secure communications | CER: – | NIS2: 1 | Only NIS2no specific requirement on the other side in the acts covered |
| Secure acquisition and development | CER: – | NIS2: 1 | Only NIS2no specific requirement on the other side in the acts covered |
| Configuration, change and patch management | CER: – | NIS2: 1 | Only NIS2no specific requirement on the other side in the acts covered |
| Vulnerability handling | CER: – | NIS2: 1 | Only NIS2no specific requirement on the other side in the acts covered |
| Human resources security | CER: 3 | NIS2: 2 | Both cover itread the wording below |
| Physical and environmental security | CER: 1 | NIS2: 2 | Both cover itread the wording below |
| Detection and response | |||
| Monitoring and detection | CER: – | NIS2: 1 | Only NIS2no specific requirement on the other side in the acts covered |
| Incident handling | CER: 1 | NIS2: 1 | Both cover itread the wording below |
| Incident classification | CER: 1 | NIS2: 3 | NIS2 more detailedmore requirements on this, not necessarily stricter |
| Reporting to authorities | CER: 3 | NIS2: 5 | Both cover itread the wording below |
| Informing customers and the public | CER: 1 | NIS2: 2 | Both cover itread the wording below |
| Threat intelligence and information sharing | CER: 1 | NIS2: 1 | CER asks morebinding, where the other is optional |
| Continuity and resilience | |||
| Business continuity and crisis management | CER: 3 | NIS2: 1 | CER more detailedmore requirements on this, not necessarily stricter |
| Backup and recovery | CER: – | NIS2: 2 | Only NIS2no specific requirement on the other side in the acts covered |
| Security testing | CER: – | NIS2: 1 | Only NIS2no specific requirement on the other side in the acts covered |
| Third parties and supply chain | |||
| Supplier and third-party risk | CER: 3 | NIS2: 2 | Both cover itread the wording below |
| Register of third-party arrangements | CER: – | NIS2: 1 | Only NIS2no specific requirement on the other side in the acts covered |
| Supervision and enforcement | |||
| Registration with authorities | CER: 4 | NIS2: 2 | CER more detailedmore requirements on this, not necessarily stricter |
| Cooperation with supervisors | CER: 4 | NIS2: – | Only CERno specific requirement on the other side in the acts covered |
| Penalties and liability | CER: 1 | NIS2: 2 | Both cover itread the wording below |
What This Covers
The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.
Included
- CER Directive (EU) 2022/2557 of the European Parliament and of the Council of 14 December 2022
Status
Reviewed against the official texts.
Included
- NIS2 Directive (EU) 2022/2555
- NIS2 Implementing Regulation Commission Implementing Regulation (EU) 2024/2690 Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
Status
Reviewed against the official texts.
Key Numbers
Deadline
CER: By 17 July 2026 (Member States); Member State notifies within one month of identification (Member States); Within nine months of receiving the notification; Central authorities reply within 10 working days of receiving the request (Member States); Rules notified to the Commission by 17 October 2024 (Member States)
NIS2: Not in the acts covered
How often
CER: List reviewed at least every four years (Member States); Whenever necessary, and at least every four years
NIS2: Not in the acts covered
Threshold
CER: Actual or potential significant disruption of essential servicesEssential Service; Essential services to or in six or more Member States
NIS2: Not in the acts covered
Goes to
CER: Competent authority
NIS2: Not in the acts covered
Evidence to keep
CER: Resilience planIn critical infrastructure regulation, a document explaining how an organisation will protect and maintain services that society depends on, and restore them after disruption. It connects identified risks with practical safeguards, responsibilities and arrangements for prevention, response and recovery. The required contents, approval process and use of equivalent existing documents depend on the applicable national law. or equivalent documents; Information and evidence on the Article 13 measures (Critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. that are also entities under Directive (EU) 2022/2555)
NIS2: Not in the acts covered
Incident reports go to
CER: Competent authority
NIS2: CSIRTComputer Security Incident Response Team or competent authority
First notice of an incident
CER: Within 24 hours of becoming aware
NIS2: Without undue delay and in any event within 24 hours of becoming aware
Incident notification
CER: Not in the acts covered
NIS2: Without undue delay and in any event within 72 hours of becoming aware (24 hours for trust serviceAn electronic service, normally provided for payment, such as issuing and validating certificates, creating and validating electronic signatures and seals, electronic registered delivery, electronic archiving, attestation of attributes or recording data in electronic ledgers. Trust service providers are regulated by eIDAS and in scope of NIS2. providers, for incidents affecting their trust servicesAn electronic service, normally provided for payment, such as issuing and validating certificates, creating and validating electronic signatures and seals, electronic registered delivery, electronic archiving, attestation of attributes or recording data in electronic ledgers. Trust service providers are regulated by eIDAS and in scope of NIS2.)
Intermediate report
CER: Not in the acts covered
NIS2: On request
Final report
CER: Within one month of the initial notification, where relevant
NIS2: Within one month of the incident notification
Deadline to have the measures in place
CER: 10 months after the date of the notification (Member States)
NIS2: Not in the acts covered
External assessment or certification
CER: Audit by an independent and qualified auditor, where the authority requires evidence (Critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. that are also entities under Directive (EU) 2022/2555)
NIS2: Not in the acts covered
Review of the risk framework
CER: Not in the acts covered
NIS2: Risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change. and treatment plan at planned intervals, at least annually, and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes (DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers)
Register of third-party arrangements
CER: Not in the acts covered
NIS2: Directory of direct suppliers and service providers (DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers)
Registration with the authority
CER: Not in the acts covered
NIS2: Required; changes without delay and in any event within two weeks
Management body training
CER: Not in the acts covered
NIS2: Required
Management body liability
CER: Not in the acts covered
NIS2: Yes, for infringements of Article 21
Maximum fines
CER: Set by each Member State; effective, proportionate and dissuasive (Member States)
NIS2: Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities.: maximum of at least EUR 10 million or 2% of the undertaking's total worldwide annual turnover in the preceding financial year, whichever is higher. Important entitiesAn organisation in an Annex I or Annex II sector of NIS2 that falls within scope but does not qualify as an essential entity, typically a medium-sized or large company. Important entities have the same risk management and reporting duties, but supervision is mainly reactive, after evidence of non-compliance.: maximum of at least EUR 7 million or 1.4%, whichever is higher.
Governance
Management accountability
Only NIS2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 GV.RR, GV.OV · ISO/IEC 27001:2022 Clause 5.1, A.5.4
Nothing in the acts covered.
Management approves and oversees the measures
The management body approves the cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk-management measures, oversees their implementation and can be held liable for infringements of Article 21 by the entity. National liability requirements for public institutions and officials are unaffected.
Roles and independence
Both cover it read the wording below
NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.5.2, A.5.3
Liaison officer
Designate a liaison officer or equivalent as the point of contact with the competent authorities.
Roles, responsibilities and authorities
Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
Security roles assigned and communicated to the management bodies, at least one person reporting directly to them, conflicting duties segregated where applicable, and the assignment reviewed by the management bodies at planned intervals and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.
Security policy
Both cover it read the wording below
NIST CSF 2.0 GV.PO · ISO/IEC 27001:2022 A.5.1
Resilience plan
Have in place and apply a resilience plan or equivalent documents that describe the measures taken. Documents and measures produced under other legal acts may be reused where relevant, and the competent authority may declare them compliant in whole or in part.
Risk analysis and security policies
Policies on risk analysis and on information system security.
Network and information system security policy
Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
A security policy approved by the management body, reviewed at least annually and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.
Awareness and training
Both cover it read the wording below
NIST CSF 2.0 PR.AT · ISO/IEC 27001:2022 A.6.3
Raise staff awareness
Raise awareness of the resilience measures among relevant personnel, considering training courses, information materials and exercises.
Management body training
Members of the management body follow training to identify risks and assess cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk-management practices. Entities are encouraged to offer similar training to employees regularly.
Cyber hygiene and training
Basic cyber hygiene practices and cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. training.
Risk management
Risk management framework
Both cover it read the wording below
NIST CSF 2.0 GV.RM · ISO/IEC 27001:2022 Clause 6.1
Proportionate measures and incident prevention
Take appropriate and proportionate technical, security and organisational measures to ensure resilience, based on the Member State risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change. and the entity's own. The measures include preventing incidents, with due regard to disaster risk reduction and climate adaptation.
Encouraging standards
Applies to: Member States
Where useful, and without imposing or favouring a particular technology, Member States encourage the use of European and international standards and technical specifications relevant to the security and resilience measures of critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities.. The article places no duty on the entity itself to use them.
Appropriate and proportionate measures
Technical, operational and organisational measures to manage the risks to network and information systems, set by the state of the art, relevant standards, cost, the entity's exposure and size, and the likelihood and severity of incidents.
All-hazards approach
The measures follow an all-hazards approach that aims to protect network and information systems and their physical environment from incidents.
Risk management framework
Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
A framework to identify, analyse, assess and treat risks, with a risk treatment plan. Results and plan are reviewed at planned intervals, at least annually, and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.
Risk assessment
Both cover it read the wording below
NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 Clauses 6.1.2, 8.2
Carry out a critical entity risk assessment
Carry out a risk assessment within nine months of being notified as a critical entityA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities., then whenever necessary and at least every four years. Assess all relevant risks that could disrupt the provision of the essential services, using the Member State risk assessmentsRisk Assessment and other relevant sources of information.
All-hazards scope and dependencies
Cover all relevant natural and man-made risks, including cross-sectoral and cross-border risks, accidents, natural disasters, public health emergencies, hybrid threats and other antagonistic threats such as terrorist offences. Take into account how other sectors depend on the entity and how it depends on other sectors, including, where relevant, in neighbouring Member States and third countries. Relevant assessments made under other legal acts may be reused, and the competent authority may declare them compliant in whole or in part.
Risk analysis and security policies
Policies on risk analysis and on information system security.
Risk management framework
Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
A framework to identify, analyse, assess and treat risks, with a risk treatment plan. Results and plan are reviewed at planned intervals, at least annually, and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.
Review, audit and improvement
Both cover it read the wording below
NIST CSF 2.0 ID.IM, GV.OV · ISO/IEC 27001:2022 A.5.35, A.5.36, Clauses 9, 10
Inspections, audits and remedial orders
Applies to: Competent authorities
Competent authorities can inspect critical infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk. and premises on site, supervise Article 13 measures off site, and conduct or order audits of critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities.. They may order an entity to remedy an infringement within a reasonable time limit and to report the measures taken.
Provide information and audit evidence
Applies to: Critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. that are also entities under Directive (EU) 2022/2555
Where the competent authority requires it, and within the reasonable time limit it sets, provide the information needed to assess the Article 13 measures and evidence that they are effectively implemented. The evidence includes the results of an audit by an independent and qualified auditor, chosen by the entity and paid for by it.
Assessing effectiveness
Policies and procedures to assess whether the cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk-management measures work.
Corrective measures
An entity that finds it does not comply with the measures takes the necessary corrective measures without undue delay.
Independent review
Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
Independent reviews of network and information securityProtecting information and the systems that handle it so that only authorised people can access it, it remains accurate and complete, and it is available when needed. These aims are called confidentiality, integrity and availability. Information security combines organisational requirements, staff practices and technical safeguards to reduce risks such as disclosure, alteration, disruption or destruction. at planned intervals and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.
Asset management
Only NIS2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 ID.AM · ISO/IEC 27001:2022 A.5.9 to A.5.13
Nothing in the acts covered.
Asset management
Asset managementAsset Management in Information Security.
Asset inventory
Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
A complete, accurate, up-to-date and consistent inventory of assets, with changes recorded in a traceable way.
Protection
Access control
Both cover it read the wording below
NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.15, A.5.18, A.8.2, A.8.3
Employee security management
Ensure adequate employee security management, considering categories of personnel in critical functions, access rights to premises, critical infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk. and sensitive information, background check procedures under Article 14 and the categories of people who must undergo them, and training and qualification requirements. Include the personnel of external service providers when setting the categories of personnel in critical functions.
Access control policies
Access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements. policies.
Access rights and privileged accounts
Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
Management of access rights, and stricter controls on privileged and system administration accounts.
Authentication
Only NIS2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.17, A.8.5
Nothing in the acts covered.
Multi-factor authentication
Multi-factor or continuous authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. solutions, where appropriate.
Multi-factor authentication
Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
Multi-factor or continuous authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. where appropriate, in line with the classification of the asset accessed.
Cryptography and encryption
Only NIS2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.8.24
Nothing in the acts covered.
Cryptography
Policies and procedures on the use of cryptographyThe use of mathematical methods to protect information and provide evidence that it can be trusted. Cryptography can hide information, detect changes and help verify where information came from. Encryption, which makes readable information unintelligible without the means to decrypt it, is one use of cryptography. The broader discipline also supports integrity checks and digital signatures. and, where appropriate, encryptionEncryption changes readable information into an unreadable form using a mathematical method and a key, a value that controls the transformation. Decryption recovers the original information with the appropriate key. Encryption helps keep stored or transmitted data confidential, so people without the necessary key cannot readily read it..
Network security
Only NIS2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.8.20 to A.8.22
Nothing in the acts covered.
Network security and segmentation
Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
Network security measures, and systems segmented into networks or zones by risk and from third parties' systems.
Secure communications
Only NIS2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.14
Nothing in the acts covered.
Secured communications
Secured voice, video and text communications and secured emergency communication systems within the entity, where appropriate.
Secure acquisition and development
Only NIS2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.PS · ISO/IEC 27001:2022 A.8.25 to A.8.31
Nothing in the acts covered.
Secure acquisition, development and maintenance
Security in the acquisition, development and maintenance of network and information systems, including vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. handling and disclosure.
Configuration, change and patch management
Only NIS2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.PS · ISO/IEC 27001:2022 A.8.9, A.8.19, A.8.32
Nothing in the acts covered.
Configuration, change and patch management
Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
Secure configurations, controlled changes, repairs and maintenance, and security patches applied within a reasonable time after release, unless the disadvantages outweigh the cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. benefits and the reasons are documented.
NIS2 Implementing Regulation, Annex, points 6.3, 6.4 and 6.6
Vulnerability handling
Only NIS2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.8.8
Nothing in the acts covered.
Secure acquisition, development and maintenance
Security in the acquisition, development and maintenance of network and information systems, including vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. handling and disclosure.
Human resources security
Both cover it read the wording below
NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.6.1 to A.6.6
Employee security management
Ensure adequate employee security management, considering categories of personnel in critical functions, access rights to premises, critical infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk. and sensitive information, background check procedures under Article 14 and the categories of people who must undergo them, and training and qualification requirements. Include the personnel of external service providers when setting the categories of personnel in critical functions.
Request background checks where permitted Optional
Under conditions set by the Member State and in duly reasoned cases, the entity may request background checks on people in sensitive roles, people with direct or remote access to its premises, information or control systems, and candidates for those positions.
Limits and content of background checks
Applies to: Member States
Checks are proportionate, strictly limited to what is necessary and carried out only to evaluate a potential security risk to the entity. At a minimum they confirm the person's identity and check criminal records for offences relevant to the position. Central authorities answer requests for criminal records held in other Member States within 10 working days.
Human resources security
Human resources security.
Background verification
Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
Background checks on employees, and where applicable on direct suppliers and service providers, to the extent feasible and where the role needs it.
Physical and environmental security
Both cover it read the wording below
NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.7.1 to A.7.14
Physical protection of premises and infrastructure
Ensure adequate physical protection of premises and critical infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk., considering for example fencing, barriers, perimeter monitoring, detection equipment and access controlsAccess Control.
All-hazards approach
The measures follow an all-hazards approach that aims to protect network and information systems and their physical environment from incidents.
Physical and environmental security
Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
Supporting utilities, protection against physical and environmental threats, and perimeter and physical access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements..
Detection and response
Monitoring and detection
Only NIS2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 DE.CM, DE.AE · ISO/IEC 27001:2022 A.8.15, A.8.16
Nothing in the acts covered.
Monitoring and logging
Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
Monitoring and logging of network and information systems to detect events that could be incidents.
Incident handling
Both cover it read the wording below
NIST CSF 2.0 RS.MA, RS.AN, RS.MI · ISO/IEC 27001:2022 A.5.24 to A.5.28
Respond to and mitigate incidents
Respond to, resist and mitigate the consequences of incidents, considering risk and crisis management procedures, protocols and alert routines.
Incident handling
Procedures to handle incidents.
Incident classification
NIS2 more detailed more requirements on this, not necessarily stricter
NIST CSF 2.0 RS.MA · ISO/IEC 27001:2022 A.5.25
Judging the significance of a disruption
Determine significance by taking into account in particular the number and proportion of users affected, the duration of the disruption, and the geographical area affected, including whether it is geographically isolated.
When an incident is significant
An incident is significant when it has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to others.
Event assessment and classification
Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
Suspicious events are assessed to decide whether they are incidents and, if so, their nature and severity. Recurring incidents under Article 4 are checked quarterly.
When an incident is significant
Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
Criteria that make an incident significant: general criteria for all these providers (Article 3), recurring incidents (Article 4) and criteria for each kind of provider (Articles 5 to 14).
Reporting to authorities
Both cover it read the wording below
NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5
Initial incident notification
Notify the competent authority without undue delay of incidents that significantly disrupt, or could significantly disrupt, the provision of essential services. Send the initial notification within 24 hours of becoming aware of the incident, unless operationally unable to do so.
Detailed incident report
Where relevant, follow the initial notification with a detailed report within one month.
Content of the notification
Include any available information that lets the competent authority understand the nature, cause and possible consequences of the incident, including any cross-border impact. Notifying does not expose the entity to increased liability.
Notify significant incidents
Notify the CSIRTComputer Security Incident Response Team or competent authority without undue delay of any significant incidentUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident., with the information needed to judge any cross-border impact.
Early warning
An early warning, saying where applicable whether the incident is suspected to be caused by unlawful or malicious acts or could have a cross-border impact.
Incident notification
An incident notification updating the early warning with an initial assessment of severity and impact and, where available, indicators of compromise.
Intermediate report
An intermediate report on status updates, when the CSIRTComputer Security Incident Response Team or authority asks for one.
Final report
A final report with a detailed description, the likely type of threat or root cause, the applied and ongoing mitigation and any cross-border impact. For an ongoing incident, a progress report at that time and the final report within one month of handling it.
Informing customers and the public
Both cover it read the wording below
NIST CSF 2.0 RS.CO, RC.CO
Follow-up to the entity and informing the public
Applies to: Competent authorities and Member States
After a notification, the competent authority gives the entity relevant follow-up information as soon as possible, including information that could support its response. Member States inform the public where they determine that this is in the public interest.
Inform affected recipients
Where appropriate, notify recipients of the services without undue delay of significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. likely to affect the provision of those services.
Warn of significant cyber threats
Where applicable, tell recipients potentially affected by a significant cyber threatA cyber threat whose technical characteristics suggest it could have a severe impact on an organisation's systems or on the users of its services. NIS2 links the impact to considerable material or non-material damage; DORA links it to a possible major ICT-related incident., without undue delay, what they can do about it and, where appropriate, about the threat itself.
Threat intelligence and information sharing
CER asks more binding, where the other is optional
NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.5.6, A.5.7
Follow-up to the entity and informing the public
Applies to: Competent authorities and Member States
After a notification, the competent authority gives the entity relevant follow-up information as soon as possible, including information that could support its response. Member States inform the public where they determine that this is in the public interest.
Information-sharing arrangements Optional
Entities may exchange cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. information such as threats, vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. and indicators of compromise within information-sharing arrangements. Essential and important entitiesAn organisation in an Annex I or Annex II sector of NIS2 that falls within scope but does not qualify as an essential entity, typically a medium-sized or large company. Important entities have the same risk management and reporting duties, but supervision is mainly reactive, after evidence of non-compliance. notify the competent authority when they join or withdraw.
Continuity and resilience
Business continuity and crisis management
CER more detailed more requirements on this, not necessarily stricter
NIST CSF 2.0 RC.RP, RC.CO · ISO/IEC 27001:2022 A.5.29, A.5.30
Respond to and mitigate incidents
Respond to, resist and mitigate the consequences of incidents, considering risk and crisis management procedures, protocols and alert routines.
Recover and resume the essential service
Recover from incidents and resume the essential serviceIn the EU Critical Entities Resilience Directive, a service needed to keep society's vital functions, economic activity, public health and safety or the environment functioning. Examples include services in energy, transport, health and drinking water. The concept concerns the service people depend on. National authorities identify the critical entities that provide such services. The Directive requires reporting of incidents that significantly disrupt or could significantly disrupt essential services, with details implemented through national requirements., considering business continuityAn organisation's ability to keep delivering its products and services at an acceptable, previously agreed level during a disruption. The focus is on sustaining the activities customers and others depend on, even when normal operations are interrupted. A business continuity management system helps an organisation develop and maintain that capability; a business continuity plan records the arrangements for putting it into practice. measures and alternative supply chains.
Resilience plan
Have in place and apply a resilience plan or equivalent documents that describe the measures taken. Documents and measures produced under other legal acts may be reused where relevant, and the competent authority may declare them compliant in whole or in part.
Business continuity and crisis management
Business continuityAn organisation's ability to keep delivering its products and services at an acceptable, previously agreed level during a disruption. The focus is on sustaining the activities customers and others depend on, even when normal operations are interrupted. A business continuity management system helps an organisation develop and maintain that capability; a business continuity plan records the arrangements for putting it into practice., such as backupA backup is a copy of files, programs or other information kept so they can be recovered when needed. If original records are lost, damaged or unavailable, a usable backup provides a source for restoring them. Backups can support recovery of business systems and health records. management and disaster recoveryThe organised work of restoring IT systems and recovering information after a serious disruption, so the organisation can resume operations. It includes deciding which systems matter most, preparing backups and recovery resources, assigning responsibilities, and testing the recovery procedures. A disaster recovery environment is the technical set-up used for this restoration. A disaster recovery plan records how the work will be carried out., and crisis management.
Backup and recovery
Only NIS2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.DS, RC.RP · ISO/IEC 27001:2022 A.8.13, A.8.14
Nothing in the acts covered.
Business continuity and crisis management
Business continuityAn organisation's ability to keep delivering its products and services at an acceptable, previously agreed level during a disruption. The focus is on sustaining the activities customers and others depend on, even when normal operations are interrupted. A business continuity management system helps an organisation develop and maintain that capability; a business continuity plan records the arrangements for putting it into practice., such as backupA backup is a copy of files, programs or other information kept so they can be recovered when needed. If original records are lost, damaged or unavailable, a usable backup provides a source for restoring them. Backups can support recovery of business systems and health records. management and disaster recoveryThe organised work of restoring IT systems and recovering information after a serious disruption, so the organisation can resume operations. It includes deciding which systems matter most, preparing backups and recovery resources, assigning responsibilities, and testing the recovery procedures. A disaster recovery environment is the technical set-up used for this restoration. A disaster recovery plan records how the work will be carried out., and crisis management.
Backup and redundancy
Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
BackupA backup is a copy of files, programs or other information kept so they can be recovered when needed. If original records are lost, damaged or unavailable, a usable backup provides a source for restoring them. Backups can support recovery of business systems and health records. copies and sufficient redundancy, with regular integrity checks on the copies and regular testing of recovery of copies and redundancies.
Security testing
Only NIS2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 ID.IM · ISO/IEC 27001:2022 A.5.35, A.8.29, A.8.34
Nothing in the acts covered.
Security testing
Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
A policy and procedures for security testing of network and information systems.
Third parties and supply chain
Supplier and third-party risk
Both cover it read the wording below
NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.19, A.5.21 to A.5.23
All-hazards scope and dependencies
Cover all relevant natural and man-made risks, including cross-sectoral and cross-border risks, accidents, natural disasters, public health emergencies, hybrid threats and other antagonistic threats such as terrorist offences. Take into account how other sectors depend on the entity and how it depends on other sectors, including, where relevant, in neighbouring Member States and third countries. Relevant assessments made under other legal acts may be reused, and the competent authority may declare them compliant in whole or in part.
Recover and resume the essential service
Recover from incidents and resume the essential serviceIn the EU Critical Entities Resilience Directive, a service needed to keep society's vital functions, economic activity, public health and safety or the environment functioning. Examples include services in energy, transport, health and drinking water. The concept concerns the service people depend on. National authorities identify the critical entities that provide such services. The Directive requires reporting of incidents that significantly disrupt or could significantly disrupt essential services, with details implemented through national requirements., considering business continuityAn organisation's ability to keep delivering its products and services at an acceptable, previously agreed level during a disruption. The focus is on sustaining the activities customers and others depend on, even when normal operations are interrupted. A business continuity management system helps an organisation develop and maintain that capability; a business continuity plan records the arrangements for putting it into practice. measures and alternative supply chains.
Employee security management
Ensure adequate employee security management, considering categories of personnel in critical functions, access rights to premises, critical infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk. and sensitive information, background check procedures under Article 14 and the categories of people who must undergo them, and training and qualification requirements. Include the personnel of external service providers when setting the categories of personnel in critical functions.
Supply chain security
Supply chain security, including the security aspects of the relationship with each direct supplier and service provider.
What to weigh for each supplier and service provider
Entities weigh the specific vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. of each direct supplier and service provider, the quality of their products and cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. practices, including secure development, and the results of EU coordinated risk assessmentsRisk Assessment of critical supply chains.
Register of third-party arrangements
Only NIS2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 GV.SC
Nothing in the acts covered.
Directory of suppliers
Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
A directory of direct suppliers and service providers, kept up to date.
Supervision and enforcement
Registration with authorities
CER more detailed more requirements on this, not necessarily stricter
Identification of critical entities
Applies to: Member States
Each Member State identifies the critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. in the sectors and subsectors of the Annex by 17 July 2026 and reviews the list at least every four years. An entity qualifies when it provides an essential service, operates on that territory with its critical infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk. located there, and an incident would significantly disrupt that service or a dependent one.
Notification and start of obligations
Applies to: Member States
The Member State notifies each critical entityA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. within one month of identifying it and tells it which obligations apply and from when. The resilience obligations in Chapter III apply to the entity from 10 months after the date of that notification.
Carve-out for banking, financial market and digital infrastructure
Applies to: Member States, for critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. in banking, financial market infrastructure and digital infrastructure
Article 11 and Chapters III, IV and VI do not apply to critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. identified in banking, financial market infrastructure and digital infrastructure (points 3, 4 and 8 of the Annex). Member States may keep or adopt national requirements for a higher level of resilience if they are consistent with Union law.
Report services in six or more Member States
After being notified as a critical entityA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities., tell the competent authority if the entity provides essential services to or in six or more Member States, which services these are and in which Member States.
Register with the authority
Submit to the competent authority the entity's name, address, contact details including IP ranges and, where applicable, its sector and the Member States where it provides services. Report changes without delay and within two weeks.
Registry of digital providers
DNSDomain Name System, TLDTop-Level Domain, domain name registration, cloud, data centre, content delivery, managed (security) service providers, marketplaces, search engines and social networks submit their details to the competent authority by 17 January 2025 for the ENISAEuropean Union Agency for Cybersecurity registry, and report changes without delay and within three months. The authority is that of their main establishment or EU representative (Article 26).
Cooperation with supervisors
Only CER no specific requirement on the other side in the acts covered
Liaison officer
Designate a liaison officer or equivalent as the point of contact with the competent authorities.
Report services in six or more Member States
After being notified as a critical entityA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities., tell the competent authority if the entity provides essential services to or in six or more Member States, which services these are and in which Member States.
Inspections, audits and remedial orders
Applies to: Competent authorities
Competent authorities can inspect critical infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk. and premises on site, supervise Article 13 measures off site, and conduct or order audits of critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities.. They may order an entity to remedy an infringement within a reasonable time limit and to report the measures taken.
Provide information and audit evidence
Applies to: Critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. that are also entities under Directive (EU) 2022/2555
Where the competent authority requires it, and within the reasonable time limit it sets, provide the information needed to assess the Article 13 measures and evidence that they are effectively implemented. The evidence includes the results of an audit by an independent and qualified auditor, chosen by the entity and paid for by it.
Nothing in the acts covered.
Penalties and liability
Both cover it read the wording below
Penalties
Applies to: Member States
Member States lay down the penalties for infringements of the national measures and take the steps needed to implement them. The penalties are effective, proportionate and dissuasive. Member States notify the Commission of these provisions by 17 October 2024 and of any later change without delay.
Management approves and oversees the measures
The management body approves the cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk-management measures, oversees their implementation and can be held liable for infringements of Article 21 by the entity. National liability requirements for public institutions and officials are unaffected.
Administrative fines
Infringements of Article 21 or 23 can be fined. Member States set maximums of at least the amounts below, whichever is higher.
Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022.
More Comparisons
Subject to more than one?
We run one control set for both, without doing the work twice. Ask what that saves you.