SC.8 Process for Compromised Passwords
Have a process to change passwords promptly when the user knows or suspects the password or account has been compromised.
3
artefacts
1
held by a system
0
at each review
moderate
to go live
Ticketing / ITSM
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Service desk ticket sample · Ticketing / ITSM
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Password reset procedure · Policy repository / GRC workspace
- Incident playbook section · Document repository
First move
Start with the 1 of 3 artefacts that already live in a system (Ticketing / ITSM); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- no documented reset workflow
- users unaware how to report
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 sheetSC.7 Educate Users on Strong Passwords · SC.9 Device Unlocking Credentials and Brute-Force Protection