12.6.3.1 Training on phishing and social engineering
Security awareness training includes threats and vulnerabilities that could impact the security of cardholder data including phishing and related attacks, and social engineering.
5
artefacts
0
held by a system
2
at each review
hard
to go live
HR system / LMS
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
- Click rates and remediation training records · HR system / LMS
- Sample assessments · Document repository
governing documentDocuments that govern the control
- Training module specifically on phishing and social engineering · HR system / LMS
- Phishing simulation campaign reports · Policy repository / GRC workspace
- Curriculum reviewed against current threats · 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
- Phishing simulations not run
- No remediation for clickers
- Content generic
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.3 Security awareness training delivered · 12.6.3.2 Training on acceptable use of end-user technologies