Clause 8 – Operation
Actually perform risk assessments at planned intervals (e.g. yearly) and whenever significant changes occur, using the method from 6.1.2, and keep the results.
Teams should prove that information security risk assessments are performed on a planned cycle and repeated when material change occurs. Retain the method reference from 6.1.2, identify ownership by the risk owner or ISMS manager, and preserve dated outputs that show scope, criteria, and triggers. A common weakness is treating the risk register as static rather than as a living record tied to incidents, new suppliers, system changes, and formal review dates.
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
These free kit documents help you document or evidence clause 8.2. Each one is tailored to your organization when you build your kit.
Review the dependencies with 6.1.2 — Information security risk assessment and 8.3 — Information security risk treatment (operation). Keep the ownership and evidence consistent across these activities.
Plan your ISO/IEC 27001 implementation timeline for the wider implementation context.
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.
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.
Start freePlain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.