Skip to main content
PCI Report

Learn all about the PCI compliance Vulnerability Management report

Updated over a week ago

About the PCI Compliance Vulnerability Management Report

The PCI compliance Vulnerability Management report helps you audit the Payment Card Industry Data Security Standard (PCI) and understand your PCI compliance status per a Business Group or more.


  • Select Business Groups to view in the PCI report;

  • Audit the Payment Card Industry data security standard;

  • Understand Vulnerability Management PCI compliance status such as, "30 days window to patch assets with high and critical vulnerabilities."

  1. Go to Analytics > PCI Compliance Vulnerability Management Report

  2. Select the Business Groups that interest you most

  3. Click the Open PCI Report button to view the results.

PCI controls and processes in the report

The "PCI Security Controls and Processes" requires companies to “maintain a Vulnerability Management Program” and an “Information Security Policy”.
The PCI controls and processes this report will help you follow are 6.1, 6.2, 6.3, 6.5, 6.6,11.2, and 12.2.

PCI Control and Process



Establish a process to identify security vulnerabilities using reputable outside sources, and assign a risk ranking (e.g. “high,” “medium,” or “low”) to newly discovered security vulnerabilities.


Protect all system components and software from known vulnerabilities by installing applicable vendor-supplied security patches. Install critical security patches within one month of release.


Develop internal and external software applications including web-based administrative access to applications in accordance with PCI DSS and based on industry best practices. Incorporate information security throughout the software development life cycle. This applies to all software developed internally as well as bespoke or custom software developed by a third party.


Follow change control processes and procedures for all changes to system components. Ensure all 18 relevant PCI DSS requirements are implemented on new or changed systems and networks after significant changes.


Prevent common coding vulnerabilities in software development processes by training developers in secure coding techniques and developing applications based on secure coding guidelines – including how sensitive data is handled in memory.


Ensure all public-facing web applications are protected against known attacks, either by performing application vulnerability assessment at least annually and after any changes, or by installing an automated technical solution that detects and prevents web-based attacks (for example, a web-application firewall) in front of public-facing web applications, to continually check all traffic.


Ensure that related security policies and operational procedures are documented, in use, and known to all affected parties.


Run internal and external network vulnerability scans at least quarterly and after any significant change in the network. Address vulnerabilities and perform rescans as needed, until passing scans are achieved. After passing a scan for initial PCI DSS compliance, an entity must, in subsequent years, complete four consecutive quarters of passing scans. Quarterly external scans must be performed by an Approved Scanning Vendor (ASV). Scans conducted after network changes and internal scans may be performed by internal staff.


Implement a risk assessment process that is performed at least annually and upon significant changes to the environment that identifies critical assets, threats, and vulnerabilities, and results in a formal assessment

Analytics FAQ and Data Validation

Read our Analytics FAQ and Data Validation article here.

Did this answer your question?