PCI DSS 4.0
Req 10: Logging and Monitoring

PCI DSS 4.0 10.2.1.5: 10.2.1.5 Logs capture changes to identification and authentication credentials

Audit logs must record every change to identification and authentication credentials, including at minimum: the creation of new accounts; any elevation of privileges; and every change, addition or deletion affecting accounts that hold administrative access. Applies to all entities. The guidance notes these records leave residual evidence if someone tries to misuse credentials to get around them or to impersonate a legitimate account. Customized approach objective: every change to identification and authentication credentials leaves a record.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

CMMC 2.0 · 4 controls

ISO 27001:2022 · 4 controls

  • 5.16 Identity management
  • 8.15 Logging
  • 8.2 Privileged access rights
  • 8.32 Change management
  • NIST-CSF-DE.CM-03 Personnel activity and technology usage are monitored to find potentially adverse events
  • NIST-CSF-ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked
  • NIST-CSF-PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization
  • NIST-CSF-PR.PS-04 Log records are generated and made available for continuous monitoring

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-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

HIPAA Security Rule · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

  • E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)
  • SEC04-BP01 Configure service and application logging
  • ASBv3-LT-2 Enable threat detection for identity and access management

C5 (Germany) · 1 control

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

CIS Controls v8 · 1 control

  • CIS-8.5 Collect Detailed Audit Logs

FedRAMP High · 1 control

FedRAMP Moderate · 1 control

ISO 27002:2022 · 1 control

ISO 27701:2019 · 1 control

  • 6.9.4 Logging and monitoring

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