AC-9(1)—Unsuccessful Logons
>Control Description
Notify the user, upon successful logon, of the number of unsuccessful logon attempts since the last successful logon.
>Supplemental Guidance
Information about the number of unsuccessful logon attempts since the last successful logon allows the user to recognize if the number of unsuccessful logon attempts is consistent with the user's actual logon attempts.
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What formal policies and procedures govern the implementation of AC-9(1) (Unsuccessful Logons)?
- •Who are the designated roles responsible for implementing, maintaining, and monitoring AC-9(1)?
- •How frequently is the AC-9(1) policy reviewed and updated, and what triggers policy changes?
- •What training or awareness programs ensure personnel understand their responsibilities related to AC-9(1)?
Technical Implementation:
- •Describe the specific technical mechanisms or controls used to enforce AC-9(1) requirements.
- •What automated tools, systems, or technologies are deployed to implement AC-9(1)?
- •How is AC-9(1) integrated into your system architecture and overall security posture?
- •What configuration settings, parameters, or technical specifications enforce AC-9(1) requirements?
Evidence & Documentation:
- •What documentation demonstrates the complete implementation of AC-9(1)?
- •What audit logs, records, reports, or monitoring data validate AC-9(1) compliance?
- •Can you provide evidence of periodic reviews, assessments, or testing of AC-9(1) effectiveness?
- •What artifacts would you present during a FedRAMP assessment to demonstrate AC-9(1) compliance?
Ask AI
Configure your API key to use AI features.