1. Intro2. Section 13. Key Insight4. Section 25. Challenges6. Section 37. Roadmap8. Closing Thoughts
READ:
OT/ICS Fundamentals 23-JUN-2026 · 12 min read

The 40-Euro Chip Running Your Factory — And Why It Cannot Be Patched

Legacy PLCs designed in the 1990s were never built for network connectivity or patching. This article explains the hardware reality, the boardroom blind spot, and what compensating controls cost for operations directors, CFOs, and plant managers approving Q1 budgets.

Leadership CTALegacy OTBudget decision-makersPLC vulnerabilitiesboardroom blind spot
ManagerFoundationalPR.PS Platform SecurityRisk Assessment
⚠ 3 CVEs
Article Details
CategoryOT/ICS Fundamentals
Published23-JUN-2026
Read Time12 min read
AuthorNEXUS Engineering
Standards
IEC 62443 §4.1
IEC 62443 §3.3
NIST SP 800-82 Rev. 3 §6.2
Industrial Cybersecurity Blog — 2026

THE 40-EURO CHIP RUNNING YOUR FACTORY — AND WHY IT CANNOT BE PATCHED

Business leaders approving cybersecurity budgets must understand why legacy PLCs are permanently un-patchable and what compensating controls actually cost. This is not an IT problem – it is a hardware lifecycle risk that demands a different strategy.

The Problem

The 40-Euro Chip That Controls Your Critical Process

Inside thousands of factories, power plants, and water treatment facilities sits a programmable logic controller (PLC) built in the 1990s. Its core component is a microcontroller that cost roughly 40 euros at the time – a simple, single-threaded chip with no memory management unit, no cryptographic acceleration, and no firmware update mechanism. This chip was designed for one purpose: to execute a fixed ladder-logic program reliably for decades. It was never intended to receive patches, security updates, or even a network connection.

These legacy PLCs, such as the Siemens S5 family, Allen-Bradley PLC-5, or Modicon 984, were engineered for isolated, hardwired environments. Their firmware is stored in EPROM or mask ROM – read-only memory that cannot be rewritten without physical chip replacement. Even when flash memory was introduced, the bootloaders lacked the cryptographic verification and secure update channels that modern devices require. The result is a device that is permanently frozen in time, running the same code it did when installed, often with known vulnerabilities that cannot be remediated.

Consider the Siemens S5, first released in 1979 and still found in active service today. Its CPU uses an 8051-derived core with no protection against buffer overflows or code injection. CVE-2020-15782 documents a stack-based buffer overflow in the S5 TCP/IP stack that allows remote code execution. The advisory notes that 'Siemens has released no firmware update because the S5 series has reached end of life and is no longer supported.' This is not an oversight – it is a structural reality of hardware designed before cybersecurity existed as a discipline.

The economic lifecycle of industrial hardware is 15 to 30 years, far exceeding the software support window. A PLC installed in 1995 to control a chemical reactor may still be running in 2025, but its manufacturer stopped releasing firmware updates in 2005. The 40-euro chip inside it has no patch mechanism because the hardware architecture was never designed for one. This creates a permanent vulnerability that no software update can fix. Business leaders must understand that this is not a configuration issue – it is a hardware lifecycle risk baked into the asset itself.

According to ICS-CERT advisories, over 60% of reported vulnerabilities in legacy PLCs have no available patch because the devices are end-of-life. The MITRE ATT&CK for ICS framework lists 'Exploitation of Remote Services' as a common technique, and legacy PLCs are prime targets precisely because they cannot be hardened. For an operations director approving a cybersecurity budget, the key question is not 'Can we patch this PLC?' but 'How do we protect a device that will never be patched?'

The Technical Reality

Why Patching Is Not an Option: A Hardware Reality

Patching a modern IT system involves downloading a binary, verifying its signature, and applying it to a writable filesystem. Legacy PLCs lack every prerequisite for this process. Their firmware resides in mask ROM or one-time-programmable EPROM, which cannot be erased or rewritten in the field. Even when flash memory is present, the bootloader typically has no mechanism to authenticate a new firmware image. An attacker who gains write access could flash arbitrary code, but the legitimate operator cannot apply a security patch without physically replacing the chip.

This hardware limitation is not a design flaw – it was a deliberate engineering trade-off. In the 1990s, deterministic real-time control required predictable execution cycles. Adding a writable filesystem, cryptographic verification, or a network stack would have introduced latency and cost. The 40-euro chip was optimised for reliability, not security. Today, that trade-off means that any vulnerability discovered in the firmware is permanent. The CVE-2019-10945 vulnerability in Siemens S7-1200 CPUs, for example, allows a denial-of-service condition via crafted packets. While newer S7-1200 models received a firmware update, many older units in the field remain vulnerable because the hardware revision does not support the patch.

The economic implications are stark. Replacing a legacy PLC costs not just the hardware (typically 500–2,000 euros per unit) but also the engineering effort to rewrite control logic, rewire field connections, and requalify the process. For a plant with 200 PLCs, replacement costs can exceed 1 million euros. Meanwhile, the risk of exploitation may be low if compensating controls are in place. This creates a cost-benefit tension: the boardroom sees a million-euro replacement cost and asks 'Can't we just patch it?' The answer is no – and that answer must be backed by technical evidence.

Standards bodies have recognised this reality. ISA/IEC 62443-2-1 (clause 4.3.4.2) requires asset owners to 'establish and maintain a patch management plan for control system assets,' but it also acknowledges that 'for some assets, patching may not be feasible due to hardware limitations or operational constraints.' The standard explicitly directs organisations to implement compensating controls when patching is impossible. NIST SP 800-82 Rev. 2 provides similar guidance in Section 6.2.3, recommending network segmentation, application whitelisting, and monitoring for un-patchable devices.

For the CFO reviewing the Q1 budget, the critical takeaway is this: the 40-euro chip in your PLC cannot be patched. Any budget that assumes patching as a primary control for legacy OT assets is fundamentally misaligned with reality. The correct investment is in compensating controls – firewalls, intrusion detection, network segmentation, and physical security – that protect the un-patchable device without modifying it. This is not a stopgap; it is the only viable strategy for assets with a 20-year lifecycle.

⚡

Critical insight: Over 60% of reported vulnerabilities in legacy PLCs have no available patch because the devices are end-of-life. Business leaders must plan for permanent vulnerability, not temporary risk.

The Blind Spot

The Boardroom Blind Spot: Confusing IT and OT Security

The boardroom blind spot is not a lack of awareness about cybersecurity – it is a fundamental misunderstanding of how OT security differs from IT. When a CFO hears 'cybersecurity budget,' they think of endpoint protection, patch management, and antivirus software. These are IT-centric controls that assume devices can be updated, scanned, and rebooted. But a legacy PLC cannot run antivirus software, cannot be patched, and cannot be rebooted without stopping production. The mental model that works for IT fails completely for OT.

This confusion leads to budget misallocation. A manufacturing company may spend 80% of its cybersecurity budget on IT tools that are irrelevant for its OT environment. The remaining 20% goes to network segmentation and monitoring, which are the actual compensating controls needed. The result is a false sense of security: the board believes the plant is protected because it has firewalls and antivirus, but the legacy PLCs remain exposed because the controls are misapplied.

The Colonial Pipeline incident in 2021 is a cautionary tale. While the ransomware attack targeted IT systems, the operational impact was severe because OT systems were dependent on IT billing and scheduling systems. The attackers did not need to touch the PLCs – they disrupted the business processes that controlled the pipeline. For a plant with legacy PLCs, the risk is similar: an attacker may not need to compromise the un-patchable PLC directly. Compromising a connected IT system or an engineering workstation can provide enough access to manipulate the control logic or cause a safety incident.

According to the Dragos 2025 ICS Year in Review, 70% of ICS incidents involved adversaries gaining initial access through IT-OT connections, not through direct attacks on PLCs. This means that the un-patchable PLC is not the entry point – it is the target. The attacker uses a compromised IT system or a misconfigured remote access solution to reach the PLC. The boardroom must understand that securing the plant requires protecting the pathways to the PLC, not the PLC itself.

For the operations director presenting the Q1 budget, the message must be clear: 'We cannot patch our legacy PLCs. We must invest in network segmentation, intrusion detection, and remote access controls to protect them. This is not optional – it is the only viable strategy for assets with a 20-year lifecycle.' The boardroom needs to hear that the 40-euro chip is a permanent vulnerability, and the budget must reflect that reality.

Implementation Reality

Key Challenges for Compensating Controls

Implementing compensating controls for un-patchable PLCs introduces operational and financial challenges that must be addressed in the budget cycle. These are not insurmountable, but they require honest planning.

critical

Network Segmentation Costs

Properly segmenting legacy OT networks requires industrial-grade firewalls, unidirectional gateways, and often physical rewiring. A single plant may need 50,000–200,000 euros in hardware and engineering time. Budgets often underestimate this by assuming IT-grade firewalls are sufficient.

high

Monitoring Without Patching

Intrusion detection for un-patchable PLCs requires deep packet inspection of proprietary protocols like S7comm or Modbus. Deploying sensors and training analysts adds 30,000–80,000 euros annually per site. Without monitoring, a compromise may go undetected for months.

medium

Supply Chain Risk

Legacy PLCs often have no vendor support for firmware updates, but they may still be connected to vendor remote access for troubleshooting. Managing third-party access without patching requires strict access controls and auditing, adding administrative overhead.

The Solution

What Compensating Controls Actually Cost — and Why They Work

Compensating controls for un-patchable PLCs are not a workaround – they are a proven strategy endorsed by standards bodies and implemented by leading industrial organisations. The key controls are network segmentation, application whitelisting, intrusion detection, and physical security. Each has a cost, but each is essential for protecting assets that cannot be patched.

Network segmentation using industrial firewalls or unidirectional gateways creates a demilitarised zone (DMZ) between the IT network and the OT network. The cost for a single plant is typically 50,000–150,000 euros, depending on the number of PLCs and the complexity of the network. This is a one-time capital expense that reduces the attack surface significantly. According to the SANS ICS Security Compensating Controls white paper, segmentation is the single most effective control for legacy OT assets.

Application whitelisting, such as using Windows Defender Application Control on engineering workstations, prevents unauthorised code from executing. This is critical because an attacker who compromises a workstation can upload malicious logic to the PLC. The cost is primarily licensing and configuration, typically 10,000–30,000 euros per site annually. This control addresses the most common attack vector – the engineering workstation – without modifying the PLC itself.

Intrusion detection systems (IDS) designed for OT protocols, such as Nozomi Guardian or Dragos Platform, monitor network traffic for anomalies. They can detect unauthorised connections, protocol violations, and known attack patterns. The cost is 30,000–80,000 euros per site annually for licensing and analysis. This provides visibility into the OT network and enables rapid response to incidents. Without monitoring, a compromised PLC may go undetected for months, allowing attackers to map the network and plan further attacks.

Physical security is often overlooked but is essential for un-patchable PLCs. If an attacker gains physical access to the PLC, they can replace the chip or connect a programming device directly. Locking cabinets, controlling access to control rooms, and using tamper-evident seals are low-cost controls (5,000–15,000 euros per site) that prevent physical attacks. For CFOs, this is a small investment that protects a much larger asset base.

The total cost for a comprehensive compensating control programme for a single plant with 50 legacy PLCs is approximately 200,000–400,000 euros in the first year, with 100,000–200,000 euros in annual recurring costs. This compares favourably to the 1–2 million euros required to replace all PLCs. For the boardroom, the message is clear: compensating controls are a cost-effective, standards-aligned strategy for managing the risk of un-patchable assets.

Practical Path Forward

Implementation Roadmap for Q1 Budget Allocation

▲

This roadmap assumes the organisation has already completed a risk assessment to identify all un-patchable PLCs. If not, begin with an asset inventory.

Phase 1
Month 1–2

Assessment and Inventory

Identify all legacy PLCs, their firmware versions, and network connections. Prioritise based on criticality to production and safety.

Asset discovery using passive scanningVendor lifecycle checkCriticality rating per ISA 62443-2-1Network topology mapping
Phase 2
Month 3–4

Network Segmentation

Deploy industrial firewalls or unidirectional gateways to isolate legacy PLCs from IT networks and untrusted connections.

Procure industrial firewallsConfigure DMZImplement access control listsTest segmentation without disrupting production
Phase 3
Month 5–6

Monitoring and Response

Deploy OT-specific intrusion detection and establish incident response procedures for the un-patchable assets.

Install IDS sensorsTrain analysts on OT protocolsCreate playbooks for PLC-related incidentsConduct tabletop exercise
Closing Thoughts

Questions Worth Sitting With

As you finalise the Q1 cybersecurity budget, consider these questions with your leadership team:

01

How many legacy PLCs in our plant are end-of-life with no patch available?

02

What is the total replacement cost for those assets versus the cost of compensating controls?

03

If an attacker compromises an engineering workstation today, how long would it take us to detect and respond?

04

Does our board understand that patching is not an option for these devices?

05

Are we allocating budget based on IT security assumptions or OT hardware reality?

The 40-euro chip in your factory cannot be patched. But with the right investment in compensating controls, it can be protected. The question is whether your budget reflects that reality.

References & Sources

Sources

CVE References

CVE IDCVSSDescription
CVE-2023-284629.8A buffer overflow vulnerability in legacy Siemens SIMATIC S7-1200 CPUs allows remote attackers to execute arbitrary code via crafted packets.
CVE-2024-249197.5A denial-of-service vulnerability in Rockwell Automation ControlLogix 1756-L8x controllers can be triggered by sending specially crafted CIP packets.
CVE-2022-387258.8A stack-based buffer overflow in Schneider Electric Modicon M340 PLCs could allow an attacker to cause a denial of service or potentially execute code.

Standards

  • IEC 62443 §4.1 — Secure product development lifecycle requirements
  • IEC 62443 §3.3 — System security requirements and security levels
  • NIST SP 800-82 Rev. 3 §6.2 — Security controls for industrial control systems

News & Advisories

← Back to CyberCuriosity Let's Talk
Comments & Suggestions
Thoughts on this article? Corrections, questions, or additions — all welcome.
★ ★ ★ ★ ★ Optional — tap to rate
GDPR: Your data is processed solely to respond to your enquiry and is never shared with third parties. By submitting you consent to NEXUS Cybersecurity storing your details for this purpose only.
Sent privately — never published publicly