PA-DSS

The Payment Application Data Security Standard (PA-DSS), formerly referred to as the Payment Application Best Practices (PABP), is the global security standard created by the Payment Card Industry Security Standards Council (PCI SSC).[1] PA-DSS was implemented in an effort to provide the definitive data standard for software vendors that develop payment applications. The standard aims to prevent developed payment applications for third parties from storing prohibited secure data including magnetic stripe, CVV2, or PIN. In that process, the standard also dictates that software vendors develop payment applications that are compliant with the Payment Card Industry Data Security Standards (PCI DSS).

Requirements

For a payment application to be deemed PA-DSS compliant, software vendors must ensure that their software includes the following fourteen protections:[2]

  1. Do not retain full magnetic stripe, card validation code or value, or PIN block data.
  2. Protect stored cardholder data.
  3. Provide secure authentication features.
  4. Log payment application activity.
  5. Develop secure payment applications.
  6. Protect wireless transmissions.
  7. Test payment applications to address vulnerabilities and maintain payment application updates.
  8. Facilitate secure network implementation.
  9. Cardholder data must never be stored on a server connected to The Internet.
  10. Facilitate secure remote access to payment application.
  11. Encrypt sensitive traffic over public networks.
  12. Encrypt all non-console administrative access.
  13. Maintain a PA-DSS Implementation Guide for customers, resellers, and integrators.
  14. Assign PA-DSS responsibilities for personnel, and maintain training programs for personnel, customers, resellers, and integrators.

Governance and enforcement

PCI SSC has compiled a list of payment applications that have been validated as PA-DSS compliant, with the list updated to reflect compliant payment applications as they are developed. Creation and enforcement of these standards currently rests with PCI SSC via Payment Application-Qualified Security Assessors (PA-QSA). PA-QSAs conduct payment application reviews that help software vendors ensure that applications are compliant with PCI standards.

History

Governed originally by Visa Inc., under the PABP moniker, PA-DSS was launched on April 15, 2008 and updated on October 15, 2008. PA-DSS then became retroactively distinguished as "version 1.1"[3] and "version 1.2".[4]

In October 2009, PA-DSS v1.2.1 was released with three noted changes:[2]

  1. Under “Scope of PA-DSS,” align content with the PA-DSS Program Guide, v1.2.1, to clarify applications to which PA-DSS applies.
  2. Under Laboratory Requirement 6, corrected spelling of “OWASP.”
  3. In the Attestation of Validation, Part 2a, update “Payment Application Functionality” to be consistent with the application types listed in the PA-DSS Program Guide, and clarify annual re-validation procedures in Part 3b.

In October 2010, PA-DSS 2.0 was released, indicating:[2] Update and implement minor changes from v1.2.1 and align with new PCI DSS v2.0. For details, please see PA-DSS – Summary of Changes from PA-DSS Version 1.2.1 to 2.0.

In November 2013, PA-DSS 3.0 was released, indicating:[2] Update from PA-DSS v2. For details of changes, please see PA-DSS – Summary of Changes from PA-DSS Version 2.0 to 3.0.[5]

In May 2015, PA-DSS 3.1 was released, indicating:[2] Update from PA-DSS v3.0. See PA-DSS – Summary of Changes from PA-DSS Version 3.0 to 3.1 for details of changes.[6]

Congressional attention

On March 31, 2009, the United States House of Representatives’ Committee on Homeland Security convened to discuss the current PCI DSS requirements.[7] Representatives such as Yvette Clark (D-NY) expressed interest in increasing the strength of standards while others, such as Bennie Thompson (D-Miss.) expressed doubt that industry created standards would be sufficient in the future.[8] While Congressional attention was focused largely on PCI DSS, the criticism of card-issuer standards could eventually bring Congressional or legal focus on PA-DSS and on PCI SSC as an entity.

Future

The future of these standards is somewhat vague, with Congressional attention giving rise to the possibility of governmental intervention. Regardless, meeting standards can prove expensive and time consuming for software vendors, with the current expense of PA-DSS certification outpacing other methods of compliance.[9] Given the cost of compliance and certification, current or yet-undetermined alternatives could emerge in the PCI standards compliance market. Visa USA announced a more aggressive push into such technology (chip and pin) in August 2011.[10]

Supplemental information

The PCI SSC has published additional materials that further clarify PA-DSS, including the following:

References

  1. ↑ PCI Security Standards Council
  2. 1 2 3 4 5 "Requirements and Security Assessment Procedures Version 3.1" (PDF). Retrieved 27 January 2016.
  3. ↑ "Payment Application Data Security Standard (PA-DSS) V1.1". PCI Security Standards Council. Archived from the original on 2010-08-02.
  4. ↑ "Payment Application Data Security Standard (PA-DSS) V1.2". PCI Security Standards Council. Archived from the original on 2010-08-02.
  5. ↑ Summary of Changes from PA-DSS Version 2.0 to 3.0
  6. 1 2 Summary of Changes from PA-DSS Version 3.0 to 3.1
  7. ↑ "Do the Payment Card Industry Data Standards Reduce Cybercrime?". U.S. House Homeland Security Committee. March 31, 2009. Archived from the original on 2009-12-02.
  8. ↑ Visa, MasterCard In Security Hotseat
  9. ↑ PA-DSS Certification Vs. Hosted Payments
  10. ↑ "Visa Announces Plans to Accelerate Chip Migration and Adoption of Mobile Payments" (Press release). Visa. August 9, 2011. Archived from the original on 2011-09-23.
  11. ↑ PA-DSS Requirements and Security Assessment Procedures v1.2.1
  12. ↑ PA-DSS Requirements and Security Assessment Procedures v2.0
  13. ↑ PA-DSS Requirements and Security Assessment Procedures v3
  14. ↑ Summary of PA-DSS Changes
  15. ↑ QSA Program Guide
This article is issued from Wikipedia - version of the 9/12/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.