IA-11 Re-authentication
Requires users to re-authenticate when organization-defined circumstances or situations occur, such as a change of role or privilege, use of a more sensitive function, or expiry of an authenticated session.
4
artefacts
2
held by a system
0
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
- Configuration evidence showing re-authentication enforced at those points · Identity provider / directory
- Sample logs showing re-authentication events occurring · Identity provider / directory
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Documented list of circumstances that require re-authentication · Policy repository / GRC workspace
- Design note covering re-authentication for privileged and sensitive operations · 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
- Circumstances never defined, so re-authentication happens only at session expiry
- Privilege elevation performed without re-proving identity
- Long lived tokens keep sessions alive past any re-authentication point
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 sheetIA-10 Adaptive Authentication. Require individuals accessing the system to employ [organization-defined] under specific [organization-defined] · IA-12 Identity proofing