Information technology -- Security techniques -- Information security management systems -- Requirements

This International Standard specifies the requirements for establishing, implementing, maintaining and continually improving an information security management system within the context of the organization. This International Standard also includes requirements for the assessment and treatment of information security risks tailored to the needs of the organization. The requirements set out in this International Standard are generic and are intended to be applicable to all organizations, regardless
of type, size or nature. Excluding any of the requirements specified in Clauses 4 to 10 is not acceptable when an organization claims conformity to this International Standard.

Technologies de l'information -- Techniques de sécurité -- Systèmes de management de la sécurité de l'information -- Exigences

L'ISO/CEI 27001:2013 sp�cifie les exigences relatives � l'�tablissement, � la mise en �uvre, � la mise � jour et � l'am�lioration continue d'un syst�me de management de la s�curit� de l'information dans le contexte d'une organisation. Elle comporte �galement des exigences sur l'appr�ciation et le traitement des risques de s�curit� de l'information, adapt�es aux besoins de l'organisation. Les exigences fix�es dans l'ISO/CEI 27001:2013 sont g�n�riques et pr�vues pour s'appliquer � toute organisation, quels que soient son type, sa taille et sa nature. Il n'est pas admis qu'une organisation s'affranchisse de l'une des exigences sp�cifi�es aux Articles 4 � 10 lorsqu'elle revendique la conformit� � l'ISO/CEI 27001:2013.

Informacijska tehnologija - Varnostne tehnike - Sistemi upravljanja informacijske varnosti - Zahteve

Ta mednarodni standard določa zahteve za vzpostavitev, izvajanje, vzdrževanje in nenehno izboljševanje sistema upravljanja informacijske varnosti v okviru organizacije. Ta mednarodni standard zajema tudi zahteve za ocenjevanje in obravnavanje tveganj informacijske varnosti, ki so prilagojene potrebam organizacije. Zahteve, postavljene v tem mednarodnem standardu, so generične in so namenjene uporabi v vseh organizacijah ne glede na vrsto, velikost ali naravo. Izključevanje katere koli zahteve, določene v točkah 4 do 10, ni sprejemljivo, kadar organizacija zagotavlja skladnost s tem mednarodnim standardom.

General Information

Status
Withdrawn
Public Enquiry End Date
30-Sep-2013
Publication Date
15-Oct-2013
Withdrawal Date
05-Feb-2018
Technical Committee
Current Stage
9900 - Withdrawal (Adopted Project)
Start Date
06-Feb-2018
Due Date
01-Mar-2018
Completion Date
06-Feb-2018

RELATIONS

Buy Standard

Standard
REDLINE ISO/IEC 27001:2013 - Information technology -- Security techniques -- Information security management systems -- Requirements
English language
23 pages
sale 15% off
Preview
sale 15% off
Preview
Standard
ISO/IEC 27001:2013 - Information technology -- Security techniques -- Information security management systems -- Requirements
English language
23 pages
sale 15% off
Preview
sale 15% off
Preview
Standard
ISO/IEC 27001:2013 - Information technology -- Security techniques -- Information security management systems -- Requirements
English language
23 pages
sale 15% off
Preview
sale 15% off
Preview
Standard
SIST ISO/IEC 27001:2013
English language
28 pages
sale 10% off
Preview
sale 10% off
Preview

e-Library read for
1 day
Standard
ISO/IEC 27001:2013 - Technologies de l'information -- Techniques de sécurité -- Systemes de management de la sécurité de l'information -- Exigences
French language
23 pages
sale 15% off
Preview
sale 15% off
Preview
Standard – translation
SIST ISO/IEC 27001:2013 (brez AC) - prevod brez popravka
Slovenian language
26 pages
sale 10% off
Preview
sale 10% off
Preview

e-Library read for
1 day
Standard – translation
SIST ISO/IEC 27001:2013 (+ AC) - DODAN POPRAVEK AC101:2014, natisnjeno za čitalnico
Slovenian language
26 pages
sale 10% off
Preview
sale 10% off
Preview

e-Library read for
1 day

Standards Content (sample)

INTERNATIONAL ISO/IEC
STANDARD 27001
Redline version
compares second edition
to first edition
Information technology — Security
techniques — Information security
management systems — Requirements
Technologies de l’information — Techniques de sécurité — Systèmes
de management de la sécurité de l’information — Exigences
Reference number
ISO/IEC 27001:redline:2014(E)
ISO/IEC 2014
---------------------- Page: 1 ----------------------
ISO/IEC 27001:redline:2014(E)
IMPORTANT — PLEASE NOTE
This is a mark-up copy and uses the following colour coding:
Text example 1 — indicates added text (in green)
Text example 2 — indicates removed text (in red)
— indicates added graphic figure
— indicates removed graphic figure
1.x ... — Heading numbers containg modifications are highlighted in yellow in
the Table of Contents
DISCLAIMER

This Redline version provides you with a quick and easy way to compare the main changes

between this edition of the standard and its previous edition. It doesn’t capture all single

changes such as punctuation but highlights the modifications providing customers with

the most valuable information. Therefore it is important to note that this Redline version is

not the official ISO standard and that the users must consult with the clean version of the

standard, which is the official standard, for implementation purposes.
COPYRIGHT PROTECTED DOCUMENT
© ISO 2014

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form

or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior

written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of

the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2014 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 27001:redline:2014(E)
Contents Page

Foreword ..........................................................................................................................................................................................................................................v

0 Introduction ...........................................................................................................................................................................................................................vi

0.1 General ..........................................................................................................................................................................................................vi

0.2 Process approach .................................................................................................................................................................................vi

0.3 Compatibility with other management systems ..................................................................................................... vii

1 Scope ................................................................................................................................................................................................................................. 1

1.1 General ........................................................................................................................................................................................................... 1

1.2 Application ................................................................................................................................................................................................. 1

2 Normative references ...................................................................................................................................................................................... 1

3 Terms and definitions ..................................................................................................................................................................................... 2

3 4 Terms and definitions Context of the organization ........................................................................................................... 2

4.1 Understanding the organization and its context ....................................................................................................... 2

4.2 Understanding the needs and expectations of interested parties .............................................................. 2

4.3 Determining the scope of the information security management system .......................................... 2

4.4 Information security management system ..................................................................................................................... 3

5 Leadership .................................................................................................................................................................................................................. 4

5.1 Leadership and commitment ..................................................................................................................................................... 4

5.2 Policy ............................................................................................................................................................................................................... 5

5.3 Organizational roles, responsibilities and authorities.......................................................................................... 5

4 6 Information security management system Planning ...................................................................................................... 5

4.1 General requirements ....................................................................................................................................................................... 5

4.2 6.1 Establishing and managing the ISMS Actions to address risks and opportunities ....................... 6

4.3 6.2 Documentation requirements Information security objectives and planning to

achieve them ..........................................................................................................................................................................................10

5 7 Management responsibility Support .............................................................................................................................................12

5.1 7.1 Management commitment Resources ..............................................................................................................................12

5.2 7.2 Resource management Competence ..................................................................................................................................12

7.3 Awareness ................................................................................................................................................................................................13

7.4 Communication ...................................................................................................................................................................................13

7.5 Documented information ............................................................................................................................................................13

8 Operation ..................................................................................................................................................................................................................14

8.1 Operational planning and control .......................................................................................................................................14

8.2 Information security risk assessment..............................................................................................................................15

8.3 Information security risk treatment .................................................................................................................................15

6 9 Internal ISMS audits Performance evaluation .....................................................................................................................15

9.1 Monitoring, measurement, analysis and evaluation ............................................................................................15

9.2 Internal audit .........................................................................................................................................................................................16

9.3 Management review ........................................................................................................................................................................16

7 Management review of the ISMS .......................................................................................................................................................17

7.1 General ........................................................................................................................................................................................................17

7.2 Review input ..........................................................................................................................................................................................17

7.3 Review output .......................................................................................................................................................................................17

8 10 ISMS improvement Improvement .....................................................................................................................................................18

8.1 Continual improvement ...............................................................................................................................................................18

8.2 10.1 .......................................................................................................................... Corrective Nonconformity and

corrective action .................................................................................................................................................................................18

8.3 10.2 ...................................................................................................................................................................Preventive

action Continual improvement ...............................................................................................................................................18

Annex A (normative) Control Reference control objectives and controls ...................................................................20

© ISO 2014 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 27001:redline:2014(E)

Annex B (informative) OECD principles and this International Standard ..................................................................39

Annex C (informative) Correspondence between ISO 9001:2000, ISO 14001:2004 and this

International Standard ...............................................................................................................................................................................40

Bibliography .............................................................................................................................................................................................................................42

Standards publications .................................................................................................................................................................................................43

Other publications .............................................................................................................................................................................................................44

iv © ISO 2014 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 27001:redline:2014(E)
Foreword

ISO (the International Organization for Standardization) and IEC (the International Electrotechnical

Commission) form the specialized system for worldwide standardization. National bodies that are

members of ISO or IEC participate in the development of International Standards through technical

committees established by the respective organization to deal with particular fields of technical

activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international

organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the

work. In the field of information technology, ISO and IEC have established a joint technical committee,

ISO/IEC JTC 1.

International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.

The main task of the joint technical committee is to prepare International Standards. Draft International

Standards adopted by the joint technical committee are circulated to national bodies for voting.

Publication as an International Standard requires approval by at least 75 % of the national bodies

casting a vote.

Attention is drawn to the possibility that some of the elements of this document may be the subject of

patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.

ISO/IEC 27001 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,

Subcommittee SC 27, IT Security techniques.

This second edition cancels and replaces the first edition (ISO/IEC 27001:2005), which has been

technically revised.
© ISO 2014 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/IEC 27001:redline:2014(E)
0 Introduction
0.1 General

This International Standard has been prepared to provide a model for establishing, implementing, operating,

monitoring, reviewing, maintaining and improving an Information Security Management System (ISMS).

The adoption of an ISMS should be a strategic decision for an organization. The design and implementation

of an organization’s ISMS is influenced by their needs and objectives, security requirements, the processes

employed and the size and structure of the organization. These and their supporting systems are expected

to change over time. It is expected that an ISMS implementation will be scaled in accordance with the

needs of the organization, e.g. a simple situation requires a simple ISMS solution.

This International Standard can be used in order to assess conformance by interested internal and

external parties.
0.1 General
0.2 Process approach

This International Standard adopts a process approach for establishing, implementing, operating,

monitoring, reviewing, maintaining and improving an organization’s ISMS.

An organization needs to identify and manage many activities in order to function effectively. Any

activity using resources and managed in order to enable the transformation of inputs into outputs can be

considered to be a process. Often the output from one process directly forms the input to the next process.

The application of a system of processes within an organization, together with the identification and

interactions of these processes, and their management, can be referred to as a “process approach”.

The process approach for information security management presented in this International Standard

encourages its users to emphasize the importance of:

a) understanding an organization’s information security requirements and the need to establish policy

and objectives for information security;

b) implementing and operating controls to manage an organization’s information security risks in the

context of the organization’s overall business risks;
c) monitoring and reviewing the performance and effectiveness of the ISMS; and
d) continual improvement based on objective measurement.

This International Standard adopts the “Plan-Do-Check-Act” (PDCA) model, which is applied to structure

all ISMS processes. Figure 1 illustrates how an ISMS takes as input the information security requirements

and expectations of the interested parties and through the necessary actions and processes produces

information security outcomes that meets those requirements and expectations. Figure 1 also illustrates

the links in the processes presented in Clauses 4, 5, 6, 7 and 8.

The adoption of the PDCA model will also reflect the principles as set out in the OECD Guidelines (2002)

governing the security of information systems and networks. This International Standard provides a

robust model for implementing the principles in those guidelines governing risk assessment, security

design and implementation, security management and reassessment.

EXAMPLE 1 A requirement might be that breaches of information security will not cause serious financial

damage to an organization and/or cause embarrassment to the organization.

1) OECD Guidelines for the Security of Information Systems and Networks — Towards a Culture of Security. Paris:

OECD, July 2002. www.oecd.org
vi © ISO 2014 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC 27001:redline:2014(E)

EXAMPLE 2 An expectation might be that if a serious incident occurs — perhaps hacking of an organization’s

eBusiness web site — there should be people with sufficient training in appropriate procedures to minimize the

impact.
Figure 1 — PDCA model applied to ISMS processes

Plan (establish the ISMS) Establish ISMS policy, objectives, processes and procedures relevant to

managing risk and improving information security to deliver results in
accordance with an organization’s overall policies and objectives.

Do (implement and oper- Implement and operate the ISMS policy, controls, processes and proce-

ate the ISMS) dures.

Check (monitor and Assess and, where applicable, measure process performance against

review the ISMS) ISMS policy, objectives and practical experience and report the results

to management for review.

Act (maintain and Take corrective and preventive actions, based on the results of the inter-

improve the ISMS) nal ISMS audit and management review or other relevant information, to

achieve continual improvement of the ISMS.

This International Standard has been prepared to provide requirements for establishing, implementing,

maintaining and continually improving an information security management system. The adoption of an

information security management system is a strategic decision for an organization. The establishment

and implementation of an organization’s information security management system is influenced by the

organization’s needs and objectives, security requirements, the organizational processes used and the

size and structure of the organization. All of these influencing factors are expected to change over time.

0.3 Compatibility with other management systems

This International Standard is aligned with ISO 9001:2000 and ISO 14001:2004 in order to support

consistent and integrated implementation and operation with related management standards. One

suitably designed management system can thus satisfy the requirements of all these standards.

Table C.1 illustrates the relationship between the clauses of this International Standard, ISO 9001:2000

and ISO 14001:2004.

This International Standard is designed to enable an organization to align or integrate its ISMS with

related management system requirements.

The information security management system preserves the confidentiality, integrity and availability

of information by applying a risk management process and gives confidence to interested parties that

risks are adequately managed.

It is important that the information security management system is part of and integrated with the

organization’s processes and overall management structure and that information security is considered

in the design of processes, information systems, and controls. It is expected that an information security

management system implementation will be scaled in accordance with the needs of the organization.

© ISO 2014 – All rights reserved vii
---------------------- Page: 7 ----------------------
ISO/IEC 27001:redline:2014(E)

This International Standard can be used by internal and external parties to assess the organization’s

ability to meet the organization’s own information security requirements.

The order in which requirements are presented in this International Standard does not reflect their

importance or imply the order in which they are to be implemented. The list items are enumerated for

reference purpose only.

ISO/IEC 27000 describes the overview and the vocabulary of information security management

systems, referencing the information security management system family of standards (including

[2] [3] [4]

ISO/IEC 27003 , ISO/IEC 27004 and ISO/IEC 27005 ), with related terms and definitions.

0.2 Compatibility with other management system standards

This International Standard applies the high-level structure, identical sub-clause titles, identical text,

common terms, and core definitions defined in Annex SL of ISO/IEC Directives, Part 1, Consolidated ISO

Supplement, and therefore maintains compatibility with other management system standards that have

adopted the Annex SL.

This common approach defined in the Annex SL will be useful for those organizations that choose to operate

a single management system that meets the requirements of two or more management system standards.

viii © ISO 2014 – All rights reserved
---------------------- Page: 8 ----------------------
INTERNATIONAL STANDARD ISO/IEC 27001:redline:2014(E)
Information technology — Security techniques —
Information security management systems — Requirements

IMPORTANT — — This publication does not purport to include all the necessary provisions of

a contract. Users are responsible for its correct application. Compliance with an International

Standard does not in itself confer immunity from legal obligations.
1 Scope
1.1 General

This International Standard covers all types of organizations (e.g. commercial enterprises, government

agencies, non-profit organizations). This International Standard specifies the requirements for

establishing, implementing, operating, monitoring, reviewing, maintaining and improving a documented

ISMS within the context of the organization’s overall business risks. It specifies requirements for the

implementation of security controls customized to the needs of individual organizations or parts thereof.

The ISMS is designed to ensure the selection of adequate and proportionate security controls that

protect information assets and give confidence to interested parties.

NOTE 1: References to ‘business’ in this International Standard should be interpreted broadly to mean those

activities that are core to the purposes for the organization’s existence.

NOTE 2: ISO/IEC 17799 provides implementation guidance that can be used when designing controls.

This International Standard specifies the requirements for establishing, implementing, maintaining

and continually improving an information security management system within the context of the

organization. This International Standard also includes requirements for the assessment and treatment

of information security risks tailored to the needs of the organization. The requirements set out in this

International Standard are generic and are intended to be applicable to all organizations, regardless

of type, size or nature. Excluding any of the requirements specified in Clauses 4 to 10 is not acceptable

when an organization claims conformity to this International Standard.
1.2 Application

The requirements set out in this International Standard are generic and are intended to be applicable to all

organizations, regardless of type, size and nature. Excluding any of the requirements specified in Clauses 4,

5, 6, 7, and 8 is not acceptable when an organization claims conformity to this International Standard.

Any exclusion of controls found to be necessary to satisfy the risk acceptance criteria needs to be

justified and evidence needs to be provided that the associated risks have been accepted by accountable

persons. Where any controls are excluded, claims of conformity to this International Standard are

not acceptable unless such exclusions do not affect the organization’s ability, and/or responsibility, to

provide information security that meets the security requirements determined by risk assessment and

applicable legal or regulatory requirements.

NOTE: If an organization already has an operative business process management system (e.g. in relation with

ISO 9001 or ISO 14001), it is preferable in most cases to satisfy the requirements of this International Standard

within this existing management system.
2 Normative references

The following referenced documentsdocuments, in whole or in part, are normatively referenced in this

document and are indispensable for the application of this documentits application. For dated references,

© ISO 2014 – All rights reserved 1
---------------------- Page: 9 ----------------------
ISO/IEC 27001:redline:2014(E)

only the edition cited applies. For undated references, the latest edition of the referenced document

(including any amendments) applies.

ISO/IEC 17799:2005 27000, Information technology — Security techniques — Code of practice for

information security management Information security management systems — Overview and vocabulary

3 Terms and definitions

For the purposes of this document, the terms and definitions given in ISO/IEC 27000 apply.

3 4 Terms and definitions Context of the organization
For the purposes of this document, the following terms and definitions apply.
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 ability to achieve the intended outcome(s) of its information security management system.

NOTE Determining these issues refers to establishing the external and internal context of the organization

[5]
considered in Clause 5.3 of ISO 31000:2009 .
3.1
asset
anything that has value to the organization
[SOURCE: ISO/IEC 13335-1:2004]
4.2 Understanding the needs and expectations of interested parties
The organization shall determine:

a) interested parties that are relevant to the information security management system; and

b) the requirements of these interested parties relevant to information security.

NOTE The requirements of interested parties may include legal and regulatory requirements and

contractual obligations.
3.2
availability
the property of being accessible and usable upon demand by an authorized entity
[SOURCE: ISO/IEC 13335-1:2004]
4.3 Determining the scope of the information security management system

The organization shall determine the boundaries and applicability of the information security

management system to establish its scope.
When determining this scope, the organization shall consider:
a) the external and internal issues referred to in 4.1;
b) the requirements referred to in 4.2; and

c) interfaces and dependencies between activities performed by the organization, and those that are

performed by other organizations.
The scope shall be available as documented information.
2 © ISO 2014 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/IEC 27001:redline:2014(E)
3.3
confidentiality

the property that information is not made available or disclosed to unauthorized individuals,

entities, or processes
[SOURCE: ISO/IEC 13335-1:2004]
4.4 Information security management system

The organization shall establish, implement, maintain and continually improve an information security

management system, in accordance with the requirements of this International Standard.

3.4
information security

preservation of confidentiality, integrity and availability of information; in addition, other properties

such as authenticity, accountability, non-repudiation and reliability can also be involved

[SOURCE: ISO/IEC 17799:2005]
3.5
information security event

an identified occurrence of a system, service or network state indicating a possible breach of information

security policy or failure of safeguards, or a previously unknown situation that may be security relevant

[SOURCE: ISO/IEC TR 18044:2004]
3.6
information security incident

a single or a series of unwanted or unexpected information security events that have a significant

probability of compromising business operations and threatening information security

[SOURCE: ISO/IEC TR 18044:2004]
3.7
information security management system
ISMS

that part of the overall management system, based on a business risk approach, to establish, implement,

operate, monitor, review, maintain and improve information security

Note 1 to entry: The management system includes organizational structure, policies, planning activities,

responsibilities, practices, procedures, processes and resources.
3.8
integrity
the property of safeguarding the accuracy and completeness of assets
[SOURCE: ISO/IEC 13335-1:2004]
3.9
residual risk
the risk remaining after risk treatment
[SOURCE: ISO/IEC Guide 73:2002]
3.10
risk acceptance
decision to accept a risk
[SOURCE: ISO/IEC Guide 73:2002]
© ISO 2014 – All rights reserved 3
---------------------- Page: 11 ------
...

ISO/IEC
27001
Information
technology
Security techniques
Information security
management systems
Requirements
Second edition
2013-10-01
---------------------- Page: 1 ----------------------
Our vision Our process

To be the world’s leading provider of high qual- Our standards are developed by experts

ity, globally relevant International Standards all over the world who work on a volunteer

through its members and stakeholders. or part-time basis. We sell International
Standards to recover the costs of organizing
this process and making standards widely
Our mission
available.
ISO develops high quality voluntary
Please respect our licensing terms and
International Standards that facilitate interna-
copyright to ensure this system remains
tional exchange of goods and services, support
independent.
sustainable and equitable economic growth,
If you would like to contribute to the devel-
promote innovation and protect health, safety
opment of ISO standards, please contact the
and the environment.
ISO Member Body in your country:
www.iso.org/iso/home/about/iso_mem-
bers.htm
This document has been prepared by:
Copyright protected document
ISO/IEC JTC 1, Information technology, SC 27,
IT Security techniques. All rights reserved. Unless otherwise speci-
fied, no part of this publication may be repro-
Committee members:
duced or utilized otherwise in any form or
ABNT, AENOR, AFNOR, ANSI, ASI, ASRO, BIS,
by any means, electronic or mechanical,
BSI, BSJ, CODINORM, CYS, DGN, DIN, DS, DSM,
including photocopy, or posting on the inter-
DTR, ESMA, EVS, GOST R, IANOR, ILNAS,
net or intranet, without prior permission.
IMANOR, INDECOPI, INN, IRAM, ISRM, JISC,
Permission can be requested from either ISO
KATS, KAZMEMST, KEBS, MSB, NBN, NEN,
at the address below or ISO’s member body
NSAI, PKN, SA, SABS, SAC, SCC, SFS, SII, SIS,
in the country of the requester:
SIST, SLSI, SN, SNV, SNZ, SPRING SG, SUTN,
© ISO/IEC 2013, Published in Switzerland
TISI, UNI, UNIT, UNMZ, (ISC)2, CCETT, Cloud
security alliance, ECBS, Ecma International,
ISO copyright office
ENISA, EPC, ISACA, ISSEA, ITU, Mastercard,
Case postale 56 • CH-1211 Geneva 20
Mastercard - Europe
Tel. +41 22 749 01 11
Fax. +41 22 749 09 47
This list reflects contributing members at the
E-mail copyright@iso.org
time of publication.
Web www.iso.org
Cover photo credit: ISO/CS, 2013
© ISO/IEC 2013 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 27001:2013
Executive summary
• Organizations of all types and sizes col- continually improving an information
lect, process, store and transmit infor- security management system.
mation in many forms. This information • It can be used by internal and external

is valuable to an organization’s business parties to assess the ability of an orga-

and operations. nization to meet its own information
• In today’s interconnected and mobile security requirements.
world, information is processed us- • Effective information security assures
ing systems and networks that employ management and other stakeholders

state-of-the-art technology. It is vital to that the organization’s assets are safe,

protect this information against both thereby acting as a business enabler.
deliberate and accidental threats and • Other International Standards in the
vulnerabilities. ISO/IEC 27000 family give complemen-
• ISO/IEC 27001 helps organizations to tary advice or requirements on other
keep secure both their information as- aspects of the overall process of manag-
sets and those of their customers. ing information security.
• It provides requirements for establish-
ing, implementing, maintaining and
© ISO/IEC 2013 – All rights reserved
---------------------- Page: 3 ----------------------
ISO/IEC 27001:2013
Contents Page

Our vision ....................................................................................................................................................................................................................................2

Our mission ...............................................................................................................................................................................................................................2

Our process ................................................................................................................................................................................................................................2

Copyright protected document .............................................................................................................................................................................2

Executive summary ...........................................................................................................................................................................................................3

Foreword ......................................................................................................................................................................................................................................6

0 Introduction ...........................................................................................................................................................................................................7

1 Scope ..............................................................................................................................................................................................................................8

2 Normative references ...................................................................................................................................................................................8

3 Terms and definitions ..................................................................................................................................................................................8

4 Context of the organization ....................................................................................................................................................................8

4.1 Understanding the organization and its context ....................................................................................................8

4.2 Understanding the needs and expectations of interested parties ...........................................................8

4.3 Determining the scope of the information security management system .......................................8

4.4 Information security management system ..................................................................................................................9

5 Leadership ...............................................................................................................................................................................................................9

5.1 Leadership and commitment ..................................................................................................................................................9

5.2 Policy ............................................................................................................................................................................................................9

5.3 Organizational roles, responsibilities and authorities.......................................................................................9

6 Planning ..................................................................................................................................................................................................................10

6.1 Actions to address risks and opportunities .............................................................................................................10

6.2 Information security objectives and planning to achieve them .............................................................11

7 Support ....................................................................................................................................................................................................................11

7.1 Resources ...............................................................................................................................................................................................11

7.2 Competence .........................................................................................................................................................................................11

7.3 Awareness .............................................................................................................................................................................................12

7.4 Communication ................................................................................................................................................................................12

7.5 Documented information .........................................................................................................................................................12

8 Operation ..............................................................................................................................................................................................................13

8.1 Operational planning and control ....................................................................................................................................13

8.2 Information security risk assessment...........................................................................................................................13

8.3 Information security risk treatment ..............................................................................................................................13

9 Performance evaluation ........................................................................................................................................................................13

9.1 Monitoring, measurement, analysis and evaluation .........................................................................................13

9.2 Internal audit ......................................................................................................................................................................................14

9.3 Management review .....................................................................................................................................................................14

10 Improvement .....................................................................................................................................................................................................14

10.1 Nonconformity and corrective action ...........................................................................................................................14

10.2 Continual improvement ............................................................................................................................................................14

Annex A (normative) Reference control objectives and controls ....................................................................................15

Bibliography .........................................................................................................................................................................................................................30

© ISO/IEC 2013 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 27001:2013
Foreword

ISO (the International Organization for The main task of the joint technical committee

Standardization) and IEC (the International is to prepare International Standards. Draft

Electrotechnical Commission) form the special- International Standards adopted by the joint

ized system for worldwide standardization. technical committee are circulated to national

National bodies that are members of ISO or IEC bodies for voting. Publication as an International

participate in the development of International Standard requires approval by at least 75 % of

Standards through technical committees estab- the national bodies casting a vote.

lished by the respective organization to deal
Attention is drawn to the possibility that some
with particular fields of technical activity. ISO
of the elements of this document may be the
and IEC technical committees collaborate in
subject of patent rights. ISO and IEC shall not
fields of mutual interest. Other international
be held responsible for identifying any or all
organizations, governmental and non-govern-
such patent rights.
mental, in liaison with ISO and IEC, also take
part in the work. In the field of information
ISO/IEC 27001 was prepared by Joint Technical
technology, ISO and IEC have established a joint
Committee ISO/IEC JTC 1, Information technol-
technical committee, ISO/IEC JTC 1.
ogy, Subcommittee SC 27, IT Security techniques.
International Standards are drafted in
This second edition cancels and replaces the
accordance with the rules given in the
first edition (ISO/IEC 27001:2005), which has
ISO/IEC Directives, Part 2.
been technically revised.
© ISO/IEC 2013 – All rights reserved
---------------------- Page: 5 ----------------------
ISO/IEC 27001:2013
Introduction
organization’s ability to meet the organization’s
0.1 General
own information security requirements.
This International Standard has been pre-
The order in which requirements are presented
pared to provide requirements for establishing,
in this International Standard does not reflect
implementing, maintaining and continually
their importance or imply the order in which
improving an information security management
they are to be implemented. The list items are
system. The adoption of an information security
enumerated for reference purpose only.
management system is a strategic decision for
an organization. The establishment and imple-
ISO/IEC 27000 describes the overview and the
mentation of an organization’s information
vocabulary of information security management
security management system is influenced
systems, referencing the information secu-
by the organization’s needs and objectives,
rity management system family of standards
security requirements, the organizational pro-
[2] [3]
(including ISO/IEC 27003 , ISO/IEC 27004
cesses used and the size and structure of the
[4]
and ISO/IEC 27005 ), with related terms and
organization. All of these influencing factors
definitions.
are expected to change over time.
The information security management system
preserves the confidentiality, integrity and
0.2 Compatibility with other
availability of information by applying a risk
management system standards
management process and gives confidence to
interested parties that risks are adequately
This International Standard applies the high-
managed.
level structure, identical sub-clause titles, iden-
tical text, common terms, and core definitions
It is important that the information security
defined in Annex SL of ISO/IEC Directives, Part
management system is part of and integrated
1, Consolidated ISO Supplement, and therefore
with the organization’s processes and overall
maintains compatibility with other manage-
management structure and that information
ment system standards that have adopted the
security is considered in the design of pro-
Annex SL.
cesses, information systems, and controls. It is
expected that an information security manage-
This common approach defined in the Annex SL
ment system implementation will be scaled in
will be useful for those organizations that
accordance with the needs of the organization.
choose to operate a single management system
that meets the requirements of two or more
This International Standard can be used by
management system standards.
internal and external parties to assess the
© ISO/IEC 2013 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC 27001:2013
outcome(s) of its information security manage-
1 Scope
ment system.
This International Standard specifies the
NOTE Determining these issues refers to
requirements for establishing, implement-
establishing the external and internal context
ing, maintaining and continually improving
of the organization considered in Clause 5.3 of
an information security management system
[5]
ISO 31000:2009 .
within the context of the organization. This
International Standard also includes require-
4.2 Understanding the needs
ments for the assessment and treatment of
information security risks tailored to the needs
and expectations of interested
of the organization. The requirements set out in
parties
this International Standard are generic and are
intended to be applicable to all organizations,
The organization shall determine:
regardless of type, size or nature. Excluding any
a) interested parties that are relevant to
of the requirements specified in Clauses 4 to 10
the information security management
is not acceptable when an organization claims
system; and
conformity to this International Standard.
b) the requirements of these interested
parties relevant to information security.
2 Normative references
NOTE The requirements of interested parties
The following documents, in whole or in part,
may include legal and regulatory requirements
are normatively referenced in this document
and contractual obligations.
and are indispensable for its application. For
dated references, only the edition cited applies.
4.3 Determining the scope of
For undated references, the latest edition of the
the information security man-
referenced document (including any amend-
ments) applies.
agement system
ISO/IEC 27000, Information technology —
The organization shall determine the bounda-
Security techniques — Information security man-
ries and applicability of the information security
agement systems — Overview and vocabulary
management system to establish its scope.
When determining this scope, the organization
3 Terms and definitions shall consider:
a) the external and internal issues referred
For the purposes of this document, the terms
to in 4.1;
and definitions given in ISO/IEC 27000 apply.
b) the requirements referred to in 4.2; and
4 Context of the organization
c) interfaces and dependencies between
activities performed by the organization,
and those that are performed by other
4.1 Understanding the organiza-
organizations.
tion and its context
The scope shall be available as documented
The organization shall determine external and
information.
internal issues that are relevant to its purpose
and that affect its ability to achieve the intended
© ISO/IEC 2013 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC 27001:2013
4.4 Information security man- 5.2 Policy
agement system
Top management shall establish an information
security policy that:
The organization shall establish, implement,
maintain and continually improve an informa-
a) is appropriate to the purpose of the
tion security management system, in accord-
organization;
ance with the requirements of this International
Standard. b) includes information security objectives
(see 6.2) or provides the framework for
setting information security objectives;
5 Leadership
c) includes a commitment to satisfy appli-
cable requirements related to informa-
5.1 Leadership and commitment
tion security; and
Top management shall demonstrate leadership
d) includes a commitment to continual
and commitment with respect to the informa-
improvement of the information security
tion security management system by: management system.
The information security policy shall:
a) ensuring the information security policy
and the information security objec-
e) be available as documented information;
tives are established and are compat-
ible with the strategic direction of the f) be communicated within the organiza-
organization;
tion; and
b) ensuring the integration of the infor-
g) be available to interested parties, as
mation security management system
appropriate.
requirements into the organization’s
processes;
5.3 Organizational roles,
c) ensuring that the resources needed for responsibilities and authorities
the information security management
Top management shall ensure that the respon-
system are available;
sibilities and authorities for roles relevant
d) communicating the importance of
to information security are assigned and
effective information security manage-
communicated.
ment and of conforming to the infor-
Top management shall assign the responsibility
mation security management system
and authority for:
requirements;
e) ensuring that the information secu-
a) ensuring that the information secu-
rity management system achieves its
rity management system conforms to
intended outcome(s);
the requirements of this International
Standard; and
f) directing and supporting persons to con-
tribute to the effectiveness of the infor-
b) reporting on the performance of the
mation security management system;
information security management sys-
tem to top management.
g) promoting continual improvement; and
NOTE Top management may also assign respon-
h) supporting other relevant management
sibilities and authorities for reporting performance
roles to demonstrate their leadership as
of the information security management system
it applies to their areas of responsibility.
within the organization.
© ISO/IEC 2013 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/IEC 27001:2013
c) identifies the information security risks:
6 Planning
1) apply the information security risk
assessment process to identify risks
6.1 Actions to address risks
associated with the loss of confiden-
and opportunities
tiality, integrity and availability for
information within the scope of the
6.1.1 General
information security management
system; and
When planning for the information security
management system, the organization shall
2) identify the risk owners;
consider the issues referred to in 4.1 and the
d) analyses the information security risks:
requirements referred to in 4.2 and determine
the risks and opportunities that need to be
1) assess the potential consequences
addressed to:
that would result if the risks identi-
fied in 6.1.2 c) 1) were to materialize;
a) ensure the information security manage-
2) assess the realistic likelihood of the
ment system can achieve its intended
occurrence of the risks identified in
outcome(s);
6.1.2 c) 1); and
b) prevent, or reduce, undesired effects;
3) determine the levels of risk;
and
e) evaluates the information security risks:
c) achieve continual improvement.
1) compare the results of risk analysis
The organization shall plan:
with the risk criteria established in
d) actions to address these risks and oppor-
6.1.2 a); and
tunities; and
2) prioritize the analysed risks for risk
e) how to
treatment.
1) integrate and implement the actions
The organization shall retain documented
into its information security man-
information about the information security
agement system processes; and
risk assessment process.
2) evaluate the effectiveness of these
actions. 6.1.3 Information security risk
treatment
6.1.2 Information security risk
The organization shall define and apply an
assessment
information security risk treatment process to:
The organization shall define and apply an infor-
a) select appropriate information security
mation security risk assessment process that:
risk treatment options, taking account of
the risk assessment results;
a) establishes and maintains information
security risk criteria that include:
b) determine all controls that are necessary
to implement the information security
1) the risk acceptance criteria; and
risk treatment option(s) chosen;
2) criteria for performing information
NOTE Organizations can design controls
security risk assessments;
as required, or identify them from any source.
b) ensures that repeated information secu-
rity risk assessments produce consistent, c) compare the controls determined in
valid and comparable results; 6.1.3 b) above with those in Annex A and
© ISO/IEC 2013 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC 27001:2013

verify that no necessary controls have c) take into account applicable information

been omitted; security requirements, and results from
risk assessment and risk treatment;
NOTE 1 Annex A contains a comprehensive
list of control objectives and controls. Users
d) be communicated; and
of this International Standard are directed to
e) be updated as appropriate.
Annex A to ensure that no necessary controls
are overlooked.
The organization shall retain documented infor-
mation on the information security objectives.
NOTE 2 Control objectives are implicitly
included in the controls chosen. The control
When planning how to achieve its informa-
objectives and controls listed in Annex A are
tion security objectives, the organization shall
not exhaustive and additional control objec-
determine:
tives and controls may be needed.
f) what will be done;
d) produce a Statement of Applicability
that contains the necessary controls (see
g) what resources will be required;
6.1.3 b) and c)) and justification for inclu-
h) who will be responsible;
sions, whether they are implemented or
not, and the justification for exclusions of
i) when it will be completed; and
controls from Annex A;
j) how the results will be evaluated.
e) formulate an information security risk
treatment plan; and
7 Support
f) obtain risk owners’ approval of the infor-
mation security risk treatment plan and
7.1 Resources
acceptance of the residual information
security risks.
The organization shall determine and provide
The organization shall retain documented
the resources needed for the establishment,

information about the information security implementation, maintenance and continual

risk treatment process. improvement of the information security man-
agement system.
NOTE The information security risk assess-
ment and treatment process in this International
7.2 Competence
Standard aligns with the principles and generic
[5]
guidelines provided in ISO 31000 .
The organization shall:
6.2 Information security objec- a) determine the necessary competence
of person(s) doing work under its con-
tives and planning to achieve
trol that affects its information security
them
performance;
The organization shall establish information
b) ensure that these persons are competent
security objectives at relevant functions and
on the basis of appropriate education,
levels.
training, or experience;
The information security objectives shall:
c) where applicable, take actions to acquire
the necessary competence, and evaluate
a) be consistent with the information secu-
the effectiveness of the actions taken;
rity policy;
and
b) be measurable (if practicable);
© ISO/IEC 2013 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/IEC 27001:2013
d) retain appropriate documented informa- b) documented information determined
tion as evidence of competence. by the organization as being necessary
for the effectiveness of the information
NOTE Applicable actions may include, for exam-
security management system.
ple: the provision of training to, the mentoring of,
or the re-assignment of current employees; or the
NOTE The extent of documented information
hiring or contracting of competent persons.
for an information security management system
can differ from one organization to another due
to:
7.3 Awareness
1) the size of organization and its type of
Persons doing work under the organization’s
activities, processes, products and services;
control shall be aware of:
2) the complexity of processes and their inter-
a) the information security policy; actions; and
3) the competence of persons.
b) their contribution to the effectiveness
of the information security manage-
ment system, including the benefits of
7.5.2 Creating and updating
improved information security perfor-
When creating and updating documented
mance; and
information the organization shall ensure
c) the implications of not conforming with
appropriate:
the information security management
system requirements. a) identification and description (e.g. a title,
date, author, or reference number);
7.4 Communication
b) format (e.g. language, software version,
graphics) and media (e.g. paper, elec-
The organization shall determine the need for
tronic); and
internal and external communications relevant
to the information security management sys-
c) review and approval for suitability and
tem including:
adequacy.
a) on what to communicate;
7.5.3 Control of documented
b) when to communicate;
information
c) with whom to communicate;
Documented information required by the infor-
mation security management system and by
d) who shall communicate; and
this International Standard shall be controlled
e) the processes by which communication
to ensure:
shall be effected.
a) it is available and suitable for use, where
and when it is needed; and
7.5 Documented information
b) it is adequately protected (e.g. from loss
7.5.1 General
of confidentiality, improper use, or loss
of integrity).
The organization’s information security man-
For the control of documented information,
agement system shall include:
the organization shall address the following
a) documented information required by
activities, as applicable:
this International Standard; and
c) d
...

INTERNATIONAL ISO/IEC
STANDARD 27001
Second edition
2013-10-01
Information technology — Security
techniques — Information security
management systems — Requirements
Technologies de l’information — Techniques de sécurité — Systèmes
de management de la sécurité de l’information — Exigences
Reference number
ISO/IEC 27001:2013(E)
ISO/IEC 2013
---------------------- Page: 1 ----------------------
ISO/IEC 27001:2013(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2013

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form

or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior

written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of

the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2013 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 27001:2013(E)
Contents Page

Foreword ........................................................................................................................................................................................................................................iv

0 Introduction ...............................................................................................................................................................................................................v

1 Scope ................................................................................................................................................................................................................................. 1

2 Normative references ...................................................................................................................................................................................... 1

3 Terms and definitions ..................................................................................................................................................................................... 1

4 Context of the organization ....................................................................................................................................................................... 1

4.1 Understanding the organization and its context ....................................................................................................... 1

4.2 Understanding the needs and expectations of interested parties .............................................................. 1

4.3 Determining the scope of the information security management system .......................................... 1

4.4 Information security management system ..................................................................................................................... 2

5 Leadership .................................................................................................................................................................................................................. 2

5.1 Leadership and commitment ..................................................................................................................................................... 2

5.2 Policy ............................................................................................................................................................................................................... 2

5.3 Organizational roles, responsibilities and authorities.......................................................................................... 3

6 Planning ......................................................................................................................................................................................................................... 3

6.1 Actions to address risks and opportunities ................................................................................................................... 3

6.2 Information security objectives and planning to achieve them ................................................................... 5

7 Support ........................................................................................................................................................................................................................... 5

7.1 Resources ..................................................................................................................................................................................................... 5

7.2 Competence ............................................................................................................................................................................................... 5

7.3 Awareness ................................................................................................................................................................................................... 5

7.4 Communication ...................................................................................................................................................................................... 6

7.5 Documented information ............................................................................................................................................................... 6

8 Operation ..................................................................................................................................................................................................................... 7

8.1 Operational planning and control .......................................................................................................................................... 7

8.2 Information security risk assessment................................................................................................................................. 7

8.3 Information security risk treatment .................................................................................................................................... 7

9 Performance evaluation ............................................................................................................................................................................... 7

9.1 Monitoring, measurement, analysis and evaluation ............................................................................................... 7

9.2 Internal audit ............................................................................................................................................................................................ 8

9.3 Management review ........................................................................................................................................................................... 8

10 Improvement ............................................................................................................................................................................................................ 9

10.1 Nonconformity and corrective action ................................................................................................................................. 9

10.2 Continual improvement .................................................................................................................................................................. 9

Annex A (normative) Reference control objectives and controls ........................................................................................10

Bibliography .............................................................................................................................................................................................................................23

© ISO/IEC 2013 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 27001:2013(E)
Foreword

ISO (the International Organization for Standardization) and IEC (the International Electrotechnical

Commission) form the specialized system for worldwide standardization. National bodies that are

members of ISO or IEC participate in the development of International Standards through technical

committees established by the respective organization to deal with particular fields of technical

activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international

organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the

work. In the field of information technology, ISO and IEC have established a joint technical committee,

ISO/IEC JTC 1.

International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.

The main task of the joint technical committee is to prepare International Standards. Draft International

Standards adopted by the joint technical committee are circulated to national bodies for voting.

Publication as an International Standard requires approval by at least 75 % of the national bodies

casting a vote.

Attention is drawn to the possibility that some of the elements of this document may be the subject of

patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.

ISO/IEC 27001 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,

Subcommittee SC 27, IT Security techniques.

This second edition cancels and replaces the first edition (ISO/IEC 27001:2005), which has been

technically revised.
iv © ISO/IEC 2013 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 27001:2013(E)
0 Introduction
0.1 General

This International Standard has been prepared to provide requirements for establishing, implementing,

maintaining and continually improving an information security management system. The adoption of an

information security management system is a strategic decision for an organization. The establishment

and implementation of an organization’s information security management system is influenced by the

organization’s needs and objectives, security requirements, the organizational processes used and the

size and structure of the organization. All of these influencing factors are expected to change over time.

The information security management system preserves the confidentiality, integrity and availability

of information by applying a risk management process and gives confidence to interested parties that

risks are adequately managed.

It is important that the information security management system is part of and integrated with the

organization’s processes and overall management structure and that information security is considered

in the design of processes, information systems, and controls. It is expected that an information security

management system implementation will be scaled in accordance with the needs of the organization.

This International Standard can be used by internal and external parties to assess the organization’s

ability to meet the organization’s own information security requirements.

The order in which requirements are presented in this International Standard does not reflect their

importance or imply the order in which they are to be implemented. The list items are enumerated for

reference purpose only.

ISO/IEC 27000 describes the overview and the vocabulary of information security management

systems, referencing the information security management system family of standards (including

[2] [3] [4]

ISO/IEC 27003 , ISO/IEC 27004 and ISO/IEC 27005 ), with related terms and definitions.

0.2 Compatibility with other management system standards

This International Standard applies the high-level structure, identical sub-clause titles, identical text,

common terms, and core definitions defined in Annex SL of ISO/IEC Directives, Part 1, Consolidated ISO

Supplement, and therefore maintains compatibility with other management system standards that have

adopted the Annex SL.

This common approach defined in the Annex SL will be useful for those organizations that choose to operate

a single management system that meets the requirements of two or more management system standards.

© ISO/IEC 2013 – All rights reserved v
---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO/IEC 27001:2013(E)
Information technology — Security techniques —
Information security management systems — Requirements
1 Scope

This International Standard specifies the requirements for establishing, implementing, maintaining

and continually improving an information security management system within the context of the

organization. This International Standard also includes requirements for the assessment and treatment

of information security risks tailored to the needs of the organization. The requirements set out in this

International Standard are generic and are intended to be applicable to all organizations, regardless

of type, size or nature. Excluding any of the requirements specified in Clauses 4 to 10 is not acceptable

when an organization claims conformity to this International Standard.
2 Normative references

The following documents, in whole or in part, are normatively referenced in this document and are

indispensable for its application. For dated references, only the edition cited applies. For undated

references, the latest edition of the referenced document (including any amendments) applies.

ISO/IEC 27000, Information technology — Security techniques — Information security management

systems — Overview and vocabulary
3 Terms and definitions

For the purposes of this document, the terms and definitions given in ISO/IEC 27000 apply.

4 Context of the organization
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 ability to achieve the intended outcome(s) of its information security management system.

NOTE Determining these issues refers to establishing the external and internal context of the organization

[5]
considered in Clause 5.3 of ISO 31000:2009 .
4.2 Understanding the needs and expectations of interested parties
The organization shall determine:

a) interested parties that are relevant to the information security management system; and

b) the requirements of these interested parties relevant to information security.

NOTE The requirements of interested parties may include legal and regulatory requirements and

contractual obligations.
4.3 Determining the scope of the information security management system

The organization shall determine the boundaries and applicability of the information security

management system to establish its scope.
© ISO/IEC 2013 – All rights reserved 1
---------------------- Page: 6 ----------------------
ISO/IEC 27001:2013(E)
When determining this scope, the organization shall consider:
a) the external and internal issues referred to in 4.1;
b) the requirements referred to in 4.2; and

c) interfaces and dependencies between activities performed by the organization, and those that are

performed by other organizations.
The scope shall be available as documented information.
4.4 Information security management system

The organization shall establish, implement, maintain and continually improve an information security

management system, in accordance with the requirements of this International Standard.

5 Leadership
5.1 Leadership and commitment

Top management shall demonstrate leadership and commitment with respect to the information

security management system by:

a) ensuring the information security policy and the information security objectives are established

and are compatible with the strategic direction of the organization;

b) ensuring the integration of the information security management system requirements into the

organization’s processes;

c) ensuring that the resources needed for the information security management system are available;

d) communicating the importance of effective information security management and of conforming to

the information security management system requirements;

e) ensuring that the information security management system achieves its intended outcome(s);

f) directing and supporting persons to contribute to the effectiveness of the information security

management system;
g) promoting continual improvement; and

h) supporting other relevant management roles to demonstrate their leadership as it applies to their

areas of responsibility.
5.2 Policy
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 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;
2 © ISO/IEC 2013 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC 27001:2013(E)
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 authorities for roles relevant to information

security are assigned and communicated.
Top management shall assign the responsibility and authority for:

a) ensuring that the information security management system conforms to the requirements of this

International Standard; and

b) reporting on the performance of the information security management system to top management.

NOTE Top management may also assign responsibilities and authorities for reporting performance of the

information security management system within the organization.
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:

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:
d) actions to address these risks and opportunities; and
e) how to

1) integrate and implement the actions into its information 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 security risk assessment process that:

a) establishes and maintains information security risk criteria that include:
1) the risk acceptance criteria; and
2) criteria for performing information security risk assessments;

b) ensures that repeated information security risk assessments produce consistent, valid and

comparable results;
© ISO/IEC 2013 – All rights reserved 3
---------------------- Page: 8 ----------------------
ISO/IEC 27001:2013(E)
c) identifies the information security risks:

1) apply the information security risk assessment process to identify risks associated with the loss

of confidentiality, integrity and availability for information within the scope of the information

security management system; and
2) identify the risk owners;
d) 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;

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;
e) evaluates the information security risks:

1) compare the results of risk analysis with the risk criteria established in 6.1.2 a); and

2) prioritize the analysed risks for risk treatment.

The organization shall retain documented information about the information security risk

assessment process.
6.1.3 Information security risk treatment

The organization shall define and apply an information security risk treatment process to:

a) select appropriate information security risk treatment options, taking account of the risk

assessment results;

b) determine all controls that are necessary to implement the information security risk treatment

option(s) chosen;

NOTE Organizations can design controls as required, or identify them from any source.

c) compare the controls determined in 6.1.3 b) above with those in Annex A and verify that no necessary

controls have been omitted;

NOTE 1 Annex A contains a comprehensive list of control objectives and controls. Users of this International

Standard are directed to Annex A to ensure that no necessary controls are overlooked.

NOTE 2 Control objectives are implicitly included in the controls chosen. The control objectives and

controls listed in Annex A are not exhaustive and additional control objectives and controls may be needed.

d) produce a Statement of Applicability that contains the necessary controls (see 6.1.3 b) and c)) and

justification for inclusions, whether they are implemented or not, and the justification for exclusions

of controls from Annex A;
e) formulate an information security risk treatment plan; and

f) obtain risk owners’ approval of the information security risk treatment plan and acceptance of the

residual information security risks.

The organization shall retain documented information about the information security risk treatment

process.

NOTE The information security risk assessment and treatment process in this International Standard aligns

[5]
with the principles and generic guidelines provided in ISO 31000 .
4 © ISO/IEC 2013 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC 27001:2013(E)
6.2 Information security objectives and planning to achieve them

The organization shall establish information security 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 requirements, and results from risk assessment

and risk treatment;
d) be communicated; and
e) be updated as appropriate.

The organization shall retain documented information on the information security objectives.

When planning how to achieve its information security objectives, the organization shall determine:

f) what will be done;
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 and continual improvement of the information security management system.

7.2 Competence
The organization shall:

a) determine the necessary competence of person(s) doing work under its control that affects its

information security performance;

b) ensure that these persons are competent on the basis of appropriate education, training, or experience;

c) where applicable, take actions to acquire the necessary competence, and evaluate the effectiveness

of the actions taken; and
d) retain appropriate documented information as evidence of competence.

NOTE Applicable actions may include, for example: the provision of training to, the mentoring of, or the re-

assignment of current employees; or the hiring or contracting of competent persons.

7.3 Awareness
Persons doing work under the organization’s control shall be aware of:
a) the information security policy;
© ISO/IEC 2013 – All rights reserved 5
---------------------- Page: 10 ----------------------
ISO/IEC 27001:2013(E)

b) their contribution to the effectiveness of the information security management system, including

the benefits of improved information security performance; and

c) the implications of not conforming with the information security management system requirements.

7.4 Communication

The organization shall determine the need for internal and external communications relevant to the

information security management system including:
a) on what to communicate;
b) when to communicate;
c) with whom to communicate;
d) who shall communicate; and
e) the processes by which communication shall be effected.
7.5 Documented information
7.5.1 General
The organization’s information security management system shall include:
a) documented information required by this International Standard; and

b) documented information determined by the organization as being necessary for the effectiveness of

the information security management system.

NOTE The extent of documented information for an information security management system can differ

from one organization to another due to:

1) the size of organization and its type of activities, processes, products and services;

2) the complexity of processes and their interactions; and
3) the competence of persons.
7.5.2 Creating and updating

When creating and updating documented information the organization shall ensure appropriate:

a) identification and description (e.g. a title, date, author, or reference number);

b) format (e.g. language, software version, graphics) and media (e.g. paper, electronic); and

c) review and approval for suitability and adequacy.
7.5.3 Control of documented information

Documented information required by the information security management system and by this

International Standard shall be controlled to ensure:
a) it is available and suitable for use, where and when it is needed; and

b) it is adequately protected (e.g. from loss of confidentiality, improper use, or loss of integrity).

6 © ISO/IEC 2013 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/IEC 27001:2013(E)

For the control of documented information, the organization shall address the following activities,

as applicable:
c) distribution, access, retrieval and use;
d) storage and preservation, including the preservation of legibility;
e) control of changes (e.g. version control); and
f) retention and disposition.

Documented information of external origin, determined by the organization to be necessary for

the planning and operation of the information security management system, shall be identified as

appropriate, and controlled.

NOTE Access implies a decision regarding the permission to view the documented information only, or the

permission and authority to view and change the documented information, etc.
8 Operation
8.1 Operational planning and control

The organization shall plan, implement and control the processes needed to meet information security

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 extent necessary to have confidence that

the processes have been carried out as planned.

The organization shall control planned changes and review the consequences of unintended changes,

taking action to mitigate any adverse effects, as necessary.

The organization shall ensure that outsourced processes are determined and controlled.

8.2 Information security risk assessment

The organization shall perform information security risk assessments at planned intervals or when

significant changes are proposed or occur, taking account of the criteria established in 6.1.2 a).

The organization shall retain documented information of the results of the information security

risk assessments.
8.3 Information security risk treatment
The organization shall implement the information security risk treatment plan.

The organization shall retain documented information of the 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 security management system.
The organization shall determine:

a) what needs to be monitored and measured, including information security processes and controls;

© ISO/IEC 2013 – All rights reserved 7
---------------------- Page: 12 ----------------------
ISO/IEC 27001:2013(E)

b) the methods for monitoring, measurement, analysis and evaluation, as applicable, to ensure

valid results;

NOTE The methods selected should produce comparable and reproducible results to be considered valid.

c) when the monitoring and measuring shall be performed;
d) who shall monitor and measure;

e) when the results from monitoring and measurement shall be analysed and evaluated; and

f) who shall analyse and evaluate these results.

The organization shall retain appropriate documented information as evidence of the monitoring and

measurement results.
9.2 Internal audit

The organization shall conduct internal audits at planned intervals to provide information on whether

the information security management system:
a) conforms to

1) the organization’s own requirements for its information security management system; and

2) the requirements of this International Standard;
b) is effectively implemented and maintained.
The organization shall:

c) plan, establish, implement and maintain an audit programme(s), including the frequency, methods,

responsibilities, planning requirements and
...

SLOVENSKI STANDARD
SIST ISO/IEC 27001:2013
01-november-2013

Informacijska tehnologija - Varnostne tehnike - Sistemi upravljanja informacijske

varnosti - Zahteve
Information technology -- Security techniques -- Information security management
systems -- Requirements

Technologies de l'information -- Techniques de sécurité -- Systèmes de management de

la sécurité de l'information -- Exigences
Ta slovenski standard je istoveten z: ISO/IEC 27001:2013
ICS:
35.040 Nabori znakov in kodiranje Character sets and
informacij information coding
SIST ISO/IEC 27001:2013 en,fr,de

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
SIST ISO/IEC 27001:2013
---------------------- Page: 2 ----------------------
SIST ISO/IEC 27001:2013
INTERNATIONAL ISO/IEC
STANDARD 27001
Second edition
2013-10-01
Information technology — Security
techniques — Information security
management systems — Requirements
Technologies de l’information — Techniques de sécurité — Systèmes
de management de la sécurité de l’information — Exigences
Reference number
ISO/IEC 27001:2013(E)
ISO/IEC 2013
---------------------- Page: 3 ----------------------
SIST ISO/IEC 27001:2013
ISO/IEC 27001:2013(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2013

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form

or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior

written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of

the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2013 – All rights reserved
---------------------- Page: 4 ----------------------
SIST ISO/IEC 27001:2013
ISO/IEC 27001:2013(E)
Contents Page

Foreword ........................................................................................................................................................................................................................................iv

0 Introduction ...............................................................................................................................................................................................................v

1 Scope ................................................................................................................................................................................................................................. 1

2 Normative references ...................................................................................................................................................................................... 1

3 Terms and definitions ..................................................................................................................................................................................... 1

4 Context of the organization ....................................................................................................................................................................... 1

4.1 Understanding the organization and its context ....................................................................................................... 1

4.2 Understanding the needs and expectations of interested parties .............................................................. 1

4.3 Determining the scope of the information security management system .......................................... 1

4.4 Information security management system ..................................................................................................................... 2

5 Leadership .................................................................................................................................................................................................................. 2

5.1 Leadership and commitment ..................................................................................................................................................... 2

5.2 Policy ............................................................................................................................................................................................................... 2

5.3 Organizational roles, responsibilities and authorities.......................................................................................... 3

6 Planning ......................................................................................................................................................................................................................... 3

6.1 Actions to address risks and opportunities ................................................................................................................... 3

6.2 Information security objectives and planning to achieve them ................................................................... 5

7 Support ........................................................................................................................................................................................................................... 5

7.1 Resources ..................................................................................................................................................................................................... 5

7.2 Competence ............................................................................................................................................................................................... 5

7.3 Awareness ................................................................................................................................................................................................... 5

7.4 Communication ...................................................................................................................................................................................... 6

7.5 Documented information ............................................................................................................................................................... 6

8 Operation ..................................................................................................................................................................................................................... 7

8.1 Operational planning and control .......................................................................................................................................... 7

8.2 Information security risk assessment................................................................................................................................. 7

8.3 Information security risk treatment .................................................................................................................................... 7

9 Performance evaluation ............................................................................................................................................................................... 7

9.1 Monitoring, measurement, analysis and evaluation ............................................................................................... 7

9.2 Internal audit ............................................................................................................................................................................................ 8

9.3 Management review ........................................................................................................................................................................... 8

10 Improvement ............................................................................................................................................................................................................ 9

10.1 Nonconformity and corrective action ................................................................................................................................. 9

10.2 Continual improvement .................................................................................................................................................................. 9

Annex A (normative) Reference control objectives and controls ........................................................................................10

Bibliography .............................................................................................................................................................................................................................23

© ISO/IEC 2013 – All rights reserved iii
---------------------- Page: 5 ----------------------
SIST ISO/IEC 27001:2013
ISO/IEC 27001:2013(E)
Foreword

ISO (the International Organization for Standardization) and IEC (the International Electrotechnical

Commission) form the specialized system for worldwide standardization. National bodies that are

members of ISO or IEC participate in the development of International Standards through technical

committees established by the respective organization to deal with particular fields of technical

activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international

organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the

work. In the field of information technology, ISO and IEC have established a joint technical committee,

ISO/IEC JTC 1.

International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.

The main task of the joint technical committee is to prepare International Standards. Draft International

Standards adopted by the joint technical committee are circulated to national bodies for voting.

Publication as an International Standard requires approval by at least 75 % of the national bodies

casting a vote.

Attention is drawn to the possibility that some of the elements of this document may be the subject of

patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.

ISO/IEC 27001 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,

Subcommittee SC 27, IT Security techniques.

This second edition cancels and replaces the first edition (ISO/IEC 27001:2005), which has been

technically revised.
iv © ISO/IEC 2013 – All rights reserved
---------------------- Page: 6 ----------------------
SIST ISO/IEC 27001:2013
ISO/IEC 27001:2013(E)
0 Introduction
0.1 General

This International Standard has been prepared to provide requirements for establishing, implementing,

maintaining and continually improving an information security management system. The adoption of an

information security management system is a strategic decision for an organization. The establishment

and implementation of an organization’s information security management system is influenced by the

organization’s needs and objectives, security requirements, the organizational processes used and the

size and structure of the organization. All of these influencing factors are expected to change over time.

The information security management system preserves the confidentiality, integrity and availability

of information by applying a risk management process and gives confidence to interested parties that

risks are adequately managed.

It is important that the information security management system is part of and integrated with the

organization’s processes and overall management structure and that information security is considered

in the design of processes, information systems, and controls. It is expected that an information security

management system implementation will be scaled in accordance with the needs of the organization.

This International Standard can be used by internal and external parties to assess the organization’s

ability to meet the organization’s own information security requirements.

The order in which requirements are presented in this International Standard does not reflect their

importance or imply the order in which they are to be implemented. The list items are enumerated for

reference purpose only.

ISO/IEC 27000 describes the overview and the vocabulary of information security management

systems, referencing the information security management system family of standards (including

[2] [3] [4]

ISO/IEC 27003 , ISO/IEC 27004 and ISO/IEC 27005 ), with related terms and definitions.

0.2 Compatibility with other management system standards

This International Standard applies the high-level structure, identical sub-clause titles, identical text,

common terms, and core definitions defined in Annex SL of ISO/IEC Directives, Part 1, Consolidated ISO

Supplement, and therefore maintains compatibility with other management system standards that have

adopted the Annex SL.

This common approach defined in the Annex SL will be useful for those organizations that choose to operate

a single management system that meets the requirements of two or more management system standards.

© ISO/IEC 2013 – All rights reserved v
---------------------- Page: 7 ----------------------
SIST ISO/IEC 27001:2013
---------------------- Page: 8 ----------------------
SIST ISO/IEC 27001:2013
INTERNATIONAL STANDARD ISO/IEC 27001:2013(E)
Information technology — Security techniques —
Information security management systems — Requirements
1 Scope

This International Standard specifies the requirements for establishing, implementing, maintaining

and continually improving an information security management system within the context of the

organization. This International Standard also includes requirements for the assessment and treatment

of information security risks tailored to the needs of the organization. The requirements set out in this

International Standard are generic and are intended to be applicable to all organizations, regardless

of type, size or nature. Excluding any of the requirements specified in Clauses 4 to 10 is not acceptable

when an organization claims conformity to this International Standard.
2 Normative references

The following documents, in whole or in part, are normatively referenced in this document and are

indispensable for its application. For dated references, only the edition cited applies. For undated

references, the latest edition of the referenced document (including any amendments) applies.

ISO/IEC 27000, Information technology — Security techniques — Information security management

systems — Overview and vocabulary
3 Terms and definitions

For the purposes of this document, the terms and definitions given in ISO/IEC 27000 apply.

4 Context of the organization
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 ability to achieve the intended outcome(s) of its information security management system.

NOTE Determining these issues refers to establishing the external and internal context of the organization

[5]
considered in Clause 5.3 of ISO 31000:2009 .
4.2 Understanding the needs and expectations of interested parties
The organization shall determine:

a) interested parties that are relevant to the information security management system; and

b) the requirements of these interested parties relevant to information security.

NOTE The requirements of interested parties may include legal and regulatory requirements and

contractual obligations.
4.3 Determining the scope of the information security management system

The organization shall determine the boundaries and applicability of the information security

management system to establish its scope.
© ISO/IEC 2013 – All rights reserved 1
---------------------- Page: 9 ----------------------
SIST ISO/IEC 27001:2013
ISO/IEC 27001:2013(E)
When determining this scope, the organization shall consider:
a) the external and internal issues referred to in 4.1;
b) the requirements referred to in 4.2; and

c) interfaces and dependencies between activities performed by the organization, and those that are

performed by other organizations.
The scope shall be available as documented information.
4.4 Information security management system

The organization shall establish, implement, maintain and continually improve an information security

management system, in accordance with the requirements of this International Standard.

5 Leadership
5.1 Leadership and commitment

Top management shall demonstrate leadership and commitment with respect to the information

security management system by:

a) ensuring the information security policy and the information security objectives are established

and are compatible with the strategic direction of the organization;

b) ensuring the integration of the information security management system requirements into the

organization’s processes;

c) ensuring that the resources needed for the information security management system are available;

d) communicating the importance of effective information security management and of conforming to

the information security management system requirements;

e) ensuring that the information security management system achieves its intended outcome(s);

f) directing and supporting persons to contribute to the effectiveness of the information security

management system;
g) promoting continual improvement; and

h) supporting other relevant management roles to demonstrate their leadership as it applies to their

areas of responsibility.
5.2 Policy
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 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;
2 © ISO/IEC 2013 – All rights reserved
---------------------- Page: 10 ----------------------
SIST ISO/IEC 27001:2013
ISO/IEC 27001:2013(E)
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 authorities for roles relevant to information

security are assigned and communicated.
Top management shall assign the responsibility and authority for:

a) ensuring that the information security management system conforms to the requirements of this

International Standard; and

b) reporting on the performance of the information security management system to top management.

NOTE Top management may also assign responsibilities and authorities for reporting performance of the

information security management system within the organization.
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:

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:
d) actions to address these risks and opportunities; and
e) how to

1) integrate and implement the actions into its information 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 security risk assessment process that:

a) establishes and maintains information security risk criteria that include:
1) the risk acceptance criteria; and
2) criteria for performing information security risk assessments;

b) ensures that repeated information security risk assessments produce consistent, valid and

comparable results;
© ISO/IEC 2013 – All rights reserved 3
---------------------- Page: 11 ----------------------
SIST ISO/IEC 27001:2013
ISO/IEC 27001:2013(E)
c) identifies the information security risks:

1) apply the information security risk assessment process to identify risks associated with the loss

of confidentiality, integrity and availability for information within the scope of the information

security management system; and
2) identify the risk owners;
d) 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;

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;
e) evaluates the information security risks:

1) compare the results of risk analysis with the risk criteria established in 6.1.2 a); and

2) prioritize the analysed risks for risk treatment.

The organization shall retain documented information about the information security risk

assessment process.
6.1.3 Information security risk treatment

The organization shall define and apply an information security risk treatment process to:

a) select appropriate information security risk treatment options, taking account of the risk

assessment results;

b) determine all controls that are necessary to implement the information security risk treatment

option(s) chosen;

NOTE Organizations can design controls as required, or identify them from any source.

c) compare the controls determined in 6.1.3 b) above with those in Annex A and verify that no necessary

controls have been omitted;

NOTE 1 Annex A contains a comprehensive list of control objectives and controls. Users of this International

Standard are directed to Annex A to ensure that no necessary controls are overlooked.

NOTE 2 Control objectives are implicitly included in the controls chosen. The control objectives and

controls listed in Annex A are not exhaustive and additional control objectives and controls may be needed.

d) produce a Statement of Applicability that contains the necessary controls (see 6.1.3 b) and c)) and

justification for inclusions, whether they are implemented or not, and the justification for exclusions

of controls from Annex A;
e) formulate an information security risk treatment plan; and

f) obtain risk owners’ approval of the information security risk treatment plan and acceptance of the

residual information security risks.

The organization shall retain documented information about the information security risk treatment

process.

NOTE The information security risk assessment and treatment process in this International Standard aligns

[5]
with the principles and generic guidelines provided in ISO 31000 .
4 © ISO/IEC 2013 – All rights reserved
---------------------- Page: 12 ----------------------
SIST ISO/IEC 27001:2013
ISO/IEC 27001:2013(E)
6.2 Information security objectives and planning to achieve them

The organization shall establish information security 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 requirements, and results from risk assessment

and risk treatment;
d) be communicated; and
e) be updated as appropriate.

The organization shall retain documented information on the information security objectives.

When planning how to achieve its information security objectives, the organization shall determine:

f) what will be done;
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 and continual improvement of the information security management system.

7.2 Competence
The organization shall:

a) determine the necessary competence of person(s) doing work under its control that affects its

information security performance;

b) ensure that these persons are competent on the basis of appropriate education, training, or experience;

c) where applicable, take actions to acquire the necessary competence, and evaluate the effectiveness

of the actions taken; and
d) retain appropriate documented information as evidence of competence.

NOTE Applicable actions may include, for example: the provision of training to, the mentoring of, or the re-

assignment of current employees; or the hiring or contracting of competent persons.

7.3 Awareness
Persons doing work under the organization’s control shall be aware of:
a) the information security policy;
© ISO/IEC 2013 – All rights reserved 5
---------------------- Page: 13 ----------------------
SIST ISO/IEC 27001:2013
ISO/IEC 27001:2013(E)

b) their contribution to the effectiveness of the information security management system, including

the benefits of improved information security performance; and

c) the implications of not conforming with the information security management system requirements.

7.4 Communication

The organization shall determine the need for internal and external communications relevant to the

information security management system including:
a) on what to communicate;
b) when to communicate;
c) with whom to communicate;
d) who shall communicate; and
e) the processes by which communication shall be effected.
7.5 Documented information
7.5.1 General
The organization’s information security management system shall include:
a) documented information required by this International Standard; and

b) documented information determined by the organization as being necessary for the effectiveness of

the information security management system.

NOTE The extent of documented information for an information security management system can differ

from one organization to another due to:

1) the size of organization and its type of activities, processes, products and services;

2) the complexity of processes and their interactions; and
3) the competence of persons.
7.5.2 Creating and updating

When creating and updating documented information the organization shall ensure appropriate:

a) identification and description (e.g. a title, date, author, or reference number);

b) format (e.g. language, software version, graphics) and media (e.g. paper, electronic); and

c) review and approval for suitability and adequacy.
7.5.3 Control of documented information

Documented information required by the information security management system and by this

International Standard shall be controlled to ensure:
a) it is available and suitable for use, where and when it is needed; and

b) it is adequately protected (e.g. from loss of confidentiality, improper use, or loss of integrity).

6 © ISO/IEC 2013 – All rights reserved
---------------------- Page: 14 ----------------------
SIST ISO/IEC 27001:2013
ISO/IEC 27001:2013(E)

For the control of documented information, the organization shall address the following activities,

as applicable:
c) distribution, access, retrieval and use;
d) storage and preservation, including the preservation of legibility;
e) control of changes (e.g. version control); and
f) retention and disposition.

Documented information of external origin, determined by the organization to be necessary for

the planning and operation of the information security management system, shall be identified as

appropriate, and controlled.

NOTE Access implies a decision regarding the permission to view the documented information only, or the

permission and authority to view and change the documented information, etc.
8 Operation
8.1 Operational planning and control

The organization shall plan, implement and control the processes needed to meet information security

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 extent necessary to have confidence that

the processes have been carried out as planned.

The organization shall control planned changes and review the consequences of unintended changes,

taking action to mitigate any adverse effects, as necessary.

The organization shall ensure that outsourced processes are determined and controlled.

8.2 Information security risk assessment

The organization shall perform information security risk assessments at planned intervals or when

significant changes are proposed or occur, taking account of the criteria established in 6.1.2 a).

The organization shall retain documented information of the results of the information security

risk assessments.
8.3 Information security risk treatment
The organization shall implement the information security risk treatment plan.

The organization shall retain documented information of the 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 security management system.
The organization shall determine:

a) what needs to be monitored and measured, including information security processes and controls;

...

NORME ISO/CEI
INTERNATIONALE 27001
Deuxième édition
2013-10-01
Technologies de l’information —
Techniques de sécurité — Systèmes
de management de la sécurité de
l’information — Exigences
Information technology — Security techniques — Information
security management systems — Requirements
Numéro de référence
ISO/CEI 27001:2013(F)
ISO/CEI 2013
---------------------- Page: 1 ----------------------
ISO/CEI 27001:2013(F)
DOCUMENT PROTÉGÉ PAR COPYRIGHT
© ISO/CEI 2013

Droits de reproduction réservés. Sauf indication contraire, aucune partie de cette publication ne peut être reproduite ni utilisée

sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie, l’affichage sur

l’internet ou sur un Intranet, sans autorisation écrite préalable. Les demandes d’autorisation peuvent être adressées à l’ISO à

l’adresse ci-après ou au comité membre de l’ISO dans le pays du demandeur.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Version française parue en 2013
Publié en Suisse
ii © ISO/CEI 2013 – Tous droits réservés
---------------------- Page: 2 ----------------------
ISO/CEI 27001:2013(F)
Sommaire Page

Avant-propos ..............................................................................................................................................................................................................................iv

0 Introduction ...............................................................................................................................................................................................................v

1 Domaine d’application ................................................................................................................................................................................... 1

2 Références normatives ................................................................................................................................................................................... 1

3 Termes et définitions ....................................................................................................................................................................................... 1

4 Contexte de l’organisation .......................................................................................................................................................................... 1

4.1 Compréhension de l’organisation et de son contexte............................................................................................ 1

4.2 Compréhension des besoins et des attentes des parties intéressées ...................................................... 1

4.3 Détermination du domaine d’application du système de management de la sécurité

de l’information ...................................................................................................................................................................................... 2

4.4 Système de management de la sécurité de l’information .................................................................................. 2

5 Leadership .................................................................................................................................................................................................................. 2

5.1 Leadership et engagement............................................................................................................................................................ 2

5.2 Politique ........................................................................................................................................................................................................ 2

5.3 Rôles, responsabilités et autorités au sein de l’organisation .......................................................................... 3

6 Planification .............................................................................................................................................................................................................. 3

6.1 Actions liées aux risques et opportunités ........................................................................................................................ 3

6.2 Objectifs de sécurité de l’information et plans pour les atteindre ............................................................. 5

7 Support ........................................................................................................................................................................................................................... 5

7.1 Ressources .................................................................................................................................................................................................. 5

7.2 Compétence ............................................................................................................................................................................................... 6

7.3 Sensibilisation ......................................................................................................................................................................................... 6

7.4 Communication ...................................................................................................................................................................................... 6

7.5 Informations documentées .......................................................................................................................................................... 6

8 Fonctionnement .................................................................................................................................................................................................... 7

8.1 Planification et contrôle opérationnels ............................................................................................................................. 7

8.2 Appréciation des risques de sécurité de l’information ........................................................................................ 8

8.3 Traitement des risques de sécurité de l’information ............................................................................................. 8

9 Évaluation des performances .................................................................................................................................................................. 8

9.1 Surveillance, mesures, analyse et évaluation ................................................................................................................ 8

9.2 Audit interne ............................................................................................................................................................................................. 8

9.3 Revue de direction ............................................................................................................................................................................... 9

10 Amélioration ............................................................................................................................................................................................................. 9

10.1 Non-conformité et actions correctives ............................................................................................................................... 9

10.2 Amélioration continue ...................................................................................................................................................................10

Annexe A (normative) Objectifs et mesures de référence ...........................................................................................................11

Bibliographie

...........................................................................................................................................................................................................................23

© ISO/CEI 2013 – Tous droits réservés iii
---------------------- Page: 3 ----------------------
ISO/CEI 27001:2013(F)
Avant-propos

L’ISO (Organisation internationale de normalisation) et la CEI (Commission électrotechnique

internationale) forment le système spécialisé de la normalisation mondiale. Les organismes nationaux

membres de l’ISO ou de la CEI participent au développement de Normes internationales par l’intermédiaire

des comités techniques créés par l’organisation concernée afin de s’occuper des domaines particuliers

de l’activité technique. Les comités techniques de l’ISO et de la CEI collaborent dans des domaines

d’intérêt commun. D’autres organisations internationales, gouvernementales et non gouvernementales,

en liaison avec l’ISO et la CEI participent également aux travaux. Dans le domaine des technologies de

l’information, l’ISO et la CEI ont créé un comité technique mixte, l’ISO/CEI JTC 1.

Les Normes internationales sont rédigées conformément aux règles données dans les Directives

ISO/CEI, Partie 2.

La tâche principale du comité technique mixte est d’élaborer les Normes internationales. Les projets de

Normes internationales adoptés par le comité technique mixte sont soumis aux organismes nationaux

pour vote. Leur publication comme Normes internationales requiert l’approbation de 75 % au moins des

organismes nationaux votants.

L’attention est appelée sur le fait que certains des éléments du présent document peuvent faire l’objet

de droits de propriété intellectuelle ou de droits analogues. L’ISO et la CEI ne sauraient être tenues pour

responsables de ne pas avoir identifié de tels droits de propriété et averti de leur existence.

L’ISO/CEI 27001 a été élaborée par le comité technique mixte ISO/CEI JTC 1, Technologies de l’information,

sous-comité SC 27, Techniques de sécurité des technologies de l’information.

Cette deuxième édition annule et remplace la première édition (ISO/CEI 27001:2005), qui a fait l’objet

d’une révision technique.
iv © ISO/CEI 2013 – Tous droits réservés
---------------------- Page: 4 ----------------------
ISO/CEI 27001:2013(F)
0 Introduction
0.1 Généralités

La présente Norme internationale a été élaborée pour fournir des exigences en vue de l’établissement,

de la mise en œuvre, de la tenue à jour et de l’amélioration continue d’un système de management de

la sécurité de l’information. L’adoption d’un système de management de la sécurité de l’information

relève d’une décision stratégique de l’organisation. L’établissement et la mise en œuvre d’un système

de management de la sécurité de l’information d’une organisation tiennent compte des besoins et des

objectifs de l’organisation, des exigences de sécurité, des processus organisationnels mis en œuvre, ainsi

que de la taille et de la structure de l’organisation. Tous ces facteurs d’influence sont appelés à évoluer

dans le temps.

Le système de management de la sécurité de l’information préserve la confidentialité, l’intégrité et la

disponibilité de l’information en appliquant un processus de gestion des risques et donne aux parties

intéressées l’assurance que les risques sont gérés de manière adéquate.

Il est important que le système de management de la sécurité de l’information fasse partie intégrante

des processus et de la structure de management d’ensemble de l’organisation et que la sécurité de

l’information soit prise en compte dans la conception des processus, des systèmes d’information et des

mesures. Il est prévu qu’un système de management de la sécurité de l’information évolue conformément

aux besoins de l’organisation.

La présente Norme internationale peut être utilisée par les parties internes et externes pour évaluer la

capacité de l’organisation à répondre à ses propres exigences en matière de sécurité de l’information.

L’ordre dans lequel les exigences sont présentées dans la présente Norme internationale ne reflète pas

leur importance, ni l’ordre dans lequel elles doivent être mises en œuvre. Les éléments des listes sont

énumérés uniquement à des fins de référence.

L’ISO/CEI 27000 décrit une vue d’ensemble et le vocabulaire des systèmes de management de la sécurité

de l’information, en se référant à la famille des normes du système de management de la sécurité de

[2] [3] [4]

l’information (incluant l’ISO/CEI 27003, l’ISO/CEI 27004 et l’ISO/CEI 27005 ) avec les termes et les

définitions qui s’y rapportent.
0.2 Compatibilité avec d’autres systèmes de management

La présente Norme internationale applique la structure de haut niveau, les titres de paragraphe

identiques, le texte, les termes communs et les définitions fondamentales définies dans l’Annexe SL des

Directives ISO/CEI, Partie 1, Supplément ISO consolidé, et, par conséquent, est compatible avec les autres

normes de systèmes de management qui se conforment à l’Annexe SL.

Cette approche commune définie dans l’Annexe SL sera utile aux organisations qui choisissent de mettre

en œuvre un système de management unique pour répondre aux exigences de deux ou plusieurs normes

de systèmes de management.
© ISO/CEI 2013 – Tous droits réservés v
---------------------- Page: 5 ----------------------
NORME INTERNATIONALE ISO/CEI 27001:2013(F)
Technologies de l’information — Techniques de
sécurité — Systèmes de management de la sécurité de
l’information — Exigences
1 Domaine d’application

La présente Norme internationale spécifie les exigences relatives à l’établissement, à la mise en œuvre,

à la mise à jour et à l’amélioration continue d’un système de management de la sécurité de l’information

dans le contexte d’une organisation. La présente Norme internationale comporte également des

exigences sur l’appréciation et le traitement des risques de sécurité de l’information, adaptées aux

besoins de l’organisation. Les exigences fixées dans la présente Norme internationale sont génériques et

prévues pour s’appliquer à toute organisation, quels que soient son type, sa taille et sa nature. Il n’est pas

admis qu’une organisation s’affranchisse de l’une des exigences spécifiées aux Articles 4 à 10 lorsqu’elle

revendique la conformité à la présente Norme internationale.
2 Références normatives

Les documents suivants, en tout ou partie, sont référencés de manière normative dans le présent

document et sont indispensables à son application. Pour les références datées, seule l’édition citée

s’applique. Pour les références non datées, la dernière édition du document de référence s’applique (y

compris les éventuels amendements).

ISO/CEI 27000, Technologies de l’information — Techniques de sécurité — Systèmes de management de la

sécurité de l’information — Vue d’ensemble et vocabulaire
3 Termes et définitions

Pour les besoins du présent document, les termes et définitions fournis dans la norme

ISO/CEI 27000 s’appliquent.
4 Contexte de l’organisation
4.1 Compréhension de l’organisation et de son contexte

L’organisation doit déterminer les enjeux externes et internes pertinents compte tenu de sa mission et

qui influent sur sa capacité à obtenir le(s) résultat(s) attendu(s) de son système de management de la

sécurité de l’information.

NOTE Déterminer ces enjeux revient à établir le contexte externe et interne de l’organisation étudié dans le

[5]
paragraphe 5.3 de l’ISO 31000:2009.
4.2 Compréhension des besoins et des attentes des parties intéressées
L’organisation doit déterminer:

a) les parties intéressées qui sont concernées par le système de management de la sécurité de

l’information; et

b) les exigences de ces parties intéressées concernant la sécurité de l’information.

NOTE Les exigences des parties intéressées peuvent inclure des exigences légales et réglementaires et des

obligations contractuelles.
© ISO/CEI 2013 – Tous droits réservés 1
---------------------- Page: 6 ----------------------
ISO/CEI 27001:2013(F)

4.3 Détermination du domaine d’application du système de management de la sécurité

de l’information

Pour établir le domaine d’application du système de management de la sécurité de l’information,

l’organisation doit en déterminer les limites et l’applicabilité.

Lorsqu’elle établit ce domaine d’application, l’organisation doit prendre en compte:

a) les enjeux externes et internes auxquels il est fait référence en 4.1;
b) les exigences auxquelles il est fait référence en 4.2; et

c) les interfaces et les dépendances existant entre les activités réalisées par l’organisation et celles

réalisées par d’autres organisations.

Le domaine d’application doit être disponible sous forme d’information documentée.

4.4 Système de management de la sécurité de l’information

L’organisation doit établir, mettre en œuvre, tenir à jour et améliorer continuellement un système

de management de la sécurité de l’information, conformément aux exigences de la présente Norme

internationale.
5 Leadership
5.1 Leadership et engagement

La direction doit faire preuve de leadership et affirmer son engagement en faveur du système de

management de la sécurité de l’information en:

a) s’assurant qu’une politique et des objectifs sont établis en matière de sécurité de l’information et

qu’ils sont compatibles avec l’orientation stratégique de l’organisation;

b) s’assurant que les exigences liées au système de management de la sécurité de l’information sont

intégrées aux processus métiers de l’organisation;

c) s’assurant que les ressources nécessaires pour le système de management de la sécurité de

l’information sont disponibles;

d) communiquant sur l’importance de disposer d’un management de la sécurité de l’information

efficace et de se conformer aux exigences du système de management de la sécurité de l’information;

e) s’assurant que le système de management de la sécurité de l’information produit le ou les

résultats escomptés;

f) orientant et soutenant les personnes pour qu’elles contribuent à l’efficacité du système de

management de la sécurité de l’information;
g) promouvant l’amélioration continue; et

h) aidant les autres managers concernés à faire également preuve de leadership dès lors que cela

s’applique à leurs domaines de responsabilités.
5.2 Politique
La direction doit établir une politique de sécurité de l’information qui:
a) est adaptée à la mission de l’organisation;
2 © ISO/CEI 2013 – Tous droits réservés
---------------------- Page: 7 ----------------------
ISO/CEI 27001:2013(F)

b) inclut des objectifs de sécurité de l’information (voir 6.2) ou fournit un cadre pour l’établissement

de ces objectifs;

c) inclut l’engagement de satisfaire aux exigences applicables en matière de sécurité de l’information; et

d) inclut l’engagement d’œuvrer pour l’amélioration continue du système de management de la sécurité

de l’information.
La politique de sécurité de l’information doit:
e) être disponible sous forme d’information documentée;
f) être communiquée au sein de l’organisation; et
g) être mise à la disposition des parties intéressées, le cas échéant.
5.3 Rôles, responsabilités et autorités au sein de l’organisation

La direction doit s’assurer que les responsabilités et autorités des rôles concernés par la sécurité de

l’information sont attribuées et communiquées au sein de l’organisation.
La direction doit désigner qui a la responsabilité et l’autorité de:

a) s’assurer que le système de management de la sécurité de l’information est conforme aux exigences

de la présente Norme internationale; et

b) rendre compte à la direction des performances du système de management de la sécurité de

l’information.

NOTE La direction peut également attribuer des responsabilités et autorités pour rendre compte des

performances du système de management de la sécurité de l’information au sein de l’organisation.

6 Planification
6.1 Actions liées aux risques et opportunités
6.1.1 Généralités

Lorsqu’elle conçoit son système de management de la sécurité de l’information, l’organisation doit

tenir compte des enjeux de 4.1 et des exigences de 4.2, et déterminer les risques et opportunités qui

nécessitent d’être abordés pour:

a) s’assurer que le système de management de la sécurité de l’information peut atteindre le ou les

résultats escomptés;
b) empêcher ou limiter les effets indésirables; et
c) appliquer une démarche d’amélioration continue.
L’organisation doit planifier:
d) les actions menées pour traiter ces risques et opportunités; et
e) la manière:

1) d’intégrer et de mettre en œuvre les actions au sein des processus du système de management

de la sécurité de l’information; et
2) d’évaluer l’efficacité de ces actions.
© ISO/CEI 2013 – Tous droits réservés 3
---------------------- Page: 8 ----------------------
ISO/CEI 27001:2013(F)
6.1.2 Appréciation des risques de sécurité de l’information

L’organisation doit définir et appliquer un processus d’appréciation des risques de sécurité de

l’information qui:

a) établit et tient à jour les critères de risque de sécurité de l’information incluant:

1) les critères d’acceptation des risques;

2) les critères de réalisation des appréciations des risques de sécurité de l’information;

b) s’assure que la répétition de ces appréciations des risques produit des résultats cohérents, valides

et comparables;
c) identifie les risques de sécurité de l’information:

1) applique le processus d’appréciation des risques de sécurité de l’information pour identifier les

risques liés à la perte de confidentialité, d’intégrité et de disponibilité des informations entrant

dans le domaine d’application du système de management de la sécurité de l’information; et

2) identifie les propriétaires des risques;
d) analyse les risques de sécurité de l’information:

1) apprécie les conséquences potentielles dans le cas où les risques identifiés en 6.1.2 c) 1) se

concrétisaient;

2) procède à une évaluation réaliste de la vraisemblance d’apparition des risques identifiés en

6.1.2 c) 1); et
3) détermine les niveaux des risques;
e) évalue les risques de sécurité de l’information:

1) compare les résultats d’analyse des risques avec les critères de risque déterminés en 6.1.2 a); et

2) priorise les risques analysés pour le traitement des risques.

L’organisation doit conserver des informations documentées sur le processus d’appréciation des risques

de sécurité de l’information.
6.1.3 Traitement des risques de sécurité de l’information

L’organisation doit définir et appliquer un processus de traitement des risques de sécurité de

l’information pour:

a) choisir les options de traitement des risques appropriées, en tenant compte des résultats de

l’appréciation des risques;

b) déterminer toutes les mesures nécessaires à la mise en œuvre de(s) (l’)option(s) de traitement des

risques de sécurité de l’information choisie(s);

NOTE Les organisations peuvent concevoir ces mesures, le cas échéant, ou bien les identifier à partir de

n’importe quelle source.

c) comparer les mesures déterminées ci-dessus en 6.1.3 b) avec celles de l’Annexe A et vérifier

qu’aucune mesure nécessaire n’a été omise;

NOTE 1 L’Annexe A comporte une liste détaillée d’objectifs et de mesures. Les utilisateurs de la présente

Norme internationale sont invités à se reporter à l’Annexe A pour s’assurer qu’aucune mesure nécessaire n’a

été négligée.

NOTE 2 Les objectifs sont implicitement inclus dans les mesures choisies. Les objectifs et les mesures énumérés

dans l’Annexe A ne sont pas exhaustifs et des objectifs et des mesures additionnels peuvent s’avérer nécessaires.

4 © ISO/CEI 2013 – Tous droits réservés
---------------------- Page: 9 ----------------------
ISO/CEI 27001:2013(F)

d) produire une déclaration d’applicabilité contenant les mesures nécessaires (voir 6.1.3 b) et c)) et

la justification de leur insertion, le fait qu’elles soient mises en œuvre ou non, et la justification de

l’exclusion de mesures de l’Annexe A;
e) élaborer un plan de traitement des risques de sécurité de l’information; et

f) obtenir des propriétaires des risques l’approbation du plan de traitement des risques et l’acceptation

des risques résiduels de sécurité de l’information.

L’organisation doit conserver des informations documentées sur le processus de traitement des risques

de sécurité de l’information.

NOTE L’appréciation des risques de sécurité de l’information et le processus de traitement figurant dans

la présente Norme internationale s’alignent sur les principes et les lignes directrices générales fournies dans

[5]
l’ISO 31000.
6.2 Objectifs de sécurité de l’information et plans pour les atteindre

L’organisation doit établir, aux fonctions et niveaux concernés, des objectifs de sécurité de l’information.

Les objectifs de sécurité de l’information doivent:
a) être cohérents avec la politique de sécurité de l’information;
b) être mesurables (si possible);

c) tenir compte des exigences applicables à la sécurité de l’information, et des résultats de l’appréciation

et du traitement des risques;
d) être communiqués; et
e) être mis à jour quand cela est approprié.

L’organisation doit conserver des informations documentées sur les objectifs liés à la sécurité de

l’information.

Lorsqu’elle planifie la façon d’atteindre ses objectifs de sécurité de l’information, l’organisation doit

déterminer:
f) ce qui sera fait;
g) les ressources qui seront nécessaires;
h) qui sera responsable;
i) les échéances; et
j) la façon dont les résultats seront évalués.
7 Support
7.1 Ressources

L’organisation doit identifier et fournir les ressources nécessaires à l’établissement, la mise en œuvre, la

tenue à jour et l’amélioration continue du système de management de la sécurité de l’information.

© ISO/CEI 2013 – Tous droits réservés 5
---------------------- Page: 10 ----------------------
ISO/CEI 27001:2013(F)
7.2 Compétence
L’organisation doit:

a) déterminer les compétences nécessaires de la ou des personnes effectuant, sous son contrôle, un

travail qui a une incidence sur les performances de la sécurité de l’information;

b) s’assurer que ces personnes sont compétentes sur la base d’une formation initiale ou continue ou

d’une expérience appropriée;

c) le cas échéant, mener des actions pour acquérir les compétences nécessaires et évaluer l’efficacité

des actions entreprises; et

d) conserver des informations documentées appropriées comme preuves de ces compétences.

NOTE Les actions envisageables peuvent notamment inclure la formation, l’encadrement ou la réaffectation

du personnel actuellement employé ou le recrutement, direct ou en sous-traitance, de personnes compétentes.

7.3 Sensibilisation
Les personnes effectuant un travail sous le contrôle de l’organisation doivent:
a) être sensibilisées à la politique de sécurité de l’information;

b) avoir conscience de leur contribution à l’efficacité du système de management de la sécurité de

l’information, y compris aux effets positifs d’une amélioration des performances de la sécurité de

l’information; et

c) avoir conscience des implications de toute non-conformité aux exigences requises par le système de

management de la sécurité de l’information.
7.4 Communication

L’organisation doit déterminer les besoins de communication interne et externe pertinents pour le

système de management de la sécurité de l’information, et notamment:
a) sur quels sujets communiquer;
b) à quels moments communiquer;
c) avec qui communiquer;
d) qui doit communiquer; et
e) les processus par lesquels la communication doit s’effectuer.
7.5 Informations documentées
7.5.1 Généralités

Le système de management de la sécurité de l’information de l’organisation doit inclure:

a) les informations documentées exigées par la présente Norme internationale; et

b) les informations documentées que l’organisation juge nécessaires à l’efficacité du système de

management de la sécurité de l’information.

NOTE L’étendue des informations documentées dans le cadre d’un système de management de la sécurité de

l’information peut différer selon l’organisation en fonction de:

1) la taille de l’organisation, ses domaines d’activité et ses processus, produits et services;

6 © ISO/CEI 2013 – Tous droits réservés
---------------------- Page: 11 ----------------------
ISO/CEI 27001:2013(F)
2) la complexité des processus et de leurs interactions; et
3) la compétence des personnes.
7.5.2 Création et mise à jour

Quand elle crée et met à jour ses informations documentées, l’organisation doit s’assurer que les éléments

suivants sont appropriés:

a) identification et description (par exemple titre, date, auteur, numéro de référence);

b) format (par exemple langue, version logicielle, graphiques) et support (par exemple, papier,

électronique); et
c) examen et approbation du caractère approprié et pertinent des informations.
7.5.3 Maîtrise des informations documentées

Les informations documentées exigées par le système de management de la sécurité de l’information et

par la présente Norme internationale doivent être contrôlées pour s’assurer:

a) qu’elles sont disponibles et conviennent à l’utilisation, où et quand elles sont nécessaires; et

b) qu’elles sont correctement protégées (par exemple, de toute perte de confidentialité, utilisation

inappropriée ou perte d’intégrité).

Pour contrôler les informations documentées, l’organisation doit traiter des activités suivantes, quand

elles lui sont applicables:
c) distribution, accès, récupération et utilisation;
d) stockage et conservation, y compris préservation de la lisibilité;
e) contrôle des modifications (par exemple, contrôle des versions); et
f) durée de conservation et suppression.

Les informations documentées d’origine externe que l’organisation juge nécessaires à la planification et

au fonctionnement du système de management de la sécurité de l’information doivent être identifiées

comme il convient et
...

SLOVENSKI SIST ISO/IEC 27001
STANDARD
november 2013
Informacijska tehnologija – Varnostne tehnike – Sistemi upravljanja
informacijske varnosti – Zahteve
Information technology – Security techniques – Information security management
systems – Requirements
Technologies de l'information – Techniques de sécurité – Systèmes de
management de la sécurité de l'information – Exigences
Referenčna oznaka
ICS 35.040 SIST ISO/IEC 27001:2013 (sl)
Nadaljevanje na straneh 2 do 27

© 2014-01. Slovenski inštitut za standardizacijo. Razmnoževanje ali kopiranje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
SIST ISO/IEC 27001 : 2013
NACIONALNI UVOD

Standard SIST ISO/IEC 27001 (sl), Informacijska tehnologija – Varnostne tehnike – Sistemi

upravljanja informacijske varnosti – Zahteve, 2013, ima status slovenskega standarda in je istoveten

mednarodnemu standardu ISO/IEC 27001 (en), Information technology – Security techniques –

Information security management systems – Requirements, druga izdaja, 2013-10-01.

Ta standard preklicuje in nadomešča standard SIST ISO/IEC 27001:2010.
NACIONALNI PREDGOVOR

Mednarodni standard ISO/IEC 27001:2013 je pripravil pododbor združenega tehničnega odbora

Mednarodne organizacije za standardizacijo in Mednarodne elektrotehniške komisije ISO/IEC JTC

1/SC 27 Varnostne tehnike v informacijski tehnologiji.

Slovenski standard SIST ISO/IEC 27001:2013 je prevod mednarodnega standarda ISO/IEC

27001:2013. Slovenski standard SIST ISO/IEC 27001:2013 je pripravil tehnični odbor SIST/TC ITC

Informacijska tehnologija. V primeru spora glede besedila slovenskega prevoda je odločilen izvirni

mednarodni standard v angleškem jeziku.

Odločitev za izdajo tega standarda je dne 25. oktobra 2013 sprejel SIST/TC ITC Informacijska

tehnologija.
ZVEZA S STANDARDI

SIST ISO/IEC 27000 Informacijska tehnologija – Varnostne tehnike – Sistemi upravljanja

informacijske varnosti – Pregled in izrazoslovje
OSNOVA ZA IZDAJO STANDARDA
– privzem standarda ISO/IEC 27001:2013
PREDHODNA IZDAJA

– ISO/IEC 27001:2010, Informacijska tehnologija – Varnostne tehnike – Sistemi upravljanja

informacijske varnosti – Zahteve
OPOMBI

– Povsod, kjer se v besedilu standarda uporablja izraz “mednarodni standard”, v SIST ISO/IEC

27001:2013 to pomeni “slovenski standard”.
– Nacionalni uvod in nacionalni predgovor nista sestavni del standarda.
---------------------- Page: 2 ----------------------
SIST ISO/IEC 27001 : 2013
VSEBINA Stran

Predgovor .................................................................................................................................................4

0 Uvod ......................................................................................................................................................5

0.1 Splošno...............................................................................................................................................5

0.2 Združljivost z drugimi standardi za sisteme upravljanja.....................................................................5

1 Področje uporabe ..................................................................................................................................6

2 Zveza s standardi ..................................................................................................................................6

3 Izrazi in definicije ...................................................................................................................................6

4 Okvir organizacije ..................................................................................................................................6

4.1 Razumevanje organizacije in njenega okvira.....................................................................................6

4.2 Razumevanje potreb in pričakovanj zainteresiranih strank................................................................6

4.3 Določitev obsega sistema upravljanja informacijske varnosti ............................................................6

4.4 Sistem upravljanja informacijske varnosti ..........................................................................................7

5 Voditeljstvo ............................................................................................................................................7

5.1 Voditeljstvo in zavezanost ..................................................................................................................7

5.2 Politika ................................................................................................................................................7

5.3 Organizacijske vloge, odgovornosti in pooblastila .............................................................................7

6 Načrtovanje ...........................................................................................................................................8

6.1 Ukrepi za obravnavanje tveganj in priložnosti....................................................................................8

6.2 Cilji informacijske varnosti in načrtovanje njihovega doseganja ........................................................9

7 Podpora .............................................................................................................................................. 10

7.1 Viri.................................................................................................................................................... 10

7.2 Kompetentnost ................................................................................................................................ 10

7.3 Ozaveščenost.................................................................................................................................. 10

7.4 Sporočanje ...................................................................................................................................... 10

7.5 Dokumentirane informacije.............................................................................................................. 10

8 Delovanje............................................................................................................................................ 11

8.1 Načrtovanje in obvladovanje delovanja........................................................................................... 11

8.2 Ocenjevanje tveganj informacijske varnosti .................................................................................... 11

8.3 Obravnavanje tveganj informacijske varnosti.................................................................................. 12

9 Vrednotenje ........................................................................................................................................ 12

9.1 Spremljanje, merjenje, analiziranje in vrednotenje.......................................................................... 12

9.2 Notranja presoja .............................................................................................................................. 12

9.3 Vodstveni pregled............................................................................................................................ 13

10 Izboljševanje..................................................................................................................................... 13

10.1 Neskladnosti in popravni ukrepi .................................................................................................... 13

10.2 Nenehno izboljševanje .................................................................................................................. 14

Dodatek A (normativni): Cilji kontrol in kontrole .................................................................................... 15

Literatura................................................................................................................................................ 27

---------------------- Page: 3 ----------------------
SIST ISO/IEC 27001 : 2013
Predgovor

ISO (Mednarodna organizacija za standardizacijo) in IEC (Mednarodna elektrotehniška komisija)

tvorita specializiran sistem za svetovno standardizacijo. Nacionalni organi, ki so člani ISO ali IEC,

sodelujejo pri pripravi mednarodnih standardov prek tehničnih odborov, ki jih za obravnavanje

določenih strokovnih področij ustanovi ustrezna organizacija. Tehnični odbori ISO in IEC sodelujejo na

področjih skupnega interesa. Pri delu sodelujejo tudi druge mednarodne, vladne in nevladne

organizacije, povezane z ISO in IEC. Na področju informacijske tehnologije sta ISO in IEC vzpostavila

združeni tehnični odbor ISO/IEC JTC 1.

Mednarodni standardi so pripravljeni v skladu s pravili, podanimi v 2. delu Direktiv ISO/IEC.

Glavna naloga tehničnih odborov je priprava mednarodnih standardov. Osnutki mednarodnih

standardov, ki jih sprejmejo tehnični odbori, se pošljejo vsem članom v glasovanje. Za objavo

mednarodnega standarda je treba pridobiti soglasje najmanj 75 odstotkov članov, ki se udeležijo

glasovanja.

Opozoriti je treba na možnost, da je lahko nekaj elementov tega mednarodnega standarda predmet

patentnih pravic. ISO in IEC ne prevzemata odgovornosti za prepoznavanje katerih koli ali vseh takih

patentnih pravic.

ISO/IEC 27001 je pripravil združeni tehnični odbor JTC ISO/IEC 1 Informacijska tehnologija, pododbor

SC 27 Varnostne tehnike IT.

Druga izdaja preklicuje in nadomešča prvo izdajo (ISO/IEC 27001:2005), ki je tehnično revidirana.

---------------------- Page: 4 ----------------------
SIST ISO/IEC 27001 : 2013
0 Uvod
0.1 Splošno

Ta mednarodni standard je bil pripravljen, da zagotovi zahteve za vzpostavitev, izvajanje, vzdrževanje

in nenehno izboljševanje sistema upravljanja informacijske varnosti. Privzem sistema upravljanja

informacijske varnosti je strateška odločitev za organizacijo. Na vzpostavitev in izvedbo sistema

upravljanja informacijske varnosti organizacije vplivajo potrebe in cilji organizacije, varnostne zahteve,

uporabljeni organizacijski procesi ter velikost in struktura organizacije. Vsi ti dejavniki, ki vplivajo na

sistem, se bodo po pričakovanjih s časom spreminjali.

Sistem upravljanja informacijske varnosti ohranja zaupnost, celovitost in razpoložljivost informacij z

uporabo procesa za obvladovanje tveganj ter zainteresiranim strankam vzbuja zaupanje, da se

tveganja ustrezno obvladujejo.

Pomembno je, da je sistem upravljanja informacijske varnosti del procesov organizacije in splošne

strukture vodenja in je integriran z njimi ter da je informacijska varnost sprejeta pri zasnovi procesov,

informacijskih sistemov in kontrol. Pričakuje se, da bo izvajanje sistema upravljanja informacijske

varnosti skladno s potrebami organizacije.

Ta mednarodni standard lahko uporabljajo notranje ali zunanje stranke za ocenjevanje sposobnosti

organizacije izpolnjevati lastne zahteve informacijske varnosti.

Vrstni red predstavitve zahtev v tem mednarodnem standardu ne odraža njihovega pomena ali

nakazuje vrstnega reda, v katerem naj bi se izvedle. Elementi na seznamu so oštevilčeni zgolj za

namene sklicevanja.

Standard ISO/IEC 27000 podaja pregled in izrazje sistemov upravljanja informacijske varnosti, pri

čemer se sklicuje na skupino standardov za sisteme upravljanja informacijske varnosti (vključno s

[2] [3] [4]

standardi ISO/IEC 27003 , ISO/IEC 27004 in ISO/IEC 27005 ) s povezanimi izrazi in definicijami.

0.2 Združljivost z drugimi standardi za sisteme upravljanja

Ta mednarodni standard uporablja strukturo visoke ravni, enake naslove podtočk, enako besedilo,

splošne izraze in temeljne definicije iz dodatka SL k Direktivam ISO/IEC, 1. del, konsolidirana priloga

ISO, zato ohranja združljivost z drugimi standardi za sisteme upravljanja, ki so sprejeli dodatek SL.

Ta splošni pristop iz dodatka SL bo koristil tistim organizacijam, ki so izbrale vzpostavitev enotnega

sistema upravljanja, ki izpolnjuje zahteve iz dveh ali več standardov za sisteme upravljanja.

---------------------- Page: 5 ----------------------
SIST ISO/IEC 27001 : 2013
Informacijska tehnologija – Varnostne tehnike – Sistemi upravljanja
informacijske varnosti – Zahteve
1 Področje uporabe

Ta mednarodni standard določa zahteve za vzpostavitev, izvajanje, vzdrževanje in nenehno

izboljševanje sistema upravljanja informacijske varnosti v okviru organizacije. Zajema tudi zahteve za

ocenjevanje in obravnavanje tveganj informacijske varnosti, ki so prilagojene potrebam organizacije.

Zahteve, postavljene v tem mednarodnem standardu, so generične in so namenjene uporabi v vseh

organizacijah ne glede na vrsto, velikost ali naravo. Izključevanje katere koli zahteve, določene v

točkah 4 do 10, ni sprejemljivo, kadar organizacija zagotavlja skladnost s tem mednarodnim

standardom.
2 Zveza s standardi

Ta dokument se v celoti ali v delih normativno sklicuje na naslednje dokumente, ki so nepogrešljivi pri

njegovi uporabi. Pri datiranih sklicevanjih se uporablja zgolj navedena izdaja. Pri nedatiranih sklicevanjih

se uporablja zadnja izdaja navedenega dokumenta (vključno z dopolnili).

ISO/IEC 27000 Informacijska tehnologija – Varnostne tehnike – Sistemi upravljanja

informacijske varnosti – Pregled in izrazoslovje
3 Izrazi in definicije

V tem dokumentu so uporabljeni izrazi in definicije, ki so podani v standardu ISO/IEC 27000.

4 Okvir organizacije
4.1 Razumevanje organizacije in njenega okvira

Organizacija mora določiti zunanja in notranja vprašanja, ki so pomembna za njen namen ter vplivajo

na njeno sposobnost doseganja pričakovanega(-ih) rezultata(-ov) njenega sistema upravljanja

informacijske varnosti.

OPOMBA: Določanje teh vprašanj se nanaša na opredelitev zunanjega in notranjega okvira organizacije iz točke 5.3

[5]
standarda ISO 31000:2009 .
4.2 Razumevanje potreb in pričakovanj zainteresiranih strank
Organizacija mora določiti:

a) zainteresirane stranke, ki so pomembne za sistem upravljanja informacijske varnosti, in

b) zahteve teh zainteresiranih strank, ki so pomembne za informacijsko varnost.

OPOMBA: Zahteve zainteresiranih strank lahko vključujejo zahteve zakonodaje in predpisov ter pogodbene obveznosti.

4.3 Določitev obsega sistema upravljanja informacijske varnosti

Organizacija mora določiti meje in uporabnost sistema upravljanja informacijske varnosti za

opredelitev njegovega obsega.
Organizacija pri določanju tega obsega upošteva:
a) zunanja in notranja vprašanja iz točke 4.1,
b) zahteve iz točke 4.2 ter

c) povezave in odvisnosti med aktivnostmi, ki jih izvaja organizacija, in aktivnostmi, ki jih izvajajo

druge organizacije.
---------------------- Page: 6 ----------------------
SIST ISO/IEC 27001 : 2013
Obseg mora biti na voljo v obliki dokumentiranih informacij.
4.4 Sistem upravljanja informacijske varnosti

Organizacija mora vzpostaviti, izvajati, vzdrževati in nenehno izboljševati sistem upravljanja

informacijske varnosti v skladu z zahtevami tega mednarodnega standarda.
5 Voditeljstvo
5.1 Voditeljstvo in zavezanost

Najvišje vodstvo mora izkazovati sposobnost vodenja in zavezanost v zvezi s sistemom upravljanja

informacijske varnosti z:

a) zagotavljanjem informacijske varnostne politike in postavljanjem ciljev informacijske varnosti, ki

so združljivi s strateško usmeritvijo organizacije;

b) zagotavljanjem vključitve zahtev sistema upravljanja informacijske varnosti v procese

organizacije;

c) zagotavljanjem razpoložljivosti virov, potrebnih za sistem upravljanja informacijske varnosti;

d) sporočanjem pomena uspešnega upravljanja informacijske varnosti in izpolnjevanjem zahtev

sistema upravljanja informacijske varnosti;

e) zagotavljanjem, da sistem upravljanja informacijske varnosti dosega pričakovani(-e) rezultat(-e);

f) usmerjanjem in podpiranjem oseb za večjo uspešnost sistema upravljanja informacijske varnosti;

g) spodbujanjem nenehnega izboljševanja in

h) podpiranjem drugih pomembnih vodstvenih vlog za izkazovanje svojega voditeljstva v skladu s

svojim področjem odgovornosti.
5.2 Politika
Najvišje vodstvo mora zagotavljati informacijsko varnostno politiko, ki:
a) ustreza namenu organizacije;

b) zajema cilje informacijske varnosti (glej točko 6.2) ali zagotavlja okvir za postavljanje ciljev

informacijske varnosti;

c) zajema zavezanost k izpolnjevanju veljavnih zahtev v zvezi z informacijsko varnostjo in

d) zajema zavezanost k nenehnemu izboljševanju sistema upravljanja informacijske varnosti.

Informacijska varnostna politika mora biti:
e) na voljo v obliki dokumentiranih informacij;
f) sporočena znotraj organizacije in
g) po potrebi na voljo zainteresiranim strankam.
5.3 Organizacijske vloge, odgovornosti in pooblastila

Najvišje vodstvo mora zagotavljati, da so odgovornosti in pooblastila za vloge, pomembne za

informacijsko varnost, določeni ter da so sporočeni vsem.
Najvišje vodstvo mora določiti odgovornosti in pooblastila za:

a) zagotavljanje, da je sistem upravljanja informacijske varnosti skladen z zahtevami tega

mednarodnega standarda, in

b) poročanje najvišjemu vodstvu o delovanju sistema upravljanja informacijske varnosti.

---------------------- Page: 7 ----------------------
SIST ISO/IEC 27001 : 2013

OPOMBA: Najvišje vodstvo lahko določi tudi odgovornosti in pooblastila za poročanje o delovanju sistema upravljanja

informacijske varnosti znotraj organizacije.
6 Načrtovanje
6.1 Ukrepi za obravnavanje tveganj in priložnosti
6.1.1 Splošno

Pri načrtovanju sistema upravljanja informacijske varnosti mora organizacija upoštevati vprašanja iz

točke 4.1 in zahteve iz točke 4.2 ter določiti tveganja in priložnosti, ki jih je treba obravnavati, da:

a) zagotovi, da lahko sistem upravljanja informacijske varnosti doseže pričakovane rezultate;

b) prepreči ali omeji neželene učinke in
c) doseže nenehno izboljševanje.
Organizacija mora načrtovati:
d) ukrepe za obravnavanje teh tveganj in priložnosti ter
e) način, kako

1) vključiti ukrepe v procese svojega sistema upravljanja informacijske varnosti in jih izvajati ter

2) vrednotiti uspešnosti teh ukrepov.
6.1.2 Ocenjevanje tveganj informacijske varnosti

Organizacija mora določiti in uporabiti proces ocenjevanja tveganj informacijske varnosti, da:

a) vzpostavi in vzdržuje kriterije tveganj informacijske varnosti, ki zajemajo:
1) kriterije za sprejem tveganj in
2) kriterije za izvajanje ocenjevanja tveganj informacijske varnosti;

b) zagotavlja, da ponovljena ocenjevanja tveganj informacijske varnosti zagotavljajo dosledne,

veljavne in primerljive rezultate;
c) prepozna tveganja informacijske varnosti:

1) uporabi proces ocenjevanja tveganj informacijske varnosti za prepoznavanje tveganj,

povezanih z izgubo zaupnosti, celovitosti in razpoložljivosti za informacije v okviru sistema

upravljanja informacijske varnosti, in
2) prepozna lastnike tveganj;
d) analizira tveganja informacijske varnosti:

1) oceni morebitne posledice, do katerih bi prišlo ob uresničitvi tveganj, prepoznanih v točki

6.1.2.c)(1),
2) oceni realno verjetnost pojava tveganj, prepoznanih v točki 6.1.2.c)(1), in
3) določi ravni tveganj;
e) ovrednoti tveganja informacijske varnosti:

1) primerja rezultate analize tveganj s kriteriji tveganj, postavljenimi v točki 6.1.2.a); in

2) prednostno razvrsti analizirana tveganja za obravnavanje tveganj.

Organizacija mora hraniti dokumentirane informacije o procesu ocenjevanja tveganj informacijske

varnosti.
---------------------- Page: 8 ----------------------
SIST ISO/IEC 27001 : 2013
6.1.3 Obravnavanje tveganj informacijske varnosti

Organizacija mora določiti in uporabljati proces obravnavanja tveganj informacijske varnosti za:

a) izbiro ustreznih možnosti obravnavanja tveganj informacijske varnosti, pri čemer upošteva

rezultate ocenjevanja tveganj;

b) določitev vseh kontrol, ki so potrebne za izvajanje izbranih možnosti obravnavanja tveganj

informacijske varnosti;

OPOMBA: Organizacije lahko zasnujejo kontrole po potrebi ali jih opredelijo na podlagi katerega koli vira.

c) primerjavo kontrol iz gornje točke 6.1.3.b) s kontrolami iz dodatka A in preverjanje, da nobena

potrebna kontrola ni bila izpuščena;

OPOMBA 1: Dodatek A vsebuje izčrpen seznam ciljev kontrol in kontrol. Uporabniki tega mednarodnega standarda

naj upoštevajo dodatek A, da ne spregledajo nobene potrebne kontrole.

OPOMBA 2: Cilji kontrol so posredno vključeni v izbrane kontrole. Cilji kontrol in kontrole, navedeni v dodatku A, niso

izčrpni in so morda potrebni dodatni cilji kontrol in kontrole.

d) pripravo izjave o uporabnosti, ki vsebuje potrebne kontrole (glej točko 6.1.3.b) in c)) ter

utemeljitev za vključitev ne glede na to, ali so izvedene ali ne, ter utemeljitev za izključitev kontrol

iz dodatka A;
e) pripravo načrta obravnavanja tveganj informacijske varnosti in

f) doseganje strinjanja lastnikov tveganj glede načrta obravnavanja tveganj informacijske varnosti

ter sprejem preostalih tveganj informacijske varnosti.

Organizacija mora hraniti dokumentirane informacije o procesu obravnavanja tveganj informacijske

varnosti.

OPOMBA: Proces ocenjevanja in obravnavanja tveganj informacijske varnosti v tem mednarodnem standardu je usklajen z

[5]
načeli in splošnimi smernicami iz standarda ISO 31000 .
6.2 Cilji informacijske varnosti in načrtovanje njihovega doseganja

Organizacija mora vzpostaviti cilje informacijske varnosti za ustrezne funkcije in ravni.

Cilji informacijske varnosti morajo:
a) biti skladni z informacijsko varnostno politiko;
b) biti merljivi (če je mogoče);

c) upoštevati veljavne zahteve informacijske varnosti ter rezultate ocenjevanja in obravnavanja

tveganj;
d) biti sporočeni in
e) biti posodobljeni, če je to potrebno.

Organizacija mora hraniti dokumentirane informacije o ciljih informacijske varnosti.

Organizacija mora pri načrtovanju doseganja ciljev informacijske varnosti določiti:

f) kaj bo naredila,
g) kateri viri bodo potrebni,
h) kdo bo odgovoren,
i) kdaj bo delo končano in
j) kako bodo rezultati ovrednoteni.
---------------------- Page: 9 ----------------------
SIST ISO/IEC 27001 : 2013
7 Podpora
7.1 Viri

Organizacija mora določiti in zagotoviti vire, potrebne za vzpostavitev, izvajanje, vzdrževanje in

nenehno izboljševanje sistema upravljanja informacijske varnosti.
7.2 Kompetentnost
Organizacija mora:

a) določiti potrebno kompetentnost osebe (oseb), ki izvaja(-jo) delo pod njenim nadzorom, ki vpliva

na izvajanje informacijske varnosti;

b) zagotavljati, da so te osebe kompetentne na podlagi primerne izobrazbe, usposobljenosti ali

izkušenj;

c) po potrebi sprejeti ukrepe za zagotavljanje potrebne kompetentnosti ter ovrednotiti uspešnost

sprejetih ukrepov in
d) hraniti ustrezne dokumentirane informacije kot dokaz kompetentnosti.

OPOMBA: Primerni ukrepi lahko na primer zajemajo: zagotavljanje usposabljanja, mentorstvo ali prerazporeditev trenutnih

zaposlenih ali najem ali pogodbeno zaposlitev kompetentnih oseb.
7.3 Ozaveščenost
Osebe, ki opravljajo delo pod nadzorom organizacije, morajo poznati:
a) informacijsko varnostno politiko,

b) svoj prispevek k uspešnosti sistema upravljanja informacijske varnosti, vključno s koristmi

izboljšanega delovanja informacijske varnosti, in

c) posledice neskladnosti z zahtevami sistema upravljanja informacijske varnosti.

7.4 Sporočanje

Organizacija mora določiti potrebo po notranjem in zunanjem sporočanju, pomembnem za sistem

upravljanja informacijske varnosti, vključno s:
a) kaj sporoča,
b) kdaj sporoča,
c) komu sporoča,
d) kdo mora sporočati in
e) procesi, ki vplivajo na sporočanje.
7.5 Dokumentirane informacije
7.5.1 Splošno
Sistem upravljanja informacijske varnosti organizacije mora vključevati:
a) dokumentirane informacije, ki jih zahteva ta mednarodni standard, in

b) dokumentirane informacije, ki jih organizacija določi kot potrebne za uspešnost sistema

upravljanja informacijske varnosti.

OPOMBA: Obseg dokumentiranih informacij za sistem upravljanja informacijske varnosti se lahko od organizacije do

organizacije razlikuje zaradi:

1) velikosti organizacije ter njene vrste dejavnosti, procesov, izdelkov in storitev;

---------------------- Page: 10 ----------------------
SIST ISO/IEC 27001 : 2013
2) kompleksnosti procesov in njihovih medsebojnih vplivov ter
3) kompetentnosti osebja.
7.5.2 Ustvarjanje in posodabljanje

Organizacija mora pri ustvarjanju in posodabljanju dokumentiranih informacij zagotoviti ustrezno:

a) opredelitev in opis (npr. naslov, datum, avtor ali referenčna številka),

b) obliko (npr. jezik, različica programske opreme, grafika) in medij (npr. papir, elektronski medij) ter

c) pregled ter odobritev za ustreznost in zadostnost.
7.5.3 Obvladovanje dokumentiranih informacij

Dokumentirane informacije, ki jih zahtevata sistem upravljanja informacijske varnosti in ta mednarodni

standard, se morajo obvladovati, da se zagotovijo:

a) njihova razpoložljivost in primernost za uporabo, kjer in kadar so potrebne, ter

b) njihova ustrezna zaščita (npr. pred izgubo zaupnosti, neprimerno uporabo ali izgubo celovitosti).

Za obvladovanje dokumentiranih informacij mora organizacija po potrebi obravnavati naslednje

aktivnosti:
c) razdeljevanje, dostop, pridobivanje in uporabo;
d) shranjevanje in ohranjanje, vključno z ohranjanjem razločnosti;
e) obvladovanje sprememb (npr. obvladovanje različic) ter
f) hranjenje in odstranjevanje.

Dokumentirane informacije zunanjega izvora, ki jih organizacija določi kot potrebne za načrtovanje in

delovanje sistema upravljanja informacijske varnosti, so prepoznane kot ustrezne in so nadzorovane.

OPOMBA: Dostop označuje odločitev v zvezi z dovoljenjem samo za ogled dokumentiranih informacij ali z dovoljenjem in

pooblastilom za ogled in spremembo dokumentiranih informacij itd.
8 Delovanje
8.1 Načrtovanje in obvladovanje delovanja

Organizacija mora načrtovati, izvajati in obvladovati procese, potrebne za izpolnjevanje zahtev

informacijske varnosti ter izvajanje ukrepov, opredeljenih v točki 6.1. Organizacija mora izvajati tudi

načrte za doseganje ciljev informacijske varnosti iz točke 6.2.

Organizacija mora hraniti dokumentirane informacije, dokler se ne prepriča, da so bili procesi izvedeni

v načrtovanem obsegu.

Organizacija mora obvladovati načrtovane spremembe in pregledovati posledice nenačrtovanih

sprememb, pri čemer mora po potrebi ukrepati, da se ublažijo morebitni negativni učinki.

Organizacija mora zagotoviti, da so procesi, predani v izvajanje zunanjim izvajalcem, določeni in

obvladovani.
8.2 Ocenjevanje tveganj informacijske varnosti

Organizacija mora izvajati ocenjevanja tveganj informacijske varnosti v načrtovanih časovnih

presledkih ali kadar so predlagane ali nastanejo bistvene spremembe, pri čemer upošteva kriterije,

določene v točki 6.1.2.a).
---------------------- Page: 11 ----------------------
SIST ISO/IEC 27001 : 2013

Organizacija mora hraniti dokumentirane informacije o rezultatih ocenjevanj tveganj informacijske

varnosti.
8.3 Obravnavanje tveganj informacijske varnosti
Organizacija mora izvajati načrt obravnavanja tveganj informacijske varnosti.

Organizacija mora hraniti dokumentirane informacije o rezultatih obravnavanj tveganj informacijske

varnosti.
9 Vrednotenje delovanja
9.1 Spremljanje, merjenje, analiziranje in vrednotenje

Organizacija mora vrednotiti delovanje informacijske varnosti in uspešnost sistema upravljanja

informacijske varnosti.
Organizacija mora določiti:

a) katere potrebe morajo biti spremljane in merjene, vključno s procesi in kontrolami informacijske

varnosti,

b) metode za spremljanje, merjenje, analiziranje in vrednotenje, če je to potrebno, da se zagotovijo

veljavni rezultati,

OPOMBA Izbrane metode naj zagotovijo primerljive in ponovljive rezultate, da se lahko štejejo za veljavne.

c) kdaj se morata izvajati spremljanje in merjenje,
d) kdo mora spremljati in meriti,

e) kdaj se morajo analizirati in vrednotiti rezultati spremljanja in merjenja ter

f) kdo mora analizirati in ovrednotiti te rezultate.

Organizacija mora hraniti ustrezne dokumentirane informacije kot dokaz o rezultatih nadzorovanja in

merjenja.
9.2 Notranja presoja

Organizacija mora izvajati notranje presoje v načrtovanih časovnih presledkih, da bi zagotovila

informacije o tem, ali sistem upravljanja informacijske varnosti:
a) izpolnjuje
1) zahteve organizacije za sistem upravljanja informacijske varnosti in
2) zahteve tega mednarodnega standarda;
b) se uspešno izvaja in vzdržuje.
Organizacija mora:

c) načrtovati, vzpostaviti, izvajati in vzdrževati program(-e) presoj, vključno s pogostostjo, metodami,

odgovornostmi, zahtevami načrtovanja in poročanjem. Program(-i) presoj morajo upoštevati

pomen, ki ga imajo obravnavani procesi, in rezultate predhodnih presoj,
d) opredeliti kriterije presoje in obseg vsake presoje,

e) izbrati presojevalce in izvajati presoje, ki zagotavljajo objektivnost in neodvisnost procesa

presoje,
f) zagotavljati, da se rezultati presoj sporočajo zadevnemu vodstvu,

g) hraniti dokumentirane informacije kot dokaz programov presoje in rezultatov presoj.

---------------------- Page: 12 ----------------------
SIST ISO/IEC 27001 : 2013
9.3 Vodstveni pregled

Najvišje vodstvo mora pregledovati sistem upravljanja informacijske varnosti organizacije v

načrtovanih časovnih presledkih, da zagotovi njegovo nenehno ustreznost, primernost in uspešnost.

Vodstveni pregled mora obravnavati:
...

SLOVENSKI SIST ISO/IEC 27001
STANDARD
november 2013
Informacijska tehnologija – Varnostne tehnike – Sistemi upravljanja
informacijske varnosti – Zahteve (vključen popravek SIST ISO/IEC
27001:2013/AC101:2014)
Information technology – Security techniques – Information security management
systems – Requirements
Technologies de l'information – Techniques de sécurité – Systèmes de
management de la sécurité de l'information – Exigences
Referenčna oznaka
ICS 35.040 SIST ISO/IEC 27001:2013 (sl)
Nadaljevanje na straneh 2 do 27

© 2014-01. Slovenski inštitut za standardizacijo. Razmnoževanje ali kopiranje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
SIST ISO/IEC 27001 : 2013
NACIONALNI UVOD

Standard SIST ISO/IEC 27001 (sl), Informacijska tehnologija – Varnostne tehnike – Sistemi

upravljanja informacijske varnosti – Zahteve, 2013, ima status slovenskega standarda in je istoveten

mednarodnemu standardu ISO/IEC 27001 (en), Information technology – Security techniques –

Information security management systems – Requirements, druga izdaja, 2013-10-01.

Ta standard preklicuje in nadomešča standard SIST ISO/IEC 27001:2010.
NACIONALNI PREDGOVOR

Mednarodni standard ISO/IEC 27001:2013 je pripravil pododbor združenega tehničnega odbora

Mednarodne organizacije za standardizacijo in Mednarodne elektrotehniške komisije ISO/IEC JTC

1/SC 27 Varnostne tehnike v informacijski tehnologiji.

Slovenski standard SIST ISO/IEC 27001:2013 je prevod mednarodnega standarda ISO/IEC

27001:2013. Slovenski standard SIST ISO/IEC 27001:2013 je pripravil tehnični odbor SIST/TC ITC

Informacijska tehnologija. V primeru spora glede besedila slovenskega prevoda je odločilen izvirni

mednarodni standard v angleškem jeziku.

Odločitev za izdajo tega standarda je dne 25. oktobra 2013 sprejel SIST/TC ITC Informacijska

tehnologija.
ZVEZA S STANDARDI

SIST ISO/IEC 27000 Informacijska tehnologija – Varnostne tehnike – Sistemi upravljanja

informacijske varnosti – Pregled in izrazoslovje
OSNOVA ZA IZDAJO STANDARDA
– privzem standarda ISO/IEC 27001:2013
PREDHODNA IZDAJA

– ISO/IEC 27001:2010, Informacijska tehnologija – Varnostne tehnike – Sistemi upravljanja

informacijske varnosti – Zahteve
OPOMBI

– Povsod, kjer se v besedilu standarda uporablja izraz “mednarodni standard”, v SIST ISO/IEC

27001:2013 to pomeni “slovenski standard”.
– Nacionalni uvod in nacionalni predgovor nista sestavni del standarda.
---------------------- Page: 2 ----------------------
SIST ISO/IEC 27001 : 2013
VSEBINA Stran

Predgovor .................................................................................................................................................4

0 Uvod ......................................................................................................................................................5

0.1 Splošno...............................................................................................................................................5

0.2 Združljivost z drugimi standardi za sisteme upravljanja.....................................................................5

1 Področje uporabe ..................................................................................................................................6

2 Zveza s standardi ..................................................................................................................................6

3 Izrazi in definicije ...................................................................................................................................6

4 Okvir organizacije ..................................................................................................................................6

4.1 Razumevanje organizacije in njenega okvira.....................................................................................6

4.2 Razumevanje potreb in pričakovanj zainteresiranih strank................................................................6

4.3 Določitev obsega sistema upravljanja informacijske varnosti ............................................................6

4.4 Sistem upravljanja informacijske varnosti ..........................................................................................7

5 Voditeljstvo ............................................................................................................................................7

5.1 Voditeljstvo in zavezanost ..................................................................................................................7

5.2 Politika ................................................................................................................................................7

5.3 Organizacijske vloge, odgovornosti in pooblastila .............................................................................7

6 Načrtovanje ...........................................................................................................................................8

6.1 Ukrepi za obravnavanje tveganj in priložnosti....................................................................................8

6.2 Cilji informacijske varnosti in načrtovanje njihovega doseganja ........................................................9

7 Podpora .............................................................................................................................................. 10

7.1 Viri.................................................................................................................................................... 10

7.2 Kompetentnost ................................................................................................................................ 10

7.3 Ozaveščenost.................................................................................................................................. 10

7.4 Sporočanje ...................................................................................................................................... 10

7.5 Dokumentirane informacije.............................................................................................................. 10

8 Delovanje............................................................................................................................................ 11

8.1 Načrtovanje in obvladovanje delovanja........................................................................................... 11

8.2 Ocenjevanje tveganj informacijske varnosti .................................................................................... 11

8.3 Obravnavanje tveganj informacijske varnosti.................................................................................. 12

9 Vrednotenje ........................................................................................................................................ 12

9.1 Spremljanje, merjenje, analiziranje in vrednotenje.......................................................................... 12

9.2 Notranja presoja .............................................................................................................................. 12

9.3 Vodstveni pregled............................................................................................................................ 13

10 Izboljševanje..................................................................................................................................... 13

10.1 Neskladnosti in popravni ukrepi .................................................................................................... 13

10.2 Nenehno izboljševanje .................................................................................................................. 14

Dodatek A (normativni): Cilji kontrol in kontrole .................................................................................... 15

Literatura................................................................................................................................................ 27

---------------------- Page: 3 ----------------------
SIST ISO/IEC 27001 : 2013
Predgovor

ISO (Mednarodna organizacija za standardizacijo) in IEC (Mednarodna elektrotehniška komisija)

tvorita specializiran sistem za svetovno standardizacijo. Nacionalni organi, ki so člani ISO ali IEC,

sodelujejo pri pripravi mednarodnih standardov prek tehničnih odborov, ki jih za obravnavanje

določenih strokovnih področij ustanovi ustrezna organizacija. Tehnični odbori ISO in IEC sodelujejo na

področjih skupnega interesa. Pri delu sodelujejo tudi druge mednarodne, vladne in nevladne

organizacije, povezane z ISO in IEC. Na področju informacijske tehnologije sta ISO in IEC vzpostavila

združeni tehnični odbor ISO/IEC JTC 1.

Mednarodni standardi so pripravljeni v skladu s pravili, podanimi v 2. delu Direktiv ISO/IEC.

Glavna naloga tehničnih odborov je priprava mednarodnih standardov. Osnutki mednarodnih

standardov, ki jih sprejmejo tehnični odbori, se pošljejo vsem članom v glasovanje. Za objavo

mednarodnega standarda je treba pridobiti soglasje najmanj 75 odstotkov članov, ki se udeležijo

glasovanja.

Opozoriti je treba na možnost, da je lahko nekaj elementov tega mednarodnega standarda predmet

patentnih pravic. ISO in IEC ne prevzemata odgovornosti za prepoznavanje katerih koli ali vseh takih

patentnih pravic.

ISO/IEC 27001 je pripravil združeni tehnični odbor JTC ISO/IEC 1 Informacijska tehnologija, pododbor

SC 27 Varnostne tehnike IT.

Druga izdaja preklicuje in nadomešča prvo izdajo (ISO/IEC 27001:2005), ki je tehnično revidirana.

---------------------- Page: 4 ----------------------
SIST ISO/IEC 27001 : 2013
0 Uvod
0.1 Splošno

Ta mednarodni standard je bil pripravljen, da zagotovi zahteve za vzpostavitev, izvajanje, vzdrževanje

in nenehno izboljševanje sistema upravljanja informacijske varnosti. Privzem sistema upravljanja

informacijske varnosti je strateška odločitev za organizacijo. Na vzpostavitev in izvedbo sistema

upravljanja informacijske varnosti organizacije vplivajo potrebe in cilji organizacije, varnostne zahteve,

uporabljeni organizacijski procesi ter velikost in struktura organizacije. Vsi ti dejavniki, ki vplivajo na

sistem, se bodo po pričakovanjih s časom spreminjali.

Sistem upravljanja informacijske varnosti ohranja zaupnost, celovitost in razpoložljivost informacij z

uporabo procesa za obvladovanje tveganj ter zainteresiranim strankam vzbuja zaupanje, da se

tveganja ustrezno obvladujejo.

Pomembno je, da je sistem upravljanja informacijske varnosti del procesov organizacije in splošne

strukture vodenja in je integriran z njimi ter da je informacijska varnost sprejeta pri zasnovi procesov,

informacijskih sistemov in kontrol. Pričakuje se, da bo izvajanje sistema upravljanja informacijske

varnosti skladno s potrebami organizacije.

Ta mednarodni standard lahko uporabljajo notranje ali zunanje stranke za ocenjevanje sposobnosti

organizacije izpolnjevati lastne zahteve informacijske varnosti.

Vrstni red predstavitve zahtev v tem mednarodnem standardu ne odraža njihovega pomena ali

nakazuje vrstnega reda, v katerem naj bi se izvedle. Elementi na seznamu so oštevilčeni zgolj za

namene sklicevanja.

Standard ISO/IEC 27000 podaja pregled in izrazje sistemov upravljanja informacijske varnosti, pri

čemer se sklicuje na skupino standardov za sisteme upravljanja informacijske varnosti (vključno s

[2] [3] [4]

standardi ISO/IEC 27003 , ISO/IEC 27004 in ISO/IEC 27005 ) s povezanimi izrazi in definicijami.

0.2 Združljivost z drugimi standardi za sisteme upravljanja

Ta mednarodni standard uporablja strukturo visoke ravni, enake naslove podtočk, enako besedilo,

splošne izraze in temeljne definicije iz dodatka SL k Direktivam ISO/IEC, 1. del, konsolidirana priloga

ISO, zato ohranja združljivost z drugimi standardi za sisteme upravljanja, ki so sprejeli dodatek SL.

Ta splošni pristop iz dodatka SL bo koristil tistim organizacijam, ki so izbrale vzpostavitev enotnega

sistema upravljanja, ki izpolnjuje zahteve iz dveh ali več standardov za sisteme upravljanja.

---------------------- Page: 5 ----------------------
SIST ISO/IEC 27001 : 2013
Informacijska tehnologija – Varnostne tehnike – Sistemi upravljanja
informacijske varnosti – Zahteve
1 Področje uporabe

Ta mednarodni standard določa zahteve za vzpostavitev, izvajanje, vzdrževanje in nenehno

izboljševanje sistema upravljanja informacijske varnosti v okviru organizacije. Zajema tudi zahteve za

ocenjevanje in obravnavanje tveganj informacijske varnosti, ki so prilagojene potrebam organizacije.

Zahteve, postavljene v tem mednarodnem standardu, so generične in so namenjene uporabi v vseh

organizacijah ne glede na vrsto, velikost ali naravo. Izključevanje katere koli zahteve, določene v

točkah 4 do 10, ni sprejemljivo, kadar organizacija zagotavlja skladnost s tem mednarodnim

standardom.
2 Zveza s standardi

Ta dokument se v celoti ali v delih normativno sklicuje na naslednje dokumente, ki so nepogrešljivi pri

njegovi uporabi. Pri datiranih sklicevanjih se uporablja zgolj navedena izdaja. Pri nedatiranih sklicevanjih

se uporablja zadnja izdaja navedenega dokumenta (vključno z dopolnili).

ISO/IEC 27000 Informacijska tehnologija – Varnostne tehnike – Sistemi upravljanja

informacijske varnosti – Pregled in izrazoslovje
3 Izrazi in definicije

V tem dokumentu so uporabljeni izrazi in definicije, ki so podani v standardu ISO/IEC 27000.

4 Okvir organizacije
4.1 Razumevanje organizacije in njenega okvira

Organizacija mora določiti zunanja in notranja vprašanja, ki so pomembna za njen namen ter vplivajo

na njeno sposobnost doseganja pričakovanega(-ih) rezultata(-ov) njenega sistema upravljanja

informacijske varnosti.

OPOMBA: Določanje teh vprašanj se nanaša na opredelitev zunanjega in notranjega okvira organizacije iz točke 5.3

[5]
standarda ISO 31000:2009 .
4.2 Razumevanje potreb in pričakovanj zainteresiranih strank
Organizacija mora določiti:

a) zainteresirane stranke, ki so pomembne za sistem upravljanja informacijske varnosti, in

b) zahteve teh zainteresiranih strank, ki so pomembne za informacijsko varnost.

OPOMBA: Zahteve zainteresiranih strank lahko vključujejo zahteve zakonodaje in predpisov ter pogodbene obveznosti.

4.3 Določitev obsega sistema upravljanja informacijske varnosti

Organizacija mora določiti meje in uporabnost sistema upravljanja informacijske varnosti za

opredelitev njegovega obsega.
Organizacija pri določanju tega obsega upošteva:
a) zunanja in notranja vprašanja iz točke 4.1,
b) zahteve iz točke 4.2 ter

c) povezave in odvisnosti med aktivnostmi, ki jih izvaja organizacija, in aktivnostmi, ki jih izvajajo

druge organizacije.
---------------------- Page: 6 ----------------------
SIST ISO/IEC 27001 : 2013
Obseg mora biti na voljo v obliki dokumentiranih informacij.
4.4 Sistem upravljanja informacijske varnosti

Organizacija mora vzpostaviti, izvajati, vzdrževati in nenehno izboljševati sistem upravljanja

informacijske varnosti v skladu z zahtevami tega mednarodnega standarda.
5 Voditeljstvo
5.1 Voditeljstvo in zavezanost

Najvišje vodstvo mora izkazovati sposobnost vodenja in zavezanost v zvezi s sistemom upravljanja

informacijske varnosti z:

a) zagotavljanjem informacijske varnostne politike in postavljanjem ciljev informacijske varnosti, ki

so združljivi s strateško usmeritvijo organizacije;

b) zagotavljanjem vključitve zahtev sistema upravljanja informacijske varnosti v procese

organizacije;

c) zagotavljanjem razpoložljivosti virov, potrebnih za sistem upravljanja informacijske varnosti;

d) sporočanjem pomena uspešnega upravljanja informacijske varnosti in izpolnjevanjem zahtev

sistema upravljanja informacijske varnosti;

e) zagotavljanjem, da sistem upravljanja informacijske varnosti dosega pričakovani(-e) rezultat(-e);

f) usmerjanjem in podpiranjem oseb za večjo uspešnost sistema upravljanja informacijske varnosti;

g) spodbujanjem nenehnega izboljševanja in

h) podpiranjem drugih pomembnih vodstvenih vlog za izkazovanje svojega voditeljstva v skladu s

svojim področjem odgovornosti.
5.2 Politika
Najvišje vodstvo mora zagotavljati informacijsko varnostno politiko, ki:
a) ustreza namenu organizacije;

b) zajema cilje informacijske varnosti (glej točko 6.2) ali zagotavlja okvir za postavljanje ciljev

informacijske varnosti;

c) zajema zavezanost k izpolnjevanju veljavnih zahtev v zvezi z informacijsko varnostjo in

d) zajema zavezanost k nenehnemu izboljševanju sistema upravljanja informacijske varnosti.

Informacijska varnostna politika mora biti:
e) na voljo v obliki dokumentiranih informacij;
f) sporočena znotraj organizacije in
g) po potrebi na voljo zainteresiranim strankam.
5.3 Organizacijske vloge, odgovornosti in pooblastila

Najvišje vodstvo mora zagotavljati, da so odgovornosti in pooblastila za vloge, pomembne za

informacijsko varnost, določeni ter da so sporočeni vsem.
Najvišje vodstvo mora določiti odgovornosti in pooblastila za:

a) zagotavljanje, da je sistem upravljanja informacijske varnosti skladen z zahtevami tega

mednarodnega standarda, in

b) poročanje najvišjemu vodstvu o delovanju sistema upravljanja informacijske varnosti.

---------------------- Page: 7 ----------------------
SIST ISO/IEC 27001 : 2013

OPOMBA: Najvišje vodstvo lahko določi tudi odgovornosti in pooblastila za poročanje o delovanju sistema upravljanja

informacijske varnosti znotraj organizacije.
6 Načrtovanje
6.1 Ukrepi za obravnavanje tveganj in priložnosti
6.1.1 Splošno

Pri načrtovanju sistema upravljanja informacijske varnosti mora organizacija upoštevati vprašanja iz

točke 4.1 in zahteve iz točke 4.2 ter določiti tveganja in priložnosti, ki jih je treba obravnavati, da:

a) zagotovi, da lahko sistem upravljanja informacijske varnosti doseže pričakovane rezultate;

b) prepreči ali omeji neželene učinke in
c) doseže nenehno izboljševanje.
Organizacija mora načrtovati:
d) ukrepe za obravnavanje teh tveganj in priložnosti ter
e) način, kako

1) vključiti ukrepe v procese svojega sistema upravljanja informacijske varnosti in jih izvajati ter

2) vrednotiti uspešnosti teh ukrepov.
6.1.2 Ocenjevanje tveganj informacijske varnosti

Organizacija mora določiti in uporabiti proces ocenjevanja tveganj informacijske varnosti, da:

a) vzpostavi in vzdržuje kriterije tveganj informacijske varnosti, ki zajemajo:
1) kriterije za sprejem tveganj in
2) kriterije za izvajanje ocenjevanja tveganj informacijske varnosti;

b) zagotavlja, da ponovljena ocenjevanja tveganj informacijske varnosti zagotavljajo dosledne,

veljavne in primerljive rezultate;
c) prepozna tveganja informacijske varnosti:

1) uporabi proces ocenjevanja tveganj informacijske varnosti za prepoznavanje tveganj,

povezanih z izgubo zaupnosti, celovitosti in razpoložljivosti za informacije v okviru sistema

upravljanja informacijske varnosti, in
2) prepozna lastnike tveganj;
d) analizira tveganja informacijske varnosti:

1) oceni morebitne posledice, do katerih bi prišlo ob uresničitvi tveganj, prepoznanih v točki

6.1.2.c)(1),
2) oceni realno verjetnost pojava tveganj, prepoznanih v točki 6.1.2.c)(1), in
3) določi ravni tveganj;
e) ovrednoti tveganja informacijske varnosti:

1) primerja rezultate analize tveganj s kriteriji tveganj, postavljenimi v točki 6.1.2.a); in

2) prednostno razvrsti analizirana tveganja za obravnavanje tveganj.

Organizacija mora hraniti dokumentirane informacije o procesu ocenjevanja tveganj informacijske

varnosti.
---------------------- Page: 8 ----------------------
SIST ISO/IEC 27001 : 2013
6.1.3 Obravnavanje tveganj informacijske varnosti

Organizacija mora določiti in uporabljati proces obravnavanja tveganj informacijske varnosti za:

a) izbiro ustreznih možnosti obravnavanja tveganj informacijske varnosti, pri čemer upošteva

rezultate ocenjevanja tveganj;

b) določitev vseh kontrol, ki so potrebne za izvajanje izbranih možnosti obravnavanja tveganj

informacijske varnosti;

OPOMBA: Organizacije lahko zasnujejo kontrole po potrebi ali jih opredelijo na podlagi katerega koli vira.

c) primerjavo kontrol iz gornje točke 6.1.3.b) s kontrolami iz dodatka A in preverjanje, da nobena

potrebna kontrola ni bila izpuščena;

OPOMBA 1: Dodatek A vsebuje izčrpen seznam ciljev kontrol in kontrol. Uporabniki tega mednarodnega standarda

naj upoštevajo dodatek A, da ne spregledajo nobene potrebne kontrole.

OPOMBA 2: Cilji kontrol so posredno vključeni v izbrane kontrole. Cilji kontrol in kontrole, navedeni v dodatku A, niso

izčrpni in so morda potrebni dodatni cilji kontrol in kontrole.

d) pripravo izjave o uporabnosti, ki vsebuje potrebne kontrole (glej točko 6.1.3.b) in c)) ter

utemeljitev za vključitev ne glede na to, ali so izvedene ali ne, ter utemeljitev za izključitev kontrol

iz dodatka A;
e) pripravo načrta obravnavanja tveganj informacijske varnosti in

f) doseganje strinjanja lastnikov tveganj glede načrta obravnavanja tveganj informacijske varnosti

ter sprejem preostalih tveganj informacijske varnosti.

Organizacija mora hraniti dokumentirane informacije o procesu obravnavanja tveganj informacijske

varnosti.

OPOMBA: Proces ocenjevanja in obravnavanja tveganj informacijske varnosti v tem mednarodnem standardu je usklajen z

[5]
načeli in splošnimi smernicami iz standarda ISO 31000 .
6.2 Cilji informacijske varnosti in načrtovanje njihovega doseganja

Organizacija mora vzpostaviti cilje informacijske varnosti za ustrezne funkcije in ravni.

Cilji informacijske varnosti morajo:
a) biti skladni z informacijsko varnostno politiko;
b) biti merljivi (če je mogoče);

c) upoštevati veljavne zahteve informacijske varnosti ter rezultate ocenjevanja in obravnavanja

tveganj;
d) biti sporočeni in
e) biti posodobljeni, če je to potrebno.

Organizacija mora hraniti dokumentirane informacije o ciljih informacijske varnosti.

Organizacija mora pri načrtovanju doseganja ciljev informacijske varnosti določiti:

f) kaj bo naredila,
g) kateri viri bodo potrebni,
h) kdo bo odgovoren,
i) kdaj bo delo končano in
j) kako bodo rezultati ovrednoteni.
---------------------- Page: 9 ----------------------
SIST ISO/IEC 27001 : 2013
7 Podpora
7.1 Viri

Organizacija mora določiti in zagotoviti vire, potrebne za vzpostavitev, izvajanje, vzdrževanje in

nenehno izboljševanje sistema upravljanja informacijske varnosti.
7.2 Kompetentnost
Organizacija mora:

a) določiti potrebno kompetentnost osebe (oseb), ki izvaja(-jo) delo pod njenim nadzorom, ki vpliva

na izvajanje informacijske varnosti;

b) zagotavljati, da so te osebe kompetentne na podlagi primerne izobrazbe, usposobljenosti ali

izkušenj;

c) po potrebi sprejeti ukrepe za zagotavljanje potrebne kompetentnosti ter ovrednotiti uspešnost

sprejetih ukrepov in
d) hraniti ustrezne dokumentirane informacije kot dokaz kompetentnosti.

OPOMBA: Primerni ukrepi lahko na primer zajemajo: zagotavljanje usposabljanja, mentorstvo ali prerazporeditev trenutnih

zaposlenih ali najem ali pogodbeno zaposlitev kompetentnih oseb.
7.3 Ozaveščenost
Osebe, ki opravljajo delo pod nadzorom organizacije, morajo poznati:
a) informacijsko varnostno politiko,

b) svoj prispevek k uspešnosti sistema upravljanja informacijske varnosti, vključno s koristmi

izboljšanega delovanja informacijske varnosti, in

c) posledice neskladnosti z zahtevami sistema upravljanja informacijske varnosti.

7.4 Sporočanje

Organizacija mora določiti potrebo po notranjem in zunanjem sporočanju, pomembnem za sistem

upravljanja informacijske varnosti, vključno s:
a) kaj sporoča,
b) kdaj sporoča,
c) komu sporoča,
d) kdo mora sporočati in
e) procesi, ki vplivajo na sporočanje.
7.5 Dokumentirane informacije
7.5.1 Splošno
Sistem upravljanja informacijske varnosti organizacije mora vključevati:
a) dokumentirane informacije, ki jih zahteva ta mednarodni standard, in

b) dokumentirane informacije, ki jih organizacija določi kot potrebne za uspešnost sistema

upravljanja informacijske varnosti.

OPOMBA: Obseg dokumentiranih informacij za sistem upravljanja informacijske varnosti se lahko od organizacije do

organizacije razlikuje zaradi:

1) velikosti organizacije ter njene vrste dejavnosti, procesov, izdelkov in storitev;

---------------------- Page: 10 ----------------------
SIST ISO/IEC 27001 : 2013
2) kompleksnosti procesov in njihovih medsebojnih vplivov ter
3) kompetentnosti osebja.
7.5.2 Ustvarjanje in posodabljanje

Organizacija mora pri ustvarjanju in posodabljanju dokumentiranih informacij zagotoviti ustrezno:

a) opredelitev in opis (npr. naslov, datum, avtor ali referenčna številka),

b) obliko (npr. jezik, različica programske opreme, grafika) in medij (npr. papir, elektronski medij) ter

c) pregled ter odobritev za ustreznost in zadostnost.
7.5.3 Obvladovanje dokumentiranih informacij

Dokumentirane informacije, ki jih zahtevata sistem upravljanja informacijske varnosti in ta mednarodni

standard, se morajo obvladovati, da se zagotovijo:

a) njihova razpoložljivost in primernost za uporabo, kjer in kadar so potrebne, ter

b) njihova ustrezna zaščita (npr. pred izgubo zaupnosti, neprimerno uporabo ali izgubo celovitosti).

Za obvladovanje dokumentiranih informacij mora organizacija po potrebi obravnavati naslednje

aktivnosti:
c) razdeljevanje, dostop, pridobivanje in uporabo;
d) shranjevanje in ohranjanje, vključno z ohranjanjem razločnosti;
e) obvladovanje sprememb (npr. obvladovanje različic) ter
f) hranjenje in odstranjevanje.

Dokumentirane informacije zunanjega izvora, ki jih organizacija določi kot potrebne za načrtovanje in

delovanje sistema upravljanja informacijske varnosti, so prepoznane kot ustrezne in so nadzorovane.

OPOMBA: Dostop označuje odločitev v zvezi z dovoljenjem samo za ogled dokumentiranih informacij ali z dovoljenjem in

pooblastilom za ogled in spremembo dokumentiranih informacij itd.
8 Delovanje
8.1 Načrtovanje in obvladovanje delovanja

Organizacija mora načrtovati, izvajati in obvladovati procese, potrebne za izpolnjevanje zahtev

informacijske varnosti ter izvajanje ukrepov, opredeljenih v točki 6.1. Organizacija mora izvajati tudi

načrte za doseganje ciljev informacijske varnosti iz točke 6.2.

Organizacija mora hraniti dokumentirane informacije, dokler se ne prepriča, da so bili procesi izvedeni

v načrtovanem obsegu.

Organizacija mora obvladovati načrtovane spremembe in pregledovati posledice nenačrtovanih

sprememb, pri čemer mora po potrebi ukrepati, da se ublažijo morebitni negativni učinki.

Organizacija mora zagotoviti, da so procesi, predani v izvajanje zunanjim izvajalcem, določeni in

obvladovani.
8.2 Ocenjevanje tveganj informacijske varnosti

Organizacija mora izvajati ocenjevanja tveganj informacijske varnosti v načrtovanih časovnih

presledkih ali kadar so predlagane ali nastanejo bistvene spremembe, pri čemer upošteva kriterije,

določene v točki 6.1.2.a).
---------------------- Page: 11 ----------------------
SIST ISO/IEC 27001 : 2013

Organizacija mora hraniti dokumentirane informacije o rezultatih ocenjevanj tveganj informacijske

varnosti.
8.3 Obravnavanje tveganj informacijske varnosti
Organizacija mora izvajati načrt obravnavanja tveganj informacijske varnosti.

Organizacija mora hraniti dokumentirane informacije o rezultatih obravnavanj tveganj informacijske

varnosti.
9 Vrednotenje delovanja
9.1 Spremljanje, merjenje, analiziranje in vrednotenje

Organizacija mora vrednotiti delovanje informacijske varnosti in uspešnost sistema upravljanja

informacijske varnosti.
Organizacija mora določiti:

a) katere potrebe morajo biti spremljane in merjene, vključno s procesi in kontrolami informacijske

varnosti,

b) metode za spremljanje, merjenje, analiziranje in vrednotenje, če je to potrebno, da se zagotovijo

veljavni rezultati,

OPOMBA Izbrane metode naj zagotovijo primerljive in ponovljive rezultate, da se lahko štejejo za veljavne.

c) kdaj se morata izvajati spremljanje in merjenje,
d) kdo mora spremljati in meriti,

e) kdaj se morajo analizirati in vrednotiti rezultati spremljanja in merjenja ter

f) kdo mora analizirati in ovrednotiti te rezultate.

Organizacija mora hraniti ustrezne dokumentirane informacije kot dokaz o rezultatih nadzorovanja in

merjenja.
9.2 Notranja presoja

Organizacija mora izvajati notranje presoje v načrtovanih časovnih presledkih, da bi zagotovila

informacije o tem, ali sistem upravljanja informacijske varnosti:
a) izpolnjuje
1) zahteve organizacije za sistem upravljanja informacijske varnosti in
2) zahteve tega mednarodnega standarda;
b) se uspešno izvaja in vzdržuje.
Organizacija mora:

c) načrtovati, vzpostaviti, izvajati in vzdrževati program(-e) presoj, vključno s pogostostjo, metodami,

odgovornostmi, zahtevami načrtovanja in poročanjem. Program(-i) presoj morajo upoštevati

pomen, ki ga imajo obravnavani procesi, in rezultate predhodnih presoj,
d) opredeliti kriterije presoje in obseg vsake presoje,

e) izbrati presojevalce in izvajati presoje, ki zagotavljajo objektivnost in neodvisnost procesa

presoje,
f) zagotavljati, da se rezultati presoj sporočajo zadevnemu vodstvu,

g) hraniti dokumentirane informacije kot dokaz programov presoje in rezultatov presoj.

---------------------- Page: 12 ----------------------
SIST ISO/IEC 27001 : 2013
9.3 Vodstveni pregled

Najvišje vodstvo mora pregledovati sistem upravljanja informacijske varnosti organizacije v

načrtovanih časovnih presledkih, da zagotovi njegovo nenehno ustreznost, primernos

...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.