AC-2 (05)—Account Management | Inactivity Logout
Moderate
High
>Control Description
Require that users log out when ⚙organization-defined time period of expected inactivity or description of when to log out.
>FedRAMP Baseline Requirements
Parameter Values
Additional Requirements and Guidance
AC-2 (5) Guidance: Should use a shorter timeframe than AC-12.
>Discussion
Inactivity logout is behavior- or policy-based and requires users to take physical action to log out when they are expecting inactivity longer than the defined period. Automatic enforcement of inactivity logout is addressed by AC-11.
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What formal policies and procedures govern the implementation of AC-2(5) (Inactivity Logout)?
- •Who are the designated roles responsible for implementing, maintaining, and monitoring AC-2(5)?
- •How frequently is the AC-2(5) policy reviewed and updated, and what triggers policy changes?
- •What training or awareness programs ensure personnel understand their responsibilities related to AC-2(5)?
Technical Implementation:
- •Describe the specific technical mechanisms or controls used to enforce AC-2(5) requirements.
- •What automated tools, systems, or technologies are deployed to implement AC-2(5)?
- •How is AC-2(5) integrated into your system architecture and overall security posture?
- •What configuration settings, parameters, or technical specifications enforce AC-2(5) requirements?
Evidence & Documentation:
- •What documentation demonstrates the complete implementation of AC-2(5)?
- •What audit logs, records, reports, or monitoring data validate AC-2(5) compliance?
- •Can you provide evidence of periodic reviews, assessments, or testing of AC-2(5) effectiveness?
- •What artifacts would you present during a FedRAMP assessment to demonstrate AC-2(5) compliance?
Ask AI
Configure your API key to use AI features.