What evidence do auditors commonly ask for on IA-11 Re-authentication?

Identification and authentication policy; Procedures addressing user and device re-authentication; System security plan; System design documentation; System configuration settings and associated documentation; List of circumstances or situations requiring re-authentication.

What is the most common gap auditors find on IA-11?

The organization-defined circumstances requiring re-authentication were never documented

NIST SP 800-53 Rev 5 · IA - Identification and Authentication

`IA-11` Re-authentication

Require users to re-authenticate when organization-defined circumstances or situations requiring re-authentication.

Source: NIST SP 800-53 Rev 5, IA-11. 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 NIST SP 800-53 Rev 5 in the compliance library.

Base controls and their enhancements. Which apply follows the baseline you are assessed against (for example FedRAMP Moderate or High, or the low, moderate and high baselines of SP 800-53B). Text in square brackets is a parameter your organisation sets.

artefacts

held by a system

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. 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

Test of Mechanisms supporting and/or implementing identification and authentication capabilities · Identity provider / directory

periodic reviewEvidence produced at each review

System audit records · Identity provider / directory

governing documentDocuments that govern the control

Identification and authentication policy · Policy repository / GRC workspace
Procedures addressing user and device re-authentication · Policy repository / GRC workspace
System security plan · Policy repository / GRC workspace
System design documentation · Policy repository / GRC workspace
System configuration settings and associated documentation · Policy repository / GRC workspace
List of circumstances or situations requiring re-authentication · Policy repository / GRC workspace

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your Identity provider / directory 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

The organization-defined circumstances requiring re-authentication were never documented
Users are not prompted to re-authenticate when changing roles or elevating privileges as the defined circumstances require

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

IA-10 Adaptive Authentication · IA-12 Identity Proofing