When it comes to doubters of the PCI data security standard, A. Bryan Sartin of Cybertrust says one statistic speaks for itself: No organization that has been completely compliant with PCI has been compromised. Sartin, a computer forensic investigator, says he is only “slightly biased” by the fact he teaches PCI compliance. “PCI is a very good thing,” he insists, adding that “If you are a person who performs security assessments, it’s not a burden.<\/p>\n","protected":false},"excerpt":{"rendered":"
Most recently updated in September, the PCI standard requires, among other things, firewalls, the encryption of cardholder and other sensitive data sent across public networks, and restrictions on physical access to cardholder data.<\/p>\n
Still, he estimates 70% of companies who are obligated by compliance regulations to have PCI — and who would face fines and cur penalties for non-compliance — have PCI in some form today, and are heading toward full implementation.<\/p>\n
To counteract such attitudes, Visa, one of the backers of the PCI standard, has embarked on a carrot-and-stick approach with merchants, rewarding those who comply, and threatening financial penalties and other consequences to those who don’t.<\/p>\n
http:\/\/www.darkreading.com\/document.asp?doc_id=124780&f_src=darkreading_section_318<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-176","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/176","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=176"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/176\/revisions"}],"predecessor-version":[{"id":2663,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/176\/revisions\/2663"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=176"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=176"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=176"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}