ePrivacy 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 22 of 26 topics. Each verdict names what it rests on; read the wording before relying on it.
- ePrivacy Asks more on 0 topics Alone on 6 topics More detailed on 0 topics
- PCI DSS Asks more on 0 topics Alone on 13 topics More detailed on 3 topics
| Topic | ePrivacy | PCI DSS | Verdict |
|---|---|---|---|
| Governance | |||
| Management accountability | ePrivacy: – | PCI DSS: 1 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Security policy | ePrivacy: 1 | PCI DSS: 2 | Both cover itread the wording below |
| Awareness and training | ePrivacy: – | PCI DSS: 2 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Risk management | |||
| Risk assessment | ePrivacy: – | PCI DSS: 1 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Asset management | ePrivacy: – | PCI DSS: 1 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Protection | |||
| Access control | ePrivacy: 1 | PCI DSS: 4 | PCI DSS more detailedmore requirements on this, not necessarily stricter |
| Authentication | ePrivacy: – | PCI DSS: 5 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Cryptography and encryption | ePrivacy: – | PCI DSS: 3 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Data security | ePrivacy: 1 | PCI DSS: 4 | PCI DSS more detailedmore requirements on this, not necessarily stricter |
| Network security | ePrivacy: 1 | PCI DSS: 7 | PCI DSS more detailedmore requirements on this, not necessarily stricter |
| Secure communications | ePrivacy: 1 | PCI DSS: 2 | Both cover itread the wording below |
| Secure acquisition and development | ePrivacy: – | PCI DSS: 3 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Configuration, change and patch management | ePrivacy: – | PCI DSS: 1 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Vulnerability handling | ePrivacy: – | PCI DSS: 4 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Human resources security | ePrivacy: – | PCI DSS: 1 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Physical and environmental security | ePrivacy: – | PCI DSS: 5 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Detection and response | |||
| Monitoring and detection | ePrivacy: – | PCI DSS: 12 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Incident handling | ePrivacy: 1 | PCI DSS: 1 | Both cover itread the wording below |
| Reporting to authorities | ePrivacy: 4 | PCI DSS: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Informing customers and the public | ePrivacy: 2 | PCI DSS: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Continuity and resilience | |||
| Security testing | ePrivacy: – | 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 | ePrivacy: 1 | PCI DSS: 2 | Both cover itread the wording below |
| Privacy and data protection | |||
| Lawful processing | ePrivacy: 4 | PCI DSS: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Transparency | ePrivacy: 3 | PCI DSS: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Supervision and enforcement | |||
| Cooperation with supervisors | ePrivacy: 1 | PCI DSS: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Penalties and liability | ePrivacy: 1 | PCI DSS: – | Only ePrivacyno 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
- ePrivacy Directive 2002/58/EC of the European Parliament and of the Council of 12 July 2002, as amended by Directive 2009/136/EC; Commission Regulation (EU) No 611/2013
Status
Reviewed against the official texts.
Key Numbers
Deadline
ePrivacy: Without undue delay after detection (Providers of publicly available electronic communications services); Immediately (Providers contracted by a provider of publicly available electronic communications services)
PCI DSS: Not in the acts covered
Goes to
ePrivacy: Subscribers (Providers of publicly available electronic communications services); Subscribers and individuals affected (Providers of publicly available electronic communications services); Contracting provider (Providers contracted by a provider of publicly available electronic communications services)
PCI DSS: Not in the acts covered
Evidence to keep
ePrivacy: Inventory of personal data breachesPersonal Data Breach Under the ePrivacy Directive (Providers of publicly available electronic communications services)
PCI DSS: Not in the acts covered
Incident reports go to
ePrivacy: Competent national authority (Providers of publicly available electronic communications services)
PCI DSS: Not in the acts covered
First notice of an incident
ePrivacy: Within 24 hours of detection, where feasible (Providers of publicly available electronic communications services)
PCI DSS: Not in the acts covered
Incident notification
ePrivacy: Within three days of the initial notification (Providers of publicly available electronic communications services)
PCI DSS: Not in the acts covered
Maximum fines
ePrivacy: Set by each Member State; no EU maximum (Member States and competent national authorities)
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.
Security policy
Both cover it read the wording below
NIST CSF 2.0 GV.PO · ISO/IEC 27001:2022 A.5.1
Secure the service
Applies to: Providers of publicly available electronic communications services
Take technical and organisational measures suited to the risk to secure the service, with the network provider where needed. At least limit access to personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. to authorised staff for lawful purposes, protect stored or transmitted data against destruction, loss, alteration and unauthorised processing, and apply a security policy. National authorities may audit the measures.
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
Only PCI DSS no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.AT · ISO/IEC 27001:2022 A.6.3
Nothing in the acts covered.
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 assessment
Only PCI DSS no specific requirement on the other side in the acts covered
NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 Clauses 6.1.2, 8.2
Nothing in the acts covered.
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.
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
Secure the service
Applies to: Providers of publicly available electronic communications services
Take technical and organisational measures suited to the risk to secure the service, with the network provider where needed. At least limit access to personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. to authorised staff for lawful purposes, protect stored or transmitted data against destruction, loss, alteration and unauthorised processing, and apply a security policy. National authorities may audit the measures.
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
PCI DSS more detailed more requirements on this, not necessarily stricter
NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.12, A.8.10 to A.8.12
Secure the service
Applies to: Providers of publicly available electronic communications services
Take technical and organisational measures suited to the risk to secure the service, with the network provider where needed. At least limit access to personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. to authorised staff for lawful purposes, protect stored or transmitted data against destruction, loss, alteration and unauthorised processing, and apply a security policy. National authorities may audit the measures.
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
PCI DSS more detailed more requirements on this, not necessarily stricter
NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.8.20 to A.8.22
Secure the service
Applies to: Providers of publicly available electronic communications services
Take technical and organisational measures suited to the risk to secure the service, with the network provider where needed. At least limit access to personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. to authorised staff for lawful purposes, protect stored or transmitted data against destruction, loss, alteration and unauthorised processing, and apply a security policy. National authorities may audit the measures.
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
Both cover it read the wording below
NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.14
Confidentiality of communications
Applies to: Anyone other than the users of the communication
Do not listen to, tap, store or otherwise intercept communications and related traffic dataAny data processed to convey a communication over an electronic communications network or to bill for it. Providers must erase or anonymise traffic data when it is no longer needed for transmission, subject to permitted further processing and lawful statutory derogations under Article 15 of the ePrivacy Directive. without the users' consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard., unless legally authorised under Article 15(1). Technical storage needed for transmission remains allowed. Regulation (EU) 2026/1881 gives a temporary exception, until 3 April 2028, for number-independent interpersonal communications services detecting online child sexual abuse under its conditions.
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
Only PCI DSS no specific requirement on the other side in the acts covered
NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.6.1 to A.6.6
Nothing in the acts covered.
Personnel are screened to reduce risks from insider threats
Personnel are screened to reduce risks from insider threats.
Physical and environmental 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.7.1 to A.7.14
Nothing in the acts covered.
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
Keep a breach inventory
Applies to: Providers of publicly available electronic communications services
Keep an inventory of personal data breachesPersonal Data Breach Under the ePrivacy Directive recording the facts, effects and remedial action, with only the information authorities need to check compliance. Authorities may issue guidelines and instructions, can audit compliance and must impose appropriate sanctions for failures.
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.
Reporting to authorities
Only ePrivacy no specific requirement on the other side in the acts covered
NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5
Notify the authority of a personal data breach
Applies to: Providers of publicly available electronic communications services
For providers of publicly available electronic communications services only: report every personal data breachA breach of security leading to accidental or unlawful destruction, loss, alteration or unauthorised disclosure of or access to personal data. A controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours after becoming aware of the breach, unless it is unlikely to result in a risk to people's rights and freedoms. to the competent national authority without undue delay, within 24 hours of detection where feasible. Detection means enough awareness to make a meaningful notification, not a mere suspicion. Describe the breach, contact points, recommended mitigation, the consequences and the measures taken.
ePrivacy, Article 4(3); Regulation (EU) No 611/2013, Article 2(1) and (2)
Second notification to the authority
Applies to: Providers of publicly available electronic communications services
For providers of publicly available electronic communications services only: where full information is not yet available and further investigation is needed, send an initial notification within 24 hours of detection. Send a second notification as soon as possible and at the latest within three days of the initial one. If information is still missing then, send what is held with a reasoned justification for the delay and the rest as soon as possible.
Tell subscribers and individuals
Applies to: Providers of publicly available electronic communications services
For providers of publicly available electronic communications services only: where a breach is likely to harm a person's data or privacy, tell them without undue delay after detection, in clear language and without promoting services. This is not needed if the provider satisfies the authority that the data was unintelligible, for example securely encrypted with the key uncompromised. Delay is allowed only in exceptional cases where telling them could put the investigation at risk, and only with the authority's agreement.
ePrivacy, Article 4(3); Regulation (EU) No 611/2013, Articles 3 and 4
Subcontracted provider informs the contracting provider
Applies to: Providers contracted by a provider of publicly available electronic communications services
A provider contracted to deliver part of an electronic communications service, with no direct contract with subscribers, immediately tells the contracting provider of a personal data breachA breach of security leading to accidental or unlawful destruction, loss, alteration or unauthorised disclosure of or access to personal data. A controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours after becoming aware of the breach, unless it is unlikely to result in a risk to people's rights and freedoms..
Nothing in the acts covered.
Informing customers and the public
Only ePrivacy no specific requirement on the other side in the acts covered
NIST CSF 2.0 RS.CO, RC.CO
Warn of a network security risk
Applies to: Providers of publicly available electronic communications services
Where there is a particular risk of a breach of network security, tell subscribers about the risk. Where the risk lies outside the provider's own measures, also tell them of any possible remedies and their likely cost.
Tell subscribers and individuals
Applies to: Providers of publicly available electronic communications services
For providers of publicly available electronic communications services only: where a breach is likely to harm a person's data or privacy, tell them without undue delay after detection, in clear language and without promoting services. This is not needed if the provider satisfies the authority that the data was unintelligible, for example securely encrypted with the key uncompromised. Delay is allowed only in exceptional cases where telling them could put the investigation at risk, and only with the authority's agreement.
ePrivacy, Article 4(3); Regulation (EU) No 611/2013, Articles 3 and 4
Nothing in the acts covered.
Continuity and resilience
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
Subcontracted provider informs the contracting provider
Applies to: Providers contracted by a provider of publicly available electronic communications services
A provider contracted to deliver part of an electronic communications service, with no direct contract with subscribers, immediately tells the contracting provider of a personal data breachA breach of security leading to accidental or unlawful destruction, loss, alteration or unauthorised disclosure of or access to personal data. A controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours after becoming aware of the breach, unless it is unlikely to result in a risk to people's rights and freedoms..
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.
Privacy and data protection
Lawful processing
Only ePrivacy no specific requirement on the other side in the acts covered
NIST Privacy Framework CT.PO-P
Storing or reading data on a device
Applies to: Any organisation storing or reading information on a user's device
Before storing or reading information on a user's device, give clear and comprehensive information and obtain consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard.. This does not apply to storage or access solely to carry a communication, or strictly necessary for a service the user explicitly asked for.
Traffic data
Applies to: Providers of public communications networks and publicly available electronic communications services
Erase or anonymise traffic dataAny data processed to convey a communication over an electronic communications network or to bill for it. Providers must erase or anonymise traffic data when it is no longer needed for transmission, subject to permitted further processing and lawful statutory derogations under Article 15 of the ePrivacy Directive. once it is no longer needed for transmission, apart from billing until the challenge period ends and marketing or value added services with prior, withdrawable consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard.. Tell subscribers what is processed and for how long, and limit handling to authorised staff.
Location data other than traffic data
Applies to: Providers of public communications networks and publicly available electronic communications services, and third parties providing value added services that process location data
Process location data only anonymised, or with consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard. for a value added service for as long as that service needs. Tell users first about the data, purpose, duration and any third-party transfer. Let them withdraw consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard. at any time and refuse temporarily, simply and free of charge.
Unsolicited direct marketing
Applies to: Any organisation sending electronic direct marketing
Use automated calling, fax or email for direct marketing only with prior consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard.. A customer's email details may be used for the seller's own similar products if the customer can object easily and free of charge at collection and in each message. Other marketing follows the national choice of opt-in or opt-out. Marketing emails must not hide the sender's identity or lack a valid address for opt-out requests. The consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard. and opt-outAn opt-out is a way for a person to refuse an activity or stop further participation. In direct marketing, it means taking a step such as unsubscribing from messages. In a default-on arrangement, the activity proceeds unless the person refuses. Having an opt-out does not establish valid consent where the applicable law requires a positive agreement beforehand. requirements protect subscribers who are natural persons; Member States protect the interests of other subscribers.
Nothing in the acts covered.
Transparency
Only ePrivacy no specific requirement on the other side in the acts covered
NIST Privacy Framework CM.AW-P
Storing or reading data on a device
Applies to: Any organisation storing or reading information on a user's device
Before storing or reading information on a user's device, give clear and comprehensive information and obtain consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard.. This does not apply to storage or access solely to carry a communication, or strictly necessary for a service the user explicitly asked for.
Traffic data
Applies to: Providers of public communications networks and publicly available electronic communications services
Erase or anonymise traffic dataAny data processed to convey a communication over an electronic communications network or to bill for it. Providers must erase or anonymise traffic data when it is no longer needed for transmission, subject to permitted further processing and lawful statutory derogations under Article 15 of the ePrivacy Directive. once it is no longer needed for transmission, apart from billing until the challenge period ends and marketing or value added services with prior, withdrawable consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard.. Tell subscribers what is processed and for how long, and limit handling to authorised staff.
Location data other than traffic data
Applies to: Providers of public communications networks and publicly available electronic communications services, and third parties providing value added services that process location data
Process location data only anonymised, or with consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard. for a value added service for as long as that service needs. Tell users first about the data, purpose, duration and any third-party transfer. Let them withdraw consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard. at any time and refuse temporarily, simply and free of charge.
Nothing in the acts covered.
Supervision and enforcement
Cooperation with supervisors
Only ePrivacy no specific requirement on the other side in the acts covered
Procedures for access requests
Applies to: Providers of publicly available electronic communications services
Set internal procedures for answering requests for access to users' personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. made under national law adopted under Article 15(1). On demand, give the competent national authority information on those procedures, the number of requests received, the legal justification invoked and the response given.
Nothing in the acts covered.
Penalties and liability
Only ePrivacy no specific requirement on the other side in the acts covered
Penalties set nationally
Applies to: Member States and competent national authorities
Member States set penalties for infringements, including criminal sanctions where appropriate, which are effective, proportionate and dissuasive. Competent authorities can order infringements to stop and have investigative powers and resources, including to obtain information.
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.