Frequently Asked Question
How did Prioritized Approach Tool calculations change for PCI DSS v3.2?
As an example: If a Milestone contains 10 PCI DSS requirements, and an entity identifies 5 requirements as 'N/A', 3 requirements a "No" (not in place), and 2 requirements as "Yes" (in place), the resulting calculation would be:
- For v3.1 of the Prioritized Approach: The calculation considered 7 requirements (the sum of "N/A" and "Yes" responses) as "in place" out of the total 10 requirements, resulting in a score of 70% for that milestone.
- For v3.2 of the Prioritized Approach: Because the 5 "N/A" responses are excluded from the calculation, there will be 2 requirements ('Yes' responses) identified as "in place" out of the 5 applicable requirements, resulting in a score of 40% for that milestone.
This example calculation is also summarized in the following table:
| Total Requirements | Requirements identified as 'N/A' | Requirements included in calculation | In place | Not in place | Milestone score |
PCI DSS v3.1 | 10 | 5 | 10 | 2 | 3 | 70% |
PCI DSS v3.2 | 10 | 5 | 5 | 2 | 3 | 40% |
While this change simplifies and improves accuracy of the calculation process, the result is that a non-compliant merchant may appear to show a "drop" in compliance when using the Prioritized Approach Tool for PCI DSS v3.2 when compared to their report for PCI DSS 3.1 (or earlier), even if they report the same requirements as being in place, not in place, and not applicable. Organizations and their compliance reporting entities will need to take this into consideration when comparing results from the Prioritized Approach v3.2 to results from previous versions.
Entities that are able to report all applicable PCI DSS controls as being in place will achieve an Overall result of 100%.
Related
-
What evidence is a TPSP expected to provide to customers to demonstrate PCI DSS compliance?
-
Does PCI SSC consider guidance from other standards organizations when making updates to PCI standards?
-
If an organization provides software or functionality that runs on a consumer's device (for example, smartphones, tablets, or laptops) and is used to accept payment account data, can the organization store card verification codes for those consumers?
Featured FAQ Articles
Featured
-
Do PCI DSS requirements for keyed cryptographic hashing apply to previously hashed PANs?
-
Is the PCI DSS Attestation of Compliance intended to be shared?
-
How does an entity report the results of a PCI DSS assessment for new requirements that are noted in PCI DSS as best practices until a future date?
-
Where do I direct questions about complying with PCI standards?
-
Can SAQ eligibility criteria be used for determining applicability of PCI DSS requirements for assessments documented in a Report on Compliance?
Most Popular
-
What evidence is a TPSP expected to provide to customers to demonstrate PCI DSS compliance?
-
Does PCI SSC consider guidance from other standards organizations when making updates to PCI standards?
-
If an organization provides software or functionality that runs on a consumer's device (for example, smartphones, tablets, or laptops) and is used to accept payment account data, can the organization store card verification codes for those consumers?
-
Do PCI DSS requirements for keyed cryptographic hashing apply to previously hashed PANs?
-
Can a compensating control be used for requirements with a periodic or defined frequency, where an entity did not perform the activity within the required timeframe?
Most Recently Updated
-
How does encrypted cardholder data impact PCI DSS scope for third-party service providers?
-
Does PCI SSC provide a list of PCI DSS-compliant third-party service providers?
-
How does encrypted cardholder data impact PCI DSS scope?
-
What effect does the use of a PCI-listed P2PE solution have on a merchant's PCI DSS validation?
-
Are Mobile Payments on COTS (MPoC)™ solutions, Software-based PIN Entry on COTS (SPoC)™ solutions, or Contactless Payments on COTS (CPoC™) solutions eligible for a P2PE Solution approval?