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.
More Security Insights
- The Power of Cloud: Driving Business Model Innovation
- Business Analytics for Midsize Businesses: Challenges and Benefits
- The Critical Importance of High Performance Data Integration for Big Data Analytics
- Why is Information Governance So Important for Modern Analytics?
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.