{"id":1696,"date":"2008-04-17T00:00:00","date_gmt":"2008-04-17T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2008\/04\/17\/pci-security-standards-council-issues-payment-application-data-security-standard\/"},"modified":"2021-12-30T11:39:49","modified_gmt":"2021-12-30T11:39:49","slug":"pci-security-standards-council-issues-payment-application-data-security-standard","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2008\/04\/17\/pci-security-standards-council-issues-payment-application-data-security-standard\/","title":{"rendered":"PCI Security Standards Council issues Payment Application Data Security Standard"},"content":{"rendered":"<p>The PCI Security Standards Council, a global, open industry standards body providing management of the Payment Card Industry Data Security Standard (DSS), PCI PIN Entry Device (PED) Security Requirements and the Payment Application Data Security Standard (PA-DSS), announced at the Electronic Transactions Association Annual Meeting and Expo the release of version 1.1 of the Payment Application Data Security Standard (PA-DSS).  Following release of the PA-DSS, this fall the Council will also roll out a program to include maintenance of a list of validated payment applications.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Companies that are approved as PA-QSAs will be recognized in a Council maintained and published list and can begin conducting PA-DSS assessments in accordance with the PA-DSS Security Audit Procedures.<\/p>\n<p>All companies that were previously recognized as PA-QSAs under Visa PABP will need to enroll and re-validate as a Council PA-QSA.<\/p>\n<p>http:\/\/www.net-security.org\/secworld.php?id=6025<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12],"tags":[],"class_list":["post-1696","post","type-post","status-publish","format-standard","hentry","category-regulations"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1696","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=1696"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1696\/revisions"}],"predecessor-version":[{"id":4183,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1696\/revisions\/4183"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1696"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1696"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1696"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}