AU-9(7)—Store On Component With Different Operating System
>Control Description
Store audit information on a component running a different operating system than the system or component being audited.
>Supplemental Guidance
Storing auditing information on a system component running a different operating system reduces the risk of a vulnerability specific to the system, resulting in a compromise of the audit records.
>Related Controls
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What formal policies and procedures govern the implementation of AU-9(7) (Store On Component With Different Operating System)?
- •Who are the designated roles responsible for implementing, maintaining, and monitoring AU-9(7)?
- •How frequently is the AU-9(7) policy reviewed and updated, and what triggers policy changes?
- •What training or awareness programs ensure personnel understand their responsibilities related to AU-9(7)?
Technical Implementation:
- •Describe the specific technical mechanisms or controls used to enforce AU-9(7) requirements.
- •What automated tools, systems, or technologies are deployed to implement AU-9(7)?
- •How is AU-9(7) integrated into your system architecture and overall security posture?
- •What configuration settings, parameters, or technical specifications enforce AU-9(7) requirements?
Evidence & Documentation:
- •What documentation demonstrates the complete implementation of AU-9(7)?
- •What audit logs, records, reports, or monitoring data validate AU-9(7) compliance?
- •Can you provide evidence of periodic reviews, assessments, or testing of AU-9(7) effectiveness?
- •What artifacts would you present during a FedRAMP assessment to demonstrate AU-9(7) compliance?
Ask AI
Configure your API key to use AI features.