> CER vs Swift CSP 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 Swift CSP

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

[Swift CSP](https://grc.plus/regulation/swift-customer-security-program-swift-csp/)Swift users, for their architecture type

## At a Glance

They differ on 23 of 27 topics. Each verdict names what it rests on; read the wording before relying on it.

- **CER** Asks more on 2 topics Alone on 12 topics More detailed on 1 topic
- **Swift CSP** Asks more on 0 topics Alone on 8 topics More detailed on 0 topics

| Topic | CER | Swift CSP | Verdict |
| --- | --- | --- | --- |
| Governance |  |  |  |
| Roles and independence | CER: 1 | Swift CSP: – | **Only CER**no specific requirement on the other side in the acts covered |
| Security policy | CER: 1 | Swift CSP: – | **Only CER**no specific requirement on the other side in the acts covered |
| Awareness and training | CER: 1 | Swift CSP: 1 | **Both cover it**read the wording below |
| Risk management |  |  |  |
| Risk management framework | CER: 2 | Swift CSP: – | **Only CER**no specific requirement on the other side in the acts covered |
| Risk assessment | CER: 2 | Swift CSP: 1 | **CER asks more**binding, where the other is optional |
| Review, audit and improvement | CER: 2 | Swift CSP: – | **Only CER**no specific requirement on the other side in the acts covered |
| Protection |  |  |  |
| Access control | CER: 1 | Swift CSP: 2 | **Both cover it**read the wording below |
| Authentication | CER: – | Swift CSP: 4 | **Only Swift CSP**no specific requirement on the other side in the acts covered |
| Cryptography and encryption | CER: – | Swift CSP: 1 | **Only Swift CSP**no specific requirement on the other side in the acts covered |
| Data security | CER: – | Swift CSP: 4 | **Only Swift CSP**no specific requirement on the other side in the acts covered |
| Network security | CER: – | Swift CSP: 4 | **Only Swift CSP**no specific requirement on the other side in the acts covered |
| Secure communications | CER: – | Swift CSP: 3 | **Only Swift CSP**no specific requirement on the other side in the acts covered |
| Vulnerability handling | CER: – | Swift CSP: 4 | **Only Swift CSP**no specific requirement on the other side in the acts covered |
| Human resources security | CER: 3 | Swift CSP: 1 | **CER asks more**binding, where the other is optional |
| Physical and environmental security | CER: 1 | Swift CSP: 1 | **Both cover it**read the wording below |
| Detection and response |  |  |  |
| Monitoring and detection | CER: – | Swift CSP: 3 | **Only Swift CSP**no specific requirement on the other side in the acts covered |
| Incident handling | CER: 1 | Swift CSP: 1 | **Both cover it**read the wording below |
| Incident classification | CER: 1 | Swift CSP: – | **Only CER**no specific requirement on the other side in the acts covered |
| Reporting to authorities | CER: 3 | Swift CSP: – | **Only CER**no specific requirement on the other side in the acts covered |
| Informing customers and the public | CER: 1 | Swift CSP: – | **Only CER**no specific requirement on the other side in the acts covered |
| Threat intelligence and information sharing | CER: 1 | Swift CSP: – | **Only CER**no specific requirement on the other side in the acts covered |
| Continuity and resilience |  |  |  |
| Business continuity and crisis management | CER: 3 | Swift CSP: – | **Only CER**no specific requirement on the other side in the acts covered |
| Security testing | CER: – | Swift CSP: 1 | **Only Swift CSP**no specific requirement on the other side in the acts covered |
| Third parties and supply chain |  |  |  |
| Supplier and third-party risk | CER: 3 | Swift CSP: 1 | **CER more detailed**more requirements on this, not necessarily stricter |
| Supervision and enforcement |  |  |  |
| Registration with authorities | CER: 4 | Swift CSP: – | **Only CER**no specific requirement on the other side in the acts covered |
| Cooperation with supervisors | CER: 4 | Swift CSP: – | **Only CER**no specific requirement on the other side in the acts covered |
| Penalties and liability | CER: 1 | Swift CSP: – | **Only CER**no specific requirement on the other side in the acts covered |

## 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

- [Swift CSP](https://grc.plus/regulation/swift-customer-security-program-swift-csp/) Swift Customer Security Controls Framework v2026 (CSCF v2026) 32 requirements

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)

Swift CSP: 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

Swift CSP: 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

Swift CSP: Not in the acts covered

### Goes to

CER: Competent authority

Swift CSP: 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)

Swift CSP: Not in the acts covered

### Incident reports go to

CER: Competent authority

Swift CSP: Not in the acts covered

### First notice of an incident

CER: Within 24 hours of becoming aware

Swift CSP: Not in the acts covered

### Final report

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

Swift CSP: Not in the acts covered

### Deadline to have the measures in place

CER: 10 months after the date of the notification (Member States)

Swift CSP: 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)

Swift CSP: Not in the acts covered

### Maximum fines

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

Swift CSP: Not in the acts covered

## Governance

### Roles and independence

**Only CER** no specific requirement on the other side in the acts covered

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)

Nothing in the acts covered.

### Security policy

**Only CER** no specific requirement on the other side in the acts covered

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)

Nothing in the acts covered.

### 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)

- Security Training and Awareness
  Applies to: All types
  Train staff with access to Swift on security, including role-specific training for privileged users.
  [Swift CSP, Control 7.2](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

## Risk management

### Risk management framework

**Only CER** no specific requirement on the other side in the acts covered

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)

Nothing in the acts covered.

### Risk assessment

**CER asks more** binding, where the other is optional

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)

- Scenario-based Risk Assessment (advisory) Recommended
  Applies to: All types (advisory)
  Assess the risk of Swift-related attack scenarios regularly.
  [Swift CSP, Control 7.4A](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### Review, audit and improvement

**Only CER** no specific requirement on the other side in the acts covered

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)

Nothing in the acts covered.

## 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)

- Operating System Privileged Account Control
  Applies to: A1, A2, A3, A4; advisory for B
  Restrict and control the use of administrator accounts on the operating systems of in-scope components.
  [Swift CSP, Control 1.2](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Logical Access Control
  Applies to: All types
  Grant access on need-to-know, least privilege and segregation of duties, and review it regularly.
  [Swift CSP, Control 5.1](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### Authentication

**Only Swift CSP** 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.

- Password Policy
  Applies to: All types
  Make passwords resistant to common attacks through an enforced password policy.
  [Swift CSP, Control 4.1](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Multi-Factor Authentication
  Applies to: All types
  Require multi-factor authentication for interactive access to Swift-related applications and operating system administration.
  [Swift CSP, Control 4.2](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Token Management
  Applies to: All types
  Manage hardware authentication tokens and keep them under the control of their owners.
  [Swift CSP, Control 5.2](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Password Repository Protection
  Applies to: All types
  Protect stored passwords, physical and logical, against disclosure.
  [Swift CSP, Control 5.4](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### Cryptography and encryption

**Only Swift CSP** 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.

- External Transmission Data Protection (advisory) Recommended
  Applies to: A1, A2, A3, A4 (advisory)
  Protect Swift-related data sent or stored outside the secure zone, such as back-ups or files moved to other sites.
  [Swift CSP, Control 2.5A](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### Data security

**Only Swift CSP** no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.12, A.8.10 to A.8.12

Nothing in the acts covered.

- Transaction Business Controls
  Applies to: All types
  Restrict transaction activity to what is expected for your business, such as hours, counterparties and value limits, and detect deviations.
  [Swift CSP, Control 2.9](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- RMA Business Controls (advisory) Recommended
  Applies to: All types (advisory)
  Review Relationship Management Application relationships regularly and remove those no longer needed.
  [Swift CSP, Control 2.11A](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Software Integrity
  Applies to: A1, A2, A3; advisory for A4
  Check the integrity of the Swift-related software you run.
  [Swift CSP, Control 6.2](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Database Integrity
  Applies to: A1, A2; advisory for A4
  Check the integrity of the database records of the messaging interface.
  [Swift CSP, Control 6.3](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### Network security

**Only Swift CSP** 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.

- Swift Environment Protection
  Applies to: A1, A2, A3
  Place the Swift infrastructure in a secure zone, separated from the general IT environment, with controlled access into and out of it.
  [Swift CSP, Control 1.1](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Virtualisation or Cloud Platform Protection
  Applies to: A1, A2, A3, A4; advisory for B
  Secure the virtualisation or cloud platform that hosts in-scope components to the same level as the components themselves.
  [Swift CSP, Control 1.3](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Restriction of Internet Access
  Applies to: All types
  Limit internet access from operator PCs and in-scope systems to what is needed, and control it.
  [Swift CSP, Control 1.4](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Customer Environment Protection
  Applies to: A4
  For users with a customer connector, protect that environment in a dedicated, separated zone.
  [Swift CSP, Control 1.5](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### Secure communications

**Only Swift CSP** 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.

- Internal Data Flow Security
  Applies to: A1, A2, A3
  Protect the confidentiality, integrity and authenticity of data flows between Swift-related components.
  [Swift CSP, Control 2.1](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Back Office Data Flow Security
  Applies to: A1, A2, A3, A4
  Protect data flows between the back office and the secure zone, starting with bridging servers. Mandatory since v2026; legacy direct flows tentatively from 2028.
  [Swift CSP, Control 2.4](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Operator Session Confidentiality and Integrity
  Applies to: All types
  Protect interactive operator sessions to Swift-related applications against eavesdropping and tampering.
  [Swift CSP, Control 2.6](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### Vulnerability handling

**Only Swift CSP** 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.

- Security Updates
  Applies to: All types
  Install vendor security updates on in-scope hardware and software within a risk-based time frame.
  [Swift CSP, Control 2.2](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- System Hardening
  Applies to: All types
  Harden operating systems, databases and network devices of the Swift environment against attack.
  [Swift CSP, Control 2.3](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Vulnerability Scanning
  Applies to: A1, A2, A3, A4; advisory for B
  Scan in-scope components for vulnerabilities and act on the results.
  [Swift CSP, Control 2.7](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Application Hardening
  Applies to: A1, A2, A3
  Harden the Swift messaging and communication interfaces and related applications.
  [Swift CSP, Control 2.10](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### Human resources security

**CER asks more** binding, where the other is optional

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)

- Staff Screening Process (advisory) Recommended
  Applies to: All types (advisory)
  Screen staff who operate or administer the Swift environment before and during employment, where local law allows.
  [Swift CSP, Control 5.3A](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### 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)

- Physical Security
  Applies to: All types
  Prevent unauthorised physical access to sensitive equipment, workplaces, tokens and storage media.
  [Swift CSP, Control 3.1](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

## Detection and response

### Monitoring and detection

**Only Swift CSP** 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.

- Malware Protection
  Applies to: All types
  Protect in-scope components with up-to-date anti-malware.
  [Swift CSP, Control 6.1](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Logging and Monitoring
  Applies to: All types
  Record security events and monitor them to detect anomalous activity and operations.
  [Swift CSP, Control 6.4](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Intrusion Detection (advisory) Recommended
  Applies to: A1, A2, A3, A4 (advisory)
  Detect and contain anomalous network activity inside and towards the secure zone.
  [Swift CSP, Control 6.5A](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### 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)

- Cyber Incident Response Planning
  Applies to: All types
  Keep and test a cyber incident response plan that covers Swift, including informing Swift and using its threat intelligence.
  [Swift CSP, Control 7.1](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### Incident classification

**Only CER** no specific requirement on the other side in the acts covered

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)

Nothing in the acts covered.

### Reporting to authorities

**Only CER** no specific requirement on the other side in the acts covered

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)

Nothing in the acts covered.

### Informing customers and the public

**Only CER** no specific requirement on the other side in the acts covered

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)

Nothing in the acts covered.

### Threat intelligence and information sharing

**Only CER** no specific requirement on the other side in the acts covered

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)

Nothing in the acts covered.

## Continuity and resilience

### Business continuity and crisis management

**Only CER** no specific requirement on the other side in the acts covered

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)

Nothing in the acts covered.

### Security testing

**Only Swift CSP** 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.

- Penetration Testing (advisory) Recommended
  Applies to: All types (advisory)
  Test the security of the Swift environment through penetration tests.
  [Swift CSP, Control 7.3A](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

## Third parties and supply chain

### Supplier and third-party risk

**CER more detailed** more requirements on this, not necessarily stricter

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)

- Outsourced Critical Activity Protection
  Applies to: All types
  Ensure that critical activities outsourced to third parties are protected to the same standard.
  [Swift CSP, Control 2.8](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

## Supervision and enforcement

### Registration with authorities

**Only CER** no specific requirement on the other side in the acts covered

- 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)

Nothing in the acts covered.

### 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

**Only CER** no specific requirement on the other side in the acts covered

- 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)

Nothing in the acts covered.

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

- [Compare CER](https://grc.plus/compare/cer/)
- [Compare Swift CSP](https://grc.plus/compare/swift-csp/)

Source: https://grc.plus/compare/cer-vs-swift-csp/
