Keep threat, vulnerability and consequence separate

Threat describes the potential hostile event and its likelihood in the relevant place and time. Examples include a projectile strike, attempted boarding, coercive diversion, sabotage, surveillance, GNSS interference or attack by an uncrewed surface vessel.

Vulnerability describes how susceptible the ship is and how effective its controls are. Freeboard, speed, access points, watchkeeping, detection range, machinery redundancy, communications, firefighting capability and crew proficiency can all matter.

Consequence describes what can happen if the event succeeds. Loss of life is paramount. Other consequences include fire, pollution, loss of propulsion, cargo release, blockage of a route, detention, business interruption and escalation involving another State.

A severe regional threat does not mean every event is almost certain for every vessel. Nor does strong hardening make the threat disappear. The assessment should record these dimensions separately before reaching an overall judgment.

The company should avoid decorative multiplication of arbitrary numbers. A matrix can support comparison, but only when definitions, evidence and decision thresholds are documented. A score of 12 has no inherent meaning if one assessor calls vulnerability “three” and another uses the same number for a different condition.

Define the ship and operation precisely

“Transit Hormuz” is too broad an assessment unit. The operation should specify ship, direction, route version, entry window, load condition, draft, speed limits, intended ports, waiting plan and reporting arrangement.

The ship profile should include flag, ownership and management associations, recent trading pattern, cargo, public visibility and any characteristic that current competent guidance identifies as relevant. An association can affect perceived exposure, but it must not be treated as proof of targeting without evidence.

Physical characteristics matter. A deeply laden tanker may have limited manoeuvring margin and high pollution consequence. A fast ship may reduce boarding exposure but still face missiles or drones. A small low-freeboard vessel may be easier to board. A gas carrier can have strong design protections while presenting potentially severe emergency consequences.

Operational context also changes risk. A safe speed in open water may be unsafe in congestion. A daylight passage may improve visual detection but increase visibility. Waiting can avoid a reported hazard while creating a stationary target and consuming crew rest.

The assessment must state the contemplated operation, not an average ship in an average week.

Use current threat evidence with explicit scope

The company security officer should assemble current JMIC and UKMTO products, coastal and flag-state notices, NAVAREA warnings, naval coordination advice and verified incident reporting. Each source needs an issue time, geographic scope and validity check.

A recent attack near an intended route is relevant evidence. It does not automatically reveal why that vessel was selected or predict that every similar ship will be attacked. Incident clusters require denominators such as comparable transits before they support a rate.

JMIC’s threat scale gives a common likelihood vocabulary. The assessor should quote the current level and definition rather than translating “severe” into an invented percentage. If an analyst makes a forecast, it should be labeled as a forecast with its assumptions.

Conflicting reports should remain visible. A master’s report, an authority warning that relays it and a later IMO-confirmed entry may be three stages of one event, not three incidents.

Evidence should be refreshed before sailing and during the passage. The May 2026 industry guidance says transit decisions should use fresh, continually updated voyage-specific assessments and a shared operational picture among the master, company security officer, shore management and ship security officer.

Test vulnerability against each threat

A single “vessel vulnerability” rating hides important differences. Controls effective against boarding may offer little protection against a projectile or navigation deception.

For small-craft boarding, assess detection, speed, freeboard, access control, barriers, lighting policy, manoeuvring limits, communications and protected positions.

For missiles, drones and uncrewed surface craft, consider lookout sectors, warning time, machinery readiness, watertight integrity, firefighting, casualty shelter, damage control and authority coordination. The assessment should not promise that shipboard measures can prevent a military weapon strike.

For GNSS interference, test independent radar and visual fixing, gyro and log inputs, paper-chart competence where relevant, ECDIS cross-checking, parallel indexes and bridge drills.

For coercive hails or attempted diversion, verify authentication procedures, flag guidance, reporting paths, bridge authority and the safe-navigation consequences of complying or refusing.

IMO’s ship-security-assessment guidance calls for identifying existing measures, key operations to protect, possible threats and their likelihood, and weaknesses including human factors. The output should show which weakness each proposed control addresses.

Treat people as a control with limits

A risk assessment can overstate controls by listing “enhanced watch” without testing whether enough rested and qualified people exist to sustain it.

The plan should identify bridge, engine-room, lookout, security and damage-control roles through the full exposure period. It should account for uncertain delays, pilotage, port watches and post-transit recovery. A short high-intensity phase can become a long operation if a window closes.

Training must fit the threat. A GNSS-loss drill does not prove readiness for fire, flooding, mass casualty or suspicious VHF communications. Drill findings should change the plan where they reveal gaps.

Stress and fatigue can reduce detection and judgment. The May guidance specifically recognizes human-performance effects from workload, uncertainty and environmental conditions. A control that depends on flawless performance under extreme fatigue is weak.

The master retains professional judgment over decisions necessary to maintain ship security. Shore and chartering pressure cannot convert an exhausted team into an acceptable mitigation.

Connect controls to decision thresholds

The assessment should end with actions, owners and triggers rather than a color alone.

A proceed decision may require an authenticated route, functioning redundancies, rested team, reporting completed, cover confirmed and no new incident within a defined review area. A defer decision may follow a worsened threat assessment, unavailable route confirmation or failed essential equipment. An abort trigger may include loss of position integrity, propulsion degradation, route closure or a developing attack ahead.

Thresholds should be set before commercial pressure peaks. The document should name who can authorize sailing, who can stop it and how disagreement is escalated. The master’s overriding authority remains intact.

Residual risk must be described honestly. “Controls applied” does not mean “safe.” It means specified vulnerabilities were reduced while defined exposure remains.

MARAD’s active advisory tells US-flagged ships to conduct pre-voyage risk assessments, incorporate protective measures into vessel security plans, coordinate with NCAGS and consider current routing recommendations. Other flags should follow their own binding and advisory requirements.

Translate the assessment into commercial terms

Owners need to know whether the ship can perform the ordered voyage with acceptable residual risk and within insurance conditions. Charterers need the factual basis for timing, alternative employment and contract notices. Insurers need disclosure consistent with policy terms, not a matrix engineered to obtain approval.

Brokers should not compare two fixtures solely by war-risk premium. A lower premium may reflect different information, deductibles, warranties, duration or vessel profile. Traders should model delay and cargo consequences separately from ship-security probability.

Scenario costs should include waiting, fuel, port charges, crew, security measures, additional premium, cargo deterioration, inventory disruption and a casualty downside. Estimates must be labeled and should not imply that money compensates for unacceptable life-safety exposure.

ZeaClub can link each threat, vulnerability and control to current evidence, assign review times and flag changed assumptions. It can compare scenarios and preserve approvals. It should not generate a false precise “sail score” or replace the master, security professionals, flag State, insurer or legal adviser.

Commercial conclusion

A severe threat level is a regional input, not a universal sailing verdict. It should raise the baseline, accelerate review and demand stronger evidence.

The defensible workflow is to define the exact operation, identify current threats, test ship-specific vulnerabilities, assess consequences, apply controls and state residual risk with proceed, defer and abort thresholds.

That process may produce different decisions for two ships without contradicting the regional warning. Consistency means using the same disciplined method, not forcing every vessel into the same answer.

This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.

Sources