Guide · Ship security

ISPS ship security: levels, responsibilities and alerts

Updated 2026-10-11 · About 7 min read

In one sentence

Authorities set security levels; ships and port facilities implement their plans, and SSAS alerts designated recipients.

Application of SOLAS XI-2 and ISPS

The international SOLAS XI-2 / ISPS framework applies to passenger ships, cargo ships of 500 GT or more and mobile offshore drilling units engaged on international voyages, and to port facilities serving these ships. Passenger and cargo ships include the corresponding high-speed craft; check government non-commercial ship exceptions and port-facility application conditions. ISPS Part A is mandatory and Part B is guidance; check separately for local adoption of guidance requirements.[S1][S2][B2]

This page uses the ISPS conference text, the international SOLAS XI-2 text reproduced in the EU Official Journal annex and the STCW Manila amendments; it does not extend the EU regulation’s own provisions into global obligations. This page explains the provisions and concepts reviewed, rather than a complete current consolidated text. For application, check the latest text, applicable flag requirements and company procedures.[S1][S2][S3][S4]

How security levels are set and changed

Flag Administrations set security levels and provide information to their ships; port-state governments set levels and inform facilities and entering or visiting ships, updating notifications when levels change. Ships must follow a higher port-state level and respond to an increase without undue delay, rather than deciding to disregard it.[S2][B1][B2]

Level 1 maintains minimum appropriate protection at all times; level 2 adds appropriate measures for a period of heightened risk; level 3 adds more specific measures for a limited period when an incident is probable or imminent, without requiring an identified target. Follow authority instructions and applicable approved plans, rather than treating blog examples as a fixed global checklist.[S1][B1]

SSP, CSO, SSO and PFSO responsibilities

The SSP must be carried on board, approved by the Administration or a delegated recognized security organization, and cover the security levels. It may be electronic and must be protected against unauthorized deletion, destruction, amendment or disclosure; confidentiality does not mean that a paper original is invariably required.[S1][B2]

The CSO ensures assessments, plan preparation and submission, implementation, maintenance and ship-port coordination. Each ship has a designated SSO for plan implementation and supervision, inspection, reporting, training and coordination; each port facility has a designated PFSO for the relevant plan, inspections, training and coordination. This is a responsibility outline; read the full provisions and approved plan for actual assignments.[S1][B1][B2]

SSAS alert recipients and security records

Ships within SOLAS XI-2/6’s application require SSAS to send identity, position and information that security is threatened or compromised to the authority-designated recipient, which may include the company. The system does not alert other ships or raise an alarm aboard, and continues until deactivated or reset. This does not guarantee it cannot be noticed in any circumstances or promise a particular rescue outcome.[S2][B2]

Security records include plan-related training, incidents, level changes, communications and reviews or audits and must be kept on board. The Administration specifies minimum retention; this page gives no universal number of years.[S1][B2]

Crew security familiarization and designated-duty training

The STCW Manila text requires non-passenger personnel engaged on ISPS-applicable seagoing ships to receive security familiarization before assignment. Crew without designated security duties require relevant awareness training, while those with designated duties must meet the corresponding standard. The SSO separately needs the applicable competence standard and certificate of proficiency; everyone does not have identical training or certification requirements.[S3][S4][B3]

Questions

Do ships and terminals set their own security levels?

No. Administrations or Contracting Governments set and communicate levels; ships and shore facilities implement the corresponding measures.

Must SSAS alerts go only to government agencies?

No. The authority-designated recipient may include the company; no alarm is raised on board.

Is security training needed only by the SSO?

No. Non-passenger personnel engaged on ISPS-applicable ships require security familiarization; Crew without designated duties need relevant awareness training, while designated-duty personnel and the SSO meet their respective standards. The requirements are not identical for all.

Sources