Determine which role creates the obligation
For NIS2, assess the entity's sector, size or other inclusion criteria, services and jurisdiction. For the CRA, determine whether the activity concerns making a product with digital elements available on the EU market and which economic-operator obligations are relevant.
A manufacturer operating a covered digital service can face both sets of obligations. However, the mere presence of software within a business does not automatically make that business subject to all CRA manufacturer duties.
Compare the protected subject and requirements
NIS2 Article 21 concerns security of network and information systems used in the entity's operations and services, with organisational duties, supplier security and incident management. The CRA addresses product cybersecurity properties, vulnerability handling and manufacturer responsibilities across relevant product lifecycles.
Security updates can be relevant to both regimes, but they arise from different legal roles. Map the product, supported service and responsible teams separately.
Keep notification duties distinct
NIS2 Article 23 sets a framework for significant incidents affecting covered services. CRA reporting obligations address defined events related to products, including actively exploited vulnerabilities and severe incidents affecting product security, subject to the statute's application dates and conditions.
Do not send every event through one generic compliance clock. Identify the triggering facts, relevant authority or reporting platform, and which legal entity has the duty.
Check CRA application and transition dates
Regulation (EU) 2024/2847 has staggered application dates. Its principal provisions generally apply from 11 December 2027, while certain reporting obligations begin earlier, from 11 September 2026, and notified-body provisions from 11 June 2026.
At the October 2026 review date, distinguish obligations already applicable from forthcoming product requirements. Check the official consolidated position and the facts of any product transition.
Coordinate engineering and compliance evidence
Product security requirements, software component information, update support and vulnerability remediation may contribute evidence to both programmes. Preserve distinct legal scope assessments, manufacturer processes, covered-entity risk decisions and incident reporting routes.
Do not assume that meeting CRA product requirements alone demonstrates NIS2 entity compliance, or that NIS2 coverage makes a product CRA compliant.
Points of clarification
Does the CRA replace NIS2?
No. The regulations address different legal roles and subject matter, and both can be relevant to one business.
Are the CRA's main product duties already fully applicable in October 2026?
No. The CRA uses phased application dates, so specific duties and transitional provisions must be checked individually.