- SOC 2 Readiness
- 24/7 incident line
- 24/7 security operations team
Payment Card Security
PCI DSS Compliance
Achieve and maintain PCI DSS compliance for secure payment card processing. Protect cardholder data and meet industry security standards.

Who This Service Is For
Any organization that stores, processes or transmits payment card data, or that can affect the security of that data, falls under the Payment Card Industry Data Security Standard. That includes retailers and e-commerce sites, restaurants and hospitality groups, municipalities and utilities that take card payments, software companies that embed payments in their product, and service providers that host or support a client's card environment.
Most teams come to us at one of three moments: an acquiring bank has asked for a validation they have never completed, a QSA assessment is approaching and the gap list is long, or the v4.0.1 requirements that became mandatory in March 2025 exposed controls that used to be optional. Our team handles the practical work between "we need to be compliant" and a clean SAQ or Report on Compliance.
PCI DSS v4.0.1 Requirements
Build and Maintain a Secure Network and Systems
- Req 1: Install and maintain network security controls
- Req 2: Apply secure configurations to all system components
Protect Account Data
- Req 3: Protect stored account data
- Req 4: Protect cardholder data with strong cryptography during transmission over open, public networks
Maintain a Vulnerability Management Program
- Req 5: Protect all systems and networks from malicious software
- Req 6: Develop and maintain secure systems and software
Implement Strong Access Control Measures
- Req 7: Restrict access by business need to know
- Req 8: Identify users and authenticate access to system components
- Req 9: Restrict physical access to cardholder data
Regularly Monitor and Test Networks
- Req 10: Log and monitor all access to system components and cardholder data
- Req 11: Test security of systems and networks regularly
Maintain an Information Security Policy
- Req 12: Support information security with organizational policies and programs
Merchant and Service Provider Levels, in Detail
| Merchant level | Annual transactions (per brand) | Typical validation |
|---|---|---|
| Level 1 | Over 6 million, across all channels, or any merchant a brand designates (for example after a breach) | Report on Compliance by a QSA (some brands accept an internal assessor), quarterly ASV scans, Attestation of Compliance |
| Level 2 | 1 to 6 million, across all channels | SAQ, quarterly ASV scans, AOC. Mastercard expects a Level 2 SAQ to be completed by staff with ISA training, or a ROC instead |
| Level 3 | 20,000 to 1 million e-commerce transactions | SAQ, ASV scans where the SAQ requires them, AOC |
| Level 4 | Fewer than 20,000 e-commerce, and all other merchants up to 1 million | SAQ and scans as the acquirer requires. Requirements vary most at this level |
| Service provider level | Annual transactions | Typical validation |
|---|---|---|
| Level 1 | More than 300,000 transactions stored, processed or transmitted for Visa or Mastercard | Report on Compliance by a QSA, quarterly ASV scans, AOC. Often listed on the brand’s service provider registry |
| Level 2 | Fewer than 300,000 | SAQ D for Service Providers (or a ROC), quarterly ASV scans, AOC |
Thresholds count each brand’s transactions separately, and American Express, Discover and JCB use their own levels. Treat this table as a guide and get your level in writing from your acquirer.
SAQ or ROC, QSA or ISA: Who Does What
| Self-Assessment Questionnaire (SAQ) | Report on Compliance (ROC) | |
|---|---|---|
| What it is | A questionnaire you complete about your own environment | A detailed report of an on-site assessment against every applicable requirement |
| Who completes it | You, sometimes with help from a consultant or an ISA | A Qualified Security Assessor, or an ISA where the brand allows |
| Who it is for | Most Level 2 to 4 merchants and Level 2 service providers | Level 1 merchants and service providers, and anyone the acquirer asks |
| Scope of questions | Depends on the SAQ type, from a short list (SAQ A) to the full standard (SAQ D) | Every applicable requirement and testing procedure |
| Output | The SAQ and an Attestation of Compliance, signed by an officer of your company | The ROC and an AOC, signed by the assessor and your company |
QSA
A Qualified Security Assessor works for a firm qualified by the PCI Security Standards Council. Independent of you, they test your controls and sign the ROC. They cannot assess controls they designed or operate for you.
ISA
An Internal Security Assessor is your own employee, trained and qualified by the Council. ISAs improve the quality of SAQs and internal assessments, and some brands let an ISA perform a Level 1 merchant’s assessment.
AOC
The Attestation of Compliance is the summary your acquirer, partners and customers actually receive. Ask every service provider for theirs, and check its date and which services it covers.
Which SAQ Applies to You?
Which PCI DSS SAQ is likely to apply?
Three steps: how you take cards, whether you store card numbers, and whether you handle card data for other businesses. The answer is indicative; your acquirer decides how you validate.
PCI DSS 4.0 Is Now Mandatory
All future-dated requirements became mandatory March 31, 2025. Learn about the 64 new requirements including MFA mandates, client-side script controls, and authenticated scanning.
The v4.0.1 Requirements That Catch Teams Out
MFA for all access into the CDE
Payment page scripts
Authenticated internal scanning
Targeted risk analyses
Phishing and password changes
Scope confirmation and the customized approach
ASV Scanning: The Quarterly Test You Cannot Do Yourself
| External scan | Internal scan | |
|---|---|---|
| Requirement | 11.3.2 | 11.3.1 |
| Who runs it | A PCI SSC Approved Scanning Vendor | Qualified staff or a third party; independence is not required |
| What it sees | Internet-facing IPs and domains in scope | Systems inside the network, with credentials (authenticated) |
| Pass mark | No vulnerability scored 4.0 or higher on CVSS, and none of the automatic failures in the ASV Program Guide | High-risk and critical vulnerabilities resolved; others managed under a risk analysis |
How a quarter works
- You give the ASV every external IP and domain in scope; leaving one out is your risk, not theirs.
- The ASV scans, then you fix or dispute findings, with evidence, before the quarter ends.
- A rescan confirms the fix. Only the passing report counts.
- Four passing quarters a year are expected; a first-time validation can usually rely on one recent pass plus a documented plan.
GuardsArm is not an ASV. We run internal and authenticated scanning, help you choose an ASV, and fix or document what the scans find. Our vulnerability scanning service covers the internal side.
The Yearly PCI Cycle
1 of 4
Daily to weekly
- Review security events and logs of critical systems (10.4.1), using automated tools
- Check payment pages for unauthorized script and header changes (11.6.1), at least weekly unless a risk analysis sets otherwise
- Run change detection on critical files (11.5.2), at least weekly
2 of 4
Quarterly
- External vulnerability scan by an ASV, with a passing result (11.3.2)
- Authenticated internal vulnerability scan, with rescans after fixes (11.3.1)
- Scan for unauthorized wireless access points (11.2.1)
- Service providers: review that staff follow security policies and procedures (12.4.2)
3 of 4
Every six months
- Review network security control rule sets (1.2.7)
- Review user accounts and access privileges (7.2.4)
- Service providers: confirm scope (12.5.2.1) and test segmentation (11.4.6)
4 of 4
Every 12 months
- Confirm PCI DSS scope (12.5.2) and review the security policy (12.1.2)
- Internal and external penetration tests (11.4.2, 11.4.3) and merchant segmentation tests (11.4.5)
- Review targeted risk analyses (12.3.1), cryptographic suites (12.3.3) and hardware and software in use (12.3.4)
- Security awareness training (12.6.3), incident response plan test (12.10.2) and service provider compliance check (12.8.4)
- Submit the SAQ or ROC, the Attestation of Compliance and ASV scan reports to your acquirer
Segmentation Testing
Segmentation is the main way to keep most of your network out of PCI scope. It is not required, but if you rely on it to reduce scope, you must prove it works. Requirement 11.4.5 asks merchants to test segmentation controls at least once every 12 months and after any change to them. Service providers must test every six months (11.4.6).
The test is a penetration test aimed at the boundary: from every out-of-scope segment, the tester tries to reach the cardholder data environment, and confirms that all segmentation controls and methods actually isolate it. The tester must be qualified and organizationally independent of the systems being tested, which can be an internal team that does not manage those systems.
Typical failures are a forgotten firewall rule, a management network that touches both sides, a shared directory server, monitoring or backup agents with broad access, and cloud security groups that allow more than the diagram shows.
Before the segmentation test
- 1
Draw the boundary
A current network diagram with every CDE and connected-system segment.
- 2
List every control
Firewalls, security groups, VLAN access lists, host firewalls.
- 3
Review the rules
Each allowed path into the CDE has a business justification.
- 4
Plan the retest
Fix what the test finds and retest before you sign.
How a GuardsArm PCI Engagement Runs
- Step 1Typically the first week or two
Scope and data flows
We map every place card data is captured, transmitted, processed or stored, including the people, systems and third parties that can affect its security. The result is a cardholder data flow diagram and a draft scope statement. - Step 2
Scope reduction options
Before anyone fixes a control, we look for ways to shrink the environment: segmentation, tokenization, hosted payment pages or point-to-point encryption. A smaller scope usually saves more effort than any single remediation. - Step 3Usually a few weeks
Gap assessment
We test your environment against each applicable v4.0.1 requirement, interview control owners and review evidence. Every gap is written up with the requirement number, what we observed and what would close it. - Step 4
Remediation support
Our team works with yours through the fixes: network security control rules, logging and alerting, MFA, script management on payment pages, policies and targeted risk analyses. We can run the internal testing the standard requires alongside this. - Step 5
Validation readiness
We assemble the evidence set, help you complete the correct Self-Assessment Questionnaire, or prepare you for your Qualified Security Assessor so the Report on Compliance runs without surprises. - Step 6
Business as usual
PCI DSS is continuous. We can stay on to track the recurring activities: quarterly scans, log reviews, access reviews, annual scope confirmation and policy refreshes.
What You Receive
- Cardholder data flow diagram and scope statement
- Scope reduction options with the trade-offs of each
- Gap assessment mapped to v4.0.1 requirement numbers
- Prioritized remediation plan with owners
- Policy and procedure set aligned to Requirement 12
- Targeted risk analysis templates and completed examples
- Service provider responsibility matrix
- Evidence index organized for your SAQ or QSA
What You Provide
An engagement moves fastest when these are ready early.
Payment channel list
Every way you accept cards: in store, online, by phone, by mail.
Network and system inventory
Diagrams, asset lists and cloud accounts that touch payments.
Service provider AOCs
Attestations of Compliance from processors, gateways and hosts.
Previous validation
Your last SAQ or ROC, and any acquirer correspondence.
A named owner
One person who can make scope and remediation decisions.
Common Mistakes We See
Treating the SAQ as a form to fill in. An SAQ is a legal attestation signed by an officer of the company. Answering "yes" to a control that is not in place exposes the business if a breach is ever investigated.
Leaving the network flat. Without effective segmentation, every system that can talk to the cardholder data environment is in scope. Segmentation has to be tested, not assumed, and the standard sets how often.
Forgetting the payment page. When a site embeds a third-party payment form, the page that loads it is still an attack surface. Script controls under v4.0.1 exist because attackers inject skimming code into exactly these pages.
Ignoring service providers. Many organizations cannot say which provider is responsible for which requirement. A written responsibility matrix and current AOCs close that gap and are expected under Requirement 12.8.
What GuardsArm Is Not
Not a QSA
We prepare you for assessment; a QSA issues any Report on Compliance.
Not an ASV
External quarterly scans must come from an Approved Scanning Vendor.
Not your acquirer
Your bank decides your level and validation method.
More on PCI DSS
Start with the basics
The PCI compliance guide explains the 12 requirements in plain language and the ways to reduce scope.
Moving to v4.0.1?
The PCI DSS 4.0 page covers what changed, the 2025 requirements by theme, the customized approach and a migration checklist.
Evidence, not assumptions
PCI DSS Compliance: evidence and assessment handoff
Readiness is preparation, not an outcome determination. The exact evidence and external review process depend on the applicable requirements and agreed scope.
Readiness support
Define the boundary, review control design, coordinate remediation and organize an evidence index. Control owners remain responsible for operating controls and supplying accurate records.
Independent audit or certification
Where applicable to PCI DSS Compliance, an independent auditor, assessor, certification body or authority sets its own procedures, evaluates the evidence and reaches its own conclusion. Readiness support does not replace that work or guarantee its outcome.
Evidence examples
Control design and governance
- Approved policies, standards and procedures with version and ownership history.
- A scope and control matrix showing requirement coverage and control owners.
- Risk decisions, exceptions, remediation approvals and leadership review records.
Operating and technical records
- Dated access reviews, change tickets, training completion and vulnerability follow-up.
- Source exports for identity, MFA, logging, backup and other in-scope configurations.
- Records that show both the review period and any gaps, failures or corrective actions.
Data, third parties and testing
- Relevant data inventories or flow maps, vendor records and contractual control evidence.
- Test plans and results, exercise records, incident timelines and tracked follow-up actions.
- An evidence index linking each source item to its owner, control and assessment request.
Roles and handoff
Your control owners
Operate controls, provide authentic source evidence, explain variations and complete remediation.
GuardsArm readiness team
Map requests, review completeness and consistency, track gaps and prepare the handoff package.
Independent reviewer, where applicable
Defines its requests and procedures, evaluates evidence independently and issues conclusions within its remit.
- 1
Request
Tie each evidence request to the agreed scope, criterion, owner and review period.
- 2
Collect
Preserve source context and record dates, coverage and known limitations.
- 3
Review
Mark items ready, open or not applicable, with rationale and follow-up ownership.
- 4
Hand off
Provide the index, source access and outstanding-item log to the intended reviewer.
PCI DSS Compliance FAQs
Straight answers to the questions merchants and service providers ask us most.
Is GuardsArm a Qualified Security Assessor (QSA)?
No. GuardsArm is not a QSA and does not issue Reports on Compliance. We do the preparation and remediation work: scoping, gap assessments, control implementation, testing and evidence collection. If your acquirer or a card brand requires a QSA, we work alongside the assessor you engage so the assessment goes smoothly. For merchants that validate with a Self-Assessment Questionnaire, we help you complete the right SAQ accurately.
Which version of PCI DSS applies now?
PCI DSS v4.0.1 is the current version. It is a limited revision of v4.0 that corrected errors and clarified wording without adding new requirements, and v4.0 was retired at the end of 2024. The requirements that v4.0 marked as future-dated became mandatory on 31 March 2025, so any assessment today covers the full requirement set.
How do we know which merchant level and SAQ we fall under?
Merchant levels are set by each card brand, mostly by annual transaction volume, and your acquiring bank tells you how to validate. The SAQ type depends on how you accept payments. A merchant that fully outsources an e-commerce payment page may qualify for SAQ A, one whose site controls how the payment page is delivered usually falls under SAQ A-EP, and environments that store, process or transmit card data on their own systems generally need SAQ D. Eligibility criteria change between SAQ revisions, so we confirm the current version with you and your acquirer.
Do we still need PCI DSS if a payment processor handles our cards?
Usually yes, though the scope can be much smaller. Outsourcing moves many requirements to your provider, but you still own the parts you control, such as the web page that redirects or embeds the payment form, the staff who handle card details by phone, and the management of your service providers. You also need each provider's Attestation of Compliance and a clear split of responsibilities.
How long does it take to become compliant?
It depends on scope and starting point. A small merchant with a fully outsourced payment flow can often finish in a few weeks. An organization that stores card data across a flat network may need several months, most of it spent on segmentation, logging and access control. The gap assessment gives you a realistic plan before you commit to dates.
Can you perform the scans and penetration tests PCI DSS requires?
We perform internal vulnerability scanning, penetration testing and segmentation testing. External quarterly scans for PCI DSS must come from a PCI SSC Approved Scanning Vendor (ASV); we help you choose one, interpret the results and fix what they find.
Still Have Questions?
Our cybersecurity experts are here to help. Get personalized answers and a free security consultation.