CMMC 2.0
Audit and Accountability

CMMC 2.0 AU.L2-3.3.9: Audit Management

Restrict the ability to manage audit logging functionality to a limited subset of privileged users, separate from general administrators.

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

What else in your programme already covers this

This control maps to 38 controls across 19 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 · 6 controls

  • 10.2.1.3 10.2.1.3 Access to the audit logs is itself logged
  • 10.3.1 10.3.1 Audit log read access limited to job need
  • 10.3.3 10.3.3 Audit logs promptly backed up to central secure storage
  • 10.5.1 10.5.1 Keep logs 12 months, latest three months online
  • 4.1.1 4.1.1 Requirement 4 policies and procedures maintained and communicated
  • 3.1.1 3.1.1 Requirement 3 policies and procedures maintained and in use

CIS Controls v8 · 5 controls

  • CIS-8.1 Establish and Maintain an Audit Log Management Process
  • CIS-8.11 Conduct Audit Log Reviews
  • CIS-8.2 Collect Audit Logs
  • CIS-8.3 Ensure Adequate Audit Log Storage
  • CIS-8.9 Centralize Audit Logs

SOC 2 · 5 controls

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC7.2 CC7.2 Monitoring system components for anomalies
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

NIST SP 800-53 Rev 5 · 4 controls

  • SEC01-BP01 Separate workloads using accounts
  • SEC03-BP05 Define permission guardrails for your organization

C5 (Germany) · 2 controls

  • C5-OPS-12 Logging and Monitoring - Access, Storage and Deletion
  • C5-OPS-16 Logging and Monitoring - Configuration
  • 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
  • ANSSI-HYG-29 Limit Administration Rights on Workstations to Operational Need

FedRAMP High · 1 control

  • AU-9(4) Access by Subset of Privileged Users

FedRAMP Moderate · 1 control

  • AU-9(4) Access by Subset of Privileged Users

HIPAA Security Rule · 1 control

ISO 22301:2019 · 1 control

ISO 27001:2022 · 1 control

  • 8.18 Use of privileged utility programs

ISO 27002:2022 · 1 control

  • 8.2 Privileged access rights

ISO 27701:2019 · 1 control

  • 6.9.4 Logging and monitoring
  • 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.9 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 38 it maps to, and the evidence behind each claim, over MCP and REST.