164.308(a)(5)(ii)(C) Log-in Monitoring (Addressable)
Implement procedures for monitoring log-in attempts and reporting discrepancies. NIST recommends automated alerts on failed authentication thresholds and anomalous login patterns.
4
artefacts
2
held by a system
1
at each review
easy
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
- Failed login alert configuration · Identity provider / directory
- Sample monitoring reports · Identity provider / directory
periodic reviewEvidence produced at each review
- Anomalous login investigation records · Identity provider / directory
governing documentDocuments that govern the control
- Account lockout policy · Policy repository / GRC workspace
First move
Automate the pull from your Identity provider / directory. Scheduled export of users, roles and MFA state from the directory; access-review completion pulled from the IdP, not a spreadsheet.
Common gaps auditors find
- No lockout threshold defined
- Failed logins logged but not alerted on
- Service accounts excluded from monitoring
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 sheet164.308(a)(5)(ii)(B) Protection from Malicious Software (Addressable) · 164.308(a)(5)(ii)(D) Password Management (Addressable)