When Cyberattacks Reach the Physical World: Protecting Legacy Infrastructure Without Replacing It

The cyberattack against French supermarkets is a warning that cybersecurity is no longer only about stolen information or unavailable websites. As Reuters reported on October 12, attackers manipulated connected refrigeration systems, raising temperatures to 122°F (50°C), spoiling food and reportedly causing fires. Robert McGreevy’s Fox News reporting brought the consequences into focus: disruption to an essential part of the food supply chain. 

In my discussion with Robert McGreevy at Fox News, the most important question was not simply how refrigerators were compromised. It was what the incident tells us about the industrial systems that keep modern society functioning and what operators can do now without replacing equipment that may still have years of useful life. 

The structural issue is bigger than outdated firmware 

Refrigeration controls, water-treatment systems, electrical infrastructure, production lines, and pharmaceutical manufacturing equipment belong to operational technology (OT). Unlike typical enterprise laptops, these systems are engineered for availability, reliability, and safety, with capital lifecycles commonly reaching 15–25 years or more. They may depend on older operating systems, proprietary protocols, specialist engineering applications, and controllers that cannot be interrupted for routine upgrades. 

Some equipment affected in France reportedly involved older or unpatched refrigeration-management technology. But age alone is not the vulnerability: internet exposure, weak credentials, unrestricted remote maintenance, fragmented asset visibility, and inadequate segmentation turn a weakness in one device into an opportunity for wider disruption. Updating supported firmware is important, but it is not a complete security architecture solution. 

The risk extends across critical infrastructure 

The risk is not confined to grocery stores. In the United States, federal cybersecurity agencies have documented compromises of internet-exposed programmable logic controllers, including devices used by water and wastewater utilities. 

A further warning emerged in UK reporting in August 2026: an incident in July reportedly disrupted a small electricity-generation facility for four days. Reports raised concerns about a possible cyber intrusion involving industrial control systems, although attribution was not conclusively established. The UK government subsequently confirmed that the incident involved micro-scale generation and did not threaten the wider energy system. 

Taken alongside the French refrigeration incident and documented intrusions into U.S. water-sector controllers, the UK case illustrates why operators should assess shared weaknesses in remote access, exposed controllers, legacy software, and segmentation. These are separate incidents and do not establish a coordinated campaign across food, water and electricity. However, they do show why the possibility of cross-sector disruption warrants serious resilience planning. 

Consider the potential consequences if a capable adversary coordinated disruptions across food refrigeration and distribution, drinking water or wastewater operations, and electricity supply. The combined effects could extend from spoiled inventory and business interruption to public-health, economic, and social consequences. This is a scenario for resilience planning, not a claim that these separate incidents form one coordinated campaign. 

What about the connected devices in our homes? 

During my Fox News interview, we also discussed whether attackers could take control of connected refrigerators, ovens, thermostats, and other devices in our homes. These devices can have vulnerabilities, but a mass campaign to disable household appliances is not, in my view, the predominant near-term threat to families. More common concerns include stolen credentials, financial fraud, personal-data theft, and unauthorized access. 

Households should still take sensible precautions: use unique passwords and a password manager, enable multifactor authentication, keep device and router firmware current, disable unnecessary remote access, and separate smart-home devices from computers holding sensitive information. Single sign-on can simplify access where available; a well-configured home router or firewall is useful. A VPN can protect certain connections, but it does not itself secure a vulnerable appliance. 

The more consequential large-scale scenario is an attack on the shared infrastructure that keeps homes functioning. An adversary does not need to compromise millions of individual refrigerators to spoil food across a region if it can disrupt electricity or refrigeration supply chains. A disruption to water treatment or distribution can affect entire communities; outages in electricity, telecommunications, or internet infrastructure can cascade into daily life and economic activity. 

This is the distinction between individual consumer cybercrime and systemic infrastructure risk. It does not mean that a coordinated attack is established in the French incident, nor that every legacy system is inherently compromised. It means that the same long-lived OT architectures supporting water, power, and food distribution deserve preventative security and resilience planning now. 

Zero Trust for OT: Protect the investment, change the trust model 

The answer cannot simply be to rip out and replace every older controller, workstation, or industrial application. Nor is air-gapping a realistic general strategy for environments that depend on remote diagnostics, suppliers, logistics, and enterprise integration. The practical path is to place legacy operations within a governed architecture that treats every connection as a decision: who is connecting, from which device, in what security state, to which asset, for what purpose? 

That scrutiny is especially important for vendor and technician access across multiple sites. A shared management portal or remote-access path can extend the reach of a compromise, making the identity, endpoint, and session used for operational access a business-continuity concern. 

Zero Trust means no user, endpoint, or network location receives implicit trust. Identity and device posture must be verified; access must be limited to the necessary functions; and critical systems must be segmented so that a compromised endpoint or store cannot become a pathway into an entire enterprise. OT safety interlocks and independent process protections must remain in place, even when cyber controls fail. 

How IGEL fits into a layered OT security architecture 

The IGEL Adaptive Secure Endpoint Platform™ provides an immutable, centrally managed foundation for supported access endpoints. In industrial environments, its role is to strengthen the endpoint and access layer around operational equipment, rather than directly securing programmable logic controllers (PLCs), refrigeration controllers, or specialized machinery. 

Where compatibility and operational requirements have been validated, this approach can help organizations modernize supported workstations and access endpoints while retaining existing industrial equipment. IGEL is part of a layered OT security architecture, not a substitute for controller patching, dedicated OT secure remote access, network segmentation, independent safety protections, or recovery procedures 

Five actions operators should take now 

1. Identify exposure. Inventory refrigeration, water, power and other OT assets; find internet-reachable controllers, remote-access paths, unsupported software and high-consequence dependencies.
2. Secure every remote connection. Remove unnecessary direct exposure, replace default credentials, require strong authentication, and control vendor and technician access through approved gateways.
3. Establish Zero Trust access. Verify user identity, endpoint identity, and posture before access; apply least privilege and continuously reassess access when context changes.
4. Segment to contain disruption. Separate operational zones, sites, and high-consequence assets with enforceable policies, and test whether a compromise can move laterally across facilities.
5. Recover safely and strengthen prevention. Validate backups of controller logic and configurations, manual operating procedures, independent safety protections, and restoration priorities. Harden supported access endpoints with immutable operating environments and centralized management, then phase upgrades according to operational risk.

From reactive cybersecurity to operational resilience 

The measure of success is not merely whether an intrusion is detected. It is whether an adversary can turn a compromised connection into unsafe physical commands, disrupted essential services or cascading failure. Security architecture must prevent where possible, contain what gets through, and preserve safe operations and recovery. 

The lesson from France is simple: the industrial equipment society relies upon cannot all be replaced on an IT refresh cycle. But the trust architecture around it can and must change. Protect the endpoint. Verify every connection. Limit the blast radius. Keep essential services operating. 

Sources and reporting context 

• Reuters, “Hackers heat French supermarket fridges, sparking fires and food losses,” October 12, 2026. 
• Robert McGreevy, Fox News, “French supermarkets face millions in losses after cyberattack hits refrigerators nationwide,” October 13, 2026. 
• Robert McGreevy, Fox News, “Hackers could already be inside American utilities, cyber experts warn of ‘Trojan Horse’ threat,” October 18, 2026. 
• CISA et al., AA23-335A, “IRGC-Affiliated Cyber Actors Exploit PLCs in Multiple Sectors, Including U.S. Water and Wastewater Systems Facilities”. 
• UK Parliament, written response to Question 25232, September 7, 2026. 
• CBS News, “Iran-linked hackers blamed for taking down U.K. power plant for first time, reports say,” August 2026.