# When Skynet Meets the Assembly Line CISA’s New Playbook - Link: https://www.agilicus.com/when-skynet-meets-the-assembly-line-cisas-new-playbook/ - Published: 2025-12-14T00:30:32+00:00 - Author: Don Bowman ## Navigating the new guidance on mixing artificial intelligence with industrial control systems without blowing anything up It feels like just yesterday we were worried about connecting a PLC to the internet, and now we are asking it to write poetry. CISA, along with their pals in Canada and Australia, just [dropped](https://www.cisa.gov/news-events/alerts/2025/12/03/cisa-australia-and-partners-author-joint-guidance-securely-integrating-artificial-intelligence) guidance on securely integrating artificial intelligence into operational technology environments. While the benefits of efficiency are dazzling, the risks are about as subtle as a brick through a window. This isn’t just about data leaks; it is about kinetic consequences. Let’s unwrap these four key principles and see if we can keep the factory lights on while teaching the machines to think, all while avoiding the typical pitfalls of merging silicon brains with heavy metal brawn. ### Teaching Old Dogs New Digital Tricks CISA’s first principle sounds deceptively simple: **understand the technology**. But in practice, asking a legacy mill operator to suddenly grasp the nuances of neural networks is like asking a fish to understand a bicycle — the context just isn’t there. We are already facing a demographic cliff where seasoned Industrial Control Systems experts are retiring, taking decades of tribal knowledge about obscure protocols and temperamental programmable logic controllers with them. Now, we are asking the skeleton crew left behind to also become experts in machine learning? It is a tall order. The intersection of professionals who can debug a 30-year-old turbine controller _and_ explain the intricacies of model weights and matrix math is practically non-existent. We are effectively hunting for unicorns in a haystack. This skills gap is terrifying because the culture of artificial intelligence development is fundamentally at odds with the plant floor. The “move fast and break things” ethos of Silicon Valley is a disaster waiting to happen in an environment where mistakes have kinetic consequences. If a chatbot hallucinates, you get a weird sentence; if a boiler control system hallucinates because the model misread a sensor, you get a crater. This is why CISA places such heavy emphasis on the secure development lifecycle. Organisations cannot treat these tools as black boxes. Before a single algorithm interacts with a sensor, the engineering teams need to understand how the sausage is made — and more importantly, how the sausage might be poisoned. Without a deep understanding of how these models are built, trained, and maintained, operators are essentially inviting a digital gremlin into the control room and hoping it behaves. It is a recipe for disaster that relies on hope rather than engineering, creating a vulnerability no firewall can block. ### The Myth of the Air Gap and the Prompt Injection Once your team has a grasp on the concepts, you run headfirst into an architectural nightmare. For decades, the operational technology world relied on the air gap — a physical disconnect from the internet — as its primary defence. It was simple, effective, and now, it is mostly a fairy tale. Integrating artificial intelligence, specifically cloud-based large language models, creates a perimeter that is incredibly difficult to police. You are essentially poking holes in the hull of a submarine to let some fresh air in. The real terror here lies in how these systems communicate. Take the Model Context Protocol (MCP), which standardises how artificial intelligence models interact with external data and tools. It is brilliant for functionality but terrifying for security. We are facing a resurgence of text-based vulnerabilities that feel eerily similar to SQL injection. In the early 2000s, a clever string of text could trick a database into deleting itself. Today, prompt injection allows a user — or a malicious email processed by an agent — to instruct the model to ignore previous safety guardrails and execute commands on the underlying control systems. Unlike a SQL query, however, natural language is fuzzy. You cannot just blacklist a few characters to stop it. This makes the perimeter porous. Therefore, CISA’s second principle insists on a ruthless assessment of the business case. You must weigh the shiny allure of predictive maintenance against the very real possibility of a chatbot being tricked into over-pressurising a boiler. If the business case cannot survive a threat model where the interface is a compulsive liar, it does not belong on the plant floor. ### Governance Is Not Just Red Tape It Is Survival If the previous section convinced you that your perimeter is looking a bit like Swiss cheese, then Principle 3 — Establishing artificial intelligence governance— is where we try to reinforce the structural integrity. I know the word _governance_ usually induces a coma faster than reading the terms of service on a new phone, but here, it is not just administrative red tape; it is survival. It is the backbone of defence in depth. When CISA talks about governance, they are really asking you to abandon the “set it and forget it” mentality that has plagued industrial control systems since the 1990s. This brings us to Zero Trust. We have to stop thinking of this merely as identity management for people. Sure, verifying user credentials is great, but in an operational technology environment, the real chatter is machine-to-machine. We need strict Zero Trust architecture for system-to-system interactions. Does the predictive maintenance algorithm actually _need_ write-access to the programmable logic controller? Probably not. If you treat every internal request with the same suspicion you would accord a stranger knocking on your door at 3 a.m., you are on the right track. This approach requires a radical rethink of traffic flow. Legacy environments focus on keeping bad things out. But with artificial intelligence models sitting inside your network, potentially compromised by those text-based injections, you need to police the exit as strictly as the entrance. A compromised model must be contained. If an AI agent tries to establish an outbound connection to an unknown server, your architecture must block it cold. Governance also mandates continuous testing. Unlike a physical pump, an AI model experiences drift; it rots. You need the regulatory framework to catch that decay before the digital decision-making starts impacting the physical world. ### Keeping the Cyber Physical Systems from Going Rogue While the previous chapter’s focus on governance and zero trust helps lock down the digital perimeter, Principle 4 forces us to confront the kinetic reality of the factory floor. We are moving from the theoretical to the tangible, or specifically,** embedding safety and security** into systems that have the power to crush, burn, or flood. In a standard IT environment, a hallucinating artificial intelligence model might write a bizarre email or botch a spreadsheet. In an Operational Technology environment, that same glitch could over-pressurise a pipeline or instruct a robotic arm to swing through a space occupied by a human operator. The introduction of these models into cyber-physical systems significantly magnifies the ramifications of a breach. We are no longer just worried about data exfiltration; we are worried about casualty counts. It brings to mind the ominous warnings of the _Terminator_ franchise — granting autonomy to a system without absolute certainty of its alignment is a recipe for disaster. We cannot afford a Skynet scenario where an algorithm decides that the most efficient way to cool a reactor is to vent radioactive steam without checking the wind direction first. This necessitates a move away from“ black box” deployments; if we cannot explain the transparency and logic behind an AI’s decision, it has no business controlling a programmable logic controller. Consequently, CISA argues that these systems must be deeply integrated into incident response plans. Operators need a manual override — a digital “kill switch” — that disconnects the artificial intelligence without crashing the critical process it monitors. If the model begins to drift or behaves maliciously, the defence team must be able to revert to deterministic, logic-based automation immediately. We must ensure we don’t accidentally automate a disaster simply because we trusted the math more than the mechanic. ## Conclusions Integrating artificial intelligence into operational technology is like trying to install a jet engine on a tractor; it might go faster, or it might just explode. The guidance from CISA and its international partners offers a solid roadmap, but the terrain is treacherous. From the erosion of the air gap to the very real threat of prompt injection in physical systems, the challenges are immense. We need to prioritize safety over efficiency and ensure that our defence in depth strategies are as robust as the steel in the machines we control. Proceed with caution, or the next ‘glitch’ might be a lot louder than an error message.