COM-01 Identification of applicable legal, regulatory, self-imposed or contractual requirements
Explicitly define and document the legal, regulatory, self imposed and contractual requirements bearing on the information security of the cloud service, together with the procedures the provider uses to comply with each
4
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Register of applicable legal, regulatory, self imposed and contractual security requirements · Policy repository / GRC workspace
- Mapping of each requirement to the procedure that satisfies it · Policy repository / GRC workspace
- Evidence of legal and regulatory horizon scanning keeping the register current · Policy repository / GRC workspace
- Named owner recorded against each requirement · Document repository
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
- Register lists statutes only and omits commitments made to customers in contracts
- Requirements identified with no procedure named against them
- Register not refreshed when the service began operating in a new jurisdiction
- Self imposed commitments made in public statements never captured
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 sheetBCM-04 Verification, updating and testing of the business continuity · COM-02 Policy for planning and conducting audits