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 Acunetix 360'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 Acunetix 360, you must first run a PCI DSS Scan.
A normal scan in Acunetix 360 presents only an unofficial PCI DSS Report.
For further information, see PCI Scanning in Acunetix 360.
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 DSS Compliance Report.
PCI DSS Compliance Report Sections
There are four sections in the PCI DSS Compliance Report:
- Scan Metadata
- Scan Overview
- Vulnerability Summary
- Vulnerability Names and Details
- Show/Hide Scan Details
This section provides details on the following items:
- Scan Target
- Scan Time
- Scan Duration
- Total Requests
- Average Speed
- Risk Level
For further information, see Progress, and Scan Duration and Speed.
This provides a numerical and graphic 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 Acunetix 360 verified by taking extra steps such as extracting some data from the target
This section provides a summary of information about each discovered vulnerability and categorizes them based on severity. For example, if Acunetix 360 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 Acunetix 360 finds a vulnerability but has no proof of exploit, Acunetix 360 presents a certainty degree about this issue.
This table lists and explains the columns in the Vulnerability Summary.
This shows whether Acunetix 360 has verified a vulnerability.
This displays the name of the issue and provides a link to a detected issue that attackers can exploit.
This is the HTTP method of the request in which Acunetix 360 sent the payload. It demonstrates what Acunetix 360 deployed in order to identify an issue.
This is a reference to a resource that contains the issue.
This is the vulnerability severity of the issue.
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.
This is the name of the identified issue
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 What is Acunetix 360?.
This displays further details about the vulnerability.
This indicates how much Acunetix 360 is sure about the identified issue.
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.
This offers further steps to resolve the identified issue.
This provides links to other websites where you can find more information.
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.
This provides further information on the solution of identified issues.
This is the whole HTTP request that Acunetix 360 sent to detect the issue.
This is the reply from the system against the payload.
Show Scan Detail
This section provides some profile and policy settings that Acunetix 360 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.
For further information, see Security Checks.
How to Generate a PCI DSS Compliance Report in Acunetix 360
- Log in to Acunetix 360.
- From the main menu, click Scans, then Recent Scans. The Recent Scans window is displayed.
- Next to the relevant scan, click Report. The Scan Summary window is displayed.
- Click Export. The Export Report dialog is displayed.
- From the Report dropdown, select PCI DSS Compliance.
- From the Format dropdown, select an option.
- 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).
- Only Confirmed Issues includes only those issues that are confirmed.
- Click Export. You can view the report in the Save location.