Business guides – contracts, HR, AI & compliance

CRA cloud backend 2027 – when does remote processing count?

Does your connected product depend on a cloud backend? Learn when processing qualifies as an RDPS under the EU Cyber Resilience Act, what evidence to collect and why ordinary SaaS is different.

Published Mallbutiken.se
CRA cloud backend 2027 – when does remote processing count?

A cloud connection alone does not make every online service part of a product under the Cyber Resilience Act (CRA). Article 3(1)–(2) of Regulation (EU) 2024/2847 covers a product with digital elements and certain remote data processing solutions (RDPS). Classification must be made for a specific product, function and software service.

Short answer: check remote processing, whether losing it prevents one product function, and whether the software was developed by or under the manufacturer’s responsibility. The Commission’s July 2026 guidance explains that third-party SaaS and general cloud infrastructure are not automatically RDPS.

Three cumulative checks before calling a backend RDPS

  1. Is software processing data at a distance? Public cloud, private cloud and the manufacturer’s own servers may all qualify. Location or who operates the server is not decisive.
  2. Would losing the processing prevent the product from performing at least one function? Remote operation, user onboarding, identity, configuration and updating may qualify; the function need not be the product’s main function.
  3. Was the relevant software designed and developed by the manufacturer or specifically under its responsibility? Custom development for the manufacturer differs from purchasing a general, pre-existing SaaS offering.

Decision table: five common cloud arrangements

ArrangementInitial assessmentEvidence to check
Manufacturer-built remote control APIPotential RDPSFunction, architecture, ownership and loss-of-function test
Manufacturer's own application on a third-party PaaSApplication may be RDPSOwn code versus the provider's execution environment
Ready-made third-party SaaSNot automatically RDPSDevelopment responsibility; risks of integrated third-party components
Telemetry used only for future statisticsGenerally not RDPS for that functionCheck if losing telemetry actually removes a product function
Informational website with manualsNormally not RDPSCheck if it also issues essential credentials or controls a device

Examples: avoid classifying the whole cloud platform

Smart lock with remote unlocking

If the manufacturer’s backend is necessary to unlock remotely, that software may qualify even if the lock still opens with a physical key. An alternative local method does not remove the remote function.

Login portal for a connected device

A portal that issues credentials needed for a device function may be RDPS if the development-responsibility condition is also satisfied. A site displaying instructions alone normally is not.

External telemetry analytics

If data is used only for product improvement and no device function fails when analytics is absent, it is generally not RDPS. Its possible security impact still belongs in the product risk assessment.

Seven pieces of evidence worth documenting

  1. Identify the exact product, model, firmware version and marketed functions.
  2. Map interfaces, API calls, storage, remote modules and subcontractors.
  3. Explain and, where safe, test which functions fail when each remote service is unavailable.
  4. Keep contracts, specifications and evidence showing who designed and developed the software.
  5. Distinguish manufacturer-controlled software from third-party IaaS, PaaS and SaaS layers.
  6. Record security and supplier risks even for a component classified outside RDPS.
  7. Approve a reasoned decision, owner, evidence links and triggers for reassessment after changes.

RDPS is not the whole supplier stack

The Commission’s guidance distinguishes functional software modules and their interfaces from the manufacturer’s entire IT environment. General payroll, CRM, unrelated analytics and underlying cloud infrastructure do not become RDPS simply because the manufacturer uses them. Third-party services can still create product security risks requiring due diligence and mitigations. CRA classification does not replace GDPR, NIS2 or contractual controls.

Which CRA deadlines matter in November 2026?

Since 11 September 2026, Article 14 reporting duties already apply to manufacturers in scope for actively exploited vulnerabilities and severe incidents affecting product security. The principal product requirements apply from 11 December 2027. This article explains scope, not the separate incident-notification workflow or a CE certification.

Frequently asked questions

Does every SaaS system used by an IoT manufacturer fall under CRA?

No. Evaluate the actual product function, who designed the software and the security consequences of an external service.

If a device works manually, is its remote cloud function outside scope?

Not necessarily. If the manufacturer offers remote control as a product function, losing remote operation may meet the functional test.

Does outsourcing cloud operations transfer manufacturer responsibility?

No, not merely because a third party operates the infrastructure. The design and development responsibility is a key distinction.

Can an Excel register certify our RDPS classification?

No. Registers organise facts and decisions. A qualified person must assess the relevant law, evidence and product-specific security risks.

For the wider CRA duties and the technical risk evidence, continue with:

Source review: 18 November 2026. Editorial, AI-assisted information; not a legal opinion, CE approval, verified security test or approval by an external lawyer.

Explore the topic

Back to blog
Customers rate us 4.6/5 based on 10261 reviews.