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 an
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
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
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
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 sheetINQ-04 Limiting Access to or Disclosure of Data in Investigation Requests · OIS-02 Information Security Policy