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. Clause 7, Annex A informative
The input of 7.1 is all information about the organization that is relevant to establishing the context. The action: the external and internal context should be established. This covers the basic criteria (7.2), scope and boundaries (7.3) and a suitable organization that operates the risk management (7.4).
The implementation guidance says it is essential to determine the purpose, because it influences the overall process and especially the context. “It is essential”. The purpose can be: to support an ISMS; legal compliance and demonstration of due care; preparation of a business continuity plan; preparation of an incident response plan; a description of the information security requirements for a product, a service or a mechanism. The guidance for the elements that support an ISMS is treated further in 7.2, 7.3 and 7.4. Output: the establishment of the basic criteria, of scope and boundaries, and of the organization for the process.
7.2.1: depending on the scope and the objectives, different approaches can apply. The approach can also differ by iteration. A suitable approach should be selected or developed that addresses basic criteria: evaluation criteria, impact criteria, acceptance criteria. In addition the organization should assess whether the needed resources are available to carry out the risk assessment and to draw up a treatment plan, to establish and implement policies and procedures including the selected controls, to monitor the controls, and to monitor the process itself.
7.2.2: evaluation criteria should be developed in order to evaluate the organization's information security risk, taking into account the strategic value of the business information process, the criticality of the information assets involved, the operational and business importance of availability, confidentiality and integrity, and the expectations and perceptions of stakeholders and negative consequences for image and reputation. The criteria can additionally be used to set priorities for treatment. “Can”.
7.2.3 carries the note that ISO 31000 uses “consequence criteria” instead of “impact criteria”. Impact criteria should be developed and specified as the degree of harm or of cost to the organization caused by an information security event, taking into account the classification of the information asset affected, breaches of information security, for example loss of confidentiality, integrity and availability, impaired operations internally or at third parties, the loss of business and financial value, the disruption of plans and deadlines, and damage to reputation. ISO 31000 is not retold.
7.2.4: acceptance criteria should be developed and specified. They often depend on policies, objectives and the interests of stakeholders. The organization should set its own scales for levels of risk acceptance. In the development, the following should be taken into account: the criteria can contain several thresholds, with a desired target level and the possibility that more senior managers accept risks above it under specified circumstances; they can be expressed as a ratio of estimated gain or other business benefit to the estimated risk; different criteria can apply to different classes of risk; they can contain requirements for a later additional treatment, for example a risk can be accepted if approval and commitment exist to reduce it to an acceptable level within a specified time. The criteria can differ according to how long the risk is expected to exist, for example for a temporary activity. They should be drawn up taking into account business, operations, technology, finance and social and humanitarian factors. “Can” remains a possibility. Further information can be in Annex A.
7.3: the organization should establish scope and boundaries. According to the wording of the guidance, the scope needs to be established so that all relevant assets are taken into account in the assessment. The boundaries need to be identified so that risks which can arise across these boundaries are treated. The English wording is “needs to” twice, not “shall”. Information about the organization should be collected in order to determine the environment and its relevance. When establishing the scope, the organization should take into account: strategic business objectives, strategies and policies; business processes; functions and structure; the information security policy; the organization's overall approach to risk management; information assets; locations and their geographical characteristics; constraints that act on the organization; the expectation of stakeholders; the socio-cultural environment; interfaces, that is the exchange of information with the environment. In addition the organization should justify every exclusion from the scope. Examples of the scope can be an IT application, an IT infrastructure, a business process or a specified part of an organization. “May”. Further information can be in Annex A.
7.4: organization and responsibilities for the process should be established and maintained. As the main roles and responsibilities the clause names: development of a process suitable for the organization; identification and analysis of the stakeholders; definition of the roles and responsibilities of all internal and external parties; establishment of the needed relationships with stakeholders and of the interfaces to higher-level risk management functions, for example operational risk management, and to other relevant projects or activities; definition of escalation paths for decisions; definition of the records to be kept. This organization should be approved by the responsible managers. 7.4 does not prescribe an organization chart.
Annex A is informative. A.1 speaks of examining the organization: purpose, business, mission, values and strategies, together with what contributes to their development, for example subcontracting. It explains these words with examples and names forms of structure, including divisional and functional structure, and the remark that an organization can have elements of both forms. An organization chart should show reporting lines and delegation and also other information flows. A.2 says all constraints that determine the organization and its orientation of information security should be taken into account. Their source can lie inside or outside. Resource and emergency constraints belong among the most important. These are recommendations of an informative annex. They do not create a second requirement beside Clause 7. A.3 continues the list of constraints. The examples are not copied here as a checklist.
Not in this text: a context method from ISO 31000, an organization chart as an obligation, and the example descriptions from Annex A as a shall-list.