What is the most common gap auditors find on IA-2(8)?

Authentication for the selected account types relies on static credentials that can be captured and replayed

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

`IA-2(8)` Identification and Authentication (Organizational Users) | Access to Accounts: Replay Resistant

Q: What evidence do auditors commonly ask for on IA-2(8) Identification and Authentication (Organizational Users) | Access to Accounts: Replay Resistant?

Identification and authentication policy; System security plan; Procedures addressing user identification and authentication; System design documentation; System configuration settings and associated documentation; System audit records.

Implement replay-resistant authentication mechanisms for access to Selection (one or more): privileged accounts; non-privileged accounts.

Source: NIST SP 800-53 Rev 5, IA-2(8). 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

moderate

to go live

Identity provider / directory

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

List of privileged system accounts · Identity provider / directory
Test of Mechanisms supporting and/or implementing identification and authentication capabilities; Mechanisms supporting and/or implementing replay-resistant authentication mechanisms · 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
System security plan · Policy repository / GRC workspace
Procedures addressing user identification and authentication · Policy repository / GRC workspace
System design documentation · Policy repository / GRC workspace
System configuration settings and associated documentation · Policy repository / GRC workspace

First move

Start with the 2 of 8 artefacts that already live in a system (Identity provider / directory); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Authentication for the selected account types relies on static credentials that can be captured and replayed
The selection of privileged or non-privileged accounts requiring replay-resistant authentication was never documented

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-2(6) Identification and Authentication (Organizational Users) | Access to Accounts: separate Device · IA-2(10) Identification and Authentication (Organizational Users) | Single Sign-on