Index · Methodologies · Portfolio
The Riverman methodologies for industrial networks.
Six frameworks, each addressing a different problem on the plant floor: from how networks are designed, to how they are secured, to how they are troubleshot, to how the people who run them learn the work. Each is small, named, and meant to be carried in the head.
Free to plant operators and industrial workers. Forever. Commercial use under the Riverman Fair License v2.0.
River Caudle · Riverman · OT/ICS Security Practice
§ Design
§ Security
§ Troubleshooting
Reboot · Inspect · Verify · Examine · Replace
Layer-1-up, physical-first troubleshooting. For the tech on shift. When in doubt, follow the RIVER.
Read the method →
Scope · Test · Replicate · Execute · Assess · Mitigate
Cyclic methodology for intermittent, remote, and multi-system problems. Execute → Assess → Execute → Assess until you reach the solution.
Read the method →
§ Training
§ Doctrine
In OT, change is risk. Stability is security.
Why "if it ain't broke, don't fix it" is professional excellence. Firmware longevity as a feature, not a flaw.
Read the doctrine →
One unit per zone · scope is the only thing that changes
Operational sovereignty for industrial infrastructure. The full doctrine lives at industrialindependence.org.
External site ↗
§ How They Fit Together
SHIP is what you build, SECURE is how you defend it, RIVER and STREAM are how you fix it, Schema on Read is how you teach it, and the OT Stability Doctrine is how you stop people from breaking it. The Industrial Independence Architecture is the lens through which they all line up.
If you're starting from zero on a plant floor:
River Caudle · river@riverman.io · Houston, Texas