IA-5(13)—Authenticator Management | Expiration of Cached Authenticators
IL4 High
IL5
IL6
>Control Description
Prohibit the use of cached authenticators after ⚙organization-defined time period.
>DoD Impact Level Requirements
Additional Requirements and Guidance
IA-5 (13) Guidance: For components subject to configuration baseline(s) (such as STIG or CIS,) the time period should conform to the baseline standard.
>Discussion
Cached authenticators are used to authenticate to the local machine when the network is not available. If cached authentication information is out of date, the validity of the authentication information may be questionable.
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What formal policies and procedures govern the implementation of IA-5(13) (Expiration Of Cached Authenticators)?
- •Who are the designated roles responsible for implementing, maintaining, and monitoring IA-5(13)?
- •How frequently is the IA-5(13) policy reviewed and updated, and what triggers policy changes?
- •What governance structure ensures IA-5(13) requirements are consistently applied across all systems?
Technical Implementation:
- •Describe the specific technical mechanisms or controls used to enforce IA-5(13) requirements.
- •What automated tools, systems, or technologies are deployed to implement IA-5(13)?
- •How is IA-5(13) integrated into your system architecture and overall security posture?
- •What configuration settings, parameters, or technical specifications enforce IA-5(13) requirements?
Evidence & Documentation:
- •What documentation demonstrates the complete implementation of IA-5(13)?
- •What audit logs, records, reports, or monitoring data validate IA-5(13) compliance?
- •Can you provide evidence of periodic reviews, assessments, or testing of IA-5(13) effectiveness?
- •What artifacts would you present during a FedRAMP assessment to demonstrate IA-5(13) compliance?
Ask AI
Configure your API key to use AI features.