CRA Scope for Connected Devices and Their Cloud Backends
Apply the CRA remote data processing tests to connected device architectures and record external cloud dependencies separately.
By CenitiaUpdated
Fact-checked against the law as of Reviewed by Vladimír Vician on How we check
A connected device's backend can be part of the product under the Cyber Resilience Act (Regulation (EU) 2024/2847), but not every cloud service is automatically included. Two questions decide it for each service. Would its absence prevent the product from performing one of its functions? Was its software designed and developed by the manufacturer, or under the manufacturer's responsibility?
The cloud boundary worksheet records both the conclusion and the architecture evidence. This article focuses on remote data processing solutions connected to a product; it does not decide every SaaS, NIS 2 or data protection obligation.
Apply both tests
Article 3(2) of the Cyber Resilience Act defines remote data processing as data processing at a distance for which the software is designed and developed by the manufacturer, or under the responsibility of the manufacturer, and the absence of which would prevent the product from performing one of its functions. Article 3(1) makes a product's remote data processing solutions part of the product. Read Regulation (EU) 2024/2847 (Cyber Resilience Act) with section 8 of the Commission guidance on the application of the Cyber Resilience Act (C/2026/6013). Both conditions must be met (guidance paragraphs 188 and 202).
The function test. Ask which function stops working when the software is absent, and describe that function precisely. “One of its functions” is wider than the core function. The guidance says it is not limited to core functionality or intended purpose, and gives sending commands to a device, onboarding the user, configuration, automated distribution of updates and identity and access management as examples (paragraphs 189 and 190). A function that the user can also perform manually still counts (paragraph 191). Processing that supports no product function falls outside the definition, for example remote analysis of telemetry collected purely for statistics or for future product development (paragraph 192). Even then, check whether it introduces risks to the product (paragraph 193).
The responsibility test. Ask who designed and developed the software and under whose responsibility. “Under the responsibility of the manufacturer” covers software built by, or on behalf of, the manufacturer to its designs and specifications. It does not cover an existing service that the manufacturer merely licenses (paragraph 195). Who operates or hosts the service is not decisive (paragraph 196).
Four fictional architectures
| Architecture | Working assessment | Evidence needed |
|---|---|---|
| Manufacturer designed commissioning API on third party infrastructure | Candidate remote data processing: design responsibility and function dependency may both be met | Architecture, code ownership, design contract and commissioning flow |
| Outsourced bespoke device control application | Candidate remote data processing even though a contractor develops or runs it | Specifications, responsibilities and unavailable-service behaviour |
| Generic third party customer support chat | Not automatically part of the product boundary; check actual function and responsibility | Integration scope and whether a product function depends on it |
| Off-the-shelf identity SaaS used by a manufacturer application | Assess separately from the manufacturer's own application; the generic service is treated like a third party component | Service contract, design boundaries and authentication failure model |
These are conditional assessments using invented architectures. A product's marketing label, invoice wording or cloud provider's name cannot settle the boundary alone.
The guidance distinguishes three cloud service models. Software that the manufacturer deploys on third party infrastructure or platform services is designed and developed by the manufacturer, or under its responsibility, and may qualify as remote data processing. A fully developed third party SaaS application is not (paragraphs 198 to 200). Where a product function depends on such a third party solution, the manufacturer treats it like a component: it assesses the integration risks, mitigates them in the product and exercises due diligence (paragraphs 201 and 202). “Outside the remote data processing boundary” does not mean “irrelevant to product risk”.
Draw the software boundary rather than circling the whole cloud
Identify the device-facing application and directly interacting software. Record interfaces to databases, identity services, message brokers and operational tooling. Remote data processing means the software, not the hardware it runs on (paragraph 180). It is limited to the software modules responsible for the product's functionality and their interfaces to external services; back-end systems that the product does not interact with directly are not part of it (paragraph 205).
For each dependency, explain what data or commands cross the boundary, how failure is handled and what trust is granted. A broken dependency can still expose credentials or prevent updates even when it is not classified as your own remote data processing solution. The guidance keeps such systems in the risk assessment as external dependencies (paragraph 206).
Connect the boundary to evidence and support
Once the boundary is assessed, state in the technical documentation that the product has remote data processing solutions or relies on third party remote solutions, and describe them (paragraph 204). Include the relevant software and integration in the risk assessment and in vulnerability handling. Inventory server components separately where that improves traceability; do not pretend that an SBOM extracted from the device also describes the backend.
Identify who can patch the application, which releases are deployed and how compatibility with installed devices is maintained. A change to your own remote data processing software is a change to the product, and it can affect many devices without a new firmware image. Record the change and reassess the risks rather than assuming that no product change occurred. A major change in a third party service is not treated as a substantial modification of your product, but it can require you to revise the risk assessment (paragraph 208).
Handle uncertainty explicitly
If a contract does not clarify design responsibility, request the design specifications, development arrangement and release authority. If the unavailable-service effect is unclear, test or analyse the failure behaviour in a safe environment.
Keep an unresolved boundary question open until a competent reviewer addresses it. Do not choose the narrowest boundary simply because it makes the compliance register shorter.
Before using the conclusion
Check the scope exclusions in Article 2 of the Cyber Resilience Act and the applicable dates separately. The worksheet does not determine a cloud operator's duties under other legislation, such as the NIS 2 Directive (Directive (EU) 2022/2555). The four architectures above are invented; this article does not classify any real backend.
CRA applicability and timing
Most Cyber Resilience Act obligations apply to products placed on the market from 11 December 2027; a product placed on the market earlier becomes subject to them only if it is substantially modified from that date (Article 69(2)). Article 14 reporting is already a current duty: it has applied since 11 September 2026 to every in-scope product, including products placed on the market before 11 December 2027 (Article 69(3)), and it continues after the support period ends. Check the product’s scope, your role and the transitional provisions. See the Commission page for manufacturers, the Commission page on reporting and the Commission guidance on the application of the Cyber Resilience Act (C/2026/6013).
Continue reading
Related guides
tutorial
Secure OTA Firmware Updates and the Evidence to Keep
Plan secure OTA test evidence for signatures, interrupted updates, recovery and downgrade controls against the CRA update requirements, with a small host demo.
6 min read
guide
When a Firmware Update Needs New CE Evidence or Retesting
Assess firmware changes against existing CE evidence, notified body notification duties and the CRA substantial modification rules with a change impact record.
6 min read
tutorial
CycloneDX VEX for Embedded Firmware: a Worked Synthetic Example
Write a scoped CycloneDX VEX decision for embedded firmware: an unresolved in_triage record, a synthetic not_affected record with justification, and reassessment triggers.
5 min read
tutorial
CRA Cybersecurity Risk Assessment for an IoT Gateway
Create an IoT gateway risk register that connects product boundaries, abuse cases, security controls and verifiable release evidence.
4 min read
Put this into practice
Free tools & references
- CRA Readiness CheckerScore your product against the Cyber Resilience Act essential requirements.Open tool →
- EU Directive SelectorDescribe your product and find which EU directives and regulations apply.Open tool →
New to the terminology? Browse the compliance glossary — plain-English, citation-backed definitions of every term above.