Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
Clause 6.1.1 Actions to address risks and opportunities – General
Mandatory requirement
What it means in plain language
When planning the ISMS, think about what could stop it from achieving its goals (risks) and what could make it better (opportunities), based on your context and interested parties. Plan actions for them, build those actions into your processes and later check whether they worked.
Is it mandatory? Yes. Clauses 4–10 are the management-system requirements; all of them must be met to be certified, and none can be excluded.
Documented information
No specific document; evidenced through the risk process.
Why this requirement matters
This clause is often missed when teams treat risk work as a one-time assessment instead of part of ISMS planning. Good practice is to look beyond threats: recurring manual effort, gaps in skills, or fragmented tooling can all be opportunities to improve how the ISMS operates. Teams should connect those items to action owners, due dates, and later review so management can see whether planned actions actually moved the ISMS forward.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
The organisation records threats in a risk register but does not track opportunities, so improvement ideas never become planned actions or are lost after meetings.
Actions are listed without owners or review dates, making it unclear who must deliver them or how effectiveness will be checked later.
ISMS risks linked to context changes, such as growth or outsourcing, are not revisited, so the planning basis becomes outdated and incomplete.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Use the Context of the Organization template to anchor ISMS-level risks and opportunities to real drivers such as growth, new markets, supplier reliance, remote working, or regulatory pressure. For each item, record the affected objective, the expected consequence or benefit, the owner, and the action that will reduce impact or capture the opportunity.
Treat actions as managed work, not notes. Put them into the Risk Register & Treatment Plan with due dates, accountable roles, status, and a practical check for effectiveness, such as fewer overdue tickets, faster incident response, or improved review completion. Keep the wording specific enough that progress can be verified.
Bring the register into management review and planning meetings so decisions are explicit: accept, reduce, transfer, or pursue. If an opportunity depends on budget, tooling, or staff time, capture the dependency rather than leaving it implicit, because unclear assumptions often cause actions to stall.
Refresh the register when context changes, after significant incidents, or when a project introduces new risks or improvement ideas. Retain evidence of reassessment, such as revised action plans, meeting notes, and closure records showing why a risk was closed or an opportunity was deprioritised.
What an auditor will ask to see
Risk Register & Treatment Plan entries showing risks, opportunities, owners, due dates, and effectiveness checks tied to the relevant objective or context driver.
Management review notes documenting decisions on proposed actions, including accepted risks, funded improvements, and deferred opportunities with reasons.
Updated Context of the Organization template or planning notes showing how changes in suppliers, staffing, or scope led to new ISMS actions.
Baseline documents in the kit
These free kit documents help you document or evidence clause 6.1.1. Each one is tailored to your organization when you build your kit.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.