PCI DSS 4.0 11.4.2: 11.4.2 Internal penetration testing annually and after change
Internal penetration testing must be performed: using the methodology the entity has defined; no less than annually; after every significant upgrade or change to infrastructure or applications; by a qualified tester, whether an internal resource or an external third party; and with organizational independence of the tester (a QSA or ASV is not required). Guidance (purpose): internal testing finds vulnerabilities and misconfigurations an attacker with some internal foothold could use, and can expose previously unknown systems that indicate change control failures. Objective under the customized approach: technical testing following the defined methodology verifies internal defenses as often as needed to keep pace with new and evolving attacks and to confirm that significant changes bring in no unknown vulnerabilities.
This control maps to 38 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.
You are reading one control. How much of PCI DSS 4.0 have you already done?
PCI DSS 4.0 11.4.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.