Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A programmable logic controller is a ruggedised industrial computer that reads sensors and drives equipment on a repeating scan cycle, and its programming interface is usually unauthenticated.

What Is a PLC?
A programmable logic controller is the small, hardened computer that makes industrial equipment do what it does. It reads inputs from sensors and switches, executes a program written by a control engineer, and writes outputs to motors, valves, heaters, and relays. A bottling line, a lift, a water treatment dosing skid, and a wind turbine pitch system are all, at the bottom, a PLC running the same loop a few hundred times a second.
The first ones appeared in 1969 at General Motors, designed by Modicon to replace walls of relay panels that had to be rewired whenever a car model changed. Half a century later the architecture is recognisably the same, which is both why PLCs are so reliable and why their security assumptions are so dated.
A PLC does not run an event loop in the way a server does. It repeats a fixed cycle:
A typical cycle takes between one and fifty milliseconds and must be deterministic, because the control strategy assumes it. That requirement explains a great deal about industrial security: anything that adds unpredictable delay — an agent, an inline inspection device, a burst of scanning traffic — can push a controller past its watchdog and fault it.
IEC 61131-3 defines five languages. Ladder diagram still dominates because it reads like the relay logic it replaced; function block diagram suits process control; structured text is used where algorithms get complex; instruction list and sequential function chart complete the set. Programs are written on an engineering workstation using vendor software — Siemens TIA Portal, Rockwell Studio 5000, Schneider EcoStruxure Control Expert, Mitsubishi GX Works — and then downloaded to the controller over the network. Common families in the field include the Siemens SIMATIC S7-1200 and S7-1500, the Rockwell ControlLogix and CompactLogix ranges, the Schneider Modicon M340 and M580, and the compact Unitronics Vision units widely used in water and building services.
There is no endpoint agent for a PLC, so protection is architectural. Put controllers in their own zone with an explicit conduit to the supervisory layer and nothing else. Keep the key switch in RUN during production and make moving it a controlled activity. Enable whatever the platform offers — program source protection, download passwords, signed firmware on newer families such as the S7-1500 — and accept that these are deterrents rather than barriers. Archive the controller application and compare the running program against the approved version regularly, which is also what makes restoration possible. Finally, watch the wire: passive monitoring that decodes S7comm or CIP will see a program download that no other control would catch.
Never scan a live controller to find out what it will tolerate. Our OT-SCADA Penetration Test assesses controller exposure using passive analysis, configuration review, and bench testing on identical spares.
A PLC controls discrete machinery and fast sequences, typically one machine or skid at a time. A distributed control system is an integrated platform for continuous processes across a whole plant, with its own engineering, operator, and historian layers supplied together. The boundary has blurred, and large PLC-based systems now do work that once required a DCS.
Yes, although it looks different from a Windows infection. An attacker who can reach the programming interface can change the running logic, which is what Stuxnet did. Researchers have also demonstrated persistent code hidden in controller firmware and web servers. The realistic defence is preventing network reachability and detecting program changes rather than scanning the device.
It does, when it is used. With the selector in RUN rather than REMOTE, many controllers refuse network program downloads outright, so an attacker with full network access still cannot alter the logic. The cost is that legitimate changes require someone to walk to the panel, which is exactly why the control is so often bypassed.
Compare the running application against an approved archived copy on a schedule, using vendor tooling or a change-detection product. Supplement that with passive network monitoring that alerts on program download and mode change commands. Relying on the controller to tell you is unwise: most keep little more than a change counter and no record of who made the change.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.