The Coalfire Blog

Welcome to the Coalfire Blog, a resource covering the most important issues in IT security and compliance. You'll also find information on Coalfire's insights into the unique cybersecurity issues that impact the industries we serve, including Cloud Service Providers, RetailFinancial Services, Healthcare, Higher Education, Payments, Government.

The Coalfire blog is written by the company's leadership team and our highly-credentialed security assessment experts.

The Coalfire Blog

PCI DSS 3.0 puts emphasis on year-round awareness

September 10, 2013, Matt Getzelman, PCI Practice Director

Bookmark and Share

Matt Getzelman

It's easy to think of PCI compliance as just another annual hoop to jump through. Of course, after the annual audit, the business is safe for another 12 months, right? Well, not exactly, and with the upcoming release of PCI DSS 3.0, there will be an even bigger reason to think about compliance beyond the scope of a yearly audit.

eWEEK's Sean Michael Kerner recently highlighted comments from several industry experts in an effort to understand what the new compliance requirements will mean for businesses. One of the most important points to keep in mind is that officials are pushing merchants to think about compliance more frequently.

"There is no requirement for more reports than an annual validation, but that's just a snapshot in time," PCI Security Standards Council CTO Troy Leach told eWEEK. "What we're hoping with this is that, through the process, there is more regularity of checking by the merchant as the environment changes."

In practice, this translates to a heightened focus on user education, security awareness and self evaluation. For example, one of the changes in PCI DSS 3.0 is the ability to use passphrases rather than merely relying on passwords for user profiles. Employees will still need to be aware of their organization's policies regarding password or passphrase choices, and it may also be an opportunity to educate them about password-strength best practices.

PCI DSS 3.0 change drivers
While a higher degree of awareness and education is one of the driving forces behind PCI DSS 3.0, there are several other factors influencing the upcoming changes. The PCI Security Council identified several in particular, including:

  • Use of weak passwords
  • Third-party IT services
  • Inconsistency in compliance assessments
  • Slow malware and vulnerability detection

It is important to keep in mind that the changes are not designed solely to make compliance more difficult for merchants. In fact, changes such as allowing the use of passphrases are intended to give organizations more options to satisfy PCI mandates. However, the push for standardized auditing practices makes it important for IT decision makers to not only be aware of accepted practices but to ensure that those they receive IT services from follow those requirements as well.

"Securing cardholder data is a shared responsibility," the PCI Security Standards Council said. "Today's payment environment has become ever more complex, creating multiple points of access to cardholder data."

At a high level, PCI DSS 3.0 is intended to shift the focus from compliance (audits) to security (preventing breaches).

Most importantly, the PCI Council will add guidance for organizations to maintain compliance as part of business-as-usual practices. That’s an important change intended to move organizations past the idea that PCI compliance is a once-a-year affair designed to satisfy auditors and then soon to be forgotten.

<< Go Back

Blog post currently doesn't have any comments.

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