Comments on: PABP != PCI Compliance http://www.paymentsystemsblog.com/2008/02/02/pabp-pci-compliance/ David D. Bergert Sun, 29 Aug 2010 15:07:24 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Heartland Payment Systems Breach - My Thoughts | Payment Systems Blog http://www.paymentsystemsblog.com/2008/02/02/pabp-pci-compliance/comment-page-1/#comment-846 Heartland Payment Systems Breach - My Thoughts | Payment Systems Blog Wed, 21 Jan 2009 15:11:01 +0000 http://www.paymentsystemsblog.com/?p=6#comment-846 [...] 30th, 2008) If they were PCI compliant how did a breach occur ? It is important to note (again, and again) that Compliance != Security. Compliance is a snapshot in time, PCI is not based on an [...] [...] 30th, 2008) If they were PCI compliant how did a breach occur ? It is important to note (again, and again) that Compliance != Security. Compliance is a snapshot in time, PCI is not based on an [...]

]]> By: Mike http://www.paymentsystemsblog.com/2008/02/02/pabp-pci-compliance/comment-page-1/#comment-585 Mike Wed, 01 Oct 2008 19:25:41 +0000 http://www.paymentsystemsblog.com/?p=6#comment-585 Thank you for the link. It's important to remember that PABP (now the PA-DSS) is meant to 'enable' compliance but not act as magic pixie dust to bring compliance for all. That being said, using compliant payment applications can and will have a large impact on the security of Level 3 and 4 merchants. Thank you for the link. It’s important to remember that PABP (now the PA-DSS) is meant to ‘enable’ compliance but not act as magic pixie dust to bring compliance for all.

That being said, using compliant payment applications can and will have a large impact on the security of Level 3 and 4 merchants.

]]>