Maritime Security Policy ISPS SOLAS

8/12/2019 Maritime Security Policy ISPS SOLAS

1/52

1

MARITIME SECURITY

REGULATIONS

SOLAS AND ISPS CODE


2/52

2

BACKGROUND


3/52


4/52

4

AMENDMENTS TO

SOLAS


5/52

5

ACCELERATED

AIS IMPLEMENTATIONThe existing SOLAS Reg. V/19.2.4

(effective 1st July 2002) requires AIS

installation on new and existing ships.The applicability date for existing ships on

international voyages, is spread over a

period from 1 July 2003 to 1 July 2007depending on ship type and size.


6/52

6

ENHANCED SECURITY

REGULATIONS IN SOLAS

Existing SOLAS Chapter XI Special

Measures to Enhance Maritime Safetyrenumbered as XI-1; with amendments

to Reg. 3 Ship identification number

and addition of a new Reg. 5Continuoussynopsis record.


7/52

7

Chapter (XI re-numbered)

XI/1Reg. 3 amendment Ship identification numberto be marked permanently (on existing ships at

1st scheduled dry-dock after 1 July 2004) in a

visible and in an easily accessible place.

New Reg. 5 All ships to be issued with a

continuous synopsis record intended to provide

an on-board record of the history of the ship.On existing ships the record shall provide

history, at least, as from 1 July 2004.


8/52


9/52

9

NEW CHAPTER XI/2

The new Chapter XI-2 titled Special

Measures to Enhance Maritime SecurityHas 13 regulations on security related

requirements for ships and ports. Refers

to the ISPS Code Parts A and B


10/52

10

3. OBLIGATIONS OF CONTRACTING

GOVERNMENTS WITH RESPECT TO

SECURITY

ADMs shall set security levels and ensurethat information on security levels is

provided to ships under their flag.CGs shall set security levels and ensure

that information on security levels isprovided to port facilities within theirterritory, and to ships prior to entering aport or whilst in a port within theirterritory.


11/52

11

4. REQUIREMENTS FOR COMPANIES AND

SHIPS

Companies and ships :

Compliance with relevant parts of this chapter

and ISPS Code Part AGuidance in ISPS Code Part B to be taken into

account

Ships :Compliance to be verified and certified as

provided for in ISPS Code Part A.


12/52


13/52

13

6. SHIP SECURITY ALERT SYSTEM

Shall initiate & transmit alert to a competentauthority designated by ADM

Shall identify ship, its location and indicate that

shipssecurity is under threatShall not send the alert to any other ship nor raise

alarm on board

Shall continue the alert until deactivated or resetHave activation possible from bridge & at least

one other location


14/52

14

7. THREATS TO SHIPS

CGs shall, for ships operating in or

having communicated an intention to

enter their territorial sea :Ensure provision of security levelinformation

Provide a point of contact for ships torequest advice or assistance

report any security concerns about other

ships, movements or communications


15/52

15

7. THREATS TO SHIPS

Where a risk of attack has beenidentified, the CGs shall advise the

ships concerned and theiradministrations of

Current security level

Security measures that the coastalstate has decided to put in place andthose that the ships concerned should

put in place.


16/52


17/52

17

9. CONTROL AND COMPLIANCE MEASURES

Controls for ships in a port of another CG :

Such ships are subject to control by

officers duly authorized by that CG, whomay be same as those carrying out

functions of Reg. I/19.Such controls shall be limited to verifying

availability on board, of a valid ISSC orInterim ISSC issued under provisions of

Part A of ISPS Code.


18/52

18


A valid certificate shall be accepted unless there are

clear grounds for believing that theship is not in

compliance with requirements of this chapter or

Part A of ISPS Code.

Where no valid cert is produced or when there are

such clear grounds, the officers duly authorized

may impose control measures. Such measures mustbe proportionate, taking into account guidance in

Part B of ISPS Code.


19/52

19


Possible control measures :Inspection of the ship

Delaying or detention of the ship

Restrictions of operations including

movement within port

Expulsion from port

Additionally or alternatively, other lesseradministrative or corrective measures.


20/52


21/52


22/52


23/52

23

11. ALTERNATIVE SECURITY AGREEMENTS

CGs may conclude in writing, bilateral or multilateral

agreements with other CGs on alternative security

arrangements covering short international voyages

on fixed routes between port facilities within theirterritories.

Such agreements shall not compromise the level of

security of other ships or of port facilities not

covered by the agreement.Any ship covered by such an agreement shall not

conduct any ship-to-ship activities with any ship

not covered by the agreement.


24/52

24

12. EQUIVALENT SECURITY ARRANGEMENTS

Other security measures equivalent to and at least aseffective as those prescribed in this chapter or inPart A of ISPS Code may be allowed :

By an Administration on a particular ship or agroup of ships entitled to fly its flagBy a CG in a particular port facility or a group of

port facilities located within its territory, otherthan those covered by an agreement concludedunder Reg. 11

The Administration or the CG, as applicable, shallcommunicate to IMO particulars of any suchequivalent measures allowed.


25/52


26/52

26

13. COMMUNICATION OF INFORMATION

1.Such information shall include names

and contact details of :

the national authority/authorities responsiblefor ship and port facility security; including

those designated to receive & act upon

ship-to-shore security alerts

those designated to receive and act upon any

communications from CGs exercising

control & compliance measures

.Continued..


27/52

27


1..Continued..Those designated to provide advice or

assistance to ships and to whom ships can

report any security concerns(The information against above 3 details is to bemade available for the information of Companiesand Ships)

any RSO authorized to act on their behalf andthe details of the specific responsibility andconditions of authority delegated to suchorganizations


28/52

28


2. CGs shall send, to IMO, list showing theapproved PFS plans for the PFs locatedwithin their territory together with the

location or locations covered by eachapproved PFS plan. CGs shall, at 5 yearintervals after 1 July 2004,

communicate to IMO a revised andupdated list. IMO shall make availablethe information to other CGs upon

request.


29/52

29


3. CGs shall communicate to IMO information

on agreements concluded under Regulation

11 and any amendments or ending of such

agreement.

4. Any CG which allows any equivalent

security arrangements with respect to a shipor with respect to a port facility shall

communicate to IMO particulars thereof.


30/52

30

ISPS CODEGENERAL


31/52

31

ISPS Code - Objectives

To establish An international framework

involving co-operation between CGs, Govt

agencies, local administrations and shipping

& port industries to detect security threats

and take preventive measures.

To establish respective roles and

responsibilities of CGs, Govt agencies, local

administrations and shipping & port

industries.


32/52

32

ISPS CodeFunctional requirements

Gathering & assessing information on security threats

& exchanging it with appropriate CGs.

Requiring maintenance of communication protocols

for ships & PFsPreventing unauthorized access to ships, PFs & their

restricted areas.

Preventing introduction of unauthorized weapons,incindiary devices or explosives to ships or PFs.


33/52

33

ISPS CodeFunctional requirements

Providing means for raising alarm in

reaction to security incidents.

Requiring ship & PF security plans basedupon security assessments.

Requiring training, drills and exercises to

ensure familiarity with security plansand procedures.


34/52

34

ISPS CodeResponsibilities of CGs

CGs have the overall responsibility for maritime

security regime in their areas of jurisdiction.

For port facilities, CGs will identify the

organization(s) or the administration(s),within the Contracting Government, as

designatedauthority.

Maritime Administrations would normallyhavethe responsibilities in respect of security of

ships under their flag.


35/52

35


CGs shall set security levels & provideguidance for protection from securityincidents.

Factors to be considered in setting levels :The degree that the threat information is credible

The degree that the threat information iscorroborated

The degree that the threat information is specificor imminent

The potential consequences of such a securityincident


36/52

36


Duties of CGs, under Chp XI-2 and ISPS CodePart A, that can not be delegated to RSO :

Setting of security level

Approving a PFS Assessment and/or a PFS Planand subsequent amendments

Determining which PFs require to designatePFSO

Exercising control & compliance measuresEstablishing the requirements for a Declaration ofSecurity


37/52

37

ISPS CodeDeclaration of security

Declaration of security :

CGs shall determine when it is required by

assessing the risk the ship/port interface or ship

to ship activity poses to people, property or theenvironment

A ship may request completion of DOS

To be completed by the master or the SSO on

behalf of ship AND PFSO or any other body

identified by CG on behalf of port facility


38/52

38

ISPS CODE

SHIP SECURITY

COMPANY RESPONSIBILITIES


39/52

39

COMPANY RESPONSIBILITIES -

OVERALL

Ensure that the Company and ships comply

with relevant requirements of SOLAS

Chapter XI-2 and of Part A of the ISPS

Code, taking into account the guidance givenin Part B of the ISPS Code.

Ensure that compliance by ships is verified and

certified as provided for in part A of ISPSCode.


40/52


41/52

41


SPECIFIC

Ensure availability with shipsMaster, at all times, of

following information (updated and kept current) :

Who is responsible for appointing the crew members or

others employed or engaged on the ship in any capacityon the business of that ship

Who is responsible for deciding employment of the ship

When ship is employed under the terms of charter

party(ies), who are the parties to such charter party(ies)


42/52

42


SPECIFIC

Establish in the ship security plan that the master hasthe overriding authority and responsibility :

To make decisions with respect to the security of theship

To request the assistance of the Company or of anyContracting Government as may be necessary

Ensure that CSO, the Master of the ship and SSO aregiven the necessary support to fulfill their duties

and responsibilities.


43/52


44/52

44

ISPS Code

Ship Security Assessment

CSO to ensure that SSA is carried out by persons

with appropriate skills to evaluate the security

of a ship

RSO may carry out SSA

SSA shall be documented, reviewed & retained

by the CompanySSA shall include an on-scene security survey

continued


45/52

45

ISPS Code

Ship Security Assessment

SSA shall include at least the identification of:

existing security measures, procedures and

operationsand evaluation of key shipboard operations

possible threats to such operations and thelikelihood of their occurrence, in order to

establish and prioritise security measuresidentification of weaknesses, including human

factors in the infrastructure, policies &procedures


46/52

46

ISPS CodeShip security plan

ADM to approve

RSO may prepare SSP for a specific ship

ADM may entrust review & approval of SSP or

its amendments to RSO ( Provided that RSOis not involved in either preparing the SSA orSSP or amendments)

Shall be available on board and protected fromunauthorized access or disclosure

Not subject to inspection under control &compliance measures


47/52

47

ISPS Code - Records

Records of following activities addressed inSSP shall be maintained on board :

Training, drills & exercises

Security threats, security incidents &breaches of security

Changes in security level

Communications relating to the directsecurity of the ship such as specific threatsto the ship or to port facilities the ship is ator has been

continued


48/52

48

ISPS Code - Records

continued

Internal audits & reviews of security activities

Periodic review of the SSA

Periodic review of the SSPImplementation of any amendments to the

plan

Maintenance, calibration and testing ofsecurity equipment, if any including testingof the ship security alert system


49/52

49

ISPS CodeCSO and SSO

CSO and SSO :

Company shall designate a person or persons as

CSO and clearly identify for which ship/s each

person is responsible. CSO & appropriateshore-based personnel shall have knowledge

and have received training.

A SSO shall be designated for each ship. He

shall have knowledge and have receivedtraining.


50/52

50

Security Co-ordinator

at HQ

SSOs for Ships

in Group A

CSO for Ships

in Group A

CSO for Ships

in Group B

SSOs for Ships

in Group B

COMPANY

(Top Mgmt.)


51/52

51

ISPS CodeTraining, drills & exercises

on ship security

Drills shall be carried out at appropriate

intervals to ensure effective implementation

of the SSP, taking into account :

Ship personnel changes

PFs to be visited

Other relevant circumstances

CSO shall ensure effective coordination &implementation of SSP by participating in

the exercises at appropriate intervals.


52/52

Documents

Maritime Security Policy ISPS SOLAS