Skip to content

PCI DSS targeted risk analysis: requirement 12.3.1 in practice

By Sam Rivera, Founder, SentinelPanda · October 24, 2026 · 3 min read · PCI DSS

Flexibility in PCI DSS 4.0 is not free. Every "periodically" comes with a paper trail.

Why 12.3.1 exists

PCI DSS 3.2.1 fixed most frequencies for you: quarterly, annually, daily. Version 4.0 replaced several of those fixed intervals with "periodically", on the reasonable view that a corner shop and a payment processor should not inspect terminals or review service accounts on the same schedule.

The price of that flexibility is requirement 12.3.1. Wherever a requirement lets you choose a frequency, you have to show your reasoning in a targeted risk analysis. It was a best practice until 31 March 2025 and has been assessed ever since.

Which requirements point to it

  • 5.2.3.1 — how often to re-evaluate system components you have judged not at risk from malware.
  • 5.3.2.1 — how often to run periodic malware scans, where you rely on them.
  • 7.2.5.1 — how often to review access for application and system accounts.
  • 8.6.3 — how often to change passwords for application and system accounts.
  • 9.5.1.2.1 — how often to inspect POI devices for tampering and substitution.
  • 10.4.2.1 — how often to review logs for components outside the daily review in 10.4.1.
  • 11.3.1.1 — how quickly to address vulnerabilities that are not ranked high-risk or critical.
  • 11.6.1 — how often the payment-page change-and-tamper mechanism runs, if not every seven days.
  • 12.10.4.1 — how often incident response personnel are trained.

What the analysis must contain

  • The assets being protected — specific systems, devices or account types, not "the CDE".
  • The threat the requirement exists to counter.
  • The factors that make that threat more or less likely, or more or less damaging, in your environment.
  • The resulting frequency, with the justification connecting it to those factors.
  • A review at least every 12 months to confirm the result still holds, and an updated analysis when it does not.

A worked example: POI inspection

Take 9.5.1.2.1. The assets are forty countertop terminals across six stores. The threats are skimming overlays and device substitution. The factors: two stores have terminals customers can reach unattended, staff turnover is high in all six, and the regional acquirer has reported overlay attacks in the past year. The terminals carry tamper-evident seals that a trained eye can check in seconds.

A defensible result is a visual check at opening in the two high-exposure stores and a weekly check in the other four, with the reasoning written next to each frequency. An assessor can follow that. "Monthly, because that is what we have always done" is the version that gets challenged.

How assessors read them

The test is whether the frequency follows from the analysis or the analysis was written to fit a frequency already chosen. Nine analyses that all conclude "annually" read as cost decisions, and a generic enterprise risk assessment does not satisfy 12.3.1 because it does not address a specific requirement. You can keep all nine in one document, but each needs its own reasoning.

Keep 12.3.2 separate. That requirement covers the customized approach, where you design your own control to meet a requirement's objective. It needs its own analysis per control, approved by senior management, and is a much heavier piece of work.

Common mistakes

  • One template copied nine times with only the requirement number changed.
  • No owner and no review date, so the 12-month review never happens.
  • Not revisiting the analysis after a significant change, such as a new store format or a move to unattended kiosks.
  • Choosing a frequency longer than the old fixed interval with no factor that explains why the risk went down.
PCI DSS Requirement 12 explained POI device inventory and inspection PCI DSS compensating controls

Run your compliance program in one workspace.