> DORA vs PCI DSS side by side, topic by topic: where they overlap, where they differ and which asks more, with incident deadlines, testing, third parties and fines.

# DORA vs PCI DSS

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

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

[PCI DSS](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/)Entities that store, process or transmit account data, or can affect its security

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

## What This Covers

The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.

Included

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

Not yet included

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

Status

Reviewed against the official texts.

Included

- [PCI DSS](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/) PCI DSS v4.0.1 (June 2024) 63 requirements

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 microenterprises), 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 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 ICT 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 risk; 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 risk management framework, and bears ultimate responsibility for managing ICT risk.
  [DORA, Article 5(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Budget for resilience
  The management body allocates and reviews the budget for digital operational resilience, including awareness programmes, training and ICT skills for all staff.
  [DORA, Article 5(2)(g)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Governance (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  Governance and organisation of the simplified ICT risk management framework.
  [DORA ICT Risk Management RTS, Article 28](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- PCI DSS compliance is managed
  PCI DSS compliance is managed.
  [PCI DSS, Requirement 12.4](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### Roles and independence

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

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

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

Nothing in the acts covered.

### Security policy

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

- 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 security policy that governs and provides direction for protection of the entity's information assets is known and current.
  [PCI DSS, Requirement 12.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Acceptable use policies for end-user technologies are defined and implemented
  Acceptable use policies for end-user technologies are defined and implemented.
  [PCI DSS, Requirement 12.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### 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 risk up to date, including by following specific training regularly.
  [DORA, Article 5(4)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Staff awareness and training
  ICT security awareness programmes and digital operational resilience training are compulsory for all employees and senior management.
  [DORA, Article 13(6)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

- Anti-phishing mechanisms protect users against phishing attacks
  Anti-phishing mechanisms protect users against phishing attacks.
  [PCI DSS, Requirement 5.4](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Security awareness education is an ongoing activity
  Security awareness education is an ongoing activity.
  [PCI DSS, Requirement 12.6](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

## Risk management

### Risk management framework

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

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

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

Nothing in the acts covered.

### Risk assessment

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

- Risks to the cardholder data environment are formally identified, evaluated, and managed
  Risks to the cardholder data environment are formally identified, evaluated, and managed.
  [PCI DSS, Requirement 12.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### Review, audit and improvement

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

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

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

Nothing in the acts covered.

### Asset management

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

- PCI DSS scope is documented and validated
  PCI DSS scope is documented and validated.
  [PCI DSS, Requirement 12.5](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

## 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.
  [DORA, Article 9(4)(c)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Identity management and access control
  Applies to: Financial entities, except those on the simplified framework
  Identity management and access control policies, including authentication.
  [DORA ICT Risk Management RTS, Articles 20 and 21](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Access control (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  Access control.
  [DORA ICT Risk Management RTS, Article 33](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- 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 data by business need to know are defined and understood.
  [PCI DSS, Requirement 7.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Access to system components and data is appropriately defined and assigned
  Access to system components and data is appropriately defined and assigned.
  [PCI DSS, Requirement 7.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- 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 control system(s).
  [PCI DSS, Requirement 7.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- 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.
  [PCI DSS, Requirement 8.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

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

- 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.
  [PCI DSS, Requirement 8.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Strong authentication for users and administrators is established and managed
  Strong authentication for users and administrators is established and managed.
  [PCI DSS, Requirement 8.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Multi-factor authentication (MFA) is implemented to secure access into the CDE
  Multi-factor authentication (MFA) is implemented to secure access into the CDE.
  [PCI DSS, Requirement 8.4](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Multi-factor authentication (MFA) systems are configured to prevent misuse
  Multi-factor authentication (MFA) systems are configured to prevent misuse.
  [PCI DSS, Requirement 8.5](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Use of application and system accounts and associated authentication factors is strictly managed
  Use of application and system accounts and associated authentication factors is strictly managed.
  [PCI DSS, Requirement 8.6](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

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

- Primary account number (PAN) is secured wherever it is stored
  Primary account number (PAN) is secured wherever it is stored.
  [PCI DSS, Requirement 3.5](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Cryptographic keys used to protect stored account data are secured
  Cryptographic keys used to protect stored account data are secured.
  [PCI DSS, Requirement 3.6](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- 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 cryptography is used to protect stored account data, key management processes and procedures covering all aspects of the key lifecycle are defined and implemented.
  [PCI DSS, Requirement 3.7](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### 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.
  [DORA, Article 9(2) and (3)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- ICT operations and data security
  Applies to: Financial entities, except those on the simplified framework
  Policies and procedures for ICT operations, capacity and performance management, and data and system security.
  [DORA ICT Risk Management RTS, Articles 8, 9 and 11](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Operations, data and network security (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT operations security, and data, system and network security.
  [DORA ICT Risk Management RTS, Articles 34 and 35](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Processes and mechanisms for protecting stored account data are defined and understood
  Processes and mechanisms for protecting stored account data are defined and understood.
  [PCI DSS, Requirement 3.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Storage of account data is kept to a minimum
  Storage of account data is kept to a minimum.
  [PCI DSS, Requirement 3.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Sensitive authentication data (SAD) is not stored after authorization
  Sensitive authentication data (SAD) is not stored after authorization.
  [PCI DSS, Requirement 3.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Access to displays of full PAN and ability to copy PAN are restricted
  Access to displays of full PAN and ability to copy PAN are restricted.
  [PCI DSS, Requirement 3.4](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### 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.
  [DORA, Article 9(4)(b)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Network security
  Applies to: Financial entities, except those on the simplified framework
  Network security management and the protection of information in transit.
  [DORA ICT Risk Management RTS, Articles 13 and 14](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Operations, data and network security (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT operations security, and data, system and network security.
  [DORA ICT Risk Management RTS, Articles 34 and 35](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- 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.
  [PCI DSS, Requirement 1.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Network security controls (NSCs) are configured and maintained
  Network security controls (NSCs) are configured and maintained.
  [PCI DSS, Requirement 1.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Network access to and from the cardholder data environment is restricted
  Network access to and from the cardholder data environment is restricted.
  [PCI DSS, Requirement 1.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Network connections between trusted and untrusted networks are controlled
  Network connections between trusted and untrusted networks are controlled.
  [PCI DSS, Requirement 1.4](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Risks to the CDE from computing devices that are able to connect to both untrusted networks and the CDE are mitigated
  Risks to the CDE from computing devices that are able to connect to both untrusted networks and the CDE are mitigated.
  [PCI DSS, Requirement 1.5](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Wireless environments are configured and managed securely
  Wireless environments are configured and managed securely.
  [PCI DSS, Requirement 2.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- 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.
  [PCI DSS, Requirement 11.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### 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 data with strong cryptography during transmission over open, public networks are defined and understood.
  [PCI DSS, Requirement 4.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- PAN is protected with strong cryptography during transmission
  PAN is protected with strong cryptography during transmission.
  [PCI DSS, Requirement 4.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### 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
  ICT project management, and the acquisition, development and maintenance of ICT systems.
  [DORA ICT Risk Management RTS, Articles 15 and 16](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Development and change (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT systems acquisition, development and maintenance, and ICT project and change management.
  [DORA ICT Risk Management RTS, Articles 37 and 38](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- 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.
  [PCI DSS, Requirement 6.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Bespoke and custom software are developed securely
  Bespoke and custom software are developed securely.
  [PCI DSS, Requirement 6.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Public-facing web applications are protected against attacks
  Public-facing web applications are protected against attacks.
  [PCI DSS, Requirement 6.4](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### 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.
  [DORA, Article 9(4)(e)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Patches and updates
  Documented policies for patches and updates.
  [DORA, Article 9(4)(f)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Vulnerability and patch management
  Applies to: Financial entities, except those on the simplified framework
  Procedures to identify and fix vulnerabilities and to apply patches and updates.
  [DORA ICT Risk Management RTS, Article 10](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- ICT change management
  Applies to: Financial entities, except those on the simplified framework
  ICT change management procedures.
  [DORA ICT Risk Management RTS, Article 17](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Development and change (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT systems acquisition, development and maintenance, and ICT project and change management.
  [DORA ICT Risk Management RTS, Articles 37 and 38](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Changes to all system components are managed securely
  Changes to all system components are managed securely.
  [PCI DSS, Requirement 6.5](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

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

- 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.
  [PCI DSS, Requirement 2.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- System components are configured and managed securely
  System components are configured and managed securely.
  [PCI DSS, Requirement 2.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Security vulnerabilities are identified and addressed
  Security vulnerabilities are identified and addressed.
  [PCI DSS, Requirement 6.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- External and internal vulnerabilities are regularly identified, prioritized, and addressed
  External and internal vulnerabilities are regularly identified, prioritized, and addressed.
  [PCI DSS, Requirement 11.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### 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 ICT security.
  [DORA ICT Risk Management RTS, Article 19](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Personnel are screened to reduce risks from insider threats
  Personnel are screened to reduce risks from insider threats.
  [PCI DSS, Requirement 12.7](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### 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.
  [DORA ICT Risk Management RTS, Article 18](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Processes and mechanisms for restricting physical access to cardholder data are defined and understood
  Processes and mechanisms for restricting physical access to cardholder data are defined and understood.
  [PCI DSS, Requirement 9.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Physical access controls manage entry into facilities and systems containing cardholder data
  Physical access controls manage entry into facilities and systems containing cardholder data.
  [PCI DSS, Requirement 9.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Physical access for personnel and visitors is authorized and managed
  Physical access for personnel and visitors is authorized and managed.
  [PCI DSS, Requirement 9.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Media with cardholder data is securely stored, accessed, distributed, and destroyed
  Media with cardholder data is securely stored, accessed, distributed, and destroyed.
  [PCI DSS, Requirement 9.4](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Point-of-interaction (POI) devices are protected from tampering and unauthorized substitution
  Point-of-interaction (POI) devices are protected from tampering and unauthorized substitution.
  [PCI DSS, Requirement 9.5](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

## 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.
  [DORA, Article 10](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Logging
  Applies to: Financial entities, except those on the simplified framework
  Logging procedures, protocols and tools: what is logged, how logs are protected and how long they are kept.
  [DORA ICT Risk Management RTS, Article 12](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Incident management and detection
  Applies to: Financial entities, except those on the simplified framework
  An ICT-related incident management policy, and criteria to detect anomalous activity and trigger incident response.
  [DORA ICT Risk Management RTS, Articles 22 and 23](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- 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 software are defined and understood.
  [PCI DSS, Requirement 5.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Malicious software (malware) is prevented, or detected and addressed
  Malicious software (malware) is prevented, or detected and addressed.
  [PCI DSS, Requirement 5.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Anti-malware mechanisms and processes are active, maintained, and monitored
  Anti-malware mechanisms and processes are active, maintained, and monitored.
  [PCI DSS, Requirement 5.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- 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 data are defined and understood.
  [PCI DSS, Requirement 10.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- 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.
  [PCI DSS, Requirement 10.2](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Audit logs are protected from destruction and unauthorized modifications
  Audit logs are protected from destruction and unauthorized modifications.
  [PCI DSS, Requirement 10.3](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Audit logs are reviewed to identify anomalies or suspicious activity
  Audit logs are reviewed to identify anomalies or suspicious activity.
  [PCI DSS, Requirement 10.4](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Audit log history is retained and available for analysis
  Audit log history is retained and available for analysis.
  [PCI DSS, Requirement 10.5](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Time-synchronization mechanisms support consistent time settings across all systems
  Time-synchronization mechanisms support consistent time settings across all systems.
  [PCI DSS, Requirement 10.6](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- 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.
  [PCI DSS, Requirement 10.7](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Network intrusions and unexpected file changes are detected and responded to
  Network intrusions and unexpected file changes are detected and responded to.
  [PCI DSS, Requirement 11.5](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Unauthorized changes on payment pages are detected and responded to
  Unauthorized changes on payment pages are detected and responded to.
  [PCI DSS, Requirement 11.6](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### Incident handling

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

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

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

- Suspected and confirmed security incidents that could impact the CDE are responded to immediately
  Suspected and confirmed security incidents that could impact the CDE are responded to immediately.
  [PCI DSS, Requirement 12.10](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### Incident classification

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

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

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

Nothing in the acts covered.

### Reporting to authorities

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

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

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

Nothing in the acts covered.

### Informing customers and the public

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

NIST CSF 2.0 RS.CO, RC.CO

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

Nothing in the acts covered.

### Threat intelligence and information sharing

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

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

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

Nothing in the acts covered.

## Continuity and resilience

### Business continuity and crisis management

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

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

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

Nothing in the acts covered.

### Backup and recovery

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

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

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

Nothing in the acts covered.

### Security testing

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

- 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.
  [PCI DSS, Requirement 11.1](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- External and internal penetration testing is regularly performed, and exploitable vulnerabilities and security weaknesses are corrected
  External and internal penetration testing is regularly performed, and exploitable vulnerabilities and security weaknesses are corrected.
  [PCI DSS, Requirement 11.4](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### Threat-led penetration testing

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

NIST CSF 2.0 ID.IM

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

Nothing in the acts covered.

## Third parties and supply chain

### Supplier and third-party risk

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

- 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.
  [PCI DSS, Requirement 12.8](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)
- Third-party service providers (TPSPs) support their customers' PCI DSS compliance
  Third-party service providers (TPSPs) support their customers' PCI DSS compliance.
  [PCI DSS, Requirement 12.9](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/#requirements)

### Contract requirements

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

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

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

Nothing in the acts covered.

### Register of third-party arrangements

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

NIST CSF 2.0 GV.SC

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

Nothing in the acts covered.

### Exit and termination

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

NIST CSF 2.0 GV.SC

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

Nothing in the acts covered.

## Supervision and enforcement

### Penalties and liability

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

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

Nothing in the acts covered.

Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022.

## More Comparisons

- [Compare DORA](https://grc.plus/compare/dora/)
- [Compare PCI DSS](https://grc.plus/compare/pci-dss/)

Source: https://grc.plus/compare/dora-vs-pci-dss/
