AU.L2-3.3.8[a]: Define Who Gets Notified When Logging Breaks

Mapped to NIST 800-171 Requirement: 3.3.8
CMMC Assessment Objective: AU.L2-3.3.8[a]

What This Objective Means
This objective ensures that logging disruptions—such as full disks, failed log forwarding, or stopped logging services—are not ignored. Your systems and processes must:
• Detect when audit logging fails
• Notify specific, designated personnel or roles
• Document who receives those alerts and how quickly
The goal is to react quickly to avoid data loss or missed audit coverage.

Why It Matters
If audit logs aren’t being generated or retained:
• You lose your ability to detect and investigate incidents
• CUI-related activity may go untracked
• You may fail compliance assessments without knowing it
Having designated personnel ensures that logging failures are detected, escalated, and resolved promptly.

How to Implement It
• Assign responsibility to roles such as:
◦ System administrators
◦ Security analysts or monitoring teams
◦ MSPs or MSSPs, if applicable
• Configure alerting in your SIEM or logging tools to:
◦ Monitor log volume, errors, and disk usage
◦ Send automated alerts via email, SMS, or ticketing systems
• Document responsible roles and escalation paths in your:
◦ System Security Plan (SSP)
◦ Audit and Accountability Policy
◦ Incident Response Plan

Evidence the Assessor Will Look For
• A list of personnel or roles designated to respond to logging failures
• Documentation showing how they are notified (e.g., alerting tools or ticketing system)
• Policy or procedure language specifying responsibilities and escalation steps
• Screenshots or logs showing past alerts sent to those roles

Common Gaps
• No one is specifically assigned to monitor log integrity or failures
• Logging tools generate alerts, but no one is reviewing them
• Failure notifications are not configured or go to unmonitored inboxes

How Cuick Trac Helps
Cuick Trac supports this control by:
• Monitoring logging health and generating alerts for logging failures
• Assigning log monitoring to specific roles within the secure enclave
• Helping organizations define escalation procedures and assign responsibilities
• Providing documentation templates that map personnel to incident response actions
With Cuick Trac, log failures don’t go unnoticed—they go directly to the right people.

Final CTA
If no one knows the logging system failed, it’s already too late.
Schedule a Cuick Trac demo and make sure someone’s always watching the watchers.

🍪 We Use Cookies

To enhance your experience and analyze site usage, we use cookies. By continuing to use our site, you agree to our use of cookies in accordance with our Privacy Policy.