PCI DSS 4.0
Req 10: Logging and Monitoring

PCI DSS 4.0 10.2.1.4: 10.2.1.4 Logs capture invalid logical access attempts

Audit logs must record every invalid logical access attempt. Applies to all entities. The guidance notes that repeated invalid login attempts against a target can signal password guessing or a brute-force attack. Customized approach objective: every invalid access attempt leaves a record.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 26 controls across 17 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 · 3 controls

  • AC-2(12) Account Monitoring for Atypical Usage
  • AC-7 Unsuccessful Logon Attempts
  • AU-2 Event Logging

FedRAMP Moderate · 3 controls

  • AC-2(12) Account Monitoring for Atypical Usage
  • AC-7 Unsuccessful Logon Attempts
  • AU-2 Event Logging

NIST SP 800-53 Rev 5 · 3 controls

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

SOC 2 · 2 controls

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • 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

HIPAA Security Rule · 1 control

ISO 27001:2022 · 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.4 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 26 it maps to, and the evidence behind each claim, over MCP and REST.