The clearest warning signs are card data you cannot trace, systems you cannot classify, and controls that only get attention before an assessment. A red flag does not prove a compliance failure. It tells you where to check first.
These signs assume PCI DSS already applies to you. If you are still working that out, start with who needs PCI DSS.
Signs your scope may be wrong
You cannot show where account data flows
Requirement 1.2.4 calls for an accurate diagram of all account data flows across systems and networks. If your diagram is old, or nobody can explain it, your scope may rest on assumptions. Requirement 12.5.2 expects you to confirm scope at least once every 12 months and upon significant change.
Card data appears in unexpected places
PCI DSS names backups, removable media, paper, and audio recordings as often-overlooked storage locations. A card number in one of those places may mean your cardholder data environment (CDE) is bigger than you think. Requirement 12.10.7 calls for response procedures when stored primary account numbers appear where they are not expected.
Also check whether sensitive authentication data lingers anywhere. Requirement 3.3.1 prohibits storing it after authorization, even if it is encrypted.
Your network is flat, or segmentation is untested
PCI SSC scoping guidance says that without adequate segmentation, the entire network is in scope. PCI DSS does not require segmentation, but if you rely on it, you need to test it. Requirement 11.4.5 calls for penetration tests of segmentation controls at least once every 12 months and after changes. Service providers do this every six months under Requirement 11.4.6.
New systems connect without review
Systems that connect to the CDE are in scope, whatever their function. Remote support tools, partner links, and shared services can all add to your scope quietly. Requirement 12.5.1 expects a current inventory of in-scope components, so a stale inventory is a useful warning.
Your payment setup has changed since you chose your SAQ
Each SAQ has eligibility criteria tied to how you accept payments. A new checkout design, payment channel, or provider can change which one fits. SAQ A itself warns that applicable requirements outside the SAQ may show it is unsuitable for your environment.
Signs your program may be at risk
Controls get attention only before an assessment
PCI DSS encourages business-as-usual processes so that controls keep working between assessments. Watch for a rush to collect evidence near the deadline. A missed task is hard to repair later, since a compensating control cannot address a requirement missed in the past.
Nobody can name the owner of a control
Requirement 12.1.3 calls for clearly defined security roles that personnel acknowledge. If a control’s owner changes depending on whom you ask, it may not be running as written.
You assume your providers have it covered
Requirement 12.8.1 calls for a list of your providers, and 12.8.4 calls for monitoring their compliance status at least once every 12 months. Requirement 12.8.5 calls for records of who manages which requirement. Gaps in these records often mean nobody has confirmed shared responsibilities.
Compensating controls roll forward unchanged
Assessors evaluate compensating controls at each annual assessment. The original constraint or surrounding environment may have changed since a control was first documented. If nobody has reviewed yours recently, put it on the list.
Start with the sign closest to your payment flow, then widen the check from there. The PCI DSS hub maps the rest of the topic.
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 (Requirements 1.2.4, 12.5.1, 12.5.2, and 12.5.2.1)
- PCI DSS v4.0.1 (Requirements 3.2.1, 3.3.1, and 12.10.7)
- PCI DSS v4.0.1 (Section 4, Segmentation, and Requirements 11.4.5 and 11.4.6)
- PCI DSS v4.0.1 (Requirements 12.1.3, 12.8.1, 12.8.4, and 12.8.5)
- PCI DSS v4.0.1 (Section 5, Business-as-Usual Processes, and Appendix B, Compensating Controls)
- Guidance for PCI DSS Scoping and Network Segmentation, v1.1 (Scoping categories and flat network guidance)
- PCI DSS v4.0.1 SAQ A, Revision 1 (Merchant Eligibility Criteria)
