Product security
Ship a digital product in the EU
Build an evidence file, decide how to handle vulnerabilities and check whether an outside assessment is part of the route.
The situation
Your company sells a connected router in several EU countries. A security researcher says one shipping version can be exploited. The same product team is preparing a new version and a large buyer wants product certification.
What to do first
Write down the installed versions, affected components and who can make a reporting decision. Gather this while engineering investigates the fix.
How to organize the work
- 1
Trace the reporting clock and preserve facts
Check whether the product and event meet the CRA reporting trigger. Record awareness, whether exploitation has been observed and the versions already shipped. Use the early and full reporting clocks from the official source.
- Who
- Product security + regulatory affairs
- Output
- Incident decision and reporting record
- 2
Build a release record tied to actual tests
Where the product includes a web application or API, tie its permissions and data protection requirements to reproducible tests. Bring that evidence into the product security risk and release file.
- Who
- Release engineering + application security
- Output
- Versioned tests and component inventory
- 3
Confirm whether certification is relevant
Ask the buyer which product configuration and security claims it needs. Check that those claims match the target of evaluation, edition, assurance level and any separate conformity requirement.
- Who
- Product assurance + customer owner
- Output
- Evaluation route and exact product scope