EvidenceSheet

8.1.1 All security policies and operational procedures that are identified in Requirement 8 are: • Documented. • Kept up to date. • In use. • Known to all affected parties

All security policies and operational procedures that are identified in Requirement 8 are: • Documented. • Kept up to date. • In use. • Known to all affected parties.

4
artefacts
0
held by a system
1
at each review
hard
to go live
Document repository
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

  • Pre task briefings and last minute risk assessments · Document repository

governing documentDocuments that govern the control

  • Operational procedures and safe systems of work (SSOW) · Policy repository / GRC workspace
  • Permit to work systems for high risk activities · Document repository
  • Work adaptation evidence (ergonomic adjustments, schedule design) · 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

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

7.3.3 The access control system(s) is set to “deny all” by default · 8.1.2 Roles and responsibilities for performing activities in Requirement 8 are documented, assigned, and understood