Iso Iec 27005 2022
Iso Iec 27005 2022
Iso Iec 27005 2022
STANDARD 27005
Fourth edition
2022-10
Reference number
ISO/IEC 27005:2022(E)
© ISO/IEC 2022
ISO/IEC 27005:2022(E)
Contents Page
Foreword...........................................................................................................................................................................................................................................v
Introduction............................................................................................................................................................................................................................... vi
1 Scope.................................................................................................................................................................................................................................. 1
2 Normative references...................................................................................................................................................................................... 1
3 erms and definitions..................................................................................................................................................................................... 1
T
3.1 Terms related to information security risk................................................................................................................... 1
3.2 Terms related to information security risk management................................................................................. 5
4 Structure of this document........................................................................................................................................................................ 7
5 Information security risk management....................................................................................................................................... 7
5.1 Information security risk management process....................................................................................................... 7
5.2 Information security risk management cycles........................................................................................................... 9
6 Context establishment.................................................................................................................................................................................... 9
6.1 Organizational considerations.................................................................................................................................................. 9
6.2 Identifying basic requirements of interested parties....................................................................................... 10
6.3 Applying risk assessment........................................................................................................................................................... 10
6.4 Establishing and maintaining information security risk criteria.......................................................... 11
6.4.1 General...................................................................................................................................................................................... 11
6.4.2 Risk acceptance criteria............................................................................................................................................. 11
iTeh STANDARD PREVIEW
6.4.3 Criteria for performing information security risk assessments........................................... 13
6.5 Choosing an appropriate method........................................................................................................................................ 15
(standards.iteh.ai)
7 Information security risk assessment process ................................................................................................................. 16
7.1 General......................................................................................................................................................................................................... 16
7.2 Identifying information security risks........................................................................................................................... 17
7.2.1 Identifying and ISO/IEC describing 27005:2022
information security risks.................................................................. 17
https://standards.iteh.ai/catalog/standards/sist/a81e3455-413d-48cd-9a3c-
7.2.2 Identifying risk owners.............................................................................................................................................. 18
7.3 Analysing information 71cd98fbe1e1/iso-iec-27005-2022
security risks.............................................................................................................................. 19
7.3.1 General...................................................................................................................................................................................... 19
7.3.2 Assessing potential consequences................................................................................................................... 19
7.3.3 Assessing likelihood...................................................................................................................................................... 20
7.3.4 Determining the levels of risk.............................................................................................................................. 22
7.4 Evaluating the information security risks.................................................................................................................. 22
7.4.1 Comparing the results of risk analysis with the risk criteria.................................................. 22
7.4.2 Prioritizing the analysed risks for risk treatment............................................................................. 23
8 Information security risk treatment process..................................................................................................................... 23
8.1 General......................................................................................................................................................................................................... 23
8.2 Selecting appropriate information security risk treatment options................................................... 23
8.3 Determining all controls that are necessary to implement the information security
risk treatment options................................................................................................................................................................... 24
8.4 Comparing the controls determined with those in ISO/IEC 27001:2022, Annex A................ 27
8.5 Producing a Statement of Applicability.......................................................................................................................... 27
8.6 Information security risk treatment plan.................................................................................................................... 28
8.6.1 Formulation of the risk treatment plan....................................................................................................... 28
8.6.2 Approval by risk owners........................................................................................................................................... 29
8.6.3 Acceptance of the residual information security risks.................................................................. 30
9 Operation................................................................................................................................................................................................................... 31
9.1 Performing information security risk assessment process......................................................................... 31
9.2 Performing information security risk treatment process............................................................................. 31
10 Leveraging related ISMS processes................................................................................................................................................ 32
10.1 Context of the organization....................................................................................................................................................... 32
10.2 Leadership and commitment................................................................................................................................................... 32
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.
The procedures used to develop this document and those intended for its further maintenance
are described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria
needed for the different types of document should be noted. This document was drafted in
accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives or
www.iec.ch/members_experts/refdocs).
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. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents) or the IEC
list of patent declarations received (see https://patents.iec.ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
iTeh STANDARD PREVIEW
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
(standards.iteh.ai)
expressions related to conformity assessment, as well as information about ISO's adherence to
the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see
www.iso.org/iso/foreword.html. In the IEC, see www.iec.ch/understanding-standards.
This document was prepared by Joint ISO/IEC 27005:2022
Technical Committee ISO/IEC JTC 1, Information technology,
https://standards.iteh.ai/catalog/standards/sist/a81e3455-413d-48cd-9a3c-
Subcommittee SC 27, Information security, cybersecurity and privacy protection.
71cd98fbe1e1/iso-iec-27005-2022
This fourth edition cancels and replaces the third edition (ISO/IEC 27005:2018), which has been
technically revised.
The main changes are as follows:
— all guidance text has been aligned with ISO/IEC 27001:2022, and ISO 31000:2018;
— the terminology has been aligned with the terminology in ISO 31000:2018;
— the structure of the clauses has been adjusted to the layout of ISO/IEC 27001:2022;
— risk scenario concepts have been introduced;
— the event-based approach is contrasted with the asset-based approach to risk identification;
— the content of the annexes has been revised and restructured into a single annex.
Any feedback or questions on this document should be directed to the user’s national standards
body. A complete listing of these bodies can be found at www.iso.org/members.html and
www.iec.ch/national-committees.
Introduction
This document provides guidance on:
— implementation of the information security risk requirements specified in ISO/IEC 27001;
— essential references within the standards developed by ISO/IEC JTC 1/SC 27 to support information
security risk management activities;
— actions that address risks related to information security (see ISO/IEC 27001:2022, 6.1 and Clause 8);
— implementation of risk management guidance in ISO 31000 in the context of information security.
This document contains detailed guidance on risk management and supplements the guidance in
ISO/IEC 27003.
This document is intended to be used by:
— organizations that intend to establish and implement an information security management system
(ISMS) in accordance with ISO/IEC 27001;
— persons that perform or are involved in information security risk management (e.g. ISMS
professionals, risk owners and other interested parties);
— organizations that intend to improve their information security risk management process.
iTeh STANDARD PREVIEW
(standards.iteh.ai)
ISO/IEC 27005:2022
https://standards.iteh.ai/catalog/standards/sist/a81e3455-413d-48cd-9a3c-
71cd98fbe1e1/iso-iec-27005-2022
1 Scope
This document provides guidance to assist organizations to:
— fulfil the requirements of ISO/IEC 27001 concerning actions to address information security risks;
— perform information security risk management activities, specifically information security risk
assessment and treatment.
This document is applicable to all organizations, regardless of type, size or sector.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
iTeh STANDARD PREVIEW
undated references, the latest edition of the referenced document (including any amendments) applies.
(standards.iteh.ai)
ISO/IEC 27000, Information technology — Security techniques — Information security management
systems — Overview and vocabulary
— the social, cultural, political, legal, regulatory, financial, technological, economic, geological environment,
whether international, national, regional or local;
[SOURCE: ISO Guide 73:2009, 3.3.1.1, modified — Note 1 to entry has been modified.]
3.1.2
internal context
internal environment in which the organization seeks to achieve its objectives
Note 1 to entry: Internal context can include:
— capabilities, understood in terms of resources and knowledge (e.g. capital, time, people, processes, systems
and technologies);
— relationships with internal interested parties, taking into account their perceptions and values;
[SOURCE: ISO Guide 73:2009, 3.3.1.2, modified — Note 1 to entry has been modified.]
3.1.3
iTeh STANDARD PREVIEW
risk
(standards.iteh.ai)
effect of uncertainty on objectives
Note 1 to entry: An effect is a deviation from the expected, positive or negative.
ISO/IEC 27005:2022
https://standards.iteh.ai/catalog/standards/sist/a81e3455-413d-48cd-9a3c-
Note 2 to entry: Objectives can have different aspects and categories, and can be applied at different levels.
71cd98fbe1e1/iso-iec-27005-2022
Note 3 to entry: Uncertainty is the state, even partial, of deficiency of information related to, understanding or
knowledge of, an event (3.1.11), its consequence (3.1.14), or likelihood (3.1.13).
Note 4 to entry: Risk is usually expressed in terms of risk sources (3.1.6), potential events, their consequences
and their likelihood.
Note 5 to entry: In the context of information security management systems, information security risks can be
expressed as effect of uncertainty on information security objectives.
Note 6 to entry: Information security risks are usually associated with a negative effect of uncertainty on
information security objectives.
Note 7 to entry: Information security risks can be associated with the potential that threats (3.1.9) will exploit
vulnerabilities (3.1.10) of an information asset or group of information assets and thereby cause harm to an
organization.
[SOURCE: ISO 31000:2018, 3.1, modified — the phrase: “It can be positive, negative or both, and can
address, create or result in opportunities and threats” has been replaced with “positive or negative” in
Note 1 to entry; the original Note 3 to entry has been renumbered as Note 4 to entry; and Notes 3, 5, 6
and 7 to entry have been added.]
3.1.4
risk scenario
sequence or combination of events (3.1.11) leading from the initial cause to the unwanted consequence
(3.1.14)
[SOURCE: ISO 17666:2016, 3.1.13, modified — Note 1 to entry has been deleted.]
3.1.5
risk owner
person or entity with the accountability and authority to manage a risk (3.1.3)
[SOURCE: ISO Guide 73:2009, 3.5.1.5]
3.1.6
risk source
element which alone or in combination has the potential to give rise to risk (3.1.3)
Note 1 to entry: A risk source can be one of these three types:
— human;
— environmental;
— technical.
[SOURCE: ISO 31000:2018, 3.4, modified — Notes 1 and 2 to entry have been added.]
3.1.7
risk criteria
terms of reference against which the significance of a risk (3.1.3) is evaluated
(standards.iteh.ai)
Note 2 to entry: Risk criteria can be derived from standards, laws, policies and other requirements.
Note 2 to entry: An event can also be something that is expected which does not happen, or something that is not
expected which does happen.
[SOURCE: ISO 31000:2018, 3.5, modified — Note 3 to entry has been removed.]
3.1.12
information security incident
single or a series of unwanted or unexpected information security events that have a significant
probability of compromising business operations and threatening information security
3.1.13
likelihood
chance of something happening
Note 1 to entry: In risk management terminology, the word “likelihood” is used to refer to the chance of something
happening, whether defined, measured or determined objectively or subjectively, qualitatively or quantitatively,
and described using general terms or mathematically (such as a probability or a frequency over a given time
period).
Note 2 to entry: The English term “likelihood” does not have a direct equivalent in some languages; instead, the
equivalent of the term “probability” is often used. However, in English, “probability” is often narrowly interpreted
as a mathematical term. Therefore, in risk management terminology, “likelihood” is used with the intent that it
should have the same broad interpretation as the term “probability” has in many languages other than English.
Note 3 to entry: Any consequence can escalate through cascading and cumulative effects.
Note 2 to entry: Controls may not always exert the intended or assumed modifying effect.
[SOURCE: ISO Guide 73:2009, 3.8.1.6, modified — Note 2 to entry has been modified.]
Note 2 to entry: Consultation is a two-way process of informed communication between an organization and its
interested parties on an issue prior to making a decision or determining a direction on that issue. Consultation is:
3.2.3
iTeh STANDARD PREVIEW
risk assessment
overall process of risk identification (3.2.4), risk analysis (3.2.5) and risk evaluation (3.2.6)
[SOURCE: ISO Guide 73:2009,(standards.iteh.ai)
3.4.1]
3.2.4
risk identification ISO/IEC 27005:2022
https://standards.iteh.ai/catalog/standards/sist/a81e3455-413d-48cd-9a3c-
process of finding, recognizing and describing risks (3.1.3)
71cd98fbe1e1/iso-iec-27005-2022
Note 1 to entry: Risk identification involves the identification of risk sources (3.1.6), events (3.1.11), their causes
and their potential consequences (3.1.14).
Note 2 to entry: Risk identification can involve historical data, theoretical analysis, informed and expert opinions,
and interested parties’ needs.
[SOURCE: ISO Guide 73:2009, 3.5.1, modified — "interested party" has replaced "stakeholder" in Note 2
to entry.]
3.2.5
risk analysis
process to comprehend the nature of risk (3.1.3) and to determine the level of risk (3.1.15)
Note 1 to entry: Risk analysis provides the basis for risk evaluation (3.2.6) and decisions about risk treatment
(3.2.7).
[SOURCE: ISO Guide 73:2009, 3.7.1, modified — “significance” has replaced “magnitude”.]
3.2.7
risk treatment
process to modify risk (3.1.3)
Note 1 to entry: Risk treatment can involve:
— avoiding the risk by deciding not to start or continue with the activity that gives rise to the risk;
— sharing the risk with another party or parties (including contracts and risk financing); and
Note 2 to entry: Information security risk treatment does not include “taking or increasing risk in order to pursue
an opportunity” but the organization can have this option for general risk management.
Note 3 to entry: Risk treatments that deal with negative consequences are sometimes referred to as “risk
mitigation”, “risk elimination”, “risk prevention” and “risk reduction”.
Note 4 to entry: Risk treatment can create new risks or modify existing risks.
Note 2 to entry: Risk sharing can be carried out through insurance or other forms of contract.
Note 3 to entry: The extent to which risk is distributed can depend on the reliability and clarity of the sharing
arrangements.
Note 2 to entry: The level of risk (3.1.15) retained can depend on risk criteria (3.1.7).
[SOURCE: ISO Guide 73:2009, 3.8.1.5, modified — the word “temporary” has been added at the start of
the definition and the phrase; “Risk retention includes the acceptance of residual risks” has replaced
“Retention can be restricted to a certain period of time “ in Note 1 to entry.]
As Figure 1 illustrates, the information security risk management process can be iterative for risk
assessment and/or risk treatment activities. An iterative approach to conducting risk assessment can
increase depth and detail of the assessment at each iteration. The iterative approach provides a good
balance between minimizing the time and effort spent in identifying controls, while still ensuring that
risks are appropriately assessed.
Context establishment means assembling the internal and external context for information security
risk management or an information security risk assessment.
If the risk assessment provides sufficient information to effectively determine the actions required
to modify the risks to an acceptable level, then the task is complete and the risk treatment follows.
If the information is insufficient, another iteration of the risk assessment should be performed. This
can involve a change of context of the risk assessment (e.g. revised scope), involvement of expertise in
the relevant field, or other ways to collect the information required to enable risk modification to an
acceptable level (see "risk decision point 1" in Figure 1).
Risk treatment involves an iterative process of:
— formulating and selecting risk treatment options;
— planning and implementing risk treatment;
— assessing the effectiveness of that treatment;
— deciding whether the remaining risk is acceptable;
— taking further treatment if not acceptable.
It is possible that the risk treatment does not immediately lead to an acceptable level of residual risks. In
this situation, another attempt to find further risk treatment can be performed, or there can be another
iteration of the risk assessment, either as a whole or in parts. This can involve a change of context of the
risk assessment (e.g. by a revised scope) and involvement of expertise in the relevant field. Knowledge
about relevant threats or vulnerabilities can lead to better decisions about suitable risk treatment
activities in the next iteration of the risk assessment (see "risk decision point 2" in Figure 1).
Context establishment is discussed in detail in Clause 6, risk assessment activities in Clause 7 and risk
treatment activities in Clause 8.
Other activities necessary for managing information security risks are discussed in Clause 10.
iTeh STANDARD PREVIEW
5.2 Information security risk management cycles
(standards.iteh.ai)
The risk assessment and the risk treatment should be updated on a regular basis and based on
changes. This should apply to, the entire risk assessment and the updates can be divided into two risk
management cycles: ISO/IEC 27005:2022
https://standards.iteh.ai/catalog/standards/sist/a81e3455-413d-48cd-9a3c-
— strategic cycle, where business assets, risk sources and threats, target objectives or consequences
71cd98fbe1e1/iso-iec-27005-2022
to information security events are evolving from changes in the overall context of the organization.
This can result as inputs for an overall update of the risk assessment or risk assessments and the
risk treatments. It can also serve as an input for identifying new risks and initiate completely new
risk assessments;
— operational cycle, where the above-mentioned elements serves as input information or changed
criteria that will affect a risk assessment or assessment where the scenarios should be reviewed
and updated. The review should include updating of the corresponding risk treatment as applicable.
The strategic cycle should be conducted at longer time basis or when major changes occur while the
operational cycle should be shorter depending on the detailed risks that are identified and assessed as
well as the related risk treatment.
The strategic cycle applies to the environment in which the organization seeks to achieve its objectives,
while the operational cycle applies to all risk assessments considering the context of the risk
management process. In both cycles, there can be many risk assessments with different contexts and
scope in each assessment.
6 Context establishment
An organization is defined as person or group of people that has its own functions with responsibilities,
authorities and relationships to achieve its objectives. An organization is not necessarily a company,