Regional security reporting, CSO contact and SSAS readiness
What is being checked
The inspector is checking whether the Master and officers know the applicable regional security-reporting arrangements, can contact the Company Security Officer at all times and can demonstrate that the Ship Security Alert System is maintained and tested as required. Verification must not disclose protected SSAS activation details or locations.
Ready onboard
0/8 completePractice questions
Answer aloud, then open the preparation point.
1Which regional security-reporting arrangement applies to the current voyage?
Identify the current regional reporting or information-sharing arrangement from controlled company guidance and the voyage-specific risk assessment.
2What reports are required, and how do you confirm that they were received?
Show the applicable initial, position, final or incident reports and the permitted evidence of transmission and acknowledgement.
3Where can the bridge team find the current 24-hour CSO contact details?
Use the approved posted or controlled contact information. Responsible officers should know how to reach the CSO at all times.
4What approvals and notifications are required before an SSAS test?
Follow company, flag and equipment procedures, including advance coordination with all required recipients so the test is not treated as a real alert.
5Show the permitted evidence that SSAS tests and maintenance are current without revealing protected details.
Use test, maintenance and defect-closure records. Do not reveal activation points, activation method, transmission details or protected SSP content.
6What is the reporting and escalation route following a security incident or significant threat change?
Follow the company security communication chain, contact the CSO and applicable reporting centre, preserve records and update the voyage controls as required.
Where an observation may arise
Current 24-hour CSO contact details are unavailable, outdated or not known to responsible officers.
Applicable regional reporting requirements are not understood or have not been followed.
Required security reports or acknowledgements cannot be demonstrated.
SSAS testing is overdue, inadequately recorded or not conducted under the required notification procedure.
A defect, test failure or maintenance requirement has not been properly reported and closed.
The Master or officers cannot explain the reporting and escalation chain.
Protected SSAS or SSP information is displayed or handled inappropriately.
Master's practical note
Ask the responsible officer to trace one recent voyage report from the requirement to the sent message and acknowledgement, then verify the SSAS test record and notification chain. Never ask for a live activation or allow inspection preparation to expose the SSAS location or activation method.
Equipment boundary and references
Equipment boundary: SSAS design, activation, transmission path, reset and test arrangements vary and are security-sensitive. The public guide must not identify activation points or provide a testing sequence. Use flag, company and manufacturer instructions for the fitted system.
References
- OCIMF SIRE 2.0 Question Library Part 1, Version 1.0, Question 7.3.1
- SOLAS Regulation XI-2/6, Ship Security Alert System
- IMO guidance on SSAS testing and message priority
- BMP Maritime Security, current reporting guidance
- Company security procedures and approved Ship Security Plan
Last reviewed: 2026-08-25
