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: IA, EA
Source: ISO/IEC 27005:2018(en), English. Clause 1, Clause 6, introduction. Comparison with ISO/IEC 27001:2022(en), 6.1.2, 6.1.3, 8.2, 8.3, insofar as these sentences are recorded in blog/iso-iec-27001-2022.md from the 2022 PDF that is available. The edition ISO/IEC 27005:2022 is not available.
This is the guidance of 2018. It is not certifiable. A missing recommendation, a different order of the steps in 8.2 or an unused example from Annex C, D or E is not a nonconformity against this document. The annexes are informative. Clause 4 says part of the implementation guidance cannot be suitable in every case.
The introduction and the foreword say the guidance does not contain direct guidance for implementing the ISMS requirements from ISO/IEC 27001. It provides no particular method. Identification through assets, threats and vulnerabilities is, according to the introduction, no longer required by ISO/IEC 27001. Other approaches can be used. ISO/IEC 27001 stands in the bibliography without a year of edition, not in the normative references.
What an organization shall fulfil under ISO/IEC 27001:2022 for the risk assessment and the risk treatment stands in that standard, explained in 27001-04 and 27001-05. Briefly, the sentences recorded there, so that the comparison has a place to point to: 6.1.2 requires a process that establishes and maintains risk criteria, including acceptance criteria and criteria for performing the assessments, that ensures repeated assessments produce consistent, valid and comparable results, that identifies risks associated with the loss of confidentiality, integrity and availability of information within the scope and identifies the risk owners, that analyses consequences, realistic likelihood of occurrence and levels of risk, and that compares the results with the criteria and prioritizes them for treatment. Documented information on the process shall be retained. 6.1.3 requires the treatment options to be selected, all needed controls to be determined, them to be compared with Annex A, a statement of applicability to be prepared with the four particulars named there, a treatment plan to be formulated, and the risk owners' approval of the plan and acceptance of the residual risks to be obtained. Documented information on the treatment process shall be retained. 8.2 requires the assessments at planned intervals or when significant changes are proposed or occur, taking into account the criteria from 6.1.2 a), and the retention of the results. 8.3 requires the plan to be implemented and the results of the treatment to be retained.
From this guidance of 2018 it can be seen whether an organization has described a context with evaluation, impact and acceptance criteria, whether it has carried out identification, analysis of consequences, likelihood and level of risk and a comparison with the criteria, whether a treatment plan and residual risks are in place, and whether an acceptance decision of its own after the treatment should be made and recorded. Clause 6 says the detailed results should be documented. Clause 10 says the acceptance decision should be formally recorded. These are recommendations of this guidance.
The guidance does not describe the statement of applicability, nor the comparison with Annex A of ISO/IEC 27001:2022, nor the four particulars of that statement, nor the risk owners as the persons who approve the plan and accept the residual risk, nor the timing from 8.2. Its acceptance speaks of managers and decision-makers. Its sentence that controls in the ISMS would have to be risk-based is its summary of ISO/IEC 27001 without a year of edition, not the wording of 6.1.3 of the 2022 edition. The recommendation in Annex E that a method should produce repeatable results is a sentence of an informative annex. It is not the sentence in 6.1.2 b) of the 2022 edition.
Gaps that only ISO/IEC 27005:2022 would close remain open. That edition is not available.
Not in this text: an audit checklist from Annexes B to F, and a claim that following this guidance fulfils 6.1.2, 6.1.3, 8.2 and 8.3 of ISO/IEC 27001:2022. The guidance says it does not contain this implementation help. Whether the organization's process fulfils those requirements is read against ISO/IEC 27001:2022.