12.6.2 Security awareness program reviewed annually
The security awareness program is reviewed at least once every 12 months and updated as needed to address emerging threats and vulnerabilities relevant to the cardholder data environment.
5
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
- Annual review minutes with attendees · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Threat landscape input documentation · Document repository
- Curriculum change log · Policy repository / GRC workspace
- Approval signatures · Document repository
- Communication of updates · 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
- No annual review
- Curriculum unchanged for years
- Threats not incorporated
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 sheet12.6.1 Formal security awareness program implemented · 12.6.3 Security awareness training delivered