Explanations of ISO/IEC 27005:2018
The source is ISO/IEC 27005:2018(en), third edition, July 2018. Title: Information technology — Security techniques — Information security…
Read articleISO/IEC 27005:2018
For: V, IA
Source: ISO/IEC 27005:2018(en), English. Introduction, Clause 1, Clause 2, Clause 3, Clause 4, Clause 5, foreword to the edition
The introduction says the document provides guidelines for information security risk management in an organization. It provides no particular method. The organization defines its approach, for example depending on the scope of an information security management system, on the context of the risk management or on the sector. Existing methods can be used under the framework described here in order to implement the requirements of an ISMS. “Can”. The document is based on identification through assets, threats and vulnerabilities. The introduction says this method is no longer required by ISO/IEC 27001. Other approaches can be used.
The same paragraph and the foreword say the document does not contain direct guidance for implementing the ISMS requirements from ISO/IEC 27001. It is addressed to management and personnel who deal with this risk management and, as far as appropriate, to external parties that support such activities.
Clause 1 repeats: guidelines for information security risk management. The document supports the general concepts from ISO/IEC 27001 and is designed to assist a satisfactory implementation of information security on the basis of a risk management approach. “Is designed to assist”. Knowledge of the concepts, models, processes and terms from ISO/IEC 27001 and ISO/IEC 27002 is important for a complete understanding. Neither stands here as an edition available to these articles. The document is applicable to all kinds of organizations that want to handle risks which can impair the information security of the organization. Examples: commercial enterprises, government authorities, non-profit organizations.
Clause 2 names only ISO/IEC 27000 as a normative reference. Clause 3 says the terms from ISO/IEC 27000 and the following apply. A list of terms of its own, with definitions, does not stand in the text of Clause 3 that was read. The terminology databases of ISO and IEC are named.
Clause 4 describes the structure. Background in Clause 5. Overview in Clause 6. Then: context in Clause 7, risk assessment in Clause 8, risk treatment in Clause 9, risk acceptance in Clause 10, risk communication in Clause 11, monitoring and review in Clause 12. The annexes provide additional information. Annex A on the context. Annex B on identification and valuation of assets and on impact assessments. Annex C examples of typical threats. Annex D vulnerabilities and methods of vulnerability assessment. Annex E examples of assessment approaches. Annex F constraints for risk modification. All annexes are informative.
Clause 5 says a systematic approach is necessary in order to identify the organization's needs regarding information security requirements and to create an effective ISMS. “Is necessary” is the wording of the background. The approach should suit the organization's environment and in particular should suit the risk management of the enterprise as a whole. Security efforts should address risks effectively and in a timely manner where and when they are needed. Information security risk management should be part of all information security management activities and should be applied both in the realization and in the ongoing operation of an ISMS.
It should be a continual process. The process should establish the external and internal context, assess the risks and treat them with a treatment plan, in order to implement recommendations and decisions. Risk management analyses what can happen and what consequences are possible, before it is decided what should be done, and when, in order to reduce the risk to an acceptable level.
The contribution the process should make is listed in Clause 5: risks are identified; they are assessed according to consequences for the business and according to the likelihood of occurrence; likelihood and consequences are communicated and understood; a priority order for treatment is established; actions for reduction are prioritized; stakeholders are involved when decisions are made, and informed of the status; the effectiveness of the treatment is monitored; risks and the process are regularly monitored and reviewed; information is recorded in order to improve the approach; management and personnel are informed about the risks and the controls taken. These are objectives to which the process should contribute, not a requirements list of a certification.
The process can be applied to the organization as a whole, to a delimited part, for example a department, a location or a service, to an information system, existing or planned, or to particular aspects of control, for example business continuity planning. “Can”.
Not in this text: a method, which the guidance expressly does not prescribe, the content of ISO/IEC 27000, and implementation guidance for the requirements of ISO/IEC 27001:2022. This guidance does not say of itself that it provides that. The comparison for auditors is in 27005-10.