Exploitable vulnerabilities and security weaknesses discovered during penetration testing must be corrected: in line with how the entity rates the risk each issue poses, using the Requirement 6.3.1 risk ranking; and with penetration testing repeated to verify that the corrections work. Guidance (good practice): when assessing risk, entities should consider how likely exploitation is and whether other controls reduce the risk, and any weakness showing a PCI DSS requirement is not met should be addressed. Objective under the customized approach: weaknesses and vulnerabilities uncovered when system defenses are tested get mitigated.
This control maps to 58 controls across 28 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
You are reading one control. How much of PCI DSS 4.0 have you already done?
PCI DSS 4.0 11.4.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.