International Ship and Port Facility Security (ISPS) Code: CIRCULAR CAM 01/2013
International Ship and Port Facility Security (ISPS) Code: CIRCULAR CAM 01/2013
The present circular replaces and withdraws circular CAM 05/2006 dated 12th September
2006.
O/Ref : AH/101648
The ISPS Code entered into effect internationally on the 1 of July 2004 and consists of Part A
(mandatory provisions) and Part B (recommended provisions).
The purpose of the Code is to provide a standardized, consistent framework for evaluating
risk, enabling governments to offset changes in threat with changes in vulnerability for ships
and port facilities.
The term "company" used in this circular means the owner of the ship or any other
organization or person such as the manager or the bareboat charterer, who has assumed the
responsibility for operation of the ship from the owner of the ship and who, on assuming such
responsibility, has agreed to take over all the duties and responsibilities imposed by the
International Safety Management Code (SOLAS 74 Regulation IX/1).
Regulation (EC) N° 725/2004 of the European Parliament and of the Council of 31 March
2004 on enhancing ship and port facility security is also applicable to all vessels flying the
Luxembourg flag. This regulation harmonizes the implementation of the ISPS Code within
Member States and renders some elements of Part B of the Code mandatory.
It is therefore reminded that the following paragraphs of Part B of the ISPS Code are
mandatory for ships flying the Luxembourg flag:
3. Generalities
The following classification societies have been authorised to act as a RSO on behalf of
Luxembourg: ABS, BV, GL-DNV, LRS, NKK, RINA.
The National Focal Point for security matters is the Luxembourg Maritime Administration:
In regard to Regulation 6.2.1. of SOLAS, Chapter XI-2, the ships security alert system,
when activated by a Luxembourg registered vessel, shall initiate and transmit the ship-
to-shore security alert to the Company Security Officer (CSO).
After having verified that the security alert is related to a real threat, the CSO must
immediately forward the SSAS alert to:
Email: [email protected]
However, if at the time of the alert, the CSO does not have Internet access, the above
mentioned information can be transmitted by phone to the CIN: +352 4997 2346.
As this procedure differs from the procedure detailed in the hereby cancelled
Circular CAM 05/2006, Companies should make sure that the SSAS is properly and
accordingly reprogrammed as soon as possible, but not later than 1 March 2014. After 1
March 2014, messages sent by vessels directly to CIN will be ignored.
Additionally, CSOs are requested to transmit to CAM, at least once a year, a report on the
results of all SSAS tests messages sent by the Luxembourg flagged ships in their fleet.
Companies shall provide their ships with a mean of detecting and cancelling false security
alert system activations. If nevertheless a false alert is transmitted to the Luxembourg
authorities, it will have to be lifted by the Company by contacting without delay the CAM (by
phone) and the CIN (by email).
Until further notice, security level to be maintained on all ships flying the flag of the
Grand-Duchy of Luxembourg is SECURITY LEVEL 1.
The competent Coastal State Authorities or the Port Security Officers of the ports that the ship
is visiting may upgrade the security level to a higher state for Luxembourg ships. The
company shall immediately forward such changes to CAM by fax or Email.
5. ISPS Code
Companies may choose from any of the RSOs listed in point 3.1 of the present document to
conduct SSP review and approval, verification audit, issuance of the ISSC and SSP
amendment approval, provided that the selected RSO has not provided consultative services
with regard to preparation of the SSA. It is preferable to keep the same RSO performing the
entire certification process.
The Ship Security Plan shall clearly state that the SSO must complete a DoS as described in
the ISPS Code, Part A, paragraph 5.
For all its ships, every company shall develop, implement, and maintain a functional SSP that
is compliant with SOLAS Chapter XI-2 and the ISPS Code.
The company shall ensure that the SSP contains a clear statement emphasizing the Master’s
authority and that the Master has overriding authority and responsibility to make decisions
with respect to the safety and security of the ship and to request assistance of the company or
of any Contracting Government as may be necessary. The Master of the ship has the ultimate
responsibility for both safety and security aboard the ship.
The company shall ensure that the Master has available on board, at all times, the following
information required by SOLAS Chapter XI-2, Regulation 5, to provide to Coastal State
authorities:
- contact details for the person or entity responsible for appointing the members of the
crew or other persons currently employed or engaged on board the ship in any
capacity on the business of that ship;
- contact details for the person or entity responsible for deciding the employment of that
ship;
- in cases where the ship is employed under the terms of charter party(ies), contact
details of such charter party(ies).
The company shall ensure that the CSO, the Master and the SSO are given the necessary
support to fulfil their duties and responsibilities in accordance with Chapter XI-2, Part A and
the relevant provisions of Part B of the ISPS Code.
The purpose of a SSA is to identify and analyze the security risks for a given type of ship in a
trading area. The results of the security assessment provide the basis for measures which are
essential to develop, implement, maintain and update the ship security plan. This assessment
shall take into account the additional workload such measures will rise up.
The CSO is responsible for satisfactory development of the SSA whether prepared by the
company itself or a contracted organization. The SSA serves as a tool for development of a
realistic SSP. It takes into account the unique operating environment of each individual ship,
the ship’s compliment and duties, structural configuration and security enhancements.
The ISPS Code does not permit the SSA to be performed by the same RSO chosen by the
company to perform the Plan review, approval, verification and certification.
Accordingly, the CSO shall ensure that the SSA addresses at least those elements for an SSA
as detailed in Part B, Section 8, of the Code. Due to the potentially sensitive operational and
security information contained therein, the SSA shall be protected from unauthorized
disclosure.
The SSA shall be sent, together with the SSP, to the RSO by a predetermined method to
prevent unauthorized disclosure. The RSO shall review the SSA to ensure that each element
required by the Code is satisfactorily addressed and is used as a reference for the SSP.
The CSO is responsible for satisfactory development of the SSP whether prepared by the
company itself or a contracted organization. The SSP is developed from the information
compiled in the SSA. It ensures application onboard the ship of measures designed to protect
persons onboard, the cargo, cargo transport units, ship’s stores or the ship from the risks of a
security violation. Because of the potentially sensitive operational information contained
therein, the SSP shall be protected from unauthorized disclosure.
The CSO shall ensure that the SSP addresses in detail those elements for an SSP as detailed in
Part B, Section 9, of the Code, especially those vulnerabilities found during the assessment
with a description of countermeasures that address those vulnerabilities. At completion of the
SSP, and approval by the company, the CSO shall send the SSP, together with the SSA, for
approval by the RSO by a predetermined method to prevent unauthorized disclosure.
The RSO shall review the SSP to ensure that each element required by Part A and the relevant
provisions of Part B of the Code, as well as all the vulnerabilities referenced in the SSA, are
satisfactorily addressed. CAM recommends that the plan review process has to take place in
the company, if possible, with the direct interaction of the CSO and the RSO to preclude the
need to transport this sensitive material by means out of their control.
Identification of the locations where the ship security alert system activation points are
provided, and the procedures, instructions and guidance on the use of the ship security alert
system, including the testing, activation, deactivation and resetting, and to limit false alerts,
may, in order to avoid compromising in any way the objective of the system, be kept
elsewhere in a separate document known only to the Master, the SSO and other management
level officers on board.
After certification under Part A, Section 19.1.1 has been completed, no changes shall be made
to the security system and any associated security equipment or approved security plan
without the sanction of the acting RSO. However, in accordance with the ISPS Code, part A,
section 9.5, minor changes to the contact data or to the onboard personal will not be required
to be approved beforehand by CAM or by the acting RSO. These minor changes will
however, in every case, have to be notified to CAM and to the acting RSO.
5.6 Records
Records of activities detailed in Part A, Section 10.1 shall be addressed in the SSP and kept
onboard for a minimum period as specified below. The records shall be kept in the working
language of the ship. If the working language of the ship is not English or French, then a
translation into one of these languages shall be included.
Such records shall be maintained on board for a period of three (3) years after the events and
thereafter may be removed to the company for safekeeping and review by the RSO during
periodical and renewal audits.
Records required to be kept by SOLAS Chapter XI-2, Regulation 9.2.1, including DoS, for a
period covering at least the last 10 calls at port facilities shall be maintained on board. The
said period shall not be less then one month.
Records may be kept in any format but must be protected from unauthorized access or
disclosure and loss. The records shall be in a form to be readily available to Port State control
officials if so requested.
The CSO is the person designated by the company to perform the duties and responsibilities
of the CSO as detailed in Part A, Section 11 and the relevant provisions of Part B, Sections 8,
9 and 13 of the Code. The CSO shall have the knowledge of, and receive training in, some or
all of the elements of Part B, Section 13.1 of the Code.
The SSO is the person designated by the company to perform the duties and responsibilities
detailed in Part A, Section 12 and Part B, Sections 8, 9 and 13. The SSO shall have completed
a training course regarding the requirements and recommendations of the ISPS Code.
Company and shipboard personnel having specific security duties must have sufficient
knowledge, ability and resources to perform their assigned duties per Part B, Section 13.1,
13.2, and 13.3 of the ISPS Code.
All other shipboard personnel must have sufficient knowledge of and be familiar with
relevant provisions of the SSP including the elements described in Part B, Section 13.4 of the
ISPS Code. Regulation VI/6 of the STCW Convention, as amended, as well as Paragraphs 1-4
of Section A-VI/6 of the STCW Code, as amended, are also applicable.
Carriage and use of weapons by seafarers on board are not recommended. However, if the
company decides to have weapons on board it should contact the Luxembourg Ministry of
Justice for the purpose of necessary authorisations.
The SSP shall address drill and training frequency. Drills shall be conducted at least every
three (3) months. In cases where more than 25% of the ship’s personnel have changed, at any
one time, with personnel previously not participating in any drill on that ship within the last
three (3) months, a drill shall be conducted within one (1) week of the change.
Records indicating type of drill or exercise, SSP element(s) covered, and attendance shall be
maintained by the SSO for a period of three (3) years. They may be kept in any format but
must be protected from unauthorized access or disclosure. The records shall be in a form to be
readily available to Port State Control officials if so requested.
Various types of exercises, which may include participation of the CSO, PSO, relevant
authorities of contracting governments as well as SSO, if available, should be carried out at
least once each calendar year with no more than 18 months between the exercises. These
exercises should test communications, coordination, resources availability and response.
These exercises may be:
Part B, Regulation 9.15 of the ISPS Code refers to the frequency of searches at security level
1. It has been decided that as Part B of the Code is not made mandatory, the intervals for
search of boarding persons will be left at the discretion of the company until stricter
requirements are enforced.
This circular should be of interest to shipowners, managers, masters and officers. Accredited
shipping managers are kindly requested to make sure that this circular is properly distributed
to the respective staffs or companies intervening in the management of the ships.