Skip to main content

Control

Programmable Logic Controller (PLC)

A ruggedised industrial computer that executes deterministic control logic against field I/O.

Critical criticalityLevel 1

What it does

Reads sensors, runs scan-cycle logic, drives outputs such as valves, motors and drives.

Typically locatedControl cabinets on the plant floor, substations, pump stations and skids.

At a glance

PurdueLevel 1
CategoryControl
Protocolsmodbus-tcp, ethernet-ip, profinet, profinet-dcp, s7comm, umas, pccc, pcom, fins, mc-protocol
Talks toHMI, SCADA server, Engineering workstation, Remote I/O, Drives, Other controllers
Common vendorsSiemens (SIMATIC S7-1200/1500, S7-300/400 legacy), Rockwell Automation (Logix, Micro800), Schneider Electric (Modicon M580/M340), ABB (AC 500), Mitsubishi Electric, Omron, Beckhoff, Unitronics

Why should I care?

Programmable Logic Controller sits at Level 1. Compromise here is not just a data problem — it changes what the physical process does or what operators can see and control.

Common security problems

  • Unauthenticated programming paths in older families
  • Run/Program keyswitch left in remote-programmable state
  • Firmware that is years behind vendor releases due to outage constraints
  • Flat networks that expose controllers well beyond their process peers

If it is compromised

  • Unauthorised logic change can alter physical process behaviour
  • Loss of control or loss of view for operators
  • Potential equipment damage or unsafe process state depending on the process

What to monitor

  • Program download / upload events
  • CPU mode changes (Run / Program / Stop)
  • New clients speaking controller protocols
  • Checksum or project comparison against a known-good baseline

How to defend it

  • Restrict controller protocols to named engineering hosts through conduit rules
  • Enable controller access protection features supported by the platform
  • Keep validated logic backups and compare periodically
  • Physically secure cabinets and keyswitches