8.3.9 Password change frequency if only factor
If passwords are the only authentication factor, they are changed at least every 90 days, or access to resources is dynamically analyzed and access granted based on security posture.
5
artefacts
1
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
- Dynamic access posture tool configuration if used · Identity provider / directory
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Password expiration policy set to 90 days where applicable · Policy repository / GRC workspace
- Coverage matrix of password-only systems · Policy repository / GRC workspace
- Sample of forced password changes · Policy repository / GRC workspace
- Risk analysis supporting posture-based approach · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Identity provider / directory on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Expiration disabled with no compensating control
- Posture analysis not deployed
- Inconsistent enforcement
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.8 Authentication policy communicated · 8.3.10 Service provider customer password guidance