Applicable vulnerabilities that are not ranked high-risk or critical under the entity's Requirement 6.3.1 rankings must be addressed in line with the risk level established by a targeted risk analysis (conducted following all elements of Requirement 12.3.1), and rescans are run as needed. Applicability: the timeframe for fixing lower-risk vulnerabilities depends on that risk analysis, which must at minimum identify the assets being protected, the threats, and how likely a threat is and what its impact would be. Objective under the customized approach: vulnerabilities ranked below high-risk or critical are fixed at a frequency that matches the entity's risk. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
This control maps to 39 controls across 20 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.3.1.1 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.