Identify different legal subjects
NIS2 applies to specific entity types under its scope and Member State rules. The Data Act concerns actors including users of connected products, data holders, data recipients and providers of data processing services under particular chapters.
A manufacturer of a connected product or a cloud provider should determine its role under each law instead of treating all digital services as equally regulated.
Compare obligations for connected product data
Data Act rights and duties concern making certain data available and the conditions of access and use. NIS2 Article 21 concerns proportionate safeguards protecting network and information systems used by covered entities.
Data access rights do not automatically authorise insecure interfaces. Design access, authentication and authorisation to meet applicable duties without promising unrestricted exposure.
Examine cloud switching and interoperability
Data Act provisions address contractual, technical and commercial barriers to switching data processing services. NIS2 business continuity, supplier security and secure system maintenance may influence how switching is executed safely.
Maintain inventories of data, identities, service integrations and dependencies. Test the transition and termination process rather than assuming portability clauses alone establish operational resilience.
Distinguish incidents from data access disputes
A cyberattack affecting covered services may invoke NIS2 incident-handling and significant-incident reporting. A disagreement over statutory data access or switching obligations is not automatically a significant NIS2 incident.
Separate technical incident records, data-access requests and regulatory assessments. If personal data is involved, consider GDPR obligations independently.
Check application dates and exclusions
The Data Act generally applies from 12 September 2025, subject to provision-specific timing and transitional rules. Evaluate the product, service and relevant contract against the actual applicable provisions.
Do not assume every Data Act duty was applicable to all legacy contracts or every connected device from the same date. Check the official Regulation and any amendments.
Maintain a cross-regime compliance map
Record the legal entity, role, covered services, Data Act chapter, NIS2 classification, technical control owner and appropriate evidence. Reuse security controls where suitable without merging distinct reporting and enforcement routes.
Review Member State NIS2 law and current EU guidance. A Data Act contract review does not establish NIS2 compliance.
Points of clarification
Does compliance with one EU law automatically satisfy NIS2?
No. The relevant scope, legal duties and evidence must be assessed under each instrument.
Can a single organisation be subject to both frameworks?
Yes, where its legal entities, activities or products meet the relevant scope conditions.