Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk //

Compliance

9/26/2011
03:22 PM
50%
50%

QSAs Share What Drives Improved PCI Practices

As organizations shift attitudes and overcome misconceptions, PCI compliance and security improve

After looking under the covers at so many different kinds of organizations, Payment Card Industry (PCI) Qualified Security Assessors (QSAs) get to see the full range of the good, the bad, and the ugly of PCI compliance and security regimes. According to many QSAs, avoiding PCI struggles, poor security, and flagged yearly assessments are often more about the right attitudes from management than about the IT security practices themselves. QSAs say the organizations that come at PCI positively reap the most benefits. In other words, approach PCI in earnest, and best practices will follow.

"I've been involved in PCI assessments and security before the Data Security Standards were in place, so I've kind of seen the whole evolution," says Chris Novak, a QSA and managing principal for Verizon Business. "And one of the things I've really seen is that organizations who have really looked at it in a positive way -- seen it as a way to get better at security -- they do a better job a compliance."

While organizations should certainly respect the penalties and ramifications of noncompliance with PCI, management needs to remember why the standard exists in the first place. Security is the name of the game, but often senior leadership loses sight of that and looks at compliance as a challenge rather than an opportunity to improve protection.

"I think that what a lot of folks miss is that the key point of compliance is not to find everybody that's not compliant and penalize them," Novak says. "The idea is to drive people toward becoming compliant so they secure their infrastructure."

According to Andrew Jamieson, a QSA for Witham Laboratories, the compliance issue that he sees organizations trip over time and time again during his assessments is poor documentation of security policies. The organization generally might be doing OK with many of its day-to-day IT practices, but because of a lack of management engagement, the policy documentation that drives long-term compliance and overall security success is nonexistent.

"It's because compliance isn't driven down from management. The problem is that when people first read through PCI, it sounds like an IT security problem," he says. "So they kick it to the IT department, but IT is not necessarily in a position to provide the policy-level documentation that's required."

Even when management does become engaged in PCI, it is with the wrong outlook, Jamieson says. Many times senior leaders view PCI compliance as a one-off project. The problem is that passing an assessment might prove point-in-time compliance, but that one-time push is not going to keep breaches at bay if the organization doesn't support it long-term.

"A lot of people we work with on PCI DSS run it as a project. In other words, 'We're not compliant, let's get compliant. Formulate a budget and have a team run it as a project.' Once they get compliant, then management loses interest in funding anything else," he says. "At that point, it's much harder to maintain the practices to keep PCI compliance and security going."

That project mentality is one of the fastest ways to ensure the money poured into the initial effort will be wasted. When it comes time to face a QSA assessment in subsequent years, future project teams end up having to reinvent the wheel all over again.

"As a QSA, we come in once a year, and I think that companies shouldn't see that as the time they should be compliant," Jamieson says. "We recommend people keep a spreadsheet or database of the systems they have, the policies, configurations, patch states, and logging done on them -- that's basically the audit right there. If you keep up to date throughout the year, the audit becomes a really painless process. I'm not going to say it's easy, but it's easier done throughout the year than in a single point in time."

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
What the FedEx Logo Taught Me About Cybersecurity
Matt Shea, Head of Federal @ MixMode,  6/4/2021
Edge-DRsplash-10-edge-articles
A View From Inside a Deception
Sara Peters, Senior Editor at Dark Reading,  6/2/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-34682
PUBLISHED: 2021-06-12
Receita Federal IRPF 2021 1.7 allows a man-in-the-middle attack against the update feature.
CVE-2021-31811
PUBLISHED: 2021-06-12
In Apache PDFBox, a carefully crafted PDF file can trigger an OutOfMemory-Exception while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.
CVE-2021-31812
PUBLISHED: 2021-06-12
In Apache PDFBox, a carefully crafted PDF file can trigger an infinite loop while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.
CVE-2021-32552
PUBLISHED: 2021-06-12
It was discovered that read_file() in apport/hookutils.py would follow symbolic links or open FIFOs. When this function is used by the openjdk-16 package apport hooks, it could expose private data to other local users.
CVE-2021-32553
PUBLISHED: 2021-06-12
It was discovered that read_file() in apport/hookutils.py would follow symbolic links or open FIFOs. When this function is used by the openjdk-17 package apport hooks, it could expose private data to other local users.