Incident to report to a regulator?Incident to report? Intake Line

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.

DORAFinancial entities

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

Status

Reviewed against the official texts.

Included

  • 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 microenterprisesMicroenterprise Under DORA), 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 functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these 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 ICTInformation and Communication Technology 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 riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment.; 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 riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management framework, and bears ultimate responsibility for managing ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment..

    DORA, Article 5(2)

  • Budget for resilience

    The management body allocates and reviews the budget for digital operational resilienceThe ability of a financial entity to build, assure and review its operational integrity and reliability by securing all the ICT capabilities it needs, directly or through ICT third-party service providers, so that it can keep providing financial services, including during disruptions. It is the overall goal of DORA., including awareness programmes, training and ICTInformation and Communication Technology skills for all staff.

    DORA, Article 5(2)(g)

  • Governance (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    Governance and organisation of the simplified ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management framework.

    DORA ICT Risk Management RTS, Article 28

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 riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. (not required of microenterprisesMicroenterprise Under DORA). Risk management, control and internal audit functions are kept appropriately segregated and independent.

    DORA, Article 6(4)

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 availabilityThe information-security property that authorised people and systems can access and use information or services when needed, reliably and within an acceptable time. An outage or an attack that overwhelms a service can reduce availability even if no information is stolen or changed. In product security, this includes keeping essential functions accessible and usable., authenticity, integrity and 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. of data and assets, including customers' where applicable.

    DORA, Article 9(4)(a)

  • ICT security policies

    Applies to: Financial entities, except those on the simplified framework

    ICTInformation and Communication Technology 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

  • Information security policy (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    An information securityProtecting information and the systems that handle it so that only authorised people can access it, it remains accurate and complete, and it is available when needed. These aims are called confidentiality, integrity and availability. Information security combines organisational requirements, staff practices and technical safeguards to reduce risks such as disclosure, alteration, disruption or destruction. policy and measures.

    DORA ICT Risk Management RTS, Article 29

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 riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. up to date, including by following specific training regularly.

    DORA, Article 5(4)

  • Staff awareness and training

    ICTInformation and Communication Technology security awareness programmes and digital operational resilienceThe ability of a financial entity to build, assure and review its operational integrity and reliability by securing all the ICT capabilities it needs, directly or through ICT third-party service providers, so that it can keep providing financial services, including during disruptions. It is the overall goal of DORA. training are compulsory for all employees and senior management.

    DORA, Article 13(6)

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

    Swift CSP, Control 7.2

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 riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management framework within the overall risk management system, with the strategies, policies, procedures, protocols and tools to protect all information and ICTInformation and Communication Technology assets.

    DORA, Article 6(1) and (2)

  • Simplified ICT risk management framework

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    Small and non-interconnected investment firms, exempted payment and e-moneyElectronic 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)

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 riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. continuously, assess cyber threatsAny potential circumstance, event or action that could damage, disrupt or otherwise harm network and information systems, their users or other persons. NIS2, DORA, the CRA, the Network Code on Cybersecurity and the Cyber Solidarity Act all use this Cybersecurity Act definition. and 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 review risk scenarios at least yearly.

    DORA, Article 8(2)

  • ICT risk management policy

    Applies to: Financial entities, except those on the simplified framework

    A policy and procedures for ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management: risk toleranceAn organisation's or other actor's readiness to bear a risk in order to achieve its objectives. Risk tolerance can be shaped by legal or regulatory requirements and changes with context, so frameworks ask organisations to state it rather than prescribing it., identification, assessment and treatment of risks, and the monitoring of residual riskThe risk that remains after risk treatment has been applied. The NIST AI RMF notes that residual risk directly affects end users and affected communities, and asks system providers to document it so users understand the possible negative impacts..

    DORA ICT Risk Management RTS, Article 3

  • ICT risk management (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    Identification and management of ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment..

    DORA ICT Risk Management RTS, Article 31

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

    Swift CSP, Control 7.4A

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 microenterprisesMicroenterprise Under DORA), after major ICT-related incidentsAn ICT-related incident with a high adverse impact on the network and information systems that support critical or important functions of a financial entity. Financial entities must report it to their competent authority in initial, intermediate and final reports. and following supervisory instructions or conclusions from testing or audits, and improved continuously.

    DORA, Article 6(5)

  • Internal audit

    Auditors with sufficient ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. expertise audit the framework regularly, in line with the audit plan. Not required of microenterprisesMicroenterprise Under DORA.

    DORA, Article 6(6)

  • 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 riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management framework.

    DORA ICT Risk Management RTS, Article 27

  • Framework review report (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    The format and content of the report on the review of the simplified framework.

    DORA ICT Risk Management RTS, Article 41

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 ICTInformation and Communication Technology-supported business functions, information and ICTInformation and Communication Technology assets and their dependencies, and review the classification at least yearly.

    DORA, Article 8(1)

  • ICT asset management

    Applies to: Financial entities, except those on the simplified framework

    An ICTInformation and Communication Technology asset managementAsset Management in Information Security policy and procedure, including an inventory of assets and their criticality.

    DORA ICT Risk Management RTS, Articles 4 and 5

  • Asset classification (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    Classification of information assets and ICTInformation and Communication Technology assets.

    DORA ICT Risk Management RTS, Article 30

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)

  • Identity management and access control

    Applies to: Financial entities, except those on the simplified framework

    Identity management and access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements. policies, including 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..

    DORA ICT Risk Management RTS, Articles 20 and 21

  • Access control (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    Access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements..

    DORA ICT Risk Management RTS, Article 33

  • 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

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

    Swift CSP, Control 5.1

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 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. based on relevant standards, and protection of cryptographic keys, with encryptionEncryption changes readable information into an unreadable form using a mathematical method and a key, a value that controls the transformation. Decryption recovers the original information with the appropriate key. Encryption helps keep stored or transmitted data confidential, so people without the necessary key cannot readily read it. decided by data classification and risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change..

    DORA, Article 9(4)(d)

  • Identity management and access control

    Applies to: Financial entities, except those on the simplified framework

    Identity management and access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements. policies, including 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..

    DORA ICT Risk Management RTS, Articles 20 and 21

  • Password Policy

    Applies to: All types

    Make passwords resistant to common attacks through an enforced password policy.

    Swift CSP, Control 4.1

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

    Swift CSP, Control 4.2

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

    Swift CSP, Control 5.2

  • Password Repository Protection

    Applies to: All types

    Protect stored passwords, physical and logical, against disclosure.

    Swift CSP, Control 5.4

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 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. based on relevant standards, and protection of cryptographic keys, with encryptionEncryption changes readable information into an unreadable form using a mathematical method and a key, a value that controls the transformation. Decryption recovers the original information with the appropriate key. Encryption helps keep stored or transmitted data confidential, so people without the necessary key cannot readily read it. decided by data classification and risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change..

    DORA, Article 9(4)(d)

  • Encryption and key management

    Applies to: Financial entities, except those on the simplified framework

    EncryptionEncryption changes readable information into an unreadable form using a mathematical method and a key, a value that controls the transformation. Decryption recovers the original information with the appropriate key. Encryption helps keep stored or transmitted data confidential, so people without the necessary key cannot readily read it. and cryptographic controls, and the management of cryptographic keys through their whole life cycle.

    DORA ICT Risk Management RTS, Articles 6 and 7

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

    Swift CSP, Control 2.5A

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)

  • ICT operations and data security

    Applies to: Financial entities, except those on the simplified framework

    Policies and procedures for ICTInformation and Communication Technology operations, capacity and performance management, and data and system security.

    DORA ICT Risk Management RTS, Articles 8, 9 and 11

  • Operations, data and network security (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    ICTInformation and Communication Technology operations security, and data, system and network security.

    DORA ICT Risk Management RTS, Articles 34 and 35

  • 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

  • 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

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

    Swift CSP, Control 6.2

  • 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

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)

  • 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

  • Operations, data and network security (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    ICTInformation and Communication Technology operations security, and data, system and network security.

    DORA ICT Risk Management RTS, Articles 34 and 35

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

    Swift CSP, Control 1.1

  • 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

  • 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

  • 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

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

    Swift CSP, Control 2.1

  • 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

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

    Swift CSP, Control 2.6

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

    ICTInformation and Communication Technology project management, and the acquisition, development and maintenance of ICTInformation and Communication Technology systems.

    DORA ICT Risk Management RTS, Articles 15 and 16

  • Development and change (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    ICTInformation and Communication Technology systems acquisition, development and maintenance, and ICTInformation and Communication Technology project and change management.

    DORA ICT Risk Management RTS, Articles 37 and 38

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)

  • Patches and updates

    Documented policies for patches and updates.

    DORA, Article 9(4)(f)

  • Vulnerability and patch management

    Applies to: Financial entities, except those on the simplified framework

    Procedures to identify and fix 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 to apply patches and updates.

    DORA ICT Risk Management RTS, Article 10

  • ICT change management

    Applies to: Financial entities, except those on the simplified framework

    ICTInformation and Communication Technology change management procedures.

    DORA ICT Risk Management RTS, Article 17

  • Development and change (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    ICTInformation and Communication Technology systems acquisition, development and maintenance, and ICTInformation and Communication Technology project and change management.

    DORA ICT Risk Management RTS, Articles 37 and 38

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)

  • Tests to run

    Appropriate tests such as vulnerabilityA 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. assessments and scans, network security assessments, source code reviews where feasible, scenario-based tests and penetration tests.

    DORA, Article 25

  • Vulnerability and patch management

    Applies to: Financial entities, except those on the simplified framework

    Procedures to identify and fix 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 to apply patches and updates.

    DORA ICT Risk Management RTS, Article 10

  • 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

  • System Hardening

    Applies to: All types

    Harden operating systems, databases and network devices of the SwiftSociety for Worldwide Interbank Financial Telecommunication environment against attack.

    Swift CSP, Control 2.3

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

    Swift CSP, Control 2.7

  • Application Hardening

    Applies to: A1, A2, A3

    Harden the SwiftSociety for Worldwide Interbank Financial Telecommunication messaging and communication interfaces and related applications.

    Swift CSP, Control 2.10

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 ICTInformation and Communication Technology security.

    DORA ICT Risk Management RTS, Article 19

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

    Swift CSP, Control 5.3A

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 Security

    Applies to: All types

    Prevent unauthorised physical access to sensitive equipment, workplaces, tokens and storage media.

    Swift CSP, Control 3.1

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

  • 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

  • Incident management and detection

    Applies to: Financial entities, except those on the simplified framework

    An ICT-related incidentA single event or series of linked events, not planned by the financial entity, that compromises the security of network and information systems and adversely affects the availability, authenticity, integrity or confidentiality of data or the entity's services. DORA requires financial entities to record and classify every such incident. management policy, and criteria to detect anomalous activity and trigger incident responseThe coordinated work an organisation carries out to deal with a cybersecurity incident and limit its consequences. An incident is an event that compromises, or threatens to compromise, the security of systems or information. Response can include investigating what happened, containing the problem, removing its cause and restoring affected services. It helps reduce damage and return operations to a controlled state..

    DORA ICT Risk Management RTS, Articles 22 and 23

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

    Swift CSP, Control 6.1

  • Logging and Monitoring

    Applies to: All types

    Record security events and monitor them to detect anomalous activity and operations.

    Swift CSP, Control 6.4

  • 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

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 incidentAn ICT-related incident with a high adverse impact on the network and information systems that support critical or important functions of a financial entity. Financial entities must report it to their competent authority in initial, intermediate and final reports. disrupts core activities, to find the causes and the improvements needed.

    DORA, Article 13(2)

  • Incident management process

    A process to detect, manage and notify ICT-related incidentsA single event or series of linked events, not planned by the financial entity, that compromises the security of network and information systems and adversely affects the availability, authenticity, integrity or confidentiality of data or the entity's services. DORA requires financial entities to record and classify every such incident.: record all incidents and significant cyber threatsA cyber threat whose technical characteristics suggest it could have a severe impact on an organisation's systems or on the users of its services. NIS2 links the impact to considerable material or non-material damage; DORA links it to a possible major ICT-related incident., assign roles, escalate, and find and fix root causes.

    DORA, Article 17

  • Incident management and detection

    Applies to: Financial entities, except those on the simplified framework

    An ICT-related incidentA single event or series of linked events, not planned by the financial entity, that compromises the security of network and information systems and adversely affects the availability, authenticity, integrity or confidentiality of data or the entity's services. DORA requires financial entities to record and classify every such incident. management policy, and criteria to detect anomalous activity and trigger incident responseThe coordinated work an organisation carries out to deal with a cybersecurity incident and limit its consequences. An incident is an event that compromises, or threatens to compromise, the security of systems or information. Response can include investigating what happened, containing the problem, removing its cause and restoring affected services. It helps reduce damage and return operations to a controlled state..

    DORA ICT Risk Management RTS, Articles 22 and 23

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

    Swift CSP, Control 7.1

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)

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 incidentsAn ICT-related incident with a high adverse impact on the network and information systems that support critical or important functions of a financial entity. Financial entities must report it to their competent authority in initial, intermediate and final reports. to the competent authority, using the common templates.

    DORA, Article 19(1)

  • Initial notification

    An initial notification once the incident is classified as major.

    DORA, Article 19(4)(a); Delegated Regulation (EU) 2025/301, Article 5

  • Intermediate report

    An intermediate report, updated when regular activities have been recovered.

    DORA, Article 19(4)(b); Delegated Regulation (EU) 2025/301, Article 5

  • Final report

    A final report once the root cause analysisA structured investigation into the underlying causes of a problem or incident, rather than only its visible effects. For an IT incident, it examines how technical failures, working practices or other conditions combined to cause the disruption. The findings help an organisation choose corrective measures that address those causes and reduce the chance of recurrence. 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

  • Voluntary notice of cyber threats Optional

    Significant cyber threatsA cyber threat whose technical characteristics suggest it could have a severe impact on an organisation's systems or on the users of its services. NIS2 links the impact to considerable material or non-material damage; DORA links it to a possible major ICT-related incident. may be notified to the competent authority.

    DORA, Article 19(2)

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 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. to clients, counterparts and the public, and a person in charge of public and media communication.

    DORA, Article 14

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

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 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., cyber threatsAny potential circumstance, event or action that could damage, disrupt or otherwise harm network and information systems, their users or other persons. NIS2, DORA, the CRA, the Network Code on Cybersecurity and the Cyber Solidarity Act all use this Cybersecurity Act definition. and incidents and to analyse their likely impact.

    DORA, Article 13(1)

  • Information-sharing arrangements Optional

    Financial entities may exchange cyber threatAny potential circumstance, event or action that could damage, disrupt or otherwise harm network and information systems, their users or other persons. NIS2, DORA, the CRA, the Network Code on Cybersecurity and the Cyber Solidarity Act all use this Cybersecurity Act definition. information within trusted communities, under arrangements that protect 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. and personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity.. They must tell the competent authority when they join or leave.

    DORA, Article 45

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 ICTInformation and Communication Technology business continuityAn organisation's ability to keep delivering its products and services at an acceptable, previously agreed level during a disruption. The focus is on sustaining the activities customers and others depend on, even when normal operations are interrupted. A business continuity management system helps an organisation develop and maintain that capability; a business continuity plan records the arrangements for putting it into practice. policy, response and recovery plans that are tested at least yearly and after substantive changes to systems supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions., and a business impact analysisThe process of analysing operational functions and the effect a disruption might have on them. Its results inform recovery priorities in continuity planning..

    DORA, Article 11

  • ICT business continuity

    Applies to: Financial entities, except those on the simplified framework

    The components of the ICTInformation and Communication Technology business continuityAn organisation's ability to keep delivering its products and services at an acceptable, previously agreed level during a disruption. The focus is on sustaining the activities customers and others depend on, even when normal operations are interrupted. A business continuity management system helps an organisation develop and maintain that capability; a business continuity plan records the arrangements for putting it into practice. policy, the testing of continuity plans, and ICTInformation and Communication Technology response and recovery plans.

    DORA ICT Risk Management RTS, Articles 24 to 26

  • Business continuity (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    An ICTInformation and Communication Technology business continuity planThe documented, predetermined instructions or procedures that keep an organisation's core operations running during and after a significant disruption. DORA, for example, requires financial entities to have an ICT business continuity policy. and its testing.

    DORA ICT Risk Management RTS, Articles 39 and 40

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

    BackupA backup is a copy of files, programs or other information kept so they can be recovered when needed. If original records are lost, damaged or unavailable, a usable backup provides a source for restoring them. Backups can support recovery of business systems and health records. policies setting scope and minimum frequency, restoration on own systems segregated from the source, periodic testing, and redundant ICTInformation and Communication Technology capacity (microenterprisesMicroenterprise Under DORA assess the need based on their risk profile).

    DORA, Article 12

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 ICTInformation and Communication Technology systems and applications supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions. tested at least yearly. Not required of microenterprisesMicroenterprise Under DORA.

    DORA, Article 24

  • Tests to run

    Appropriate tests such as vulnerabilityA 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. assessments and scans, network security assessments, source code reviews where feasible, scenario-based tests and penetration tests.

    DORA, Article 25

  • Security testing (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    ICTInformation and Communication Technology security testing.

    DORA ICT Risk Management RTS, Article 36

  • Penetration Testing (advisory) Recommended

    Applies to: All types (advisory)

    Test the security of the SwiftSociety for Worldwide Interbank Financial Telecommunication environment through penetration tests.

    Swift CSP, Control 7.3A

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 microenterprisesMicroenterprise Under DORA 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)

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 riskIn the Digital Operational Resilience Act context, the technology risk a financial organisation faces when it uses Information and Communication Technology services supplied by another organisation or that supplier's subcontractors. This concerns the organisation's dependence on externally provided technology, including outsourced services. Managing it involves assessing suppliers, documenting service arrangements, setting suitable contract terms, monitoring risks and planning how to leave an arrangement while keeping services running. is managed within the ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management framework, and the entity stays fully responsible for compliance.

    DORA, Article 28(1)

  • Third-party risk strategy

    A regularly reviewed strategy on ICT third-party riskIn the Digital Operational Resilience Act context, the technology risk a financial organisation faces when it uses Information and Communication Technology services supplied by another organisation or that supplier's subcontractors. This concerns the organisation's dependence on externally provided technology, including outsourced services. Managing it involves assessing suppliers, documenting service arrangements, setting suitable contract terms, monitoring risks and planning how to leave an arrangement while keeping services running., with a policy on ICTInformation and Communication Technology services supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions.. The management body regularly reviews the risks from those arrangements. Not required of microenterprisesMicroenterprise Under DORA or Article 16 entities.

    DORA, Article 28(2)

  • 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

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)

  • Terms for critical or important functions

    Contracts for services supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions. add full service level descriptions, notice periods, business contingency plans, participation in TLPTThreat-Led Penetration Testing, unrestricted rights of access, inspection and audit (microenterprisesMicroenterprise Under DORA may agree to delegate these to an independent third party), and exit strategies with a transition period.

    DORA, Article 30(3)

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 ICTInformation and Communication Technology 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 functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions..

    DORA, Article 28(3)

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 ICTInformation and Communication Technology services supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions., covering provider failure, falling quality and business disruption.

    DORA, Article 28(8)

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

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.

We e-mail you a download link. Your details go to our CRM so a consultant can follow up about the mapping. Privacy notice

More Comparisons

Subject to more than one?

We run one control set for both, without doing the work twice. Ask what that saves you.

Loading the form…