What evidence do auditors commonly ask for on OIS-01 Information Security Management System (ISMS)?

ISMS scope statement listing the in scope legal entities, sites and cloud delivery processes; Statement of Applicability with inclusion and exclusion justifications for every control; Minutes, inputs and decisions of the most recent management review; Valid certificate and certification body audit report for the management system.

What is the most common gap auditors find on OIS-01?

Scope leaves out subsidiaries or data centre sites that in fact operate production components

BSI C5 (121-criteria catalogue) · C5: Organisation of Information Security

`OIS-01` Information Security Management System (ISMS)

Operate an information security management system aligned to ISO/IEC 27001 covering the organisational units, sites and processes that deliver the cloud service, and retain documented scope, statement of applicability and the latest management review results.

Source: BSI C5 (121-criteria catalogue), OIS-01. 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 BSI C5 (121-criteria catalogue) in the compliance library.

The edition of the catalogue is not stamped here; check the edition your attestation is issued against.

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

Minutes, inputs and decisions of the most recent management review · Policy repository / GRC workspace
Valid certificate and certification body audit report for the management system · Policy repository / GRC workspace

governing documentDocuments that govern the control

ISMS scope statement listing the in scope legal entities, sites and cloud delivery processes · Policy repository / GRC workspace
Statement of Applicability with inclusion and exclusion justifications for every control · 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

Scope leaves out subsidiaries or data centre sites that in fact operate production components
Statement of Applicability not reconciled with the control set actually in force
Management review last held more than twelve months ago or held without recorded decisions

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

INQ-04 Limiting Access to or Disclosure of Data in Investigation Requests · OIS-02 Information Security Policy