CMMC 2.0
Audit and Accountability

CMMC 2.0 AU.L2-3.3.2: User Accountability

Ensure actions taken on the system can be traced uniquely to the individual user responsible so users can be held accountable.

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

What else in your programme already covers this

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

NIST SP 800-53 Rev 5 · 6 controls

FedRAMP High · 4 controls

  • AU-12 Audit Record Generation
  • AU-3 Content of Audit Records
  • AU-3(1) Additional Audit Information
  • IA-2 Identification and Authentication (Organizational Users)

FedRAMP Moderate · 4 controls

  • AU-12 Audit Record Generation
  • AU-3 Content of Audit Records
  • AU-3(1) Additional Audit Information
  • IA-2 Identification and Authentication (Organizational Users)

PCI DSS 4.0 · 4 controls

  • 10.2.1.1 10.2.1.1 Logs capture individual user access to cardholder data
  • 10.2.1.5 10.2.1.5 Logs capture changes to identification and authentication credentials
  • 10.2.2 10.2.2 Required details recorded for each auditable event
  • 8.2.1 8.2.1 Unique ID assigned to every user

SOC 2 · 3 controls

  • SOC2-CC6.2 CC6.2 Registering and authorising users before issuing credentials
  • 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
  • ANSSI-HYG-08 Identify Each Person by Name and Separate User and Administrator Roles
  • ANSSI-HYG-36 Enable and Configure Logging on the Most Important Components
  • IM-1 Use centralized identity and authentication system
  • LT-3 Enable logging for security investigation

C5 (Germany) · 2 controls

  • C5-OPS-13 Logging and Monitoring - Identification of Events
  • C5-OPS-15 Logging and Monitoring - Accountability

CIS Controls v8 · 2 controls

  • CIS-5.1 Establish and Maintain an Inventory of Accounts
  • CIS-8.5 Collect Detailed Audit Logs

HIPAA Security Rule · 2 controls

ISO 27001:2022 · 2 controls

ISO 27002:2022 · 2 controls

ISO 27701:2019 · 2 controls

  • 6.9.4 Logging and monitoring
  • 7.3.6 Access, correction and/or erasure
  • NIST-CSF-DE.CM-03 Personnel activity and technology usage 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

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

  • E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)
  • AUCDR-IS-1 Limit risk of unauthorised access to the CDR data environment

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