RiverClear: what an organization looks like inside Radius

1. Observe: the surface as found

A run starts passively. Radius watches the RiverClear surface (assets, services, identities, dependencies) and writes nothing to a controller. The first screen is the inventory Radius built, including what the operator’s own inventory missed: the historian’s second interface, a remote-access appliance nobody owns, and a service account that both the corporate directory and the plant network trust.

2. Reason: the attack graph

From the inventory Radius builds the attack graph and decides what to try first, by where each path leads. On RiverClear the paths that matter end at the reservoir SCADA controller and the production warehouse. The graph orders them by consequence, not by the severity score of the first hop. Chains that share a hop (here, the trusted service account) are grouped, because they share a fix.

3. Attack: inside the rules that were signed

Radius runs the real chain against RiverClear: the remote-access appliance, the identity bridge, the stale service account, the engineering workstation. Every action is checked against the rules of engagement before it runs. The field controllers are marked passive-only in those rules, so the chain stops at the workstation that can reach them. That is the point that proves the path, before the payload that would affect the process.

4. Validate: how far it got

The findings screen shows each hop with the command, the timestamp and what came back. That is the evidence: not that a path is theoretically exploitable, but that this chain reached this host at this time, and stopped where the rules said it must.

The safety trail behind it

Alongside the findings sits the safety audit trail: every action an agent attempted, the decision taken on it, the reason, and a snapshot of the rules of engagement in force at that moment. On RiverClear the trail shows the attempts the interceptor refused at the controller boundary as clearly as the ones it allowed. An operations manager can read it and see what was done to the plant, action by action.

5. Report: three reports, three levels

The run ends with three reports (executive, technical, compliance), each at three levels: the whole run, a single asset, a single finding. On RiverClear the executive report says what was reachable and what a fix changes. The technical report carries the chain hop by hop. The compliance report expresses the run as control evidence: what was tested, when, under whose authorization, with what outcome.

After the fix

The fix on RiverClear is the chokepoint the graph pointed at: revoke the service account’s trust on the plant side and segment the workstation. Once it lands, Radius attacks the same path again. The ticket carries the chain that produced it and closes only when the re-attack fails.

Customer results will be published when a customer agrees to be named.