By DataTip · Published
TL;DR: A manufacturer can have CRA reporting duties when it places a covered product with digital elements on the EU market, even if the business or product is based elsewhere. Selling through a distributor does not by itself transfer the manufacturer's responsibility. Importers and distributors have separate notification duties and can become manufacturers through branding or substantial modification.
- The product need not be created in the EU; placement of a covered product on the EU market is the relevant trigger described here.
- Selling through a distributor does not by itself transfer the manufacturer's reporting duty.
- Importers and distributors generally notify the manufacturer and relevant authorities rather than filing reports themselves, but can become manufacturers through branding or substantial modification.
- Standalone SaaS is generally outside the CRA, subject to the stated remote data processing solution caveat.
- The reporting categories are actively exploited vulnerabilities and severe incidents, including potential negative effects on product security.
A business can have CRA reporting duties for a connected product placed on the EU market even if the business and product are based elsewhere. A US company selling through a distributor is one example: the distributor does not automatically take over the manufacturer’s reporting responsibility.
A manufacturer can have CRA reporting duties when it places a covered product with digital elements on the EU market, even if the business or product is based elsewhere. Selling through a distributor does not by itself transfer the manufacturer’s responsibility. Importers and distributors have separate notification duties and can become manufacturers through branding or substantial modification.
The EU Cyber Resilience Act (CRA) reporting requirements for actively exploited vulnerabilities and severe incidents took effect on September 11, 2026. The broader product-compliance regime is scheduled to apply from December 11, 2027. Fisher Phillips describes the reporting requirements as live for manufacturers facing the CRA’s reporting rules. Its overview of the EU Cyber Resilience Act characterizes the law as covering products with digital elements.
What products fall within CRA reporting duties?
The CRA covers a broad range of products with digital elements, including software and hardware, related remote data processing solutions, and components placed on the market separately. Examples include industrial controllers, connected consumer devices, operating systems, mobile applications, network equipment and firmware. Fisher Phillips also describes the CRA as an EU cybersecurity law for products with digital elements. Its account of the reporting requirements provides context for why product scope matters.

The scope has exclusions. The categories include medical devices and in vitro diagnostics, type-approved motor vehicles, certified civil aviation equipment and marine equipment. It also excludes specified products developed or modified exclusively for national security or defence, products designed to process classified information, and qualifying spare parts manufactured to the same specifications as the parts they replace.
Standalone software-as-a-service is generally outside the CRA. The exception described here is a remote data processing solution designed and developed by the manufacturer that the product cannot perform its functions without. That product-dependency condition matters: standalone SaaS is not automatically covered simply because it is software. Other regimes, including NIS2 or DORA, might come into play, but that possibility does not establish that either applies to a particular SaaS business.
Who has CRA reporting duties when a product crosses borders?
The manufacturer bears the reporting duty. A manufacturer is a person or entity that develops or manufactures a product with digital elements, or has it designed, developed or manufactured, and markets it under its own name or trademark. The product may be sold for payment, monetized in another way or supplied free of charge.
For CRA reporting, the product does not need to have been created in the EU. The relevant trigger is placing a covered product on the EU market. The source’s example is a US company selling into the EU through a distributor: the company is treated as a manufacturer under the CRA and must report. Using a distributor does not, by itself, remove that responsibility.
A manufacturer established outside the EU must also designate an authorized representative in the EU. This is a separate requirement from determining which business has the manufacturer role. A company selling across borders should consider which entity develops or commissions the product and whose name or trademark is used to market it; the general rule does not settle every corporate, contractual or distribution arrangement.
How do importer and distributor duties differ?
Importers and distributors generally do not file CRA reports themselves, but they do have notification duties. If either becomes aware of a product vulnerability, it must inform the manufacturer without undue delay. If the product presents a significant cybersecurity risk, the importer or distributor must immediately inform the relevant Member State market-surveillance authorities.
An importer or distributor can become the manufacturer for CRA purposes. That happens if it markets the product under its own name or trademark, or substantially modifies a product already on the market. Private-label and white-label arrangements therefore merit close review: branding or substantial modification can change which party has the manufacturer role and its associated reporting duty.
If your business is involved in these arrangements, consider which entity is treated as the manufacturer and who within the business will assess that question. The CRA role depends on the facts described above; the responsibilities of particular internal departments are not specified here.
What is different for open-source software stewards?
Open-source software stewards follow a separate, lighter regime rather than the manufacturer reporting regime described above. The European Commission’s stated start date for steward reporting obligations is December 11, 2027. That is distinct from the reporting requirements for actively exploited vulnerabilities and severe incidents that took effect on September 11, 2026.
Which vulnerabilities and incidents can trigger reporting?
The two reporting categories are actively exploited vulnerabilities and severe incidents. They are distinct: one concerns malicious exploitation of a vulnerability, while the other concerns negative effects on product security.

An actively exploited vulnerability requires reliable evidence that a malicious actor exploited a vulnerability in a system without the system owner’s permission. Good-faith testing and coordinated disclosure without malicious intent do not trigger this reporting duty. The distinction is about evidence of malicious exploitation, not merely the discovery or disclosure of a weakness.
A severe incident concerns actual or potential negative effects on product security, including effects on data or functions. It also includes an incident that has led, or could lead, to malicious code being introduced or executed in a product or in a user’s network. Potential effects matter; the definition is not limited to incidents with an already-established negative outcome.
A compromise of a manufacturer’s own development, production or maintenance environment may also be relevant if it could increase cybersecurity risk for users. The practical question is whether the incident could affect the security of the product or users, not only whether the compromise occurred in a customer-facing system.
Frequently asked questions
Does the CRA apply to products developed outside the EU?
Yes. A product need not be created in the EU for the manufacturer reporting duty to apply. The relevant trigger described here is placing a covered product on the EU market. A manufacturer established outside the EU must also designate an authorized representative in the EU.
Does selling through an EU distributor transfer the manufacturer’s reporting duty?
No, not by itself. The US-company example treats the company selling the product into the EU through a distributor as the manufacturer, with the reporting duty. An importer or distributor may become the manufacturer if it uses its own name or trademark or substantially modifies the product.
When does an importer or distributor have to report a vulnerability?
Importers and distributors generally do not file reports themselves. When they become aware of a product vulnerability, they must inform the manufacturer without undue delay; if the product presents a significant cybersecurity risk, they must immediately inform the relevant Member State market-surveillance authorities.
Are standalone SaaS products covered by the CRA?
Standalone SaaS is generally outside the CRA. The stated exception concerns a manufacturer-designed and -developed remote data processing solution that the product cannot perform its functions without. Whether another regime might apply is a separate question.
Key takeaways
- The product need not be created in the EU; placement of a covered product on the EU market is the relevant trigger described here.
- Selling through a distributor does not by itself transfer the manufacturer’s reporting duty.
- Importers and distributors generally notify the manufacturer and relevant authorities rather than filing reports themselves, but can become manufacturers through branding or substantial modification.
- Standalone SaaS is generally outside the CRA, subject to the stated remote data processing solution caveat.
- The reporting categories are actively exploited vulnerabilities and severe incidents, including potential negative effects on product security.
Practical tips
- Identify which entity develops or commissions the product and which name or trademark is used to market it.
- Review private-label and white-label arrangements for branding or substantial modifications that could change the manufacturer role.
- Consider who within your business will assess which entity has the CRA manufacturer role; the CRA role depends on the facts of the arrangement.
Related Posts
19. November 2026
CRA Vulnerability Reporting: Who Else Gets the Details?
After a qualifying CRA report, who must hear about the vulnerability - and who…
18. November 2026
Open-Source AI Models: Choose One Workflow to Validate
Asia-Pacific adoption signals offer context, not a guarantee of fit. A focused…
15. November 2026
CRA Reporting Duties: Triage Legacy Product Lines
Products sold years ago may still warrant CRA review. Product scope, EU market…




