IA.L2-3.5.10 Cryptographically-Protected Passwords
Store and transmit passwords only in cryptographically protected form.
3
artefacts
1
held by a system
2
at each review
moderate
to go live
Identity provider / directory
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Configuration showing authentication traffic is encrypted in transit · Identity provider / directory
periodic reviewEvidence produced at each review
- Evidence of password hashing or equivalent protection at rest · Identity provider / directory
- Review confirming no plaintext credential storage · Identity provider / directory
governing documentDocuments that govern the control
none for this control
First move
Start with the 1 of 3 artefacts that already live in a system (Identity provider / directory); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Credentials stored in scripts or configuration files in plaintext
- Legacy protocols transmit credentials unprotected
- Reversible encryption used instead of one way protection
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.9 Temporary Passwords · IA.L2-3.5.11 Obscure Feedback