IDM-08 Confidentiality of authentication information
Hand out authentication secrets in a controlled manner that preserves confidentiality, force initial passwords to be replaced at first logon and to expire within fourteen days, inform users of resets, and store passwords
4
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
- Procedure for issuing initial credentials and the channel used to convey them to the recipient · Policy repository / GRC workspace
- Setting that expires an unused initial password after at most fourteen days · Policy repository / GRC workspace
- Hashing algorithm and parameters applied to stored credentials · Policy repository / GRC workspace
- Copy of the message a user receives after a password change or reset · 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
- Initial passwords identical or built from a predictable pattern across new starters
- Credentials held with a fast unsalted hash or reversibly encrypted in legacy components
- Technically unavoidable deviations accepted without the required risk analysis and compensating measures
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 sheetIDM-07 Access to cloud customer data · IDM-09 Authentication mechanisms