> CER vs NIS2 Poland side by side, topic by topic: where they overlap, where they differ and which asks more, with incident deadlines, testing, third parties and fines.

# CER vs NIS2 Poland

Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.

[CER](https://grc.plus/regulation/critical-entities-resilience-directive-cer/)Critical entities identified by Member States

[NIS2 Poland](https://grc.plus/regulation/nis2/poland/)Essential and important entities

## At a Glance

They differ on 5 of 19 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 Poland** Asks more on 0 topics Alone on 0 topics More detailed on 1 topic

| Topic | CER | NIS2 Poland | Verdict |
| --- | --- | --- | --- |
| Governance |  |  |  |
| Roles and independence | CER: 1 | NIS2 Poland: 1 | **Both cover it**read the wording below |
| Security policy | CER: 1 | NIS2 Poland: 2 | **Both cover it**read the wording below |
| Awareness and training | CER: 1 | NIS2 Poland: 2 | **Both cover it**read the wording below |
| Risk management |  |  |  |
| Risk management framework | CER: 2 | NIS2 Poland: 3 | **Both cover it**read the wording below |
| Risk assessment | CER: 2 | NIS2 Poland: 2 | **Both cover it**read the wording below |
| Review, audit and improvement | CER: 2 | NIS2 Poland: 3 | **Both cover it**read the wording below |
| Protection |  |  |  |
| Access control | CER: 1 | NIS2 Poland: 2 | **Both cover it**read the wording below |
| Human resources security | CER: 3 | NIS2 Poland: 2 | **Both cover it**read the wording below |
| Physical and environmental security | CER: 1 | NIS2 Poland: 2 | **Both cover it**read the wording below |
| Detection and response |  |  |  |
| Incident handling | CER: 1 | NIS2 Poland: 1 | **Both cover it**read the wording below |
| Incident classification | CER: 1 | NIS2 Poland: 3 | **NIS2 Poland more detailed**more requirements on this, not necessarily stricter |
| Reporting to authorities | CER: 3 | NIS2 Poland: 5 | **Both cover it**read the wording below |
| Informing customers and the public | CER: 1 | NIS2 Poland: 2 | **Both cover it**read the wording below |
| Threat intelligence and information sharing | CER: 1 | NIS2 Poland: 1 | **CER asks more**binding, where the other is optional |
| Continuity and resilience |  |  |  |
| Business continuity and crisis management | CER: 3 | NIS2 Poland: 1 | **CER more detailed**more requirements on this, not necessarily stricter |
| Third parties and supply chain |  |  |  |
| Supplier and third-party risk | CER: 3 | NIS2 Poland: 2 | **Both cover it**read the wording below |
| Supervision and enforcement |  |  |  |
| Registration with authorities | CER: 4 | NIS2 Poland: 2 | **CER more detailed**more requirements on this, not necessarily stricter |
| Cooperation with supervisors | CER: 4 | NIS2 Poland: – | **Only CER**no specific requirement on the other side in the acts covered |
| Penalties and liability | CER: 1 | NIS2 Poland: 2 | **Both cover it**read 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](https://grc.plus/regulation/critical-entities-resilience-directive-cer/) Directive (EU) 2022/2557 of the European Parliament and of the Council of 14 December 2022 Articles 6, 8, 12 to 17, 21, 22 · 29 requirements

Status

Reviewed against the official texts.

Included

- [NIS2](https://grc.plus/regulation/nis2/) Directive (EU) 2022/2555 Articles 3, 20, 21, 23, 27, 29, 34 · 31 requirements
- [NIS2 Implementing Regulation](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/) Commission Implementing Regulation (EU) 2024/2690 Articles 3 to 14 · Annex · 17 requirements 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

National requirements

- [KSC](https://grc.plus/regulation/nis2/poland/) Article 11

2 national requirements recorded, as departures from the Directive or additions to it. Everything else applies as the Directive has it.

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 Poland: 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 Poland: Not in the acts covered

### Threshold

CER: Actual or potential significant disruption of essential services; Essential services to or in six or more Member States

NIS2 Poland: Not in the acts covered

### Goes to

CER: Competent authority

NIS2 Poland: Not in the acts covered

### Evidence to keep

CER: Resilience plan or equivalent documents; Information and evidence on the Article 13 measures (Critical entities that are also entities under Directive (EU) 2022/2555)

NIS2 Poland: Not in the acts covered

### Incident reports go to

CER: Competent authority

NIS2 Poland: CSIRT or competent authority

### First notice of an incident

CER: Within 24 hours of becoming aware

NIS2 Poland: Immediately and no later than 24 hours after detecting the serious incident

### Incident notification

CER: Not in the acts covered

NIS2 Poland: Immediately and no later than 72 hours after detecting the serious incident (24 hours for trust service providers)

### Intermediate report

CER: Not in the acts covered

NIS2 Poland: On request

### Final report

CER: Within one month of the initial notification, where relevant

NIS2 Poland: 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 Poland: Not in the acts covered

### External assessment or certification

CER: Audit by an independent and qualified auditor, where the authority requires evidence (Critical entities that are also entities under Directive (EU) 2022/2555)

NIS2 Poland: Not in the acts covered

### Review of the risk framework

CER: Not in the acts covered

NIS2 Poland: Risk assessment and treatment plan at planned intervals, at least annually, and after significant incidents 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 Poland: 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 Poland: Required; changes without delay and in any event within two weeks

### Management body training

CER: Not in the acts covered

NIS2 Poland: Required

### Management body liability

CER: Not in the acts covered

NIS2 Poland: Yes, for infringements of Article 21

### Maximum fines

CER: Set by each Member State; effective, proportionate and dissuasive (Member States)

NIS2 Poland: Essential 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 entities: maximum of at least EUR 7 million or 1.4%, whichever is higher.

## Governance

### 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.
  [CER, Article 13(3)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

- 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 incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 1.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive

### 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.
  [CER, Article 13(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

- Risk analysis and security policies
  Policies on risk analysis and on information system security.
  [NIS2, Article 21(2)(a)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- 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 incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 1.1](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive

### 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.
  [CER, Article 13(1)(f)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

- Management body training
  Members of the management body follow training to identify risks and assess cybersecurity risk-management practices. Entities are encouraged to offer similar training to employees regularly.
  [NIS2, Article 20(2)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Cyber hygiene and training
  Basic cyber hygiene practices and cybersecurity training.
  [NIS2, Article 21(2)(g)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive

## 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 assessment and the entity's own. The measures include preventing incidents, with due regard to disaster risk reduction and climate adaptation.
  [CER, Article 13(1), opening words and point (a)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- 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 entities. The article places no duty on the entity itself to use them.
  [CER, Article 16](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

- 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.
  [NIS2, Article 21(1)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- All-hazards approach
  The measures follow an all-hazards approach that aims to protect network and information systems and their physical environment from incidents.
  [NIS2, Article 21(2)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- 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 incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 2.1](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive

### 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 entity, 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 assessments and other relevant sources of information.
  [CER, Article 12(1)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- 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.
  [CER, Article 12(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

- Risk analysis and security policies
  Policies on risk analysis and on information system security.
  [NIS2, Article 21(2)(a)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- 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 incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 2.1](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive

### 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 infrastructure and premises on site, supervise Article 13 measures off site, and conduct or order audits of critical entities. They may order an entity to remedy an infringement within a reasonable time limit and to report the measures taken.
  [CER, Article 21(1) and (3)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Provide information and audit evidence
  Applies to: Critical 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.
  [CER, Article 21(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

- Assessing effectiveness
  Policies and procedures to assess whether the cybersecurity risk-management measures work.
  [NIS2, Article 21(2)(f)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Corrective measures
  An entity that finds it does not comply with the measures takes the necessary corrective measures without undue delay.
  [NIS2, Article 21(4)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- 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 security at planned intervals and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 2.3](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive

## 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 infrastructure 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.
  [CER, Article 13(1)(e) and second subparagraph](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

- Access control policies
  Access control policies.
  [NIS2, Article 21(2)(i)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- 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.
  [NIS2 Implementing Regulation, Annex, points 11.2 and 11.3](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive

### 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 infrastructure 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.
  [CER, Article 13(1)(e) and second subparagraph](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- 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.
  [CER, Article 14(1)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- 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.
  [CER, Article 14(2) and (3)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

- Human resources security
  Human resources security.
  [NIS2, Article 21(2)(i)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- 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.
  [NIS2 Implementing Regulation, Annex, point 10.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive

### 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 infrastructure, considering for example fencing, barriers, perimeter monitoring, detection equipment and access controls.
  [CER, Article 13(1)(b)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

- All-hazards approach
  The measures follow an all-hazards approach that aims to protect network and information systems and their physical environment from incidents.
  [NIS2, Article 21(2)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- 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 control.
  [NIS2 Implementing Regulation, Annex, points 13.1 to 13.3](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive

## Detection and response

### 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.
  [CER, Article 13(1)(c)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

- Incident handling
  Procedures to handle incidents.
  [NIS2, Article 21(2)(b)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive

### Incident classification

**NIS2 Poland 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.
  [CER, Article 15(1)(a) to (c)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

- 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.
  [NIS2, Article 23(3)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- 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.
  [NIS2 Implementing Regulation, Annex, point 3.4](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive
- 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).
  [NIS2 Implementing Regulation, Articles 3 to 14](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive

### 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.
  [CER, Article 15(1), first subparagraph](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Detailed incident report
  Where relevant, follow the initial notification with a detailed report within one month.
  [CER, Article 15(1), first subparagraph](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- 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.
  [CER, Article 15(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

- Notify significant incidents
  Notify the CSIRT or competent authority without undue delay of any significant incident, with the information needed to judge any cross-border impact.
  [NIS2, Article 23(1)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Early warning from detection Differs
  The early warning is due immediately and no later than 24 hours after detecting the serious incident, not after becoming aware of it.
  [NIS2 Poland, Article 11(1)(4)](https://grc.plus/regulation/nis2/poland/#requirements)
- Incident notification from detection Differs
  The incident notification is due immediately and no later than 72 hours after detecting the serious incident; trust service providers notify within 24 hours.
  [NIS2 Poland, Article 11(1)(4a) and 11(1a)](https://grc.plus/regulation/nis2/poland/#requirements)
- Intermediate report
  An intermediate report on status updates, when the CSIRT or authority asks for one.
  [NIS2, Article 23(4)(c)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- 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.
  [NIS2, Article 23(4)(d) and (e)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive

### 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.
  [CER, Article 15(4)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

- Inform affected recipients
  Where appropriate, notify recipients of the services without undue delay of significant incidents likely to affect the provision of those services.
  [NIS2, Article 23(1)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Warn of significant cyber threats
  Where applicable, tell recipients potentially affected by a significant cyber threat, without undue delay, what they can do about it and, where appropriate, about the threat itself.
  [NIS2, Article 23(2)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive

### 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.
  [CER, Article 15(4)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

- Information-sharing arrangements Optional
  Entities may exchange cybersecurity information such as threats, vulnerabilities and indicators of compromise within information-sharing arrangements. Essential and important entities notify the competent authority when they join or withdraw.
  [NIS2, Article 29](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive

## 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.
  [CER, Article 13(1)(c)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Recover and resume the essential service
  Recover from incidents and resume the essential service, considering business continuity measures and alternative supply chains.
  [CER, Article 13(1)(d)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- 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.
  [CER, Article 13(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

- Business continuity and crisis management
  Business continuity, such as backup management and disaster recovery, and crisis management.
  [NIS2, Article 21(2)(c)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive

## 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.
  [CER, Article 12(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Recover and resume the essential service
  Recover from incidents and resume the essential service, considering business continuity measures and alternative supply chains.
  [CER, Article 13(1)(d)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Employee security management
  Ensure adequate employee security management, considering categories of personnel in critical functions, access rights to premises, critical infrastructure 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.
  [CER, Article 13(1)(e) and second subparagraph](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

- Supply chain security
  Supply chain security, including the security aspects of the relationship with each direct supplier and service provider.
  [NIS2, Article 21(2)(d)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- What to weigh for each supplier and service provider
  Entities weigh the specific vulnerabilities of each direct supplier and service provider, the quality of their products and cybersecurity practices, including secure development, and the results of EU coordinated risk assessments of critical supply chains.
  [NIS2, Article 21(3)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive

## 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 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 infrastructure located there, and an incident would significantly disrupt that service or a dependent one.
  [CER, Article 6(1), (2) and (5)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Notification and start of obligations
  Applies to: Member States
  The Member State notifies each critical entity 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.
  [CER, Article 6(3)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Carve-out for banking, financial market and digital infrastructure
  Applies to: Member States, for critical entities in banking, financial market infrastructure and digital infrastructure
  Article 11 and Chapters III, IV and VI do not apply to critical 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.
  [CER, Article 8](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Report services in six or more Member States
  After being notified as a critical entity, 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.
  [CER, Article 17(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

- 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.
  [NIS2, Article 3(4)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Registry of digital providers
  DNS, TLD, 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 ENISA registry, and report changes without delay and within three months. The authority is that of their main establishment or EU representative (Article 26).
  [NIS2, Article 27](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive

### 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.
  [CER, Article 13(3)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Report services in six or more Member States
  After being notified as a critical entity, 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.
  [CER, Article 17(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Inspections, audits and remedial orders
  Applies to: Competent authorities
  Competent authorities can inspect critical infrastructure and premises on site, supervise Article 13 measures off site, and conduct or order audits of critical entities. They may order an entity to remedy an infringement within a reasonable time limit and to report the measures taken.
  [CER, Article 21(1) and (3)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Provide information and audit evidence
  Applies to: Critical 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.
  [CER, Article 21(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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.
  [CER, Article 22](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

- Management approves and oversees the measures
  The management body approves the cybersecurity 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.
  [NIS2, Article 20(1)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Administrative fines
  Infringements of Article 21 or 23 can be fined. Member States set maximums of at least the amounts below, whichever is higher.
  [NIS2, Article 34(4) and (5)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive

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. 13 topics where all apply the Directive as it is are not shown.

## More Comparisons

- [Compare CER](https://grc.plus/compare/cer/)
- [Compare NIS2 Poland](https://grc.plus/compare/nis2-poland/)

Source: https://grc.plus/compare/cer-vs-nis2-poland/
