Who does the Cyber Resilience Act apply to?
Direct answer
The Cyber Resilience Act applies to manufacturers, importers and distributors of products with digital elements that have a direct or indirect connection capability. Manufacturers carry the primary obligations. The regulation is extraterritorial: a company outside the EU that places products on the EU market is in scope. Products covered by sector-specific rules and non-commercial open source are largely excluded.
Key takeaways
- Two-question scope test: does the customer install and run their own copy, and does the product have a direct or indirect data connection? Two positives and you are a manufacturer.
- Manufacturers, importers and distributors of products with digital elements (Art. 2).
- Manufacturers carry the primary obligations: design, conformity, vulnerability handling, reporting.
- Extraterritorial: non-EU manufacturers selling into the EU are in scope.
- Non-EU manufacturers must appoint an authorised representative in the EU or ensure an EU-established economic operator performs the Article 4 tasks under Regulation (EU) 2019/1020 (CRA Art. 18).
- OEM liability follows the brand: the entity placing the product on the EU market under its own name is the "manufacturer" for CRA purposes. An upstream OEM developer is not the manufacturer unless it also markets the finished product directly.
- Exclusions: medical devices (MDR/IVDR), motor vehicles, civil aviation, and non-commercial open source (Art. 2).
- Remote data-processing solutions integral to the product are in scope even if hosted in the cloud (Art. 3(2)).
Who Does the Cyber Resilience Act Apply To?
Watch on YouTube ↗The full answer
The CRA applies to economic operators in the supply chain of products with digital elements that include a direct or indirect data connection (Art. 2, 3).
Two questions settle scope. Answer both before working out which operator you are -- if either comes back negative, the rest of the CRA does not reach you.
| Question | In scope | Out of scope |
|---|---|---|
| 1. Product or service? | The customer gets their own copy, installs it and runs it | They only log into an environment you host -- that is a service, and NIS2 is the relevant framework |
| 2. Connected? | A direct or indirect logical or physical data connection to a device or network | No data connection to any device or network |
Two positives and you are a manufacturer under the CRA, wherever your company is established.
Question two is the one most often answered wrongly, because indirect counts: a sensor that reaches the internet only through a gateway is in scope. Question one carries its own trap -- hosting is not a safe harbour when the product depends on it. Software a manufacturer builds to run at a distance, which the product needs to perform a core function, is treated as part of the product (Art. 3(2)).
Manufacturers carry the primary obligations: secure design, technical documentation, conformity assessment, vulnerability handling, SBOM and incident reporting. A manufacturer established outside the EU must appoint an authorised representative in the EU, or otherwise ensure an EU-established economic operator performs the relevant tasks under Article 4 of Regulation (EU) 2019/1020 (CRA Art. 18). This is commonly fulfilled through the importer, an appointed authorised representative, or a fulfilment service provider.
Importers may place only compliant products on the EU market and must verify that the manufacturer completed its obligations. If the importer has reason to believe the product does not conform, it may not place it on the market.
Distributors must act with due care and satisfy themselves that the CE marking and required documentation are in place before making a product available.
OEM supply chain. The CRA places obligations on the entity that places the product on the EU market under its own name or trademark. An upstream OEM developer that supplies components or white-label hardware to a third party is not the "manufacturer" for CRA compliance purposes unless it also markets the finished product directly. If a software house supplies a module that another company integrates and brands, the branding entity is the manufacturer and carries the CRA burden. Compliance follows the brand on the box, not the origin of the technology.
Extraterritorial reach. A company established in the United States, Canada, or anywhere outside the EU that sells products with digital elements into the Union is in scope.
Exclusions. Products already subject to sector-specific EU rules with equivalent requirements are excluded -- medical devices (MDR/IVDR), motor vehicles (type-approval) and civil aviation (EASA). Non-commercial open-source software developed outside a commercial activity is largely outside scope.
How Acuna GRC handles it
- Solution
CRA
Track every vulnerability to a verified fix, keep CRA technical documentation, record exploited vulnerabilities, check component suppliers and reuse NIS2.
- Module
Vulnerability management
Vulnerable items from your scanners rolled up into one issue per vulnerability, with an owner and a due date.
- Core workspace
Comply
The frameworks you select, the scopes and tags that segment your organization, the common measures library and the mapping of measures across frameworks.
Sources
This page explains the rules in general terms and is not legal advice.
See how Acuna GRC runs this.
Tell us your frameworks and your team. We show you how Acuna GRC runs the program.
Hosted in Switzerland, the EU or the US
.png&w=3840&q=75&dpl=dpl_4WWtFHEr9P8wkcdWCGky2WYKjEiM)

