PCI DSS cost and timing depend mostly on your scope, your validation type, and how many controls already operate. A merchant with fully outsourced payments and a service provider validating with a ROC face very different work. Size these drivers first, because each one changes the budget and schedule that follow.
Estimate your relative effort
Each row runs from lighter to heavier effort. Find where you sit on each one to start a planning conversation with your team. The table shows no cost or duration.
| Effort driver | Lighter | Moderate | Heavier |
|---|---|---|---|
| Validation type | Short SAQ (for example, SAQ A) | Longer SAQ (for example, SAQ A-EP or C), or SAQ D | ROC with a QSA |
| Payment channels | One | Two | Three or more |
| Stored account data | None | Tokenized or minimal | Stored PAN |
| Network segmentation | CDE is fully outsourced | Clear, tested segmentation | Flat or unclear network |
| Custom payment software | None | Some integrations | You build payment software |
If most of your answers sit in the lighter column, most effort will go to confirming eligibility, documenting scope, and managing providers. In the middle, expect meaningful work on documentation, technical controls, and evidence, and start with a gap assessment. If several sit in the heavier column, scope reduction may be your best early investment: reducing storage or improving segmentation changes the size of everything that follows.
What drives PCI DSS cost
Validation type
Your validation route sets the depth of the work. An SAQ covers the requirements for a specific environment, and SAQ A is far shorter than SAQ D. A ROC documents a full assessment, typically prepared by a QSA. Payment brands and acquirers decide which route applies, so confirm it before you budget.
Scope and stored data
Scope sets how many systems, people, and processes need controls. Stored account data adds retention rules, unreadable PAN, and key management under Requirement 3. If you can stop storing data you do not need, you remove work from every later stage.
Segmentation
PCI DSS does not require segmentation. Without it, though, a flat network puts the entire network in scope. The standard says proper segmentation may reduce assessment scope and cost, along with the cost and difficulty of maintaining controls. Segmentation also adds a duty, because you must validate those controls with penetration tests (11.4.5).
Payment channels
Each acceptance channel adds its own flows, systems, and requirements. A retail terminal raises device inspection and physical security questions. An e-commerce page raises script management under Requirements 6.4.3 and 11.6.1.
Custom software
Bespoke and custom software adds secure development training (6.2.2), attack prevention techniques (6.2.4), and a software inventory (6.3.2). Teams that build payment software should plan for this work as an ongoing part of development.
Third-party providers
Outsourcing can shrink your scope, but it does not remove oversight. You still keep a provider list, written agreements, and a record of who manages which requirement (12.8). Using a compliant provider does not make you compliant.
Build the budget by category
These categories help you request quotes and assign internal owners. Each one can include outside fees, tool costs, and staff time.
| Budget category | What it covers | How often the standard expects it |
|---|---|---|
| Assessment or SAQ support | Assessor work, or help completing self-assessment | As your acquirer or brand requires |
| External scans | Approved Scanning Vendor (ASV) scans and rescans (11.3.2) | At least once every three months |
| Internal scans | Scanning tools and qualified staff (11.3.1) | At least once every three months |
| Penetration testing | Internal and external tests (11.4.2, 11.4.3) | At least every 12 months and after significant change |
| Logging and monitoring | Log tools and daily review (10.4.1, 10.4.1.1) | Daily |
| Training | Awareness training (12.6.3) | Upon hire and at least every 12 months |
| Remediation | Fixes the gap assessment identifies | One-time, then as your environment changes |
Staff time is easy to miss, so count it. Control owners run reviews, collect evidence, and answer assessor questions throughout the year.
What drives the schedule
The size of your gaps
Your gap assessment sets the real schedule. A missing document is a quick fix. Redesigning a network, or reengineering long-standing business practices to remove stored data, needs far more planning.
Controls that must be in place
PCI DSS does not treat scheduled work as complete. Controls that are not implemented yet, or that are set for a future date, are not in place. Build your plan so that fixes finish, and can be evidenced, before you validate.
Activities with a required frequency
Some controls need a track record. For a first assessment against a requirement, you generally show the activity within the most recent required period. You also show documented procedures to keep it going. After that, you must show every period. A control required every three months must have run at least four times in the previous year.
External ASV scans follow similar logic. A first assessment does not need four passing scans in 12 months if the assessor verifies the conditions in Requirement 11.3.2. These include a passing most recent scan.
People and third parties
Scheduling also depends on who else must act. Assessors, ASVs, penetration testers, and providers all have their own availability. Request provider evidence early, because you will need it to confirm their status and responsibilities.
Dates to plan around
| Date | What it means |
|---|---|
| June 2024 | PCI SSC published PCI DSS v4.0.1 |
| January 2025 | SAQ A revision 1 removed 6.4.3, 11.6.1, and 12.3.1, and added a script attack eligibility criterion |
| March 31, 2025 | Future-dated requirements stopped being best practices and now count fully in assessments |
Your own validation date comes from your acquirer or the organization requesting your results. Ask for it early and plan backward from it.
How non-compliance fees work
The PCI QSA Program Guide says participating payment brands independently establish penalties and fees. They also manage their own compliance enforcement programs. Amounts and conditions aren’t in the PCI SSC documents, so ask your acquirer what applies to you.
A non-compliant result does not have to end the conversation. An SAQ’s attestation includes a target date for compliance, and the requesting organization may ask for an action plan. Early, honest contact with your acquirer gives you the best view of your options. Our page on why PCI DSS matters covers the wider business case.
Ways to reduce effort
- Keep less data. Remove account data you do not need, and consolidate what remains into fewer locations.
- Simplify your channels. Review whether each payment channel still serves the business.
- Consider scope-reducing options. Options include segmentation, PCI-listed point-to-point encryption (P2PE) solutions, and outsourcing to a compliant provider. Confirm the effect on your eligibility first.
- Start with a gap assessment. Our steps on how to prepare show where to begin.
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 4: Segmentation and Use of Third-Party Service Providers)
- PCI DSS v4.0.1 (Section 7: Description of Timeframes Used in PCI DSS Requirements)
- PCI DSS v4.0.1 (Section 12: PCI DSS Assessment Process)
- PCI DSS v4.0.1 (Requirements 3.2.1, 3.3.1, 6.2.2, 6.3.2, 6.4.3, 11.3.2, 11.4.2, 11.4.3, 11.4.5, and 12.8.1)
- PCI DSS v4.0.1 SAQ A (r1, January 2025) (Section 3, Part 3 and Part 4: Action Plan for Non-Compliant Requirements)
- PCI QSA Program Guide v4.1 (Section 2.1: Participating Payment Brands)
- Guidance for PCI DSS Scoping and Network Segmentation (May 2017) (Section 1: Introduction)
