'Offensive technologies' can secure networks
- — 15 May, 2007 10:29
The First Usenix Workshop on Offensive Technologies is being held in Boston on Aug 6. It's hard to resist an event called WOOT, even though we weren't quite sure what it was all about. So we shot an e-mail to Tal Garfinkel, a Ph.D graduate student in Stanford University's computer science department and one of WOOT's program chairs, and asked him to explain.
What do you mean exactly by "offensive technologies"?
There are many ways to chop up the conceptual space of computer security. One way is by grouping technologies into those required for attack and defense. The primary focus of traditional academic computer security has been defense. Intrusion detection, access control, bug detection/prevention and the like. The primary focus of much of the more "black hat" or "grey hat" communities has been offensive technologies -- techniques for exploiting software weaknesses, reverse engineering, information gathering, evading detection and the like. Interestingly, for any given question in the defensive space -- for example, how do you defend against keyloggers? -- there is a dual in the offensive space, such as: How do you design a better keylogger? By understanding both perspectives, one gets a deeper understanding of computer security, and for many years one side has informed the other.
Many of us have read some of the black hat magazines, read the code of attack tools, and followed the state of the art in attack to inform our view of defense. However, the coverage of that side of the equation has often been spotty. The editorial quality of places like Phrack is quite low, and the lack of peer review means sometimes the veracity of claims being made is questionable. In black hat, for example, the metric for quality often seems to be how much news the hype about your work induces, rather than how original, important or credible your claims are.
Why the need for this separate workshop from the broader Usenix Security Symposium taking place that week in Boston?
While attack technologies have definitely been part of forums like Usenix Security for a while, the bar for publishing new attack work is quite high in terms of novelty and certain topics (such as reverse engineering, malware design, automatic exploit development) are often overlooked entirely. Often there is work that would really be helpful to have in the literature to help researchers understand the state of the art in offensive practice, that simply doesn't fit the model of what we are currently looking for in academic conferences. The absence of this work not only means we have a less than complete literature to draw from, but also tends to exclude many practitioners who have a lot of valuable stuff to contribute to the academic discourse.
I think if you look at our program committee you find a really interesting cross section of folks from different backgrounds with different relationships to attack technologies -- this is both to represent different view points and attract broader participation.
We're running out of stuff to write about worms, phishing, pharming, bots, spyware and so on. What's the next big thing the bad guys have up their sleeves?
I can't say for sure, although I think the best advice to predict this is to follow the money.
One area I think there is interesting potential for growth is in high value targets, such as business intelligence that can be used for arbitrage, or intellectual property that can be sold to offshore interests where litigation and enforcement may be challenging. There has been very interesting and public growth in the high end of computer security, with people selling custom rootkits, exploits and other technology that just a few years ago would only be available to folks in government agencies, or that you would have to build on your own. I expect in the coming years the information that is available in black markets, and the pool of skilled talent that has the know-how to acquire this information will continue to increase. Given the spotty state of security within the enterprise perimeter, this seems like cause for concern