ISPS Certification (International Ship Security Certificate)
The ISSC records verification of ship security within SOLAS XI-2 scope; validity depends on timely verifications and endorsements.
Operational Explanation
The ISSC connects certification with the security system actually implemented on the ship. Preparation links the approved plan, CSO and SSO responsibilities, completed activities and relevant evidence. The certificate must remain consistent with the ship and continued maintenance of that system, as well as verification dates.
A full certificate lasts no more than five years. Where only one intermediate verification is required and validity is five years, it falls between the second and third anniversaries and must be endorsed. Arrange renewal and required additional verifications with the flag or its authorized RSO.
| Document / evidence | How to use it |
|---|---|
| Certificate | Identity, authorised issuer, validity and verification endorsements. |
| Plan and responsibilities | Approved SSP, pertinent version and CSO/SSO responsibilities. |
| Implementation | Relevant training, drill/exercise, audit/review and finding follow-up evidence, protected from unauthorised access. |
Regulatory Reference
ISPS Code A/19 — ISSC; SOLAS XI-2; A.1206(34), PSC Procedures 2025.
For the link between plan, records, responsibilities and certification also read ISPS A/9–13 and A/19. The ISPS 2003 text published by the Turkish Administration supports the cited provisions; apply current flag provisions and instructions.
Scope of Application
Passenger ships including high-speed craft; cargo ships including high-speed craft of at least 500 GT; and MODUs, engaged on international voyages. Check national extensions separately.
Procedure / How to Complete It
- Check category, voyages, authorized issuer, expiry and ISSC endorsements.
- Arrange verifications with the flag/RSO and maintain implementation of the approved SSP.
- Make the SSO and relevant training and exercise evidence available, respecting security-document confidentiality.
- For an invalid or expired ISSC, promptly involve the Company and competent authorities.
For each agreed verification, connect its type with required evidence, findings and completed actions. Afterwards check the report and the certificate/endorsement actually issued. CSO and SSO organise access to pertinent documentation under confidentiality rules; preparation does not require disclosure of SSP contents.
Practical Example
A completed intermediate verification also requires the endorsement: a booking or report alone does not establish certificate validity.
The file records verification date, result and actual endorsement, making any outstanding follow-up visible. Security activity records remain protected under the plan and applicable instructions.
What Typically Goes Wrong
Confusing expiry with the intermediate window, or treating detention as automatic for every ISSC problem.
Common Mistakes Mistake Library
| Mistake | Consequence | How to avoid it |
|---|---|---|
| Plan the intermediate verification from final expiry alone | The required window or endorsement may be missed and the certificate may lose validity. | Read ISSC dates and endorsements and arrange verification and endorsement with flag/RSO within the pertinent limits. |
| Treat the report as a replacement for endorsement | The file may show completed verification without the required certificate endorsement. | Check the certificate actually endorsed and resolve any missing entry with the issuer. |
| Treat every ISSC problem as automatic detention | Effects or actions not decided by the competent authority may be attributed to the finding. | Report the problem and follow the authorised authority’s assessment under SOLAS XI-2/9. |
What the PSCO Checks
Operational Tips
- Distinguish full and interim certificates.
- Record deadlines and actions agreed with the RSO.
Preparation checklist
- Scope and ISSC checked
- Intermediate, renewal and endorsements checked
- SSO and relevant documentation available
FAQ
Related Topics
Certified substantive revision: 13 October 2026 · page fingerprint 79827fa6f22e