BreakwaterBreakwater
Product access →Talk to us

Power + utilities

Prioritize resilience, not finding volume.

Substations, remote engineering access, legacy protocols, and compensating controls make up one operating system, even when different teams manage the pieces. A finding that is routine on a corporate laptop can affect service continuity when it reaches a protection relay. Breakwater Secure, Assure, and SOAR give utility security, OT engineering, and compliance teams one evidence trail from exposure to authorized, verified response.

See how the modules apply here ↓
01 OBSERVE · Substations + remote access02 VALIDATE · Utility-facing software03 GOVERN + VERIFY · Substation changes

How the modules fit

One evidence-to-action system, applied to the grid.

Secure, Assure, and SOAR keep their separate jobs. What changes here is the asset list, the software under test, and who signs off on a change.

Capability availability depends on product maturity, installation, integrations, permissions, and the operating boundaries agreed for each deployment. See the executive reference architecture → for how evidence, boundaries, and authority connect.

01OBSERVE

Breakwater Secure

Build the operating picture across substations and remote engineering access.

Secure connects substations, RTUs, protection relays, remote-access gateways, and the certificates protecting them to asset identity, protocol behavior, and reachability. A remote-maintenance path into a substation that was supposed to be temporary shows up as a candidate route, not an assumption in a network diagram.

  • Substation + RTU inventory
  • Protection relay reachability
  • Legacy protocol exposure
  • PQC readiness
THE DECISIONWhat exists, what changed, and what is plausibly exposed?Visit Secure ↗
02VALIDATE

Breakwater Assure

Separate a defensible finding from scanner noise before it reaches an engineer.

AMI head-end software, DERMS platforms, and utility-facing applications generate findings that compete for the same engineering attention as grid operations. Assure traces each finding to its exact source and replay evidence, so a security team can defend a priority call to an operations lead who is also managing storm response.

  • Source traceability
  • Independent replay
  • Coverage limits
  • Human review
THE DECISIONIs this finding defensible, and what evidence supports it?Visit Assure ↗
03GOVERN + VERIFY

Breakwater SOAR

Keep a substation change inside named engineering approval and rollback.

A segmentation or access change at a substation carries real safety and reliability stakes. SOAR opens the case with evidence attached, routes it to a named protection or OT engineer, constrains execution to the agreed scope, and re-tests the path after the change to confirm what actually closed.

  • Case evidence
  • Approval gates
  • Bounded execution
  • Outcome verification
THE DECISIONWhat can change safely, who can approve it, and did it work?Visit SOAR ↗
WHAT THIS LOOKS LIKE

A vendor's temporary access, closed with a named engineer's sign-off.

A remote-access gateway installed for a vendor's temporary maintenance window is still active six months later. Secure flags it against the utility's asset inventory. A permitted reachability check confirms it can reach a protection relay's engineering interface from outside the substation's intended boundary.

SOAR opens a case, a named protection engineer approves closing the access with a rollback plan, and Breakwater re-tests the path after the change. The record, what was found, what was proposed, who approved it, what was confirmed, stays attached to the substation's file.

Who owns the decision

Built for the teams who share one substation.

Breakwater keeps each team's evidence attributable to its own systems without erasing where responsibility actually sits.

Plan an evaluation

Bring us the system you cannot fully account for.

We will define a bounded evaluation with explicit evidence sources, success criteria, and the utility's own approval model.

Plan a bounded evaluation →