NIST SP 800-53 Rev. 5 AU-6(3) — Correlate Audit Record Repositories

What this control requires

Analyzes and correlates audit records across repositories to enhance organization-wide situational awareness across all risk management levels. This control supports the Audit Correlation Tool capability within the Audit and Accountability family.

In plain English

Analyzes and correlates audit records across repositories to enhance organization-wide situational awareness across all risk management levels. In practice, this means you can prove you audit management-level controls on a defined cadence.

Why it matters

SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

What an auditor looks for

A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan.

Within Audit and Accountability, the assessor will trace your implementation back to the catalogue reference (Control AU-6(3)) and look for objective evidence on the latest two assessment cycles.

How to implement

Secure Development

Pipeline. Require code review, SAST (Semgrep / Snyk Code), SCA (Dependabot / Renovate), secret-scanning and IaC scanning in the merge pipeline.

Branch protection. Protected branches enforce reviews, signed commits and passing CI before merge; document the protection rules as the control evidence.

Code Review Testing

Pipeline. Require at least one human reviewer plus passing CI (lint, type, unit, security scan) before merge — protected branches enforce this.

Logging Monitoring

AWS. Org-trail CloudTrail to a central log archive account, GuardDuty in every region, and Security Hub for cross-source correlation.

Azure. Pipe every diagnostic setting into a central Log Analytics workspace; onboard Microsoft Sentinel for SIEM/SOAR.

GCP. Aggregate audit logs in a dedicated logging project with sink to BigQuery; enable Security Command Center Premium and route findings to Chronicle SIEM.

Operational checklist

• Audit. Document the trigger, the owner and the cadence.
• Review. Document the trigger, the owner and the cadence.
• Audit Record. Document the trigger, the owner and the cadence.
• Correlate Audit Record. Document the trigger, the owner and the cadence.
• Correlation. Document the trigger, the owner and the cadence.
• Scope: management, organization, records, audit records, review, capability, correlation, accountability.

Evidence to collect

• Code Repo Scan. Source-control evidence — branch protection, required reviewers, CI status, SCA / SAST reports.

Source control pipelines (GitHub, GitLab) enforce SDLC guardrails. Focus: Correlate Audit Record Repositories.

Common pitfalls

• CI security checks set to warn-only; the merge button is faster than the security feedback.
• Per-account logging that nobody stitches together at the org level — incidents that cross accounts go undetected for days.

Related controls in NIST SP 800-53 Rev. 5

• Control AU-7 — Audit Record Reduction And Report Generation
• Control AU-6 — Audit Record Review, Analysis, And Reporting
• Control AU-9(2) — Store On Separate Physical Systems Or Components
• Control PM-6 — Measures Of Performance
• Control AU-12(1) — System-Wide And Time-Correlated Audit Trail
• Control AU-12(2) — Standardized Formats

References

• NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5
• Catalogue identifier: Control AU-6(3)

Topics: governance riskawareness trainingsecure developmentcode review testingdevsecopslogging monitoring