Risk // Compliance
7/18/2012
01:00 AM
Connect Directly
RSS
E-Mail
50%
50%
Repost This

A Common-Sense Secret For Cheaper PCI Audits

Pre-audit logistics prep can go a long way toward saving on PCI assessment costs

There are plenty of legitimate reasons why PCI compliance efforts can cost an enterprise a bundle. Legacy systems may need to be rearchitected, new technologies have to be purchased, and improved business processes must be implemented. Those types of activities take capital, but they often offer ROI in terms of improved security.

But there's one PCI expense that's guaranteed to offer zero return: disorganization. Most Qualified Security Assessors (QSAs) will tell you that one of the biggest ways PCI-regulated companies waste their money is through poor logistical planning prior to the audit itself.

"Time is money, and if I have to extend the audit by four more days because I spend half my time sitting around while the company is scrambling, that can cost a lot of money," says Court Little, director of strategic security at Solutionary.

A company can bungle pre-audit logistics in many ways. Sometimes the organization fails to gather its documentation in advance. Other times a manager forgets that a key person the assessor needs to access will be away at a conference or on vacation during the scheduled audit. Some managers realize on the day of the audit that they need to clear access to resources or interviewees through legal, a sometimes time-consuming process. And still other times, the organization fails to prepare guest credentials into IT resources necessary to give the assessor enough access to validate the company's claim. Often, the matter is exacerbated when any combination of these oversights occur during the same audit.

Each of these offenses drastically increases the length of time the QSA spends on the audit, and could affect that auditor's perception of your PCI readiness, increasing the chances of an initial fail and future mitigation work to get into compliance. If an enterprise can't even get the required people and documents together to satisfy the auditor, then what does that say about its ability to secure cardholder data?

According to Little, these procedural hang-ups can be easily avoided with a little communication with the QSA prior to the audit and a lot of homework before that auditor hits your doorstep.

"Whether they're veterans of PCI or not, they should definitely request a list from their QSA of everything that they need to have ready for them when the audit begins," he says. "If the company can organize and know exactly what the auditor is going to need and who they're going to need to talk to, that will greatly increase the efficiency of an audit."

More than likely, the No. 1 item on that list will be meticulous documentation of policies and procedures. According to Bob Gaines, every kind of auditor, whether a PCI QSA or not, cites lack of documentation as the biggest pet peeve during the audit process.

"The biggest pet peeve they'll have is that the company had all of its policies, but it is stuck in Ed's head somewhere in the finance department or wherever," says Gaines, security and compliance manager for All Covered. "The policy isn't written down anywhere."

So companies need to think several steps ahead, preparing for the audit by keeping gradual and meticulous records throughout the year to avoid the eleventh-hour scramble to re-create documentation before the QSA's arrival. But documentation isn't all you'll be asked for. Little says organizations are also usually unprepared for the interview process required by PCI assessments. He has seen many companies waste everybody's time by making bad assumptions about who the auditor will need to talk to because they've failed to talk to that QSA in advance.

"We literally have meetings where they schedule 10 to 15 people in a room and I don't need all those people there. I just need two people," he says, explaining that a simple preflight checklist could avoid such excess. "The QSA shouldn't come in blind -- the people should be prepared before the audit. If you can do a lot of that logistics work leading up to it, it becomes a well-oiled audit versus just a grab bag of activity where either the client brings nobody to answer questions and the QSA has to fetch everybody, or they bring everybody and they waste everybody's 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
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-0360
Published: 2014-04-23
Memory leak in Cisco IOS before 15.1(1)SY, when IKEv2 debugging is enabled, allows remote attackers to cause a denial of service (memory consumption) via crafted packets, aka Bug ID CSCtn22376.

CVE-2012-1317
Published: 2014-04-23
The multicast implementation in Cisco IOS before 15.1(1)SY allows remote attackers to cause a denial of service (Route Processor crash) by sending packets at a high rate, aka Bug ID CSCts37717.

CVE-2012-1366
Published: 2014-04-23
Cisco IOS before 15.1(1)SY on ASR 1000 devices, when Multicast Listener Discovery (MLD) tracking is enabled for IPv6, allows remote attackers to cause a denial of service (device reload) via crafted MLD packets, aka Bug ID CSCtz28544.

CVE-2012-3062
Published: 2014-04-23
Cisco IOS before 15.1(1)SY, when Multicast Listener Discovery (MLD) snooping is enabled, allows remote attackers to cause a denial of service (CPU consumption or device crash) via MLD packets on a network that contains many IPv6 hosts, aka Bug ID CSCtr88193.

CVE-2012-3918
Published: 2014-04-23
Cisco IOS before 15.3(1)T on Cisco 2900 devices, when a VWIC2-2MFT-T1/E1 card is configured for TDM/HDLC mode, allows remote attackers to cause a denial of service (serial-interface outage) via certain Frame Relay traffic, aka Bug ID CSCub13317.

Best of the Web