EvidenceSheet

IDM-03 Locking and withdrawal of user accounts in the event of inactivity or multiple failed logins

Automatically lock accounts of staff and automated system components left unused for two months, require authorised approval to reinstate them, revoke them outright after six months, and re-run the full granting procedure before any reissue.

Source: BSI C5 (121-criteria catalogue), IDM-03. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open BSI C5 (121-criteria catalogue) in the compliance library.

The edition of the catalogue is not stamped here; check the edition your attestation is issued against.

4
artefacts
2
held by a system
2
at each review
easy
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

  • System configuration showing the dormancy threshold set at two months · Cloud console / configuration management
  • List of accounts deleted at the six month point with evidence of full re-request where reinstated · Identity provider / directory

periodic reviewEvidence produced at each review

  • Report of accounts locked for dormancy in the period with their lock dates · Identity provider / directory
  • Unlock approval records naming the authorising person or system component · Document repository

governing documentDocuments that govern the control

none for this control

First move

Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.

Common gaps auditors find

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 sheet

IDM-02 Granting and change of user accounts and access rights · IDM-04 Withdraw or adjust access rights as the task area changes