> CER vs PCI DSS 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 PCI DSS

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

[PCI DSS](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/)Entities that store, process or transmit account data, or can affect its security

## At a Glance

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

- **CER** Asks more on 0 topics Alone on 11 topics More detailed on 1 topic
- **PCI DSS** Asks more on 0 topics Alone on 12 topics More detailed on 2 topics

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

- [PCI DSS](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/) PCI DSS v4.0.1 (June 2024) 63 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)

PCI DSS: 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

PCI DSS: 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

PCI DSS: Not in the acts covered

### Goes to

CER: Competent authority

PCI DSS: 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)

PCI DSS: Not in the acts covered

### Incident reports go to

CER: Competent authority

PCI DSS: Not in the acts covered

### First notice of an incident

CER: Within 24 hours of becoming aware

PCI DSS: Not in the acts covered

### Final report

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

PCI DSS: Not in the acts covered

### Deadline to have the measures in place

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

PCI DSS: 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)

PCI DSS: Not in the acts covered

### Maximum fines

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

PCI DSS: Not in the acts covered

## Governance

### Management accountability

**Only PCI DSS** 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.

- PCI DSS compliance is managed
  PCI DSS compliance is managed.
  [PCI DSS, Requirement 12.4](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

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

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

- A comprehensive information security policy that governs and provides direction for protection of the entity's information assets is known and current
  A comprehensive information security policy that governs and provides direction for protection of the entity's information assets is known and current.
  [PCI DSS, Requirement 12.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Acceptable use policies for end-user technologies are defined and implemented
  Acceptable use policies for end-user technologies are defined and implemented.
  [PCI DSS, Requirement 12.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

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

- Anti-phishing mechanisms protect users against phishing attacks
  Anti-phishing mechanisms protect users against phishing attacks.
  [PCI DSS, Requirement 5.4](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Security awareness education is an ongoing activity
  Security awareness education is an ongoing activity.
  [PCI DSS, Requirement 12.6](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#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

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

- Risks to the cardholder data environment are formally identified, evaluated, and managed
  Risks to the cardholder data environment are formally identified, evaluated, and managed.
  [PCI DSS, Requirement 12.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#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.

### Asset management

**Only PCI DSS** 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.

- PCI DSS scope is documented and validated
  PCI DSS scope is documented and validated.
  [PCI DSS, Requirement 12.5](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

## Protection

### Access control

**PCI DSS more detailed** more requirements on this, not necessarily stricter

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)

- Processes and mechanisms for restricting access to system components and cardholder data by business need to know are defined and understood
  Processes and mechanisms for restricting access to system components and cardholder data by business need to know are defined and understood.
  [PCI DSS, Requirement 7.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Access to system components and data is appropriately defined and assigned
  Access to system components and data is appropriately defined and assigned.
  [PCI DSS, Requirement 7.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Access to system components and data is managed via an access control system(s)
  Access to system components and data is managed via an access control system(s).
  [PCI DSS, Requirement 7.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- User identification and related accounts for users and administrators are strictly managed throughout an account's lifecycle
  User identification and related accounts for users and administrators are strictly managed throughout an account's lifecycle.
  [PCI DSS, Requirement 8.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### Authentication

**Only PCI DSS** 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.

- Processes and mechanisms for identifying users and authenticating access to system components are defined and understood
  Processes and mechanisms for identifying users and authenticating access to system components are defined and understood.
  [PCI DSS, Requirement 8.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Strong authentication for users and administrators is established and managed
  Strong authentication for users and administrators is established and managed.
  [PCI DSS, Requirement 8.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Multi-factor authentication (MFA) is implemented to secure access into the CDE
  Multi-factor authentication (MFA) is implemented to secure access into the CDE.
  [PCI DSS, Requirement 8.4](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Multi-factor authentication (MFA) systems are configured to prevent misuse
  Multi-factor authentication (MFA) systems are configured to prevent misuse.
  [PCI DSS, Requirement 8.5](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Use of application and system accounts and associated authentication factors is strictly managed
  Use of application and system accounts and associated authentication factors is strictly managed.
  [PCI DSS, Requirement 8.6](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### Cryptography and encryption

**Only PCI DSS** 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.

- Primary account number (PAN) is secured wherever it is stored
  Primary account number (PAN) is secured wherever it is stored.
  [PCI DSS, Requirement 3.5](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Cryptographic keys used to protect stored account data are secured
  Cryptographic keys used to protect stored account data are secured.
  [PCI DSS, Requirement 3.6](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented
  Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented.
  [PCI DSS, Requirement 3.7](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### Data security

**Only PCI DSS** 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.

- Processes and mechanisms for protecting stored account data are defined and understood
  Processes and mechanisms for protecting stored account data are defined and understood.
  [PCI DSS, Requirement 3.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Storage of account data is kept to a minimum
  Storage of account data is kept to a minimum.
  [PCI DSS, Requirement 3.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Sensitive authentication data (SAD) is not stored after authorization
  Sensitive authentication data (SAD) is not stored after authorization.
  [PCI DSS, Requirement 3.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Access to displays of full PAN and ability to copy PAN are restricted
  Access to displays of full PAN and ability to copy PAN are restricted.
  [PCI DSS, Requirement 3.4](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### Network security

**Only PCI DSS** 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.

- Processes and mechanisms for installing and maintaining network security controls are defined and understood
  Processes and mechanisms for installing and maintaining network security controls are defined and understood.
  [PCI DSS, Requirement 1.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Network security controls (NSCs) are configured and maintained
  Network security controls (NSCs) are configured and maintained.
  [PCI DSS, Requirement 1.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Network access to and from the cardholder data environment is restricted
  Network access to and from the cardholder data environment is restricted.
  [PCI DSS, Requirement 1.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Network connections between trusted and untrusted networks are controlled
  Network connections between trusted and untrusted networks are controlled.
  [PCI DSS, Requirement 1.4](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Risks to the CDE from computing devices that are able to connect to both untrusted networks and the CDE are mitigated
  Risks to the CDE from computing devices that are able to connect to both untrusted networks and the CDE are mitigated.
  [PCI DSS, Requirement 1.5](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Wireless environments are configured and managed securely
  Wireless environments are configured and managed securely.
  [PCI DSS, Requirement 2.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Wireless access points are identified and monitored, and unauthorized wireless access points are addressed
  Wireless access points are identified and monitored, and unauthorized wireless access points are addressed.
  [PCI DSS, Requirement 11.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### Secure communications

**Only PCI DSS** 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.

- Processes and mechanisms for protecting cardholder data with strong cryptography during transmission over open, public networks are defined and understood
  Processes and mechanisms for protecting cardholder data with strong cryptography during transmission over open, public networks are defined and understood.
  [PCI DSS, Requirement 4.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- PAN is protected with strong cryptography during transmission
  PAN is protected with strong cryptography during transmission.
  [PCI DSS, Requirement 4.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### Secure acquisition and development

**Only PCI DSS** 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.

- Processes and mechanisms for developing and maintaining secure systems and software are defined and understood
  Processes and mechanisms for developing and maintaining secure systems and software are defined and understood.
  [PCI DSS, Requirement 6.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Bespoke and custom software are developed securely
  Bespoke and custom software are developed securely.
  [PCI DSS, Requirement 6.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Public-facing web applications are protected against attacks
  Public-facing web applications are protected against attacks.
  [PCI DSS, Requirement 6.4](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### Configuration, change and patch management

**Only PCI DSS** 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.

- Changes to all system components are managed securely
  Changes to all system components are managed securely.
  [PCI DSS, Requirement 6.5](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### Vulnerability handling

**Only PCI DSS** 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.

- Processes and mechanisms for applying secure configurations to all system components are defined and understood
  Processes and mechanisms for applying secure configurations to all system components are defined and understood.
  [PCI DSS, Requirement 2.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- System components are configured and managed securely
  System components are configured and managed securely.
  [PCI DSS, Requirement 2.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Security vulnerabilities are identified and addressed
  Security vulnerabilities are identified and addressed.
  [PCI DSS, Requirement 6.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- External and internal vulnerabilities are regularly identified, prioritized, and addressed
  External and internal vulnerabilities are regularly identified, prioritized, and addressed.
  [PCI DSS, Requirement 11.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### Human resources security

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

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)

- Personnel are screened to reduce risks from insider threats
  Personnel are screened to reduce risks from insider threats.
  [PCI DSS, Requirement 12.7](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### Physical and environmental security

**PCI DSS more detailed** more requirements on this, not necessarily stricter

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)

- Processes and mechanisms for restricting physical access to cardholder data are defined and understood
  Processes and mechanisms for restricting physical access to cardholder data are defined and understood.
  [PCI DSS, Requirement 9.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Physical access controls manage entry into facilities and systems containing cardholder data
  Physical access controls manage entry into facilities and systems containing cardholder data.
  [PCI DSS, Requirement 9.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Physical access for personnel and visitors is authorized and managed
  Physical access for personnel and visitors is authorized and managed.
  [PCI DSS, Requirement 9.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Media with cardholder data is securely stored, accessed, distributed, and destroyed
  Media with cardholder data is securely stored, accessed, distributed, and destroyed.
  [PCI DSS, Requirement 9.4](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Point-of-interaction (POI) devices are protected from tampering and unauthorized substitution
  Point-of-interaction (POI) devices are protected from tampering and unauthorized substitution.
  [PCI DSS, Requirement 9.5](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

## Detection and response

### Monitoring and detection

**Only PCI DSS** 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.

- Processes and mechanisms for protecting all systems and networks from malicious software are defined and understood
  Processes and mechanisms for protecting all systems and networks from malicious software are defined and understood.
  [PCI DSS, Requirement 5.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Malicious software (malware) is prevented, or detected and addressed
  Malicious software (malware) is prevented, or detected and addressed.
  [PCI DSS, Requirement 5.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Anti-malware mechanisms and processes are active, maintained, and monitored
  Anti-malware mechanisms and processes are active, maintained, and monitored.
  [PCI DSS, Requirement 5.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Processes and mechanisms for logging and monitoring all access to system components and cardholder data are defined and understood
  Processes and mechanisms for logging and monitoring all access to system components and cardholder data are defined and understood.
  [PCI DSS, Requirement 10.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events
  Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
  [PCI DSS, Requirement 10.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Audit logs are protected from destruction and unauthorized modifications
  Audit logs are protected from destruction and unauthorized modifications.
  [PCI DSS, Requirement 10.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Audit logs are reviewed to identify anomalies or suspicious activity
  Audit logs are reviewed to identify anomalies or suspicious activity.
  [PCI DSS, Requirement 10.4](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Audit log history is retained and available for analysis
  Audit log history is retained and available for analysis.
  [PCI DSS, Requirement 10.5](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Time-synchronization mechanisms support consistent time settings across all systems
  Time-synchronization mechanisms support consistent time settings across all systems.
  [PCI DSS, Requirement 10.6](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Failures of critical security control systems are detected, reported, and responded to promptly
  Failures of critical security control systems are detected, reported, and responded to promptly.
  [PCI DSS, Requirement 10.7](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Network intrusions and unexpected file changes are detected and responded to
  Network intrusions and unexpected file changes are detected and responded to.
  [PCI DSS, Requirement 11.5](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Unauthorized changes on payment pages are detected and responded to
  Unauthorized changes on payment pages are detected and responded to.
  [PCI DSS, Requirement 11.6](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#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)

- Suspected and confirmed security incidents that could impact the CDE are responded to immediately
  Suspected and confirmed security incidents that could impact the CDE are responded to immediately.
  [PCI DSS, Requirement 12.10](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#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 PCI DSS** 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.

- Processes and mechanisms for regularly testing security of systems and networks are defined and understood
  Processes and mechanisms for regularly testing security of systems and networks are defined and understood.
  [PCI DSS, Requirement 11.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- External and internal penetration testing is regularly performed, and exploitable vulnerabilities and security weaknesses are corrected
  External and internal penetration testing is regularly performed, and exploitable vulnerabilities and security weaknesses are corrected.
  [PCI DSS, Requirement 11.4](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

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

- Risk to information assets associated with third-party service provider (TPSP) relationships is managed
  Risk to information assets associated with third-party service provider (TPSP) relationships is managed.
  [PCI DSS, Requirement 12.8](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Third-party service providers (TPSPs) support their customers' PCI DSS compliance
  Third-party service providers (TPSPs) support their customers' PCI DSS compliance.
  [PCI DSS, Requirement 12.9](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#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 PCI DSS](https://grc.plus/compare/pci-dss/)

Source: https://grc.plus/compare/cer-vs-pci-dss/
