8.3.8 Authentication policy communicated
Authentication policies and procedures are documented and communicated to all users, including guidance on selecting strong factors and protecting them.
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 reminder evidence · Document repository
governing documentDocuments that govern the control
- User guidance document on creating strong passwords · Policy repository / GRC workspace
- Acknowledgement records of policy receipt · HR system / LMS
- Training module covering authentication hygiene · Policy repository / GRC workspace
- Sample communications (email, intranet) to users · 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
- No user-facing guidance
- Acknowledgements missing
- Training stale
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 sheet8.3.7 Password history · 8.3.9 Password change frequency if only factor