ISMS Control Checklist 2022
ISMS Control Checklist 2022
Prepared by:
,-z\m'}}-
'rr-'>
Anele T. Patriarca
Name and Signature
SECURITY
Management directio n for information security
2
:
l I
Internal Organization
Segregation ofduties Conflicting duties and areas of responsibility ISMS Sub-Policies Manual /pG 4-5 6.1.2
shall be segregated to reduce opportunities duties & areas of responsibility are
for unauthorized or unintentional segregated
modification or misuse of the ensures that development, operations, &
administration functions are
organization's assets.
segregated from one another
Contact with authorities Appropriate contacts with relevant ISMS Sub-Policies Manual /pG S 6.1.3 (f.)
authorities shall be maintained. maintained contacts of appropriate enforcement
authorities, regulatory bodies, information service
providers, and telecommunications operators
3
I (t
Information securit5r Information security shall be addressed
in project in proiect management,
ISMS Sub-poti.ies Manuat
/pG S 6.1.4
> information are secured in accordance with their
management regardless of the type ofthe project. information classification & corresponding
handling procedures
4
rt
lnformation Securi - Controls Checktist, ISO/IEC 27001:2013 as of
Of
7.HUMAN RESOURCE
Prior to employment
objective:Toensurethatemployeesandcontractorsunderstandtheirresponsibilitiesandare,u,.,o*ffi
are considered.
During employment
objective:ToensurethatemployeesandcontractorsareawareofandfulfiItheirinformation,".u,,,,;;m
5
〔 { : 1
f■aHabllty
酔
ど、1犀]は I:Itiillじ
li「
Disciplinary There shall be a formal and communicated lSMS Sub・ Po:icles Manua:/PG8 723
process disciplinary process in place to take action against Violatlon ofinforma,on security pO‖ cies are
employees who have committed an inform-=ation appropriately dealt with through a formal
security breach. disciplinary process
Termination Responsibilities for performing employment lsMS SuEpolicier Ma nual lpcg 7.3.1
or change termination or change of employment shall be HR immediately notifies the tTD
of clearly defined and assigned. Manager on all
employment resigned/retired/terminated
responsibilit employees for the immediate
ies revocaton of their access rights,
Employees with predetermined end of contract
date have their access rights revoked
accordingly.
Referenceri
'Annex 7-l Training guidelines 60l .pGC.tTD
[pg
Code of Conduct
i :
ISO/IEC 27001:2013 as of
ASSET
7
lnformation Secu
- Controls lSOノ lEC 27001:2013 as of May 2022
eivesanappropriatelevelofprotectioninaccordancewithitsimportancetotheorganization.
Classificati Information shall be classified in terms of
legal
on requirements, value, criticality and sensitivitylo
ISMS Sub-Policies Manual
/pG 11 g.2,1
All PGC-ITD lnformation assets are
guidelines unauthorised disclosure or modification. categorized into the following
classifications:
.PUBLIC
or open
.INTERNAL
or proprietary
.CONFI
or RESTRTCTED
DENTTAL
References:
.Annex 8-2 lnformation
classifica6on
guidelines [pg 69-73]
and in References:
accordance with the information clissification 'Data Labelling Guidelines
handling lpg 72-731
scheme adopted by the organization.
,modification,remoValordestructionofinformationstoredonmedia.
Management Procedures shall be implemented for the
of removable management of removable media in accordance
ISMS Sub-Policies Manual /pG 13 8.3.1
References:
media with the classification scheme adopted by the 'Annex 8-7 Removable computer
media
organization. guidelines IpCtTl
8
I I │ │
::艦翼
[:I『 思R::lmr:憶 凪 a劇 ISMS Sub-policies Manual
References:
/pG 14_15 9.1.1
infOrmation security requirements
'Annex 9-l Access Control Guidelines
[pg 781
Access to Users shall only be provided with access
networks to the ISMS Sub-poticies Manuat/pc
network and network services that they 15 9.1.2
and network have been Referencer:
specifically authorized to use. Annex 9-l Access Control Guidelines
services [pt 7gl
9
Objective:TO ensure authOrized user access and tO prevent unauthOrized access tO systems and services
A formal user access provisioning process shall be :SMS Sub‐ Policies Manua1/PG 16
implemented to assign or revoke acc-ess rights
f". 922
types to all systems and services. "li'rr".
Management
li』 躍富:∬ :淋 ∬ 前 eged a∝
of privileged
access rights
∬ “
s nghs shall |SMS Sub-policies
9.2.3
Manual/pG 16
References:
'Annex 9-1- Guidelines for
Access Control [pg g2l
3. Privileged and Service Accounts
Management The allocation of secret authentication information
of secret be controlled through a formal rnrnrg"-"nt -"
shall ISMS Sub-poticies Manuat/pG to
authenticati f.o."*. User responsibilities (9.3.1)
on
information
of users
Review Of Asset owners shall review users,access
rights at
user access regular intervals. ISMS sub‐ Policies Manua1/Pc 16
rights 924
10
Removal or of all employees and external party
adlustment }i-:-*.r_ 1,an,r
ro lnrormation and information processing facilities
users
-1 ISMS
2013Sub-policies
as of Manuat/pG 9
ofaccess rights shall 7.3.7
be removed upon termination of their
em"ploy."ni,- --' References:
contract or agreement, or adjusted ,pon .Annex 7-1 Training
.hrng". guideljnes lpg
651 .PGCJTD Code of Conduct
information
ISO/IEC 27001:2013 as of
10。
objective:Toensureproperandeffectiveuseofcryptographytoprotect.r,".onr,
of information.
13
: : I I I
3?L*'fi :l"r'.:"J:1,":T:i*::1"'phvsicaraccess,d".
Physical Security perimeters shall be deflned and used to protect
security areas that cOntain either sensitive or critical informatiOn iSMS stlb_Policies Manua1/PG 19
Perimeter 111.■
Or informatiOn prOcessing facilities
References:
Annex ll_l Physical security
guidelines IP8 881(1)
Physical entry Secure.areas shall be protected by
controls appropriate entry iSMS Sub‐
controls to ensure that only auth;rir"a p".ronn.i ' 1112
P。 licies Manua1/PG 19
14
I I 〔
areas 1116
Objective:TO prevent10ss,damage′
theft Or cOmpromise ofassets and interruptiOn tO the OrganizatiOn's OperatiOns
utilities.
sup;;il;- 1122
15
1 :
16
〔 〔
iSO/IEc 27001:2013 as of
pem・ 。
nd procedures and respOndbJnes
and
operational
environments
informationprocessingfacilitiesareprotectedagainstmalware.
Controls Detection, prevention and recovery
against controls to protect rgrinJ
malware shall be implement"a,.omUin"a ISMS Sub-policies Manual
c
malware _i,t, appropriate t2.t.l
/p 26_27
References:
.Annex l2-1 protection
from
Malware Guidelines [pg 95-96]
- Controls Checktist, lSgr/lEC 27001:2013
as of
t2.3.2
12.3.3
72.3.4
12.3.5
72.3.6
References:
'Annex l2-2 Backup and
Restore Guidelines
[pg
s6-s7l
Event logging
聾口 ::琴
keptand regularlyrevieweal寧ξ
」 靴器柵“ ISMS Sub-policies Manual
t2.4.1
References:
/pG 28
出 臆│£;:蜻 」
::‖
ng
013 as of 2022
systems
」
assOciated risk. le
12.6.1
lnformation Securi
|9O/]EC 27001:2013 as of
rmationinnetworksanditssupportinginformationprocessingfaciIities.
Networks shall be managed and
controlled to protect
information in systems and applications. ISMS Sub-policies Manual
/pG 33
13.1.1
Security of Security mechanisms, service
levels and management
network of alt network services shatr ISMS Sub-policies Manual
/pG 33_34
seryices ::,:,j:T,:Tr
included in network services
be identified and
agreements, whether these
13.1.2
withinanorganizationandwithanyexternaIentity.
20
!SpttEC 27001:2013 as of
Information
transfer :躍 ]:T臆 :攪 蹴t『 :i蹴瀾∬ 器P駅[犠 ∴ iSMs sub‐ POlic:es Manua:ノ PG 34‐
35
policies and 」l types ^
_^′ OfcOmmumcauon品
っ‖ hァ hハ ^^_^__ ・
菖i誕 ξ
・ f 13。 2.1
procedures
21
l I I
It!t 1 ,1
iSO/IEC 27001:2013 as of
r.SY5TEM ACQUIsIT10N,DEVELOPMENTAN
Security requirements of information
systems
objective:Toensurethatinformationsecurityisanintegral,
│
s which provide services over public
networks.
Information
security
requirements
脚ahL_ぃ
nr
器撃 T:獅 麗3事『癬冊器驚l:11翼 ms ●一
iSMS Sub‐ PO:icies Manua1/PG 37
14.1.1
or enhancements
^^_^― tO existing infOrmatiOn systems.
=― ‐
analysis and
specification
Securing
application
services on
脇 H翼鳳
rnn,r● ´ャ Hich.,■ 岬.■ 導:獅::鳳 :iだ 瓶猟
___ L :SMs sub‐ POiicies Manua1/PG 37‐
14.1.2
38
contract dispute^^_」 ヽ and unauthorized disclosure and
public networks modification.
Protecting
application
services
量]R器 盤:冒 諄
mis-routing,
:r_"^..● 鍔:寵 :l認 襟罵留
:__ ___
S lSMS Sub‐ PO:icies Manua:/PG 38
14.1.3
―
unauthorized message alteration,
・・ ・ ・
22
-1 2013 as
Rules for the development of software
and systems shall :SMS sub‐ POlicies Manua1/PG 39
be established and applied to developments
within the 14.2.1
organization.
System Changes to systems within the development lifecycle shall :SMS sub‐ PO‖ cies Manua:/PG 39
change be controlled by the use of formal change control
14.2.1
control procedures.
Refer tO section 12.1.2 1pg 25]
procedures
to shall be 14.2.4
strictly controlled.
software
packages
24
I 〔 │ l l l
:
lnformation
- Controls 2013 as of 2022
Object市 e:TO maintain an agreed leve1 0finfOrmatiOn security and service delively in line with supplier agreements.
Managing Changes to the provision of services by suppliers, :SMS Sub‐ Poiicies Manuaiノ PG 46
changes to includingmaintaining and improving existing information 15.2.2
supplier security policies,procedures and controls, shall be managed,
seryices taking account of the criticality of business information,
systems and processes involved and re-assessment of risks.
Responsibiliti Management responsibilities and procedures shall be iSMS Sub‐ Poiicies Manua:/PG 47
es and established to ensure a quick, effective and orderly response 16.1.1
procedures to information security incidents.
Reporting Information security events shall be reported through iSMS Sub― Po‖ cies Manualノ PG 47
information appropriate management channels as quickly as 16.1.2
security events possible. Document used:incident RepOrt form
Reporting Employees and contractors using the organization,s iSMS Sub‐ Poncies Manuai/PG 47
information information systems and services shall be required to note 16.1.3
security and report any observed or suspected information security
weaknesses weaknesses in systems or services.
Assessment of Information security events shall be assessed and it shall iSMS Sub― Po‖ cies Manuai/PG 47
and decision be decided if they are to be classified as information 16.1.4
on security incidents.
information
security events
i f i l l l l 〔 I I l l l I I i 1 1 1 1
16.1.5 Response to Information security incidents shall be responded to Yes iSMS Sub‐ Policies Manuaiノ PG 48
information in accordance with the documented procedures. 16.1.4
security
incidents
16.1.6 Learning from Knowledge gained from analysing and resolving Yes ISSP/APP
information information security incidents shall be used to reduce the
security likelihood or impact of future incidents.
incidents
16.1.7 Collection of The organization shall define and apply procedures for Yes iSMS Sub‐ Po:icies Manua:/PG 48
evidence the identification, collection, acquisition and 16.1.5
preservation of information, which can serve as
evidence.
27
1 : I i l i : i :
lnformation
- Controls :SC)ノ IEC 27001:2013 as of
Objective: Information security continuity shall be embedded in the organization's business continuity
management systems.
Planning The organization shall determine its requirements for iSMS Sub‐ Po:icies Manuaiノ PG 49‐ 50
information information security and the continuity of information 17.1.1
security security management in adverse situations, e.g. during a crisis
continuity or disaster.
Implementi The organization shall establish, document, implement and iSMS Sub‐ Po:icies Manua:ノ PG 50‐ 51
ng maintain processes, procedures and controls to ensure the 17.1.2
information required level of continuity for information security during
security an adverse situation.
continuity
Verify, The organization shall veriff the established and iSMS Sub‐ Po:icies Manuaiノ PG 52
review and implemented information security continuity controls at 17.1.3
evaluate regular intervals in order to ensure that they are valid and
information effective during adverse situations.
security
continuity
Objective: Information security continuity shall be embedded in the organization's business continuity
management systems.
Availability Information processing facilities shall be implemented :SMS Sub‐ Po‖ cies Manua:ノ PG 52
Of with redundancy sufficient to meet availability 17.2.1
information requirements.
processlng
facilities
28
: I I I I I I : l l i I : : I l : : : :
Obiective: To avoid breaches of legal, statutory regulatory or contractual obligations related to information security and of any
security requirements.
18.1.1 Identification All relevant legislative statutory, regulatory Yes ISMS Sub-Policies Manual /pC 53 18.1.1
of applicable contractual requirements and the organization's
legislation approach to meet these requirements shall be
and explicitly identified, documented and kept up to
contractual date for each information system and the
requirements organization.
18。 1.2 Intellectual Appropriate procedures shall be implemented to Yes ISMS Sub-Policies Manual IPG 53
property rights ensure compliance with legislative, regulatory and
contractual requirements related to intellectual
property rights and use of proprietary software
products.
18.1.3 Protection of Records shall be protected from loss, destruction, Yes ISMS Sub-Policies Manual /PG 53 18.1.3
records falsification,unauthorized access and
unauthorized release, in accordance
withlegislatory regulatory contractual and
business requirements.
18.1.4 Privacy and Privacy and protection of personally identifiable Yes ISMS Sub-Policies Manua! /pG 53-54
protection of information shall be ensured as required in
personally relevant legislation and regulation where
identifiable applicable.
information
29
tt
墨 OЛ EC 27001:2013 as of
objective:Toensurethatinformationsecurityisimplementedandoperatedinaccordancewiththeo.ffi
and procedures.
Technical Information systems shall be regularly reviewed ISMS Sub-policies Manual lpc Ss_56 ta.z.3
compliance for compliance with the organizationb
review information security policies and standards.
30
I I I I I I I I i ! 1 : : ! : : l l l :
References
7. ISO /tEC ZT 0OZ:20 13tnfr
tso/tic27oo7:2oi,l;';;'j:lljfi"ll?[1lll,1;.illLil?":i.]liffi^,?:.f:jfii.j:::,?.ilT:[il,:];:H'J.1llli:illj.l
Legend
1. TSE - to some extent
31