PCI DSS 4.0
Req 10: Logging and Monitoring

PCI DSS 4.0 10.2.1.2: 10.2.1.2 Logs capture all administrative actions

Audit logs must record every action carried out by anyone who holds administrative access, and this includes any interactive session run under an application account or a system account. Applies to all entities. The guidance explains that without such records mistakes or misuse of privilege cannot be traced to the specific action and account, and it defines administrative functions as those going beyond what ordinary users do in routine business work (see Appendix G). Customized approach objective: every action by individuals holding elevated privileges leaves a record.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 38 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.

FedRAMP High · 5 controls

  • AC-6(9) Log Use of Privileged Functions
  • AU-12 Audit Record Generation
  • AU-3(1) Additional Audit Information
  • CM-5(1) Access Restrictions for Change | Automated Access Enforcement and Audit Records (CM-5(1))
  • SI-4 System Monitoring

FedRAMP Moderate · 5 controls

  • AC-6(9) Log Use of Privileged Functions
  • AU-12 Audit Record Generation
  • AU-3(1) Additional Audit Information
  • CM-5(1) Access Restrictions for Change | Automated Access Enforcement and Audit Records (CM-5(1))
  • SI-4 System Monitoring

CIS Controls v8 · 4 controls

NIST SP 800-53 Rev 5 · 4 controls

SOC 2 · 4 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

C5 (Germany) · 2 controls

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

CMMC 2.0 · 2 controls

  • 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
  • E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)
  • ANSSI-HYG-36 Enable and Configure Logging on the Most Important Components
  • SEC04-BP01 Configure service and application logging
  • LT-3 Enable logging for security investigation

ISO 27001:2022 · 1 control

ISO 27002:2022 · 1 control

ISO 27701:2019 · 1 control

  • 6.9.4 Logging and monitoring
  • 03.01.07 Least Privilege - Privileged Functions

NIST SP 800-172 · 1 control

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 Req 10: Logging and Monitoring

You are reading one control. How much of PCI DSS 4.0 have you already done?

PCI DSS 4.0 10.2.1.2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.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. 415 were rejected on the ISO 27001:2022 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.