1Assign services as assets to products
Cloud services are created as SaaS assets and assigned to the products whose functions they provide – the boundary becomes visible instead of debated.
Pure cloud services are mainly regulated by NIS2. But as soon as your service provides functions of a product with digital elements – such as device management, updates or analytics – it belongs to the product's CRA scope as 'remote data processing'.
A SaaS provider operates the platform through which customers manage their connected devices. The platform was conceived as a pure cloud service – but without it the device does not fully work. That makes it part of the product the device manufacturer places on the market.
The question 'Which part of this falls under the CRA?' can only be answered when it is clear which services provide which product functions, which components they contain and who is responsible for vulnerabilities – the platform provider, the device manufacturer or both.
Which cloud functions are part of the product and which are not – traceable and reasoned.
Backend services also consist of libraries and containers whose vulnerabilities must be assessed.
Who reports, who patches, who informs users – agreed between platform provider and device manufacturer.
Device manufacturers will demand SBOMs and security evidence from their SaaS partners.
Cloud services are created as SaaS assets and assigned to the products whose functions they provide – the boundary becomes visible instead of debated.
Components of backend services are recorded like any other software, checked for vulnerabilities and assessed.
For every device manufacturer you supply, you generate the matching evidence – without starting from scratch each time.
You can tell customers and partners clearly which services are part of which products, what is inside and how you handle vulnerabilities – an answer that is increasingly required in tenders.
ProductShield supports technical structuring, risk analysis and documentation. A final legal assessment is not performed automatically and should be supplemented by specialised advisors or notified bodies where required.
Machines with controllers, HMIs and remote maintenance are products with digital elements – the CRA and the Machinery Regulation require evidence for them.
View industry →Firmware, radio modules, cloud connectivity: connected devices are at the core of the CRA and the Radio Equipment Directive – with many variants and long lifecycles.
View industry →Standard software lives on third-party libraries. The CRA requires you to know these dependencies and keep them under control.
View industry →Assemblies with microcontrollers and firmware, components from suppliers, crypto in hardware: the CRA reaches down to the board.
View industry →Controllers, SCADA and industrial IoT run for decades in critical plants. The CRA classifies many of them as important products.
View industry →