NIST 800-53 REV 5 • AUDIT AND ACCOUNTABILITY
AU-6(5) — Integrated Analysis of Audit Records
Integrate analysis of audit records with analysis of {{ insert: param, au-06.05_odp.01 }} to further enhance the ability to identify inappropriate or unusual activity.
Supplemental Guidance
Integrated analysis of audit records does not require vulnerability scanning, the generation of performance data, or system monitoring. Rather, integrated analysis requires that the analysis of information generated by scanning, monitoring, or other data collection activities is integrated with the analysis of audit record information. Security Information and Event Management tools can facilitate audit record aggregation or consolidation from multiple system components as well as audit record correlation and analysis. The use of standardized audit record analysis scripts developed by organizations (with localized script adjustments, as necessary) provides more cost-effective approaches for analyzing audit record information collected. The correlation of audit record information with vulnerability scanning information is important in determining the veracity of vulnerability scans of the system and in correlating attack detection events with scanning results. Correlation with performance data can uncover denial-of-service attacks or other types of attacks that result in the unauthorized use of resources. Correlation with system monitoring information can assist in uncovering attacks and in better relating audit information to operational situations.
Practitioner Notes
Integrate analysis of audit records with other types of monitoring data — vulnerability scans, asset inventories, threat intelligence — for a comprehensive security picture.
Example 1: Import your Nessus or Qualys vulnerability scan data into Splunk using the technology add-on. Correlate vulnerability data with IDS alerts — if an IDS fires on a system with a known critical vulnerability, that alert gets elevated to critical severity automatically.
Example 2: Feed threat intelligence (STIX/TAXII feeds from CISA, FS-ISAC, or commercial sources) into your SIEM. Configure automated matching of IOCs (IP addresses, domains, file hashes) against your network logs. In Sentinel, use the Threat Intelligence data connector and create analytics rules that fire when a known-bad indicator appears in your logs.