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.
System safety · · 5 min read
Most programmes have traceability on paper. Fewer can follow a single hazard to the verification that closed it without a manual reconstruction.
Safety evidence rarely fails because a hazard was missed. It fails because the connection between a hazard, the requirement written to control it, the design decision that implements it and the verification that confirms it lives in four different tools and three different vocabularies.
The first is orphaned mitigation: a control appears in the design with no hazard reference, so nobody can say what happens if it is removed. The second is untestable requirements: a safety requirement phrased as an intention rather than a verifiable property, which turns verification into interpretation. The third is stale evidence: analyses that were accurate at a design freeze and were never revisited after the architecture changed.
The test of a traceable programme is simple: pick one hazard at random and follow it to accepted evidence in under ten minutes.
Keep one authoritative risk register with stable identifiers, and reference those identifiers everywhere else — requirements, design records, test cases, review minutes. Write each requirement so its verification method is obvious from the wording. Record rationale where the decision is made, not in a separate document written afterwards. Review the chain on a cadence tied to design change, not to milestones.
This is unglamorous work, and it is the difference between a safety argument that is explained and one that can simply be read.
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.
Engineering practice
When safety and product security work in separate structures, the contradictions surface late — usually in a customer review.
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.