Program Visibility · Taurus
Map the plant you already run
How operators build a real asset and connection register from the drawings, historians and switches the plant already has.
Understanding industrial systems.
Practical notes on OT visibility, hardening and response, one for each program, and the questions behind industrial decisions.
Program posts describe the work as the programs train it. Posts marked as an illustrative scenario are fictional exercises. Nothing here is an instruction for changing a live system.
Program Hardening · Orion
Harden the line you cannot patch
Patching a running PLC is rarely an option, so hardening works through segmentation, compensating controls and the access paths that already exist.
Program Response · Canis Major
Read the alert you already have
The Response program trains operators to trust or explain a detection, run a playbook under pressure, and prioritize when everything changes at once.
Illustrative scenario
Before you close a segmentation gap, understand why it exists
An undocumented connection can be both a security concern and a clue to an operating dependency.
Illustrative scenario
A vendor access request is also a context problem
A familiar vendor and a familiar task still leave important questions about authorization.
Illustrative scenario
An OT alert needs an explanation before it needs a playbook
Practice separating an observation from an assumption before deciding what a response requires.