PCI DSS Compliance Report

The PCI Compliance Report helps your organization to meet the Payment Card Industry Data Security Standard (PCI DSS).

• Major card schemes established the PCI DSS this set of security standards in 2004 and they’re updated regularly. If your organization relies on payment by credit and/or debit cards, you are strictly expected to abide by these rules. With Invicti’s PCI DSS Compliance Report, you can easily view which vulnerabilities and issues infringe the standard.
• As the PCI DSS Report includes all technical details, it mainly addresses the needs of developers and IT personnel. The report primarily presents a summary of the overall security posture.

In order to be able to generate an approved PCI DSS Report in Invicti Enterprise, you must first run a PCI DSS Scan.
You can configure Invicti Standard to perform a PCI DSS Scan, but its report does not constitute an official report.
A normal scan in Invicti Enterprise and Invicti Standard  presents only an unofficial PCI DSS Report.
For further information, see PCI Scanning in Invicti.

There can be other vulnerabilities and security issues found in your web applications but not listed in the PCI DSS Compliance Report.

Click to view a sample PCI Compliance Report.

PCI DSS Compliance Report Sections

There are four sections in the PCI DSS Compliance Report:

• Scan Details
• Vulnerabilities
• Vulnerability Names and Details
• Show/Hide Scan Details

Scan Metadata

This section provides details on the following items:

• Scan Target
• Scan Time
• Scan Duration
• Description
• Total Requests
• Average Speed
• Risk Level

For further information, see Progress, and Scan Duration and Speed.

Vulnerabilities

This provides a numerical and graphical overview of:

• Numbers                        The numbers of issues detected at various Vulnerability Severity Levels
• Identified Vulnerabilities        The total number of detected vulnerabilities
• Confirmed Vulnerabilities        The total number of vulnerabilities that Invicti verified by taking extra steps such as extracting some data from the target

Vulnerability Summary

This section provides a summary of information about each discovered vulnerability and categorizes them based on severity. For example, if Invicti determines a vulnerability as Critical, it requires immediate attention.

If you click on an identified vulnerability, you access detailed information, such as HTTP request and response codes and body, about the vulnerability and, if any, Proof of Exploit. If Invicti finds a vulnerability but has no proof of exploit, Invicti presents a certainty degree about this issue.

This table lists and explains the columns in the Vulnerability Summary.

For further information, see Vulnerability Severity Levels.

Vulnerability Names and Details

This section describes all identified issues and vulnerabilities, along with their Impact and Proof of Exploit. It also explains what Actions to Take and a Remedy for each one, including External References for more information.

This table lists and explains the headings in the Vulnerability Names and Details section.

Headings	Description
Name	This is the name of the identified issue
Tag	This is the label to group, organize, and filter issues in the target web application.
Proof of Exploit	This is a piece of evidence supplied to prove that vulnerability exists, showing information that is extracted from the target using the vulnerability. For further information, see Benefits of Proof-Based Scanning™ Technology.
Vulnerability Details	This displays further details about the vulnerability.
Certainty value	This indicates how much Invicti is sure about the identified issue
Impact	This shows the effect of issue or vulnerability on the Target URL.
Required Skills for Successful Exploitation	This gives details on how malicious hackers could exploit this issue.
Actions to Take	These are the immediate steps you can take to decrease the impact or prevent exploitation.
Remedy	This offers further steps to resolve the identified issue.
External references	This provides links to other websites where you can find more information.
Classification	PCI DSS 3.2: This provides further information to help you comply with the Payment Card Industry Data Saving Standard (PCI DSS) requirements.
Proof of Concept Notes	These notes demonstrate in principle how a system may be compromised.
Remedy References	This provides further information on the solution of identified issues.
HTTP Request	This is the whole HTTP request that Invicti sent to detect the issue.
HTTP Response	This is the reply from the system against the payload.

Show/Hide Scan Details

This section provides some profile and policy settings that Invicti uses to adjust its scanning to achieve a better scan coverage. For example, it lists all enabled security checks.

It provides information on your preference in selecting this scan so that developers have more details on how the scan was run.

How to generate a PCI DSS Compliance Report in Invicti Enterprise

1. Log in to Invicti Enterprise.
2. From the main menu, select Scans > Recent Scans.
3. Next to the relevant scan, select Report.
4. On the Scan Summary page, select Export.

5. From the Report drop-down, select PCI DSS Compliance.

6. From the Format drop-down, select an option.
7. If required, select one of the following to configure your report:

• Exclude Addressed Issues excludes those issues on which you’ve already taken action. (All Information level findings are marked as Accepted Risk automatically by default. To change this behavior, see Do not mark Information issues as accepted risks in General Settings).
• Exclude History of Issues excludes the issue history from the report. If unselected, only the last 10 history items appear in the report. For further information, see Viewing Issues in Invicti Enterprise.
• Export Confirmed includes only those issues that are confirmed.
• Export Unconfirmed includes only those issues that are unconfirmed.

8. Select Export.

You can view the report in the saved location.

How to generate a PCI DSS Compliance Report in Invicti Standard

1. Open Invicti Standard.
2. From the ribbon, select the File tab. Local Scans are displayed. Double-click the relevant scan to display its results.
3. From the Reporting tab, click the PCI DSS Compliance Report. The Save Report As dialog box is displayed.

4. Select a save location, then Save.
5. The Export Report dialog is also displayed at this point, with the Path field already populated from the previous dialog.

6. From this dialog, you can decide on:

• Policy: Select the default report policy or customized report policy (see Custom Report Policies).
• Format: Select HTML and/or PDF format.
• Vulnerability Options (select one or all):

• Export Confirmed: When selected, the report will include confirmed vulnerabilities.
• Export Unconfirmed: When selected, the report will also include unconfirmed vulnerabilities.
• Export All Variations: Variations mean that if Invicti identified some passive or Information level issues in more than one page, it does not show all these variations. However, users can change this by enabling or disabling this option.
• Header and Footer:

• Enter relevant information that will appear in the header and footer section of the report.
• Open Generated Report: When selected, your report(s) is generated when you select Save.

7. Select Save.

The HTML Report format is interactive thanks to the Severity Filter. For example, if you prefer not to see Best Practice or Information details, you can deselect them. When you click on the plus sign under Vulnerabilities, you can access more information on the issue. Also, you can Hide or Show Remediation.