Risk
11/19/2009
11:15 AM
Connect Directly
LinkedIn
Google+
Twitter
RSS
E-Mail
50%
50%

Lessons Learned From PCI Compliance

Assessors reveal mistakes companies make with data security standard.

3. Take Advantage Of Overlaps

Companies large enough to process millions of credit card transactions are likely to be subject to other regulations, such as Sarbanes-Oxley, or standards such as ISO and the SAS 70 security audit, as well as state laws that mandate the protection of consumer information. Many companies treat each requirement separately, so that every audit becomes a disruptive event, says the Neohapsis QSA. A more proactive approach is to dovetail as many requirements as possible so that audits are less of an issue.

For instance, regulation X might mandate seven-character passwords, while regulation Y says eight. "Set it to nine and satisfy all those controls," he says. "I haven't seen a lot of effort there. People wait for the auditor to come through and correct you instead of doing it as a unified effort."

4. Your Assessor Isn't The Enemy

It's hard for overworked and underfunded IT and security teams to watch some dude stroll in with a scorecard and tell them where they've failed--and then send a bill. A certain coolness, if not downright animosity, is to be expected.

But your company has an obligation to protect cardholder data, and the assessor can help achieve that goal. Companies should view assessors "not as opponents, but as partners in developing sound security programs," says Fabian J. Olivia, a QSA and global PCI competency leader at IBM.

Some IT teams realize that they can use the findings from an assessment to get funding they've been asking for to implement critical projects, says Branden Williams, a QSA and senior director of consulting at AT&T Consulting's PCI group. If you know a PCI assessment is coming, document areas where your controls are weak, outline a plan to address them, and get that information in front of management immediately. Once the assessment is over, you'll have third-party validation that the issues you've raised are important, and funding may come your way.

3 Typical
PCI Compliance Errors
> PCI requires companies to maintain a network diagram that shows how card data flows through IT systems, but assessors say companies often don't have one or it lacks critical details.
> According to PCI, companies must install critical security patches, but patches sometimes break systems, or one IT group requests a patch but another forgets to install it.
> Sometimes IT runs external scans but neglects to scan inside the firewall, which PCI requires. Organizations also must show that vulnerabilities have been remediated by running a scan after patches are deployed, but many skip this step.

5. This Is A Pass/Fail Test

Unlike many regulations that emphasize risk management, PCI is a prescriptive compliance standard. It requires specific controls and processes, and organiz- ations have to meet all the requirements, or they won't pass. "There is no partial compliance," says the Neohapsis QSA. "You either are, or you are not. It's not something the QSA can change for you."

PCI critics say the standard is complex and costly, and that compliant companies can still lose data. We agree. But despite its flaws, PCI is an opportunity for companies to get serious about their obligation to protect cardholder data and implement sensible controls. "PCI compliance should be a by-product of sound security practices and programs," says IBM's Olivia. We also agree.

Previous
2 of 2
Next
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Tech Digest, Dec. 19, 2014
Software-defined networking can be a net plus for security. The key: Work with the network team to implement gradually, test as you go, and take the opportunity to overhaul your security strategy.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-8142
Published: 2014-12-20
Use-after-free vulnerability in the process_nested_data function in ext/standard/var_unserializer.re in PHP before 5.4.36, 5.5.x before 5.5.20, and 5.6.x before 5.6.4 allows remote attackers to execute arbitrary code via a crafted unserialize call that leverages improper handling of duplicate keys w...

CVE-2013-4440
Published: 2014-12-19
Password Generator (aka Pwgen) before 2.07 generates weak non-tty passwords, which makes it easier for context-dependent attackers to guess the password via a brute-force attack.

CVE-2013-4442
Published: 2014-12-19
Password Generator (aka Pwgen) before 2.07 uses weak pseudo generated numbers when /dev/urandom is unavailable, which makes it easier for context-dependent attackers to guess the numbers.

CVE-2013-7401
Published: 2014-12-19
The parse_request function in request.c in c-icap 0.2.x allows remote attackers to cause a denial of service (crash) via a URI without a " " or "?" character in an ICAP request, as demonstrated by use of the OPTIONS method.

CVE-2014-2026
Published: 2014-12-19
Cross-site scripting (XSS) vulnerability in the search functionality in United Planet Intrexx Professional before 5.2 Online Update 0905 and 6.x before 6.0 Online Update 10 allows remote attackers to inject arbitrary web script or HTML via the request parameter.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Join us Wednesday, Dec. 17 at 1 p.m. Eastern Time to hear what employers are really looking for in a chief information security officer -- it may not be what you think.