SC.9 Device Unlocking Credentials and Brute-Force Protection
Require a biometric, password or PIN before a physically present user reaches device services, protect that credential against brute force by throttling attempts or locking after a small number of failures, and enforce a
3
artefacts
0
held by a system
2
at each review
hard
to go live
Endpoint management (MDM / EDR)
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
- Screenshot or export of PIN and password length enforcement · Endpoint management (MDM / EDR)
- Record of vendor default used where the setting is not configurable · Endpoint management (MDM / EDR)
governing documentDocuments that govern the control
- MDM or group policy showing lock settings and attempt limits · 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
- laptops and phones with no lock credential
- unlimited unlock attempts
- unlock PIN below the minimum length
- device-unlock credential reused for account authentication without meeting the full password rules
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 sheetSC.8 Process for Compromised Passwords · SCOPE.1 Scope Definition