Cyberattacks targeting supermarket refrigeration systems show how closely business continuity depends on the technologies that control physical equipment. Unauthorized access can alter operating settings and cause tangible damage, including spoiled goods, unavailable equipment and disrupted operations.
Incidents reported in recent weeks across several European countries, including Italy, have brought renewed attention to the protection of operational technology and the management of remote access. According to Tgcom24’s report of November 3, 2026, investigations are examining responsibility for the attacks and possible connections between the incidents.
For retailers and food supply chain operators, these events raise a practical question: do we know which digital systems keep our critical processes running, and what would happen if those systems were compromised?
How a Cyberattack Can Disrupt the Cold Chain
In the incidents described in the Italian National Cybersecurity Agency’s advisory, unauthorized access allowed attackers to remotely activate defrost cycles and change equipment operating settings. The advisory highlights weaknesses such as outdated installations, administration interfaces exposed directly to the internet and inadequate authentication controls.
Maintaining the cold chain therefore also depends on the devices and software that regulate refrigeration equipment. Remote management supports maintenance and supervision, but requires careful control over connections and permissions.
Organizations need to know who can access their equipment, which actions they can perform and how unauthorized changes will be detected.
What Are OT Systems, and How Do They Connect to IT?
Operational Technology, or OT, refers to hardware and software used to monitor or control physical processes. In refrigeration, this includes controllers, sensors and devices that regulate temperatures, compressors and defrost cycles.
Information Technology, or IT, supports the processing, storage and exchange of information through applications, servers, digital identities and business management systems.
These environments can communicate with one another. The ACN advisory explains that connections without adequate network segregation can allow a compromised IT system to become an entry point into equipment control environments.
Business continuity therefore requires an understanding of the dependencies between applications, networks, devices and maintenance services. That knowledge needs to be shared among IT teams, equipment managers and service providers.
Why IT Recovery Must Reflect Business Requirements
Planning an incident response starts with the affected business process and the consequences of its disruption.
For refrigeration systems, restoring the control software is one part of recovery. Resuming operations also requires checks on equipment performance and the condition of the goods.
Technical recovery time must therefore be assessed against the time within which the business process needs to resume and the damage that may accumulate during the interruption.
This connection between technology and business needs should guide recovery objectives. Our article on RPO and RTO explains why these objectives require management involvement and must reflect actual business requirements.
Business Continuity: Four Checks for Organizations
ACN’s recommendations cover system inventories, access protection, network segregation, and checks on configurations and devices. Changes must be coordinated with equipment managers and maintenance providers to avoid uncontrolled interruptions to refrigeration.
From a business management perspective, these recommendations translate into four practical checks.
1. Map Critical Process Dependencies
An inventory that supports business continuity should connect technology components to the activities they support. For each critical system, organizations should identify the business process involved, the person responsible and the consequences of an outage.
2. Manage Supplier Access
Remote support needs clearly defined responsibilities and permissions. Organizations should verify which resources maintenance providers can access, for how long and how their activities are recorded.
3. Connect Monitoring to an Operational Response
An alert is useful when it reaches someone who can assess it and initiate action. Every critical alert needs clear recipients, response times and escalation procedures.
4. Test Incident Coordination
An exercise helps establish whether contacts, responsibilities and procedures work together. It can reveal missing steps before they become obstacles during an emergency.
The Role of Incident Management in IT Resilience
When an incident affects both digital systems and physical equipment, several teams need to coordinate their response. Who receives the first alert? Who contacts the supplier? Who assesses the operational impact and authorizes a return to normal service?
Defining these responsibilities is part of building resilience. Our article on Incident Management: 3 Effective Business Continuity Practices explores how structured processes support incident handling and help reduce its impact.
At SORINT.lab, connecting infrastructure, service management and business objectives is central to building IT resilience. The attacks on refrigeration systems make that relationship particularly clear.
A practical starting point is to select a critical business process and map its dependencies with everyone involved: essential systems, suppliers, alerts, responsibilities and recovery times. This assessment provides a foundation for a business continuity plan that reflects how the organization actually operates.