Designing a Cold-Chain Exposure Metric That Survives Budget Review
A single count of exposed controllers rarely changes a budget. A metric that moves in a direction, with a defined owner, does. The French incident produced enough public measurements to show what such a metric looks like when it is built correctly.
Three components
The metric needs a definition, a cadence and a decision rule.
The definition is the exact query. For example, title="StoreView Web" combined with a country filter, measured by one named tool. On 21 October 2026 this returned 271 globally, 55 in France, 7 in the Netherlands, 5 in Germany, 5 in Belgium.
The cadence is monthly or quarterly, fixed, not triggered by incidents.
The decision rule is agreed in advance: if the count does not fall after a containment campaign, escalation.
Why country splits earn their place
A global figure hides national campaigns. Censys recorded nearly 3,000 exposed Danfoss StoreView panels on 11 October, with more than 1,800 in France, then 537 in France on 14 October while counts elsewhere barely moved. A global number would have shown a moderate decline. The French figure showed a containment operation.
What to pair with the count
Counts describe interfaces. Pair them with two internal measures: percentage of controllers behind a broker, and percentage of controllers past vendor end-of-support. The public count can improve while the internal ones stagnate, which would indicate that operators are hiding devices rather than fixing them.
Reporting format that gets read
One line per month: query, count, delta, and the one action taken. No dashboard that requires interpretation during a budget meeting.
References
- Censys, Danfoss StoreView exposure report: https://censys.com/blog/frostbitten-in-france-a-danfoss-storeview-internet-exposure-report/
- CERT-FR alert CERTFR-2026-ALE-012: https://cert.cyber.gouv.fr/alerte/CERTFR-2026-ALE-012/
- ZoomEye queries executed 21 October 2026.













