# NIST SP 800-53 Rev. 5 IA-5(13) — Expiration Of Cached Authenticators - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ia-5-13-expiration-of-cached-authenticators - Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-53 Rev. 5 Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5) › IA — Identification and Authentication - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `IA-5(13)`·medium·Component: **Identification and Authentication** ## What this control requires > Prohibiting the use of cached authenticators after an organization-defined time period to ensure the validity of authentication information when network access is unavailable. This control supports the Authentication Cache Management System capability within the Identification and Authentication family. > > — NIST SP 800-53 Rev. 5, Control IA-5(13) ### In plain English Prohibiting the use of cached authenticators after an organization-defined time period to ensure the validity of authentication information when network access is unavailable. In practice, this means you can prove you access management-level controls on a defined cadence. ## Why it matters SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed. ## What an auditor looks for A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan. Within **Identification and Authentication**, the assessor will trace your implementation back to the catalogue reference (Control IA-5(13)) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Network Security **AWS.** VPC Flow Logs to S3, default-deny security groups, AWS Network Firewall for north-south, and Transit Gateway for hub-and-spoke segmentation. **Azure.** NSGs with deny-by-default, Azure Firewall Premium with TLS inspection, Private Endpoints for PaaS, and Microsoft Defender for Cloud's secure score for drift. **GCP.** VPC Service Controls perimeters around sensitive APIs, Cloud NGFW Enterprise for L7 inspection, Private Service Connect for managed services. ### Operational checklist - **Access.** Document the trigger, the owner and the cadence. - **Information.** Document the trigger, the owner and the cadence. - **Security.** Document the trigger, the owner and the cadence. - **Network.** Document the trigger, the owner and the cadence. - **Review.** Document the trigger, the owner and the cadence. - **Scope:** management, information, authentication information, organization, system, time, identity, review. ## Evidence to collect - **Identity Scan.** IAM / IdP exports — Entra ID, Okta, IAM Identity Center, Workspace directory — showing accounts, roles, MFA state and last sign-in. Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Expiration Of Cached Authenticators. ## Common pitfalls - Default-allow egress rules; East-West traffic with no segmentation; jump hosts on the public internet with password auth. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**NIST SP 800-171 Rev. 3 3.5.4** — Replay-Resistant Authentication](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-5-4-replay-resistant-authentication) - [**ISO/IEC 27001:2022 A.5.2** — Information security roles and responsibilities](https://support.icompaas.com/compliance/iso-27001-2022/a-5-2-information-security-roles-and-responsibilities) - [**CIS Controls v8 9.2** — Use DNS Filtering Services](https://support.icompaas.com/compliance/cis-controls-v8/9-2-use-dns-filtering-services) - [**BSI C5:2020 IDM-08** — Confidentiality of authentication information](https://support.icompaas.com/compliance/bsi-c5-2020/idm-08-confidentiality-of-authentication-information) - [**ISO/IEC 27701:2025 A.3.8** — Identity management](https://support.icompaas.com/compliance/iso-27701-2025/a-3-8-identity-management) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control IA-5(6)** — Protection Of Authenticators](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ia-5-6-protection-of-authenticators) - [**Control IA-2(10)** — Single Sign-On](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ia-2-10-single-sign-on) - [**Control IA-4(1)** — Prohibit Account Identifiers As Public Identifiers](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ia-4-1-prohibit-account-identifiers-as-public-identifiers) - [**Control IA-5(5)** — Change Authenticators Prior To Delivery](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ia-5-5-change-authenticators-prior-to-delivery) - [**Control IA-5(12)** — Biometric Authentication Performance](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ia-5-12-biometric-authentication-performance) - [**Control IA-2** — Identification And Authentication (Organizational Users)](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ia-2-identification-and-authentication-organizational-users) ## References - [NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls) - Catalogue identifier: `Control IA-5(13)` Topics: identity accessidentity managementaccess reviewprivileged accessnetwork security ## Related compliance guidance - [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): Start with the full NIST SP 800-53 implementation guide — scope, roadmap, evidence and how the assessment runs. - [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): If your obligation is protecting CUI in your own systems for a federal or defence contract, this derived subset — not the full catalogue — is the requirement. - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most commercial SaaS already hold a SOC 2 Type 2, and FedRAMP 20x Class A is designed for providers that have one.