> GDPR Denmark vs Swift CSP side by side, topic by topic: where they overlap, where they differ and which asks more, with incident deadlines, testing, third parties and fines.

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

[GDPR Denmark](https://grc.plus/regulation/general-data-protection-regulation-gdpr/denmark/)Controllers and processors

[Swift CSP](https://grc.plus/regulation/swift-customer-security-program-swift-csp/)Swift users, for their architecture type

## 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 CSP**no specific requirement on the other side in the acts covered |
| Risk management |  |  |  |
| Risk assessment | GDPR Denmark: 1 | Swift CSP: 1 | **GDPR Denmark asks more**binding, where the other is optional |
| Protection |  |  |  |
| Access control | GDPR Denmark: – | Swift CSP: 2 | **Only Swift CSP**no specific requirement on the other side in the acts covered |
| Authentication | GDPR Denmark: – | Swift CSP: 4 | **Only Swift CSP**no specific requirement on the other side in the acts covered |
| Cryptography and encryption | GDPR Denmark: 1 | Swift CSP: 1 | **GDPR Denmark asks more**binding, where the other is optional |
| Data security | GDPR Denmark: 2 | Swift CSP: 4 | **Swift CSP more detailed**more requirements on this, not necessarily stricter |
| Network security | GDPR Denmark: – | Swift CSP: 4 | **Only Swift CSP**no specific requirement on the other side in the acts covered |
| Secure communications | GDPR Denmark: – | Swift CSP: 3 | **Only Swift CSP**no specific requirement on the other side in the acts covered |
| Vulnerability handling | GDPR Denmark: – | Swift CSP: 4 | **Only Swift CSP**no specific requirement on the other side in the acts covered |
| Human resources security | GDPR Denmark: 1 | Swift CSP: 1 | **GDPR Denmark asks more**binding, where the other is optional |
| Physical and environmental security | GDPR Denmark: – | Swift CSP: 1 | **Only Swift CSP**no specific requirement on the other side in the acts covered |
| Detection and response |  |  |  |
| Monitoring and detection | GDPR Denmark: – | Swift CSP: 3 | **Only Swift CSP**no specific requirement on the other side in the acts covered |
| Incident handling | GDPR Denmark: 1 | Swift CSP: 1 | **Both cover it**read the wording below |
| Continuity and resilience |  |  |  |
| Security testing | GDPR Denmark: 1 | Swift CSP: 1 | **GDPR Denmark asks more**binding, where the other is optional |
| Third parties and supply chain |  |  |  |
| Supplier and third-party risk | GDPR Denmark: 2 | Swift CSP: 1 | **Both cover it**read 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](https://grc.plus/regulation/general-data-protection-regulation-gdpr/) Regulation (EU) 2016/679 Articles 5 to 10, 12 to 22, 24 to 39, 44 to 49, 58, 83 · 50 requirements

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](https://grc.plus/regulation/swift-customer-security-program-swift-csp/) Swift Customer Security Controls Framework v2026 (CSCF v2026) 32 requirements

Status

Reviewed against the official texts.

## Key Numbers

### Deadline

GDPR Denmark: At the time the data are obtained (Controllers); 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 (Controllers); 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 (Controllers); Without undue delay after becoming aware (Processors); Without undue delay (Controllers); Before the processing starts (Controllers); 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 (Controllers)

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 (Controllers)

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 (Controllers)

Swift CSP: Not in the acts covered

### Review of the risk framework

GDPR Denmark: Where necessary (Controllers)

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 Swift on security, including role-specific training for privileged users.
  [Swift CSP, Control 7.2](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

## 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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

- Scenario-based Risk Assessment (advisory) Recommended
  Applies to: All types (advisory)
  Assess the risk of Swift-related attack scenarios regularly.
  [Swift CSP, Control 7.4A](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

## 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.
  [Swift CSP, Control 1.2](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Logical Access Control
  Applies to: All types
  Grant access on need-to-know, least privilege and segregation of duties, and review it regularly.
  [Swift CSP, Control 5.1](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### 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.
  [Swift CSP, Control 4.1](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Multi-Factor Authentication
  Applies to: All types
  Require multi-factor authentication for interactive access to Swift-related applications and operating system administration.
  [Swift CSP, Control 4.2](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Token Management
  Applies to: All types
  Manage hardware authentication tokens and keep them under the control of their owners.
  [Swift CSP, Control 5.2](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Password Repository Protection
  Applies to: All types
  Protect stored passwords, physical and logical, against disclosure.
  [Swift CSP, Control 5.4](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### 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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

- External Transmission Data Protection (advisory) Recommended
  Applies to: A1, A2, A3, A4 (advisory)
  Protect Swift-related data sent or stored outside the secure zone, such as back-ups or files moved to other sites.
  [Swift CSP, Control 2.5A](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### 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: Controllers
  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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · 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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · 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.
  [Swift CSP, Control 2.9](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- RMA Business Controls (advisory) Recommended
  Applies to: All types (advisory)
  Review Relationship Management Application relationships regularly and remove those no longer needed.
  [Swift CSP, Control 2.11A](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Software Integrity
  Applies to: A1, A2, A3; advisory for A4
  Check the integrity of the Swift-related software you run.
  [Swift CSP, Control 6.2](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Database Integrity
  Applies to: A1, A2; advisory for A4
  Check the integrity of the database records of the messaging interface.
  [Swift CSP, Control 6.3](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### 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 Swift infrastructure in a secure zone, separated from the general IT environment, with controlled access into and out of it.
  [Swift CSP, Control 1.1](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- 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.
  [Swift CSP, Control 1.3](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- 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.
  [Swift CSP, Control 1.4](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Customer Environment Protection
  Applies to: A4
  For users with a customer connector, protect that environment in a dedicated, separated zone.
  [Swift CSP, Control 1.5](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### 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 confidentiality, integrity and authenticity of data flows between Swift-related components.
  [Swift CSP, Control 2.1](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- 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.
  [Swift CSP, Control 2.4](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Operator Session Confidentiality and Integrity
  Applies to: All types
  Protect interactive operator sessions to Swift-related applications against eavesdropping and tampering.
  [Swift CSP, Control 2.6](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### 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.
  [Swift CSP, Control 2.2](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- System Hardening
  Applies to: All types
  Harden operating systems, databases and network devices of the Swift environment against attack.
  [Swift CSP, Control 2.3](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Vulnerability Scanning
  Applies to: A1, A2, A3, A4; advisory for B
  Scan in-scope components for vulnerabilities and act on the results.
  [Swift CSP, Control 2.7](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Application Hardening
  Applies to: A1, A2, A3
  Harden the Swift messaging and communication interfaces and related applications.
  [Swift CSP, Control 2.10](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### 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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

- Staff Screening Process (advisory) Recommended
  Applies to: All types (advisory)
  Screen staff who operate or administer the Swift environment before and during employment, where local law allows.
  [Swift CSP, Control 5.3A](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### 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.
  [Swift CSP, Control 3.1](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

## 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-malware.
  [Swift CSP, Control 6.1](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Logging and Monitoring
  Applies to: All types
  Record security events and monitor them to detect anomalous activity and operations.
  [Swift CSP, Control 6.4](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)
- Intrusion Detection (advisory) Recommended
  Applies to: A1, A2, A3, A4 (advisory)
  Detect and contain anomalous network activity inside and towards the secure zone.
  [Swift CSP, Control 6.5A](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

### Incident handling

**Both cover it** read the wording below

NIST CSF 2.0 RS.MA, RS.AN, RS.MI · ISO/IEC 27001:2022 A.5.24 to A.5.28

- Document every breach
  Applies to: Controllers
  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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

- Cyber Incident Response Planning
  Applies to: All types
  Keep and test a cyber incident response plan that covers Swift, including informing Swift and using its threat intelligence.
  [Swift CSP, Control 7.1](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

## 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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

- Penetration Testing (advisory) Recommended
  Applies to: All types (advisory)
  Test the security of the Swift environment through penetration tests.
  [Swift CSP, Control 7.3A](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

## Third parties and supply chain

### Supplier and third-party risk

**Both cover it** read the wording below

NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.19, A.5.21 to A.5.23

- Use only processors with sufficient guarantees
  Applies to: Controllers
  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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · 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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · 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.
  [Swift CSP, Control 2.8](https://grc.plus/regulation/swift-customer-security-program-swift-csp/#requirements)

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

- [Compare GDPR Denmark](https://grc.plus/compare/gdpr-denmark/)
- [Compare Swift CSP](https://grc.plus/compare/swift-csp/)

Source: https://grc.plus/compare/gdpr-denmark-vs-swift-csp/
