Section 16.3 Security Levels (MARSEC Levels) and Corresponding Actions

A core component of the ISPS Code framework is the concept of Security Levels. These levels provide a standardized means for ships and port facilities to implement appropriate security measures commensurate with the perceived threat. The ISPS Code defines three security levels, and the Ship Security Plan (SSP) must detail the specific additional protective measures to be implemented as the security level increases. The Master, under guidance from the Company Security Officer (CSO) and relevant authorities (Flag State, Port State, or Coastal State), is responsible for ensuring the ship operates at the correct security level and that all required measures are effectively applied. Understanding these levels and the corresponding actions is crucial for maintaining a proactive and responsive security posture.

1. Definition of Security Levels (ISPS Code Part A, Section 2.1.9 – 2.1.11):

Security Level 1 (Normal):

Definition: The level for which minimum appropriate protective security measures shall be maintained at all times.

Operational Context: This is the standard day-to-day operating level when there is no specific or heightened threat information. The baseline security measures outlined in the SSP are continuously in effect.

Security Level 2 (Heightened):

Definition: The level for which appropriate additional protective security measures shall be maintained for a period of time as a result of a heightened risk of a security incident.

Operational Context: This level is set by the Flag State, a Contracting Government (e.g., Port State), or the Company when there is intelligence indicating a greater likelihood of a security incident. This might be due to general threat levels in a region, specific intelligence about potential threats to shipping or port facilities, or other security concerns.

Security Level 3 (Exceptional):

Definition: The level for which further specific protective security measures shall be maintained for a limited period of time when a security incident is probable or imminent, although it may not be possible to identify the specific target.

Operational Context: This is the highest security level and is usually set for a short duration in response to credible intelligence indicating a very high or specific threat. Operations at Security Level 3 impose significant restrictions and require maximum vigilance.

2. Setting and Communicating Security Levels:

Who Sets Security Levels:

Flag State Administration: Can set the security level for its flagged vessels.

Contracting Governments (Port States / Coastal States): Can set the security level for ships in their territorial waters or port facilities under their jurisdiction.

Company (via CSO): The Company may instruct its ships to operate at a higher security level than that set by the Flag or Port State if its own risk assessment indicates a need.

Communication:

Changes in security level are communicated to ships through various channels, including:

Company instructions (from the CSO).

Port authorities (PFSO or VTS) upon arrival or during port stay.

Flag State advisories.

Navigational warnings or security broadcasts.

The Master must ensure that any change in security level is immediately communicated to all shipboard personnel and that the required measures are implemented promptly.

The ship must acknowledge receipt of instructions to change security level.

3. Actions and Measures Corresponding to Each Security Level (as detailed in the SSP):

The Ship Security Plan (SSP) must specify the security measures to be implemented at each security level. These measures are cumulative; i.e., measures for Security Level 2 include all those for Level 1 plus additional ones, and Level 3 includes all Level 1 and 2 measures plus further specific actions. The following are general examples, and the specific measures for any given bulk carrier will be detailed in its approved SSP.

A. Measures at Security Level 1 (Normal): These are the baseline security measures implemented at all times.

Access Control:

Checking identity of all persons boarding.

Maintaining a visitor/personnel log at the access point (gangway).

Controlling embarkation of ship’s personnel and effects.

Challenging unescorted or unidentified persons.

Securing (locking/monitoring) unused access points to the ship.

Monitoring of Deck Areas and Surroundings:

Maintaining a general security watch/patrol, especially in port or at anchor.

Adequate deck lighting at night.

Monitoring the waterside of the vessel.

Restricted Areas:

Ensuring restricted areas (bridge, engine room, etc.) are appropriately secured against unauthorized access.

Cargo Handling:

Checking cargo documentation for irregularities (as part of normal due diligence, though primarily a safety/commercial check, it has security implications).

Visually inspecting cargo and cargo spaces for tampering or suspicious items during loading/discharge (to the extent practicable for bulk cargoes).

Delivery of Ship’s Stores and Bunkers:

Checking identity of delivery personnel and vehicles.

Verifying stores against delivery notes.

Supervising loading of stores and bunkers.

Security Equipment:

Ensuring security equipment (e.g., gangway controls, lighting, communication systems) is operational.

Security Communication:

Maintaining communication with CSO and PFSO as needed.

B. Additional Measures at Security Level 2 (Heightened): In addition to Level 1 measures, the SSP will require enhanced precautions:

Increased Frequency and Detail of Security Patrols: More vigilant monitoring of deck areas, restricted areas, and the ship’s surroundings (including waterside).

Stricter Access Control:

Limiting the number of access points to the ship (e.g., using only one gangway).

More thorough identity checks.

Increased searching of persons, baggage, and effects.

Escorting all visitors.

Potentially denying access to non-essential personnel.

Enhanced Monitoring of Restricted Areas: More frequent checks or continuous monitoring.

Increased Vigilance for Cargo Handling: Closer scrutiny of cargo operations and documentation. More attention to sealing of holds after loading if applicable.

More Thorough Checks of Stores and Bunkers: Before and during loading.

Waterside Security: Increased monitoring for suspicious craft; potentially deploying deterrents if safe and appropriate (e.g., rigging fire hoses, though this is more common at Level 3 or in specific high-risk piracy areas).

Briefing Crew: Reminding crew of heightened threat, emergency procedures, and reporting protocols.

Declaration of Security (DoS): May be required more frequently with port facilities.

Preparation for Higher Level: Potentially preparing to implement Level 3 measures if the situation escalates.

C. Further Specific Protective Measures at Security Level 3 (Exceptional): This is the highest level, implemented when a security incident is probable or imminent. Measures are usually for a limited duration and are very restrictive.

Maximum Restriction of Access:

Access to the ship strictly limited to those performing essential operational or security duties.

Suspension of all visits.

Potentially stopping cargo operations, bunkering, or stores delivery.

Searching all persons and items brought onboard.

Intensified Monitoring and Surveillance:

Continuous monitoring of the ship, its surroundings, and all access points.

Maximum use of lighting and any surveillance equipment (CCTV).

Possible deployment of additional security personnel or lookouts.

Restricted Movement within the Ship: Limiting access even for crew to certain areas.

Preparation for Emergency Response:

Crew briefed and ready to implement emergency security procedures (e.g., lockdown, evacuation if necessary).

SSAS activation points checked and personnel reminded of procedures (though SSAS is for covert alerting).

Communication lines to CSO, Flag State, and relevant authorities kept open.

Declaration of Security (DoS): Almost certainly required with the port facility.

Search of the Ship: A comprehensive search of the ship for suspicious devices or unauthorized persons may be conducted.

Possible Evacuation or Movement of Ship: Under instruction from authorities, the ship might need to be evacuated or moved to a more secure location.

Suspension of Operations: Non-essential operations are likely to be suspended.

4. Declaration of Security (DoS):

Purpose: A DoS is an agreement reached between a ship and a port facility (or another ship during ship-to-ship operations) concerning the security measures each will undertake when they are interfacing and there is a need for enhanced coordination. It formally records the agreed allocation of security responsibilities.

When is a DoS Required or Advisable? (ISPS Code Part A, Section 5)

When the ship is operating at a higher security level than the port facility or other ship it is interfacing with.

When the port facility is operating at a higher security level than the ship.

When there has been a security threat or a security incident involving the ship or the port facility.

When the ship is at a port which is not required to have and implement an approved Port Facility Security Plan (PFSP) (e.g., some smaller or non-ISPS compliant terminals).

During ship-to-ship (STS) operations with another ship that is not required to have and implement an approved SSP (e.g., some domestic vessels or non-SOLAS ships).

A Port State may also have national requirements for when a DoS is needed.

Content: The DoS addresses security activities such as:

Monitoring of restricted areas.

Controlling access to the ship/port facility.

Monitoring of deck areas and surroundings.

Handling of cargo.

Delivery of ship’s stores.

Handling of unaccompanied baggage.

Security communications. It specifies which party (ship, port facility, or both) is responsible for each measure for the duration of the interface.

Process:

The DoS should be completed by the Master or the SSO on behalf of the ship, and by the PFSO (or their representative) on behalf of the port facility.

It should be completed before the ship-port interface activities commence or as soon as possible thereafter if the security level changes during the interface.

Both parties retain a signed original.

The duration of validity of the DoS should be specified.

Importance: It ensures clear understanding and agreement on security responsibilities, preventing gaps or overlaps in security coverage during the critical ship-port interface.

5. Master’s and SSO’s Responsibilities Regarding Security Levels:

A. Implementing the Correct Security Level:

The Master, advised by the SSO, is responsible for ensuring that the ship operates at the security level set by the Flag State, the Port State (when in their waters), or the Company (if higher).

This involves activating all security measures detailed in the SSP for that specific level.

B. Promulgation and Awareness:

Ensure all crew members are immediately informed of any change in security level and understand the additional measures they need to implement.

Post notices regarding the current security level at access points and other appropriate locations.

C. Liaison with CSO and PFSO:

Maintain close communication with the Company Security Officer (CSO) regarding security level instructions, threat information, and any security incidents.

Liaise with the Port Facility Security Officer (PFSO) to confirm the port facility’s security level, coordinate security measures, and complete a Declaration of Security (DoS) when required.

D. Resource Management:

Ensure sufficient manpower and resources are allocated to implement the required security measures effectively, especially at higher security levels (e.g., for increased patrols, stricter access control). This may involve adjusting watch schedules or assigning additional duties.

E. Maintaining Vigilance:

Even at Security Level 1, maintain a baseline level of security awareness and vigilance.

At higher levels, ensure heightened vigilance is maintained by all crew.

F. Record Keeping:

Meticulously record all changes in security levels (date, time, authority setting the level), security measures implemented, security drills and exercises, security incidents or breaches, and communications related to security in the ship’s security records (often a dedicated security log or part of the deck logbook).

Keep copies of all completed Declarations of Security.

G. Reporting:

Report any security incidents, breaches, or suspicious activities to the CSO, PFSO, and relevant authorities as per SSP procedures and local requirements.

Report any difficulties in implementing required security measures.

Analysis for the Master (Security Levels): The management of security levels is a dynamic and critical responsibility.

Proactive Stance: Do not wait for an incident to occur. Implement measures promptly when the security level is raised.

Clear Communication is Key: Ensure all crew understand their roles and responsibilities at each security level. Misunderstandings can lead to security breaches.

Balance Security with Operations: While security is paramount, especially at higher levels, the Master must also consider how to maintain essential ship operations safely. The SSP should provide guidance on this.

Use the SSP as a Practical Guide: The SSP is not just for audits; it’s the operational manual for implementing security measures at each level.

Professional Judgment: While instructions on security levels will come from authorities or the CSO, the Master must use their professional judgment in applying the SSP measures effectively to their specific vessel and circumstances.

The system of security levels provides a flexible and responsive framework for adjusting the ship’s security posture based on evolving threat assessments. The Master’s diligent implementation of the measures specified in the Ship Security Plan for each level is crucial for deterring security threats and protecting the vessel, its crew, and its cargo.