About the PCI Report

The PCI Report helps you audit the Payment Card Industry Data Security Standard (PCI) and understand your PCI compliance status across PCI-relevant Business Groups. To work with the PCI report, you must first create dedicated PCI-relevant Business Groups that contain PCI assets.

Use the Filters pane on the right to focus your report. Click on a specific data element to filter the entire report or to access more data, and hover over a widget for more actions and information.

Before you dive in

First, ensure you cover the Reports (Analytics) Filters and Data Drilling to learn about the expected behavior of the trends and the presented data.

Widgets and trends

Findings (Instances) over time

Count of all PCI-related findings (instances) in your PCI Business Groups over time. Data-drill-down buttons allow deeper views into the data. To utilize this report and gain PCI-focused insight, make sure the report is filtered to present data on PCI-relevant Business Groups only.

Findings (Instances) by Risk Level

Count of all PCI-related findings (instances) in your PCI Business Groups, by Risk Level (None, Low, Medium, High, and Critical). To utilize this report and gain PCI-focused insight, make sure the report is filtered to present data on PCI-relevant Business Groups only.

Findings (Instances) Age by Risk Level

Count of all PCI-related findings (instances) in your PCI Business Groups, by vulnerability age range. The age start-count day is the First Seen date of a finding (instance).

Findings (Instances) by Risk Level over time

Count of all PCI-related findings (instances) in your PCI Business Groups over time, by Risk Level. Data-drill-down buttons allow deeper views into the data. To utilize this report and gain PCI-focused insight, make sure the report is filtered to present data on PCI-relevant Business Groups only.

Findings (Instances) Exceeding SLA by Risk Level over time

Count of all SLA Non-Compliant (Exceeding SLA Policy) PCI-related findings (instances) in your PCI Business Groups over time, by Risk Level. Data-drill-down buttons allow deeper views into the data. To utilize this report and gain PCI-focused insight, make sure the report is filtered to present data on PCI-relevant Business Groups only.

Findings (Instances) Compliant with SLA by Risk Level over time

Count of all SLA-Compliant PCI-related findings (instances) in your PCI Business Groups over time, by Risk Level. Data-drill-down buttons allow deeper views into the data. To utilize this report and gain PCI-focused insight, make sure the report is filtered to present data on PCI-relevant Business Groups only.

Unscanned Assets over time

Count and percentage of all unscanned PCI-related assets in your PCI Business Groups, over time. Aim to lower the stats of unscanned PCI-related assets. Data-drill-down buttons allow deeper views into the data. To utilize this report and gain PCI-focused insight, make sure the report is filtered to present data on PCI-relevant Business Groups only.

Findings (Instances) by Exception Type

Count of all PCI-related findings (instances) in your PCI Business Groups over time, by Exception type. Learn how many PCI-related findings (instances) are currently in Exception Requests, and the type of Exception Request. To utilize this report and gain PCI-focused insight, make sure the report is filtered to present data on PCI-relevant Business Groups only.

Findings (Instances) by OWASP Top 10

Count of all PCI-related findings (instances) in your PCI Business Groups over time, by OWASP Top 10. OWSP top 10 is a standard awareness document for developers and web application security citing the most critical security risks to web applications. Learn how many of your PCI-related findings (instances) are in OWASP categories.

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	Description
6.1	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.
6.2	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.
6.3	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.
6.4	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.
6.5	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.
6.6	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.
6.7	Ensure that related security policies and operational procedures are documented, in use, and known to all affected parties.
11.2	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.
12.2	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

Sources:
https://www.pcisecuritystandards.org
https://listings.pcisecuritystandards.org/documents/PCI_DSS-QRG-v3_2_1.pdf