CMMC 2.0
Audit and Accountability

CMMC 2.0 AU.L2-3.3.1: System Auditing

Generate and retain system audit logs in sufficient scope and detail to support monitoring, analysis, investigation and reporting of unlawful or unauthorized system activity.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 78 controls across 25 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 · 13 controls

  • 10.2.1 10.2.1 Audit logging enabled on all system components
  • 10.2.1.1 10.2.1.1 Logs capture individual user access to cardholder data
  • 10.2.1.2 10.2.1.2 Logs capture all administrative actions
  • 10.2.1.4 10.2.1.4 Logs capture invalid logical access attempts
  • 10.2.1.5 10.2.1.5 Logs capture changes to identification and authentication credentials
  • 10.2.1.7 10.2.1.7 Logs capture creation and deletion of system-level objects
  • 10.2.2 10.2.2 Required details recorded for each auditable event
  • 10.3.2 10.3.2 Audit log files protected from modification
  • 10.5.1 10.5.1 Keep logs 12 months, latest three months online
  • 11.5.2 11.5.2 Change detection on critical files
  • 12.4.1 12.4.1 Executive responsibility for a PCI DSS compliance program
  • 5.3.4 5.3.4 Anti-malware audit logs enabled and retained
  • 6.2.1 6.2.1 Secure development of bespoke and custom software

CIS Controls v8 · 7 controls

NIST SP 800-53 Rev 5 · 6 controls

C5 (Germany) · 5 controls

  • C5-DEV-07 Logging of changes
  • C5-OPS-10 Logging and Monitoring - Concept
  • C5-OPS-13 Logging and Monitoring - Identification of Events
  • C5-OPS-14 Logging and Monitoring - Storage of the Logging Data
  • C5-PSS-04 Error handling and Logging Mechanisms

FedRAMP High · 5 controls

  • AU-11 Audit Record Retention
  • AU-12 Audit Record Generation
  • AU-2 Event Logging
  • AU-3 Content of Audit Records
  • AU-3(1) Additional Audit Information

FedRAMP Moderate · 5 controls

  • AU-11 Audit Record Retention
  • AU-12 Audit Record Generation
  • AU-2 Event Logging
  • AU-3 Content of Audit Records
  • AU-3(1) Additional Audit Information

SOC 2 · 5 controls

  • SOC2-CC2.1 CC2.1 Relevant, quality information to support internal control (COSO principle 13)
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • 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
  • ASBv3-GS-7 Define and implement logging, threat detection and incident response strategy
  • ASBv3-IR-4 Detection and analysis - investigate an incident
  • ASBv3-LT-6 Configure log storage retention
  • LT-3 Enable logging for security investigation

NIST SP 800-171 Rev 3 · 3 controls

ACSC Essential Eight · 2 controls

  • E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)
  • E8-UAH-ML3 User Application Hardening - Maturity Level 3
  • SEC04-BP01 Configure service and application logging
  • SEC04-BP02 Capture logs, findings, and metrics in standardized locations

ISO 22301:2019 · 2 controls

  • 9.1 Monitoring, measurement, analysis and evaluation
  • 9.2 Internal audit

ISO 27001:2022 · 2 controls

  • NIST-CSF-DE.CM-01 Networks and network services are monitored to find potentially adverse events
  • NIST-CSF-PR.PS-04 Log records are generated and made available for continuous monitoring

NIST SP 800-161 Rev 1 · 2 controls

  • ANSSI-HYG-36 Enable and Configure Logging on the Most Important Components
  • ASD37-33 Capture network traffic (Limited)
  • AUCDR-IS-1 Limit risk of unauthorised access to the CDR data environment

HIPAA Security Rule · 1 control

ISO 27002:2022 · 1 control

ISO 27701:2019 · 1 control

  • 6.9.4 Logging and monitoring

ISO/IEC 42001:2023 · 1 control

  • A.6.2.8 AI system recording of event logs

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.

Other controls in Audit and Accountability

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

CMMC 2.0 AU.L2-3.3.1 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.

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.

Query this from an agent

The graph holds this control, the 78 it maps to, and the evidence behind each claim, over MCP and REST.