Just a short post to announce the first round speakers for this year’s ShmooCon Firetalks… With several more submissions at the last minute on New Years Eve, the selection committee has been hard at work trying to pull together a diverse program with the most interesting talks combined with a good mix of established and new speakers. This year was quite interesting as there was a significant uptick in female submissions … and some very good abstracts to say the least based on our first round selections.
But before we get on to the talks I just wanted to thank the selection committee for all the hard work they put in over the last few weeks. Since some may not be familiar with their full names, I’ll just list them all by their Twitter handles … @jack_daniel, @jasonmoliver and @nathiet. And before anyone says anything, there is one female on the selection committee but a deluge of PCI work kept her from participating thus far.
Also I’d would again like to thank our generous sponsors for not only providing some awesome prizes but also other contributions that are going to make this year’s Firetalks the best so far! Oh wait … we don’t have any sponsors yet. If you’re interested in becoming one, please contact us to get the conversation going. Thanks!
And without further ado … we are pleased to announce the first round speakers!!!
Thin Slicing a Black Swan: A Search for the Unknowns
by Michele Chubirka & Ronald Reck
As infosec professionals we are swimming in prodigious amounts of data, but it isn’t making us better at our jobs, it seems to make us worse. In Verizon’s 2012 Data Breach Investigations Report, it was found that across organizations, an external party discovers 92% of breaches. We continue to desperately grasp at that straw of, “more data,” but what if this is simply information gluttony? Incident response’s bloated model drives it closer to a form of security archeology rather than its promise of real-time relevance.
When Did the Smartphone Pentest Framework Get Awesome?
by Georgia Weidman
SPF came out and it was good but not spectacular, so Georgia went and lived in a cave for 2 months and came out with a much better SPF. Custom post exploitation apps using any front end you have the code for, Permission based post exploitation apps and apps that try every exploit known for the device, integration with other tools, More exploits for more platforms. If you think you’ve seen SPF, you are mistaken. Everything demoed in this presentation will be brand new functionality never before shown. When many people hear Smartphone Pentest Framework they think this tool lets you run attack tools from a smartphone. Instead this tool lets you assess the security posture of smartphone devices. As smartphones enter the workplace, sharing the network and accessing sensitive data, it is crucial to be able to assess the security posture of these devices in much the same way we perform penetration tests on workstations and servers.
Swinging Security Style: An Immodest Proposal
by Wendy Nather
I have a proposal to make — or rather, a proposition — to improve the overall state of security. Just as in the olden days, when swinging couples would put their house keys in a pile, and whoever drew a set of keys would go home with its owner, I suggest that security professionals do something similar (maybe with USB keyfobs or hardware tokens?). We don’t have enough empathy or understanding in this industry, and changing places with someone who does something very different from you (whether it be auditing, management, pentesting, engineering or something else) can help both personally and professionally. Think of it as job swapping — and if you’re married to your job, that’s kind of like spouse-swapping, isn’t it? Pick someone next to you and help them solve one of their security problems. You don’t even need to bring Crisco.
ShellSquid: Distributed Shells With Node
by Tom Steele
Shellsquid was built out of necessity. Corporate egress controls often limit outbound connections to http (tcp/80) and https (tcp/443); often requiring the traffic to exit through a proxy. When attacking victims it is then a necessity to use reverse payloads that connect on one of these two ports and are proxy aware. The safest option being https. This is straight forward. Start your listener and go. But what if you’re attacking multiple targets and want to keep them separate? What if you’re working with a team who is all attacking different targets and they can’t share a listener? What are you to do? Shellsquid is meant to alleviate this issue by dynamically routing your reverse connections to a configured listener on a different port and/or machine. Teams of penetration testers can now share a single perimeter systems listening over https, while routing reverse connections to internal hosts.
Hope to see you all at ShmooCon! See ya!