SOC 2 Readiness
24/7 Security Monitoring
Canadian-Based SOC
Back to Glossary
Emerging Technology

What Is ICS Security?

Definition

Industrial Control System (ICS) Security focuses on protecting the computers, networks, and control systems that manage industrial processes in sectors such as energy, water, manufacturing, and transportation.

People Also Ask

Common questions about ICS Security answered by our security experts.

ICS Security in Practice

Industrial control systems are the equipment itself — the programmable logic controllers, distributed control systems, human machine interfaces and safety instrumented systems that hold a physical process in a defined state. Where OT security is the discipline, ICS is the specific class of equipment it is practised on, and the equipment's design explains most of the difficulty.

These devices were engineered for determinism and reliability over decades, in an era when the network was assumed to be trusted. Authentication was frequently optional. Many still answer commands from anything that can reach them.


What you are actually protecting

ComponentFunctionWhy it is sensitive
PLCExecutes control logicLogic changes alter physical behaviour
DCSCoordinates a plant-wide processBroad authority over many loops
HMIOperator's view and controlFalsified display misleads the operator
Engineering workstationPrograms the controllersHolds the tooling to rewrite logic
HistorianRecords process dataCommon bridge between OT and IT
SISBrings the process to a safe stateLast line before physical harm

The engineering workstation is the highest-value target in most plants and is routinely the least protected: a general-purpose computer, often on an old operating system, holding the software that can reprogram everything else.


The safety system deserves its own boundary

A safety instrumented system exists to act independently of the control system when something goes wrong. That independence has to hold in security terms as well: separate segmentation, separate credentials, a separate engineering workstation, and change control that reflects what the system is for.

Where an assessment finds the SIS and the basic process control system sharing a network, an account or a workstation, that is the single most consequential finding available — the independent protective layer is no longer independent.

Sequencing an ICS security programmeSequencing an ICS security programme1InventoryFirstPassive discovery. Most registers under-count controllers substantially.2Architecture reviewSecondEstablish what can actually reach what, rather than what the diagram claims.3Separate the safety layerThirdNo shared accounts, workstations or segments with process control.4Broker engineering accessFourthAuthenticated, time-boxed and recorded — including the integrator.5Monitor and exerciseOngoingPassive detection, plus an incident plan written with operations.
Each step depends on the one before it; inventory is not optional.

Protocols with no security model

Many industrial protocols were designed without authentication or integrity — anything that can send a well-formed packet is treated as legitimate. You will not fix that at the protocol layer on installed equipment.

What works instead is constraining who can speak the protocol at all: strict segmentation so only defined hosts can reach controllers, deep inspection at the boundary, and alerting on command types that should be rare — a logic download outside a maintenance window is a strong signal.

Regulation now reaches this equipment
Alberta energy operators face Regulation 84/2024 aligned to CSA Z246.1 with AER enforcement, utilities face NERC CIP, and designated federal operators face the CCSPA. The programme content overlaps heavily — build it once against IEC 62443 and map it to each obligation rather than maintaining parallel documentation.

The integrator is part of your attack surface

Most ICS estates are configured, maintained and frequently monitored by a systems integrator rather than the operator. That relationship rarely appears in a security assessment and often carries the broadest access of anyone: standing remote connections, shared support accounts, and the engineering software required to reprogram controllers.

Treat it as the third-party risk it is. Ask what access the integrator holds, whether each of their engineers authenticates individually, whether sessions are recorded, and what happens to that access when a contract ends.

Where to start

Find the engineering workstations and establish who can log into them, whether those accounts are individual, and whether the sessions are recorded. It is the shortest path from a foothold to physical consequence.

See OT and ICS security for operators, NERC CIP compliance and Bill C-26 and the CCSPA. GuardsArm delivers OT and ICS security.

Need Help With ICS Security?

Our certified security professionals can help you implement the right ics security strategy for your organization. Get a free assessment today.

Book a Free Consultation