What evidence do auditors commonly ask for on IA-4 Identifier Management?

SSP IA-4 statement describing identifier assignment, uniqueness and the period before an identifier may be reused; Identifier issuance records and directory settings preventing reuse of retired usernames; MFA enrolment report for all privileged and remote users; Password policy configuration export from the identity provider; Service account credential vault inventory and rotation logs; Identity proofing records for high assurance accounts.

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

Password complexity enforced but reuse not blocked across systems

FedRAMP High (NIST SP 800-53 Rev 5 baseline) · IA - Identification and Authentication

`IA-4` Identifier Management

Manage identifiers; uniquely identify; prevent reuse for FedRAMP-defined period.

Source: FedRAMP High (NIST SP 800-53 Rev 5 baseline), IA-4. 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 FedRAMP High (NIST SP 800-53 Rev 5 baseline) in the compliance library.

A FedRAMP baseline is a subset of NIST SP 800-53 Rev 5, enhancements included.

artefacts

held by a system

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

Identifier issuance records and directory settings preventing reuse of retired usernames · Identity provider / directory
MFA enrolment report for all privileged and remote users · Identity provider / directory
Password policy configuration export from the identity provider · Identity provider / directory
Service account credential vault inventory and rotation logs · Identity provider / directory

periodic reviewEvidence produced at each review

Identity proofing records for high assurance accounts · Identity provider / directory

governing documentDocuments that govern the control

SSP IA-4 statement describing identifier assignment, uniqueness and the period before an identifier may be reused · Policy repository / GRC workspace
Authenticator lifecycle procedure including reset and revocation · 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

Password complexity enforced but reuse not blocked across systems
Federation trust relationships not reviewed when partnerships change
MFA exceptions granted indefinitely without compensating controls
Shared accounts authenticate without traceability to individuals

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-3 Device Identification and Authentication · IA-4(4) Identifier Management | Identify User Status (IA-4(4))