GDPR Denmark 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 13 of 15 topics. Each verdict names what it rests on; read the wording before relying on it.
- GDPR Denmark Asks more on 4 topics Alone on 0 topics More detailed on 0 topics
- Swift CSP Asks more on 0 topics Alone on 8 topics More detailed on 1 topic
| Topic | GDPR Denmark | Swift CSP | Verdict |
|---|---|---|---|
| Governance | |||
| Awareness and training | GDPR Denmark: – | Swift CSP: 1 | Only Swift CSPno specific requirement on the other side in the acts covered |
| Risk management | |||
| Risk assessment | GDPR Denmark: 1 | Swift CSP: 1 | GDPR Denmark asks morebinding, where the other is optional |
| Protection | |||
| Access control | GDPR Denmark: – | Swift CSP: 2 | Only Swift CSPno specific requirement on the other side in the acts covered |
| Authentication | GDPR Denmark: – | Swift CSP: 4 | Only Swift CSPno specific requirement on the other side in the acts covered |
| Cryptography and encryption | GDPR Denmark: 1 | Swift CSP: 1 | GDPR Denmark asks morebinding, where the other is optional |
| Data security | GDPR Denmark: 2 | Swift CSP: 4 | Swift CSP more detailedmore requirements on this, not necessarily stricter |
| Network security | GDPR Denmark: – | Swift CSP: 4 | Only Swift CSPno specific requirement on the other side in the acts covered |
| Secure communications | GDPR Denmark: – | Swift CSP: 3 | Only Swift CSPno specific requirement on the other side in the acts covered |
| Vulnerability handling | GDPR Denmark: – | Swift CSP: 4 | Only Swift CSPno specific requirement on the other side in the acts covered |
| Human resources security | GDPR Denmark: 1 | Swift CSP: 1 | GDPR Denmark asks morebinding, where the other is optional |
| Physical and environmental security | GDPR Denmark: – | Swift CSP: 1 | Only Swift CSPno specific requirement on the other side in the acts covered |
| Detection and response | |||
| Monitoring and detection | GDPR Denmark: – | Swift CSP: 3 | Only Swift CSPno specific requirement on the other side in the acts covered |
| Incident handling | GDPR Denmark: 1 | Swift CSP: 1 | Both cover itread the wording below |
| Continuity and resilience | |||
| Security testing | GDPR Denmark: 1 | Swift CSP: 1 | GDPR Denmark asks morebinding, where the other is optional |
| Third parties and supply chain | |||
| Supplier and third-party risk | GDPR Denmark: 2 | Swift CSP: 1 | Both cover itread the wording below |
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
- GDPR Regulation (EU) 2016/679
National requirements
None recorded yet, so the Directive is shown as it is. The national law may go further.
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
GDPR Denmark: At the time the data are obtained (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Within a reasonable period and at the latest one month after obtaining the data; if used to contact the person, at the latest at first communication; if disclosure is envisaged, at the latest at first disclosure (Controllers); Without undue delay and in any event within one month of receipt of the request; extendable by two further months where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Without undue delay and in any event within one month of receipt of the request (Article 12(3)); extendable by two further months where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Without undue delay after becoming aware (Processors); Without undue delay (Controllers); Before the processing starts (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Before the processing starts; where the authority considers the processing would infringe, it gives written advice within up to eight weeks of receipt of the request, extendable by six weeks (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)
Swift CSP: Not in the acts covered
Threshold
GDPR Denmark: Under 16; Member States may lower the age, not below 13 (Controllers offering information society services directly to children); Exemption only below 250 persons, and only if none of the listed conditions applies (Controllers)
Swift CSP: Not in the acts covered
Goes to
GDPR Denmark: Controller (Processors); Data subjects (Controllers)
Swift CSP: Not in the acts covered
Evidence to keep
GDPR Denmark: Written record of processing activities (Controllers); Written record of processing activities (Processors); Internal record of each breach: facts, effects and remedial action (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)
Swift CSP: Not in the acts covered
Incident reports go to
GDPR Denmark: Competent supervisory authority (Controllers)
Swift CSP: Not in the acts covered
First notice of an incident
GDPR Denmark: Without undue delay and, where feasible, within 72 hours of becoming aware (Controllers)
Swift CSP: Not in the acts covered
Intermediate report
GDPR Denmark: In phases, without undue further delay (Controllers)
Swift CSP: Not in the acts covered
External assessment or certification
GDPR Denmark: Approved code of conduct or certification may help show compliance (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)
Swift CSP: Not in the acts covered
Review of the risk framework
GDPR Denmark: Where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)
Swift CSP: Not in the acts covered
Testing of critical systems
GDPR Denmark: Regularly
Swift CSP: Not in the acts covered
Maximum fines
GDPR Denmark: Up to EUR 10 million or, for an undertaking, 2% of total worldwide annual turnover of the preceding financial year, whichever is higher; Up to EUR 20 million or, for an undertaking, 4% of total worldwide annual turnover of the preceding financial year, whichever is higher
Swift CSP: Not in the acts covered
Governance
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
GDPR Denmark asks more binding, where the other is optional
NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 Clauses 6.1.2, 8.2
Assess security risk
When judging the right level of security, weigh the risks of processing, in particular accidental or unlawful destruction, loss, alteration, and unauthorised disclosure of or access to personal data.
GDPR, Article 32(2) · applies as in the Directive
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
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.15, A.5.18, A.8.2, A.8.3
Nothing in the acts covered.
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
GDPR Denmark asks more binding, where the other is optional
NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.8.24
Pseudonymisation and encryption
Apply pseudonymisation and encryption of personal data, as appropriate to the risk.
GDPR, Article 32(1)(a) · applies as in the Directive
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
Integrity and confidentiality
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
Process personal data with appropriate security, using appropriate technical or organisational measures, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage.
GDPR, Article 5(1)(f) · applies as in the Directive
Security of systems and services
Be able to keep processing systems and services confidential, intact, available and resilient on an ongoing basis, as appropriate to the risk.
GDPR, Article 32(1)(b) · applies as in the Directive
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
Only Swift CSP no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.8.20 to A.8.22
Nothing in the acts covered.
Swift Environment Protection
Applies to: A1, A2, A3
Place the 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
Only Swift CSP no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.14
Nothing in the acts covered.
Internal Data Flow Security
Applies to: A1, A2, A3
Protect the 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
GDPR Denmark asks more binding, where the other is optional
NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.6.1 to A.6.6
Staff act only on instructions
Processors, and anyone with access to personal data under the authority of a controller or processor, process it only on the controller's instructions unless EU or Member State law requires otherwise. Controllers and processors take steps to ensure this.
GDPR, Articles 29 and 32(4) · applies as in the Directive
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
Document every breach
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
Record each personal data breach, whether notified or not, with its facts, effects and remedial action, so the authority can check compliance.
GDPR, Article 33(5) · applies as in the Directive
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..
Continuity and resilience
Security testing
GDPR Denmark asks more binding, where the other is optional
NIST CSF 2.0 ID.IM · ISO/IEC 27001:2022 A.5.35, A.8.29, A.8.34
Testing the measures
Have a process to test and evaluate regularly whether the technical and organisational security measures work, as appropriate to the risk.
GDPR, Article 32(1)(d) · applies as in the Directive
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
Use only processors with sufficient guarantees
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
Use only processors that give adequate assurances of technical and organisational measures that meet the Regulation and protect people's rights.
GDPR, Article 28(1) · applies as in the Directive
Sub-processors
Applies to: Processors
Do not engage another processor without the controller's prior written authorisation, specific or general, and under general authorisation give notice of changes so the controller can object. Bind the sub-processor by contract to the same data protection obligations. The initial processor stays fully liable for the sub-processor's failures.
GDPR, Article 28(2) and (4) · applies as in the Directive
Outsourced Critical Activity Protection
Applies to: All types
Ensure that critical activities outsourced to third parties are protected to the same standard.
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. 16 topics where all apply the Directive as it is are not shown.
More Comparisons
Subject to more than one?
We run one control set for both, without doing the work twice. Ask what that saves you.