Frequently Asked Question
I have had an external vulnerability scan completed by an ASV - does this mean I am PCI DSS compliant?
PCI DSS Requirement 11.2.2 addresses the need for quarterly external vulnerability scans to be performed by a PCI SSC Approved Scanning Vendor (ASV). The ASV will produce a scan report that details the results of the vulnerability scan — this scan report is not an indication that any other PCI DSS requirements have been reviewed or are in place.
ASVs are required to provide scan reports on official templates as defined in the ASV Program Guide. Any additional documentation provided by the ASV (for example, certificates, letters or other documentation) should be clearly identified as supplemental materials provided by the ASV Company - these supplemental materials have not been endorsed by the PCI SSC, nor should they be considered replacements for the official PCI SSC templates and forms which have been approved by the payment brands.
In addition to being a PCI DSS requirement, quarterly ASV scan reports may be requested by acquirers and/or the payment brands as part of an entity's periodic compliance reporting. Organizations should consult with their acquirer or the payment brands directly, as applicable, to understand their compliance reporting obligations.
Featured FAQ Articles
Featured
-
Do PCI DSS requirements for keyed cryptographic hashing apply to previously hashed PANs?
-
Is the PCI DSS Attestation of Compliance intended to be shared?
-
How does an entity report the results of a PCI DSS assessment for new requirements that are noted in PCI DSS as best practices until a future date?
-
Where do I direct questions about complying with PCI standards?
-
Can SAQ eligibility criteria be used for determining applicability of PCI DSS requirements for assessments documented in a Report on Compliance?
Most Popular
-
What does “console access” mean for PCI DSS Requirements 8.4.1 and 8.4.2?
-
What evidence is a TPSP expected to provide to customers to demonstrate PCI DSS compliance?
-
Does PCI SSC consider guidance from other standards organizations when making updates to PCI standards?
-
If an organization provides software or functionality that runs on a consumer's device (for example, smartphones, tablets, or laptops) and is used to accept payment account data, can the organization store card verification codes for those consumers?
-
Do PCI DSS requirements for keyed cryptographic hashing apply to previously hashed PANs?
Most Recently Updated
-
Which version of the P2PE Standard should be used for a P2PE assessment?
-
Which PCI PTS point-of-interaction (POI) devices can be used in a validated P2PE solution?
-
Is a "P2PE Assessor" required for a merchant's PCI DSS assessment if the merchant uses a Council-listed P2PE solution?
-
Can a QSA that is not also a P2PE Assessor validate an encryption solution meets P2PE Requirements?
-
How do PCI PTS-approved HSM expiry dates affect a PCI-listed P2PE Solution or Component?