What evidence do auditors commonly ask for on 6.2.2 Determining business continuity objectives?

Plan per objective covering activity, resource, owner, date and evaluation method; Evidence the resource named was actually made available; Evaluation results against the stated method.

What is the most common gap auditors find on 6.2.2?

Plans that name an owner and a date and nothing else

ISO 22301:2019 · Planning, ISO 22301:2019

`6.2.2` Determining business continuity objectives

For each objective, determine what will be done, what resources it needs, who is responsible, when it will be completed and how the results will be evaluated.

Source: ISO 22301:2019, 6.2.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 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

Evidence the resource named was actually made available · Policy repository / GRC workspace
Evaluation results against the stated method · Policy repository / GRC workspace

governing documentDocuments that govern the control

Plan per objective covering activity, resource, owner, date and evaluation method · 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

Plans that name an owner and a date and nothing else
Resource requirement omitted, so the objective competes for unallocated effort
Evaluation method left undefined until after the deadline passes

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

6.2.1 Establishing business continuity objectives · 6.3 Planning changes to the business continuity management system