Two final thoughts from the PCI Community Meeting

Matt Getzelman, PCI Practice Director

The 2014 North American PCI Community Meeting has drawn to a close, but the messages and lessons learned will continue to resonate with me long after I've returned home to Denver. There were two messages from the SSC this week that really struck a chord with me and I wanted to expand on why I think they are important moving forward.

1.    Integrate PCI DSS into your Business as Usual (BAU) practices.

This is important as it was also a major point of emphasis in the PCI DSS 3.0 standard.  Many organizations struggle to understand the difference between PCI DSS validation and PCI DSS compliance.  Of course you have to validate your PCI DSS compliance once a year, but you must maintain compliance at all times.  Day-to-day operations must reflect your security and compliance program. Changing the culture of your organization to increase security awareness at all times is a necessary endeavor for all companies, not just those that are concerned with protecting cardholder data.

2.    You cannot fully outsource your compliance responsibilities.

This one’s really important for merchants but it’s relevant for service providers, too.  It’s actually a good thing when merchants choose to outsource security functions because many merchants need help with implementing security controls.  Using security experts to help manage some of your responsibilities is a good idea; this allows you to focus on what you’re really good at, growing your business.  Having said that, it’s imperative to select competent and knowledgeable service providers.  If something goes wrong, it’s your reputation (and finances) that may suffer the consequences.  I strongly recommend that you dedicate the appropriate resources for due diligence with vendor selection and management.  Otherwise, your outsourcing decision could be one that you regret.

In Case You Missed It: Recaps from Day One and Day Two of the Community Meeting

Apple Pay: A New Way to Pay - Matt Getzelman
PCI Community Meeting - EMV Chip Update - Michael Matteo
Forensics Session Takeaways from Day 2 - Michael Pyle
PCI Community Meeting Keynote - Philip Wang
Coalfire's PCI Community Meeting Webpage

Matt Getzelman


Matt Getzelman — PCI Practice Director

Recent Posts

Post Topics



Accounting Agency AICPA Assessment assessments ASV audit AWS AWS Certified Cloud Practitioner AWS Certs AWS Summit bitcoin Black Hat Black Hat 2017 blockchain Blueborne Breach BSides BSidesLV Burp BYOD California Consumer Privacy Act careers CCPA Chertoff CISO cloud CMMC CoalfireOne Compliance Covid-19 credit cards C-Store Culture Cyber cyber attacks Cyber Engineering cyber incident Cyber Risk cyber threats cyberchrime cyberinsurance cybersecurity danger Dangers Data DDoS DevOps DevSecOps DFARS DFARS 7012 diacap diarmf Digital Forensics DoD DRG DSS e-banking Education encryption engineering ePHI Equifax Europe EU-US Privacy Shield federal FedRAMP financial services FISMA Foglight forensics Gartner Report GDPR Google Cloud NEXT '18 government GRC hack hacker hacking Halloween Health Healthcare heartbleed Higher Education HIMSS HIPAA HITECH HITRUST HITRUST CSF Horror Incident Response interview IoT ISO IT JAB JSON keylogging Kubernetes Vulnerability labs LAN law firms leadership legal legislation merchant mobile NESA News NH-ISAC NIST NIST 800-171 NIST SP 800-171 NotPetya NRF NYCCR O365 OCR of P2PE PA DSS PA-DSS password passwords Payments PCI PCI DSS penetration Penetration Testing pentesting Petya/NotPetya PHI Phishing Phising policy POODLE PowerShell Presidential Executive Order Privacy program Ransomware Retail Risk RSA RSA 2019 Safe Harbor Scanning Scans scary security security. SOC SOC 2 social social engineering Spectre Splunk Spooky Spraying Attack SSAE State Stories Story test Testing theft Virtualization Visa vulnerability Vulnerability management web Wifi women XSS