PCI DSS 4.0
Req 12: Information Security Policies

PCI DSS 4.0 12.3.2: 12.3.2 Targeted risk analysis for each customized-approach requirement

For every requirement the entity meets through the customized approach, a targeted risk analysis must be carried out that includes: documented evidence covering each element set out in Appendix D (Customized Approach), at minimum a controls matrix and a risk analysis; sign-off of that evidence by senior management; and redoing the analysis on a cycle of at least every 12 months. Applicability: applies only to entities that use a Customized Approach. Customized approach objective: this requirement forms part of the customized approach itself and must be satisfied by anyone using that approach.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 55 controls across 18 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

ISO 27002:2022 · 6 controls

  • 5.1 Policies for information security
  • 5.24 Information security incident management planning and preparation
  • 5.35 Independent review of information security
  • 5.36 Compliance with policies, rules and standards for information security
  • 5.7 Threat intelligence
  • 8.32 Change management

FedRAMP High · 5 controls

  • CA-7(4) Continuous Monitoring | Risk Monitoring (CA-7(4))
  • PL-10 Baseline Selection. Select a control baseline for the system
  • PL-11 Baseline Tailoring. Tailor the selected control baseline by applying specified tailoring actions
  • RA-3 Risk Assessment
  • RA-7 Risk Response

NIST Cybersecurity Framework 2.0 · 5 controls

  • NIST-CSF-GV.RM-06 A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicated
  • NIST-CSF-ID.RA-03 Internal and external threats to the organization are identified and recorded
  • NIST-CSF-ID.RA-04 Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded
  • NIST-CSF-ID.RA-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization
  • NIST-CSF-ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked

NIST SP 800-53 Rev 5 · 5 controls

SOC 2 · 5 controls

  • SOC2-CC3.1 CC3.1 Objectives specified clearly enough to assess risk (COSO principle 6)
  • SOC2-CC3.2 CC3.2 Identifying and analysing risks to objectives (COSO principle 7)
  • SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)
  • SOC2-CC5.1 CC5.1 Selecting control activities that mitigate risk (COSO principle 10)
  • SOC2-CC9.1 CC9.1 Mitigating risks of business disruption

FedRAMP Moderate · 4 controls

  • CA-7(4) Continuous Monitoring | Risk Monitoring (CA-7(4))
  • PL-10 Baseline Selection. Select a control baseline for the system
  • PL-11 Baseline Tailoring. Tailor the selected control baseline by applying specified tailoring actions
  • RA-3 Risk Assessment

HIPAA Security Rule · 4 controls

ISO 27001:2022 · 4 controls

  • 5.22 Monitoring, review and change management of supplier services
  • 5.25 Assessment and decision on information security events
  • 5.35 Independent review of information security
  • 8.32 Change management

NIST SP 800-66 Rev 2 · 4 controls

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 3 controls

ISO 22301:2019 · 3 controls

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

C5 (Germany) · 1 control

CMMC 2.0 · 1 control

ISO 27701:2019 · 1 control

  • 5.6.2 Information security risk assessment

NIS2 Directive · 1 control

  • Art.21.1 Take proportionate all-hazards measures calibrated to the entity's own risk exposure

NIST SP 800-171 Rev 3 · 1 control

NIST SP 800-172 · 1 control

  • 3.11.4e Security Solution Rationale Document

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 12: Information Security Policies

You are reading one control. How much of PCI DSS 4.0 have you already done?

PCI DSS 4.0 12.3.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.

If you hold ISO 27001:202249.6% covered · 141 gapsIf you hold FedRAMP Moderate49.3% covered · 142 gapsIf you hold NIST SP 800-53 Rev 547.5% covered · 147 gapsIf you hold ISO 27002:202243.2% covered · 159 gapsIf you hold CIS Controls v838.2% covered · 173 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.136.4% covered · 178 gaps

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.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

The graph holds this control, the 55 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll PCI DSS 4.0 controls