DORA vs PCI DSS
Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.
At a Glance
They differ on 24 of 34 topics. Each verdict names what it rests on; read the wording before relying on it.
- DORA Asks more on 0 topics Alone on 14 topics More detailed on 5 topics
- PCI DSS Asks more on 0 topics Alone on 1 topic More detailed on 4 topics
| Topic | DORA | PCI DSS | Verdict |
|---|---|---|---|
| Governance | |||
| Management accountability | DORA: 3 | PCI DSS: 1 | DORA more detailedmore requirements on this, not necessarily stricter |
| Roles and independence | DORA: 1 | PCI DSS: – | Only DORAno specific requirement on the other side in the acts covered |
| Security policy | DORA: 3 | PCI DSS: 2 | Both cover itread the wording below |
| Awareness and training | DORA: 2 | PCI DSS: 2 | Both cover itread the wording below |
| Risk management | |||
| Risk management framework | DORA: 2 | PCI DSS: – | Only DORAno specific requirement on the other side in the acts covered |
| Risk assessment | DORA: 3 | PCI DSS: 1 | DORA more detailedmore requirements on this, not necessarily stricter |
| Review, audit and improvement | DORA: 4 | PCI DSS: – | Only DORAno specific requirement on the other side in the acts covered |
| Asset management | DORA: 3 | PCI DSS: 1 | DORA more detailedmore requirements on this, not necessarily stricter |
| Protection | |||
| Access control | DORA: 3 | PCI DSS: 4 | Both cover itread the wording below |
| Authentication | DORA: 2 | PCI DSS: 5 | PCI DSS more detailedmore requirements on this, not necessarily stricter |
| Cryptography and encryption | DORA: 2 | PCI DSS: 3 | Both cover itread the wording below |
| Data security | DORA: 3 | PCI DSS: 4 | Both cover itread the wording below |
| Network security | DORA: 3 | PCI DSS: 7 | PCI DSS more detailedmore requirements on this, not necessarily stricter |
| Secure communications | DORA: – | PCI DSS: 2 | Only PCI DSSno specific requirement on the other side in the acts covered |
| Secure acquisition and development | DORA: 2 | PCI DSS: 3 | Both cover itread the wording below |
| Configuration, change and patch management | DORA: 5 | PCI DSS: 1 | DORA more detailedmore requirements on this, not necessarily stricter |
| Vulnerability handling | DORA: 3 | PCI DSS: 4 | Both cover itread the wording below |
| Human resources security | DORA: 1 | PCI DSS: 1 | Both cover itread the wording below |
| Physical and environmental security | DORA: 1 | PCI DSS: 5 | PCI DSS more detailedmore requirements on this, not necessarily stricter |
| Detection and response | |||
| Monitoring and detection | DORA: 3 | PCI DSS: 12 | PCI DSS more detailedmore requirements on this, not necessarily stricter |
| Incident handling | DORA: 3 | PCI DSS: 1 | DORA more detailedmore requirements on this, not necessarily stricter |
| Incident classification | DORA: 1 | PCI DSS: – | Only DORAno specific requirement on the other side in the acts covered |
| Reporting to authorities | DORA: 5 | PCI DSS: – | Only DORAno specific requirement on the other side in the acts covered |
| Informing customers and the public | DORA: 2 | PCI DSS: – | Only DORAno specific requirement on the other side in the acts covered |
| Threat intelligence and information sharing | DORA: 2 | PCI DSS: – | Only DORAno specific requirement on the other side in the acts covered |
| Continuity and resilience | |||
| Business continuity and crisis management | DORA: 3 | PCI DSS: – | Only DORAno specific requirement on the other side in the acts covered |
| Backup and recovery | DORA: 1 | PCI DSS: – | Only DORAno specific requirement on the other side in the acts covered |
| Security testing | DORA: 3 | PCI DSS: 2 | Both cover itread the wording below |
| Threat-led penetration testing | DORA: 1 | PCI DSS: – | Only DORAno specific requirement on the other side in the acts covered |
| Third parties and supply chain | |||
| Supplier and third-party risk | DORA: 2 | PCI DSS: 2 | Both cover itread the wording below |
| Contract requirements | DORA: 2 | PCI DSS: – | Only DORAno specific requirement on the other side in the acts covered |
| Register of third-party arrangements | DORA: 1 | PCI DSS: – | Only DORAno specific requirement on the other side in the acts covered |
| Exit and termination | DORA: 1 | PCI DSS: – | Only DORAno specific requirement on the other side in the acts covered |
| Supervision and enforcement | |||
| Penalties and liability | DORA: 1 | PCI DSS: – | 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
- DORA ICT Risk Management RTS Commission Delegated Regulation (EU) 2024/1774 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
Not yet included
- DORA Third-Party Policy RTS
- DORA Subcontracting RTS
- DORA Register of Information ITS
- DORA Incident Classification RTS
- DORA Incident Reporting RTS
- DORA Incident Reporting ITS
- DORA TLPT RTS
- DORA Critical Provider Criteria
- DORA Oversight Conditions RTS
Status
Reviewed against the official texts.
Key Numbers
Incident reports go to
DORA: Financial supervisor (competent authority)
PCI DSS: 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
PCI DSS: Not in the acts covered
Intermediate report
DORA: Within 72 hours of the initial notification
PCI DSS: Not in the acts covered
Final report
DORA: Within one month of the latest intermediate report
PCI DSS: 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
PCI DSS: 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.
PCI DSS: 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
PCI DSS: Not in the acts covered
Register of third-party arrangements
DORA: Required, for every ICTInformation and Communication Technology service arrangement
PCI DSS: Not in the acts covered
Management body training
DORA: Required, on a regular basis
PCI DSS: 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))
PCI DSS: Not in the acts covered
Maximum fines
DORA: Set by each Member State (Competent authorities and Member States)
PCI DSS: Not in the acts covered
Governance
Management accountability
DORA more detailed more requirements on this, not necessarily stricter
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..
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.
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.
PCI DSS compliance is managed
PCI DSSPayment Card Industry Data Security Standard compliance is managed.
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.
Nothing in the acts covered.
Security policy
Both cover it read the wording below
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.
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.
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.
A comprehensive information security policy that governs and provides direction for protection of the entity's information assets is known and current
A comprehensive 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 that governs and provides direction for protection of the entity's information assets is known and current.
Acceptable use policies for end-user technologies are defined and implemented
Acceptable use policies for end-user technologies are defined and implemented.
Awareness and training
Both cover it read the wording below
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.
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.
Anti-phishing mechanisms protect users against phishing attacks
Anti-phishing mechanisms protect users against phishingAn attack that impersonates a trusted person or organisation through electronic communications, often an email or a fake website, to trick someone into revealing information such as passwords or bank details. The attacker uses apparent familiarity or credibility to persuade the person to respond. Training simulations practise recognising these deceptive requests. attacks.
Security awareness education is an ongoing activity
Security awareness education is an ongoing activity.
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.
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.
Nothing in the acts covered.
Risk assessment
DORA more detailed more requirements on this, not necessarily stricter
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.
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..
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..
Risks to the cardholder data environment are formally identified, evaluated, and managed
Risks to the cardholder data environmentThe system components, people and processes that store, process or transmit cardholder data or sensitive authentication data, plus components with unrestricted connectivity to them. Defining the CDE sets the scope of a PCI DSS assessment. are formally identified, evaluated, and managed.
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.
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.
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.
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.
Nothing in the acts covered.
Asset management
DORA more detailed more requirements on this, not necessarily stricter
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.
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.
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.
PCI DSS scope is documented and validated
PCI DSSPayment Card Industry Data Security Standard scope is documented and validated.
Protection
Access control
Both cover it read the wording below
NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.15, A.5.18, A.8.2, A.8.3
Limit access
Limit physical and logical access to what legitimate and approved functions need, with policies, procedures and controls for access rights.
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..
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..
Processes and mechanisms for restricting access to system components and cardholder data by business need to know are defined and understood
Processes and mechanisms for restricting access to system components and cardholder dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment. by business need to know are defined and understood.
Access to system components and data is appropriately defined and assigned
Access to system components and data is appropriately defined and assigned.
Access to system components and data is managed via an access control system(s)
Access to system components and data is managed via an 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. system(s).
User identification and related accounts for users and administrators are strictly managed throughout an account's lifecycle
User identification and related accounts for users and administrators are strictly managed throughout an account's lifecycle.
Authentication
PCI DSS more detailed more requirements on this, not necessarily stricter
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..
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..
Processes and mechanisms for identifying users and authenticating access to system components are defined and understood
Processes and mechanisms for identifying users and authenticating access to system components are defined and understood.
Strong authentication for users and administrators is established and managed
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. for users and administrators is established and managed.
Multi-factor authentication (MFA) is implemented to secure access into the CDE
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. (MFA) is implemented to secure access into the CDECardholder Data Environment.
Multi-factor authentication (MFA) systems are configured to prevent misuse
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. (MFA) systems are configured to prevent misuse.
Use of application and system accounts and associated authentication factors is strictly managed
Use of application and system accounts and associated 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. factors is strictly managed.
Cryptography and encryption
Both cover it read the wording below
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..
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.
Primary account number (PAN) is secured wherever it is stored
Primary account numberThe unique payment card number that identifies the card issuer and the cardholder account, used on credit, debit and prepaid cards. Under PCI DSS the full PAN is the minimum element of cardholder data, so where it is stored, processed or transmitted drives the scope of an assessment. (PAN) is secured wherever it is stored.
Cryptographic keys used to protect stored account data are secured
Cryptographic keys used to protect stored account dataThe PCI DSS umbrella term for cardholder data, sensitive authentication data or both. PCI DSS requirements apply to every system component that stores, processes or transmits account data, or that could affect its security. are secured.
Where cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented
Where cryptographyThe use of mathematical methods to protect information and provide evidence that it can be trusted. Cryptography can hide information, detect changes and help verify where information came from. Encryption, which makes readable information unintelligible without the means to decrypt it, is one use of cryptography. The broader discipline also supports integrity checks and digital signatures. is used to protect stored account dataThe PCI DSS umbrella term for cardholder data, sensitive authentication data or both. PCI DSS requirements apply to every system component that stores, processes or transmits account data, or that could affect its security., key management processes and procedures covering all aspects of the key lifecycle are defined and implemented.
Data security
Both cover it read the wording below
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.
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.
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.
Processes and mechanisms for protecting stored account data are defined and understood
Processes and mechanisms for protecting stored account dataThe PCI DSS umbrella term for cardholder data, sensitive authentication data or both. PCI DSS requirements apply to every system component that stores, processes or transmits account data, or that could affect its security. are defined and understood.
Storage of account data is kept to a minimum
Storage of account dataThe PCI DSS umbrella term for cardholder data, sensitive authentication data or both. PCI DSS requirements apply to every system component that stores, processes or transmits account data, or that could affect its security. is kept to a minimum.
Sensitive authentication data (SAD) is not stored after authorization
Sensitive authentication dataSecurity-related information used to authenticate cardholders or authorise payment card transactions, such as card verification codes, full track data, PINs and PIN blocks. Together with cardholder data it makes up account data under PCI DSS. (SAD) is not stored after authorization.
Access to displays of full PAN and ability to copy PAN are restricted
Access to displays of full PANPrimary Account Number and ability to copy PANPrimary Account Number are restricted.
Network security
PCI DSS more detailed more requirements on this, not necessarily stricter
NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.8.20 to A.8.22
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.
Network security
Applies to: Financial entities, except those on the simplified framework
Network security management and the protection of information in transit.
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.
Processes and mechanisms for installing and maintaining network security controls are defined and understood
Processes and mechanisms for installing and maintaining network security controls are defined and understood.
Network security controls (NSCs) are configured and maintained
Network security controls (NSCs) are configured and maintained.
Network access to and from the cardholder data environment is restricted
Network access to and from the cardholder data environmentThe system components, people and processes that store, process or transmit cardholder data or sensitive authentication data, plus components with unrestricted connectivity to them. Defining the CDE sets the scope of a PCI DSS assessment. is restricted.
Network connections between trusted and untrusted networks are controlled
Network connections between trusted and untrusted networks are controlled.
Risks to the CDE from computing devices that are able to connect to both untrusted networks and the CDE are mitigated
Risks to the CDECardholder Data Environment from computing devices that are able to connect to both untrusted networks and the CDECardholder Data Environment are mitigated.
Wireless environments are configured and managed securely
Wireless environments are configured and managed securely.
Wireless access points are identified and monitored, and unauthorized wireless access points are addressed
Wireless access points are identified and monitored, and unauthorized wireless access points are addressed.
Secure communications
Only PCI DSS 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.
Processes and mechanisms for protecting cardholder data with strong cryptography during transmission over open, public networks are defined and understood
Processes and mechanisms for protecting cardholder dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment. with strong cryptographyThe use of mathematical methods to protect information and provide evidence that it can be trusted. Cryptography can hide information, detect changes and help verify where information came from. Encryption, which makes readable information unintelligible without the means to decrypt it, is one use of cryptography. The broader discipline also supports integrity checks and digital signatures. during transmission over open, public networks are defined and understood.
PAN is protected with strong cryptography during transmission
PANPrimary Account Number is protected with strong cryptographyThe use of mathematical methods to protect information and provide evidence that it can be trusted. Cryptography can hide information, detect changes and help verify where information came from. Encryption, which makes readable information unintelligible without the means to decrypt it, is one use of cryptography. The broader discipline also supports integrity checks and digital signatures. during transmission.
Secure acquisition and development
Both cover it read the wording below
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.
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.
Processes and mechanisms for developing and maintaining secure systems and software are defined and understood
Processes and mechanisms for developing and maintaining secure systems and software are defined and understood.
Bespoke and custom software are developed securely
Bespoke and custom software are developed securely.
Public-facing web applications are protected against attacks
Public-facing web applications are protected against attacks.
Configuration, change and patch management
DORA more detailed more requirements on this, not necessarily stricter
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.
Patches and updates
Documented policies for patches and updates.
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.
ICT change management
Applies to: Financial entities, except those on the simplified framework
ICTInformation and Communication Technology change management procedures.
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.
Changes to all system components are managed securely
Changes to all system components are managed securely.
Vulnerability handling
Both cover it read the wording below
NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.8.8
Patches and updates
Documented policies for patches and updates.
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.
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.
Processes and mechanisms for applying secure configurations to all system components are defined and understood
Processes and mechanisms for applying secure configurations to all system components are defined and understood.
System components are configured and managed securely
System components are configured and managed securely.
Security vulnerabilities are identified and addressed
Security 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. are identified and addressed.
External and internal vulnerabilities are regularly identified, prioritized, and addressed
External and internal 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. are regularly identified, prioritized, and addressed.
Human resources security
Both cover it read the wording below
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.
Personnel are screened to reduce risks from insider threats
Personnel are screened to reduce risks from insider threats.
Physical and environmental security
PCI DSS more detailed more requirements on this, not necessarily stricter
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.
Processes and mechanisms for restricting physical access to cardholder data are defined and understood
Processes and mechanisms for restricting physical access to cardholder dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment. are defined and understood.
Physical access controls manage entry into facilities and systems containing cardholder data
Physical access controls manage entry into facilities and systems containing cardholder dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment..
Physical access for personnel and visitors is authorized and managed
Physical access for personnel and visitors is authorized and managed.
Media with cardholder data is securely stored, accessed, distributed, and destroyed
Media with cardholder dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment. is securely stored, accessed, distributed, and destroyed.
Point-of-interaction (POI) devices are protected from tampering and unauthorized substitution
Point-of-interaction (POI) devices are protected from tampering and unauthorized substitution.
Detection and response
Monitoring and detection
PCI DSS more detailed more requirements on this, not necessarily stricter
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.
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.
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..
Processes and mechanisms for protecting all systems and networks from malicious software are defined and understood
Processes and mechanisms for protecting all systems and networks from malicious softwareSoftware or firmware deliberately designed to harm a computer system or the information it holds. Malware can steal or destroy data, change information without permission, spy on activity or stop systems working. Examples include viruses, worms and spyware. Screening email or uploads for malware means looking for this harmful code before it can affect people or systems. are defined and understood.
Malicious software (malware) is prevented, or detected and addressed
Malicious software (malware) is prevented, or detected and addressed.
Anti-malware mechanisms and processes are active, maintained, and monitored
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. mechanisms and processes are active, maintained, and monitored.
Processes and mechanisms for logging and monitoring all access to system components and cardholder data are defined and understood
Processes and mechanisms for logging and monitoring all access to system components and cardholder dataUnder PCI DSS, the payment card data that must be protected: at a minimum the full primary account number, which may be accompanied by the cardholder name, expiration date or service code. Where cardholder data is stored, processed or transmitted defines the scope of a PCI DSS assessment. are defined and understood.
Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events
Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
Audit logs are protected from destruction and unauthorized modifications
Audit logs are protected from destruction and unauthorized modifications.
Audit logs are reviewed to identify anomalies or suspicious activity
Audit logs are reviewed to identify anomalies or suspicious activity.
Audit log history is retained and available for analysis
Audit log history is retained and available for analysis.
Time-synchronization mechanisms support consistent time settings across all systems
Time-synchronization mechanisms support consistent time settings across all systems.
Failures of critical security control systems are detected, reported, and responded to promptly
Failures of critical security control systems are detected, reported, and responded to promptly.
Network intrusions and unexpected file changes are detected and responded to
Network intrusions and unexpected file changes are detected and responded to.
Unauthorized changes on payment pages are detected and responded to
Unauthorized changes on payment pages are detected and responded to.
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.
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.
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..
Suspected and confirmed security incidents that could impact the CDE are responded to immediately
Suspected and confirmed security incidents that could impact the CDECardholder Data Environment are responded to immediately.
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.
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.
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.
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.
Inform affected clients
When a major incident affects clients' financial interests, inform them without undue delay of the incident and the measures taken.
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.
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.
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..
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.
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.
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).
Nothing in the acts covered.
Security testing
Both cover it read the wording below
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.
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.
Security testing (simplified)
Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)
ICTInformation and Communication Technology security testing.
Processes and mechanisms for regularly testing security of systems and networks are defined and understood
Processes and mechanisms for regularly testing security of systems and networks are defined and understood.
External and internal penetration testing is regularly performed, and exploitable vulnerabilities and security weaknesses are corrected
External and internal penetration testingA security assessment in which authorised testers simulate attacks on an application, system or network to find weaknesses that could actually be exploited. Testing takes place within agreed limits, such as the systems included and the techniques permitted. It can reveal how several weaknesses combine to give an attacker greater access, helping an organisation understand and correct the resulting exposure. is regularly performed, and exploitable 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 security weaknesses are corrected.
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.
Nothing in the acts covered.
Third parties and supply chain
Supplier and third-party risk
Both cover it read the wording below
NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.19, A.5.21 to A.5.23
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.
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.
Risk to information assets associated with third-party service provider (TPSP) relationships is managed
Risk to information assets associated with third-party service provider (TPSP) relationships is managed.
Third-party service providers (TPSPs) support their customers' PCI DSS compliance
Third-party service providers (TPSPs) support their customers' PCI DSSPayment Card Industry Data Security Standard compliance.
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.
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.
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..
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.
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.
Nothing in the acts covered.
Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022.
More Comparisons
Subject to more than one?
We run one control set for both, without doing the work twice. Ask what that saves you.