Frequently Asked Question
How does Triple DEA (TDEA) impact ASV Scan results?
Triple DEA (Data Encryption Algorithm)'also referred to as TDEA, TDES or 3DES'is a cryptographic cipher used in TLS, SSH, IPSec and other protocols and products. TDEA is susceptible to a known vulnerability that is currently ranked as Medium severity by the Common Vulnerability Scoring System (CVSS). As defined in PCI DSS Requirement 11.2.2, vulnerabilities ranked as Medium or High risk by the CVSS must be corrected and the affected systems re-scanned after the corrections to show the issue has been addressed.
ASVs are permitted to re-rank a vulnerability's risk assignment if they disagree with the CVSS (see ASV Program Guide section 6.3.3 'Exceptions to Scoring Vulnerabilities with the NVD'), or if they are able to confirm that the risk level is lower in a particular environment. When making this type of adjustment to the scan report, the ASV should consider the scan customer's unique environment, systems, and controls, and not make adjustments based on general trends or assumptions.
Scan customers are also permitted to dispute the scan findings if they determine a vulnerability was incorrectly reported or if compensating controls or environment-specific factors exist that reduce or eliminate the risk. Refer to ASV Program Guide sections 7.7 "Managing False Positives and Other Disputes" and 7.8 "Addressing Vulnerabilities with Compensating Controls" for details. In all cases, scan customers and ASVs should work together to determine the level of risk that a particular vulnerability may present in a specific environment or configuration.
TDEA has been superseded by the Advanced Encryption Algorithm (AES). Entities using TDEA are encouraged to review their implementations to determine the potential risk that TDEA may present to their environments, and consider transitioning toward a more secure alternative.
ASVs are permitted to re-rank a vulnerability's risk assignment if they disagree with the CVSS (see ASV Program Guide section 6.3.3 'Exceptions to Scoring Vulnerabilities with the NVD'), or if they are able to confirm that the risk level is lower in a particular environment. When making this type of adjustment to the scan report, the ASV should consider the scan customer's unique environment, systems, and controls, and not make adjustments based on general trends or assumptions.
Scan customers are also permitted to dispute the scan findings if they determine a vulnerability was incorrectly reported or if compensating controls or environment-specific factors exist that reduce or eliminate the risk. Refer to ASV Program Guide sections 7.7 "Managing False Positives and Other Disputes" and 7.8 "Addressing Vulnerabilities with Compensating Controls" for details. In all cases, scan customers and ASVs should work together to determine the level of risk that a particular vulnerability may present in a specific environment or configuration.
TDEA has been superseded by the Advanced Encryption Algorithm (AES). Entities using TDEA are encouraged to review their implementations to determine the potential risk that TDEA may present to their environments, and consider transitioning toward a more secure alternative.
Originally published: September 2017
Article Number: 1452
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?