Skip to content

The PCI DSS compliance calendar: every recurring requirement by frequency

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

Most failed assessments are not missing controls. They are controls that ran in March and never again.

Daily

  • 10.4.1 — review security events and the logs of CDE components, critical system components and security functions.
  • 10.4.1.1 — the review is performed by automated mechanisms.

Weekly

  • 11.5.2 — change-detection mechanism compares critical files at least weekly.
  • 11.6.1 — payment-page change-and-tamper detection runs at least every seven days, or at the frequency set by a targeted risk analysis.

Every three months

  • 11.3.1 — internal vulnerability scans, with high-risk and critical findings resolved and rescanned.
  • 11.3.2 — external vulnerability scans by an ASV, with a passing result.
  • 11.2.1 — testing for authorised and unauthorised wireless access points.
  • 3.2.1 — verify that stored account data beyond its retention period has been securely deleted.
  • 12.4.2 — service providers only: reviews confirming personnel are performing their security tasks.

Every six months

  • 1.2.7 — review network security control configurations.
  • 7.2.4 — review all user accounts and their access privileges.
  • 11.4.6 — service providers only: penetration test of segmentation controls.
  • 12.5.2.1 — service providers only: confirm PCI DSS scope.

Every 12 months

  • 11.4.2 and 11.4.3 — internal and external penetration tests.
  • 11.4.5 — merchants: penetration test of segmentation controls.
  • 12.1.2 — review the information security policy.
  • 12.3.1 — review each targeted risk analysis.
  • 12.3.3 and 12.3.4 — review cipher suites and protocols, and hardware and software technologies.
  • 12.5.2 — confirm PCI DSS scope.
  • 12.6.3 — security awareness training for all personnel.
  • 12.8.4 — monitor the PCI DSS compliance status of third-party service providers.
  • 12.10.2 — review and test the incident response plan.
  • 9.4.5.1 — inventory electronic media containing cardholder data.

Event-driven

  • After a significant change: internal and external scans (11.3.1.3, 11.3.2.1), penetration testing, and a scope review.
  • On hire: security awareness training (12.6.3).
  • On termination: immediate revocation of access (8.2.5).
  • On suspected compromise: key replacement (3.7.5) and password changes for affected accounts.

Evidence for every occurrence

Assessors sample across the assessment period, not just the week before fieldwork. A missed second-quarter ASV scan cannot be fixed retroactively, and a daily log review that stopped for a month while an agent was broken will show up in the sample.

Whatever you use to track it — a GRC platform, a ticketing system, a shared calendar — each entry needs three things: an owner, a due date, and a fixed place where the dated evidence lands. Schedule quarterly scans early in the quarter so there is time to remediate and rescan before it ends.

PCI DSS Requirement 11 explained PCI DSS Requirement 10 explained PCI ASV scans

Run your compliance program in one workspace.