CMMC 2.0
Audit and Accountability

CMMC 2.0 AU.L2-3.3.8: Audit Protection

Prevent unauthorized access to, modification of, and deletion of both audit records and the tools that produce them.

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

What else in your programme already covers this

This control maps to 48 controls across 18 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 · 7 controls

  • 10.2.1.3 10.2.1.3 Access to the audit logs is itself logged
  • 10.2.1.6 10.2.1.6 Logs capture initialization and stopping of audit logs
  • 10.3.1 10.3.1 Audit log read access limited to job need
  • 10.3.2 10.3.2 Audit log files protected from modification
  • 10.3.3 10.3.3 Audit logs promptly backed up to central secure storage
  • 10.3.4 10.3.4 File integrity monitoring on audit logs
  • 11.5.2 11.5.2 Change detection on critical files

ISO 27001:2022 · 5 controls

  • 5.28 Collection of evidence
  • 5.33 Protection of records
  • 8.15 Logging
  • 8.16 Monitoring activities
  • 8.34 Protection of information systems during audit testing 

SOC 2 · 5 controls

  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • 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.4 CC7.4 Responding to security incidents

CIS Controls v8 · 4 controls

ISO 27002:2022 · 3 controls

  • 5.28 Collection of evidence
  • 5.33 Protection of records
  • 8.15 Logging
  • NIST-CSF-PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties
  • NIST-CSF-PR.PS-04 Log records are generated and made available for continuous monitoring
  • NIST-CSF-RS.AN-07 Incident data and metadata are collected, and their integrity and provenance are preserved

NIST SP 800-53 Rev 5 · 3 controls

  • ASBv3-LT-6 Configure log storage retention
  • ASBv3-PA-7 Follow just enough administration (least privilege) principle

C5 (Germany) · 2 controls

  • C5-OPS-12 Logging and Monitoring - Access, Storage and Deletion
  • C5-OPS-14 Logging and Monitoring - Storage of the Logging Data

ISO 27701:2019 · 2 controls

  • 6.9.4 Logging and monitoring
  • 6.9.7 Information systems audit considerations
  • E8-APP-ML2 Application Control (ML2)

FedRAMP High · 1 control

  • AU-9 Protection of Audit Information

FedRAMP Moderate · 1 control

  • AU-9 Protection of Audit Information

HIPAA Security Rule · 1 control

  • 03.03.08 Protection of Audit Information

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.8 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 48 it maps to, and the evidence behind each claim, over MCP and REST.