0% found this document useful (0 votes)
189 views94 pages

ISO 27001-Various Checklist

The document provides an overview and checklist of ISO 27001 requirements for establishing an Information Security Management System (ISMS). It outlines the main clauses of ISO 27001, including leadership and commitment, planning actions to address risks, defining information security objectives, allocating necessary resources, ensuring competence, and creating awareness of the information security policy. The checklist is intended to help track progress in implementing and certifying an ISO 27001-compliant ISMS.

Uploaded by

deadone09
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
189 views94 pages

ISO 27001-Various Checklist

The document provides an overview and checklist of ISO 27001 requirements for establishing an Information Security Management System (ISMS). It outlines the main clauses of ISO 27001, including leadership and commitment, planning actions to address risks, defining information security objectives, allocating necessary resources, ensuring competence, and creating awareness of the information security policy. The checklist is intended to help track progress in implementing and certifying an ISO 27001-compliant ISMS.

Uploaded by

deadone09
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 94

ISO 27001 Checklist & Gap Analysis: Determine Initial & On-Going Status of ISO 27001 Impl

Overview: Fill out the following checklist as you complete your ISO 27001 certification journey to help track your prog
These steps will help you prepare for ISO 27001 implementation and certification, but this checklist is not meant to se
cure-all solution - every company has unique security needs which should be evaluated by an expert before pursuing

ISO 27001 Mandatory requirement for the ISMS


clause

4 Information Security Management System


4.1 Understanding the organization and its context
The organization shall determine external and internal
issues that are relevant to its purpose and that affect its
4.1
ability to achieve the intended outcome(s) of its information
security management system.
4.2 Understanding the needs and expectations of interested parties
The organization shall determine:
a) interested parties that are relevant to the information
4.2 security management system; and
b) the requirements of these interested parties relevant to
information security
4.3 Determining the scope of the information security management system
The organization shall determine the boundaries and
4.3 applicability of the information security management system
to establish its scope.
4.4 Information security management system
The organization shall establish, implement, maintain and
continually improve an information security management
4.4
system, in accordance with the requirements of this
International Standard.
5 Leadership
5.1 Leadership and commitment
Management shall provide evidence of its commitment to the
5.1 establishment, implementation, operation, monitoring,
review, maintenance and improvement of the ISMS by:
ensuring the information security policy and the information
5.1 (a) security objectives are established and are compatible with
the strategic direction of the organization;
ensuring the integration of the information security
5.1 (b) management system requirements into the organization’s
processes;
ensuring that the resources needed for the information
5.1 (c)
security management system are available;
communicating the importance of effective information
5.1 (d) security management and of conforming to the information
security management system requirements;
ensuring that the information security management system
5.1 (e)
achieves its intended outcome(s);
directing and supporting persons to contribute to the
5.1 (f) effectiveness of the information security management
system;
5.1 (g) promoting continual improvement; and
supporting other relevant management roles to demonstrate
5.1 (h)
their leadership as it applies to their areas of responsibility.
5.2

Top management shall establish an information security


policy that:
a) is appropriate to the purpose of the organization;
b) includes information security objectives (see 6.2) or
provides the framework for setting information security
objectives;
c) includes a commitment to satisfy applicable requirements
5.2 related to information security; and
d) includes a commitment to continual improvement of the
information security management system.

The information security policy shall:


e) be available as documented information;
f) be communicated within the organization; and
g) be available to interested parties, as appropriate

5.3 Organizational roles, responsibilities and authorities


Top management shall ensure that the responsibilities and
5.3 authorities for roles relevant to information security are
assigned and communicated.
6 Planning
6.1 Actions to address risks and opportunities
6.1.1 General

When planning for the information security management


system, the organization shall consider the issues referred to
in 4.1 and the requirements referred to in 4.2 and determine
the risks and opportunities that need to be addressed to:
6.1.1
a) ensure the information security management system can
achieve its intended outcome(s);
b) prevent, or reduce, undesired effects; and
c) achieve continual improvement

The organization shall plan actions to address these risks


6.1.1 (d)
and opportunities; and
The organization shall plan how to:
1) integrate and implement these actions into its information
6.1.1 (e) security management system
processes; and
2) evaluate the effectiveness of these actions.
6.1.2 Information security risk assessment
The organization shall define and apply an information
6.1.2
security risk assessment process that:
establishes and maintains information security risk criteria
that include:
6.1.2 (a) 1) the risk acceptance criteria; and
2) criteria for performing information security risk
assessments;

ensures that repeated information security risk assessments


6.1.2 (b)
produce consistent, valid and comparable results;

identifies the information security risks:


1) apply the information security risk assessment process to
identify risks associated with the loss of confidentiality,
6.1.2 (c)
integrity and availability for information within the scope of
the information security management system; and
2) identify the risk owners;

analyses the information security risks:


1) assess the potential consequences that would result if the
risks identified in 6.1.2 c) 1) were to materialize;
6.1.2 (d)
2) assess the realistic likelihood of the occurrence of the
risks identified in 6.1.2 c) 1); and
3) determine the levels of risk;
evaluates the information security risks:
1) compare the results of risk analysis with the risk criteria
6.1.2 (e)
established in 6.1.2 a); and
2) prioritize the analyzed risks for risk treatment.
6.1.3 Information security risk treatment
The organization shall define and apply an information
6.1.3
security risk treatment process to:
select appropriate information security risk treatment
6.1.3 (a)
options, taking account of the risk assessment results;
determine all controls that are necessary to implement the
6.1.3 (b)
information security risk treatment option(s) chosen;
compare the controls determined in 6.1.3 (b) above with
6.1.3 (c) those in Annex A and verify that no necessary controls have
been omitted;
produce a Statement of Applicability that contains the
necessary controls (see 6.1.3.b and c) and justification for
6.1.3 (d)
inclusions, whether they are implemented or not, and the
justification for exclusions of controls from Annex A;
6.1.3 (e) formulate an information security risk treatment plan; and
obtain risk owners’ approval of the information security risk
6.1.3 (f) treatment plan and acceptance of the residual information
security risks.

6.2 Information security objectives and plans to achieve them


The organization shall establish information security
6.2
objectives at relevant functions and levels.
The information security objectives shall:
a) be consistent with the information security policy;
b) be measurable (if practicable);
c) take into account applicable information security
6.2
requirements, and risk assessment and risk treatment
results;
d) be communicated; and
e) be updated as appropriate.

When planning how to achieve its information security


objectives, the organization shall determine:
f) what will be done;
6.2 g) what resources will be required;
h) who will be responsible;
i) when it will be completed; and
j) how the results will be evaluated.
7 Support
7.1 Resources
The organization shall determine and provide the resources
needed for the establishment, implementation, maintenance
7.1
and continual improvement of the information security
management system.
7.2 Competence
7.2 The organization shall:
determine the necessary competence of person(s) doing
7.2 (a) work under its control that affects its information security
performance;
ensure that these persons are competent on the basis of
7.2 (b)
appropriate education, training, or experience;

where applicable, take actions to acquire the necessary


7.2 (c) competence, and evaluate the effectiveness of the actions
taken; and

retain appropriate documented information as evidence of


7.2 (d)
competence.
7.3 Awareness
Persons doing work under the organization’s control shall be
7.3
aware of:
7.3 (a) the information security policy;
their contribution to the effectiveness of the information
7.3 (b) security management system, including the benefits of
improved information security performance; and
the implications of not conforming with the information
7.3 (c)
security management system requirements.
7.4 Communication
The organization shall determine the need for internal and
7.4 external communications relevant to the information security
management system including:
7.4 (a) on what to communicate;
7.4 (b) when to communicate;
7.4 (c) with whom to communicate;
7.4 (d) who shall communicate; and
7.4 (e) the processes by which communication shall be effected.
7.5 Documented information
7.5.1 General

The organization’s information security management system


7.5.1
shall include:

documented information required by this International


7.5.1 (a)
Standard; and
documented information determined by the organization as
7.5.1 (b) being necessary for the effectiveness of the information
security management system.
7.5.2 Creating and updating
When creating and updating documented information the
7.5.2
organization shall ensure appropriate:
identification and description (e.g. a title, date, author, or
7.5.2 (a)
reference number);
format (e.g. language, software version, graphics) and
7.5.2 (b)
media (e.g. paper, electronic); and
7.5.2 (c) review and approval for suitability and adequacy.
7.5.3 Control of documented information
Documented information required by the information security
7.5.3 management system and by this International Standard shall
be controlled to ensure:
it is available and suitable for use, where and when it is
7.5.3 (a)
needed; and
it is adequately protected (e.g. from loss of confidentiality,
7.5.3 (b)
improper use, or loss of integrity).

For the control of documented information, the organization


7.5.3
shall address the following activities, as applicable:
7.5.3 (c) distribution, access, retrieval and use;
storage and preservation, including the preservation of
7.5.3 (d)
legibility;
7.5.3 (e) control of changes (e.g. version control); and
7.5.3 (f) retention and disposition.
Documented information of external origin, determined by
the organization to be necessary for the planning and
7.5.3
operation of the information security management system,
shall be identified as appropriate, and controlled.
8 Operation
8.1 Operational planning and control
The organization shall plan, implement and control the
processes needed to meet information security
8.1 requirements, and to implement the actions determined in
6.1. The organization shall also implement plans to achieve
information security objectives determined in 6.2.
The organization shall keep documented information to the
8.1 extent necessary to have confidence that the processes
have been carried out as planned.
The organization shall control planned changes and review
8.1 the consequences of unintended changes, taking action to
mitigate any adverse effects, as necessary.
The organization shall ensure that outsourced processes are
8.1
determined and controlled.
8.2 Information security risk assessment
The organization shall perform information security risk
assessments at planned intervals or when significant
8.2
changes are proposed or occur, taking account of the criteria
established in 6.1.2.a.
The organization shall retain documented information of the
8.2
results of the information security risk assessments.
8.3 Information security risk treatment

The organization shall implement the information security


8.3
risk treatment plan.

The organization shall retain documented information of the


8.3
results of the information security risk treatment.

9 Performance evaluation
9.1 Monitoring, measurement, analysis and evaluation
The organization shall evaluate the information security
performance and the effectiveness of the information
9.1
security management system. The organization shall
determine:
what needs to be monitored and measured, including
9.1 (a)
information security processes and controls;
the methods for monitoring, measurement, analysis and
9.1 (b)
evaluation, as applicable, to ensure valid results;
9.1 (c) when the monitoring and measuring shall be performed;
9.1 (d) who shall monitor and measure;
when the results from monitoring and measurement shall be
9.1 (e)
analyzed and evaluated; and
9.1 (f) who shall analyze and evaluate these results.
9.2 Internal audit
The organization shall conduct internal audits at planned
9.2 intervals to provide information on whether the information
security management system:
conforms to
1) the organization’s own requirements for its information
9.2 (a)
security management system; and
2) the requirements of this International Standard;
9.2 (b) is effectively implemented and maintained.
9.2 The organization shall:
plan, establish, implement and maintain an audit
programme(s), including the frequency, methods,
responsibilities, planning requirements and reporting. The
9.2 (c)
audit programme(s) shall take into consideration the
importance of the processes concerned and the results of
previous audits;
9.2 (d) define the audit criteria and scope for each audit;
select auditors and conduct audits that ensure objectivity
9.2 (e)
and the impartiality of the audit process;
ensure that the results of the audits are reported to relevant
9.2 (f)
management; and
retain documented information as evidence of the audit
9.2 (g)
programme(s) and the audit results.
9.3 Management review

Top management shall review the organization’s information


security management system at planned intervals to ensure
9.3
its continuing suitability, adequacy and effectiveness. The
management review shall include consideration of:

9.3 (a) the status of actions from previous management reviews;


changes in external and internal issues that are relevant to
9.3 (b)
the information security management system;
feedback on the information security performance, including
trends in:
1) nonconformities and corrective actions;
9.3 (c)
2) monitoring and measurement results;
3) audit results; and
4) fulfilment of information security objectives;
9.3 (d) feedback from interested parties;
results of risk assessment and status of risk treatment plan;
9.3 (e)
and
9.3 (f) opportunities for continual improvement.
The outputs of the management review shall include
decisions related to continual improvement opportunities and
any needs for changes to the information security
9.3
management system. The organization shall retain
documented information as evidence of the results of
management reviews.
10 Improvement
10.1 Nonconformity and corrective action
10.1 When a nonconformity occurs, the organization shall:
react to the nonconformity, and as applicable:
10.1 (a) 1) take action to control and correct it; and
2) deal with the consequences;
evaluate the need for action to eliminate the causes of
nonconformity, in order that it does not recur or occur
elsewhere, by:
10.1 (b) 1) reviewing the nonconformity;
2) determining the causes of the nonconformity; and
3) determining if similar nonconformities exist, or could
potentially occur;
10.1 (c) implement any action needed;
10.1 (d) review the effectiveness of any corrective action taken; and
make changes to the information security management
10.1 (e)
system, if necessary.
Corrective actions shall be appropriate to the effects of the
10.1 nonconformities encountered. The organization shall retain
documented information as evidence of:
the nature of the nonconformities and any subsequent
10.1 (f)
actions taken, and
10.1 (g) the results of any corrective action.
10.2 Continual improvement
The organization shall continually improve the suitability,
10.2 adequacy and effectiveness of the information security
management system.

Legend
Count Status Code - Meaning
Process is defined / documented and practiced /
0 implemented
Process is practiced / implemented without adequate
0 documentation; Process must be defined / documented to
ensure repeatability of process and mitigate the risks.
100 Process is defined and not practiced
Process is not applicable for the company as per the scope
0
100
tial & On-Going Status of ISO 27001 Implementation

SO 27001 certification journey to help track your progress.


and certification, but this checklist is not meant to serve as a 100%
h should be evaluated by an expert before pursuing certification.

Status

Not Implemented

interested parties

Not Implemented

urity management system

Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented
Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented

orities

Not Implemented

Not Implemented

Not Implemented

Not Implemented
Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented

chieve them
Not Implemented
Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented
Not Implemented
Not Implemented
Not Implemented
Not Implemented
Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented
Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented
Not Implemented
Not Implemented
Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented
Not Implemented

Not Implemented

Not Implemented

Not Implemented

ation

Not Implemented

Not Implemented

Not Implemented
Not Implemented
Not Implemented
Not Implemented
Not Implemented

Not Implemented

Not Implemented

Not Implemented
Not Implemented

Not Implemented

Not Implemented
Not Implemented

Not Implemented
Not Implemented

Not Implemented

Not Implemented
Not Implemented

Not Implemented

Not Implemented
Not Implemented
Not Implemented

Not Implemented

Not Implemented

Not Implemented

Not Implemented
Not Implemented
Not Implemented

Not Implemented

Not Implemented
Not Implemented
Not Implemented

Status Code
Fully Implemented

Partially Implemented

Not Implemented
NA (Not Applicable)
Do You Have Documents / Records to Reference to Notes on Your Findings
Prove Compliance?
Notes on Your Recommendations & Next
Steps
SECTION/
REQUIREMENT/TASK ASSIGNED TO IN COMPLIANCE?
CATEGORY
5. Information Security Policies
5.1 Security policies exist.
All policies approved by
5.2
management.

5.3 Evidence of compliance.

6. Organization of information security

Roles and responsibilities


6.1
defined.

Segregation of duties
6.2
defined.

Verification body /
6.3 authority contacted for
compliance verification.

Establish contact with


6.4 special interest groups
regarding compliance.

Evidence of information
6.5 security in project
management.

Defined policy for mobile


6.6
devices.
Defined policy for
6.7
working remotely.
7. Human resources security
Defined policy for
7.1 screening employees
prior to employment.
Defined policy for HR
7.2 terms and conditions of
employment.
Defined policy for
7.3 management
responsibilities.

Defined policy for


information security
7.4
awareness, education,
and training.
Defined policy for
disciplinary process
7.5
regarding information
security.

Defined policy for HR


termination or change-of-
7.6 employment policy
regarding information
security.

8. Asset management
Complete inventory list
8.1
of assets.
Complete ownership list
8.2
of assets.
Defined "acceptable use"
8.3
of assets policy.
Defined return of assets
8.4
policy.
Defined policy for
8.5 classification
of information.
Defined policy for
8.6
labeling information.
Defined policy for
8.7 handling
of assets.
Defined policy for
8.8 management
of removable media.
Defined policy for
8.9 disposal
of media.
Defined policy for
8.10 physical
media transfer.
9. Access control
Defined policy for user
9.1 asset registration and de-
registration.

Defined policy for user


9.2
access provisioning.

Defined policy for


9.3 management of
privileged access rights.
Defined policy for
management
9.4
of secret authentication
information of users.

Defined policy for review


9.5
of user access rights.

Defined policy for


9.6 removal or adjustment of
access rights.

Defined policy for use of


9.7 secret authentication
information.

Defined policy for


9.8 information access
restrictions.

Defined policy for secure


9.9
log-in procedures.

Defined policy for


9.10 password management
systems.

Defined policy for use of


9.11 privileged utility
programs.

Defined policy for access


9.12 control
to program source code.

10. Cryptography

Defined policy for use of


10.1
cryptographic controls.

Defined policy for key


10.2
management.
11. Physical and environmental security
Defined policy for
11.1 physical security
perimeter.

Defined policy for


11.2
physical entry controls.
Defined policy for
11.3 securing offices, rooms,
and facilities.

Defined policy for


protection against
11.4
external and
environmental threats.

Defined policy for


11.5
working in secure areas.

Defined policy for


11.6 delivery and loading
areas.
Defined policy for
11.7 equipment siting and
protection.
Defined policy for
11.8
supporting utilities.
Defined policy for
11.9
cabling security.

Defined policy for


11.10
equipment maintenance.

Defined policy for


11.11
removal of assets.

Defined policy for


11.12 security of equipment and
assets off premises.

Secure disposal or re-use


11.13
of equipment.
Defined policy for
11.14 unattended user
equipment.
Defined policy for clear
11.15 desk and clear screen
policy.
12. Operations security

Defined policy for


12.1 documented operating
procedures.

Defined policy for change


12.2
management.
Defined policy for
12.3
capacity management.

Defined policy for


separation of
12.4
development, testing, and
operational environments.

Defined policy for


12.5
controls against malware.

Defined policy for


12.6
backing up systems.
Defined policy for
12.7
information backup.
Defined policy for event
12.8
logging.
Defined policy for
12.9 protection of
log information.
Defined policy for
12.10 administrator and
operator log.

Defined policy for clock


12.11
synchronization.

Defined policy for


12.12 installation of software on
operational systems.

Defined policy for


12.13 management of technical
vulnerabilities.

Defined policy for


12.14 restriction on software
installation.
Defined policy for
12.15 information system audit
control.
13. Communication security
Defined policy for
13.1
network controls.
Defined policy for
13.2 security of network
services.
Defined policy for
13.3
segregation in networks.

Defined policy for


13.4 information transfer
policies and procedures.

Defined policy for


13.5 agreements on
information transfer.

Defined policy for


13.6
electronic messaging.

Defined policy for


13.7 confidentiality or non-
disclosure agreements.

Defined policy for system


13.8 acquisition, development,
and maintenance.

14. System acquisition, development, and maintenance


Defined policy for
information security
14.1
requirements analysis and
specification.

Defined policy for


securing application
14.2
services on public
networks.

Defined policy for


14.3 protecting application
service transactions.

15. Supplier relationships


Defined policy for
15.1
supplier relationships.
16. Information security incident management
Defined policy for
16.1 information security
management.
17. Information security aspects of business continuity management
Defined policy for
17.1
redundancies.
18. Compliance
Defined policy for
identification of
18.1
applicable legislation and
contractual requirement.

Defined policy for


18.2 intellectual property
rights.
Defined policy for
18.3
protection of records.

Defined policy for


privacy and protection of
18.4
personally identifiable
information.

Defined policy for


18.5 regulation of
cryptographic control.

Defined policy for


18.6 compliance with security
policies and standards.

Defined policy for


18.7 technical compliance
review.
DATE LAST UPDATED
IMPLEMENTATION
ISO 27001 CONTROL TASKS IN COMPLIANCE?
PHASES
5 Information Security Policies
5.1 Management direction for information security
Security Policies exist?
Policies for information All policies approved by
5.1.1
security management?

Evidence of compliance?

6 Organization of information security


6.1 information security roles and responsibilites

Security roles and Roles and responsibilities


6.1.1
responsibilities defined?

Segreation of duties
6.1.2 Segregation of duties
defined?

Verification body /
6.1.3 Contact with authorities authority contacted for
compliance verificiation?

Establish contact with


Cntact with specal interest
6.1.4 special interest groups
groups
regarding compliance?

Evidence of information
Information security in
6.1.5 security in project
project management
management?

6.2 Mobile devices and teleworking


Defined policy for mobile
6.2.1 Mobile device policy
devices?
Defined policy for working
6.2.2 Teleworking
remotely?
7 Human resource security
7.1 Prior to employment

Defined policy for


7.1.1 Screening screening employees prior
to employment?

Defined policy for HR


Terms and conditions of
7.1.2 terms and conditions of
employment
employment?

Results
I identify goals aligned
with the organization’s
strategic direction,

and achieve results.

I persist through
significant difficulties to
achieve those goals.

Initiative

I anticipate needs, engage


in problem-solving, and
take action without
explicit instructions.

I take initiative to
discover new work
challenges, and influence
events leading to the
organization’s success.

Development

I demonstrate a
commitment to

the improvement of my
knowledge and skills.

Growth

I am proactive in
identifying areas for self-
development, and other
areas for growing my
skills.
NOTES
COMPANY NAME

ISO 27001 ASSET


CONTROL CONTROL ASSET REFERENCE CONFIDENTIAL?
REFERENCE NUMBER

Information
5
Security Policies

Management
direction for
5.1

information
security
Organization of
information 6
security

Information
security roles and 6.1.1
responsibilities

Human resources
security 7

Terms and
conditions of 7.1.2
employment
Asset
8
management
Responsibilities
8.1.2
for assets
Access control 9
Responsibilities
9.2.6
for assets
Cryptography 10
Secure areas 11
Physical security
11.1.1
perimeter
Operations
12
Security
Communications
13
security

System
acquisition,
14
development and
maintenance
Suppliers
15
relationships

Information
security incident 16
management

Information
security aspects
of business 17
continuity
management
Compliance 18
Privacy and
protection of
personally 18.1.4
identifiable
information
RISK RATING
RISK DETAILS COMPLETE?
(1 - LOWEST,
10 - HIGHEST)
LOW MEDIUM HIGH EXTREME

0 – ACCEPTABLE 1 – ALARP (as low as 2 – GENERALLY 3 – INTOLERABLE


RISK RATINGKEY reasonably practicable) UNACCEPTABLE

–––––––––––––––––– –––––––––––––––––– –––––––––––––––––– ––––––––––––––––––


OK TO PROCEED TAKE MITIGATION SEEK SUPPORT PLACE EVENT
EFFORTS
ON HOLD

SEVERITY

ACCEPTABLE TOLERABLE UNDESIRABLE INTOLERABLE

LITTLE TO NO EFFECTS ARE FELT, SERIOUS IMPACT TO COULD RESULT IN


EFFECT ON EVENT BUT NOT CRITICAL THE COURSE OF DISASTER
TO OUTCOME ACTION AND
OUTCOME

LIKELIHOOD

IMPROBABLE LOW MEDIUM MEDIUM HIGH

RISK IS UNLIKELY TO –1– –4– –6– – 10 –


OCCUR

POSSIBLE LOW MEDIUM HIGH EXTREME

RISK WILL LIKELY –2– –5– –8– – 11 –


OCCUR

PROBABLE MEDIUM HIGH HIGH EXTREME

RISK WILL OCCUR –3– –7– –9– – 12 –


ISO 27001 CONTROL NUMBER RANK PRIORITY

5. Security Policy Management

5.1 - Management has provided compliance direction


and support?

6. Corporate Security Management

6.1 - Internal information security task force has been


established?
6.2 - Measures in place to protect the org's mobile
devices and network?

7. Personnel Security Management

7.1 - Policy established for checking security prior to


employment?
7.2 - Policy established for security during
employment?

7.3 - Policy established for security at termination?

8. Organizational Asset Management

8.1 - Policy established for corporate assets?

8.2 - Policy established for information classification


method?
8.3 - Policy established for controlling physical
media?

9. Information Access Management

9.1 - Policy established for information access


management for business requirements?
9.2 - Policy established for managing all users' access
rights?

9.3 - Policy established for user authentication?

9.4 - Policy established for controlling access to


systems?

10. Cryptography Policy Management


10.1 - Policy established for control of the use of
cryptographic controls and keys?

11. Physical Security Management

11.1 - Policy established for physical security


management?
11.2 - Policy established for protecting the org's
equipment?

12. Operational security Management

12.1 - Policy established for operational security


management procedures and responsibilities?
12.2 - Policy established for protecting the org from
malware?
12.3 - Policy established for creating backup copies
on a regular basis?
12.4 - Policy established for using logs to record
security events?
12.5 - Policy established for controlling org's
operational software?
12.6 - Policy established for addressing org's
technical vulnerabilities?
12.7 - Policy in place for minimizing impact of audit
activities?

13. Network Security Management

13.1 - Policy established for protecting networks and


facilities?
13.2 - Policy established for protecting information
transfers?

14. System Security Management

14.1 - Policy established for ensuring security an


inherent part of info systems?
14.2 - Policy established for protecting and
controlling system development activities?
14.3 - Policy established for safeguarding data used
for system-testing purposes?

15. Supplier Relationship Management

15.1 - Policy established for forming security


agreements with suppliers?
15.2 - Policy established for managing suppliers'
security and service deliveries?

16. Security Incident Management

16.1 - Policy established for identifying and


responding to info security incidents?

17. Security Continuity Management

17.1 - Policy established for forming info security


continuity controls?
17.2 - Policy established for redundancy builds for
info-processing facilities?

18. Security Compliance Management

18.1 - Policy established for legal security


requirements compliance?
18.2 - Policy established for executing security
compliance reviews?
OWNER DATE ASSIGNED DUE DATE IN COMPLIANCE?
STATUS NOTES

PRIORITY KEY RANK KEY

HIGH 5

MEDIUM 4

LOW 3

1
STATUS KEY

NOT STARTED

25%

50%%

75%

100%

ON HOLD

PENDING
REQUIREMENT
ASSESSMENT IN COMPLIANCE? REMARKS
SECTION/CATEGORY

5. Information Security Policies


5.1 Security policies exist?
All policies approved by
5.2
management?

5.3 Evidence of compliance?

6. Organization of information security


Defined roles and
6.1
responsibilities?
Defined segregation of
6.2
duties?

Verification body /
6.3 authority contacted for
compliance verification?

Established contact with


6.4 special interest groups
regarding compliance?

Evidence of information
6.5 security in project
management?

Defined policy for


6.6
working remotely?
7. Human resources security

Defined policy for


7.1 screening employees
prior to employment?

Defined policy for HR


7.2 terms and conditions of
employment?
Defined policy for
7.3 management
responsibilities?

Defined policy for


information security
7.4 awareness, education,

and training?
Defined policy for

7.5 disciplinary process


regarding information
security?

Defined policy for HR


termination or change-of-
7.6 employment policy
regarding information
security?

8. Asset management
Complete inventory list
8.1
of assets?
Complete ownership list
8.2
of assets?

Defined "acceptable use"


8.3
of assets policy?

Defined return of assets


8.4
policy?
Defined policy for
classification
8.5
of information?
Defined policy for
8.6
labeling information?

Defined policy for


8.7 handling

of assets?

Defined policy for


management
8.8

of removable media?

Defined policy for


8.9 disposal

of media?
Defined policy for
8.10 physical
media transfer?
9. Access control

Defined policy for access


9.1
control policy?

Defined policy for access


9.2 to networks and network
services?

Defined policy for user


9.3 asset registration and de-
registration?
Defined policy for user
9.4
access provisioning?

Defined policy for


9.5 management of
privileged access rights?

Defined policy for


management
9.6
of secret authentication

information of users?

Defined policy for review


9.7
of user access rights?

Defined policy for


9.8 removal or adjustment of
access rights?

Defined policy for use of


9.9 secret authentication
information?

Defined policy for


9.10 information access
restrictions?

Defined policy for secure


9.11
log-in procedures?

Defined policy for


9.12 password management
systems?
Defined policy for use of
9.13 privileged utility
programs?
Defined policy for access
control
9.14
to program source code?

10. Cryptography

Defined policy for use of


10.1
cryptographic controls?

Defined policy for key


10.2
management?
11. Physical and environmental security
Defined policy for
11.1 physical security
perimeter?

Defined policy for


11.2
physical entry controls?

Defined policy for


11.3 securing offices, rooms,
and facilities?

Defined policy for


protection against
11.4
external and
environmental threats?

Defined policy for


11.5
working in secure areas?

Defined policy for


11.6 delivery and loading
areas?
Defined policy for
11.7 equipment siting and
protection?
Defined policy for
11.8
supporting utilities?
Defined policy for
11.9
cabling security?

Defined policy for


11.10
equipment maintenance?

Defined policy for


11.11
removal of assets?
Defined policy for
11.12 security of equipment and
assets off premises?

Secure disposal or re-use


11.13
of equipment?
Defined policy for
11.14 unattended user
equipment?
Defined policy for clear
11.15 desk and clear screen
policy?
12. Operations security

Defined policy for


12.1 documented operating
procedures?

Defined policy for change


12.2
management?

Defined policy for


12.3
capacity management?

Defined policy for


separation of
12.4 development, testing, and
operational
environments?

Defined policy for


12.5
controls against malware?

Defined policy for


12.6
backing up systems?

Defined policy for


12.7
information backup?

Defined policy for event


12.8
logging?
Defined policy for
12.9 protection of
log information?
Defined policy for
12.10 administrator and
operator log?

Defined policy for clock


12.11
synchronization?

Defined policy for


12.12 installation of software on
operational systems?

Defined policy for


12.13 management of technical
vulnerabilities?

Defined policy for


12.14 restriction on software
installation?
Defined policy for
12.15 information system audit
control?
13. Communication security
Defined policy for
13.1
network controls?
Defined policy for
13.2 security of network
services?

Defined policy for


13.3
segregation in networks?

Defined policy for


13.4 information transfer
policies and procedures?

Defined policy for


13.5 agreements on
information transfer?

Defined policy for


13.6
electronic messaging?

Defined policy for


13.7 confidentiality or non-
disclosure agreements?

Defined policy for system


13.8 acquisition, development,
and maintenance?
14. System acquisition, development, and maintenance
Defined policy for
information security
14.1
requirements analysis and
specification?

Defined policy for


securing application
14.2
services on public
networks?

Defined policy for


14.3 protecting application
service transactions?

Defined policy for in-


14.4
house development?
15. Supplier relationships
Defined policy for
15.1
supplier relationships?
16. Information security incident management
Defined policy for
16.1 information security
management?
17. Information security aspects of business continuity management
Defined policy for
17.1 information security
continuity?
Defined policy for
17.2
redundancies?
18. Compliance

Defined policy for


identification of
18.1
applicable legislation and
contractual requirement?

Defined policy for


18.2 intellectual property
rights?

Defined policy for


18.3
protection of records?

Defined policy for


privacy and protection of
18.4
personally identifiable
information?
Defined policy for
18.5 regulation of
cryptographic control?

Defined policy for


18.6 compliance with security
policies and standards?

Defined policy for


18.7 technical compliance
review?
PROCESS
AUDIT DATE REFERENCE NUMBER PERFORMED BY
DESCRIPTION
AUDIT DESCRIPTION AUDITEE RESULTS REMARKS
MANDATORY
ISO 27001 CONTROL REQUIREMENTS RELEVANT? IN COMPLIANCE?

FOR THE ISMS


A. 5. IS Policies
5.1. Management direction for information security
5.1.1 Policies for IS
A. 6. Organization of information security
6.1. Internal organization
6.1.1 IS roles / responsibilities

6.1.2 Segregation of duties


6.2. Mobile devices and teleworking
6.2.1 Mobile devices policy
6.2.2 Teleworking
A. 7. Human resources security
7.1. Prior to employment
7.1.1 Screening
Terms and conditions of
7.1.2
employment
7.2. During employment
Management
7.2.1
responsibilities

IS awareness, education,
7.2.2
and training

A. 8. Asset management
8.1. Responsibilities for assets
8.1.1 Inventory of assets
8.1.2 Ownership of assets

8.1.3 Acceptable use of assets

8.1.4 Return of assets


8.2. Information classification
Classification of
8.2.1
information

8.2.2 Labeling of information

A. 9. Access control
9.1. Responsibilities for assets
9.1.1 Access control policy
Access to networks and
9.1.2
network services
9.2. Responsibilities for assets
User registration and de-
9.2.1
registration
Management of
9.2.3
privileged access rights

Management of secret
9.2.4 authentication
information of users
Review of user access
9.2.5
rights

Removal or adjustment of
9.2.6
access rights

9.3. User responsibilities


Use of secret
9.3.1 authentication
information
9.4. System and application access control
Information access
9.4.1
restrictions

9.4.2 Secure log-in procedures

Password management
9.4.3
system
A. 10. Cryptography
10.1. Cryptographic controls

Policy on the use of


10.1.1
cryptographic controls

10.1.2 Key management


A. 11. Physical and environmental security
11.1. Secure areas
Physical security
11.1.1
perimeter
11.1.2 Physical entry controls
Securing offices, rooms,
11.1.3
and facilities

Protection against
11.1.4 external and
environmental threats

11.1.5 Working in secure areas

Delivery and loading


11.1.6
areas
11.2. Equipment
Equipment siting and
11.2.1
protection
11.2.2 Support utilities
11.2.3 Cabling security
11.2.4 Equipment maintenance

11.2.5 Removal of assets


A. 12. Operations security
12.1 Operational procedures and responsibilities
Documented operating
12.1.1
procedures

12.1.2 Change management

12.1.3 Capacity management

Separation of
12.1.4 development, testing, and
operational environments

12.2. Protection from malware


12.2.1 Controls against malware
12.3. Backup
12.3.1 Information backup
12.4. Logging and monitoring
12.4.1 Event logging
Protection of log
12.4.2
information
Administrator and
12.4.3
operator log
12.5. Control of operational software

Installation of software
12.5.1
on operational systems

12.6. Technical vulnerability management

Management of technical
12.6.1
vulnerabilities

A. 13. Communication security


13.1. Network security management
13.1.1 Network controls
Security of network
13.1.2
services

13.1.3 Segregation in networks


13.2. Information transfer

Information transfer
13.2.1
policies and procedures

Agreements on
13.2.2
information transfer
14.1. Security requirements of information systems

IS requirements analysis
14.1.1
and specification

Securing application
14.1.2 services on public
networks

Protecting application
14.1.3
service transactions

A. 15. Supplier relationships


A. 16. IS incident management
16.1.1 IS management
A. 17. IS aspects of business continuity management
17.1.1 IS continuity
17.2.1 Redundancies
A. 18. Compliance
18.1. Compliance with legal and contractual requirements

Identification of
18.1.1 applicable legislation and
contractual requirements

Intellectual property
18.1.2
rights
18.1.3 Protection of records

Privacy and protection of


18.1.4 personally identifiable
information

Regulation of
18.1.5
cryptographic controls

18.2. Independent review of information security

Independent review of
18.2.1
information security
PLEASE REFERENCE REMARKS
Reference Audit area, objective and question

Checklist Standard Section Audit Question


Security Policy
1.1 5.1 Information Security Policy
1.1.1 5.1.1 Information security Whether there exists an
policy document Information security
policy, which is approved
by the management,
published and
communicated as
appropriate
Whether theto all states
policy
management commitment
and sets out the
organizational approach
to managing information
security.

1.1.2 5.1.2 Review of Informational Whether the Information


Security Policy Security Policy is
reviewed at planned
intervals, or if significant
changes occur to ensure
its continuing suitability,
adequacy and
effectiveness.

Whether the Information


Security policy has an
owner, who has approved
management
responsibility for
development, review and
evaluation of the security
policy.

Whether any defined


Information Security
Policy review procedures
exist and do they include
requirements for the
management review.

Whether the results of the


management review are
taken into account.
Whether management
approval is obtained for
the revised policy.
Result

Status (%)

Findings

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy