ePrivacy vs Swift CSP
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 19 of 22 topics. Each verdict names what it rests on; read the wording before relying on it.
- ePrivacy Asks more on 0 topics Alone on 7 topics More detailed on 0 topics
- Swift CSP Asks more on 0 topics Alone on 9 topics More detailed on 3 topics
| Topic | ePrivacy | Swift CSP | Verdict |
|---|---|---|---|
| Governance | |||
| Security policy | ePrivacy: 1 | Swift CSP: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Awareness and training | ePrivacy: – | Swift CSP: 1 | Only Swift CSPno specific requirement on the other side in the acts covered |
| Risk management | |||
| Risk assessment | ePrivacy: – | Swift CSP: 1 | Only Swift CSPno specific requirement on the other side in the acts covered |
| Protection | |||
| Access control | ePrivacy: 1 | Swift CSP: 2 | Both cover itread the wording below |
| Authentication | ePrivacy: – | Swift CSP: 4 | Only Swift CSPno specific requirement on the other side in the acts covered |
| Cryptography and encryption | ePrivacy: – | Swift CSP: 1 | Only Swift CSPno specific requirement on the other side in the acts covered |
| Data security | ePrivacy: 1 | Swift CSP: 4 | Swift CSP more detailedmore requirements on this, not necessarily stricter |
| Network security | ePrivacy: 1 | Swift CSP: 4 | Swift CSP more detailedmore requirements on this, not necessarily stricter |
| Secure communications | ePrivacy: 1 | Swift CSP: 3 | Swift CSP more detailedmore requirements on this, not necessarily stricter |
| Vulnerability handling | ePrivacy: – | Swift CSP: 4 | Only Swift CSPno specific requirement on the other side in the acts covered |
| Human resources security | ePrivacy: – | Swift CSP: 1 | Only Swift CSPno specific requirement on the other side in the acts covered |
| Physical and environmental security | ePrivacy: – | Swift CSP: 1 | Only Swift CSPno specific requirement on the other side in the acts covered |
| Detection and response | |||
| Monitoring and detection | ePrivacy: – | Swift CSP: 3 | Only Swift CSPno specific requirement on the other side in the acts covered |
| Incident handling | ePrivacy: 1 | Swift CSP: 1 | Both cover itread the wording below |
| Reporting to authorities | ePrivacy: 4 | Swift CSP: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Informing customers and the public | ePrivacy: 2 | Swift CSP: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Continuity and resilience | |||
| Security testing | ePrivacy: – | Swift CSP: 1 | Only Swift CSPno specific requirement on the other side in the acts covered |
| Third parties and supply chain | |||
| Supplier and third-party risk | ePrivacy: 1 | Swift CSP: 1 | Both cover itread the wording below |
| Privacy and data protection | |||
| Lawful processing | ePrivacy: 4 | Swift CSP: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Transparency | ePrivacy: 3 | Swift CSP: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Supervision and enforcement | |||
| Cooperation with supervisors | ePrivacy: 1 | Swift CSP: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Penalties and liability | ePrivacy: 1 | Swift CSP: – | 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.
Included
- Swift CSP Swift Customer Security Controls Framework v2026 (CSCF v2026)
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)
Swift CSP: 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)
Swift CSP: 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)
Swift CSP: Not in the acts covered
Incident reports go to
ePrivacy: Competent national authority (Providers of publicly available electronic communications services)
Swift CSP: 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)
Swift CSP: Not in the acts covered
Incident notification
ePrivacy: Within three days of the initial notification (Providers of publicly available electronic communications services)
Swift CSP: Not in the acts covered
Maximum fines
ePrivacy: Set by each Member State; no EU maximum (Member States and competent national authorities)
Swift CSP: Not in the acts covered
Governance
Security policy
Only ePrivacy no specific requirement on the other side in the acts covered
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.
Nothing in the acts covered.
Awareness and training
Only Swift CSP 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.
Security Training and Awareness
Applies to: All types
Train staff with access to SwiftSociety for Worldwide Interbank Financial Telecommunication on security, including role-specific training for privileged users.
Risk management
Risk assessment
Only Swift CSP 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.
Scenario-based Risk Assessment (advisory) Recommended
Applies to: All types (advisory)
Assess the risk of SwiftSociety for Worldwide Interbank Financial Telecommunication-related attack scenarios regularly.
Protection
Access control
Both cover it read the wording below
NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.15, A.5.18, A.8.2, A.8.3
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.
Operating System Privileged Account Control
Applies to: A1, A2, A3, A4; advisory for B
Restrict and control the use of administrator accounts on the operating systems of in-scope components.
Logical Access Control
Applies to: All types
Grant access on need-to-know, least privilegeThe principle that a security architecture gives each user, process or other entity only the system authorisations and resources it needs to perform its function. It limits the damage a compromised account or component can do. and segregation of duties, and review it regularly.
Authentication
Only Swift CSP no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.17, A.8.5
Nothing in the acts covered.
Password Policy
Applies to: All types
Make passwords resistant to common attacks through an enforced password policy.
Multi-Factor Authentication
Applies to: All types
Require 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. for interactive access to SwiftSociety for Worldwide Interbank Financial Telecommunication-related applications and operating system administration.
Token Management
Applies to: All types
Manage hardware 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. tokens and keep them under the control of their owners.
Password Repository Protection
Applies to: All types
Protect stored passwords, physical and logical, against disclosure.
Cryptography and encryption
Only Swift CSP no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.8.24
Nothing in the acts covered.
External Transmission Data Protection (advisory) Recommended
Applies to: A1, A2, A3, A4 (advisory)
Protect SwiftSociety for Worldwide Interbank Financial Telecommunication-related data sent or stored outside the secure zone, such as back-ups or files moved to other sites.
Data security
Swift CSP 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.
Transaction Business Controls
Applies to: All types
Restrict transaction activity to what is expected for your business, such as hours, counterparties and value limits, and detect deviations.
RMA Business Controls (advisory) Recommended
Applies to: All types (advisory)
Review Relationship Management Application relationships regularly and remove those no longer needed.
Software Integrity
Applies to: A1, A2, A3; advisory for A4
Check the integrity of the SwiftSociety for Worldwide Interbank Financial Telecommunication-related software you run.
Database Integrity
Applies to: A1, A2; advisory for A4
Check the integrity of the database records of the messaging interface.
Network security
Swift CSP 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.
Swift Environment Protection
Applies to: A1, A2, A3
Place the SwiftSociety for Worldwide Interbank Financial Telecommunication infrastructure in a secure zone, separated from the general ITInformation Technology environment, with controlled access into and out of it.
Virtualisation or Cloud Platform Protection
Applies to: A1, A2, A3, A4; advisory for B
Secure the virtualisation or cloud platform that hosts in-scope components to the same level as the components themselves.
Restriction of Internet Access
Applies to: All types
Limit internet access from operator PCs and in-scope systems to what is needed, and control it.
Customer Environment Protection
Applies to: A4
For users with a customer connector, protect that environment in a dedicated, separated zone.
Secure communications
Swift CSP more detailed more requirements on this, not necessarily stricter
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.
Internal Data Flow Security
Applies to: A1, A2, A3
Protect the confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available., integrity and authenticity of data flows between SwiftSociety for Worldwide Interbank Financial Telecommunication-related components.
Back Office Data Flow Security
Applies to: A1, A2, A3, A4
Protect data flows between the back office and the secure zone, starting with bridging servers. Mandatory since v2026; legacy direct flows tentatively from 2028.
Operator Session Confidentiality and Integrity
Applies to: All types
Protect interactive operator sessions to SwiftSociety for Worldwide Interbank Financial Telecommunication-related applications against eavesdropping and tampering.
Vulnerability handling
Only Swift CSP no specific requirement on the other side in the acts covered
NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.8.8
Nothing in the acts covered.
Security Updates
Applies to: All types
Install vendor security updates on in-scope hardware and software within a risk-based time frame.
System Hardening
Applies to: All types
Harden operating systems, databases and network devices of the SwiftSociety for Worldwide Interbank Financial Telecommunication environment against attack.
Vulnerability Scanning
Applies to: A1, A2, A3, A4; advisory for B
Scan in-scope components for 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 act on the results.
Application Hardening
Applies to: A1, A2, A3
Harden the SwiftSociety for Worldwide Interbank Financial Telecommunication messaging and communication interfaces and related applications.
Human resources security
Only Swift CSP 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.
Staff Screening Process (advisory) Recommended
Applies to: All types (advisory)
Screen staff who operate or administer the SwiftSociety for Worldwide Interbank Financial Telecommunication environment before and during employment, where local law allows.
Physical and environmental security
Only Swift CSP no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.7.1 to A.7.14
Nothing in the acts covered.
Physical Security
Applies to: All types
Prevent unauthorised physical access to sensitive equipment, workplaces, tokens and storage media.
Detection and response
Monitoring and detection
Only Swift CSP no specific requirement on the other side in the acts covered
NIST CSF 2.0 DE.CM, DE.AE · ISO/IEC 27001:2022 A.8.15, A.8.16
Nothing in the acts covered.
Malware Protection
Applies to: All types
Protect in-scope components with up-to-date anti-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..
Logging and Monitoring
Applies to: All types
Record security events and monitor them to detect anomalous activity and operations.
Intrusion Detection (advisory) Recommended
Applies to: A1, A2, A3, A4 (advisory)
Detect and contain anomalous network activity inside and towards the secure zone.
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.
Cyber Incident Response Planning
Applies to: All types
Keep and test a cyber incident response planA written set of instructions for detecting and handling cybersecurity incidents and limiting their consequences. It gives the organisation a prepared approach to follow when systems or information are attacked. In practice, it should make clear who acts, how decisions and communications are handled, and how the response is coordinated. The plan supports the people doing the response work. that covers SwiftSociety for Worldwide Interbank Financial Telecommunication, including informing SwiftSociety for Worldwide Interbank Financial Telecommunication and using its threat intelligenceInformation about cyber threats that has been collected, combined and analysed to help people make security decisions. It adds context to facts about attackers, their methods or signs of an attack, helping an organisation judge what matters to its systems. It can guide monitoring, incident response, information sharing and realistic attack simulations..
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 Swift CSP no specific requirement on the other side in the acts covered
NIST CSF 2.0 ID.IM · ISO/IEC 27001:2022 A.5.35, A.8.29, A.8.34
Nothing in the acts covered.
Penetration Testing (advisory) Recommended
Applies to: All types (advisory)
Test the security of the SwiftSociety for Worldwide Interbank Financial Telecommunication environment through penetration tests.
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..
Outsourced Critical Activity Protection
Applies to: All types
Ensure that critical activities outsourced to third parties are protected to the same standard.
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.