IAM-02 Strong Password Policy and Procedures
Keep an approved password policy that sets strength requirements, implement it in the systems it governs, and review it at least annually.
4
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 review record · Document repository
governing documentDocuments that govern the control
- The approved password policy with its strength requirements · Policy repository / GRC workspace
- Technical configuration enforcing the policy per system · Policy repository / GRC workspace
- Exception records where a system cannot enforce the policy · 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
- Policy strength requirements not enforceable in some systems and no exception recorded
- Policy stated in words with no configuration evidence
- Requirements based on outdated guidance such as frequent forced rotation without other controls
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 sheetIAM-01 Identity and Access Management Policy and Procedures · IAM-03 Identity Inventory