au-4-1-transfer-to-alternate-storage

name	AU-4(1)_transfer-to-alternate-storage
description	Transfer audit logs [organization-defined] to a different system, system component, or media other than the system or system component conducting the
category	information-gathering
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","au-4-1","au","enhancement"]
tech_stack	["aws","azure","gcp","linux","windows"]
cwe_ids	["CWE-778"]
chains_with	[]
prerequisites	["AU-4"]
severity_boost	{}

AU-4(1) Transfer to Alternate Storage

Enhancement of: AU-4

High-Level Description

Family: Audit and Accountability (AU) Framework: NIST SP 800-53 Rev 5

Audit log transfer, also known as off-loading, is a common process in systems with limited audit log storage capacity and thus supports availability of the audit logs. The initial audit log storage is only used in a transitory fashion until the system can communicate with the secondary or alternate system allocated to audit log storage, at which point the audit logs are transferred. Transferring audit logs to alternate storage is similar to AU-9(2) in that audit logs are transferred to a different entity. However, the purpose of selecting AU-9(2) is to protect the confidentiality and integrity of audit records. Organizations can select either control enhancement to obtain the benefit of increased audit log storage capacity and preserving the confidentiality, integrity, and availability of audit records and logs.

What to Check

• Verify AU-4(1) Transfer to Alternate Storage is documented in SSP
• Confirm control is operating effectively
• Review evidence of continuous monitoring for AU-4(1)
• Verify enhancement builds upon base control AU-4

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for AU-4(1) 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	aws cloudtrail describe-trails