Site icon RSI Security

Common PCI DSS Mistakes and What to Do Instead

Many PCI DSS mistakes involve scope, ownership, and timing. Teams leave systems out without verification, assume a provider covers everything, or treat compliance as a once-a-year task. Each one has a practical fix, and many fixes start with better documentation and clearer owners.

Scoping and validation mistakes

1. Deciding a system is out of scope without verifying it

Why it happens. Teams focus on systems that handle card data and overlook those that connect to them. Authentication, remote access, and logging servers are easy to miss.

What to do instead. Start by assuming everything is in scope, then verify what is not. Follow the steps in Requirement 12.5.2, and keep documentation showing how you determined scope.

2. Relying on segmentation you have not tested

Why it happens. A network diagram can show a boundary that the configuration does not enforce. PCI SSC’s scoping guidance warns of many compromises through systems wrongly judged out of scope.

What to do instead. Confirm segmentation with penetration testing at least every 12 months and after changes to it (11.4.5). Service providers test at least every six months (11.4.6). Keep protecting out-of-scope systems as well.

3. Assuming a compliant provider makes you compliant

Why it happens. Outsourcing feels like handing off the whole obligation, and provider marketing can reinforce that impression.

What to do instead. Keep a list of providers, written agreements, and a record of who manages each requirement (12.8). Monitor each provider’s status at least once every 12 months. Our page on choosing a provider can help with selection.

4. Choosing an SAQ by length

Why it happens. A shorter form looks like less work, and teams may not read the eligibility criteria closely.

What to do instead. Check every criterion for the SAQ against your real setup, and ask your acquirer when unsure. SAQ A’s criteria for e-commerce merchants include confirming the site is not susceptible to script attacks.

5. Marking requirements Not Applicable or In Place too quickly

Why it happens. A requirement can look irrelevant at first glance, and a fix already underway can feel finished.

What to do instead. Verify before you select Not Applicable, and document your explanation in the SAQ’s appendix. Use Not in Place for work still in progress, since PCI DSS does not count scheduled controls.

Technical control mistakes

6. Letting diagrams go stale

Why it happens. Diagrams are often drawn for an assessment, then ignored as systems and vendors change.

What to do instead. Tie updates for your network diagram (1.2.3) and data flow diagram (1.2.4) to change management. Include backups and paper flows, and make sure the two diagrams reconcile.

7. Finding account data where nobody expected it

Why it happens. Data collects in places outside the main payment flow. Primary account numbers (PAN) can end up in backups, along with audit, exception, or troubleshooting logs.

What to do instead. Search all locations during scope confirmation. Make stored PAN unreadable wherever it lives (3.5.1), and verify deletion against your retention rules at least once every three months (3.2.1). Most entities cannot keep sensitive authentication data after authorization, even if encrypted (3.3.1).

8. Treating a TLS certificate as e-commerce security

Why it happens. A browser padlock is visible and simple, so it can seem to cover the whole site.

What to do instead. Treat the certificate as one part of the job. Accept only trusted, valid certificates, support only secure protocol versions (4.2.1), and inventory your trusted keys and certificates (4.2.1.1). E-commerce sites still need scans and other applicable controls.

9. Ignoring scripts on pages around a provider’s iframe

Why it happens. Teams hear that the provider handles payment, and they stop looking at their own page. Marketing and tag management scripts can change without security review.

What to do instead. Identify which scripts you manage and which your provider manages, then apply Requirements 6.4.3 and 11.6.1 where they apply. Bring marketing and web teams into the approval process.

10. Stopping at one MFA prompt

Why it happens. Teams add multi-factor authentication (MFA) at the VPN and assume it covers everything beyond it.

What to do instead. Treat remote access (8.4.3) and access into the CDE (8.4.2) separately. A user who connects remotely and then enters the CDE authenticates with MFA twice.

Ongoing program mistakes

11. Treating compliance as an annual project

Why it happens. Validation has a visible due date, while daily and quarterly tasks do not. Work then bunches up just before the assessment.

What to do instead. Assign owners and build the work into normal operations. Our guide to maintaining compliance lists recurring activities by frequency.

12. Reviewing logs only on business days

Why it happens. Review schedules often follow staffing hours, and manual review is hard to sustain.

What to do instead. PCI DSS defines daily as every day of the year, so plan for weekends and holidays. Automated mechanisms are required for these reviews (10.4.1.1), so use them to surface events that need attention.

13. Using a risk analysis to stretch a fixed frequency

Why it happens. The targeted risk analysis is a new concept, and teams can read it as general flexibility.

What to do instead. Use this analysis only where a requirement allows it. PCI SSC’s guidance says it cannot make a stated frequency less frequent. A legitimate constraint may call for a compensating control, and a customized approach is a separate path.

For examples of how these patterns appear in practice, see our page on audit findings. To act on them, use our preparation steps.

Frequently asked questions

Does using a PCI compliant payment processor make my business compliant?
No. PCI DSS says using a compliant provider does not make a customer compliant or remove its own responsibility. You still manage the relationship and confirm your own compliance as requested.
Can a targeted risk analysis let me run a control less often than PCI DSS states?
No. A targeted risk analysis sets the frequency only where a requirement allows it. To run a fixed-frequency activity less often, you would need a customized approach or a compensating control that qualifies.
Can I mark a requirement In Place if the fix is already scheduled?
No. Controls that are not yet implemented or are scheduled for a future date are not in place. In an SAQ, use Not in Place until the work is finished and tested.
Does a daily log review have to happen on weekends?
Yes. PCI DSS defines daily as every day of the year, not only business days. Automated mechanisms can help you meet this expectation.

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

Request a consultation

Exit mobile version