| name | AU-6_audit-record-review-analysis-and-reporting |
| description | Review and analyze system audit records [organization-defined] for indications of [organization-defined] and the potential impact of the inappropri... |
| category | information-gathering |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","au-6","au"] |
| tech_stack | ["aws","azure","gcp","linux","windows"] |
| cwe_ids | ["CWE-778"] |
| chains_with | ["AC-2","AC-3","AC-5","AC-6","AC-7","AC-17","AU-7","AU-16","CA-2","CA-7"] |
| prerequisites | [] |
| severity_boost | {"AC-2":"Chain with AC-2 for comprehensive security coverage","AC-3":"Chain with AC-3 for comprehensive security coverage","AC-5":"Chain with AC-5 for comprehensive security coverage"} |
AU-6 Audit Record Review, Analysis, and Reporting
High-Level Description
Family: Audit and Accountability (AU)
Framework: NIST SP 800-53 Rev 5
Audit record review, analysis, and reporting covers information security- and privacy-related logging performed by organizations, including logging that results from the monitoring of account usage, remote access, wireless connectivity, mobile device connection, configuration settings, system component inventory, use of maintenance tools and non-local maintenance, physical access, temperature and humidity, equipment delivery and removal, communications at system interfaces, and use of mobile code or Voice over Internet Protocol (VoIP). Findings can be reported to organizational entities that include the incident response team, help desk, and security or privacy offices. If organizations are prohibited from reviewing and analyzing audit records or unable to conduct such activities, the review or analysis may be carried out by other organizations granted such authority. The frequency, scope, and/or depth of the audit record review, analysis, and reporting may be adjusted to meet organizational needs based on new information received.
What to Check
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for AU-6 implementation details. Verify the organization has documented how this control is satisfied.
Step 2: Validate Implementation
# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly
# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null
Step 3: Test Operating Effectiveness
Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.
Tools
| Tool | Purpose | Usage |
|---|
| cloud-audit-mcp | Check logging configuration | cloud_audit_logging |
| AWS CLI | Review CloudTrail/CloudWatch |
