> 12 CFR 748 vs Data Act side by side, topic by topic: where they overlap, where they differ and which asks more, with incident deadlines, testing, third parties and fines.

# 12 CFR 748 vs Data Act

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

[12 CFR 748](https://grc.plus/regulation/us-ncua-cyber-incident-notification/)Every federally insured credit union, including federally insured state-chartered and corporate credit unions.

[Data Act](https://grc.plus/regulation/eu-data-act/)Manufacturers and related service providers, data holders, providers of data processing services

## At a Glance

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

- **12 CFR 748** Asks more on 0 topics Alone on 4 topics More detailed on 0 topics
- **Data Act** Asks more on 1 topic Alone on 10 topics More detailed on 0 topics

| Topic | 12 CFR 748 | Data Act | Verdict |
| --- | --- | --- | --- |
| Governance |  |  |  |
| Awareness and training | 12 CFR 748: 1 | Data Act: – | **Only 12 CFR 748**no specific requirement on the other side in the acts covered |
| Protection |  |  |  |
| Data security | 12 CFR 748: – | Data Act: 6 | **Only Data Act**no specific requirement on the other side in the acts covered |
| Secure acquisition and development | 12 CFR 748: – | Data Act: 1 | **Only Data Act**no specific requirement on the other side in the acts covered |
| Detection and response |  |  |  |
| Incident handling | 12 CFR 748: 3 | Data Act: – | **Only 12 CFR 748**no specific requirement on the other side in the acts covered |
| Incident classification | 12 CFR 748: 5 | Data Act: – | **Only 12 CFR 748**no specific requirement on the other side in the acts covered |
| Reporting to authorities | 12 CFR 748: 5 | Data Act: – | **Only 12 CFR 748**no specific requirement on the other side in the acts covered |
| Informing customers and the public | 12 CFR 748: – | Data Act: 1 | **Only Data Act**no specific requirement on the other side in the acts covered |
| Third parties and supply chain |  |  |  |
| Contract requirements | 12 CFR 748: 1 | Data Act: 8 | **Data Act asks more**binding, where the other is optional |
| Exit and termination | 12 CFR 748: – | Data Act: 7 | **Only Data Act**no specific requirement on the other side in the acts covered |
| Privacy and data protection |  |  |  |
| Lawful processing | 12 CFR 748: – | Data Act: 2 | **Only Data Act**no specific requirement on the other side in the acts covered |
| Transparency | 12 CFR 748: – | Data Act: 4 | **Only Data Act**no specific requirement on the other side in the acts covered |
| Rights of individuals | 12 CFR 748: – | Data Act: 4 | **Only Data Act**no specific requirement on the other side in the acts covered |
| International transfers | 12 CFR 748: – | Data Act: 3 | **Only Data Act**no specific requirement on the other side in the acts covered |
| Supervision and enforcement |  |  |  |
| Cooperation with supervisors | 12 CFR 748: – | Data Act: 3 | **Only Data Act**no specific requirement on the other side in the acts covered |
| Penalties and liability | 12 CFR 748: – | Data Act: 1 | **Only Data Act**no specific requirement on the other side in the acts covered |

## What This Covers

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

Included

- [12 CFR 748](https://grc.plus/regulation/us-ncua-cyber-incident-notification/) 12 CFR 748.1(c), added by the NCUA final rule Cyber Incident Notification Requirements for Federally Insured Credit Unions, 88 FR 12811 (1 March 2023) 15 requirements

Status

Reviewed against the official texts.

Included

- [Data Act](https://grc.plus/regulation/eu-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](https://grc.plus/regulation/poland-data-act-implementing-bill/) 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.

## Key Numbers

### Deadline

12 CFR 748: Not in the acts covered

Data Act: Without undue delay after a simple request (Data holders); Without undue delay after the user's request (Data holders and gatekeepers designated under the Digital Markets Act); Without undue delay after a reasoned request (Data holders obliged to make data available); Decline within five working days of receipt for a public emergency, 30 working days of receipt otherwise (Data holders 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 services); Retrieval for at least 30 calendar days after the end of the transitional period (Providers of data processing services); Notify within 14 working days of the switching request; alternative period of at most seven months (Providers of data processing services); No switching charges from 12 January 2027 (Providers of data processing services); Compatibility at least 12 months after publication of the references in the central Union standards repository (Providers of data processing services)

### Threshold

12 CFR 748: Not in the acts covered

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)

### Goes to

12 CFR 748: Not in the acts covered

Data Act: Competent authority designated under Article 37 (Data holders); User or third party in writing; competent authority notified (Data holders); Customer, before complying (Providers of data processing services)

### Incident reports go to

12 CFR 748: Appropriate NCUA-designated point of contact.

Data Act: Not in the acts covered

### Incident notification

12 CFR 748: As soon as possible, and received by the NCUA no later than 72 hours after the credit union reasonably believes it has experienced a reportable cyber incident. For a third-party incident under paragraph (c)(1)(i)(C), use the earlier of that reasonable belief and notification by the third party.

Data Act: Not in the acts covered

### Deadline to have the measures in place

12 CFR 748: Not in the acts covered

Data Act: Products and related services placed on the market after 12 September 2026 (Manufacturers of connected products and providers of related services)

### Maximum fines

12 CFR 748: Not in the acts covered

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

## Governance

### Awareness and training

**Only 12 CFR 748** no specific requirement on the other side in the acts covered

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

- Train Employees on Incident Reporting Recommended
  NCUA implementation guidance recommends training all employees on cyber-incident reporting, their roles and the consequences of noncompliance, with resources and guidance to fulfil their responsibilities.
  [12 CFR 748, NCUA Letter 23-CU-07, Implementation Guidelines: Train Employees](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)

Nothing in the acts covered.

## Protection

### Data security

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

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

Nothing in the acts covered.

- Restricting access for product security Optional
  Applies to: Data holders
  Users and data holders 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 holder that refuses to share on this ground notifies the competent authority.
  [Data Act, Article 4(2)](https://grc.plus/regulation/eu-data-act/#requirements)
- Protect trade secrets when sharing
  Applies to: Data holders and trade secret holders
  Identify data protected as trade secrets, including in the metadata, 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)](https://grc.plus/regulation/eu-data-act/#requirements)
- Withhold or refuse data to protect trade secrets Optional
  Applies to: Data holders
  A data holder may withhold or suspend trade secret data where measures are not agreed, not implemented or confidentiality 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)](https://grc.plus/regulation/eu-data-act/#requirements)
- 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 data. 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 gatekeeper, use it to develop a competing product or derive insights about the data holder, 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)](https://grc.plus/regulation/eu-data-act/#requirements)
- Data retrieval and erasure
  Applies to: Providers of data processing services
  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 switching has succeeded.
  [Data Act, Article 25(2)(e), (g) and (h)](https://grc.plus/regulation/eu-data-act/#requirements)
- Prevent unlawful governmental access
  Applies to: Providers of data processing services
  Take all adequate technical, organisational and legal measures, including contracts, to prevent international and third-country governmental access to or transfer of non-personal data 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)](https://grc.plus/regulation/eu-data-act/#requirements)

### Secure acquisition and development

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

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

Nothing in the acts covered.

- Data accessible by design and by default
  Applies to: Manufacturers of connected products and providers of related services
  Design and manufacture connected products, and design and provide related services, so that product and related service data and the metadata 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)](https://grc.plus/regulation/eu-data-act/#requirements)

## Detection and response

### Incident handling

**Only 12 CFR 748** 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

- Update the Incident Response Plan Recommended
  NCUA implementation guidance recommends reviewing and updating the response plan to include reporting timeframes, NCUA notification procedures, reportability criteria and escalation to management and the regulator.
  [12 CFR 748, NCUA Letter 23-CU-07, Implementation Guidelines: Update Response Plan](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)
- Review and Exercise the Reporting Process Recommended
  NCUA implementation guidance recommends regular monitoring and review of the reporting process, periodic tests and exercises of response plans and procedures, and improvements based on lessons learned.
  [12 CFR 748, NCUA Letter 23-CU-07, Implementation Guidelines: Monitor and Review](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)
- Document Incidents and Reporting Decisions Recommended
  NCUA implementation guidance recommends documenting all cyber incidents, including those that are not reportable, and retaining records under the credit union's retention policies. Document indicators of compromise, relevant network/traffic information, attack vector, exfiltrated-data information and forensic or other incident reports. Keep an audit trail supporting management's reporting decisions. This does not authorise sending excluded technical material in the initial notice.
  [12 CFR 748, NCUA Letter 23-CU-07, Implementation Guidelines: Document All Incidents](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)

Nothing in the acts covered.

### Incident classification

**Only 12 CFR 748** no specific requirement on the other side in the acts covered

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

- Include Substantial Third-Party and Supply-Chain Incidents
  A substantial cyber incident is reportable if it leads to disruption of the credit union's business operations or unauthorised access to sensitive data, facilitated through or caused by a compromise of a credit union service organisation, cloud service provider, other third-party data hosting provider or the supply chain. An unrelated incident at a supplier is not automatically reportable. The credit union must report qualifying incidents using the earlier reasonable-belief or third-party-notice clock.
  [12 CFR 748, 12 CFR 748.1(c)(1)(i)(C)](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)
- Apply the Good-Faith Requested-Activity Exclusion Optional
  An event is excluded from the reportable-cyber-incident definition where an entity performs the cyber incident in good faith in response to a specific request by the system owner or operators, for example an authorised penetration test. Both good faith and the specific request are required.
  [12 CFR 748, 12 CFR 748.1(c)(1)(ii)](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)
- Assess Substantial Loss of Confidentiality, Integrity or Availability
  Treat a substantial cyber incident as reportable where it leads to a substantial loss of confidentiality, integrity or availability of a network or member information system that results from unauthorised access to or exposure of sensitive data, disrupts vital member services, or seriously affects the safety and resiliency of operational systems and processes. Apply the incorporated definitions in Appendix A, I.B.2.e, and 12 CFR 749.1.
  [12 CFR 748, 12 CFR 748.1(c)(1)(i)(A)](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)
- Assess Disruption From Cyberattacks and Exploited Vulnerabilities
  Treat a substantial cyber incident as reportable where it leads to disruption of business operations, vital member services or a member information system resulting from a cyberattack or exploitation of vulnerabilities. The overarching substantial-cyber-incident condition still applies.
  [12 CFR 748, 12 CFR 748.1(c)(1)(i)(B)](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)
- Assess Whether the Incident Is Substantial Recommended
  NCUA guidance expects reasonable judgment when assessing whether an incident is substantial, taking account of factors including credit union size, the type and impact of the loss and its duration. The rule does not prescribe a single numeric substantiality threshold.
  [12 CFR 748, NCUA Letter 23-CU-07, Summary](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)

Nothing in the acts covered.

### Reporting to authorities

**Only 12 CFR 748** no specific requirement on the other side in the acts covered

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

- Ensure the NCUA Receives Notice Within 72 Hours
  As soon as possible, and received by the NCUA no later than 72 hours after the credit union reasonably believes it has experienced a reportable cyber incident. For a third-party incident under paragraph (c)(1)(i)(C), use the earlier of that reasonable belief and notification by the third party. Do not wait for a detailed incident assessment before giving the initial alert.
  [12 CFR 748, 12 CFR 748.1(c)](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)
- Use an NCUA-Designated Reporting Channel
  Notify the appropriate NCUA-designated contact using email, telephone or a similar prescribed method. Current NCUA instructions allow the Cyber Incident Credit Union Reporting System webform, voicemail at 1.833.292.3728, or secure email to cybercu@ncua.gov through the NCUA Secure Email Message Center. Use the secure centre for email to ensure receipt.
  [12 CFR 748, 12 CFR 748.1(c); NCUA Letter 25-CU-02, How to Report and footnote 2](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)
- Provide the Known Initial Facts Recommended
  NCUA guidance recommends providing the credit union name and charter number, reporter name and title, callback/contact details, when the credit union reasonably believed a reportable incident had occurred, and a general description of affected services, information and operations. Give what is known at initial reporting; a detailed incident assessment is not required within the 72-hour period.
  [12 CFR 748, NCUA Letter 23-CU-07, What to Report; Cyber Incident Reporting Guide, What to Report](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)
- Keep Sensitive Technical Material Out of the Initial Notice Recommended
  NCUA reporting guidance directs credit unions not to include sensitive personally identifiable information, indicators of compromise, specific vulnerabilities or email attachments in the initial notification. This is agency reporting guidance, separately identified from the rule's statutory reporting trigger.
  [12 CFR 748, NCUA Letter 23-CU-07 and Cyber Incident Reporting Guide, What to Report](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)
- Contact the NCUA Promptly When Reportability Is Uncertain Recommended
  NCUA guidance recommends contacting the agency as soon as possible if the credit union is unsure whether a cyber incident is reportable. This does not replace the reporting obligation when its legal trigger is met.
  [12 CFR 748, NCUA Letter 23-CU-07, Summary](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)

Nothing in the acts covered.

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

Nothing in the acts covered.

- Handling third-country access requests
  Applies to: Providers of data processing services
  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)](https://grc.plus/regulation/eu-data-act/#requirements)

## Third parties and supply chain

### Contract requirements

**Data Act asks more** binding, where the other is optional

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

- Review Critical Provider Notification Terms Recommended
  NCUA implementation guidance recommends reviewing critical service-provider contracts for provisions requiring timely cyber-incident notification. The cyber notification rule itself does not impose a new requirement to amend those contracts.
  [12 CFR 748, NCUA Letter 23-CU-07, Implementation Guidelines: Review Contracts](https://grc.plus/regulation/us-ncua-cyber-incident-notification/#requirements)

- Protect trade secrets when sharing
  Applies to: Data holders and trade secret holders
  Identify data protected as trade secrets, including in the metadata, 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)](https://grc.plus/regulation/eu-data-act/#requirements)
- Limits on the data holder's own use
  Applies to: Data holders
  Use readily available non-personal data 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)](https://grc.plus/regulation/eu-data-act/#requirements)
- Fair, reasonable and non-discriminatory terms
  Applies to: Data holders obliged to make data available
  Where a business-to-business data sharing duty applies under Article 5 or other law, agree the arrangements with the data recipient 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)](https://grc.plus/regulation/eu-data-act/#requirements)
- No discrimination and no unrequested sharing
  Applies to: Data holders obliged to make data available
  Do not discriminate between comparable categories of data recipients, 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)](https://grc.plus/regulation/eu-data-act/#requirements)
- Reasonable compensation
  Applies to: Data holders 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 SME 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)](https://grc.plus/regulation/eu-data-act/#requirements)
- 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)](https://grc.plus/regulation/eu-data-act/#requirements)
- 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)](https://grc.plus/regulation/eu-data-act/#requirements)
- Switching terms in a written contract
  Applies to: Providers of data processing services
  Set out switching 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)](https://grc.plus/regulation/eu-data-act/#requirements)

### Exit and termination

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

NIST CSF 2.0 GV.SC

Nothing in the acts covered.

- Remove obstacles to switching
  Applies to: Providers of data processing services
  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](https://grc.plus/regulation/eu-data-act/#requirements)
- Switching terms in a written contract
  Applies to: Providers of data processing services
  Set out switching 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)](https://grc.plus/regulation/eu-data-act/#requirements)
- Data retrieval and erasure
  Applies to: Providers of data processing services
  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 switching has succeeded.
  [Data Act, Article 25(2)(e), (g) and (h)](https://grc.plus/regulation/eu-data-act/#requirements)
- Longer transition where 30 days is not feasible
  Applies to: Providers of data processing services
  Where the 30 day transition is technically unfeasible, notify the customer within 14 working days of the switching 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)](https://grc.plus/regulation/eu-data-act/#requirements)
- Information on switching
  Applies to: Providers of data processing services
  Tell the customer about available switching 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 interoperability specifications for the exportable data.
  [Data Act, Article 26](https://grc.plus/regulation/eu-data-act/#requirements)
- Withdrawal of switching charges
  Applies to: Providers of data processing services
  Charge nothing for switching 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 switching. Before contracting, give clear information on standard fees, early termination penalties and any reduced switching charges, and on services where switching is highly complex or costly.
  [Data Act, Article 29(1) to (6)](https://grc.plus/regulation/eu-data-act/#requirements)
- Technical support for switching
  Applies to: Providers of data processing services
  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)](https://grc.plus/regulation/eu-data-act/#requirements)

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

Nothing in the acts covered.

- Legal basis for personal data
  Applies to: Data holders
  Where the user is not the data subject, make personal data available to the user or third party only with a valid legal basis under GDPR Article 6 and, where relevant, under GDPR Article 9 and ePrivacy Article 5(3).
  [Data Act, Articles 4(12) and 5(7)](https://grc.plus/regulation/eu-data-act/#requirements)
- 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 data. 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 gatekeeper, use it to develop a competing product or derive insights about the data holder, 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)](https://grc.plus/regulation/eu-data-act/#requirements)

### Transparency

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

NIST Privacy Framework CM.AW-P

Nothing in the acts covered.

- Pre-contract information on the data
  Applies to: Sellers, rentors and lessors of connected products, and providers of related services
  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 service providers also state who the data holder 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)](https://grc.plus/regulation/eu-data-act/#requirements)
- Information on switching
  Applies to: Providers of data processing services
  Tell the customer about available switching 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 interoperability specifications for the exportable data.
  [Data Act, Article 26](https://grc.plus/regulation/eu-data-act/#requirements)
- Publish jurisdiction and access safeguards
  Applies to: Providers of data processing services
  Publish on the website, and keep up to date, the jurisdiction of the ICT infrastructure used for each service and a general description of the measures against international governmental access to non-personal data held in the Union where that conflicts with Union or national law. List those websites in contracts.
  [Data Act, Article 28](https://grc.plus/regulation/eu-data-act/#requirements)
- Withdrawal of switching charges
  Applies to: Providers of data processing services
  Charge nothing for switching 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 switching. Before contracting, give clear information on standard fees, early termination penalties and any reduced switching charges, and on services where switching is highly complex or costly.
  [Data Act, Article 29(1) to (6)](https://grc.plus/regulation/eu-data-act/#requirements)

### Rights of individuals

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

NIST Privacy Framework CT.DM-P

Nothing in the acts covered.

- Data accessible by design and by default
  Applies to: Manufacturers of connected products and providers of related services
  Design and manufacture connected products, and design and provide related services, so that product and related service data and the metadata 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)](https://grc.plus/regulation/eu-data-act/#requirements)
- Give the user access to readily available data
  Applies to: Data holders
  Where the user cannot access data directly, make readily available data and metadata accessible on a simple request, without undue delay, of the same quality as the data holder 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)](https://grc.plus/regulation/eu-data-act/#requirements)
- Share data with a third party at the user's request
  Applies to: Data holders and gatekeepers designated under the Digital Markets Act
  At the request of the user, or a party acting for the user, make readily available data and metadata available to a third party without undue delay, of the same quality as the data holder has, free of charge to the user and in a machine-readable format, under the terms of Articles 8 and 9. Gatekeepers under the Digital Markets Act are not eligible third parties.
  [Data Act, Article 5(1) and (3)](https://grc.plus/regulation/eu-data-act/#requirements)
- 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 services 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)](https://grc.plus/regulation/eu-data-act/#requirements)

### International transfers

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

Nothing in the acts covered.

- Publish jurisdiction and access safeguards
  Applies to: Providers of data processing services
  Publish on the website, and keep up to date, the jurisdiction of the ICT infrastructure used for each service and a general description of the measures against international governmental access to non-personal data held in the Union where that conflicts with Union or national law. List those websites in contracts.
  [Data Act, Article 28](https://grc.plus/regulation/eu-data-act/#requirements)
- Prevent unlawful governmental access
  Applies to: Providers of data processing services
  Take all adequate technical, organisational and legal measures, including contracts, to prevent international and third-country governmental access to or transfer of non-personal data 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)](https://grc.plus/regulation/eu-data-act/#requirements)
- Handling third-country access requests
  Applies to: Providers of data processing services
  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)](https://grc.plus/regulation/eu-data-act/#requirements)

## Supervision and enforcement

### Cooperation with supervisors

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

Nothing in the acts covered.

- Restricting access for product security Optional
  Applies to: Data holders
  Users and data holders 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 holder that refuses to share on this ground notifies the competent authority.
  [Data Act, Article 4(2)](https://grc.plus/regulation/eu-data-act/#requirements)
- Withhold or refuse data to protect trade secrets Optional
  Applies to: Data holders
  A data holder may withhold or suspend trade secret data where measures are not agreed, not implemented or confidentiality 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)](https://grc.plus/regulation/eu-data-act/#requirements)
- Provide data to public bodies on an exceptional need
  Applies to: Data holders 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 Bank 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 data, or pseudonymise it where the request requires personal data.
  [Data Act, Articles 14 and 18(1) to (4)](https://grc.plus/regulation/eu-data-act/#requirements)

### Penalties and liability

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

Nothing 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 GDPR Article 83(5) amount.
  [Data Act, Article 40(1), (2) and (4)](https://grc.plus/regulation/eu-data-act/#requirements)

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

## More Comparisons

- [Compare 12 CFR 748](https://grc.plus/compare/12-cfr-748/)
- [Compare Data Act](https://grc.plus/compare/data-act/)

Source: https://grc.plus/compare/12-cfr-748-vs-data-act/
