Wherever a PCI DSS requirement calls for a targeted risk analysis, that analysis must be documented and contain: the assets being protected; the threats the requirement guards against; factors that raise how likely a threat is to materialise and/or how much harm it would do; a resulting analysis that sets, and justifies, how the frequency or processes chosen by the entity reduce that likelihood or harm; a check of every such analysis (minimum cadence: at least every 12 months) deciding whether results still hold or a new analysis is needed; and performance of updated analyses when that annual review shows the need. Objective under the customized approach: current knowledge and evaluation of risks to the CDE are kept up to date. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
This control maps to 49 controls across 25 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 12.3.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.