A framework by Mike Holcomb
BASIC START
The top 10 cybersecurity controls for OT/ICS environments. If you run, defend or test industrial systems and don't know where to begin, begin here.
Why BASIC START
Most OT sites don't get compromised through exotic zero-days. They get hit through the same gaps over and over: flat networks, always-on vendor access, unknown assets, no tested backups and nobody watching the wire. These are also the gaps a penetration tester finds first.
BASIC START groups the fixes for those gaps into ten controls. The first five (BASIC) are the foundation. The next five (START) build on it. The letters make the list easy to remember in a meeting, on a plant floor or in a budget conversation.
The 10 controls
BASIC
1. Backup & Recovery
Keep current, offline copies of PLC and controller logic, HMI and SCADA projects, historian and engineering workstation images, and network device configs. Test restores. A backup you've never restored is a guess.
2. Asset Inventory
Know every device: hardware, software and firmware. Make, model, firmware version, IP and MAC, location, owner and how critical it is to the process. You can't protect, patch or monitor what you don't know exists.
3. Secure Network Architecture
Separate IT from OT with an industrial DMZ, then break OT into zones with controlled conduits between them (the IEC 62443 approach). Deny by default. Nothing in the control network should talk directly to the internet.
4. Incident Response Planning
Write an OT-specific plan: who decides to isolate or shut down, how operations run manually, which vendors to call and how to preserve evidence. Then run tabletop exercises with operations, engineering and IT in the room.
5. Continuous Vulnerability Management
Track vendor and CISA ICS advisories against your inventory. Prioritize by exposure and known exploitation, not just CVSS. When you can't patch, apply and document compensating controls.
START
6. Secure Remote Access
Route all remote and vendor access through a jump host in the DMZ with multi-factor authentication. Grant it on demand, limit it in time and log every session. No always-on connections, no unmanaged remote tools.
7. Training & Awareness
Train people for the role they have. Operators, engineers, maintenance techs and contractors each need to recognize phishing, USB and social engineering risks in their own work, and know how and when to report something odd.
8. Risk Assessments
Start from consequences: what is the worst thing that could happen to the process, and what would it take? Identify your crown jewels, rank risks by impact and likelihood, and revisit after every significant change.
9. Real-Time Network Monitoring
Passively monitor OT traffic so you know what normal looks like. Alert on new devices, new connections, program downloads and controller mode changes. Make sure someone actually owns and responds to those alerts.
10. Teamwork (IT/OT Partnership)
Security in OT only works when IT, OT engineering and operations work together. Agree on ownership, shared change management and who calls the shots during an incident, before you need to.
How to use it
- Score yourself. For each control, rate your site from 1 (not started) to 5 (fully in place and maintained). Be honest. The low scores are your roadmap.
- Fix the foundation first. Backups, inventory and architecture make every other control cheaper and more effective.
- Test it. A penetration test or assessment shows whether the controls you believe you have actually hold up.
- Repeat. Re-score at least once a year and after major changes to the plant or network.
Industrial Penetration Testing is coming soon
Mike Holcomb's new book. Join the waitlist to hear first when it's ready.