(see Sections 1 to 5 of Annex 3 of SDM Circular 24/2015)
1. Language of the Ship Security Plan (ISPS Code, Part A, 9.4)
The Ship Security Plan (SSP) should be written in Greek or English and to any other languages designated by the Company as the command and the working languages on-board their ship.
2. Copies of the approved SSP and of any subsequent amendments thereto
Τhe DMS requires each Company to have in the office from which the ship is operated at least one copy of the approved SSP (including any subsequently approved amendments thereto) relating to that ship. This copy of the SSP (and any amendments thereto) shall be protected from unauthorised access or disclosure.
3. SSP as part of the Safety Management System
In the interest of the national security of the Republic of Cyprus as well as of the other Contracting Governments and the need to protect the SSP from unauthorised access and disclosure, SSPs must NOT form or be part of safety management systems.
4. Interface with ships or ports that are not subject to the requirements of the ISPS Code and Regulation (EC) 725/2004
The SSP should include provisions to ensure that security is not compromised by any ship to port or ship to ship activity, with a port or a ship which are not subject to the provisions of the ISPS Code and Art. 3.8 of the Regulation (EC) 725/2004.
5. Changes to SSP (ISPS Code, Part A, 9.5)
Changes to a SSP must be applied only after these have been approved by the RSO that has approved the SSP and has issued the ship´s ISSC.
All items described under the provisions of the ISPS Code, Part A/9.4 must be firstly approved by the RSO of the ship prior to their implementation with the only exemption being the contact details of the CSO and alternate CSO (ISPS Code, Part A/ 9.4.14) provided that the approved SSP contains in the main text the duties of the CSO and his/her alternates (ISPS Code Part A/12) and that the contact details are attached to the SSP as an annex.
The SDM will only accept the above mentioned arrangement provided that the EN04F01 form is submitted to the DMS prior to the implementation of the changes.
If changes of the CSO / alternate CSO details are not communicated to DMS in time and / or the DMS is unable to reach the CSO and or alternate CSO, these cases will be treated as non-compliances with the provisions of this Circular and will result to additional investigation by the SDM (i.e. additional ship board verification may be requested to be carried out by the RSO or additional shore based verification may be
requested to be conducted by either the DMS or the RO issuing the Document of Compliance of the company).
The following cases are considered significant, necessitating changes to the SSP plans, which must be submitted for approval prior to their implementation:
When a ship has undergone a major conversion as defined by SOLAS 74 as amended.
When any or all of the restricted areas have been changed.
When new surveillance equipment and related equipment is installed on board for monitoring the security of the ship and these have not been included in the approved SSP.
When procedures related to the SSP and actions taken when the ship is on security level 1, 2 and 3 are modified.
When a ship is going to trade in areas that have not been covered by the ship security assessment.