Product security · CRA
When a freezer becomes a cyber incident
A remote connection keeps maintenance cheap. An ungoverned one can put the cold chain at risk. Europe’s refrigeration incidents show where product security becomes physical safety.
Engineering practice · · 5 min read
When safety and product security work in separate structures, the contradictions surface late — usually in a customer review.
A connected industrial product typically carries two analyses: a hazard analysis owned by system safety, and a threat model owned by product security. They describe the same architecture, the same interfaces and often the same failure consequences, in incompatible formats.
The practical fix is not to merge the disciplines or their methods. It is to give both a shared spine: one system model and interface definition, one severity scale for consequences, one architecture decision record set, and one verification plan that both analyses draw from. Hazard analysis and threat modelling keep their own techniques and their own reviewers, but they argue about the same picture.
Different methods, one system model, one severity scale, one verification plan.
Reviews get shorter because the two teams are not reconciling vocabulary. Mitigations get cheaper because conflicts appear at design time. Under CRA, the technical documentation improves noticeably, because the security argument can reference the same architecture rationale the safety argument already relies on. The evidence stops being two stacks that a reader has to reconcile.
CRA SCOPE CHECKER
Enter your website. We read what you make and sell, then ask only the few questions the regulation turns on.
About 60 seconds. No account. PDF report on request.
Product security · CRA
A remote connection keeps maintenance cheap. An ungoverned one can put the cold chain at risk. Europe’s refrigeration incidents show where product security becomes physical safety.
CRA readiness
The reporting duties arrive well before the main obligations. They are the first point where a product organisation is measured on process, not intention.
System safety
Most programmes have traceability on paper. Fewer can follow a single hazard to the verification that closed it without a manual reconstruction.
CRA readiness
The template for a technical documentation pack is public. What is not public is which sections a reviewer actually reads twice.
CRA readiness
The first SBOM run is usually a success. The second one, three months later, is where the gap between having a tool and having a process becomes visible.
System safety
Run separately, the two standards produce two item definitions, two review cadences and two sets of evidence that quietly contradict each other.
System safety
A hazard analysis that stops at a mitigation statement has done half the job. The other half is writing something a test engineer can act on.
CRA readiness
Most organisations can produce a vulnerability handling policy on request. Fewer can produce evidence that it was followed on the last three findings.
System safety
A safety case is usually written as an argument about a specific, frozen configuration. Continuous updates make that assumption false on day one.