EvidenceSheet

12.1.2 The information security policy is: • Reviewed at least once every 12 months. • Updated as needed to reflect changes to business objectives or risks to the environment

The information security policy is: • Reviewed at least once every 12 months. • Updated as needed to reflect changes to business objectives or risks to the environment.

5
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

  • Evidence of updates made as a result of changes to business objectives or risks to the environment · Cloud console / configuration management
  • Interview confirmation from responsible personnel about how the review is triggered and performed · Policy repository / GRC workspace

governing documentDocuments that govern the control

  • Review records showing the information security policy was reviewed at least once every 12 months, with the date and reviewer · Policy repository / GRC workspace
  • The change history linking a specific business or risk change to a specific policy revision · Policy repository / GRC workspace
  • Approval of the reviewed or updated policy by the appropriate authority · 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

12.1.1 An overall information security policy is: • Established. • Published. • Maintained. • Disseminated to all relevant personnel, as well as to relevant vendors and business partners · 12.1.3 Information security roles and responsibilities defined and acknowledged