[DEEP RESEARCH] Who Owns the Cold Chain When the Controller Goes Online?

French supermarkets reported refrigeration disruptions after attackers allegedly forced defrost cycles during the night of October 11–12. France’s national incident-response team, CERT-FR, subsequently confirmed numerous compromises across Danfoss AK-SM and AK-SC, Copeland XWEB and Dixell XWEB controller families. These are systems used to supervise refrigeration—not merely office computers near a cold room. [1][2]

The initial intrusion route, actor and motive remain unconfirmed. Published controller vulnerabilities are relevant background, not established explanations for these attacks. [3]

Remove dangerous public exposure now, with facilities coordinating alarm and cooling continuity. Use the next renewal to decide which controllers can remain supported behind protected access and which need a funded replacement. April 2027 is a proposed portfolio-review deadline, not a CERT requirement or permission to delay containment.

One useful check this week: ask the refrigeration contractor and network owner to identify the same site’s remote-access path. Compare their answers with router rules and an authorized external exposure check, including nonstandard ports. A disagreement is an ownership problem worth resolving before the next emergency callout.

Below the tear: how to distinguish a sustainable maintenance service from a temporary legacy exception—and what to test before signing either.

Close the exposed path without losing the service

The hard part is not deciding that a controller should be off the public Internet. It is preserving the cooling, monitoring and repair service that depended on that access.