CMMC 2.0 AU.L2-3.3.4: Audit Failure Alerting

What else in your programme already covers this

This control maps to 29 controls across 14 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

PCI DSS 4.0 · 5 controls

10.4.1.1 10.4.1.1 Automated mechanisms used for audit log review
10.7.1 10.7.1 Service providers detect critical control failures (superseded)
10.7.2 10.7.2 Detect and alert on critical security control failures
11.6.1 11.6.1 Payment page tamper detection
12.10.5 12.10.5 Plan covers alerts from security monitoring systems

NIST Cybersecurity Framework 2.0 · 4 controls

NIST-CSF-DE.AE-06 Information on adverse events is provided to authorized staff and tools
NIST-CSF-DE.CM-01 Networks and network services are monitored to find potentially adverse events
NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
NIST-CSF-RS.CO-02 Internal and external stakeholders are notified of incidents

ISO 27001:2022 · 3 controls

5.24 Information security incident management planning and preparation
8.15 Logging
8.16 Monitoring activities

NIST SP 800-53 Rev 5 · 3 controls

NIST800-AU-4 AU-4 Audit Log Storage Capacity
NIST800-AU-5 AU-5 Response to Audit Logging Process Failures
NIST800-SI-17 SI-17 Fail-safe Procedures

SOC 2 · 3 controls

SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
SOC2-CC7.2 CC7.2 Monitoring system components for anomalies
SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents

C5 (Germany) · 2 controls

C5-OPS-17 Logging and Monitoring - Availability of the Monitoring Software
C5-PSS-04 Error handling and Logging Mechanisms

CIS Controls v8 · 2 controls

CIS-13.1 Centralize Security Event Alerting
CIS-8.3 Ensure Adequate Audit Log Storage

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

CCM-LOG-13 Failures and Anomalies Reporting

FedRAMP High · 1 control

AU-5 Response to Audit Logging Process Failures

FedRAMP Moderate · 1 control

AU-5 Response to Audit Logging Process Failures

NIST SP 800-171 Rev 3 · 1 control

03.03.04 Response to Audit Logging Process Failures

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

You are reading one control. How much of CMMC 2.0 have you already done?

CMMC 2.0 AU.L2-3.3.4 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CMMC 2.0 your existing evidence covers. Hold FedRAMP Moderate and 108 of 110 CMMC 2.0 controls already carry evidence.

If you hold FedRAMP Moderate98.2% covered · 2 gaps If you hold NIST SP 800-171 Rev 394.5% covered · 6 gaps If you hold NIST SP 800-53 Rev 585.5% covered · 16 gaps If you hold ISO 27001:202279.1% covered · 23 gaps If you hold ISO 27002:202267.3% covered · 36 gaps If you hold CIS Controls v864.5% covered · 39 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 1 were rejected on the FedRAMP Moderate pair alone.

See the released pairs, $299 each Browse the graph free