Maintaining PCI DSS compliance means running your controls all year and keeping proof that they ran. That includes daily log review, scans every three months, and scope confirmation at least every 12 months. Service providers have added, more frequent duties, and payment brands and acquirers set your validation requirements.
Validate again, and confirm scope first
PCI DSS refers to an annual assessment, and the organizations that manage compliance programs decide who validates and how. Check your due date with your acquirer or requesting organization.
Your own scope confirmation (12.5.2) comes before that work. It is your responsibility, and your assessor’s scoping check does not replace it. Any compensating control reported in a ROC must also be documented, reviewed, and validated annually.
Recurring activities by frequency
Each row reflects PCI DSS v4.0.1. “All” means the row generally applies under the full standard, although your SAQ may include fewer requirements. Scope and environment always determine what applies to you.
| Frequency | Req. | Activity | Applies to |
|---|---|---|---|
| Daily | 10.4.1 | Review security events and logs from systems that handle account data, critical components, and security-function systems | All |
| Weekly | 11.5.2 | Run critical file comparisons | All |
| Weekly, or per targeted risk analysis | 11.6.1 | Run payment page change and tamper detection | Entities with applicable payment pages |
| Three months | 3.2.1 | Verify that data past its retention period was securely deleted | Entities storing account data |
| Three months | 11.2.1 | Test for and identify wireless access points | All |
| Three months | 11.3.1 | Run internal vulnerability scans | All |
| Three months | 11.3.2 | Run external scans through an ASV | All |
| Three months | 12.4.2 | Review whether personnel follow security policies and procedures | Service providers only |
| Six months | 1.2.7 | Review network security control configurations | All |
| Six months | 7.2.4 | Review user accounts and access privileges | All |
| Six months | 11.4.6 | Penetration test segmentation controls, and after changes to them | Service providers using segmentation |
| Six months | 12.5.2.1 | Confirm scope, and upon significant change | Service providers only |
| Six months | A1.1.4 | Penetration test logical separation between customers | Multi-tenant service providers |
| 12 months | 6.2.2 | Train software development personnel | Entities with bespoke or custom software |
| 12 months | 9.4.1.2 | Review security of offline media backup locations | Entities with offline backups containing cardholder data |
| 12 months | 9.4.5.1 | Inventory electronic media with cardholder data | Entities with that media |
| 12 months | 11.4.2, 11.4.3 | Run internal and external penetration tests, and after significant change | All |
| 12 months | 11.4.5 | Penetration test segmentation controls, and after changes to them | Entities using segmentation |
| 12 months | 12.1.2 | Review the information security policy | All |
| 12 months | 12.3.1 | Review each targeted risk analysis | Entities with these analyses |
| 12 months | 12.3.2 | Perform the targeted risk analysis for customized controls | Entities using the customized approach |
| 12 months | 12.3.3 | Review cipher suites and protocols | All |
| 12 months | 12.3.4 | Review hardware and software technologies | All |
| 12 months | 12.5.2 | Confirm scope, and upon significant change | All |
| 12 months | 12.6.2, 12.6.3 | Review the awareness program, train personnel, and collect acknowledgments | All |
| 12 months | 12.8.4 | Monitor provider compliance status | Entities using providers |
| 12 months | 12.10.2 | Review and test the incident response plan | All |
PCI DSS defines these terms precisely. Daily means every day of the year, and weekly means at least once every seven days. Every three months means at least once every 90 to 92 days. Some limits also run continuously, such as 12 months of log history (10.5.1).
Log review in practice
Requirement 10.4.1 covers your highest-priority logs, and Requirement 10.4.1.1 requires automated mechanisms to review them. A baseline of normal activity helps those tools highlight unusual events. Set the frequency for all other logs in a targeted risk analysis (10.4.2.1).
Our guide to the PCI DSS requirements covers logging in more detail.
Requirement 12.4: for service providers
Requirements 12.4.1, 12.4.2, and 12.4.2.1 apply only to service providers. Executive management takes responsibility for the compliance program. Every three months, someone other than the task owner reviews tasks such as daily log reviews and configuration reviews. The results are documented, remediated, and signed off.
Merchants do not have to meet these requirements. Even so, the standard encourages periodic reviews for all entities as a business-as-usual practice.
Targeted risk analyses
Some requirements let you set the frequency through a targeted risk analysis under Requirement 12.3.1. You review each analysis at least once every 12 months. PCI SSC’s guidance offers these suggested starting points, and you still need an analysis to support your choice.
| Req. | Activity | PCI SSC suggested frequency |
|---|---|---|
| 5.2.3.1 | Evaluate components not at risk for malware | At least every six months |
| 5.3.2.1 | Run periodic malware scans | At least daily |
| 7.2.5.1 | Review application and system account access | At least every six months |
| 8.6.3 | Change application and system account passwords | At least every three months |
| 9.5.1.2.1 | Inspect point-of-interaction devices | At least monthly |
| 10.4.2.1 | Review other logs | At least weekly |
| 11.6.1 | Run payment page tamper detection | At least every seven days |
| 12.10.4.1 | Train incident response personnel | At least yearly and at the start of employment |
Requirement 11.3.1.1 also uses a targeted risk analysis to address vulnerabilities not ranked high-risk or critical. This analysis cannot make a stated frequency less frequent.
Build compliance into business as usual
Business as usual (BAU) means your security controls keep working as part of normal operations. PCI DSS recommends these habits:
- Assign overall accountability to a person or team.
- Track metrics for heavily relied-upon controls.
- Detect and respond promptly to security control failures, which Requirement 10.7.2 also requires.
- Assess changes for PCI DSS impact before you make them.
- Review evidence periodically, so it is ready for your next assessment.
When an activity is missed
Expect an occasional miss, and plan for it. PCI DSS expects a process that notifies you promptly and finds out why the activity was missed. You then perform it as soon as possible, get back on schedule, and document those steps. Our page on common mistakes covers other pitfalls to avoid.
Frequently asked questions
Work with RSI Security
RSI Security is a PCI Qualified Security Assessor (QSA) company and an Approved Scanning Vendor (ASV). It performs PCI DSS assessments and quarterly ASV scans. Organizations that need help with scoping or readiness can work with RSI Security through a separate advisory engagement. RSI Security provides either advisory or assessment to a given client, never both.
Schedule a PCI DSS assessment · Talk to an advisor about readiness
Sources
- PCI DSS v4.0.1 (Section 5: Best Practices for Implementing PCI DSS into Business-as-Usual Processes)
- PCI DSS v4.0.1 (Section 7: Description of Timeframes Used in PCI DSS Requirements)
- PCI DSS v4.0.1 (Requirements 1.2.7, 3.2.1, 6.2.2, 7.2.4, 9.4.1.2, 9.4.5.1, 10.4.1, 10.4.2.1, 10.5.1, 11.2.1, 11.3.1, 11.3.2, 11.4.2 to 11.4.6, 11.5.2, and 11.6.1)
- PCI DSS v4.0.1 (Requirements 12.1.2, 12.3.1 to 12.3.4, 12.4.1 to 12.4.2.1, 12.5.2, 12.5.2.1, 12.6.2, 12.6.3, 12.8.4, 12.10.2, and A1.1.4)
- PCI DSS v4.x Targeted Risk Analysis Guidance (November 2023) (Frequently Asked Questions and TRA Requirements and Frequency Recommendations)
