IA-5(13) Authenticator Management | Expiration of Cached Authenticators
Prohibit the use of cached authenticators after a FedRAMP-defined time period.
Source: FedRAMP High (NIST SP 800-53 Rev 5 baseline), IA-5(13). 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.
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
- Configuration setting the cached credential lifetime · Identity provider / directory
periodic reviewEvidence produced at each review
- Test evidence that a cached authenticator is refused after the period · Identity provider / directory
governing documentDocuments that govern the control
- Exported policy or screenshots showing the enforced expiry · Policy repository / GRC workspace
First move
Common gaps auditors find
- Cached credential expiry left at the operating system default
- Mobile and offline endpoints excluded from the setting
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-5(8) Multiple System Accounts · IA-6 Authentication Feedback