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.
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 DSSno specific requirement on the other side in the acts covered |
| Roles and independence | CER: 1 | PCI DSS: – | Only CERno specific requirement on the other side in the acts covered |
| Security policy | CER: 1 | PCI DSS: 2 | Both cover itread the wording below |
| Awareness and training | CER: 1 | PCI DSS: 2 | Both cover itread the wording below |
| Risk management | |||
| Risk management framework | CER: 2 | PCI DSS: – | Only CERno specific requirement on the other side in the acts covered |
| Risk assessment | CER: 2 | PCI DSS: 1 | Both cover itread the wording below |
| Review, audit and improvement | CER: 2 | PCI DSS: – | Only CERno specific requirement on the other side in the acts covered |
| Asset management | CER: – | PCI DSS: 1 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Protection | |||
| Access control | CER: 1 | PCI DSS: 4 | PCI DSS more detailedmore requirements on this, not necessarily stricter |
| Authentication | CER: – | PCI DSS: 5 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Cryptography and encryption | CER: – | PCI DSS: 3 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Data security | CER: – | PCI DSS: 4 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Network security | CER: – | PCI DSS: 7 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Secure communications | CER: – | PCI DSS: 2 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Secure acquisition and development | CER: – | PCI DSS: 3 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Configuration, change and patch management | CER: – | PCI DSS: 1 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Vulnerability handling | CER: – | PCI DSS: 4 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Human resources security | CER: 3 | PCI DSS: 1 | CER more detailedmore requirements on this, not necessarily stricter |
| Physical and environmental security | CER: 1 | PCI DSS: 5 | PCI DSS more detailedmore requirements on this, not necessarily stricter |
| Detection and response | |||
| Monitoring and detection | CER: – | PCI DSS: 12 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Incident handling | CER: 1 | PCI DSS: 1 | Both cover itread the wording below |
| Incident classification | CER: 1 | PCI DSS: – | Only CERno specific requirement on the other side in the acts covered |
| Reporting to authorities | CER: 3 | PCI DSS: – | Only CERno specific requirement on the other side in the acts covered |
| Informing customers and the public | CER: 1 | PCI DSS: – | Only CERno specific requirement on the other side in the acts covered |
| Threat intelligence and information sharing | CER: 1 | PCI DSS: – | Only CERno specific requirement on the other side in the acts covered |
| Continuity and resilience | |||
| Business continuity and crisis management | CER: 3 | PCI DSS: – | Only CERno specific requirement on the other side in the acts covered |
| Security testing | CER: – | PCI DSS: 2 | Only PCI DSSno 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 itread the wording below |
| Supervision and enforcement | |||
| Registration with authorities | CER: 4 | PCI DSS: – | Only CERno specific requirement on the other side in the acts covered |
| Cooperation with supervisors | CER: 4 | PCI DSS: – | Only CERno specific requirement on the other side in the acts covered |
| Penalties and liability | CER: 1 | PCI DSS: – | Only CERno 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.
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 servicesEssential Service; 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 planIn critical infrastructure regulation, a document explaining how an organisation will protect and maintain services that society depends on, and restore them after disruption. It connects identified risks with practical safeguards, responsibilities and arrangements for prevention, response and recovery. The required contents, approval process and use of equivalent existing documents depend on the applicable national law. or equivalent documents; Information and evidence on the Article 13 measures (Critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. that are also entities under Directive (EU) 2022/2555)
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 entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. that are also entities under Directive (EU) 2022/2555)
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 DSSPayment Card Industry Data Security Standard compliance is managed.
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.
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.
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 securityProtecting information and the systems that handle it so that only authorised people can access it, it remains accurate and complete, and it is available when needed. These aims are called confidentiality, integrity and availability. Information security combines organisational requirements, staff practices and technical safeguards to reduce risks such as disclosure, alteration, disruption or destruction. policy that governs and provides direction for protection of the entity's information assets is known and current.
Acceptable use policies for end-user technologies are defined and implemented
Acceptable use policies for end-user technologies are defined and implemented.
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.
Anti-phishing mechanisms protect users against phishing attacks
Anti-phishing mechanisms protect users against phishingAn attack that impersonates a trusted person or organisation through electronic communications, often an email or a fake website, to trick someone into revealing information such as passwords or bank details. The attacker uses apparent familiarity or credibility to persuade the person to respond. Training simulations practise recognising these deceptive requests. attacks.
Security awareness education is an ongoing activity
Security awareness education is an ongoing activity.
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 assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change. and the entity's own. The measures include preventing incidents, with due regard to disaster risk reduction and climate adaptation.
Encouraging standards
Applies to: Member States
Where useful, and without imposing or favouring a particular technology, Member States encourage the use of European and international standards and technical specifications relevant to the security and resilience measures of critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities.. The article places no duty on the entity itself to use them.
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 entityA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities., then whenever necessary and at least every four years. Assess all relevant risks that could disrupt the provision of the essential services, using the Member State risk assessmentsRisk Assessment and other relevant sources of information.
All-hazards scope and dependencies
Cover all relevant natural and man-made risks, including cross-sectoral and cross-border risks, accidents, natural disasters, public health emergencies, hybrid threats and other antagonistic threats such as terrorist offences. Take into account how other sectors depend on the entity and how it depends on other sectors, including, where relevant, in neighbouring Member States and third countries. Relevant assessments made under other legal acts may be reused, and the competent authority may declare them compliant in whole or in part.
Risks to the cardholder data environment are formally identified, evaluated, and managed
Risks to the cardholder data environmentThe system components, people and processes that store, process or transmit cardholder data or sensitive authentication data, plus components with unrestricted connectivity to them. Defining the CDE sets the scope of a PCI DSS assessment. are formally identified, evaluated, and managed.
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 infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk. and premises on site, supervise Article 13 measures off site, and conduct or order audits of critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities.. They may order an entity to remedy an infringement within a reasonable time limit and to report the measures taken.
Provide information and audit evidence
Applies to: Critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. that are also entities under Directive (EU) 2022/2555
Where the competent authority requires it, and within the reasonable time limit it sets, provide the information needed to assess the Article 13 measures and evidence that they are effectively implemented. The evidence includes the results of an audit by an independent and qualified auditor, chosen by the entity and paid for by it.
Nothing in the acts covered.
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 DSSPayment Card Industry Data Security Standard scope is documented and validated.
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 infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk. and sensitive information, background check procedures under Article 14 and the categories of people who must undergo them, and training and qualification requirements. Include the personnel of external service providers when setting the categories of personnel in critical functions.
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 dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment. by business need to know are defined and understood.
Access to system components and data is appropriately defined and assigned
Access to system components and data is appropriately defined and assigned.
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 controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements. system(s).
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.
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.
Strong authentication for users and administrators is established and managed
Strong authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. for users and administrators is established and managed.
Multi-factor authentication (MFA) is implemented to secure access into the CDE
Multi-factor authenticationAuthentication through verification of at least two different types of factor: something a person knows, such as a password; something they have, such as a token; or something they are, such as a biometric. NIS2, PCI DSS, the NYDFS regulation and the FTC Safeguards Rule call for it. (MFA) is implemented to secure access into the CDECardholder Data Environment.
Multi-factor authentication (MFA) systems are configured to prevent misuse
Multi-factor authenticationAuthentication through verification of at least two different types of factor: something a person knows, such as a password; something they have, such as a token; or something they are, such as a biometric. NIS2, PCI DSS, the NYDFS regulation and the FTC Safeguards Rule call for it. (MFA) systems are configured to prevent misuse.
Use of application and system accounts and associated authentication factors is strictly managed
Use of application and system accounts and associated authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. factors is strictly managed.
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 numberThe unique payment card number that identifies the card issuer and the cardholder account, used on credit, debit and prepaid cards. Under PCI DSS the full PAN is the minimum element of cardholder data, so where it is stored, processed or transmitted drives the scope of an assessment. (PAN) is secured wherever it is stored.
Cryptographic keys used to protect stored account data are secured
Cryptographic keys used to protect stored account dataThe PCI DSS umbrella term for cardholder data, sensitive authentication data or both. PCI DSS requirements apply to every system component that stores, processes or transmits account data, or that could affect its security. are secured.
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 cryptographyThe use of mathematical methods to protect information and provide evidence that it can be trusted. Cryptography can hide information, detect changes and help verify where information came from. Encryption, which makes readable information unintelligible without the means to decrypt it, is one use of cryptography. The broader discipline also supports integrity checks and digital signatures. is used to protect stored account dataThe PCI DSS umbrella term for cardholder data, sensitive authentication data or both. PCI DSS requirements apply to every system component that stores, processes or transmits account data, or that could affect its security., key management processes and procedures covering all aspects of the key lifecycle are defined and implemented.
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 dataThe PCI DSS umbrella term for cardholder data, sensitive authentication data or both. PCI DSS requirements apply to every system component that stores, processes or transmits account data, or that could affect its security. are defined and understood.
Storage of account data is kept to a minimum
Storage of account dataThe PCI DSS umbrella term for cardholder data, sensitive authentication data or both. PCI DSS requirements apply to every system component that stores, processes or transmits account data, or that could affect its security. is kept to a minimum.
Sensitive authentication data (SAD) is not stored after authorization
Sensitive authentication dataSecurity-related information used to authenticate cardholders or authorise payment card transactions, such as card verification codes, full track data, PINs and PIN blocks. Together with cardholder data it makes up account data under PCI DSS. (SAD) is not stored after authorization.
Access to displays of full PAN and ability to copy PAN are restricted
Access to displays of full PANPrimary Account Number and ability to copy PANPrimary Account Number are restricted.
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.
Network security controls (NSCs) are configured and maintained
Network security controls (NSCs) are configured and maintained.
Network access to and from the cardholder data environment is restricted
Network access to and from the cardholder data environmentThe system components, people and processes that store, process or transmit cardholder data or sensitive authentication data, plus components with unrestricted connectivity to them. Defining the CDE sets the scope of a PCI DSS assessment. is restricted.
Network connections between trusted and untrusted networks are controlled
Network connections between trusted and untrusted networks are controlled.
Risks to the CDE from computing devices that are able to connect to both untrusted networks and the CDE are mitigated
Risks to the CDECardholder Data Environment from computing devices that are able to connect to both untrusted networks and the CDECardholder Data Environment are mitigated.
Wireless environments are configured and managed securely
Wireless environments are configured and managed securely.
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.
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 dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment. with strong cryptographyThe use of mathematical methods to protect information and provide evidence that it can be trusted. Cryptography can hide information, detect changes and help verify where information came from. Encryption, which makes readable information unintelligible without the means to decrypt it, is one use of cryptography. The broader discipline also supports integrity checks and digital signatures. during transmission over open, public networks are defined and understood.
PAN is protected with strong cryptography during transmission
PANPrimary Account Number is protected with strong cryptographyThe use of mathematical methods to protect information and provide evidence that it can be trusted. Cryptography can hide information, detect changes and help verify where information came from. Encryption, which makes readable information unintelligible without the means to decrypt it, is one use of cryptography. The broader discipline also supports integrity checks and digital signatures. during transmission.
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.
Bespoke and custom software are developed securely
Bespoke and custom software are developed securely.
Public-facing web applications are protected against attacks
Public-facing web applications are protected against attacks.
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.
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.
System components are configured and managed securely
System components are configured and managed securely.
Security vulnerabilities are identified and addressed
Security vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. are identified and addressed.
External and internal vulnerabilities are regularly identified, prioritized, and addressed
External and internal vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. are regularly identified, prioritized, and addressed.
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 infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk. and sensitive information, background check procedures under Article 14 and the categories of people who must undergo them, and training and qualification requirements. Include the personnel of external service providers when setting the categories of personnel in critical functions.
Request background checks where permitted Optional
Under conditions set by the Member State and in duly reasoned cases, the entity may request background checks on people in sensitive roles, people with direct or remote access to its premises, information or control systems, and candidates for those positions.
Limits and content of background checks
Applies to: Member States
Checks are proportionate, strictly limited to what is necessary and carried out only to evaluate a potential security risk to the entity. At a minimum they confirm the person's identity and check criminal records for offences relevant to the position. Central authorities answer requests for criminal records held in other Member States within 10 working days.
Personnel are screened to reduce risks from insider threats
Personnel are screened to reduce risks from insider threats.
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 infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk., considering for example fencing, barriers, perimeter monitoring, detection equipment and access controlsAccess Control.
Processes and mechanisms for restricting physical access to cardholder data are defined and understood
Processes and mechanisms for restricting physical access to cardholder dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment. are defined and understood.
Physical access controls manage entry into facilities and systems containing cardholder data
Physical access controls manage entry into facilities and systems containing cardholder dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment..
Physical access for personnel and visitors is authorized and managed
Physical access for personnel and visitors is authorized and managed.
Media with cardholder data is securely stored, accessed, distributed, and destroyed
Media with cardholder dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment. is securely stored, accessed, distributed, and destroyed.
Point-of-interaction (POI) devices are protected from tampering and unauthorized substitution
Point-of-interaction (POI) devices are protected from tampering and unauthorized substitution.
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 softwareSoftware or firmware deliberately designed to harm a computer system or the information it holds. Malware can steal or destroy data, change information without permission, spy on activity or stop systems working. Examples include viruses, worms and spyware. Screening email or uploads for malware means looking for this harmful code before it can affect people or systems. are defined and understood.
Malicious software (malware) is prevented, or detected and addressed
Malicious software (malware) is prevented, or detected and addressed.
Anti-malware mechanisms and processes are active, maintained, and monitored
Anti-malwareSoftware designed to find malicious software, prevent it from infecting computers and, in some cases, remove an existing infection. Malicious software, or malware, includes programs such as viruses and spyware that can damage systems, steal information or disrupt operations. In security requirements, anti-malware refers to this protective capability rather than a particular product. mechanisms and processes are active, maintained, and monitored.
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 dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment. are defined and understood.
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.
Audit logs are protected from destruction and unauthorized modifications
Audit logs are protected from destruction and unauthorized modifications.
Audit logs are reviewed to identify anomalies or suspicious activity
Audit logs are reviewed to identify anomalies or suspicious activity.
Audit log history is retained and available for analysis
Audit log history is retained and available for analysis.
Time-synchronization mechanisms support consistent time settings across all systems
Time-synchronization mechanisms support consistent time settings across all systems.
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.
Network intrusions and unexpected file changes are detected and responded to
Network intrusions and unexpected file changes are detected and responded to.
Unauthorized changes on payment pages are detected and responded to
Unauthorized changes on payment pages are detected and responded to.
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.
Suspected and confirmed security incidents that could impact the CDE are responded to immediately
Suspected and confirmed security incidents that could impact the CDECardholder Data Environment are responded to immediately.
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.
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.
Detailed incident report
Where relevant, follow the initial notification with a detailed report within one month.
Content of the notification
Include any available information that lets the competent authority understand the nature, cause and possible consequences of the incident, including any cross-border impact. Notifying does not expose the entity to increased liability.
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.
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.
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.
Recover and resume the essential service
Recover from incidents and resume the essential serviceIn the EU Critical Entities Resilience Directive, a service needed to keep society's vital functions, economic activity, public health and safety or the environment functioning. Examples include services in energy, transport, health and drinking water. The concept concerns the service people depend on. National authorities identify the critical entities that provide such services. The Directive requires reporting of incidents that significantly disrupt or could significantly disrupt essential services, with details implemented through national requirements., considering business continuityAn organisation's ability to keep delivering its products and services at an acceptable, previously agreed level during a disruption. The focus is on sustaining the activities customers and others depend on, even when normal operations are interrupted. A business continuity management system helps an organisation develop and maintain that capability; a business continuity plan records the arrangements for putting it into practice. measures and alternative supply chains.
Resilience plan
Have in place and apply a resilience plan or equivalent documents that describe the measures taken. Documents and measures produced under other legal acts may be reused where relevant, and the competent authority may declare them compliant in whole or in part.
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.
External and internal penetration testing is regularly performed, and exploitable vulnerabilities and security weaknesses are corrected
External and internal penetration testingA security assessment in which authorised testers simulate attacks on an application, system or network to find weaknesses that could actually be exploited. Testing takes place within agreed limits, such as the systems included and the techniques permitted. It can reveal how several weaknesses combine to give an attacker greater access, helping an organisation understand and correct the resulting exposure. is regularly performed, and exploitable vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. and security weaknesses are corrected.
Third parties and supply chain
Supplier and third-party risk
Both cover it read the wording below
NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.19, A.5.21 to A.5.23
All-hazards scope and dependencies
Cover all relevant natural and man-made risks, including cross-sectoral and cross-border risks, accidents, natural disasters, public health emergencies, hybrid threats and other antagonistic threats such as terrorist offences. Take into account how other sectors depend on the entity and how it depends on other sectors, including, where relevant, in neighbouring Member States and third countries. Relevant assessments made under other legal acts may be reused, and the competent authority may declare them compliant in whole or in part.
Recover and resume the essential service
Recover from incidents and resume the essential serviceIn the EU Critical Entities Resilience Directive, a service needed to keep society's vital functions, economic activity, public health and safety or the environment functioning. Examples include services in energy, transport, health and drinking water. The concept concerns the service people depend on. National authorities identify the critical entities that provide such services. The Directive requires reporting of incidents that significantly disrupt or could significantly disrupt essential services, with details implemented through national requirements., considering business continuityAn organisation's ability to keep delivering its products and services at an acceptable, previously agreed level during a disruption. The focus is on sustaining the activities customers and others depend on, even when normal operations are interrupted. A business continuity management system helps an organisation develop and maintain that capability; a business continuity plan records the arrangements for putting it into practice. measures and alternative supply chains.
Employee security management
Ensure adequate employee security management, considering categories of personnel in critical functions, access rights to premises, critical infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk. and sensitive information, background check procedures under Article 14 and the categories of people who must undergo them, and training and qualification requirements. Include the personnel of external service providers when setting the categories of personnel in critical functions.
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.
Third-party service providers (TPSPs) support their customers' PCI DSS compliance
Third-party service providers (TPSPs) support their customers' PCI DSSPayment Card Industry Data Security Standard compliance.
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 entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. in the sectors and subsectors of the Annex by 17 July 2026 and reviews the list at least every four years. An entity qualifies when it provides an essential service, operates on that territory with its critical infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk. located there, and an incident would significantly disrupt that service or a dependent one.
Notification and start of obligations
Applies to: Member States
The Member State notifies each critical entityA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. within one month of identifying it and tells it which obligations apply and from when. The resilience obligations in Chapter III apply to the entity from 10 months after the date of that notification.
Carve-out for banking, financial market and digital infrastructure
Applies to: Member States, for critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. in banking, financial market infrastructure and digital infrastructure
Article 11 and Chapters III, IV and VI do not apply to critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. identified in banking, financial market infrastructure and digital infrastructure (points 3, 4 and 8 of the Annex). Member States may keep or adopt national requirements for a higher level of resilience if they are consistent with Union law.
Report services in six or more Member States
After being notified as a critical entityA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities., tell the competent authority if the entity provides essential services to or in six or more Member States, which services these are and in which Member States.
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.
Report services in six or more Member States
After being notified as a critical entityA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities., tell the competent authority if the entity provides essential services to or in six or more Member States, which services these are and in which Member States.
Inspections, audits and remedial orders
Applies to: Competent authorities
Competent authorities can inspect critical infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk. and premises on site, supervise Article 13 measures off site, and conduct or order audits of critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities.. They may order an entity to remedy an infringement within a reasonable time limit and to report the measures taken.
Provide information and audit evidence
Applies to: Critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. that are also entities under Directive (EU) 2022/2555
Where the competent authority requires it, and within the reasonable time limit it sets, provide the information needed to assess the Article 13 measures and evidence that they are effectively implemented. The evidence includes the results of an audit by an independent and qualified auditor, chosen by the entity and paid for by it.
Nothing in the acts covered.
Penalties and liability
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.
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
Subject to more than one?
We run one control set for both, without doing the work twice. Ask what that saves you.