PCI Approved Scanning Vendors: The Complete Guide to ASV Selection and Compliance (2026)

Published on

Updated on

Key Takeaways
  • A PCI Approved Scanning Vendor (ASV) is an organization tested and listed by the PCI Security Standards Council (PCI SSC) to perform the external vulnerability scans required under PCI DSS Requirement 11.3.2.
  • Only scan reports from a vendor currently on the official PCI SSC ASV list are accepted by acquirers and card brands; the list is not static, so status must be verified at the time you select a vendor, not assumed from a vendor's marketing claims.
  • Under PCI DSS v4.0.1 (the sole enforced standard since March 31, 2025), ASVs must run quarterly scans of all internet-facing systems in scope, plus an additional scan after any significant network change (Requirement 11.3.2.1). A passing result requires no vulnerabilities scoring CVSS 4.0 or higher.
  • PCI SSC approval confirms a vendor's scan solution has passed technical testing. It is not an endorsement of that vendor's pricing, support quality, or ease of use; two approved vendors can deliver very different experiences.
  • Secusy is a PCI SSC-approved scanning vendor built for SaaS and cloud-native businesses, with fast turnaround and direct support through the dispute and remediation process.

If you’ve been told by a payment processor, acquirer, or bank that you need a scan from a “PCI approved scanning vendor”, you’re dealing with a specific, defined requirement, not a generic security checklist item. The scan has to come from a vendor on an official list. It has to happen every three months. And it has to pass, not just complete.

This guide covers what an approved scanning vendor actually is, how a company earns that certification from the PCI SSC, what PCI DSS v4.0.1 requires of your quarterly scans, and how to evaluate vendors once you’ve confirmed they’re qualified.

Key Definitions

Approved Scanning Vendor (ASV): An organization tested and approved by the PCI Security Standards Council to use a certified scan solution to perform external vulnerability scanning services, validating compliance with PCI DSS Requirement 11.3.2.

PCI DSS (Payment Card Industry Data Security Standard): The security standard maintained by the PCI SSC governing how organizations protect cardholder data throughout its lifecycle.

External Vulnerability Scan: An automated, non-intrusive scan of an organization's internet-facing systems and IP addresses to identify weaknesses an external attacker could exploit, mandated under Requirement 11.3.2.

PCI SSC (PCI Security Standards Council): The independent global body, founded by American Express, Discover, JCB, Mastercard, and Visa, that maintains PCI DSS and runs the qualification programmes for ASVs, QSAs, and other payment security service providers.

CVSS (Common Vulnerability Scoring System): The 0–10 severity scale used to score vulnerabilities found in a scan. A passing ASV scan requires no findings at 4.0 or above.

Attestation of Scan Compliance (ASC): The formal document an ASV issues confirming a scan's pass or fail status. This is the deliverable acquirers and QSAs require as evidence of Requirement 11.3.2 compliance.

What Is an Approved Scanning Vendor (ASV)?

An Approved Scanning Vendor is an organization that the PCI Security Standards Council has tested and listed as qualified to perform external vulnerability scanning services that validate compliance with PCI DSS Requirement 11.3.2.

The PCI SSC created the ASV program to solve a specific problem: before it existed, there was no standardised way to confirm that a vulnerability scanning tool was actually capable of detecting what matters for payment security. Any tool could claim to do external scanning. The ASV program changed that by requiring vendors to submit their scan solution for independent testing before being granted approved status.

It’s worth being precise about what that approval does and doesn’t mean. Appearing on the ASV list confirms that a vendor’s scan solution met the PCI SSC’s technical testing requirements. It says nothing about that vendor’s pricing, onboarding experience, support responsiveness, or how easy their platform is to use.

Two vendors can both be fully approved, while one takes two days to turn around a report and answer a dispute, and the other takes two weeks. The approval is the floor, not the deciding factor.

How Does a Vendor Become PCI SSC Approved?

A vendor becomes an ASV by registering with the PCI SSC, agreeing to the ASV Program Guide, passing a live scanning test against the Council's test environment, and undergoing Council evaluation, a process repeated annually to maintain status.

The qualification process has several concrete stages:

  1. Registration: the company registers with the PCI SSC, reviews the ASV Program Guide, and submits administrative and technical documentation.
  2. Simulated client engagement: a PCI SSC representative contacts the vendor to simulate a real client onboarding, testing whether the vendor correctly scopes a scan (IP ranges, domains, and components).
  3. Live scanning test: the vendor runs its actual scan tools against the PCI SSC’s test web perimeter. The results are submitted to the Council for evaluation; this is the real technical bar.
  4. Council evaluation and approval: the Council reviews results, conducts a second simulated engagement, and makes a final determination. Vendors who don’t pass can reapply, up to three attempts, after which a waiting period applies.

 

Approval isn’t permanent. Every ASV on the list goes through annual retesting to keep its qualification current. That’s the detail most comparisons of “top ASV vendors” skip, and it’s exactly why checking the live registry matters more than checking a vendor’s own “PCI certified” badge on their homepage.

The Official PCI SSC Approved Scanning Vendor List and Why You Have to Check It Yourself

The PCI SSC maintains the only authoritative, current list of approved scanning vendors at https://www.pcisecuritystandards.org/assessors_and_solutions/approved_scanning_vendors/. No third-party badge or vendor claim substitutes for checking it directly.

The list changes. Vendors are added when they pass qualification and removed if they fail to maintain it or don’t renew. That means a vendor’s status has to be verified at the time you’re selecting or renewing, not assumed from a past engagement or a logo on their marketing site. A business relying on scan reports from a vendor that’s since been removed from the list can find those reports rejected outright by their acquirer.

The list spans large enterprise security platforms down to vendors built specifically for smaller, leaner environments. That range matters: enterprise ASVs often bundle scanning into broader security suites priced and structured for organizations with dedicated security teams, which is overkill for a business that just needs a clean quarterly scan and a certificate that their processor will accept.

For MSPs and resellers, the list also matters from an accountability standpoint. Partnering with a vendor that holds direct PCI SSC approval, rather than reselling another vendor’s scan capability without disclosing it, keeps the compliance chain clean and gives clients a clearer line of accountability.

ASV Scan Requirements Under PCI DSS v4.0.1 (Requirement 11.3.2)

PCI DSS v4.0.1 Requirement 11.3.2 mandates external vulnerability scans by an ASV at least once every three months on all internet-facing systems in scope, plus an additional scan after any significant change (Requirement 11.3.2.1). A passing result requires no vulnerabilities scored CVSS 4.0 or higher.

PCI DSS 4.0 became the sole active standard, replacing 3.2.1, as of March 31, 2025, which is also when several updated scanning provisions, including authenticated internal scanning, took full effect. For external scanning specifically, the requirement structure is:

  • Frequency: at least every 90 days, plus an out-of-cycle scan after any significant change to the network or in-scope systems (new components, firewall rule changes, new internet-facing infrastructure).
  • Scope: all IP addresses and domains you provide as in-scope, with the ASV required to flag any additional internet-facing components it discovers that weren’t on your original list.
  • Passing threshold: no vulnerabilities with a CVSS score of 4.0 or higher in the final report. Anything in that range blocks a passing result until it’s remediated or successfully disputed.
  • The deliverable: an Attestation of Scan Compliance (ASC), the document your acquirer or QSA actually needs to see. A completed scan with unresolved high-severity findings does not satisfy the requirement, only a passing scan does.

 

One detail worth being direct about: you define the scope, not the ASV. The vendor scans what you tell them is in scope, which is why getting your environment mapped correctly before the first scan matters more than which vendor you pick.

What Are Approved Scanning Vendors Responsible For?

An ASV is responsible for scanning the scope you provide without disrupting your operations, flagging any unlisted internet-facing components it finds, issuing a formal Attestation of Scan Compliance, supporting a false-positive dispute process, and retaining scan documentation for three years.

These obligations come directly from the PCI SSC’s ASV Program Guide, and they matter most when something doesn’t go cleanly:

  • Scans must not intentionally alter or disrupt your environment.
  • The ASV must scan every IP range and domain you provide and separately flag any active component discovered that wasn’t on your list.
  • The ASV issues a clear pass/fail determination and the formal Attestation of Scan Compliance.
  • PCI DSS explicitly recognizes that scans can flag false positives, vulnerabilities that don’t actually apply to your environment, or that are already addressed by a compensating control. The ASV is required to support a dispute process for these, with documentation review and rescanning.
  • Scan reports and supporting documentation must be retained for three years.

 

The dispute process is where vendor quality shows up most. A scan tool flagging something that isn’t exploitable in your specific setup is routine, what separates a good ASV from a frustrating one is how fast and how competently they evaluate your dispute. A slow or under-resourced dispute process turns a non-issue into a missed compliance deadline.

How to Choose the Right Approved Scanning Vendor

Once a vendor is confirmed on the PCI SSC list, the decision comes down to pricing transparency, report clarity, dispute support quality, scan turnaround time, and fit for your infrastructure, since approval alone doesn't differentiate vendors on any of those.

  1. Pricing structure: Some ASVs charge per IP, others per domain, and others a flat annual rate. Per-IP or per-domain pricing gets unpredictable if your environment changes during the year, look for transparent, flat pricing that doesn’t punish growth.
  2. Report quality: Request a sample report before committing. A good one clearly separates pass from fail, explains findings in plain language, and includes the attestation your acquirer needs, without requiring a security specialist to interpret it.
  3. Dispute and remediation support: Ask directly how the vendor handles disputed findings. A vendor that treats disputes as routine, with responsive technical staff, will save you real time over a compliance cycle.
  4. Turnaround time: Some providers quote multi-day turnaround; modern ASV platforms can return results within 24 hours for a clean environment. This matters most when you’re tight against a quarterly deadline.
  5. Infrastructure fit: A vendor built for cloud-native, SaaS, or dynamic-IP environments will scan more accurately than one built around traditional on-premises network assumptions.

 

This is a summary of the decision factors; for a full vendor-by-vendor breakdown of how to weigh these, see our complete how to choose an ASV vendor guide.

What Makes Secusy ASV Different Among ASV Vendors

Secusy ASV is a PCI SSC-approved scanning vendor that was built specifically to make external vulnerability scanning straightforward, affordable, and genuinely supportive for SMBs and the MSP partners who serve them, rather than adapting an enterprise product to fit a smaller market.

The challenge that many SMBs face when navigating the PCI ASV vendor list is that most of the largest vendors on that list designed their platforms for enterprise environments. Their onboarding processes, pricing tiers, and support models assume an IT department with dedicated security personnel, ample budget, and existing familiarity with vulnerability management platforms.

For a business owner who simply needs to meet their quarterly scanning requirement and receive a clean report their payment processor will accept, these platforms create friction rather than solving a problem.

Secusy ASV takes a different approach. The platform is designed so that a business with minimal technical resources can configure its scanning scope, initiate scans, and receive clear, actionable reports without requiring external consultants to interpret results. The onboarding process is guided rather than technical, and the pricing model is transparent; so businesses know exactly what they are paying before they sign up.

For MSP partners, Secusy ASV offers white-label capabilities and a partner programme structure designed around margin and client management at scale. Rather than managing multiple client scanning relationships across different platforms, MSPs can consolidate PCI ASV scanning delivery through a single, PCI SSC-approved platform with partner-level visibility and reporting.

This matters not only for operational efficiency but also for accountability: when a client’s scan report is challenged by an acquirer, MSPs need a support partner they can rely on, not an enterprise help desk with a multi-day response time.

The combination of PCI SSC approval, SMB-focused design, affordable pricing, and genuine support responsiveness is what distinguishes Secusy ASV from both the largest names on the approved scanning vendor list and from scanning tools that are not ASV-approved at all.

Statistics & Citations
  • "PCI DSS 4.0 was released by the PCI Security Standards Council in March 2022 and became the sole active version, replacing PCI DSS 3.2.1 from March 2025." — PCI Security Standards Council, 2022
  • "External vulnerability scanning by an approved scanning vendor is governed by PCI DSS Requirement 11.3.2 under PCI DSS 4.0, which mandates quarterly scans of all internet-facing IP addresses within scope." — PCI Security Standards Council
  • "The PCI SSC ASV programme requires vendors to submit their scan solutions for technical testing before being approved and listed on the official Approved Scanning Vendor list." — PCI Security Standards Council
  • "PCI DSS compliance applies to any organisation that stores, processes, or transmits cardholder data, regardless of size or transaction volume." — PCI Security Standards Council

Navigating the landscape of PCI approved scanning vendors is more consequential than it might initially appear. The approval status of your ASV determines whether your quarterly scan reports will be accepted by acquirers, assessors, and card brands, making it the non-negotiable starting point for any vendor evaluation. But approval is a floor, not a ceiling.

The real decision lies in choosing an ASV partner whose pricing, support, platform design, and understanding of your business environment make compliance achievable rather than burdensome. PCI DSS 4.0 has raised the standard for what compliant scanning looks like, and working with an ASV who keeps pace with that standard and actively supports you through it is the difference between meeting requirements and genuinely managing risk.

For SMBs and the MSPs who support them, the right approved scanning vendor treats compliance as a shared goal rather than a transaction. Secusy ASV was built precisely for that relationship.

Summary

PCI Approved Scanning Vendors (ASVs) are organisations vetted and listed by the PCI Security Standards Council to conduct external vulnerability scans required under PCI DSS Requirement 11.3.2. Businesses that store, process, or transmit cardholder data must complete quarterly external scans using a vendor on the current PCI SSC ASV list to maintain compliance. Under PCI DSS 4.0, passing scans, not merely completed scans, are required, and the right ASV partner should offer transparent pricing, clear reporting, and active support through dispute resolution. Secusy ASV provides PCI SSC-approved scanning designed specifically for SMBs and MSP partners.

Ready to meet your PCI DSS scanning requirement with a vendor who makes it straightforward?

Start your first scan with SecureASV today — PCI SSC approved, SMB-friendly pricing, and real support when you need it. Visit Secusy ASV.com to get started or speak with our team about MSP partner opportunities.

Frequently Asked Questions

ASV stands for Approved Scanning Vendor, an organization certified by the PCI Security Standards Council to perform the external vulnerability scans required under PCI DSS Requirement 11.3.2. The term refers specifically to the certified vendor, not to the scanning tool or software itself.

PCI DSS Requirement 11.3.2 requires an ASV scan at least once every three months. An additional scan is required after any significant change to your network or in-scope systems, such as new infrastructure, firewall rule changes, or new internet-facing components, under Requirement 11.3.2.1.

A failed scan means at least one vulnerability scored 4.0 or higher on the CVSS scale was found. You remediate the issue and request a rescan from your ASV before the compliance deadline passes. A completed scan with unresolved high-severity findings doesn't satisfy Requirement 11.3.2, only a passing result does.

ASV scan pricing typically ranges from around $80 a year for small environments to $500 or more for enterprise-scale scanning, depending on the number of IPs in scope and whether rescans and dispute support are included in the base price or billed separately.

The ASV Program Guide is the PCI SSC's governing document covering how the ASV certification program works, vendor registration, testing requirements, scan report formatting, and the ongoing obligations vendors must meet to stay on the approved list. It's the document every certified ASV has to comply with.

Yes. Every ASV on the PCI SSC list goes through annual retesting to keep its qualification current. A vendor that passed certification in a previous year isn't automatically still approved, status has to be verified against the live list.

Any merchant or service provider that stores, processes, or transmits cardholder data and has internet-facing systems in scope for PCI DSS needs quarterly ASV scanning. This includes most e-commerce merchants and SaaS businesses handling card payments, including SAQ A merchants whose checkout redirects to or embeds a third-party payment form.

Authored by

Binoy Koonammavu blog image

Binoy Koonammavu, is the Founder and CEO of Secusy ASV, where he helps SMBs and fintech companies meet PCI DSS scanning requirements without the complexity of enterprise-grade tools. His writing focuses on making ASV compliance straightforward for growing businesses.

Share:

Related Post

 
Learn what PCI approved scanning vendors are, how the PCI SSC certifies them, and how to choose the right ASV for quarterly scans under PCI DSS v4.0.1.

Discover more from Secusy ASV

Subscribe now to keep reading and get access to the full archive.

Continue reading