← Role Guides
Legal & ComplianceCRA Role Guide

EU Cyber Resilience Act — Guide for General Counsel

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

General Counsel carries ultimate legal accountability for the organisation's CRA compliance posture. The CRA creates legal obligations that span product design, documentation, market authorisation, ongoing vulnerability management, and mandatory reporting. Failures can result in administrative penalties, product withdrawal, reputational damage, and civil liability under the updated EU Product Liability Directive. Understanding the full scope of exposure — and the legal instruments available to manage it — is essential for effective GC oversight.

Your CRA responsibilities:

  • Assess the CRA's applicability to each product line and advise on product classification
  • Review and approve the Declaration of Conformity before CE marking is applied
  • Establish and manage the EU Authorised Representative relationship for non-EU manufacturers
  • Advise on NCA enforcement response strategy when market surveillance inquiries arise
  • Ensure contractual protections with suppliers address CRA supply chain obligations
  • Coordinate with regulatory affairs on technical file completeness and retention obligations
  • Assess product liability exposure under the updated EU Product Liability Directive and advise on insurance adequacy
Legal & Compliance

General counsel's CRA legal exposure

The CRA imposes obligations on the 'manufacturer' as a legal entity, meaning liability attaches at the corporate level. General Counsel must advise the board on the scope of that liability: administrative fines of up to €15 million or 2.5% of global annual turnover for most non-conformities, and up to €20 million or 4% for providing incorrect, incomplete, or misleading information to conformity assessment bodies or market surveillance authorities. These penalties are imposed by national market surveillance authorities, with appeals routed through national administrative or judicial processes. Beyond regulatory penalties, the updated EU Product Liability Directive — which entered into force alongside the CRA — enables economic operators to be held civilly liable for damage caused by defective products, including defective software. The CRA and the Product Liability Directive interact: a product that is non-conformant with the CRA's security requirements is more readily characterised as 'defective' under the Directive.

CRA reference:Article 64

Declaration of Conformity and EU Authorised Representative obligations

Article 23 requires manufacturers to draw up an EU Declaration of Conformity (DoC) for each product, confirming that it meets the CRA's requirements. The DoC must be signed by the manufacturer or their authorised representative and must reference the conformity assessment procedure used. Annex V specifies the mandatory content: manufacturer identity, product description, applicable EU legislation, a reference to harmonised standards relied upon (if any), and the place and date of issue. For manufacturers not established in the EU, Article 23 requires appointment of an EU Authorised Representative before placing the product on the market. The Authorised Representative agreement must be in writing, must specify the products covered, and must grant the Representative authority to cooperate with market surveillance authorities on the manufacturer's behalf. The Representative holds a copy of the technical file and the DoC and must make them available to NCAs within defined timeframes.

CRA reference:Article 23, Annex V

NCA enforcement response preparation

National competent authorities have broad investigative and enforcement powers under the CRA. They may request access to the technical file and DoC, conduct product evaluations, issue requests for corrective action, restrict product sales, or initiate product recalls. General Counsel should prepare the organisation for NCA engagement before it occurs. This means: ensuring the technical file is retrievable and audit-ready within the response window that will be specified in any NCA notice; establishing a designated legal contact for NCA correspondence; preparing a template NCA response protocol that involves legal, regulatory affairs, and the relevant technical teams; and identifying external regulatory counsel experienced in CRA enforcement in each key Member State market. Where an NCA identifies a potential non-conformity, early engagement and a credible corrective action plan will significantly reduce the risk of formal penalties.

CRA reference:Article 41, Article 43, Article 58

CRA product liability intersection

The Directive on Liability for Defective Products (the updated Product Liability Directive, which replaced the 1985 Directive) extends liability to software and includes provisions specifically relevant to CRA non-conformity. Under the updated Directive, a product is 'defective' if it does not provide the safety that the public is entitled to expect — and products that fail to meet the CRA's Annex I security requirements are likely to be characterised as defective where that failure causes harm. The Directive reverses the burden of proof in certain circumstances and introduces disclosure obligations that require manufacturers to provide claimants with relevant technical documentation. General Counsel should assess product liability exposure for each product line, confirm that commercial insurance covers CRA-related claims, and advise engineering and product teams on the liability implications of known-but-unpatched vulnerabilities left in released products.

CRA reference:Article 13, Annex I

Getting started checklist

Commission an internal legal review mapping each in-scope product against CRA obligations and identifying current gaps. Review commercial contracts with key suppliers to confirm CRA-relevant terms — SBOM delivery, vulnerability notification, audit rights — are present or must be added on renewal. If the company is not established in the EU, identify and contract with an EU Authorised Representative immediately. Review the DoC template for each product class and confirm it satisfies Annex V requirements. Assess whether existing product liability insurance adequately covers CRA-related claims and request insurer confirmation in writing. Brief the board on the penalty exposure and the legal instruments for mitigation. Establish a retention policy for technical file documents covering the required ten-year period after last placement on the market.

CRA reference:Article 23, Annex V, Article 64, Article 13

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 GCs and their teams.

Start your free portal

Frequently asked by GCs

Can a subsidiary's non-compliance create liability for the parent company?+

The CRA's penalty provisions target the 'manufacturer' — the legal entity that places the product on the EU market. Where a subsidiary is the manufacturer, liability attaches to the subsidiary. However, parent companies may face exposure through two routes: first, if the parent company participates in placing the product on the market (for example, by holding the CE marking in its own name), it may be considered a co-manufacturer; second, in corporate law systems that permit group liability for regulatory breaches, parent company involvement in the non-compliance may attract liability. General Counsel should review the corporate structure and determine at which entity level CRA obligations are held for each product line.

Are there specific legal privilege considerations for CRA technical files?+

Technical files are regulatory documents, not legal privileged communications, and manufacturers must make them available to market surveillance authorities on request. Documents prepared by lawyers specifically to advise on legal strategy in response to an NCA investigation may attract legal professional privilege, but this protection applies to the legal advice, not to the underlying technical file. General Counsel should advise technical teams that the technical file is a regulatory document that should be accurate and complete, and should not contain speculative or preliminary draft content that could be mischaracterised in enforcement proceedings.

How should the General Counsel respond to a manufacturer liability claim arising from an actively exploited CRA product vulnerability?+

Immediately preserve all relevant documentation: the technical file, vulnerability triage records, SBOM at the time of the release in question, Article 14 notification records (if applicable), and internal communications about the vulnerability's discovery and remediation decision. Assess whether the claim triggers any notification obligation to insurers or regulators. Engage external product liability counsel experienced in EU digital product claims. Determine whether the vulnerability was known at the time of placing the product on the market — if so, this is the most significant liability factor under both the CRA and the Product Liability Directive. Cooperate with any parallel NCA investigation through separate legal representation if necessary to avoid conflicts of interest.

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 →