← AU-9
AU-9(2) AU · Audit and Accountability

Store on Separate Physical Systems or Components

LOW MODERATE ✓ HIGH
1 Overlay 2 Related Controls
Graph
Export ▾

Requirements NIST SOURCE

Store audit records [frequency] in a repository that is part of a physically different system or system component than the system or component being audited.

Discussion (NIST Supplemental Guidance)

Storing audit records in a repository separate from the audited system or system component helps to ensure that a compromise of the system being audited does not also result in a compromise of the audit records. Storing audit records on separate physical systems or components also preserves the confidentiality and integrity of audit records and facilitates the management of audit records as an organization-wide activity. Storing audit records on separate systems or components applies to initial generation as well as backup or long-term storage of audit records.

Implementation Guidance

Engineering Interpretation

Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.

No engineering interpretation has been authored for AU-9(2) yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.

Assessment

NIST SP 800-53A REV 5.2.0

Assessment Objectives

  1. the frequency of storing audit records in a repository is defined;
  2. audit records are stored <AU-09(02)_ODP frequency> in a repository that is part of a physically different system or system component than the system or component being audited.

Examine

[SELECT FROM: Audit and accountability policy; system security plan; privacy plan; procedures addressing protection of audit information; system design documentation; system configuration settings and associated documentation; system or media storing backups of system audit records; system audit records; other relevant documents or records].

Interview

[SELECT FROM: Organizational personnel with audit and accountability responsibilities; organizational personnel with information security and privacy responsibilities; system/network administrators; system developers].

Test

[SELECT FROM: Mechanisms implementing the backing up of audit records].

Overlays

Showing the OT/ICS overlay for the parent control AU-9 — see the AU-9(2) entries within each baseline below.

OT/ICS Overlay SP 800-82r3

NIST SP 800-82r3 Appendix F, Table 22. Blank baseline means the control/control enhancement is not selected in that initial OT baseline.

LOW

  • Base control: Included (matches standard baseline)

MODERATE

  • Base control: Included (matches standard baseline)
  • Included: (4)

HIGH

  • Base control: Included (matches standard baseline)
  • Included: (2) (3) (4)

STIGs & CCIs

No STIG checks or CCI mappings are currently loaded for AU-9(2). This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.

Learn more about STIG/CCI integration →

Evidence

Potential Evidence — Derived

Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.

Policy

  • Audit and accountability policy
  • system security plan
  • privacy plan

Configuration

  • system design documentation
  • system configuration settings and associated documentation

Testing

  • Mechanisms implementing the backing up of audit records

Other Records

  • procedures addressing protection of audit information
  • system or media storing backups of system audit records
  • system audit records
  • other relevant documents or records