What evidence do auditors commonly ask for on 8.2 Information security risk assessment?

A schedule of planned risk assessments and evidence they took place; Assessments triggered by significant changes such as new systems, suppliers or reorganizations; Retained results of each assessment; Evidence the 6.1.2 a) criteria were applied.

What is the most common gap auditors find on 8.2?

Assessments happen only annually and ignore significant changes

ISO/IEC 27001:2022 · Clause 8

`8.2` Information security risk assessment

Risk assessments must be carried out at planned intervals and whenever significant changes are proposed or happen, using the criteria set in 6.1.2 a), and documented information on their results must be retained.

Source: ISO/IEC 27001:2022, 8.2. 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.

artefacts

held by a system

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

Retained results of each assessment · Policy repository / GRC workspace
Evidence the 6.1.2 a) criteria were applied · Policy repository / GRC workspace

governing documentDocuments that govern the control

A schedule of planned risk assessments and evidence they took place · Policy repository / GRC workspace
Assessments triggered by significant changes such as new systems, suppliers or reorganizations · Vendor register / contract repository

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

Assessments happen only annually and ignore significant changes
Results are overwritten rather than retained
Different criteria are used from those defined
Change triggers are not defined

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

8.1 Operational planning and control · 8.3 Information security risk treatment