
Most OT security programs stall in the same place: after the assessment report lands and before anyone changes a firewall rule.
The fix is a sequence, not a bigger plan. Below is the order we recommend for buildings, plants and utilities, why each step sits where it does, and where you can spend less than a vendor will suggest.
Start with a current-state and risk assessment. Who does the work matters more than whose logo is on the report. Ask for the background of the person who will walk your plant room. They should have programmed controllers, commissioned a BAS or SCADA system, or worked an OT incident. An assessor who has only audited IT will hand you a list of missing patches for devices you cannot patch.
The output you need is short: what is connected, how it reaches the outside world, who has remote access, and which systems would cause a safety event or stop operations if they failed. Check out the companion post **here** (https://www.actimeta.com/blog/ot-cybersecurity-risk-assessment-best-practices)
Remove direct internet exposure and control the boundary between IT and OT. It is the first mitigation in the Canadian Centre for Cyber Security's July 2026 bulletin on non-state activity targeting Canadian OT, and it gives the largest return for the least money. Most field protocols, such as BACnet and Modbus, do not authenticate the commands they receive. If an attacker can reach a controller, they can usually change it. Keeping it unreachable does most of the work.
Measure it. Count your internet-reachable OT systems before and after. The target is zero, with every exception documented and owned.
Vendors and integrators need to reach your systems. The question is how. Dragos reports that 73% of its OT incident response cases to date involved compromised VPN or jump host credentials. That is vendor data from its own engagements, not a census, but it points at the same weak spot. Route every remote session through one controlled path with named accounts, multi-factor authentication, session approval and logging. Then remove the modems, remote desktop tools and cloud connectors that bypass it.
Separate OT from the business network first. Then separate OT systems from each other where the consequence justifies it. In vendor research, Forescout's Vedere Labs analyzed 47,700 network segments at 209 organizations and found that only 13% of the segments containing OT devices held OT devices alone. Shared segments are the norm.
A firewall between IT and OT, with rules someone can explain, delivers most of the benefit. Microsegmentation costs more to design and to maintain. Reserve it for systems whose compromise would hurt people or stop the business.
You may wonder why the inventory comes fifth. Steps 2 to 4 need a working list from the assessment, and a full inventory is easier to build once the network is organized. Start manually: BAS graphics, as-built drawings, maintenance records and a walkthrough. A spreadsheet an operator keeps current is worth more than a discovery platform nobody reviews. Buy the tool when the manual list becomes the bottleneck.
Monitoring comes last because it depends on everything before it. Without a known perimeter, a single remote access path and an inventory, a monitoring platform reports normal operation as thousands of anomalies. It also needs people. Decide who will read the alerts, and what they are allowed to do, before you sign the purchase order.
Run one task alongside all six steps: write down what happens when a system fails or is compromised. Who calls whom, how the site runs manually, where the controller backups are and when they were last restored. It costs little, and the SANS Five ICS Cybersecurity Critical Controls list the incident response plan first for a reason.
Not every site needs all six steps at the same depth. An office building with one BAS front end does not need the program of a hospital central plant or a water treatment facility. Rank your sites by consequence: safety, regulatory exposure, revenue and tenant impact. Every site gets a closed perimeter, controlled remote access and basic segmentation. The rest scales with what is at stake.
The frameworks agree on the content, if not on the order. ISA/IEC 62443-2-1 sets out program requirements for asset owners. NIST SP 800-82 Rev. 3 is the US reference, with Rev. 4 in public draft at the time of writing. Saudi Arabia's OTCC-1:2022 and the EU's NIS2 Directive, through national laws, set mandatory baselines for the entities in their scope. Use them to check for completeness, not to set the sequence.
A site that finishes steps 2 and 3 this quarter is safer than one that buys a monitoring platform and leaves its controllers on the internet.
It is six steps in order: assess the current state, close the perimeter, fix remote access, segment, build the asset inventory, and monitor and detect. Write down your incident response plan alongside all six, and scale the depth to each site's consequence.
With a current-state and risk assessment, done by someone who has programmed controllers, commissioned a BAS or SCADA system, or worked an OT incident. Then close the perimeter, which gives the largest return for the least money, and fix remote access.
Without a known perimeter, a single remote access path and an inventory, a monitoring platform reports normal operation as thousands of anomalies. It also needs people to read the alerts.
Planning a new smart building, upgrading the systems in an existing one, or buying technology for a facility? Actimeta is an OT cybersecurity and technology advisory firm that helps owners get the design, the vendors and the security right from the start. Our building assessment service reviews your building systems and gives you clear remediation plans. Our project management team delivers OT cybersecurity implementation services through to commissioning. Our procurement advisory services help you choose the right vendors and tools before you sign. Book a free consultation to talk through your project.