00Services · Connected Products

Connected Products

Security evidence for devices that need to reach the market and stay there.

For Manufacturers of IoT and connected consumer, commercial, and automotive devices.

01Who it's for

Work for the teams that build and secure connected products.

You build or import a connected product and need to understand the security evidence it needs before sale.
Your product ships with firmware, mobile software, and a cloud service that different teams own.
A retailer, OEM, or customer has asked how you handle product vulnerabilities.
You need to connect engineering findings to the regulations and standards your markets apply.
Your product uses third-party software or components whose security status is unclear.

02Regulations & standards

EU CRA
Sets product cybersecurity and vulnerability-handling duties for products with digital elements.
EU CRA essentials Check product scope
RED / EN 18031
Applies cybersecurity requirements to relevant radio equipment placed on the EU market.
ETSI EN 303 645
Provides a consumer IoT security baseline for connected products.
UK PSTI
Sets security requirements for connectable consumer products sold in the UK.
UN R155/R156
Sets cybersecurity management and software-update requirements for in-scope vehicles.
ISO/SAE 21434
Defines a lifecycle cybersecurity engineering process for road vehicles.

03Services

IoT Firmware Assessment
Pilot · $3,500
Static firmware analysis, SBOM, triaged findings, and a CRA gap map.
View pilot
Connected Device Assessment
Scoped engagement
Assessment of device hardware interfaces, mobile app, and cloud API.
Discuss scope
CRA Vulnerability Handling Readiness
Scoped engagement
SBOM process, coordinated disclosure policy, PSIRT workflow, and Article 14 reporting.
Discuss scope
Architecture Review & Threat Modeling
Scoped engagement
Threat modeling and security review of product architecture.
Discuss scope

04How we work

The scope is shaped around your product, operating environment, and the decisions your team needs to make.

01
Confirm the scope.
Agree the product or operating environment, evidence, and decisions the work needs to support.
02
Review the evidence.
Work from the product details, documents, technical material, and people relevant to the agreed scope.
03
Assess the requirements.
Connect technical observations to the risks, regulations, and standards that apply to the work.
04
Set out practical next steps.
Discuss the findings and identify owners, priorities, and evidence for follow-up.

05Next step