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

GDPR vs PCI DSS

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

GDPRControllers and processors

PCI DSSEntities that store, process or transmit account data, or can affect its security

At a Glance

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

  • GDPR Asks more on 0 topics Alone on 16 topics More detailed on 0 topics
  • PCI DSS Asks more on 0 topics Alone on 13 topics More detailed on 2 topics
Requirements per topic and verdict
Topic GDPRPCI DSS Verdict
Governance
Management accountability GDPR: – PCI DSS: 1 Only PCI DSSno specific requirement on the other side in the acts covered
Roles and independence GDPR: 2 PCI DSS: – Only GDPRno specific requirement on the other side in the acts covered
Security policy GDPR: – PCI DSS: 2 Only PCI DSSno specific requirement on the other side in the acts covered
Awareness and training GDPR: – PCI DSS: 2 Only PCI DSSno specific requirement on the other side in the acts covered
Risk management
Risk management framework GDPR: 1 PCI DSS: – Only GDPRno specific requirement on the other side in the acts covered
Risk assessment GDPR: 1 PCI DSS: 1 Both cover itread the wording below
Asset management GDPR: – PCI DSS: 1 Only PCI DSSno specific requirement on the other side in the acts covered
Protection
Access control GDPR: – PCI DSS: 4 Only PCI DSSno specific requirement on the other side in the acts covered
Authentication GDPR: – PCI DSS: 5 Only PCI DSSno specific requirement on the other side in the acts covered
Cryptography and encryption GDPR: 1 PCI DSS: 3 PCI DSS more detailedmore requirements on this, not necessarily stricter
Data security GDPR: 2 PCI DSS: 4 PCI DSS more detailedmore requirements on this, not necessarily stricter
Network security GDPR: – PCI DSS: 7 Only PCI DSSno specific requirement on the other side in the acts covered
Secure communications GDPR: – PCI DSS: 2 Only PCI DSSno specific requirement on the other side in the acts covered
Secure acquisition and development GDPR: – PCI DSS: 3 Only PCI DSSno specific requirement on the other side in the acts covered
Configuration, change and patch management GDPR: – PCI DSS: 1 Only PCI DSSno specific requirement on the other side in the acts covered
Vulnerability handling GDPR: – PCI DSS: 4 Only PCI DSSno specific requirement on the other side in the acts covered
Human resources security GDPR: 1 PCI DSS: 1 Both cover itread the wording below
Physical and environmental security GDPR: – PCI DSS: 5 Only PCI DSSno specific requirement on the other side in the acts covered
Detection and response
Monitoring and detection GDPR: – PCI DSS: 12 Only PCI DSSno specific requirement on the other side in the acts covered
Incident handling GDPR: 1 PCI DSS: 1 Both cover itread the wording below
Reporting to authorities GDPR: 3 PCI DSS: – Only GDPRno specific requirement on the other side in the acts covered
Informing customers and the public GDPR: 1 PCI DSS: – Only GDPRno specific requirement on the other side in the acts covered
Continuity and resilience
Backup and recovery GDPR: 1 PCI DSS: – Only GDPRno specific requirement on the other side in the acts covered
Security testing GDPR: 1 PCI DSS: 2 Both cover itread the wording below
Third parties and supply chain
Supplier and third-party risk GDPR: 2 PCI DSS: 2 Both cover itread the wording below
Contract requirements GDPR: 1 PCI DSS: – Only GDPRno specific requirement on the other side in the acts covered
Privacy and data protection
Lawful processing GDPR: 7 PCI DSS: – Only GDPRno specific requirement on the other side in the acts covered
Transparency GDPR: 2 PCI DSS: – Only GDPRno specific requirement on the other side in the acts covered
Rights of individuals GDPR: 7 PCI DSS: – Only GDPRno specific requirement on the other side in the acts covered
Privacy by design and by default GDPR: 2 PCI DSS: – Only GDPRno specific requirement on the other side in the acts covered
Impact assessment GDPR: 3 PCI DSS: – Only GDPRno specific requirement on the other side in the acts covered
Records of processing GDPR: 2 PCI DSS: – Only GDPRno specific requirement on the other side in the acts covered
Data protection officer GDPR: 2 PCI DSS: – Only GDPRno specific requirement on the other side in the acts covered
International transfers GDPR: 4 PCI DSS: – Only GDPRno specific requirement on the other side in the acts covered
Supervision and enforcement
Cooperation with supervisors GDPR: 1 PCI DSS: – Only GDPRno specific requirement on the other side in the acts covered
Penalties and liability GDPR: 2 PCI DSS: – Only GDPRno 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

  • GDPR Regulation (EU) 2016/679 Articles 5 to 10, 12 to 22, 24 to 39, 44 to 49, 58, 83 · 50 requirements

Status

Reviewed against the official texts.

Included

  • PCI DSS PCI DSS v4.0.1 (June 2024) 63 requirements

Status

Reviewed against the official texts.

Key Numbers

Deadline

GDPR: At the time the data are obtained (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Within a reasonable period and at the latest one month after obtaining the data; if used to contact the person, at the latest at first communication; if disclosure is envisaged, at the latest at first disclosure (Controllers); Without undue delay and in any event within one month of receipt of the request; extendable by two further months where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Without undue delay and in any event within one month of receipt of the request (Article 12(3)); extendable by two further months where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Without undue delay after becoming aware (Processors); Without undue delay (Controllers); Before the processing starts (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Before the processing starts; where the authority considers the processing would infringe, it gives written advice within up to eight weeks of receipt of the request, extendable by six weeks (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

PCI DSS: Not in the acts covered

Threshold

GDPR: Under 16; Member States may lower the age, not below 13 (Controllers offering information society services directly to children); Exemption only below 250 persons, and only if none of the listed conditions applies (Controllers)

PCI DSS: Not in the acts covered

Goes to

GDPR: Controller (Processors); Data subjects (Controllers)

PCI DSS: Not in the acts covered

Evidence to keep

GDPR: Written record of processing activities (Controllers); Written record of processing activities (Processors); Internal record of each breach: facts, effects and remedial action (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

PCI DSS: Not in the acts covered

Incident reports go to

GDPR: Competent supervisory authority (Controllers)

PCI DSS: Not in the acts covered

First notice of an incident

GDPR: Without undue delay and, where feasible, within 72 hours of becoming aware (Controllers)

PCI DSS: Not in the acts covered

Intermediate report

GDPR: In phases, without undue further delay (Controllers)

PCI DSS: Not in the acts covered

External assessment or certification

GDPR: Approved code of conduct or certification may help show compliance (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

PCI DSS: Not in the acts covered

Review of the risk framework

GDPR: Where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

PCI DSS: Not in the acts covered

Testing of critical systems

GDPR: Regularly

PCI DSS: Not in the acts covered

Maximum fines

GDPR: Up to EUR 10 million or, for an undertaking, 2% of total worldwide annual turnover of the preceding financial year, whichever is higher; Up to EUR 20 million or, for an undertaking, 4% of total worldwide annual turnover of the preceding financial year, whichever is higher

PCI DSS: Not in the acts covered

Governance

Management accountability

Only PCI DSS no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.RR, GV.OV · ISO/IEC 27001:2022 Clause 5.1, A.5.4

Nothing in the acts covered.

  • PCI DSS compliance is managed

    PCI DSSPayment Card Industry Data Security Standard compliance is managed.

    PCI DSS, Requirement 12.4

Roles and independence

Only GDPR 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

  • Joint controllers

    Applies to: Joint controllers

    Joint controllers set out their respective responsibilities in an arrangement, unless EU or Member State law determines them, including who handles rights requests and information duties, and make its essence available to people. A person may exercise their rights against any of them regardless of the arrangement.

    GDPR, Article 26

  • EU representative

    Applies to: Controllers and processors not established in the EU, under Article 3(2)

    A controller or processor outside the EU that falls under Article 3(2) designates a representative in writing, established in a Member State where the affected people are. Occasional low-risk processing without large-scale special category or criminal data, and public bodies, are exempt.

    GDPR, Article 27

Nothing in the acts covered.

Security policy

Only PCI DSS no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

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

    PCI DSS, Requirement 12.1

  • 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

Awareness and training

Only PCI DSS no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

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

    PCI DSS, Requirement 5.4

  • Security awareness education is an ongoing activity

    Security awareness education is an ongoing activity.

    PCI DSS, Requirement 12.6

Risk management

Risk management framework

Only GDPR no specific requirement on the other side in the acts covered

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

  • Measures to ensure and show compliance

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Put in place technical and organisational measures suited to the risks of the processing, so that it complies and the controller can show it does. Review and update them where needed. Where proportionate, these include data protection policies.

    GDPR, Article 24

Nothing in the acts covered.

Risk assessment

Both cover it read the wording below

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

  • Assess security risk

    When judging the right level of security, weigh the risks of processing, in particular accidental or unlawful destruction, loss, alteration, and unauthorised disclosure of or access to personal data.

    GDPR, Article 32(2)

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

    PCI DSS, Requirement 12.3

Asset management

Only PCI DSS no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.AM · ISO/IEC 27001:2022 A.5.9 to A.5.13

Nothing in the acts covered.

  • PCI DSS scope is documented and validated

    PCI DSSPayment Card Industry Data Security Standard scope is documented and validated.

    PCI DSS, Requirement 12.5

Protection

Access control

Only PCI DSS no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

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

    PCI DSS, Requirement 7.1

  • 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

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

    PCI DSS, Requirement 7.3

  • 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

Authentication

Only PCI DSS no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

  • 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

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

    PCI DSS, Requirement 8.3

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

    PCI DSS, Requirement 8.4

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

    PCI DSS, Requirement 8.5

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

    PCI DSS, Requirement 8.6

Cryptography and encryption

PCI DSS more detailed more requirements on this, not necessarily stricter

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

  • Pseudonymisation and encryption

    Apply pseudonymisation and encryption of personal data, as appropriate to the risk.

    GDPR, Article 32(1)(a)

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

    PCI DSS, Requirement 3.5

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

    PCI DSS, Requirement 3.6

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

    PCI DSS, Requirement 3.7

Data security

PCI DSS more detailed more requirements on this, not necessarily stricter

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

  • Integrity and confidentiality

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Process personal data with appropriate security, using appropriate technical or organisational measures, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage.

    GDPR, Article 5(1)(f)

  • Security of systems and services

    Be able to keep processing systems and services confidential, intact, available and resilient on an ongoing basis, as appropriate to the risk.

    GDPR, Article 32(1)(b)

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

    PCI DSS, Requirement 3.1

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

    PCI DSS, Requirement 3.2

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

    PCI DSS, Requirement 3.3

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

    PCI DSS, Requirement 3.4

Network security

Only PCI DSS no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

  • 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

  • Network security controls (NSCs) are configured and maintained

    Network security controls (NSCs) are configured and maintained.

    PCI DSS, Requirement 1.2

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

    PCI DSS, Requirement 1.3

  • Network connections between trusted and untrusted networks are controlled

    Network connections between trusted and untrusted networks are controlled.

    PCI DSS, Requirement 1.4

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

    PCI DSS, Requirement 1.5

  • Wireless environments are configured and managed securely

    Wireless environments are configured and managed securely.

    PCI DSS, Requirement 2.3

  • 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

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.

    PCI DSS, Requirement 4.1

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

    PCI DSS, Requirement 4.2

Secure acquisition and development

Only PCI DSS no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.PS · ISO/IEC 27001:2022 A.8.25 to A.8.31

Nothing in the acts covered.

  • 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

  • Bespoke and custom software are developed securely

    Bespoke and custom software are developed securely.

    PCI DSS, Requirement 6.2

  • Public-facing web applications are protected against attacks

    Public-facing web applications are protected against attacks.

    PCI DSS, Requirement 6.4

Configuration, change and patch management

Only PCI DSS no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.PS · ISO/IEC 27001:2022 A.8.9, A.8.19, A.8.32

Nothing in the acts covered.

  • Changes to all system components are managed securely

    Changes to all system components are managed securely.

    PCI DSS, Requirement 6.5

Vulnerability handling

Only PCI DSS no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

  • 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

  • System components are configured and managed securely

    System components are configured and managed securely.

    PCI DSS, Requirement 2.2

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

    PCI DSS, Requirement 6.3

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

    PCI DSS, Requirement 11.3

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

  • Staff act only on instructions

    Processors, and anyone with access to personal data under the authority of a controller or processor, process it only on the controller's instructions unless EU or Member State law requires otherwise. Controllers and processors take steps to ensure this.

    GDPR, Articles 29 and 32(4)

  • Personnel are screened to reduce risks from insider threats

    Personnel are screened to reduce risks from insider threats.

    PCI DSS, Requirement 12.7

Physical and environmental security

Only PCI DSS no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

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

    PCI DSS, Requirement 9.1

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

    PCI DSS, Requirement 9.2

  • 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

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

    PCI DSS, Requirement 9.4

  • 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

Detection and response

Monitoring and detection

Only PCI DSS no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

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

    PCI DSS, Requirement 5.1

  • Malicious software (malware) is prevented, or detected and addressed

    Malicious software (malware) is prevented, or detected and addressed.

    PCI DSS, Requirement 5.2

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

    PCI DSS, Requirement 5.3

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

    PCI DSS, Requirement 10.1

  • 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

  • Audit logs are protected from destruction and unauthorized modifications

    Audit logs are protected from destruction and unauthorized modifications.

    PCI DSS, Requirement 10.3

  • 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

  • Audit log history is retained and available for analysis

    Audit log history is retained and available for analysis.

    PCI DSS, Requirement 10.5

  • 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

  • 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

  • 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

  • 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

Incident handling

Both cover it read the wording below

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

  • Document every breach

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Record each personal data breach, whether notified or not, with its facts, effects and remedial action, so the authority can check compliance.

    GDPR, Article 33(5)

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

    PCI DSS, Requirement 12.10

Reporting to authorities

Only GDPR no specific requirement on the other side in the acts covered

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

  • Notify a personal data breach

    Applies to: Controllers

    Notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to risk people's rights and freedoms. Give reasons if the notice is late.

    GDPR, Article 33(1)

  • Processor tells the controller

    Applies to: Processors

    Tell the controller of a personal data breach without undue delay after becoming aware of it.

    GDPR, Article 33(2)

  • What the breach notice contains

    Applies to: Controllers

    Describe the breach, including the categories and approximate numbers of people and records where possible, the DPO or other contact point, the likely consequences, and the measures taken or proposed. Information not yet available may follow in phases.

    GDPR, Article 33(3) and (4)

Nothing in the acts covered.

Informing customers and the public

Only GDPR no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.CO, RC.CO

  • Tell the people affected

    Applies to: Controllers

    Where a breach is likely to cause high risk to people, tell them in plain language without undue delay, with the contact point, likely consequences and measures. This is not needed where the data was unintelligible, for example encrypted, where later measures remove the high risk, or where a public notice replaces disproportionate effort. The authority may require notice.

    GDPR, Article 34(1) to (4)

Nothing in the acts covered.

Continuity and resilience

Backup and recovery

Only GDPR 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

  • Restoring access after an incident

    Be able to restore availability of and access to personal data in a timely way after a physical or technical incident, as appropriate to the risk.

    GDPR, Article 32(1)(c)

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

  • Testing the measures

    Have a process to test and evaluate regularly whether the technical and organisational security measures work, as appropriate to the risk.

    GDPR, Article 32(1)(d)

  • 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

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

    PCI DSS, Requirement 11.4

Third parties and supply chain

Supplier and third-party risk

Both cover it read the wording below

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

  • Use only processors with sufficient guarantees

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Use only processors that give adequate assurances of technical and organisational measures that meet the Regulation and protect people's rights.

    GDPR, Article 28(1)

  • Sub-processors

    Applies to: Processors

    Do not engage another processor without the controller's prior written authorisation, specific or general, and under general authorisation give notice of changes so the controller can object. Bind the sub-processor by contract to the same data protection obligations. The initial processor stays fully liable for the sub-processor's failures.

    GDPR, Article 28(2) and (4)

  • 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

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

    PCI DSS, Requirement 12.9

Contract requirements

Only GDPR no specific requirement on the other side in the acts covered

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

  • Processing contract

    Govern processing by a written contract or other legal act covering subject matter, duration, nature and purpose, data types, the people concerned and the controller's obligations and rights. It requires the processor to act on documented instructions, keep staff bound to confidentiality, secure the data, follow the sub-processor requirements, help with rights and Articles 32 to 36, delete or return data at the end at the controller's choice, provide compliance information and allow audits. The processor warns the controller at once if an instruction appears to breach data protection law.

    GDPR, Article 28(3) and (9)

Nothing in the acts covered.

Privacy and data protection

Lawful processing

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.PO-P

  • Purpose limitation and data minimisation

    Applies to: Controllers

    Collect personal data for specified, explicit and legitimate purposes and do not use it later in a way that conflicts with them. Keep the data adequate, relevant and limited to what those purposes need.

    GDPR, Article 5(1)(b) and (c)

  • Accuracy and storage limitation

    Applies to: Controllers

    Keep personal data accurate and, where needed, up to date, and take every reasonable step to erase or correct inaccurate data without delay. Keep data in a form that identifies people only for as long as the purpose needs, or longer solely for archiving, research or statistics under Article 89(1) with safeguards.

    GDPR, Article 5(1)(d) and (e)

  • Accountability

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    The controller is responsible for meeting the data protection principles and must be able to demonstrate that it does.

    GDPR, Article 5(2)

  • Lawful basis

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Process personal data lawfully, fairly and transparently, and only where at least one basis applies: consent, contract, legal obligation, vital interests, a public-interest task or official authority, or legitimate interests. Legitimate interests do not apply where the person's interests or rights override them, and are not open to public authorities performing their tasks.

    GDPR, Articles 5(1)(a) and 6(1)

  • Conditions for consent

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Be able to prove consent, and keep a written consent request separate from other matters and in plain language. Let people withdraw at any time, as easily as they gave consent, and tell them so beforehand. Consent tied to a contract for data the contract does not need may not count as freely given.

    GDPR, Article 7

  • Children's consent to online services

    Applies to: Controllers offering information society services directly to children

    Where consent is the basis for processing in relation to offering an information society service directly to a child under the age limit, make sure consent is given or authorised by the holder of parental responsibility. Make reasonable efforts, given the available technology, to verify it.

    GDPR, Article 8(1) and (2)

  • Special category and criminal offence data

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Do not process special category data, such as health, biometric identification or genetic data, unless a condition in Article 9(2) applies. Process criminal conviction and offence data only under official authority or where EU or Member State law authorises it with safeguards.

    GDPR, Articles 9 and 10

Nothing in the acts covered.

Transparency

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework CM.AW-P

  • Information when collecting from the person

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Tell people, concisely and in plain language, who the controller and any DPO are, the purposes and legal basis, any legitimate interests relied on, recipients, transfers, retention, their rights, whether they must provide the data, and any automated decision-making. Before using the data for a new purpose, give information on that purpose and any relevant further details. This is not needed where the person already has the information.

    GDPR, Articles 12(1) and 13

  • Information when data comes from elsewhere

    Applies to: Controllers

    Give the same information, plus the categories of data and their source, when the data was not obtained from the person. Exceptions include where the person already has it, where this proves impossible or takes disproportionate effort, in which case take appropriate measures to protect the person, including making the information public, or where law requires the obtaining or disclosure or professional secrecy applies.

    GDPR, Article 14

Nothing in the acts covered.

Rights of individuals

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.DM-P

  • Answer rights requests in time

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Act on a request under Articles 15 to 22 and tell the person the outcome free of charge. If more time is needed for complex or numerous requests, say so and why within the first month. If no action will be taken, say why without delay and within the first month, and explain the right to complain to an authority and seek a judicial remedy. Manifestly unfounded or excessive requests may be charged for or refused, and the controller must show why.

    GDPR, Article 12(3) to (5)

  • Right of access

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Confirm whether personal data about the person is processed and give access to it, with a copy and information on purposes, data categories, recipients, retention, rights, source and automated decision-making. A reasonable fee may be charged for further copies. The right to a copy must not adversely affect the rights and freedoms of others.

    GDPR, Article 15

  • Rectification, restriction and telling recipients

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Correct inaccurate data without undue delay and, taking account of the purposes, complete incomplete data. On request, restrict processing while accuracy is contested or an Article 21(1) objection is being checked, where processing is unlawful and the person prefers restriction to erasure, or where the controller no longer needs the data but the person needs it for legal claims. Tell each recipient of any rectification, erasure or restriction unless this proves impossible or takes disproportionate effort, and tell the person who the recipients are if asked.

    GDPR, Articles 16, 18 and 19

  • Right to erasure

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Erase personal data without undue delay where it is no longer needed, consent is withdrawn with no other basis, the person objects under Article 21(1) without overriding grounds or objects to direct marketing, processing was unlawful, law requires it, or it was collected for an information society service under Article 8(1). If the data was made public, take reasonable steps to tell other controllers of the request. The right does not apply where processing is needed for freedom of expression, a legal obligation or public task, public health, archiving, research or statistics where erasure would seriously impair them, or legal claims.

    GDPR, Article 17

  • Right to data portability

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Where processing is automated and rests on consent or contract, give people, on request, the data they provided in a structured, commonly used, machine-readable format. On request, send it directly to another controller where technically feasible. The right does not apply to public-task processing and must not adversely affect the rights of others.

    GDPR, Article 20

  • Right to object

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Stop processing based on a public task or legitimate interests when the person objects on grounds of their particular situation, unless the controller demonstrates compelling legitimate grounds that override the person's interests, or legal claims. Stop direct marketing, and related profiling, on objection without exception. Present this right clearly and separately, at the latest at first communication.

    GDPR, Article 21

  • Solely automated decisions

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Do not subject people to decisions based solely on automated processing, including profiling, with legal or similarly significant effects, unless a contract need, law or explicit consent allows it. In the contract and consent cases, provide human intervention, a chance to give a view and a way to contest the decision. Special category data needs further conditions and safeguards.

    GDPR, Article 22

Nothing in the acts covered.

Privacy by design and by default

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.DP-P

  • Data protection by design

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    When deciding how to process and during processing, apply measures such as pseudonymisation that put the data protection principles into effect and build safeguards into the processing. Take account of the state of the art, cost and risk.

    GDPR, Article 25(1)

  • Data protection by default

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    By default, process only the data needed for each purpose, in amount, extent, storage period and accessibility. Do not make personal data available to an indefinite number of people without the person's intervention.

    GDPR, Article 25(2)

Nothing in the acts covered.

Impact assessment

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework ID.RA-P

  • When an impact assessment is needed

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Assess the impact on personal data before processing that is likely to cause high risk, especially with new technologies. It is required for systematic and extensive automated evaluation with legal or similarly significant effects, large-scale special category or criminal data, and large-scale systematic monitoring of a publicly accessible area.

    GDPR, Article 35(1) and (3)

  • What the assessment contains

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Describe the processing and its purposes, assess necessity and proportionality, assess the risks to people, and set out the measures to address them. Seek the advice of the DPO where one is designated, and where appropriate the views of those affected. Where necessary, review whether processing follows the assessment, at least when the risk changes.

    GDPR, Article 35(2), (7), (9) and (11)

  • Prior consultation

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Consult the supervisory authority before processing if the assessment shows the processing would result in a high risk in the absence of measures taken by the controller to mitigate it. Provide responsibilities, purposes and means, safeguards, DPO contact details, the assessment and anything else the authority asks for.

    GDPR, Article 36(1) to (3)

Nothing in the acts covered.

Records of processing

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework ID.IM-P

  • Controller's record of processing

    Applies to: Controllers

    Keep a written or electronic record of the name and contact details of the controller and any joint controller, representative and DPO, purposes, categories of people, data and recipients, transfers, erasure time limits and security measures where possible, and show it to the authority on request. The duty does not apply to organisations under 250 persons, unless the processing is likely to risk people's rights, is not occasional, or includes special category or criminal data.

    GDPR, Article 30(1), (3), (4) and (5)

  • Processor's record of processing

    Applies to: Processors

    Keep a written or electronic record of the name and contact details of the processor, each controller served and any representative and DPO, the categories of processing for each controller, transfers and, where possible, security measures. Show it to the authority on request. The same 250-person exemption applies.

    GDPR, Article 30(2) to (5)

Nothing in the acts covered.

Data protection officer

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework GV.PO-P

  • Designate a data protection officer

    Designate a DPO if the organisation is a public body, except courts acting in their judicial capacity, if its core activities need regular and systematic large-scale monitoring of people, or if they involve large-scale special category or criminal data. Choose the DPO for expertise in data protection law and practice. Publish the DPO's contact details and give them to the authority.

    GDPR, Article 37(1), (5) and (7)

  • Position and tasks of the DPO

    Involve the DPO promptly in all data protection issues and give the resources and access needed. The DPO takes no instructions on these tasks, cannot be dismissed or penalised for doing them, and reports to the highest management level, and other duties must not create a conflict of interests. The DPO advises, monitors compliance including staff training and audits, advises on impact assessments and acts as contact point for the authority.

    GDPR, Articles 38 and 39

Nothing in the acts covered.

International transfers

Only GDPR no specific requirement on the other side in the acts covered

  • Transfers need a Chapter V ground

    Transfer personal data to a third country or international organisation, including onward transfers, only under the conditions of Chapter V. A Commission adequacy decision allows a transfer without specific authorisation.

    GDPR, Articles 44 and 45

  • Appropriate safeguards

    Without an adequacy decision, transfer only with appropriate safeguards and enforceable rights and remedies for people. Options without specific authority approval include binding corporate rules approved under Article 47, standard data protection clauses, and approved codes or certification with binding commitments. Bespoke contractual clauses need the authority's authorisation.

    GDPR, Articles 46 and 47

  • Third-country orders

    Treat a third-country court or authority order to transfer or disclose personal data as recognised or enforceable only where it rests on an international agreement, such as a mutual legal assistance treaty, without prejudice to other Chapter V grounds.

    GDPR, Article 48

  • Derogations for specific situations

    Without adequacy or safeguards, transfer only on a listed ground such as explicit informed consent, contract need, important public interest, legal claims or vital interests. As a last resort, a non-repetitive transfer about few people may rest on compelling legitimate interests not overridden by the person's interests or rights, if the controller assesses it, applies safeguards, informs the authority and the people concerned, and records it. Public authorities exercising public powers cannot use the consent, contract or last-resort grounds.

    GDPR, Article 49

Nothing in the acts covered.

Supervision and enforcement

Cooperation with supervisors

Only GDPR no specific requirement on the other side in the acts covered

  • Cooperate with supervisory authority powers

    Cooperate with the supervisory authority on request. The authority can order information, audit, access data and premises, and issue warnings, reprimands and orders, including a processing ban, suspension of data flows or a fine.

    GDPR, Articles 31 and 58

Nothing in the acts covered.

Penalties and liability

Only GDPR no specific requirement on the other side in the acts covered

  • Fines for operational obligations

    Infringing the duties of controllers and processors in Articles 8, 11, 25 to 39, 42 and 43, or of certification and monitoring bodies, can be fined, and fines are set case by case to be effective, proportionate and dissuasive. Several infringements in the same or linked processing operations are capped at the amount for the gravest one.

    GDPR, Article 83(1) to (4)

  • Fines for principles, rights and transfers

    Infringing the principles and consent requirements in Articles 5, 6, 7 and 9, rights in Articles 12 to 22, transfer requirements in Articles 44 to 49, Member State law adopted under Chapter IX, or ignoring an authority's order or denying it access can be fined at the higher level.

    GDPR, Article 83(5) and (6)

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.

Loading the form…