Perimeter
7/30/2012
06:25 PM
Rich Mogull
Rich Mogull
Commentary
50%
50%

Black Hat's Future Is The Past

Black Hat has changed a lot over the years. Now, more than ever, we need it to stick to its roots

I still remember the first time I attended Black Hat. It was back when I was still working for Gartner, and at the time was considered a "rogue" conference that bordered on the illegal due to its occasional inclusion of former convicted hackers on the speaking agenda. Good, clean, white-collar analysts from Gartner most definitely weren't supposed to mingle with the underground, even those of us with hacker roots.

It took all of a nanosecond at the event to realize how wrong those characterizations were, and since then, Black Hat has become such a fixture on my annual calendar that even eighth cousins, thrice removed, know better than to try and schedule anything that week. Black Hat has grown into one of the most significant events in security: one that plays a nearly unique role in our industry by bridging the gap between enterprise security professionals and the researcher/hacker community.

But with this expansion comes the inevitable growing pains. After spending last week at Black Hat (and Def Con), I think the future of the conference will be a return to the core principles it was created for -- not, as my partner Mike Rothman suggests, a choice between focusing on the research or targeting CISOs. In my mind, it needs to do both.

(Mike and I may work together, but we don't censor at Securosis. We don't have any problem airing our dirty laundry in public and letting you decide who you agree with.)

Black Hat originally started as a way to bring the research of Def Con to enterprise and government IT security professionals. Not everyone can get approval to spend a weekend in Vegas at the world's biggest hacker conference, so founder Jeff Moss spun up a separate, related, event more-fitting a corporate and agency crowd. The core concept of Black Hat was to take the best of the research from the hacker community to the enterprise and government world. We have other enterprise security conferences, and other hacker cons, but Black Hat is one of the only to deliberately bridge these communities. (And yes, I know I'm being a bit idealistic here).

After spending last week at both events, it's clear a lot has changed. There's still some great research, but today's economics now drive some of the most important behind government, corporate, or criminal walls. More attendees are higher up on the corporate food chain, and the appeal isn't just to the front-line technical defenders. (We had 130 CISO in the Executive Briefing session I moderated the day before the main conference, with a substantial waiting list.) The vendor floor is an actual room, not a bunch of booths crammed into a crowded hallway. For the first time there was a defense track, which was often standing-room only, even in sessions where the technical content was weaker.

While Black Hat was originally established to bring offensive research to defenders, in many ways for much of its existence it was by researchers for researchers, with defenders as more of an afterthought there to pay the bills (at the Briefings at least, not the Trainings classes held beforehand). As the conference has grown, especially in the past few years, and garnered more corporate attention, the pressure is on to figure out exactly where it fits.

I agree with Mike that Black Hat sits at a crossroads. The audience is changing, the content is changing, and the world around it is changing. But while Mike (and he isn't alone) thinks the conference needs to focus more on researchers or directors and executives, I think the real opportunity is for Black Hat to return to its roots and serve first and foremost as a conduit to bring (mostly) hard-core offensive research to defensive security professionals and executives.

This is no easy task. The only way to pull it off is to continue to appeal to both those generating offensive research and the defenders. And to do so with intense technological depth that is also translated into terms mere humans can understand and use to make security decisions, without watering it down. To focus on the research first, not the "scene," but to do so in a way that is both respectful and appealing to the community that has sustained it for so long. Even to include vendors (on the show floor) but without having them fill their booths with marketeers instead of engineers.

Now, more than ever, we need a place where offensive and defensive researchers, corporate IT pros, government defenders, and CISOs can share the same halls and focus on the latest and best research, technology, and trends. That's why Black Hat first started, and I personally think that's where we need it to go.

Rich Mogull is is founder of Securosis LLC and a former security industry analyst for Gartner

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
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-2014-5426
Published: 2014-11-27
MatrikonOPC OPC Server for DNP3 1.2.3 and earlier allows remote attackers to cause a denial of service (unhandled exception and DNP3 process crash) via a crafted message.

CVE-2014-2037
Published: 2014-11-26
Openswan 2.6.40 allows remote attackers to cause a denial of service (NULL pointer dereference and IKE daemon restart) via IKEv2 packets that lack expected payloads. NOTE: this vulnerability exists because of an incomplete fix for CVE 2013-6466.

CVE-2014-6609
Published: 2014-11-26
The res_pjsip_pubsub module in Asterisk Open Source 12.x before 12.5.1 allows remote authenticated users to cause a denial of service (crash) via crafted headers in a SIP SUBSCRIBE request for an event package.

CVE-2014-6610
Published: 2014-11-26
Asterisk Open Source 11.x before 11.12.1 and 12.x before 12.5.1 and Certified Asterisk 11.6 before 11.6-cert6, when using the res_fax_spandsp module, allows remote authenticated users to cause a denial of service (crash) via an out of call message, which is not properly handled in the ReceiveFax dia...

CVE-2014-7141
Published: 2014-11-26
The pinger in Squid 3.x before 3.4.8 allows remote attackers to obtain sensitive information or cause a denial of service (out-of-bounds read and crash) via a crafted type in an (1) ICMP or (2) ICMP6 packet.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?