AU-5 (01)—Response to Audit Logging Process Failures | Storage Capacity Warning
High
>Control Description
Provide a warning to ⚙organization-defined personnel, roles, and/or locations within ⚙organization-defined time period when allocated audit log storage volume reaches ⚙organization-defined percentage of repository maximum audit log storage capacity.
>FedRAMP Baseline Requirements
No FedRAMP-specific parameter values or requirements for this baseline.
>Discussion
Organizations may have multiple audit log storage repositories distributed across multiple system components with each repository having different storage volume capacities.
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What formal policies and procedures govern the implementation of AU-5(1) (Storage Capacity Warning)?
- •Who are the designated roles responsible for implementing, maintaining, and monitoring AU-5(1)?
- •How frequently is the AU-5(1) policy reviewed and updated, and what triggers policy changes?
- •What training or awareness programs ensure personnel understand their responsibilities related to AU-5(1)?
Technical Implementation:
- •Describe the specific technical mechanisms or controls used to enforce AU-5(1) requirements.
- •What automated tools, systems, or technologies are deployed to implement AU-5(1)?
- •How is AU-5(1) integrated into your system architecture and overall security posture?
- •What configuration settings, parameters, or technical specifications enforce AU-5(1) requirements?
Evidence & Documentation:
- •What documentation demonstrates the complete implementation of AU-5(1)?
- •What audit logs, records, reports, or monitoring data validate AU-5(1) compliance?
- •Can you provide evidence of periodic reviews, assessments, or testing of AU-5(1) effectiveness?
- •What artifacts would you present during a FedRAMP assessment to demonstrate AU-5(1) compliance?
Ask AI
Configure your API key to use AI features.