Perimeter
1/29/2011
08:14 AM
Connect Directly
RSS
E-Mail
50%
50%

The SpiderLabs Report

Four out of five of the victims were so clever that they didn't need a firewall

At the recent Black Hat conference in DC, I sat down with Tom Brennan, the director of Trustwave's SpiderLabs, and Nick Percoco, senior vice president and the force behind the Trustwave SpiderLabs Global Security Report 2011, which was to be released on the following day. In the interim, I've had a chance to read through the report as well.

The report they've produced is a bit sprawling. It's in three sections, the first being what I think of as the actual report, the second a 20-page survey of attack vectors, the third being a set of "11 Strategic Initiatives for 2011." My interest is overwhelmingly in the first section.

The report, like the Verizon report I've written about elsewhere, looks at cases where SpiderLabs has been called in to assist in response to an incident. According to the report, in 85 percent of the "more than 220" investigations SpiderLabs conducted last year, a breach was confirmed. This is considerably more cases than Verizon's team looked at in the same time frame, and it would seem (though the report doesn't supply the underlying demographics to verify this) that the sample spreads across a much broader swath of kinds and sizes of companies.

If we can make one broad generalization about the companies involved in the breaches (or at least in breaches where PCI compliance was an issue), then it's this: They are run by idiots. Complete, flaming idiots:

"Breached organizations did not have a firewall policy that properly protected the payment environment at the network border in 97.5% of our cases. Of those organizations, 84% lacked a firewall completely."

The first part I can see a friendly way to interpret -- getting firewalls to do what you think they are doing can be pretty tricky. But, hey, 84 percent didn't have a firewall?

In a way, this (and some other almost-as-staggering lapses among the afflicted) is good news. These are, after all, the victims of breaches. If you spread the net wider and ask a range of security practitioners who may or may not have suffered a breach, then 98 percent of them have firewalls (and lots of other good measures in place as well). It's certainly not as simple as saying that having a firewall means not having a breach (that's emphatically not true), but at least with the companies that Trustwave deals with, not having a firewall seems to be a pretty fair predictor of soon needing to call in the SpiderLabs folks.

Since you already have a firewall, what may be of more interest to you is the prevalence of problems that involve compromises introduced by third parties:

"88 percent of investigations involved deficiencies such as default vendor-supplied credentials and unsecure remote access applications."

Is this you? Can you prove it's not?

And there are several other good takeaways from the report, which you can find free here. Definitely worth having a look at -- but I must confess that I really don't understand what's going on with that (non)firewall statistic.

Robert Richardson directs content and programs at the Computer Security Institute.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Ernie Floyd
50%
50%
Ernie Floyd,
User Rank: Apprentice
3/15/2012 | 6:58:40 PM
re: The SpiderLabs Report
Robert,
After a quick skim of the report, it was not clear what merchant level was most predominant in the investigations.-á Prior year reports have noted this.-á It's expected that most of these breaches are in Level 4 merchants.-á These operators aren't idiots, they simply often know little of IT or PCI in general.-áThey often only have whatever network equipment that is provided by their ISP.-á This would almost never include a firewall and appropriate configuration to meet PCI requirements.-á

The report continues to demonstrate there is much work left to do to raise the awareness of cyberrisks in the small business community.-á It's ashame as well, because when small businesses are breached, the damages can be so great that they bankrupt the company and cause great personal loss to those owners.
Register for Dark Reading Newsletters
Partner Perspectives
What's This?
In a digital world inundated with advanced security threats, Intel Security seeks to transform how we live and work to keep our information secure. Through hardware and software development, Intel Security delivers robust solutions that integrate security into every layer of every digital device. In combining the security expertise of McAfee with the innovation, performance, and trust of Intel, this vision becomes a reality.

As we rely on technology to enhance our everyday and business life, we must too consider the security of the intellectual property and confidential data that is housed on these devices. As we increase the number of devices we use, we increase the number of gateways and opportunity for security threats. Intel Security takes the “security connected” approach to ensure that every device is secure, and that all security solutions are seamlessly integrated.
Featured Writers
White Papers
Cartoon
Current Issue
Dark Reading's October Tech Digest
Fast data analysis can stymie attacks and strengthen enterprise security. Does your team have the data smarts?
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-4594
Published: 2014-10-25
The Payment for Webform module 7.x-1.x before 7.x-1.5 for Drupal does not restrict access by anonymous users, which allows remote anonymous users to use the payment of other anonymous users when submitting a form that requires payment.

CVE-2014-0476
Published: 2014-10-25
The slapper function in chkrootkit before 0.50 does not properly quote file paths, which allows local users to execute arbitrary code via a Trojan horse executable. NOTE: this is only a vulnerability when /tmp is not mounted with the noexec option.

CVE-2014-1927
Published: 2014-10-25
The shell_quote function in python-gnupg 0.3.5 does not properly quote strings, which allows context-dependent attackers to execute arbitrary code via shell metacharacters in unspecified vectors, as demonstrated using "$(" command-substitution sequences, a different vulnerability than CVE-2014-1928....

CVE-2014-1928
Published: 2014-10-25
The shell_quote function in python-gnupg 0.3.5 does not properly escape characters, which allows context-dependent attackers to execute arbitrary code via shell metacharacters in unspecified vectors, as demonstrated using "\" (backslash) characters to form multi-command sequences, a different vulner...

CVE-2014-1929
Published: 2014-10-25
python-gnupg 0.3.5 and 0.3.6 allows context-dependent attackers to have an unspecified impact via vectors related to "option injection through positional arguments." NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-7323.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Follow Dark Reading editors into the field as they talk with noted experts from the security world.