What evidence do auditors commonly ask for on 8.2.3 Risk assessment?

Documented risk assessment process; Risk register scoped to prioritized activities and their required resources; Analysis and evaluation records with the criteria applied; Treatment decisions recorded with rationale, including acceptance.

What is the most common gap auditors find on 8.2.3?

Risk register covering the enterprise generally rather than the prioritized activities specifically

ISO 22301:2019 · Operation, ISO 22301:2019

`8.2.3` Risk assessment

Put in place and keep up a process for assessing risk that identifies what could disrupt the organization's prioritized activities and the resources those activities need, analyses and evaluates those risks, and decides which ones need treatment.

Source: ISO 22301:2019, 8.2.3. 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 22301:2019 in the compliance library.

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

Analysis and evaluation records with the criteria applied · Policy repository / GRC workspace
Treatment decisions recorded with rationale, including acceptance · Policy repository / GRC workspace

governing documentDocuments that govern the control

Documented risk assessment process · Policy repository / GRC workspace
Risk register scoped to prioritized activities and their required resources · 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

Risk register covering the enterprise generally rather than the prioritized activities specifically
Evaluation criteria undefined, so treatment decisions are unreviewable
Resource level risks such as single site or single supplier concentration not surfaced
Accepted risks recorded without an acceptance authority

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.2.2 Business impact analysis · 8.3 Business continuity strategies and solutions