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

# DORA vs Swift CSP

Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.

[DORA](https://grc.plus/regulation/digital-operational-resilience-act-dora/)Financial entities

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

## At a Glance

They differ on 30 of 34 topics. Each verdict names what it rests on; read the wording before relying on it.

- **DORA** Asks more on 7 topics Alone on 19 topics More detailed on 1 topic
- **Swift CSP** Asks more on 2 topics Alone on 1 topic More detailed on 0 topics

| Topic | DORA | Swift CSP | Verdict |
| --- | --- | --- | --- |
| Governance |  |  |  |
| Management accountability | DORA: 3 | Swift CSP: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Roles and independence | DORA: 1 | Swift CSP: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Security policy | DORA: 3 | Swift CSP: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Awareness and training | DORA: 2 | Swift CSP: 1 | **Partly overlap**from the mapping: see the gap notes |
| Risk management |  |  |  |
| Risk management framework | DORA: 2 | Swift CSP: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Risk assessment | DORA: 3 | Swift CSP: 1 | **DORA asks more**from the mapping |
| Review, audit and improvement | DORA: 4 | Swift CSP: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Asset management | DORA: 3 | Swift CSP: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Protection |  |  |  |
| Access control | DORA: 3 | Swift CSP: 2 | **Swift CSP asks more**from the mapping |
| Authentication | DORA: 2 | Swift CSP: 4 | **DORA asks more**from the mapping |
| Cryptography and encryption | DORA: 2 | Swift CSP: 1 | **DORA asks more**binding, where the other is optional |
| Data security | DORA: 3 | Swift CSP: 4 | **DORA asks more**from the mapping |
| Network security | DORA: 3 | Swift CSP: 4 | **DORA asks more**from the mapping |
| Secure communications | DORA: – | Swift CSP: 3 | **Only Swift CSP**no specific requirement on the other side in the acts covered |
| Secure acquisition and development | DORA: 2 | Swift CSP: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Configuration, change and patch management | DORA: 5 | Swift CSP: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Vulnerability handling | DORA: 3 | Swift CSP: 4 | **Swift CSP asks more**from the mapping |
| Human resources security | DORA: 1 | Swift CSP: 1 | **DORA asks more**from the mapping |
| Physical and environmental security | DORA: 1 | Swift CSP: 1 | **Partly overlap**from the mapping: see the gap notes |
| Detection and response |  |  |  |
| Monitoring and detection | DORA: 3 | Swift CSP: 3 | **Partly overlap**from the mapping: see the gap notes |
| Incident handling | DORA: 3 | Swift CSP: 1 | **DORA more detailed**more requirements on this, not necessarily stricter |
| Incident classification | DORA: 1 | Swift CSP: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Reporting to authorities | DORA: 5 | Swift CSP: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Informing customers and the public | DORA: 2 | Swift CSP: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Threat intelligence and information sharing | DORA: 2 | Swift CSP: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Continuity and resilience |  |  |  |
| Business continuity and crisis management | DORA: 3 | Swift CSP: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Backup and recovery | DORA: 1 | Swift CSP: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Security testing | DORA: 3 | Swift CSP: 1 | **DORA asks more**binding, where the other is optional |
| Threat-led penetration testing | DORA: 1 | Swift CSP: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Third parties and supply chain |  |  |  |
| Supplier and third-party risk | DORA: 2 | Swift CSP: 1 | **Partly overlap**from the mapping: see the gap notes |
| Contract requirements | DORA: 2 | Swift CSP: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Register of third-party arrangements | DORA: 1 | Swift CSP: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Exit and termination | DORA: 1 | Swift CSP: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Supervision and enforcement |  |  |  |
| Penalties and liability | DORA: 1 | Swift CSP: – | **Only DORA**no 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

- [DORA](https://grc.plus/regulation/digital-operational-resilience-act-dora/) Regulation (EU) 2022/2554 Articles 5, 6, 8 to 14, 16 to 19, 24 to 26, 28, 30, 45, 50 · 43 requirements
- [DORA ICT Risk Management RTS](https://grc.plus/regulation/dora-rts-ict-risk-management/) Commission Delegated Regulation (EU) 2024/1774 Articles 2 to 31, 33 to 41 · 26 requirements Applies to: Financial entities, except those on the simplified framework
- [JC 2024 34](https://grc.plus/regulation/dora-guidelines-incident-costs-and-losses/) Joint Guidelines on the estimation of aggregated annual costs and losses caused by major ICT-related incidents under Regulation (EU) 2022/2554, JC 2024 34 (Final Report of 17 July 2024), issued under Article 11(11) of Regulation (EU) 2022/2554 5 requirements

Not yet included

- [DORA Third-Party Policy RTS](https://grc.plus/regulation/dora-rts-ict-third-party-policy/)
- [DORA Subcontracting RTS](https://grc.plus/regulation/dora-rts-subcontracting/)
- [DORA Register of Information ITS](https://grc.plus/regulation/dora-its-register-of-information/)
- [DORA Incident Classification RTS](https://grc.plus/regulation/dora-rts-incident-classification/)
- [DORA Incident Reporting RTS](https://grc.plus/regulation/dora-rts-incident-reporting/)
- [DORA Incident Reporting ITS](https://grc.plus/regulation/dora-its-incident-reporting-templates/)
- [DORA TLPT RTS](https://grc.plus/regulation/dora-rts-tlpt/)
- [DORA Critical Provider Criteria](https://grc.plus/regulation/dora-da-critical-provider-criteria/)
- [DORA Oversight Conditions RTS](https://grc.plus/regulation/dora-rts-oversight-conditions/)

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

### Incident reports go to

DORA: Financial supervisor (competent authority)

Swift CSP: Not in the acts covered

### First notice of an incident

DORA: Within 4 hours of classifying it as major, and no later than 24 hours of becoming aware; if classified as major after that, within 4 hours of classifying it

Swift CSP: Not in the acts covered

### Intermediate report

DORA: Within 72 hours of the initial notification

Swift CSP: Not in the acts covered

### Final report

DORA: Within one month of the latest intermediate report

Swift CSP: Not in the acts covered

### Review of the risk framework

DORA: At least once a year (periodically for microenterprises), and after major incidents

Swift CSP: Not in the acts covered

### Testing of critical systems

DORA: At least yearly, for systems supporting critical or important functions

Swift CSP: Not in the acts covered

### Threat-led penetration testing

DORA: At least every 3 years, for entities the authority identifies; the authority may request a lower or higher frequency

Swift CSP: Not in the acts covered

### Register of third-party arrangements

DORA: Required, for every ICT service arrangement

Swift CSP: Not in the acts covered

### Management body training

DORA: Required, on a regular basis

Swift CSP: Not in the acts covered

### Management body liability

DORA: Ultimate responsibility for ICT risk; penalties on members are subject to national law (Article 50(5))

Swift CSP: Not in the acts covered

### Maximum fines

DORA: Set by each Member State (Competent authorities and Member States)

Swift CSP: Not in the acts covered

## Governance

### Management accountability

**Only DORA** 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

- Management body responsibility
  The management body defines, approves, oversees and is responsible for implementing every arrangement of the ICT risk management framework, and bears ultimate responsibility for managing ICT risk.
  [DORA, Article 5(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Budget for resilience
  The management body allocates and reviews the budget for digital operational resilience, including awareness programmes, training and ICT skills for all staff.
  [DORA, Article 5(2)(g)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Governance (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  Governance and organisation of the simplified ICT risk management framework.
  [DORA ICT Risk Management RTS, Article 28](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

Nothing in the acts covered.

### Roles and independence

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.5.2, A.5.3

- Independent control function
  A control function with appropriate independence manages and oversees ICT risk (not required of microenterprises). Risk management, control and internal audit functions are kept appropriately segregated and independent.
  [DORA, Article 6(4)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

Nothing in the acts covered.

### Security policy

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.PO · ISO/IEC 27001:2022 A.5.1

- Information security policy
  A documented information security policy with requirements to protect the availability, authenticity, integrity and confidentiality of data and assets, including customers' where applicable.
  [DORA, Article 9(4)(a)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- ICT security policies
  Applies to: Financial entities, except those on the simplified framework
  ICT security policies, procedures, protocols and tools, with their general elements, approved and reviewed as part of the framework.
  [DORA ICT Risk Management RTS, Article 2](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Information security policy (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  An information security policy and measures.
  [DORA ICT Risk Management RTS, Article 29](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

Nothing in the acts covered.

### Awareness and training

**Partly overlap** from the mapping: see the gap notes

NIST CSF 2.0 PR.AT · ISO/IEC 27001:2022 A.6.3

- Management body training
  Members of the management body keep their knowledge and skills on ICT risk up to date, including by following specific training regularly.
  [DORA, Article 5(4)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Staff awareness and training
  ICT security awareness programmes and digital operational resilience training are compulsory for all employees and senior management.
  [DORA, Article 13(6)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

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

**How these map: 1 link**

- Swift CSP Control 7.2
  Partial
  DORA Article 13(6)
  DORA requires awareness programmes and resilience training for all staff and the management body, whereas the Swift control is limited to staff with access to Swift-related systems.

## Risk management

### Risk management framework

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.RM · ISO/IEC 27001:2022 Clause 6.1

- ICT risk management framework
  A sound, comprehensive and well-documented ICT risk management framework within the overall risk management system, with the strategies, policies, procedures, protocols and tools to protect all information and ICT assets.
  [DORA, Article 6(1) and (2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Simplified ICT risk management framework
  Applies to: Entities on the simplified framework (DORA Article 16)
  Small and non-interconnected investment firms, exempted payment and e-money institutions, small occupational pension funds, and institutions exempted under Directive 2013/36/EU that their Member State has not excluded under Article 2(4) follow a simplified framework instead of Articles 5 to 15.
  [DORA, Article 16(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

Nothing in the acts covered.

### Risk assessment

**DORA asks more** from the mapping

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 Clauses 6.1.2, 8.2

- Identify ICT risk
  Identify all sources of ICT risk continuously, assess cyber threats and vulnerabilities, and review risk scenarios at least yearly.
  [DORA, Article 8(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- ICT risk management policy
  Applies to: Financial entities, except those on the simplified framework
  A policy and procedures for ICT risk management: risk tolerance, identification, assessment and treatment of risks, and the monitoring of residual risk.
  [DORA ICT Risk Management RTS, Article 3](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- ICT risk management (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  Identification and management of ICT risk.
  [DORA ICT Risk Management RTS, Article 31](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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

**How these map: 1 link**

- Swift CSP Control 7.4A
  Supports
  DORA Article 3
  The RTS requires an ICT risk management policy with risk tolerance and risk assessment methods for all ICT risk, not Swift attack scenarios specifically.

### Review, audit and improvement

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.IM, GV.OV · ISO/IEC 27001:2022 A.5.35, A.5.36, Clauses 9, 10

- Yearly review of the framework
  The framework is documented and reviewed at least once a year (periodically for microenterprises), after major ICT-related incidents and following supervisory instructions or conclusions from testing or audits, and improved continuously.
  [DORA, Article 6(5)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Internal audit
  Auditors with sufficient ICT risk expertise audit the framework regularly, in line with the audit plan. Not required of microenterprises.
  [DORA, Article 6(6)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Report on the framework review
  Applies to: Financial entities, except those on the simplified framework
  The format and content of the report on the review of the ICT risk management framework.
  [DORA ICT Risk Management RTS, Article 27](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Framework review report (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  The format and content of the report on the review of the simplified framework.
  [DORA ICT Risk Management RTS, Article 41](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

Nothing in the acts covered.

### Asset management

**Only DORA** 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

- Identify and classify assets
  Identify, classify and document all ICT-supported business functions, information and ICT assets and their dependencies, and review the classification at least yearly.
  [DORA, Article 8(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- ICT asset management
  Applies to: Financial entities, except those on the simplified framework
  An ICT asset management policy and procedure, including an inventory of assets and their criticality.
  [DORA ICT Risk Management RTS, Articles 4 and 5](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Asset classification (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  Classification of information assets and ICT assets.
  [DORA ICT Risk Management RTS, Article 30](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

Nothing in the acts covered.

## Protection

### Access control

**Swift CSP asks more** from the mapping

NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.15, A.5.18, A.8.2, A.8.3

- Limit access
  Limit physical and logical access to what legitimate and approved functions need, with policies, procedures and controls for access rights.
  [DORA, Article 9(4)(c)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Identity management and access control
  Applies to: Financial entities, except those on the simplified framework
  Identity management and access control policies, including authentication.
  [DORA ICT Risk Management RTS, Articles 20 and 21](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Access control (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  Access control.
  [DORA ICT Risk Management RTS, Article 33](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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

**How these map: 4 links**

- Swift CSP Control 1.2
  Partial
  DORA Article 9(4)(c)
  DORA requires access limited to approved functions and sound management of access rights, but does not single out operating system administrator accounts or require their usage to be monitored.
- Swift CSP Control 1.2
  Partial
  DORA Articles 20 and 21
  The RTS requires privileged and administrator access on a need-to-use or ad-hoc basis, dedicated administrator accounts where possible and privileged access management tooling where feasible, for all ICT systems.
- Swift CSP Control 5.1
  Partial
  DORA Article 9(4)(c)
  DORA requires access limited to legitimate and approved functions with sound access rights management, but does not name separation of duties for operator accounts.
- Swift CSP Control 5.1
  Stricter
  DORA Articles 20 and 21
  The RTS requires need-to-know, need-to-use and least privilege, segregation of duties, limited shared accounts, prompt revocation, and access reviews at least every six months for systems supporting critical or important functions.

### Authentication

**DORA asks more** from the mapping

NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.17, A.8.5

- Strong authentication and key protection
  Strong authentication based on relevant standards, and protection of cryptographic keys, with encryption decided by data classification and risk assessment.
  [DORA, Article 9(4)(d)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Identity management and access control
  Applies to: Financial entities, except those on the simplified framework
  Identity management and access control policies, including authentication.
  [DORA ICT Risk Management RTS, Articles 20 and 21](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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

**How these map: 6 links**

- Swift CSP Control 4.1
  Supports
  DORA Article 9(4)(d)
  DORA requires strong authentication policies based on relevant standards but sets no password parameters such as length, complexity or lockout.
- Swift CSP Control 4.1
  Partial
  DORA Articles 20 and 21
  The RTS requires authentication methods commensurate with classification and risk, following leading practices; it sets no password rules of its own.
- Swift CSP Control 4.2
  Partial
  DORA Article 9(4)(d)
  DORA requires strong authentication mechanisms but does not explicitly require multi-factor authentication for interactive access to every in-scope component.
- Swift CSP Control 4.2
  Partial
  DORA Articles 20 and 21
  The RTS requires strong authentication for remote access, privileged access, assets supporting critical or important functions and publicly accessible assets; the Swift control requires it for every operator and administrator of Swift-related applications.
- Swift CSP Control 5.2
  Supports
  DORA Article 9(4)(d)
  DORA covers strong authentication and key protection but does not address the assignment, distribution, revocation and storage of hardware or software tokens.
- Swift CSP Control 5.2
  Supports
  DORA Articles 20 and 21
  The RTS covers the identity lifecycle and authentication methods but has no rule on hardware tokens.

### Cryptography and encryption

**DORA asks more** binding, where the other is optional

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.8.24

- Strong authentication and key protection
  Strong authentication based on relevant standards, and protection of cryptographic keys, with encryption decided by data classification and risk assessment.
  [DORA, Article 9(4)(d)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Encryption and key management
  Applies to: Financial entities, except those on the simplified framework
  Encryption and cryptographic controls, and the management of cryptographic keys through their whole life cycle.
  [DORA ICT Risk Management RTS, Articles 6 and 7](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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

**How these map: 1 link**

- Swift CSP Control 2.5A
  Partial
  DORA Articles 6 and 7
  The RTS requires encryption of data at rest and in transit according to classification, with managed keys; the Swift control focuses on data leaving the secure zone.

### Data security

**DORA asks more** from the mapping

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.12, A.8.10 to A.8.12

- Protect data
  Policies, protocols and tools that keep data available, authentic, intact and confidential at rest, in use and in transit.
  [DORA, Article 9(2) and (3)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- ICT operations and data security
  Applies to: Financial entities, except those on the simplified framework
  Policies and procedures for ICT operations, capacity and performance management, and data and system security.
  [DORA ICT Risk Management RTS, Articles 8, 9 and 11](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Operations, data and network security (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT operations security, and data, system and network security.
  [DORA ICT Risk Management RTS, Articles 34 and 35](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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

**How these map: 2 links**

- Swift CSP Control 6.2
  Partial
  DORA Articles 8, 9 and 11
  The RTS requires measures so that only authorised software is installed in ICT systems and endpoint devices; integrity checks of the Swift software itself are not named.
- Swift CSP Control 6.3
  Supports
  DORA Articles 8, 9 and 11
  The RTS requires data and system security according to classification, without a specific integrity check of messaging interface database records.

### Network security

**DORA asks more** from the mapping

NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.8.20 to A.8.22

- Network and infrastructure management
  Network and infrastructure management on a risk basis, designed so that connections can be severed or segmented instantly to stop contagion.
  [DORA, Article 9(4)(b)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Network security
  Applies to: Financial entities, except those on the simplified framework
  Network security management and the protection of information in transit.
  [DORA ICT Risk Management RTS, Articles 13 and 14](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Operations, data and network security (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT operations security, and data, system and network security.
  [DORA ICT Risk Management RTS, Articles 34 and 35](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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

**How these map: 7 links**

- Swift CSP Control 1.1
  Partial
  DORA Article 9(4)(b)
  DORA requires risk-based network management with the ability to sever or segment connections, but does not prescribe a dedicated secure zone for payment messaging components.
- Swift CSP Control 1.1
  Partial
  DORA Articles 13 and 14
  The RTS requires segregation and segmentation of networks by criticality, documented connections and data flows, a dedicated administration network and a yearly review of the network architecture; it does not define a Swift secure zone.
- Swift CSP Control 1.3
  Supports
  DORA Article 9(4)(b)
  DORA covers infrastructure management in general terms and does not specifically require virtualisation or cloud platforms to be secured to the same level as physical systems.
- Swift CSP Control 1.4
  Partial
  DORA Article 9(4)(b)
  DORA does not specifically require direct internet access from operator PCs and secure zone systems to be restricted to business need.
- Swift CSP Control 1.4
  Partial
  DORA Articles 13 and 14
  The RTS requires network traffic between internal networks and the internet to be secured and firewall rules reviewed; it does not restrict internet access from operator PCs as such.
- Swift CSP Control 1.5
  Partial
  DORA Article 9(4)(b)
  DORA does not prescribe a separated secure zone for customer connectivity components, only risk-based network design and segmentation.
- Swift CSP Control 1.5
  Partial
  DORA Articles 13 and 14
  The RTS requires segmentation by criticality and risk, which covers a customer connector zone, without prescribing one.

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

### Secure acquisition and development

**Only DORA** 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

- Projects, acquisition and development
  Applies to: Financial entities, except those on the simplified framework
  ICT project management, and the acquisition, development and maintenance of ICT systems.
  [DORA ICT Risk Management RTS, Articles 15 and 16](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Development and change (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT systems acquisition, development and maintenance, and ICT project and change management.
  [DORA ICT Risk Management RTS, Articles 37 and 38](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

Nothing in the acts covered.

### Configuration, change and patch management

**Only DORA** 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

- Change management
  Documented change management, so that every change to software, hardware, firmware, systems or security parameters is recorded, tested, assessed, approved, implemented and verified.
  [DORA, Article 9(4)(e)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Patches and updates
  Documented policies for patches and updates.
  [DORA, Article 9(4)(f)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Vulnerability and patch management
  Applies to: Financial entities, except those on the simplified framework
  Procedures to identify and fix vulnerabilities and to apply patches and updates.
  [DORA ICT Risk Management RTS, Article 10](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- ICT change management
  Applies to: Financial entities, except those on the simplified framework
  ICT change management procedures.
  [DORA ICT Risk Management RTS, Article 17](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Development and change (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT systems acquisition, development and maintenance, and ICT project and change management.
  [DORA ICT Risk Management RTS, Articles 37 and 38](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

Nothing in the acts covered.

### Vulnerability handling

**Swift CSP asks more** from the mapping

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.8.8

- Patches and updates
  Documented policies for patches and updates.
  [DORA, Article 9(4)(f)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Tests to run
  Appropriate tests such as vulnerability assessments and scans, network security assessments, source code reviews where feasible, scenario-based tests and penetration tests.
  [DORA, Article 25](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Vulnerability and patch management
  Applies to: Financial entities, except those on the simplified framework
  Procedures to identify and fix vulnerabilities and to apply patches and updates.
  [DORA ICT Risk Management RTS, Article 10](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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

**How these map: 4 links**

- Swift CSP Control 2.2
  Partial
  DORA Article 9(4)(f)
  DORA requires documented patch and update policies but does not require all hardware and software to remain within the vendor support life cycle.
- Swift CSP Control 2.2
  Stricter
  DORA Article 10
  The RTS requires patch management procedures with automated identification of patches, emergency patching, testing before deployment, installation deadlines and escalation when deadlines are missed.
- Swift CSP Control 2.7
  Partial
  DORA Article 25
  DORA lists vulnerability assessments and scans within the testing programme but does not set scanning scope or frequency for secure zone systems.
- Swift CSP Control 2.7
  Stricter
  DORA Article 10
  The RTS requires automated vulnerability scanning at least weekly for assets supporting critical or important functions, tracking of third-party libraries and verified remediation.

### Human resources security

**DORA asks more** from the mapping

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.6.1 to A.6.6

- Human resources policy
  Applies to: Financial entities, except those on the simplified framework
  A human resources policy covering ICT security.
  [DORA ICT Risk Management RTS, Article 19](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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

**How these map: 1 link**

- Swift CSP Control 5.3A
  Supports
  DORA Article 19
  The RTS human resources policy requires assigned security responsibilities and staff awareness of policies and reporting channels; it does not require screening.

### Physical and environmental security

**Partly overlap** from the mapping: see the gap notes

NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.7.1 to A.7.14

- Physical and environmental security
  Applies to: Financial entities, except those on the simplified framework
  A physical and environmental security policy.
  [DORA ICT Risk Management RTS, Article 18](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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

**How these map: 1 link**

- Swift CSP Control 3.1
  Partial
  DORA Article 18
  The RTS requires a physical and environmental security policy for premises, data centres and sensitive areas, and Article 21 adds logged, monitored and reviewed physical access; neither names Swift tokens or HSMs.

## Detection and response

### Monitoring and detection

**Partly overlap** from the mapping: see the gap notes

NIST CSF 2.0 DE.CM, DE.AE · ISO/IEC 27001:2022 A.8.15, A.8.16

- Detect anomalous activity
  Mechanisms to detect anomalous activity promptly, with several layers of control, alert thresholds and automatic alerts, tested regularly.
  [DORA, Article 10](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Logging
  Applies to: Financial entities, except those on the simplified framework
  Logging procedures, protocols and tools: what is logged, how logs are protected and how long they are kept.
  [DORA ICT Risk Management RTS, Article 12](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Incident management and detection
  Applies to: Financial entities, except those on the simplified framework
  An ICT-related incident management policy, and criteria to detect anomalous activity and trigger incident response.
  [DORA ICT Risk Management RTS, Articles 22 and 23](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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

**How these map: 6 links**

- Swift CSP Control 6.1
  Supports
  DORA Article 10
  DORA adds mechanisms to detect anomalous activity in general, of which malware detection is only one part.
- Swift CSP Control 6.4
  Partial
  DORA Article 10
  DORA requires prompt detection of anomalous activity with alert thresholds and multiple layers of control, but does not specify log retention or log review for Swift components.
- Swift CSP Control 6.4
  Stricter
  DORA Article 12
  The RTS requires logging procedures that define the events, retention and protection of logs, cover access control, change management, ICT operations and network traffic, detect logging failures and synchronise clocks.
- Swift CSP Control 6.4
  Partial
  DORA Articles 22 and 23
  The RTS requires mechanisms for the prompt detection of anomalous activities and behaviours, with criteria and thresholds.
- Swift CSP Control 6.5A
  Partial
  DORA Article 10
  DORA requires detection of anomalous activity including network performance issues but does not expressly require intrusion detection on the network reaching the Swift components.
- Swift CSP Control 6.5A
  Partial
  DORA Articles 22 and 23
  The RTS requires detection of anomalous activities, including network performance issues, as part of incident management.

### Incident handling

**DORA more detailed** more requirements on this, not necessarily stricter

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

- Post-incident reviews
  A review after a major ICT-related incident disrupts core activities, to find the causes and the improvements needed.
  [DORA, Article 13(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Incident management process
  A process to detect, manage and notify ICT-related incidents: record all incidents and significant cyber threats, assign roles, escalate, and find and fix root causes.
  [DORA, Article 17](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Incident management and detection
  Applies to: Financial entities, except those on the simplified framework
  An ICT-related incident management policy, and criteria to detect anomalous activity and trigger incident response.
  [DORA ICT Risk Management RTS, Articles 22 and 23](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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

**How these map: 2 links**

- Swift CSP Control 7.1
  Partial
  DORA Article 17
  DORA adds incident detection, classification, root-cause analysis and reporting procedures, while the Swift control adds notification of Swift and plan testing at least every two years.
- Swift CSP Control 7.1
  Partial
  DORA Articles 22 and 23
  The RTS requires a documented ICT-related incident management policy with contacts, detection mechanisms, evidence retention and analysis of recurring incidents.

### Incident classification

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.MA · ISO/IEC 27001:2022 A.5.25

- Classify incidents
  Classify incidents by the clients affected, reputational impact, duration, geographical spread, data losses, critical services affected and economic impact. The thresholds are in Delegated Regulation (EU) 2024/1772.
  [DORA, Article 18(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

Nothing in the acts covered.

### Reporting to authorities

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5

- Report major incidents
  Report major ICT-related incidents to the competent authority, using the common templates.
  [DORA, Article 19(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Initial notification
  An initial notification once the incident is classified as major.
  [DORA, Article 19(4)(a); Delegated Regulation (EU) 2025/301, Article 5](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Intermediate report
  An intermediate report, updated when regular activities have been recovered.
  [DORA, Article 19(4)(b); Delegated Regulation (EU) 2025/301, Article 5](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Final report
  A final report once the root cause analysis is complete, whether or not mitigation is in place, and actual impact figures are available to replace estimates.
  [DORA, Article 19(4)(c); Delegated Regulation (EU) 2025/301, Article 5](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Voluntary notice of cyber threats Optional
  Significant cyber threats may be notified to the competent authority.
  [DORA, Article 19(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

Nothing in the acts covered.

### Informing customers and the public

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.CO, RC.CO

- Crisis communication
  Crisis communication plans to disclose major incidents or vulnerabilities to clients, counterparts and the public, and a person in charge of public and media communication.
  [DORA, Article 14](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Inform affected clients
  When a major incident affects clients' financial interests, inform them without undue delay of the incident and the measures taken.
  [DORA, Article 19(3)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

Nothing in the acts covered.

### Threat intelligence and information sharing

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.5.6, A.5.7

- Threat and vulnerability intelligence
  Capabilities and staff to gather information on vulnerabilities, cyber threats and incidents and to analyse their likely impact.
  [DORA, Article 13(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Information-sharing arrangements Optional
  Financial entities may exchange cyber threat information within trusted communities, under arrangements that protect confidentiality and personal data. They must tell the competent authority when they join or leave.
  [DORA, Article 45](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

Nothing in the acts covered.

## Continuity and resilience

### Business continuity and crisis management

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RC.RP, RC.CO · ISO/IEC 27001:2022 A.5.29, A.5.30

- ICT business continuity
  An ICT business continuity policy, response and recovery plans that are tested at least yearly and after substantive changes to systems supporting critical or important functions, and a business impact analysis.
  [DORA, Article 11](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- ICT business continuity
  Applies to: Financial entities, except those on the simplified framework
  The components of the ICT business continuity policy, the testing of continuity plans, and ICT response and recovery plans.
  [DORA ICT Risk Management RTS, Articles 24 to 26](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Business continuity (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  An ICT business continuity plan and its testing.
  [DORA ICT Risk Management RTS, Articles 39 and 40](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

Nothing in the acts covered.

### Backup and recovery

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.DS, RC.RP · ISO/IEC 27001:2022 A.8.13, A.8.14

- Backup and restoration
  Backup policies setting scope and minimum frequency, restoration on own systems segregated from the source, periodic testing, and redundant ICT capacity (microenterprises assess the need based on their risk profile).
  [DORA, Article 12](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

Nothing in the acts covered.

### Security testing

**DORA 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

- Resilience testing programme
  A risk-based testing programme run by independent testers, with all ICT systems and applications supporting critical or important functions tested at least yearly. Not required of microenterprises.
  [DORA, Article 24](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Tests to run
  Appropriate tests such as vulnerability assessments and scans, network security assessments, source code reviews where feasible, scenario-based tests and penetration tests.
  [DORA, Article 25](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Security testing (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT security testing.
  [DORA ICT Risk Management RTS, Article 36](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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

**How these map: 1 link**

- Swift CSP Control 7.3A
  Partial
  DORA Article 25
  DORA lists penetration testing within a broader testing programme but does not fix its scope to the secure zone, operator PCs or jump servers.

### Threat-led penetration testing

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.IM

- Threat-led penetration testing
  Entities identified by the competent authority, other than microenterprises and Article 16(1) entities, run threat-led penetration tests on live production systems. Details are in Delegated Regulation (EU) 2025/1190.
  [DORA, Article 26(1), (2) and (8)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

Nothing in the acts covered.

## Third parties and supply chain

### Supplier and third-party risk

**Partly overlap** from the mapping: see the gap notes

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

- Manage ICT third-party risk
  ICT third-party risk is managed within the ICT risk management framework, and the entity stays fully responsible for compliance.
  [DORA, Article 28(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Third-party risk strategy
  A regularly reviewed strategy on ICT third-party risk, with a policy on ICT services supporting critical or important functions. The management body regularly reviews the risks from those arrangements. Not required of microenterprises or Article 16 entities.
  [DORA, Article 28(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

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

**How these map: 1 link**

- Swift CSP Control 2.8
  Partial
  DORA Article 28(1)
  DORA adds a full third-party risk framework, register of information and exit strategies, but does not require outsourced activities to meet the CSCF.

### Contract requirements

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.20

- Minimum contract terms
  Contracts set out the services, locations of service and data, data protection, access and return of data, service levels, incident assistance, cooperation with authorities, termination rights and participation in training.
  [DORA, Article 30(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Terms for critical or important functions
  Contracts for services supporting critical or important functions add full service level descriptions, notice periods, business contingency plans, participation in TLPT, unrestricted rights of access, inspection and audit (microenterprises may agree to delegate these to an independent third party), and exit strategies with a transition period.
  [DORA, Article 30(3)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

Nothing in the acts covered.

### Register of third-party arrangements

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.SC

- Register of information
  A register of all contractual arrangements for ICT services, at entity, sub-consolidated and consolidated level, given to the competent authority on request, with a report at least yearly on new arrangements and timely notice of planned arrangements supporting critical or important functions.
  [DORA, Article 28(3)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

Nothing in the acts covered.

### Exit and termination

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.SC

- Exit strategies
  Exit strategies for ICT services supporting critical or important functions, covering provider failure, falling quality and business disruption.
  [DORA, Article 28(8)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

Nothing in the acts covered.

## Supervision and enforcement

### Penalties and liability

**Only DORA** no specific requirement on the other side in the acts covered

- Administrative penalties
  Applies to: Competent authorities and Member States
  Competent authorities have supervisory, investigatory and sanctioning powers; Member States set the administrative penalties and remedial measures.
  [DORA, Article 50](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

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.

Full Mapping

## Get the Complete Table as a Spreadsheet

All 69 links, ready to filter, extend with your own controls and use as the starting point of a gap analysis.

## More Comparisons

- [Compare DORA](https://grc.plus/compare/dora/)
- [Compare Swift CSP](https://grc.plus/compare/swift-csp/)

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