BlackHat 2010 - Slides / Paper / Rest..


BlackHat this year passed in a blur. In retrospect staying in Vegas for only 3 nights was probably a bad idea. (This is especially obvious when you consider that the round trip involves about 60 hours of travelling time)

I got in and mostly hid in my room working on the talk. I did the talk, and promptly hid in my room feeling sick till it was time to fly home. (this means that i failed completely to participate in teamZA's magnificent #hackcup football victory)

In 2009, our "Clobbering the Cloud" talk squeezed in about 138 slides into 70 minutes.
This year my talk was 50 minutes long (i wasn't convinced that the topic could hold interest for longer periods), and my keynote deck was made up of 38 slides. But, the presentation used both the 38 keynote slides, and a prezi presentation (with about 170 transitions).

This means there was never a chance of finishing the presentation in the allotted time. I was aware of this going in, and decided that a solution would present itself while i was on stage :>
(in truth, i didn't have the heart to leave out any of the points in the prezi. I had already whittled down tons of events from the timeline, and these ~170 _had_ to be included)

The talk went well.. and live tweets [2] on the talk were complimentary:


I was going to upload a picture of the beard here, but instead i'll add the actual presentation materials. The talk was recorded and i'll paste a link here as soon as the video is made available.




[the paper][the slides*]
[prezi (stand-alone)*]prezi
(online)*
* This year i made use of the awesome prezi for my timeline visualization. They rock!

Some interesting additions have been made to the timeline since the talk, with some input from gera@core being particularly insightful.


[1] "Hang Over" reference added as akwardly as Allan's laughter to fulfill a promise

Comments

  1. Unknown16 August 2010 at 15:39

    Well played, sir.

    ReplyDelete
  2. mh16 August 2010 at 15:57

    heheh.. thank u sire.. (and thanks for showing up for the talk, even after having heard the webcast) :>

    ReplyDelete

Post a Comment

Popular posts from this blog

Simple Graphs with Arbor.js

Image
We recently released a tool at http://cc.thinkst.com to capture and collect infosec conference details. We commented on it [ here ]. One of the cooler components of it, is the ability to view the relationships between speakers/researchers who have collaborated. This post is a quick introduction to the library we used to build our graphs, with enough info to get you up and running in minutes. As I mentioned, we use ArborJS library which is a a graph visualization library using web workers and the popular jQuery . The API is really well documented [ here ] but like most people, I learn best by example (and there are precious few of these). Hopefully this post will fill that niche, and by the end of it you should have a basic understanding of how to use arbor.js in your project. Our Aim: We will be building a simple contrived example as seen in the image above. Project setup : Create a new html page and include script references to the following libraries (Download them from the links...
Read more

Small things done well¹

Image
Bad design is bad  In 2015 Moxie Marlinspike pointed out that the manual page for GPG is (now) 50% of the novel Fahrenheit 451. Any software whose man page approaches 20 thousand words better have a good excuse, and GPG can only gesture vaguely at decades of questionable design. GPG gets a bad rap but it isn’t really much of an outlier. Security software has a long history of crumby, unintuitive interfaces and terrible design choices. A deep dive into the factors behind awfully designed security software isn’t the purpose of today’s blogpost, but suffice it to say there is seldom pressure from the end users. Security software mandated by a security team is often rammed down users’ throats, so it doesn’t bother being pleasant. It’ll sell anyway. We’ve worked hard to buck this trend from our first version. It’s one reason why we are one of the few pieces of security software that customers actually talk about in terms of love: https://canary.tools/love Recently, we released a major...
Read more

Using the Linux Audit System to detect badness

Image
Security vendors have a mediocre track record in keeping their own applications and infrastructure safe. As a security product company, we need to make sure that we don’t get compromised. But we also need to plan for the horrible event that a customer console is compromised, at which point the goal is to quickly detect the breach. This post talks about how we use Linux's Audit System (LAS) along with ELK (Elasticsearch, Logstash, and Kibana) to help us achieve this goal. Background Every Canary customer has multiple Canaries on their network (physical, virtual, cloud) that reports in to their console which is hosted in AWS. Consoles are single tenant, hardened instances that live in an AWS region. This architecture choice means that a single customer console being compromised, won’t translate to a compromise of other customer consoles. ( In fact, customers would not trivially even discover other customer consoles, but that's irrelevant for this post. ) Hundreds of consoles runn...
Read more