EvidenceSheet
ISO/IEC 27001:2022 · Clause 6

6.1.1 Actions to address risks and opportunities: general

When planning the ISMS the organization considers the 4.1 issues and the 4.2 requirements and identifies the risks and opportunities it needs to address so that the ISMS can achieve its outcomes, undesired effects are prevented or reduced, and continual improvement happens. It must plan actions to address them, and plan how to integrate and implement those actions in its ISMS processes and how to evaluate whether they worked.

Source: ISO/IEC 27001:2022, 6.1.1. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ISO/IEC 27001:2022 in the compliance library.

Clauses 4 to 10 are the management-system requirements: none of them can be excluded when an organisation claims conformity. The 93 Annex A controls are a reference set: one may be excluded with a justification in the Statement of Applicability. Certification bodies assess conformity; the evidence lists here are what auditors commonly ask for, not a list the standard prescribes.

4
artefacts
0
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

  • Records evaluating whether the actions were effective · Document repository
  • Evidence that opportunities, not only risks, were considered · Document repository

governing documentDocuments that govern the control

  • A register of ISMS-level risks and opportunities traced to the 4.1 issues and 4.2 requirements · Policy repository / GRC workspace
  • Action plans addressing each, with owners and integration into ISMS processes · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

5.3 Organizational roles, responsibilities and authorities · 6.1.2 Information security risk assessment