NIST SP 800-53 Rev. 5 AU-4 — Audit Log Storage Capacity

What this control requires

llocates audit log storage capacity to meet retention requirements, ensuring sufficient space to prevent loss of audit logging capability. This control supports the Audit Log Storage System capability within the Audit and Accountability family.

In plain English

llocates audit log storage capacity to meet retention requirements, ensuring sufficient space to prevent loss of audit logging capability. 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-4) and look for objective evidence on the latest two assessment cycles.

How to implement

Cloud Posture

CSPM. Run Wiz / Prisma / Defender for Cloud / Security Command Center over every account; auto-ticket findings above your accepted-risk threshold.

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.

Configuration Management

Policy-as-code. Codify the control as Service Control Policies (AWS), Azure Policy initiatives, or Organisation Policy (GCP) so the platform enforces what the document promises.

IaC. Gate Terraform / Pulumi / CloudFormation changes with Checkov / tfsec / OPA so misconfigurations never reach production.

Drift. Run a CSPM (Wiz / Prisma / Defender for Cloud / Security Command Center) over every account and route findings to a single risk register.

Operational checklist

• Audit. Document the trigger, the owner and the cadence.
• Security. Document the trigger, the owner and the cadence.
• Configuration. Document the trigger, the owner and the cadence.
• Data. Document the trigger, the owner and the cadence.
• Network. Document the trigger, the owner and the cadence.
• Scope: management, system, storage capacity, protection, retention, configuration, capability, accountability.

Evidence to collect

• Infra Scan. Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings.

Infrastructure posture tooling (AWS Config, Azure Policy, Nessus) verifies platform hardening. Focus: Audit Log Storage Capacity.

Common pitfalls

• Treating CSPM findings as a backlog instead of a hot queue: findings older than the policy SLA accumulate until the auditor asks why.
• Per-account logging that nobody stitches together at the org level — incidents that cross accounts go undetected for days.
• Manual cloud-console changes that never make it back to Terraform — drift accumulates until the next outage forces a reconciliation.
• Default-allow egress rules; East-West traffic with no segmentation; jump hosts on the public internet with password auth.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• BSI C5:2020 OPS-14 — Logging and Monitoring - Storage of the Logging Data
• NIST SP 800-171 Rev. 3 3.13.8 — Transmission and Storage Confidentiality
• CIS Controls v8 8.3 — Ensure Adequate Audit Log Storage

Related controls in NIST SP 800-53 Rev. 5

• Control AU-11(1) — Long-Term Retrieval Capability
• Control AU-5(1) — Storage Capacity Warning
• Control AU-5(3) — Configurable Traffic Volume Thresholds
• Control AU-9(7) — Store On Component With Different Operating System
• Control AU-4(1) — Transfer To Alternate Storage
• Control CP-9(3) — Separate Storage For Critical Information

References

• NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5
• Catalogue identifier: Control AU-4

Topics: data protectionlogging monitoringcloud postureconfiguration managementnetwork security