Refrigeration & Cold-Chain OT Attacks: How to Lock Down Exposed Controllers in 5 Steps

The refrigeration attacks across Europe have left supermarkets throwing away food after attackers changed equipment settings remotely. Hundreds of French stores were affected in October, followed by further suspected attacks across Europe on November 2.

For anyone responsible for buildings, industrial equipment or other connected operations, the problem may sound familiar. Someone needs remote access to monitor equipment or fix a fault. Over time, those connections can leave controls exposed or give suppliers more access than their work requires.

The broader issue is how to securely connect Internet of Things (IoT) devices and operational technology (OT) while minimizing their attack surface. How do you keep equipment available to the people who need it while keeping attackers out?

Why these systems need remote connectivity

A technician can investigate an overnight alarm without driving to the site. A facilities team can adjust building schedules across dozens of locations. Operators can spot equipment problems before they cause downtime.

The UK’s guidance on secure OT connectivity recognizes these benefits while warning about the risks introduced by third-party access and older equipment.

Refrigeration controllers, HVAC systems and pumps all have a place in this discussion. When someone changes their behavior without permission, the consequences can include spoiled inventory, wasted energy and interrupted operations.

Operators and integrators can address that risk in five practical steps.

1. Find every way into the equipment

Choose a site or equipment group and map how it can be reached. Include management interfaces, vendor connections and remote-access tools. Find out who uses each connection and why.

Network discovery can help verify what’s exposed. Tools such as Nmap show reachable services from the scan’s location, but active scanning needs care around sensitive OT equipment. Coordinate discovery with the operations team and equipment suppliers.

Combine those findings with vendor records and network configurations to build a fuller picture of access.

2. Remove public exposure while preserving remote access

Move required connections onto a protected access method, then remove exposed management interfaces, port-forwarding rules and alternative routes that bypass it.

France’s CERT-FR recommends removing refrigeration controllers’ internet exposure and restoring access through protected connections.

The goal is to keep protected services available to authorized participants while invisible to unauthenticated public port scans, without publicly exposed inbound endpoints.

Technicians retain the access they need. Attackers lose the exposed interface they could otherwise discover and probe.

3. Give each participant only the access its work requires

A refrigeration technician may need one controller’s maintenance interface. A monitoring application may only need temperature readings.

Give each participant access to the specific services its work requires, and nothing more. Keep permissions within the equipment’s software equally focused.

This is least privilege in practice. It limits what a compromised account or device can reach and helps contain the damage it could cause.

4. Extend protection inside the network

Removing public exposure closes a major route into your systems. An authorized account or device can still be compromised, though. An attacker who gains control of a technician’s laptop, for example, may inherit its access.

Without internal controls, that foothold could provide a path to other equipment. This is lateral movement: moving from one compromised system to others.

Extend protection between internal devices, applications and services. Each connection should require explicit permission, with routes that bypass those controls closed.

The same principle applies within a facility and across sites: access to one system should provide only the permissions needed for that system.

5. Use a Kill Switch to cut off compromised access

Once you know a participant has been compromised, cut off its access to protected systems.

A Kill Switch lets teams revoke that participant’s communication authority. This closes the connections it could use to reach other systems and helps stop the compromise from spreading.

Teams need a clear way to take that action from one place. Keep permissions current as employees, suppliers and equipment change, so access can be withdrawn when it’s no longer needed.

Where Atsign fits

Atsign EdgeAI helps operators and integrators reduce public exposure, limit lateral movement and manage access across distributed IoT and OT deployments.

Its integrated control center lets authorized teams see connected systems and manage which systems can communicate across sites. If a participant is compromised, teams can use the Kill Switch from that same control center to cut off its communication access.

Teams can start by protecting remote connectivity to existing systems, then extend protection between individual systems. Atsign also reduces the site-specific networking work that slows deployments and adds operating costs as installations grow.

This gives organizations a consistent way to connect and control operational environments while keeping protected services out of public reach.

Start with one important equipment group. Identify its access paths, decide which connections are necessary and remove the exposure around them.

Is your OT equipment exposed?

Don't wait for a compromised controller to breach your cold chain or facilities. Book a 10-Minute Atsign Lockout Demo.