AU-9(6)—Protection of Audit Information | Read-only Access
IL5
IL6
>Control Description
Authorize read-only access to audit information to ⚙organization-defined subset of privileged users or roles.
>DoD Impact Level Requirements
No specific parameter values or requirements for this impact level.
>Discussion
Restricting privileged user or role authorizations to read-only helps to limit the potential damage to organizations that could be initiated by such users or roles, such as deleting audit records to cover up malicious activity.
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What formal policies and procedures govern the implementation of AU-9(6) (Read-Only Access)?
- •Who are the designated roles responsible for implementing, maintaining, and monitoring AU-9(6)?
- •How frequently is the AU-9(6) policy reviewed and updated, and what triggers policy changes?
- •What training or awareness programs ensure personnel understand their responsibilities related to AU-9(6)?
Technical Implementation:
- •Describe the specific technical mechanisms or controls used to enforce AU-9(6) requirements.
- •What automated tools, systems, or technologies are deployed to implement AU-9(6)?
- •How is AU-9(6) integrated into your system architecture and overall security posture?
- •What configuration settings, parameters, or technical specifications enforce AU-9(6) requirements?
Evidence & Documentation:
- •What documentation demonstrates the complete implementation of AU-9(6)?
- •What audit logs, records, reports, or monitoring data validate AU-9(6) compliance?
- •Can you provide evidence of periodic reviews, assessments, or testing of AU-9(6) effectiveness?
- •What artifacts would you present during a FedRAMP assessment to demonstrate AU-9(6) compliance?
Ask AI
Configure your API key to use AI features.