River Caudle
OT / ICS security · field research & frameworks
On this page
  1. § 01Embedded, not parachuted
  2. § 02What I don't do
  3. § 03The shape of an engagement
  4. § 04What you keep

Practice · How the work runs

Building capability,not reports.

How engagements run.

A report is a snapshot of someone else's understanding. Capability is yours, and it stays. The work is to leave a plant or a program able to do for itself what it was paying an outsider to do.

If the engagement ends and your team can't carry it, the engagement failed.

River Caudle · Riverman · OT/ICS Security Practice

§ 01. Embedded, not parachuted

The work happens next to your engineers.

Parachute consulting drops in, documents the gap, and leaves the gap. I work embedded. Alongside the people who run the plant, in their constraints, on their substrate. The deliverable isn't a binder; it's a team that didn't have a capability before and has it now.

How I show up

  • On the floor: with the controls people, not above them.
  • In the constraints: your uptime, your safety case, your vendors.
  • On the record: decisions written down and owned by you.
  • Time-boxed: a defined end, with capability transferred before it.

What that produces

  • A design: that your engineers can defend and modify.
  • A method: repeatable after I'm gone.
  • A baseline: measured, not asserted.
  • Independence: the point of the whole exercise.
"If the engagement ends and your team can't carry it, the engagement failed."

§ 02. What I don't do

The work has edges.

Knowing what to refuse is part of the method. These are not constraints on the engagement. They are the reason it works.

Not this

  • Compliance theater for an audit date
  • Rip-and-replace of working control systems
  • Tooling you can't run without me
  • Findings with no path to closure

This

  • Controls that survive the audit because they're real
  • Change treated as risk, sequenced deliberately
  • Tooling you own and can audit
  • A closed loop: find, design, transfer, verify

§ 03. The shape of an engagement

Assess, design, transfer.

Different programs, same arc. Scope changes; the structure doesn't. Each phase has an exit condition that is demonstrable, not asserted.

Phase

  • Assess: substrate, traffic, ownership reality
  • Design: the network as drawn, not accumulated
  • Transfer: your engineers run the method

Exit condition

  • A baseline your team can reproduce
  • A design your team can defend
  • The method run without me in the room

§ 04. What you keep

The deliverable is independence.

Practice is doctrine under load. The frameworks below are how the work is structured once it's underway. Read them to see the method before you ever talk to me.

"The deliverable is independence. Everything else is paperwork."

River Caudle · river@riverman.io · Houston, Texas