The calculation of the PCI pass/fail compliance status in PCI reports follows the PCI compliance standards set by the PCI Security Standards Council.
For each vulnerability, the PCI compliance service uses the CVSS version 2.0 base score provided by NIST to determine whether the vulnerability must be fixed to pass PCI compliance requirements. When a CVSS version 2.0 score is not available from NIST, the service provides a CVSS 2.0 score and uses that score to determine whether the vulnerability must be fixed.
The CVSS version 2.0 score is mapped to a PCI severity level for each vulnerability according to the requirements from the PCI Security Standards Council.
Important: The service uses the PCI severity level and other criteria, as defined by the PCI Security Standards Council, to determine whether a detected vulnerability passes or fails the PCI compliance requirements. Please note that the PCI severity level, based on CVSS score, is not the only criteria used to calculate a vulnerability's pass/fail status. A vulnerability may pass or fail PCI compliance based on the type of exploit. For example, a denial of service vulnerability will pass PCI compliance regardless of its CVSS score.
A PCI severity level of High, Medium or Low, which is based on the CVSS score, is assigned to the vulnerability. This easy-to-understand ranking should assist you when prioritizing remediation tasks.
See the table below for PCI severity levels based on CVSS scores.
cvss score |
Confirmed severity |
Potential Severity |
Compliance |
guidance |
7.0 through 10.0 |
Fail |
These vulnerabilities must be fixed to pass PCI compliance. Organizations should take a risk-based approach to correct these types of vulnerabilities, starting with the most critical ones (rated 10.0, followed by those rated 9, 8, 7, etc., until all vulnerabilities rated 4.0 through 10.0 are corrected. |
||
4.0 through 6.9 |
Fail |
|||
0.0 through 3.9 |
Pass |
These vulnerabilities are not required to be fixed to pass PCI compliance. Organizations are encouraged, however, to correct these vulnerabilities. |
Payment Card Industry (PCI) Compliance