AU-5(5)—Alternate Audit Logging Capability
>Control Description
Provide an alternate audit logging capability in the event of a failure in primary audit logging capability that implements ⚙organization-defined alternate audit logging functionality.
>Cross-Framework Mappings
>Supplemental Guidance
Since an alternate audit logging capability may be a short-term protection solution employed until the failure in the primary audit logging capability is corrected, organizations may determine that the alternate audit logging capability need only provide a subset of the primary audit logging functionality that is impacted by the failure.
>Related Controls
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What formal policies and procedures govern the implementation of AU-5(5) (Alternate Audit Logging Capability)?
- •Who are the designated roles responsible for implementing, maintaining, and monitoring AU-5(5)?
- •How frequently is the AU-5(5) policy reviewed and updated, and what triggers policy changes?
- •What training or awareness programs ensure personnel understand their responsibilities related to AU-5(5)?
Technical Implementation:
- •Describe the specific technical mechanisms or controls used to enforce AU-5(5) requirements.
- •What automated tools, systems, or technologies are deployed to implement AU-5(5)?
- •How is AU-5(5) integrated into your system architecture and overall security posture?
- •What configuration settings, parameters, or technical specifications enforce AU-5(5) requirements?
Evidence & Documentation:
- •What documentation demonstrates the complete implementation of AU-5(5)?
- •What audit logs, records, reports, or monitoring data validate AU-5(5) compliance?
- •Can you provide evidence of periodic reviews, assessments, or testing of AU-5(5) effectiveness?
- •What artifacts would you present during a FedRAMP assessment to demonstrate AU-5(5) compliance?
Ask AI
Configure your API key to use AI features.