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
Mandatory requirement Documented information required
What it means in plain language
For each unacceptable risk, decide what to do (reduce, avoid, transfer or accept), choose the controls needed, compare them with Annex A so nothing important is missed, and produce a Statement of Applicability. Build a treatment plan and get risk owners to approve it and accept the remaining (residual) risk.
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
Statement of Applicability.
Information about the risk treatment process (treatment plan).
Why this requirement matters
Teams should turn risk assessment outputs into an explicit treatment decision for every unacceptable risk. The key requirement is traceability: each risk needs a named owner, a chosen response, linked Annex A controls where relevant, and a documented residual risk acceptance path. Reviewers should be able to follow why a control was selected, why an option was rejected, and how the Statement of Applicability stays aligned with business context and legal or contractual duties.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
A risk is marked for treatment, but the register omits the selected response, owner, or due date, leaving no accountable path to closure.
The Statement of Applicability lists controls as applicable without risk-based rationale, or omits a relevant Annex A control tied to the treatment plan.
Residual risk is noted as accepted, but there is no evidence of risk-owner approval, escalation threshold review, or linkage to management review records.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
For each unacceptable risk, record whether the response is reduce, avoid, transfer, or accept, and make the decision explicit in the Risk Register & Treatment Plan. Name the risk owner, treatment owner, target date, and the specific condition that makes the risk acceptable after treatment. Avoid vague phrases such as “mitigated” without describing what changed operationally.
Build the Statement of Applicability from the treatment decisions, not from a generic checklist. For every Annex A control, note whether it applies, the reason it applies or does not apply, and the specific risk, legal duty, or contractual term behind that choice. If a control is excluded, document the compensating logic so the exclusion can be questioned and defended.
Check treatment completeness by comparing each chosen measure against the risk scenario: if the threat actor, asset, or impact changes, the selected control set may need to change too. Use a periodic review cadence, such as during management review or quarterly risk review, to confirm overdue actions, expired acceptances, and treatment dependencies across projects or suppliers.
Require residual risk approval from the accountable risk owner before closure, and keep the acceptance wording specific: which risk remains, what threshold is accepted, for how long, and under what monitoring trigger a revisit is required. Where risk is escalated, retain evidence of management review discussion, decision, and any added action items or controls.
What an auditor will ask to see
A signed or approved Statement of Applicability showing each control’s status and justification for applicability or exclusion.
Risk Register & Treatment Plan entries with treatment type, control mapping, owner, target date, and residual risk acceptance note.
Management review minutes or risk committee records capturing decisions on high residual risks and escalations.
Action tracker extracts showing overdue treatment actions, revised dates, and closure approval by the risk owner.
Baseline documents in the kit
These free kit documents help you document or evidence clause 6.1.3. 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.