6.6.3 User responsibilities
Users must meet their own responsibilities for protecting authentication information as the base guidance requires, read as protecting the personal data that their credentials unlock.
3
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Acceptable use and authentication terms accepted by users · Policy repository / GRC workspace
- Awareness content on credential protection · Policy repository / GRC workspace
- Evidence of enforcement where terms were breached · 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
- Terms accepted at induction and never refreshed
- Credential sharing tolerated in operational teams
- No consequence applied when sharing is discovered
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 sheet6.6.2 User access management · 6.6.4 System and application access control