Information security risk treatment for ISO 27001 Requirement 8.3
What is involved in requirement 8.3?
Clause 8 of the ISO 27001 standard deals with the operation of the information security management system as needed to meet information security requirements to achieve the information security objectives determined in 6.2.
Under clause 8.3, the requirement is for the organisation to implement the information security risk treatment plan and retain documented information on the results of that risk treatment. This requirement is therefore concerned with ensuring that the risk treatment processes described in clause 6.1, Actions to address risks and opportunities, are actually taking place. This should include evidence and clear audit trails of reviews and actions, showing the movements of the risk over time as results of investments emerge (not least also giving the organisation as well as the auditor confidence that the risk treatments are achieving their goals). Like other parts of clause 8 this is already achieved if the organisation has addressed the overall ISMS with the approach outlined in clause 7.5.
Meeting the requirement to implement information security risk treatment
To meet the requirements for 8.3 you must be able to evidence that the risk treatment plan described in clause 6.1 is being implemented.
As described in 6.1 more fully this must include the evidence behind the treatment. In simple terms ‘treatment’ can be work you are doing internally to control and tolerate the risk, or it could mean steps you are taking to transfer the risk (e.g. to a supplier), or it could be to terminate a risk entirely. The controls selected to manage the risks must consider, but are not limited to, those described in Annex A of the standard. These Annex A controls form the statement of applicability (SoA) which describes all the controls and why they have, or haven’t, been implemented by the organisation.
How to create a risk treatment and manage your risk treatment process
Risk treatment should be considered alongside risk assessment and ultimately feed into the SoA too.
Typically, organisations find that managing and evidencing risk is the most complex part of ISO 27001. Read our recent article Information Security Risk Management Explained to explore risk management more fully. It can take days, weeks, or months of work to establish a fully operational risk solution. That effort means establishing the conformant risk assessment methodology, a way of documenting and capturing the evidence of the whole security risk management process, as well as going through it for the first full set of risks and treatments.
- A template policy for Clause 8. of ISO 27001:2013
- A template policy and methodology for clause 6.1 which includes a comprehensive yet pragmatic approach to risk identification, analysis, and treatment, as well as ongoing monitoring and review
- Simple to use risk management tools, as described in the above policy and methodology, which produce and maintain the treatment plan
- A whole bank of popular risks together with suggested Annex A controls to link to and treat the risk around
- Workspaces to capture all of the work done, enabling retention of the documented information within the tools and offers links back to the controls and policies used to address the risks and issues
- Dynamically created Statement of Applicability, linking back to the Annex A Controls
- One joined-up place to securely manage the whole ISMS
Ready to take action?
Discover how ISMS.online can help you achieve or improve on your ISMS objectives
ISO 27001 Annex A Controls
- A.5 Information security policies
- A.6 Organisation of information security
- A.7 Human resource security
- A.8 Asset management
- A.9 Access control
- A.10 Cryptography
- A.11 Physical and environmental security
- A.12 Operations security
- A.13 Communications security
- A.14 System acquisition, development, and maintenance
- A.15 Supplier relationships
- A.16 Information security incident management
- A.17 Information security aspects of business continuity management
- A.18 Compliance
ISO 27001 requirements
- 4.1 Understanding the organisation and its context
- 4.2 Understanding the needs and expectations of interested parties
- 4.3 Determining the scope of the information security management system
- 4.4 Information security management system
- 5.1 Leadership and commitment
- 5.2 Information Security Policy
- 5.3 Organizational roles, responsibilities and authorities
- 6.1 Actions to address risks and opportunities
- 6.2 Information security objectives and planning to achieve them
- 7.1 Resources
- 7.2 Competence
- 7.3 Awareness
- 7.4 Communication
- 7.5 Documented information
- 8.1 Operational planning and control
- 8.2 Information security risk assessment
- 8.3 Information security risk treatment
- 9.1 Monitoring, measurement, analysis and evaluation
- 9.2 Internal audit
- 9.3 Management review
- 10.1 Nonconformity and corrective action
- 10.2 Continual improvement