EvidenceSheet

SCOPE.1 Scope Definition

Define the scope of certification covering all end user devices, servers, networks, cloud services, and remote workers. Sub-set scoping must use clear boundary by firewall or VLAN.

3
artefacts
0
held by a system
1
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

  • Boundary firewall/VLAN evidence · Cloud console / configuration management

governing documentDocuments that govern the control

  • Scope description document · Policy repository / GRC workspace
  • Device inventory list (make/model/OS) · 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

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

SC.9 Device Unlocking Credentials and Brute-Force Protection · SCOPE.2 Cloud Services in Scope