8.3.11 Hardware token and other factor protection
When authentication factors such as physical or logical security tokens, smart cards, or certificates are used, the factor is assigned to an individual user and not shared.
5
artefacts
1
held by a system
1
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
- Certificate issuance log per user · SIEM / log platform
periodic reviewEvidence produced at each review
- Lost or stolen token replacement records · Document repository
governing documentDocuments that govern the control
- Token inventory linking each token to an individual · Policy repository / GRC workspace
- Procedure prohibiting sharing · Policy repository / GRC workspace
- Sample audit confirming one token per person · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Tokens shared in teams
- Inventory not maintained
- No anti-sharing policy
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 sheet8.3.10.1 SP password rotation or posture · 8.4.1 MFA is implemented for all non-console access into the CDE for personnel with administrative access