BreakwaterBreakwater
Product access →Talk to us

Connected industry

See cyber risk in production context.

PLCs, HMIs, industrial gateways, and the software dependencies behind them keep a production line running, often years past the point where every device can be patched. A finding that is routine on an office laptop can stop a line when it reaches a controller. Breakwater Secure, Assure, and SOAR give plant IT, OT engineering, and process safety teams one evidence trail from exposure to a change the line can absorb.

See how the modules apply here ↓
01 OBSERVE · PLCs, HMIs + gateways02 VALIDATE · Plant-facing software03 GOVERN + VERIFY · Production-system changes

How the modules fit

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

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 PLCs, HMIs, and industrial gateways.

Secure connects PLCs, HMIs, gateways, unsupported and end-of-life devices, and the maintenance and vendor remote-access paths that reach them to asset identity, protocol behavior, and reachability. A gateway that should be isolated to one production cell but can reach the plant network shows up as a candidate path, not an assumption in a network diagram.

  • PLC + HMI inventory
  • Unsupported device tracking
  • Vendor remote access
  • Protocol exposure
THE DECISIONWhat exists, what changed, and what is plausibly exposed?Visit Secure ↗
02VALIDATE

Breakwater Assure

Separate a defensible finding from scanner noise before it touches production.

MES integrations and plant-facing software generate findings that compete for the same engineering time as keeping the line running. Assure traces each finding to its exact source and coverage limits, so a security team can defend a priority call to a plant manager measured on uptime, not patch counts.

  • 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 production-system change inside maintenance-window and process-safety approval.

A configuration or segmentation change on a production system carries real safety and continuity stakes. SOAR opens the case with evidence attached, routes it to a named process-safety-aware approver, constrains execution to the agreed maintenance window, 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 gateway added during a line expansion, closed inside a maintenance window.

An industrial gateway added during a line expansion turns up in a routine discovery pass, still reachable from the corporate network it was meant to be isolated from. Secure traces its firmware to a known weakness. A permitted reachability check confirms the exposed path.

SOAR opens a case, a named plant engineer approves a segmentation fix scheduled inside the next maintenance window, and Breakwater re-tests the path after the change ships. The record, what was found, what was proposed, who approved it, what was confirmed, stays attached to the gateway's file.

Who owns the decision

Built for the teams who share one line.

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 plant's own approval model.

Plan a bounded evaluation →