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

Data Act vs PCI DSS

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

Data ActManufacturers and related service providers, data holders, providers of data processing services

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

At a Glance

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

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

  • Data Act Regulation (EU) 2023/2854 of the European Parliament and of the Council of 13 December 2023 Articles 3 to 9, 11, 13, 14, 18, 23, 25, 26, 28 to 32, 40 · 33 requirements
  • Druk nr 3266 Druk nr 3266 (government bill) and Druk nr 3288 (committee report), Sejm of the Republic of Poland, 10th term 4 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

Data Act: Without undue delay after a simple request (Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties.); Without undue delay after the user's request (Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. and gatekeepersAn undertaking providing core platform services that the Commission has designated under the Digital Markets Act because it has a significant impact on the internal market, runs an important gateway between business users and end users and holds an entrenched and durable position. Gatekeepers must follow DMA obligations and prohibitions. designated under the Digital Markets ActRegulation (EU) 2022/1925, an EU law intended to make digital markets fairer and easier for businesses to enter and compete in. It sets duties for providers that the European Commission designates as gatekeepers for specified core platform services, such as app stores or online search. Business users and end users benefit from the requirements even when they are not gatekeepers themselves. The DMA is separate from the Digital Services Act.); Without undue delay after a reasoned request (Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. obliged to make data available); Decline within five working days of receipt for a public emergency, 30 working days of receipt otherwise (Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. that are legal persons, other than public sector bodies); Notice of at most two months; transition of at most 30 calendar days after the notice period (Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.); Retrieval for at least 30 calendar days after the end of the transitional period (Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.); Notify within 14 working days of the switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. request; alternative period of at most seven months (Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.); No switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. charges from 12 January 2027 (Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.); Compatibility at least 12 months after publication of the references in the central Union standards repository (Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.)

PCI DSS: Not in the acts covered

Threshold

Data Act: Micro and small enterprises; medium-sized for under one year; a medium-sized enterprise's products for one year after market placement (Micro and small enterprises, and medium-sized enterprises in their first year or for products in their first year on the market)

PCI DSS: Not in the acts covered

Goes to

Data Act: Competent authority designated under Article 37 (Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties.); User or third party in writing; competent authority notified (Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties.); Customer, before complying (Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.)

PCI DSS: Not in the acts covered

Deadline to have the measures in place

Data Act: Products and related servicesRelated Service (Data Act) placed on the market after 12 September 2026 (Manufacturers of connected productsAn item that obtains, generates or collects data about its use or environment, can communicate product data through an electronic communications service, a physical connection or on-device access and whose primary function is not storing, processing or transmitting data on behalf of a party other than the user. The Data Act gives users access rights for covered product data under the conditions it sets. and providers of related servicesRelated Service (Data Act))

PCI DSS: Not in the acts covered

Maximum fines

Data Act: Set by each Member State; for Chapters II, III and V, data protection authoritiesData Protection Authority may fine up to the GDPRGeneral Data Protection Regulation Article 83(5) amount (Member States)

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

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 assessment

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

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

Nothing in the acts covered.

  • 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

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

Nothing in the acts covered.

  • 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

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

  • Restricting access for product security Optional

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties.

    Users and data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. may agree by contract to restrict or prohibit access, use or further sharing where it could undermine the product's legal security requirements and seriously harm the health, safety or security of people. A data holderUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. that refuses to share on this ground notifies the competent authority.

    Data Act, Article 4(2)

  • Protect trade secrets when sharing

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. and trade secret holders

    Identify data protected as trade secrets, including in the metadataInformation describing other data, such as its format, structure, meaning or security labels. It helps people and systems find, interpret and use the underlying information. In the EU Data Act, metadata specifically means a structured description of the contents or use of data that facilitates finding or using it. The Act's access provisions can therefore concern both the data and the information needed to understand it., and agree with the user or third party proportionate technical and organisational measures to keep it confidential. Disclosure happens only once those measures are in place, and to a third party only as far as strictly necessary for the purpose agreed with the user.

    Data Act, Articles 4(6) and 5(9)

  • Withhold or refuse data to protect trade secrets Optional

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties.

    A data holderUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. may withhold or suspend trade secret data where measures are not agreed, not implemented or confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available. is undermined. In exceptional cases a trade secret holder may refuse a specific request if it shows serious economic damage is highly likely. The decision is reasoned and given in writing without undue delay, and the competent authority is notified.

    Data Act, Articles 4(7), 4(8), 5(10) and 5(11)

  • Third party limits on received data

    Applies to: Third parties receiving data at the user's request

    Process the data only for the purposes and under the conditions agreed with the user, and erase it when no longer needed for that purpose unless otherwise agreed for non-personal dataIn the EU Data Act, data that is not personal data: it does not relate to an identified or identifiable individual. This can include machine measurements with no link to a person, or information genuinely anonymised so people cannot be identified. Removing names alone may not be enough. Non-personal data can still be commercially sensitive and subject to contractual, security or other legal protections.. Do not make the user's choices unduly difficult, profile people unless needed for the requested service, or pass the data to another third party except under a contract with the user and with the agreed trade secret measures. Do not pass it to a gatekeeperAn undertaking providing core platform services that the Commission has designated under the Digital Markets Act because it has a significant impact on the internal market, runs an important gateway between business users and end users and holds an entrenched and durable position. Gatekeepers must follow DMA obligations and prohibitions., use it to develop a competing product or derive insights about the data holderUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties., harm the product's security, disregard agreed trade secret measures, or stop a consumer user from sharing the data.

    Data Act, Article 6(1) and (2)

  • Data retrieval and erasure

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Specify all categories of data and digital assets that can be ported, including at least all exportable data. Give a data retrieval period of at least 30 calendar days after the transitional period, and guarantee full erasure of exportable data and digital assets after that period once switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. has succeeded.

    Data Act, Article 25(2)(e), (g) and (h)

  • Prevent unlawful governmental access

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Take all adequate technical, organisational and legal measures, including contracts, to prevent international and third-country governmental access to or transfer of non-personal dataIn the EU Data Act, data that is not personal data: it does not relate to an identified or identifiable individual. This can include machine measurements with no link to a person, or information genuinely anonymised so people cannot be identified. Removing names alone may not be enough. Non-personal data can still be commercially sensitive and subject to contractual, security or other legal protections. held in the Union where it would conflict with Union or national law. A third-country decision is recognised or enforceable only if it is based on an international agreement.

    Data Act, Article 32(1) and (2)

  • 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

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

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

  • Data accessible by design and by default

    Applies to: Manufacturers of connected productsAn item that obtains, generates or collects data about its use or environment, can communicate product data through an electronic communications service, a physical connection or on-device access and whose primary function is not storing, processing or transmitting data on behalf of a party other than the user. The Data Act gives users access rights for covered product data under the conditions it sets. and providers of related servicesRelated Service (Data Act)

    Design and manufacture connected productsAn item that obtains, generates or collects data about its use or environment, can communicate product data through an electronic communications service, a physical connection or on-device access and whose primary function is not storing, processing or transmitting data on behalf of a party other than the user. The Data Act gives users access rights for covered product data under the conditions it sets., and design and provide related servicesRelated Service (Data Act), so that product and related service data and the metadataInformation describing other data, such as its format, structure, meaning or security labels. It helps people and systems find, interpret and use the underlying information. In the EU Data Act, metadata specifically means a structured description of the contents or use of data that facilitates finding or using it. The Act's access provisions can therefore concern both the data and the information needed to understand it. needed to use them are accessible to the user by default. Access is easy, secure, free of charge and in a comprehensive, structured, commonly used and machine-readable format, and direct where relevant and technically feasible. This applies to products and services placed on the market after 12 September 2026.

    Data Act, Article 3(1)

  • 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

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

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

Nothing in the acts covered.

  • 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

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

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

Nothing in the acts covered.

  • 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

Informing customers and the public

Only Data Act no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.CO, RC.CO

  • Handling third-country access requests

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Without an international agreement, give access only where the Article 32(3) conditions on reasons, review and consideration of protected interests are met. If the provider asks the competent national body for its opinion and gets no reply within one month, or the body finds the conditions are not met, the provider may reject the request. It must ask that body where national security or defence may be affected. Provide the minimum data permissible, and inform the customer before complying unless the request serves law enforcement and only for as long as needed to keep that effective.

    Data Act, Article 32(3) to (5)

Nothing in the acts covered.

Continuity and resilience

Security testing

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

NIST CSF 2.0 ID.IM · ISO/IEC 27001:2022 A.5.35, A.8.29, A.8.34

Nothing in the acts covered.

  • 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

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

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

Nothing in the acts covered.

  • 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 Data Act no specific requirement on the other side in the acts covered

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

  • Protect trade secrets when sharing

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. and trade secret holders

    Identify data protected as trade secrets, including in the metadataInformation describing other data, such as its format, structure, meaning or security labels. It helps people and systems find, interpret and use the underlying information. In the EU Data Act, metadata specifically means a structured description of the contents or use of data that facilitates finding or using it. The Act's access provisions can therefore concern both the data and the information needed to understand it., and agree with the user or third party proportionate technical and organisational measures to keep it confidential. Disclosure happens only once those measures are in place, and to a third party only as far as strictly necessary for the purpose agreed with the user.

    Data Act, Articles 4(6) and 5(9)

  • Limits on the data holder's own use

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties.

    Use readily available non-personal dataIn the EU Data Act, data that is not personal data: it does not relate to an identified or identifiable individual. This can include machine measurements with no link to a person, or information genuinely anonymised so people cannot be identified. Removing names alone may not be enough. Non-personal data can still be commercially sensitive and subject to contractual, security or other legal protections. only under a contract with the user, and do not use it to derive insights that could undermine the commercial position of the user. Do not pass non-personal product data to third parties beyond fulfilling the user contract, and bind third parties not to share further. The same insight ban protects third parties unless they give a permission they can easily withdraw.

    Data Act, Articles 4(13), 4(14) and 5(6)

  • Fair, reasonable and non-discriminatory terms

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. obliged to make data available

    Where a business-to-businessBusiness-to-business describes services or sales between companies, as opposed to services for consumers. NIS2 uses it in Annex I, which lists 'ICT service management (business-to-business)' as one of its sectors. IT service providers that serve business customers should therefore check whether NIS2 applies to them. data sharing duty applies under Article 5 or other law, agree the arrangements with the data recipientData Recipient (Data Act) on fair, reasonable and non-discriminatory terms and in a transparent manner. Terms that are unfair under Article 13, or that reduce the user's Chapter II rights to the user's detriment, are not binding.

    Data Act, Article 8(1) and (2)

  • No discrimination and no unrequested sharing

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. obliged to make data available

    Do not discriminate between comparable categories of data recipientsData Recipient (Data Act), including partner and linked enterprises, and on a reasoned request show that no discrimination took place. Do not make data available to a recipient, including exclusively, unless the user requested it under Chapter II.

    Data Act, Article 8(3) and (4)

  • Reasonable compensation

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. obliged to make data available

    Compensation agreed between businesses is non-discriminatory and reasonable and may include a margin, taking into account the costs of making data available and investments in collecting and producing it. For an SMESmall and Medium-Sized Enterprises or not-for-profit research organisation without larger partner or linked enterprises it does not exceed those costs of making data available. Give the recipient enough detail on the calculation to check this.

    Data Act, Article 9(1), (2), (4) and (7)

  • Unfair terms imposed unilaterally are not binding

    Applies to: Enterprises contracting on data

    A term on data access and use, or on liability and remedies for data obligations, that one enterprise imposes unilaterally on another is not binding on that other enterprise if it is unfair. A term is unfair if its use grossly deviates from good commercial practice, contrary to good faith and fair dealing. The party that supplied the term has to prove it was not imposed unilaterally.

    Data Act, Article 13(1), (3) and (6)

  • Terms that are or are presumed unfair

    Applies to: Enterprises contracting on data

    Always unfair: excluding liability for intent or gross negligence, excluding remedies for non-performance, or reserving the sole right to judge conformity or interpret the contract. Presumed unfair: among others, limiting remedies inappropriately, significantly detrimental use of the other party's data, blocking its use of or copies of its own data, blocking termination within a reasonable period, terminating at unreasonably short notice, or substantially changing price or conditions without a valid reason and a right to terminate.

    Data Act, Article 13(4) and (5)

  • Switching terms in a written contract

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Set out switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. rights and obligations in a written contract, available to the customer before signing. Allow the customer to switch or port on request after a notice period of at most two months, within a transitional period of at most 30 calendar days. During the transition give reasonable assistance, keep the service running, tell the customer about known risks to continuity and keep a high level of security. Support the customer's exit strategy.

    Data Act, Article 25(1) and (2)(a), (b) and (d)

Nothing in the acts covered.

Exit and termination

Only Data Act no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.SC

  • Remove obstacles to switching

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Take the measures in Articles 25, 26, 27, 29 and 30, and neither impose nor keep pre-commercial, commercial, technical, contractual or organisational obstacles to terminating the contract, signing with another provider, porting exportable data and digital assets, achieving functional equivalence, or unbundling where technically feasible.

    Data Act, Article 23

  • Switching terms in a written contract

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Set out switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. rights and obligations in a written contract, available to the customer before signing. Allow the customer to switch or port on request after a notice period of at most two months, within a transitional period of at most 30 calendar days. During the transition give reasonable assistance, keep the service running, tell the customer about known risks to continuity and keep a high level of security. Support the customer's exit strategy.

    Data Act, Article 25(1) and (2)(a), (b) and (d)

  • Data retrieval and erasure

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Specify all categories of data and digital assets that can be ported, including at least all exportable data. Give a data retrieval period of at least 30 calendar days after the transitional period, and guarantee full erasure of exportable data and digital assets after that period once switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. has succeeded.

    Data Act, Article 25(2)(e), (g) and (h)

  • Longer transition where 30 days is not feasible

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Where the 30 day transition is technically unfeasible, notify the customer within 14 working days of the switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. request, justify it and propose an alternative period of at most seven months, keeping the service running throughout. The contract also lets the customer extend the transitional period once.

    Data Act, Article 25(4) and (5)

  • Information on switching

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Tell the customer about available switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. and porting procedures, methods, formats and known limitations, and refer it to an up-to-date online register of data structures, formats, standards and open interoperabilityThe ability of different systems or organisations to communicate and work together. In data sharing, this means exchanging information in ways that allow the receiving system or organisation to understand and use it. In payments, it means making different payment accounts, providers or systems work together, for example through shared platforms or common acceptance standards. The practical requirements depend on the relevant service and requirements; the term alone does not establish a particular legal duty. specifications for the exportable data.

    Data Act, Article 26

  • Withdrawal of switching charges

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Charge nothing for switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. from 12 January 2027. From 11 January 2024 to 12 January 2027, reduced charges may be applied, limited to the costs directly linked to the switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges.. Before contracting, give clear information on standard fees, early termination penalties and any reduced switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. charges, and on services where switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. is highly complex or costly.

    Data Act, Article 29(1) to (6)

  • Technical support for switching

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Infrastructure providers take all reasonable measures in their power to help the customer reach functional equivalence with the destination service. Other providers offer open interfaces free of charge to customers and destination providers, and become compatible with common specifications or harmonised standards within 12 months of their publication in the central Union standards repository. Until those are published, export all exportable data in a structured, commonly used and machine-readable format on request.

    Data Act, Article 30(1), (2), (3) and (5)

Nothing in the acts covered.

Privacy and data protection

Lawful processing

Only Data Act no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.PO-P

  • Legal basis for personal data

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties.

    Where the user is not the data subjectThe identified or identifiable natural person to whom personal data relate. The GDPR gives data subjects rights such as access, rectification, erasure, objection and data portability, which controllers must be able to handle., make personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. available to the user or third party only with a valid legal basis under GDPRGeneral Data Protection Regulation Article 6 and, where relevant, under GDPRGeneral Data Protection Regulation Article 9 and ePrivacy Article 5(3).

    Data Act, Articles 4(12) and 5(7)

  • Third party limits on received data

    Applies to: Third parties receiving data at the user's request

    Process the data only for the purposes and under the conditions agreed with the user, and erase it when no longer needed for that purpose unless otherwise agreed for non-personal dataIn the EU Data Act, data that is not personal data: it does not relate to an identified or identifiable individual. This can include machine measurements with no link to a person, or information genuinely anonymised so people cannot be identified. Removing names alone may not be enough. Non-personal data can still be commercially sensitive and subject to contractual, security or other legal protections.. Do not make the user's choices unduly difficult, profile people unless needed for the requested service, or pass the data to another third party except under a contract with the user and with the agreed trade secret measures. Do not pass it to a gatekeeperAn undertaking providing core platform services that the Commission has designated under the Digital Markets Act because it has a significant impact on the internal market, runs an important gateway between business users and end users and holds an entrenched and durable position. Gatekeepers must follow DMA obligations and prohibitions., use it to develop a competing product or derive insights about the data holderUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties., harm the product's security, disregard agreed trade secret measures, or stop a consumer user from sharing the data.

    Data Act, Article 6(1) and (2)

Nothing in the acts covered.

Transparency

Only Data Act no specific requirement on the other side in the acts covered

NIST Privacy Framework CM.AW-P

  • Pre-contract information on the data

    Applies to: Sellers, rentors and lessors of connected productsAn item that obtains, generates or collects data about its use or environment, can communicate product data through an electronic communications service, a physical connection or on-device access and whose primary function is not storing, processing or transmitting data on behalf of a party other than the user. The Data Act gives users access rights for covered product data under the conditions it sets., and providers of related servicesRelated Service (Data Act)

    Before the contract, tell the user clearly what data the product generates or the service obtains, its type, format and estimated volume, where it is stored and for how long, and how the user can access, retrieve or erase it. Related serviceRelated Service (Data Act) providers also state who the data holderUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. is, how it intends to use the data, how to share data with a third party, the right to complain, any trade secrets, and the contract term and exit arrangements.

    Data Act, Article 3(2) and (3)

  • Information on switching

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Tell the customer about available switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. and porting procedures, methods, formats and known limitations, and refer it to an up-to-date online register of data structures, formats, standards and open interoperabilityThe ability of different systems or organisations to communicate and work together. In data sharing, this means exchanging information in ways that allow the receiving system or organisation to understand and use it. In payments, it means making different payment accounts, providers or systems work together, for example through shared platforms or common acceptance standards. The practical requirements depend on the relevant service and requirements; the term alone does not establish a particular legal duty. specifications for the exportable data.

    Data Act, Article 26

  • Publish jurisdiction and access safeguards

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Publish on the website, and keep up to date, the jurisdiction of the ICTInformation and Communication Technology infrastructure used for each service and a general description of the measures against international governmental access to non-personal dataIn the EU Data Act, data that is not personal data: it does not relate to an identified or identifiable individual. This can include machine measurements with no link to a person, or information genuinely anonymised so people cannot be identified. Removing names alone may not be enough. Non-personal data can still be commercially sensitive and subject to contractual, security or other legal protections. held in the Union where that conflicts with Union or national law. List those websites in contracts.

    Data Act, Article 28

  • Withdrawal of switching charges

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Charge nothing for switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. from 12 January 2027. From 11 January 2024 to 12 January 2027, reduced charges may be applied, limited to the costs directly linked to the switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges.. Before contracting, give clear information on standard fees, early termination penalties and any reduced switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. charges, and on services where switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. is highly complex or costly.

    Data Act, Article 29(1) to (6)

Nothing in the acts covered.

Rights of individuals

Only Data Act no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.DM-P

  • Data accessible by design and by default

    Applies to: Manufacturers of connected productsAn item that obtains, generates or collects data about its use or environment, can communicate product data through an electronic communications service, a physical connection or on-device access and whose primary function is not storing, processing or transmitting data on behalf of a party other than the user. The Data Act gives users access rights for covered product data under the conditions it sets. and providers of related servicesRelated Service (Data Act)

    Design and manufacture connected productsAn item that obtains, generates or collects data about its use or environment, can communicate product data through an electronic communications service, a physical connection or on-device access and whose primary function is not storing, processing or transmitting data on behalf of a party other than the user. The Data Act gives users access rights for covered product data under the conditions it sets., and design and provide related servicesRelated Service (Data Act), so that product and related service data and the metadataInformation describing other data, such as its format, structure, meaning or security labels. It helps people and systems find, interpret and use the underlying information. In the EU Data Act, metadata specifically means a structured description of the contents or use of data that facilitates finding or using it. The Act's access provisions can therefore concern both the data and the information needed to understand it. needed to use them are accessible to the user by default. Access is easy, secure, free of charge and in a comprehensive, structured, commonly used and machine-readable format, and direct where relevant and technically feasible. This applies to products and services placed on the market after 12 September 2026.

    Data Act, Article 3(1)

  • Give the user access to readily available data

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties.

    Where the user cannot access data directly, make readily available data and metadataInformation describing other data, such as its format, structure, meaning or security labels. It helps people and systems find, interpret and use the underlying information. In the EU Data Act, metadata specifically means a structured description of the contents or use of data that facilitates finding or using it. The Act's access provisions can therefore concern both the data and the information needed to understand it. accessible on a simple request, without undue delay, of the same quality as the data holderUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. has, easily, securely, free of charge and in a machine-readable format, and continuously and in real time where relevant and technically feasible. Do not make the user's choices unduly difficult, ask only for the information needed to verify the user, and keep no access logs beyond what is necessary.

    Data Act, Article 4(1), (4) and (5)

  • Share data with a third party at the user's request

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. and gatekeepersAn undertaking providing core platform services that the Commission has designated under the Digital Markets Act because it has a significant impact on the internal market, runs an important gateway between business users and end users and holds an entrenched and durable position. Gatekeepers must follow DMA obligations and prohibitions. designated under the Digital Markets ActRegulation (EU) 2022/1925, an EU law intended to make digital markets fairer and easier for businesses to enter and compete in. It sets duties for providers that the European Commission designates as gatekeepers for specified core platform services, such as app stores or online search. Business users and end users benefit from the requirements even when they are not gatekeepers themselves. The DMA is separate from the Digital Services Act.

    At the request of the user, or a party acting for the user, make readily available data and metadataInformation describing other data, such as its format, structure, meaning or security labels. It helps people and systems find, interpret and use the underlying information. In the EU Data Act, metadata specifically means a structured description of the contents or use of data that facilitates finding or using it. The Act's access provisions can therefore concern both the data and the information needed to understand it. available to a third party without undue delay, of the same quality as the data holderUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. has, free of charge to the user and in a machine-readable format, under the terms of Articles 8 and 9. GatekeepersAn undertaking providing core platform services that the Commission has designated under the Digital Markets Act because it has a significant impact on the internal market, runs an important gateway between business users and end users and holds an entrenched and durable position. Gatekeepers must follow DMA obligations and prohibitions. under the Digital Markets ActRegulation (EU) 2022/1925, an EU law intended to make digital markets fairer and easier for businesses to enter and compete in. It sets duties for providers that the European Commission designates as gatekeepers for specified core platform services, such as app stores or online search. Business users and end users benefit from the requirements even when they are not gatekeepers themselves. The DMA is separate from the Digital Services Act. are not eligible third parties.

    Data Act, Article 5(1) and (3)

  • Exclusion for micro and small enterprises Optional

    Applies to: Micro and small enterprises, and medium-sized enterprises in their first year or for products in their first year on the market

    The Chapter II access and sharing obligations do not apply to data from products made or designed, or related servicesRelated Service (Data Act) provided, by a micro or small enterprise, unless it has a larger partner or linked enterprise or is subcontracted to make, design or provide them. The same applies to an enterprise that has been medium-sized for less than one year, and to a medium-sized enterprise's products for one year after market placement.

    Data Act, Article 7(1)

Nothing in the acts covered.

International transfers

Only Data Act no specific requirement on the other side in the acts covered

  • Publish jurisdiction and access safeguards

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Publish on the website, and keep up to date, the jurisdiction of the ICTInformation and Communication Technology infrastructure used for each service and a general description of the measures against international governmental access to non-personal dataIn the EU Data Act, data that is not personal data: it does not relate to an identified or identifiable individual. This can include machine measurements with no link to a person, or information genuinely anonymised so people cannot be identified. Removing names alone may not be enough. Non-personal data can still be commercially sensitive and subject to contractual, security or other legal protections. held in the Union where that conflicts with Union or national law. List those websites in contracts.

    Data Act, Article 28

  • Prevent unlawful governmental access

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Take all adequate technical, organisational and legal measures, including contracts, to prevent international and third-country governmental access to or transfer of non-personal dataIn the EU Data Act, data that is not personal data: it does not relate to an identified or identifiable individual. This can include machine measurements with no link to a person, or information genuinely anonymised so people cannot be identified. Removing names alone may not be enough. Non-personal data can still be commercially sensitive and subject to contractual, security or other legal protections. held in the Union where it would conflict with Union or national law. A third-country decision is recognised or enforceable only if it is based on an international agreement.

    Data Act, Article 32(1) and (2)

  • Handling third-country access requests

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Without an international agreement, give access only where the Article 32(3) conditions on reasons, review and consideration of protected interests are met. If the provider asks the competent national body for its opinion and gets no reply within one month, or the body finds the conditions are not met, the provider may reject the request. It must ask that body where national security or defence may be affected. Provide the minimum data permissible, and inform the customer before complying unless the request serves law enforcement and only for as long as needed to keep that effective.

    Data Act, Article 32(3) to (5)

Nothing in the acts covered.

Supervision and enforcement

Cooperation with supervisors

Only Data Act no specific requirement on the other side in the acts covered

  • Restricting access for product security Optional

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties.

    Users and data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. may agree by contract to restrict or prohibit access, use or further sharing where it could undermine the product's legal security requirements and seriously harm the health, safety or security of people. A data holderUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. that refuses to share on this ground notifies the competent authority.

    Data Act, Article 4(2)

  • Withhold or refuse data to protect trade secrets Optional

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties.

    A data holderUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. may withhold or suspend trade secret data where measures are not agreed, not implemented or confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available. is undermined. In exceptional cases a trade secret holder may refuse a specific request if it shows serious economic damage is highly likely. The decision is reasoned and given in writing without undue delay, and the competent authority is notified.

    Data Act, Articles 4(7), 4(8), 5(10) and 5(11)

  • Provide data to public bodies on an exceptional need

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. that are legal persons, other than public sector bodies

    On a duly reasoned request showing an exceptional need, make the data available to the public sector body, Commission, European Central BankThe central bank for the euro area, the EU countries that use the euro. Its main task is to keep prices stable. It also supports financial stability and payment infrastructure. In European banking supervision, it works with participating national supervisory authorities to oversee banks and strengthen the banking system. or Union body without undue delay. Decline or seek a change only on the listed grounds, within five working days for a public emergency and within 30 working days in other cases. Where declining because of an earlier request for the same purpose, name the body that made it. Anonymise personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity., or pseudonymise it where the request requires personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity..

    Data Act, Articles 14 and 18(1) to (4)

Nothing in the acts covered.

Penalties and liability

Only Data Act no specific requirement on the other side in the acts covered

  • Penalties

    Applies to: Member States

    Member States set effective, proportionate and dissuasive penalties and notify the requirements to the Commission by 12 September 2025. For Chapters II, III and V, data protection supervisory authorities may also impose fines within their competence, up to the GDPRGeneral Data Protection Regulation Article 83(5) amount.

    Data Act, Article 40(1), (2) and (4)

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.

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…