ISPS (International Ship and Port Facility Security Code)

ISPS Code (International Ship and Port Facility Security Code) is an international maritime security framework adopted by the International Maritime Organization (IMO) in 2002 in response to maritime terrorism threats...

How ISPS works in practice

A practical sequence teams can use to standardize adoption and reduce risk.

1

Security Risk Assessment

Security Risk Assessment: The vessel's master and security officer (designated by vessel owner) conduct a threat assessment:

2

Identify vessel characteristics vulnerable to security threats (size, nu

Identify vessel characteristics vulnerable to security threats (size, number of crew, visibility of engineering spaces, cargo type, port call frequency)

3

Identify potential threat actors (stowaways from ports with high unautho

Identify potential threat actors (stowaways from ports with high unauthorized departure, piracy threats in certain regions, criminal organizations targeting high-value cargo)

4

Identify potential consequences of security breaches (loss of vessel, lo

Identify potential consequences of security breaches (loss of vessel, loss of crew, environmental disaster if hazardous cargo is stolen, reputational damage)

5

Design Ship Security Plan

Design Ship Security Plan: Based on risk assessment, develop detailed security procedures:

6

Access Control

Access Control: Designate crew-only areas (bridge, engine room, crew quarters); visitor-restricted areas (cargo holds, fuel tanks). Install access control systems: key cards for authorized crew, visitor passes recorded in access log.

Where ISPS has the most impact

These are the areas where mature teams typically see measurable gains.

01

For HSSE Teams

ISPS Code is a maritime security standard distinct from occupational safety (STCW, SOLAS), but intersects with safety: security incidents can rapidly escalate to safety crises (pirate boarding, stowaway creating vessel overcrowding/stability issues, smuggled explosives). HSSE teams must ensure crew receives both STCW safety training and ISPS security training, and understands that security vigilance is part of safe operations. Additionally, HSSE teams investigate security incidents (stowaways, theft, smuggling attempts) to understand how control gaps developed and improve procedures.

02

For IT & CIOs

ISPS Code compliance involves digital systems: access control systems (electronic locks and ID readers), CCTV systems with recorded footage, electronic incident reporting, cargo manifest systems. Digital systems must be secure and audit-worthy: access logs must be tamper-proof (showing who accessed which areas at what time), CCTV footage must be retrievable and preserved, incident reports must document details accurately. Additionally, cybersecurity becomes critical: if vessel navigation systems are hacked, security is undermined. ISPS compliance increasingly includes cybersecurity standards protecting vessel IT systems.

Deep Dive

ISPS explained for operations, HSSE, and leadership teams

A concise reference focused on implementation, governance, and day-to-day execution.

What Is ISPS Code?

ISPS Code (International Ship and Port Facility Security Code) is an international maritime security framework adopted by the International Maritime Organization (IMO) in 2002 in response to maritime terrorism threats (particularly post-September 11, 2001). ISPS Code establishes minimum security standards for ships and port facilities engaged in international trade, aiming to prevent unauthorized access, smuggling, hijacking, and other maritime security threats.

Core Components:

1. Risk Assessment & Threat Identification Every vessel and port facility must conduct a security risk assessment identifying potential security threats:

  • Access control threats: Unauthorized persons boarding the vessel
  • Sabotage/tampering threats: Unauthorized modification of vessel systems or cargo
  • Smuggling threats: Concealment of contraband (drugs, weapons, explosives) aboard
  • Stowaway threats: Unauthorized personnel hiding aboard
  • Cyber security threats: Unauthorized access to vessel navigation/engineering systems

2. Ship Security Plan Each vessel must develop a written Ship Security Plan (SSP) specifying:

  • Security measures: Physical barriers (fencing, locks), access control systems (ID badges, turnstiles), CCTV cameras, lighting
  • Crew training: Security awareness training for all crew, specialized training for security personnel
  • Drills & exercises: Quarterly security drills simulating security threats; crew participates in evacuation, hostile boarding response, etc.
  • Incident response: Procedures if security threat occurs (report to authorities, isolate threat area, evacuate if necessary)
  • Interface with port facilities: Coordination with port security, reporting of security incidents
  • Port state control compliance: Procedures for boarding by port authorities, crew cooperation with inspections

3. Crew Security Training All crew must receive ISPS security awareness training before the vessel operates:

  • Security awareness: Recognition of security threats, understanding responsibilities
  • Access control procedures: Enforcement of crew/visitor ID requirements; prevention of unauthorized boarding
  • Threat response: What to do if an unauthorized person attempts to board or if suspicious cargo is discovered

4. Port Facility Security Coordination Port facilities (container terminals, bulk handling facilities, passenger terminals) must also implement ISPS security measures:

  • Access control: Only authorized personnel on dock areas; visitor escorts required
  • Cargo security: Sealed containers inspected for tampering; chain-of-custody procedures
  • Information security: Cargo manifests and vessel information protected from public access
  • Incident response: Port authority procedures if security threat is detected

Regulatory Standard / Framework:

  • ISPS Code: International Ship and Port Facility Security Code (adopted IMO 2002, effective 2004)
  • SOLAS Convention (Chapter XI-2): Integrates ISPS Code requirements into SOLAS maritime safety convention
  • Flag State Responsibility: Each flag state is responsible for verifying vessels flying its flag comply with ISPS Code
  • Port State Control: Port authorities inspect vessels for ISPS Code compliance; non-compliant vessels may be detained or restricted from port entry
  • EU Regulation 725/2004: EU-level implementation of ISPS Code; applies to vessels in EU ports

Vessel Applicability:

  • All commercial vessels engaged in international voyages (crossing international borders)
  • Passenger ships (all sizes) engaged in international voyages
  • Cargo vessels 500+ gross tonnage engaged in international voyages
  • Dredging vessels engaged in international operations or making international port calls
  • Exemptions: Vessels operating purely domestically (never crossing international boundaries) may be exempted depending on flag state; fishing vessels; military/government vessels; pleasure yachts

How ISPS Code Works

ISPS Compliance Process

Phase 1: Ship Security Plan Development

  1. Security Risk Assessment: The vessel's master and security officer (designated by vessel owner) conduct a threat assessment:
  • Identify vessel characteristics vulnerable to security threats (size, number of crew, visibility of engineering spaces, cargo type, port call frequency)
  • Identify potential threat actors (stowaways from ports with high unauthorized departure, piracy threats in certain regions, criminal organizations targeting high-value cargo)
  • Identify potential consequences of security breaches (loss of vessel, loss of crew, environmental disaster if hazardous cargo is stolen, reputational damage)
  1. Design Ship Security Plan: Based on risk assessment, develop detailed security procedures:
  • Access Control: Designate crew-only areas (bridge, engine room, crew quarters); visitor-restricted areas (cargo holds, fuel tanks). Install access control systems: key cards for authorized crew, visitor passes recorded in access log.
  • Physical Security: Install security measures proportionate to risk: CCTV cameras monitoring deck areas, perimeter fencing (for shore-side operations), lighting in vulnerable areas, secure storage for hazardous equipment/tools.
  • Crew Responsibilities: Assign security duties to crew: security officer monitors access control, bosun inspects hull/superstructure daily, engineer monitors fuel/freshwater tank integrity, deck crew maintains watch for stowaways/suspicious activity.
  • Cargo Security: If carrying hazardous or high-value cargo, implement procedures: manifest cross-check (verify cargo loaded matches documentation), seal integrity (containers sealed with tamper-evident seals), restricted access to cargo areas.
  • Port Interface: Procedures for coordinating with port authority, receiving customs/immigration/police inspections, reporting security incidents.
  1. Crew Training Plan: Specify training all crew must complete before vessel departs:
  • ISPS Security Awareness Training (4-8 hours): Covers threat recognition, access control procedures, evacuation procedures, incident reporting
  • Specialized training for security-critical roles (security officer: 40 hours; captain: maritime security management course)
  1. Drills & Exercises: Schedule quarterly security drills. Example drill scenario: "Unauthorized stowaway discovered in empty cargo hold during routine inspection. Respond per procedures: isolate stowaway area, notify master, prepare for handover to port authority."

Phase 2: Implementation & Crew Training

  1. Crew Training & Certification: Before the vessel operates:
  • All crew receive ISPS Awareness training; training is documented with crew signatures confirming understanding
  • Specialized crew (security officer, master) complete advanced training; certificates issued upon completion
  • Training records maintained aboard and provided to port state control upon inspection
  1. Security Equipment Deployment: Install and maintain security equipment:
  • Access control systems (ID card readers, electronic locks)
  • CCTV systems with recorded footage retained for minimum 30 days
  • Lighting in potentially vulnerable areas
  • Communication systems (radios, alarms) for emergency notification
  1. Operational Procedures: Implement daily security routines:
  • Morning briefing: master reviews security situation, confirms all crew understand their security responsibilities
  • Daily inspection: crew inspect hull for damage/stowaways, verify locks/seals on restricted areas, check CCTV systems functioning
  • Port operations: when vessel is in port, designated crew maintain watch preventing unauthorized boarding; cargo areas secured; access logging maintained

Phase 3: Compliance Verification & Port State Control

  1. International Ship Security Certificate (ISSC): Vessel must obtain ISSC from flag state confirming compliance with ISPS Code:
  • Flag state conducts initial audit of Ship Security Plan and crew training
  • If compliant, flag state issues ISSC valid for 5 years (renewable)
  • ISSC is carried aboard vessel; copy provided to port authorities when requesting port entry
  1. Port State Control Inspections: When vessel enters port, port authority may inspect for ISPS compliance:
  • Review Ship Security Plan for adequacy
  • Verify all crew hold current ISPS training certificates
  • Inspect physical security measures (locks, CCTV, lighting)
  • Review access logs and cargo manifests
  • Interview crew on security procedures
  • If non-conformance found, vessel may be detained pending corrective action
  1. Incident Response: If security incident occurs (stowaway discovered, suspicious cargo found, unauthorized boarding attempted):
  • Master notifies port authority immediately
  • Preserve evidence (record details of incident, restrict access to incident area, photograph evidence)
  • Hand over to law enforcement if criminal activity is suspected
  • Complete incident report documenting what happened, response taken, lessons learned
  • Update Ship Security Plan if incident reveals control gaps

Real-World Example: Container Vessel in European Waters

A container vessel (Panama flag, operated by Maersk) carrying valuable cargo arrives at Rotterdam port:

  1. Pre-Departure: Before leaving previous port (Shanghai), master confirms all crew completed ISPS Awareness training within past 2 years. Vessel's ISSC is current and displayed. Ship Security Plan is reviewed and updated if necessary.
  2. Transit: During 20-day voyage, security routines are maintained: daily crew briefing on security vigilance, perimeter inspection for stowaways (especially containers loaded in Shanghai with potential for clandestine boarders), cargo seal verification confirming containers have not been tampered with.
  3. Port Approach: Vessel reports to Rotterdam Port Authority requesting entry. Vessel provides ISSC and copy of Ship Security Plan. Port authority reviews documents; plan is deemed adequate, permission to enter is granted.
  4. Port State Control Inspection: Upon arrival, Dutch port state control authority boards vessel. Inspector verifies:
  • ISSC is authentic and current ✓
  • All crew hold ISPS training certificates (interviews crew on security procedures) ✓
  • Physical security measures are in place (observes CCTV, locked access doors, access logs) ✓
  • Cargo manifests match physical cargo in holds ✓
  • No security incidents or near-misses during transit ✓

Inspection is passed without deficiency; vessel is cleared for cargo operations.

  1. Port Operations: While cargo is loaded/unloaded, vessel security remains active: crew monitor access to vessel, cargo areas are supervised, CCTV records all activity. Port workers are provided escort if they need to access crew areas.
  2. Departure: Master confirms security status (no unauthorized personnel aboard, cargo seals intact, CCTV systems functioning, fuel/freshwater tanks inspected). Vessel departs port with ISPS compliance maintained.

Why ISPS Matters: Operational impact

For HSSE Teams

ISPS Code is a maritime security standard distinct from occupational safety (STCW, SOLAS), but intersects with safety: security incidents can rapidly escalate to safety crises (pirate boarding, stowaway creating vessel overcrowding/stability issues, smuggled explosives). HSSE teams must ensure crew receives both STCW safety training and ISPS security training, and understands that security vigilance is part of safe operations. Additionally, HSSE teams investigate security incidents (stowaways, theft, smuggling attempts) to understand how control gaps developed and improve procedures.

For IT & CIOs

ISPS Code compliance involves digital systems: access control systems (electronic locks and ID readers), CCTV systems with recorded footage, electronic incident reporting, cargo manifest systems. Digital systems must be secure and audit-worthy: access logs must be tamper-proof (showing who accessed which areas at what time), CCTV footage must be retrievable and preserved, incident reports must document details accurately. Additionally, cybersecurity becomes critical: if vessel navigation systems are hacked, security is undermined. ISPS compliance increasingly includes cybersecurity standards protecting vessel IT systems.

Industry context

According to IMO and International Maritime Bureau (IMB) data, maritime piracy and armed robbery incidents have declined significantly since ISPS Code implementation in 2004. Approximately 60-100 maritime security incidents (piracy, armed robbery, stowaways) are reported annually globally, down from 400+ annually pre-ISPS. Additionally, port security incidents (smuggling, unauthorized access) declined approximately 50% in the first 5 years post-ISPS implementation. The declining trend reflects both ISPS Code effectiveness and decreased piracy due to naval interventions in high-risk regions (Gulf of Aden). Non-compliance penalties are significant: vessels detained for ISPS violations incur demurrage costs (€10,000-€50,000+ per day) and reputational damage with clients.

Implementing & Monitoring ISPS Code: From Manual to Digital

Traditionally, ISPS Code compliance was managed through paper-based processes: Ship Security Plan printed and maintained aboard vessel, crew training records filed in paper folders, access logs written in logbooks, CCTV footage recorded on tape and stored in vessel's secure area.

The transition to digital ISPS management involves:

Digital Ship Security Plan Management: Cloud-based systems (accessible on-site via tablets/secure networks) maintain current Ship Security Plan with version control. When plan is updated, all stakeholders (crew, flag state, port authorities) receive notification of changes. This ensures everyone is working from the current plan, not an outdated version.

Crew Training & Certification Tracking: Digital systems maintain records of all crew ISPS training completion, certification expiration dates, and retraining schedules. Before vessel departs port, system confirms all crew have current certifications; crew with expired certifications cannot be assigned to vessel until training is renewed.

Access Control Systems & Logging: Digital access control systems (electronic ID card readers, electronic locks) automatically log all access events: "2025-02-23 08:15, Crew ID 045 accessed Engine Room, authorized." These logs are maintained digitally with audit trails, enabling rapid incident investigation: if unauthorized access to fuel tank is suspected, access logs show exactly who accessed that area and when.

CCTV Integration: Digital CCTV systems (high-definition, encrypted storage) maintain recorded footage for 30+ days. Systems enable rapid search (e.g., "Show all footage of deck area between 23:00-06:00 during Shanghai port stay") assisting incident investigation.

Incident Reporting & Investigation: Digital incident reporting systems enable crew to report security concerns or incidents immediately, triggering alert to master. Formal incident investigation forms are completed, findings documented, and lessons learned are shared with fleet.

Best Practices for ISPS Code

  • Risk-Based Security Planning: Rather than implementing one-size-fits-all security measures, tailor Ship Security Plan to vessel's actual risk profile. A container vessel operating in high-piracy waters (Gulf of Aden, Gulf of Guinea) requires different security measures than a bulk carrier operating in Northern European waters. A security assessment should identify the highest-probability threats to that specific vessel and prioritize controls accordingly. This ensures security measures are effective without creating unnecessary operational burden.
  • Crew Security Culture & Empowerment: ISPS Code effectiveness depends on crew vigilance. Train crew not just on security procedures but on the "why"-why stowaway detection is critical (safety risk, liability, delay), why cargo security matters (financial loss, client trust, potential for smuggled contraband). Encourage crew to report security concerns without fear of retaliation. A crew member observing unusual activity should feel empowered to report it without concern they'll be dismissed or punished for false alarm.
  • Regular Security Drills & Scenario Exercises: Conduct quarterly security drills with realistic scenarios. Too many vessels conduct drills that are perfunctory ("everyone gathers here for roll call"); instead, create realistic scenarios: "Intruder found in ballast tank-how do you safely remove them?" or "CCTV detects unauthorized container being moved off the vessel-response?" Realistic drills reveal actual procedure gaps and ensure crew is prepared to respond under stress.

Frequently asked questions

Rarely, but sometimes security and safety measures create tension. Example: Securing a stowaway-prone area with restricted access may limit crew's rapid evacuation route in fire emergency. Best practice is to design Ship Security Plan in coordination with SOLAS safety requirements, ensuring security and safety measures are complementary rather than conflicting. The master must balance both security and safety obligations.

Operationalize ISPS at workforce scale

Dockt helps teams move from manual credential tracking to proactive, audit-ready competence management.