A Port Incident Is a Governance Incident First

A port incident is a governance incident first. The technical failure is usually downstream of an authority failure: someone, or something, could act without a checked permission.

Goran Svetlecic’s question from post-incident briefings, “How could we have stopped this?”, has the same answer in a port as anywhere else: the paths were there long before the compromise, walkable the whole time, but never surfaced in time to act on. A port’s shared systems form an identity graph just as surely as a corporate Active Directory does. Terminal operators, carriers, vendors, and service providers all touch the same operational technology, often through remote access granted years ago and never reviewed. Each of those connections is an edge. Operational control is the Tier 0 at the far end. An adversary does not need a million paths into the port’s systems. They need one, and the graph will provide it if nobody has walked it.

Peacetime is the plan-writing window

The U.S. Coast Guard final rule, 33 CFR Part 101 Subpart F, requires regulated facilities and vessels to designate a Cybersecurity Officer (CySO), complete a Cybersecurity Assessment, and maintain a Cybersecurity Plan. The compliance deadline is July 16, 2027. NVIC 02-26, published in October 2026, provides guidance and templates.

That window is the peacetime phase, and peacetime is when the work is cheap. Mapping the port’s shared connections, ranking them by how many routes each edge carries into operational systems, and cutting the riskiest vendor access now costs a change window and a conversation. The same cut during an incident costs tempo, surprise, and possibly operations, because every wartime cut is observed and contested. Peacetime buys optionality. Wartime spends it, almost always at a loss.

Treat the plan as paperwork and it will behave like paperwork: written to satisfy an inspector, filed, and forgotten until the incident. Treat it as the map and the control it is meant to be and it reads differently. The plan must name who authorizes operational technology actions, what evidence those actions produce, how access is revoked, and how the port keeps operating when a system is isolated.

A plan is not paperwork. It is the control that decides who may act.

Wartime in a port

During a port incident, Goran’s dilemma arrives with physical consequences. Isolate a suspect system and you may flush the adversary onto a path you have not found, or push a financially motivated actor toward destructive action before access collapses. Leave the persistence in place and watch it, and the adversary keeps walking toward operational control. The decision is hard in direct proportion to how little peacetime work preceded it. A port that has walked its graph a dozen times in quiet conditions decides against a map it already understands. A port that has not decides against a map it is reconstructing under fire.

The CySO holds the map

The CySO designation is where governance becomes personal. The CySO is the person accountable for the plan, for the map, and for refusing an action that lacks authority, including an action requested by someone senior, urgent, or commercially important. If the CySO cannot say no in practice, the designation is a title on an org chart, not a control.

That authority has to be established before the incident. During an incident, nobody negotiates decision rights. The port either has a named person empowered to isolate a system, revoke a vendor connection, and halt an operation, or it improvises while the clock runs.

What to do this quarter

Designate the CySO with a written decision right, not just a nomination. Map the port’s shared connections as a graph: who can reach operational systems, through which vendor edges, with what standing access. Cut the highest-fan vendor edges first, while the cuts are cheap. Test the revocation, because a revoke that has never been exercised is a theory. Then write the plan around what the map showed: who authorizes each consequential action, what evidence it produces, how it is revoked, and how operations continue when a system is cut off.

A port incident is a governance incident first. Fix the governance, walk the graph in peacetime, and the technical controls finally have something to enforce.

Source: Goran Svetlecic, “Attack Path Management in Peacetime and Wartime,” LinkedIn, October 27, 2026: https://www.linkedin.com/pulse/attack-path-management-peacetime-wartime-goran-svetlecic-cissp-eqeif/

Recent Posts

Tag Cloud

Stop Threats Before They Execute

Your free Kernel-Level Defense Buyer’s Guide is ready to download.

By providing my email address, I consent to receive emails and text messages—including newsletters and marketing communications—from creators of Warden Secure, Cyber Strategy Institute, our flagship zero-trust platform for ransomware prevention, and agree to the Terms and Privacy Policy. You may unsubscribe at any time.