IA.L2-3.5.7 Password Complexity
Set a minimum complexity for passwords, and require that a newly created password differ in its characters from the one it replaces.
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
- Configured password complexity settings · Policy repository / GRC workspace
- Setting or procedure requiring changed characters on password creation · Policy repository / GRC workspace
- Coverage across directories and standalone systems · 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
- Complexity enforced centrally but not on local or application accounts
- Character change requirement absent so minor edits are accepted
- Policy documented without technical 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 sheetIA.L2-3.5.6 Identifier Handling · IA.L2-3.5.8 Password Reuse