What 3.3.4 means in practice

If logging stops, someone must find out. Define which failures matter (an agent stops sending, storage fills up, a log source goes quiet) and who is alerted, then configure alerts that actually reach those people.

SPRS points and the CMMC POA&M

CMMC Level 2 practice
AU.L2-3.3.4
SPRS points
1 point. When it is not met, the DoD Assessment Methodology subtracts 1 from the score of 110.
CMMC POA&M
Allowed. It is worth 1 point, and 32 CFR 170.21(a)(2)(ii) admits requirements worth 1 point. Conditional status also needs a score of at least 88, and the item must be closed within 180 days.

Sources: NIST SP 800-171 DoD Assessment Methodology, version 1.2.1 (June 24, 2020), Annex A; 32 CFR 170.21, Plan of Action and Milestones requirements.

What an assessor checks for 3.3.4

NIST SP 800-171A gives 3 determination statements for 3.3.4, each found satisfied or other than satisfied. Determine if:

  1. 3.3.4[a] personnel or roles to be alerted in the event of an audit logging process failure are identified.
  2. 3.3.4[b] types of audit logging process failures for which alert will be generated are defined.
  3. 3.3.4[c] identified personnel or roles are alerted in the event of an audit logging process failure.

NIST SP 800-171A (June 2018), assessment objectives for 3.3.4

Evidence that shows 3.3.4 is met

  • The list of audit logging failures that raise an alert, and the roles alerted.
  • Alert rule configuration in the logging or monitoring platform.
  • A record of a test or real alert reaching the named people.

How PolicyCortex gathers the evidence

PolicyCortex reads this evidence with the collectors below, read only, and grades 3.3.4 from it. Each line says what the product checks.

  • Azure Monitor: Alert rules. Reads Azure Monitor alert rules and checks that alerts are set for audit logging process failures.

Meet the requirement once. Keep the evidence current.

Published
Last updated
Unchanged since publication