← Role Guides
Legal & ComplianceCRA Role Guide

EU Cyber Resilience Act — Guide for Regulatory Affairs Manager

What the CRA means for your role, your team, and your day-to-day responsibilities.

Regulatory affairs professionals occupy the interface between legal obligation and technical implementation. Under the Cyber Resilience Act, they are responsible for selecting and executing the correct conformity assessment route, maintaining the technical file, managing the Declaration of Conformity, and engaging with national competent authorities when required. They must also track how CRA obligations interact with NIS2, the Medical Device Regulation, the Radio Equipment Directive, and other concurrent obligations.

Your CRA responsibilities:

  • Determine product classification (Default, Class I Important, Class II Important) and select the appropriate conformity assessment route
  • Manage the technical file compilation and ensure it satisfies Annex VII requirements
  • Draft and maintain the EU Declaration of Conformity in accordance with Annex V
  • Establish and manage the EU Authorised Representative relationship where the manufacturer is outside the EU
  • Monitor delegated acts, implementing regulations, and harmonised standards published under the CRA
  • Coordinate with national competent authorities during market surveillance activities
  • Map CRA obligations against NIS2, MDR, RED, and other applicable EU regulations
Legal & Compliance

Regulatory affairs role under the CRA

Regulatory affairs managers are responsible for navigating the CRA's conformity assessment framework and ensuring the organisation selects the correct route to CE marking. The CRA establishes three categories: Default products (the large majority) can self-assess against Annex I using internal procedures. Class I Important Products — those presenting elevated risk, such as network switches, VPNs, and password managers — can self-assess but may also use harmonised standards or third-party audit to demonstrate conformity. Class II Important Products — the highest-risk category, including industrial control systems, smartcard operating systems, and hardware security devices — require mandatory third-party assessment by an accredited notified body. Misclassifying a product or selecting an inappropriate assessment route constitutes a regulatory breach independent of the product's actual security posture.

CRA reference:Article 24, Annex VIII

Navigating national competent authority relationships

Member States designate national competent authorities (NCAs) to conduct market surveillance under the CRA. NCAs have the power to request technical files, conduct product evaluations, issue product recalls, and impose financial penalties. Regulatory affairs managers should identify the relevant NCA in each Member State where the product is marketed and maintain a relationship before any enforcement action arises. If an NCA initiates a market surveillance inquiry, the manufacturer has limited time to respond with technical documentation. The regulatory affairs manager should ensure the technical file is audit-ready at all times — not assembled retrospectively. Where an NCA identifies a non-conformity, the manufacturer may have the opportunity to implement corrective action before formal penalties are imposed, but only if the response is timely and demonstrates genuine remediation.

CRA reference:Article 41, Article 43, Article 58

CRA + NIS2 + MDR multi-regulation overlap

Many manufacturers are subject to overlapping EU cybersecurity regulations. NIS2 applies to essential and important entities and imposes incident reporting and security management obligations that partially overlap with CRA Article 14. Where a manufacturer is both a CRA-obligated manufacturer and a NIS2-obligated entity, regulatory affairs must map the obligations carefully to avoid duplicate or conflicting processes. The Medical Device Regulation imposes its own cybersecurity requirements for software as a medical device — ENISA has published guidance on harmonising CRA and MDR obligations. The Radio Equipment Directive (RED) introduced cybersecurity requirements in Article 3(3)(d)-(f) for wireless devices, and the Commission has indicated that CRA conformity will satisfy RED cybersecurity requirements for products in scope of both regulations. Regulatory affairs managers should produce a regulatory matrix for each product line that maps all applicable obligations.

CRA reference:Article 2, Recital 16

Monitoring delegated acts and implementing regulations

The CRA delegates significant detail to the European Commission through delegated acts and implementing regulations. Key areas subject to further specification include: the definitive list of Class I and Class II Important Products (Annex III), the format and content of Article 14 notifications, the technical file content requirements, and any sector-specific adaptations. Harmonised standards published by ETSI and CEN-CENELEC under a CRA standardisation request will provide presumption of conformity and significantly reduce the technical file burden for manufacturers who comply with them. Regulatory affairs managers should subscribe to the Official Journal of the European Union, monitor ENISA publications, and track the standardisation bodies' work programmes. Standards that are expected to be particularly relevant include EN 303 645, IEC 62443, and ISO/IEC 27001 adapted for product security contexts.

CRA reference:Article 5, Article 27, Annex III

Getting started checklist

Begin by classifying every in-scope product line against the Default / Class I / Class II Important Product criteria in Annex III and the product descriptions in ENISA guidance documents. For each product, document the chosen conformity assessment route and the justification for that choice. Compile an inventory of the technical file artefacts already available and identify gaps. Draft or review the EU Declaration of Conformity template for each product class. If the manufacturer is established outside the EU, confirm that an EU Authorised Representative has been appointed and that the appointment agreement covers all CRA obligations including market surveillance cooperation. Produce a regulatory matrix mapping CRA obligations against all other applicable EU regulations. Set calendar reminders for the publication of implementing regulations anticipated before the December 2027 application date.

CRA reference:Annex V, Annex VII, Article 23

CVD Portal handles your CRA Article 13 obligations automatically.

Public CVD submission portal, 48-hour acknowledgment tracking, Article 14 deadline alerts, and CSAF advisory generation — built for Reg Affairss and their teams.

Start your free portal

Frequently asked by Reg Affairss

When does the CRA apply, and what is the transition timeline?+

The CRA entered into force on 10 December 2024. The Article 14 vulnerability reporting obligations apply from 11 September 2026. The full CRA requirements — including conformity assessment, technical file, and CE marking — apply from 11 December 2027. Products placed on the EU market before 11 December 2027 are not required to comply, but products that remain on the market and receive substantial modifications may require re-assessment. Regulatory affairs managers should plan their conformity assessment projects with the December 2027 deadline in mind, allowing time for notified body assessment for Class II Important Products.

What is the EU Authorised Representative's liability under the CRA?+

Article 23 requires manufacturers established outside the EU to appoint an EU Authorised Representative before placing products on the EU market. The Authorised Representative acts on the manufacturer's behalf for regulatory purposes: they hold a copy of the technical file, cooperate with market surveillance authorities, and are the point of contact for CRA obligations in the EU. Importantly, the Authorised Representative does not inherit the manufacturer's full liability — they are not liable for product non-conformities — but they do carry liability for failures to perform their own regulatory obligations, including failure to cooperate with an NCA investigation.

How often must the technical file be updated?+

The technical file must be kept current throughout the product's active market life and retained for ten years after the product is last placed on the market. It must be updated when: a new product version is released; a vulnerability is discovered that required a design change; the conformity assessment is renewed or changed; or a delegated act or harmonised standard changes the conformity basis. The technical file is a living document — regulatory affairs managers should establish a document management system that links file updates to the product release and vulnerability management processes.

Need a CVD policy template your team can deploy today?

Free CRA-compliant templates for every stage — from first CVD policy to full PSIRT programme.

Browse templates →