Airports + transportation

Protect movement without interrupting it.

Terminal cameras, access control, baggage handling, building systems, and airfield services sit on networks that cross organizational boundaries. A device meant for the passenger network and a controller meant for airside operations can end up one misconfigured rule apart. Breakwater Secure, Assure, and SOAR give airport security, IT, and operations teams one evidence trail across that boundary, from what is exposed to who approved the fix.

See how the modules apply here
01 OBSERVE · Airside + landside systems02 VALIDATE · Passenger + operations software03 GOVERN + VERIFY · Segmentation + access changes

How the modules fit

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

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 landside and airside systems.

Secure connects terminal cameras, access-control panels, baggage-handling PLCs, building automation, jet-bridge controllers, and passenger Wi-Fi to asset identity, protocol behavior, and reachability. A device that should sit on the passenger network but can reach airfield operations shows up as a candidate path, not a buried log line.

  • Camera + badge-reader inventory
  • Baggage-handling PLCs
  • Airside/landside segmentation
  • Vendor remote access
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 operations.

Passenger kiosks, gate systems, and airline-facing booking and check-in software generate a steady stream of scanner output. Assure traces each finding to its exact source, replays it, and marks what still needs human review, so security and engineering spend validation time on the vulnerability that is actually reachable from outside the terminal.

  • 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 segmentation or access change inside the airport's own approval chain.

Closing a stale rule that lets a camera reach the baggage network is a small change with a large blast radius if it is wrong. SOAR opens the case with evidence attached, routes it to a named approver on the airport's security or operations team, executes only the agreed scope, and re-tests the path after the change ships.

  • 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 badge reader on the wrong VLAN, closed with a named approver.

An access-control panel installed during a gate renovation turns up in a routine discovery scan, still on the contractor's original VLAN. Secure traces its firmware and certificate to a known weakness. A permitted reachability check confirms it can reach the badge database from outside its intended segment.

SOAR opens a case, a named airport security engineer approves a segmentation fix with a rollback plan, and Breakwater re-tests the path after the change to confirm it closed. The record, what was found, what was proposed, who approved it, what was confirmed, stays attached to the panel's file.

Who owns the decision

Built for the teams who share one terminal.

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

Plan a bounded evaluation