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

3/16/2008
09:51 PM
George V. Hulme
George V. Hulme
Commentary
50%
50%

The Clock Is Ticking For Retailer Web Application Security

In a few months time, what is now considered merely an advisable best practice will become mandatory for any business accepting credit card payments over the Web. Problem is, the mandate is ill conceived.

In a few months time, what is now considered merely an advisable best practice will become mandatory for any business accepting credit card payments over the Web. Problem is, the mandate is ill conceived.At the end of June, section 6.6 of the Payment Card Industry Data Security Standard (PCI DSS) goes into full effect. In short, this section of PCI DSS requires merchants and card payment providers to make certain their Web applications are secure.

If done right, it could actually help curb the number of Web-related security breaches.

But it's not done right. Not yet.

Here's section 6.6, which goes from a nice-to-do, to a must-do, on June 30:

Ensure that Web-facing applications are protected against known attacks by applying either of the following methods: -- Having all custom application code reviewed for common vulnerabilities by an organization that specializes in application security -- Installing an application layer firewall in front of Web-facing applications

Now, the overarching point of the PCI DSS is to both help instill a sense of trust among consumers in e-commerce, especially when it comes to online payments. And, hopefully, actually increase the Web security of online merchants, which until a couple of years ago remained ridiculously pathetic. Today, the state of retail security is just pathetic. So there's been some improvement.

In fact, the Privacy Rights Clearing House maintains a chronology of breaches here. It's a long list, and may take awhile for those with slower connections to load, so I don't recommend anyone using a dial-up connection to click the link. To date: 218 million data records have been exposed.

A few years ago, most of the breaches were caused by criminal hacking. Today, many breaches also are caused by the loss of laptops, thumb drives, and other forms of removable media. Yet, there's still a healthy number of criminal hacks, and sloppy Web and application design to go around.

And that's where section 6.6 steps in. And while I agree with the spirit of 6.6, which is better Web code, it's flawed as it's currently written.

It pretty much says that retailers can either perform a custom code assessment, or deploy a Web application firewall.

I'd much rather have PCI DSS mandate a security assessment be performed on all custom (as well as all commercial software before it's allowed to be shipped). Then, secondarily, advise the deployment of a Web application firewall.

As it stands now, retailers can build shoddy code, skimp on Q&A, and toss a Web application firewall in front of their ill-crafted code and claim compliance.

That's just not good enough.

And it's one of a long list of reasons why the list of breaches kept by the Privacy Rights Clearing House will continue to grow ... .

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Browsers to Enforce Shorter Certificate Life Spans: What Businesses Should Know
Kelly Sheridan, Staff Editor, Dark Reading,  7/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-17366
PUBLISHED: 2020-08-05
An issue was discovered in NLnet Labs Routinator 0.1.0 through 0.7.1. It allows remote attackers to bypass intended access restrictions or to cause a denial of service on dependent routing systems by strategically withholding RPKI Route Origin Authorisation ".roa" files or X509 Certificate...
CVE-2020-9036
PUBLISHED: 2020-08-05
Jeedom through 4.0.38 allows XSS.
CVE-2020-15127
PUBLISHED: 2020-08-05
In Contour ( Ingress controller for Kubernetes) before version 1.7.0, a bad actor can shut down all instances of Envoy, essentially killing the entire ingress data plane. GET requests to /shutdown on port 8090 of the Envoy pod initiate Envoy's shutdown procedure. The shutdown procedure includes flip...
CVE-2020-15132
PUBLISHED: 2020-08-05
In Sulu before versions 1.6.35, 2.0.10, and 2.1.1, when the "Forget password" feature on the login screen is used, Sulu asks the user for a username or email address. If the given string is not found, a response with a `400` error code is returned, along with a error message saying that th...
CVE-2020-7298
PUBLISHED: 2020-08-05
Unexpected behavior violation in McAfee Total Protection (MTP) prior to 16.0.R26 allows local users to turn off real time scanning via a specially crafted object making a specific function call.