Response to Audit Logging Process Failures is the requirement that decides what happens when logging itself breaks. Event Logging (03.03.01), Audit Record Content (03.03.02), and Audit Record Generation (03.03.03) build the logging capability, but Response to Audit Logging Process Failures (03.03.04) plans for the moment that capability fails. It has two (2) parts: alert designated personnel or roles within a defined time period when an audit logging process failure occurs, and take defined additional actions. Per the NIST discussion, logging failures include software and hardware errors, failures in the log capture mechanism, and reaching or exceeding audit log storage capacity, and response actions can include overwriting the oldest records, shutting down the system, or stopping audit record generation.
A common difficulty with this requirement is building a logging pipeline and never planning for its failure. Silent logging gaps are exactly what an attacker wants, and an assessor will ask how you are alerted and what you do when logging stops. Both the alert timing and the additional actions are Organization-Defined Parameters (ODPs), and for Department of Defense (DoD) contractors they are specified.
Where things stand for companies facing the transition from NIST 800-171 R2 to R3:
The following is reproduced verbatim from NIST 800-171 R3, requirement 03.03.04 Response to Audit Logging Process Failures. Only the formatting has been adjusted for readability. This requirement has two (2) lettered parts:
The source control is AU-05 from NIST 800-53. The two bracketed assignments are the ODPs: the alert time period and the additional actions. Per the NIST discussion, when the failure is related to storage, the response is carried out for the audit log storage repository, the system on which the logs reside, the total organizational audit log storage capacity, or all three, and organizations may decide to take no additional actions after alerting. You can read the requirement directly at NIST 800-171 R3, 03.03.04 (p. 23).
Two (2) values sit inside this requirement. Depending on your contract, your organization may be permitted to define them. Organizations in the DIB subject to CMMC are not, because the DoD has defined them as policy.
The values below come from Attachment A of the DoD Chief Information Officer (CIO) memorandum dated 10 April 2025 (signed David W. McKeown). The memo identifies each parameter by requirement sub-part, while NIST 800-171A R3 identifies the same parameter by ODP number. Both identifiers appear below so you can match your System Security Plan (SSP) language to either document.
The memo states that its values "will be updated as necessary," so confirm against the current version before writing them into policy.
NIST 800-171A R3 breaks 03.03.04 into four (4) assessment objectives: two (2) Organization-Defined Parameters (ODPs) and two (2) determination statements. These AOs are:
The alert (A.03.03.04.a) and the additional actions (A.03.03.04.b) are separate objectives, each tied to an ODP. If you are a DoD contractor, the ODPs are specified. Per the DoD-specified ODP values in ComplianceForge's NIST 800-171 R3 Transition Guide, the alert time period (ODP[01]) is near real time or as soon as practicable upon discovery, and the additional actions (ODP[02]) are to document the failure and resolution, troubleshoot, repair or restart the audit logging process, and report as an incident if applicable. The full guidance on assessment methods and objects, is in NIST 800-171A R3, 03.03.04 (p. 27).
Examine: audit and accountability policy and procedures; procedures for responding to audit processing failures; system design documentation; system configuration settings; list of personnel to be notified in case of an audit processing failure; system audit records; system security plan.
Interview: personnel with audit and accountability responsibilities; personnel with information security responsibilities; system developers; system administrators.
Test: mechanisms for implementing system response to audit processing failures.
03.03.04 maps from NIST 800-171 R2 requirement 3.3.4 (alert in the event of an audit logging process failure):
Mapped against the four (4) AOs, one (1) is direct (minimal effort), one (1) is net new, and two (2) have no clear mapping, with the last two (2) categories both counting as significant effort. The alert itself carries forward, but the additional-actions objective is new and the two parameters have no R2 predecessor, so three of the four (4) objectives are significant effort even though this looks like a small control.
Source Control in NIST 800-53 R5:
Secure Controls Framework (SCF) Crosswalk
Organizations running a single control set across multiple frameworks can satisfy 03.03.04 through the following SCF controls:
The crosswalks from NIST 800-171 R3 and NIST 800-171A R3 to the SCF are available at no cost through the SCF Set Theory Relationship Mapping (STRM): https://securecontrolsframework.com/start-here/set-theory-relationship-mapping-strm. The STRM also carries the relationship type for each mapping (Equal, Subset Of, Intersects With), which tells you whether an SCF control fully satisfies the requirement or only part of it. Mapping above taken from SCF 2026.3.
The following are issues teams may encounter rather than certainties. They are about the additional actions and the parameters, each of which needs documented evidence of due diligence and due care such as policies, standards, procedures, and configuration screenshots:
Reasonable objective evidence for an assessment is often subjective. The following examples of evidence to address NIST 800-171 R3 03.03.04 are sourced from the SCF Evidence Request List (ERL), available at https://securecontrolsframework.com/free-content/scf-download. These ERL artifacts are mapped to NIST 800-171 R3 03.03.04 through SCF controls. They establish a starting point for discussions on what an organization needs to have for evidence of due diligence and due care to withstand external scrutiny by an assessor or regulator.
Alongside these, keep the System Security Plan (SSP) narrative for 03.03.04 recording the ODP values you adopted.
With three (3) of the four (4) AOs at significant effort, 03.03.04 needs more attention than its size suggests. A realistic sequence:
What value does the DoD require for the first parameter in NIST 800-171 R3 03.03.04? R3 leaves the value to the organization. For the DIB, the DoD set it in the 10 April 2025 memorandum under ODP identifier 03.03.04.a: near real time or as soon as practicable upon discovery.
How many assessment objectives does NIST 800-171 R3 03.03.04 have? NIST 800-171A R3 breaks 03.03.04 into four (4) assessment objectives: two (2) Organization-Defined Parameters (ODPs) and two (2) determination statements. An assessor works through each one separately, so each needs its own evidence.
Which NIST 800-53 R5 control does NIST 800-171 R3 03.03.04 come from? AU-05.
Where does NIST 800-171 R3 03.03.04 sit in the NIST 800-171 R3 Kill Chain? Phase 11, Situational Awareness (SA). The Kill Chain is a phased model for sequencing R3 implementation, and it assigns this requirement to that phase.
03.03.04 Response to Audit Logging Process Failures alerts designated personnel within a defined time period when logging fails and takes defined additional actions. It maps from R2 3.3.4 with the alert transitioning directly, while the additional-actions objective is net new and the two parameters have no R2 predecessor, making three of four (4) objectives significant effort. The recurring problem is planning for logging but not for logging failure. Define the alert time period and the additional actions (for DoD, near real time and the document, repair, and report actions), configure alerting, and prove the actions happen.
Authoritative sources:
Authoritative sources:
This guide reproduces U.S. Government text from NIST 800-171 R3 and NIST 800-171A R3 and references the DoD ODP memorandum of 10 April 2025. It is educational, not legal or assessment advice. Last reviewed: 2026-09-22.
