Vulnerabilities / Threats
6/13/2013
05:27 PM
Mike Rothman
Mike Rothman
Commentary
Connect Directly
RSS
E-Mail
50%
50%

0-Day The (Bug) Bounty Hunter

Companies increasingly offer bug bounties to help find vulnerabilities and threats. This is an opportunity for those looking to get into security

Whenever I go to a conference, inevitably I'll meet a college student or a younger kid interested in security. They want to know how I got to -- well, wherever I am -- and how they can sit in coffee shops all day. Once I get over the shock that I had already graduated from college before these kids were born, they usually want some guidance on how to get started in the business.

For quite a while, I told them to volunteer their time configuring networks and protecting data for organizations that didn't have internal resources to do so. You know, religious organizations, charities, youth groups, whatever. Just get some experience and use that to parlay into a corporate internship -- and eventually a job. I also told them about the need to learn some coding kung fu, since application security was going to be a big problem for many years to come. Even a blind squirrel finds the nut every so often.

As opposed to taking Java courses (which seemed like a good idea at the time), there's now another alternative. These kids can become bug bounty hunters. Don't turn up your nose yet. Hear me out a bit. Kids with an interest in security today have all sorts of ways to learn about security, but a bunch can land them in hot water. They can play around with DDoS tools, social-engineer their way into the big evil company, or break into their high school's network with Metasploit. And many do exactly that. Not because they are bad kids, but because they like to hack things, and the tools are out there and easy to use.

Consider a more productive approach. With Google recently increasing the bounty to find bugs and other companies taking a similar approach, those meddling kids can turn their talents to finding defects in these software products. Not only can the kids make a shekel or two, but they'll end up with invaluable experience and a few notches in their belts when they find bugs. And they will find stuff -- it's software, after all. This practical experience looks good to recruiters and other folks looking to find talented candidates for the tons of open security jobs.

To be clear, finding bugs is more about offense than defense. But it's a start, and once someone can successfully break things, they'll have a good perspective on how to protect it. If that's the direction they want to go in. With the security skills shortage in the industry, there will be plenty of opportunities for those who want to stay on an offensive track. And I don't mean those less-than-hygienic folks we all know and love.

It turns out these bug bounty programs are the rare win-win for both parties. The companies get very cheap Q/A help. Even if they pay $10K for a juicy bug, the typical qualified tester costs 12 to 15 times that (fully loaded) per year. That person would need to find a lot of juicy bugs to justify hiring them full time. Even better, the company gets exclusive access to the defect, presumably to fix it before the threat becomes a weaponized exploit.

Now, of course, if the enterprising prodigy realizes governments will pay really big money for unique bugs, they can skip a few steps in their career progression. But the NSA already knows about those bugs, right?

Mike Rothman is President of Securosis and author of The Pragmatic CSO. Check him out on the Twitterz at @securityincite.

Mike's bold perspectives and irreverent style are invaluable as companies determine effective strategies to grapple with the dynamic security threatscape. Mike specializes in the sexy aspects of security, like protecting networks and endpoints, security management, and ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6335
Published: 2014-08-26
The Backup-Archive client in IBM Tivoli Storage Manager (TSM) for Space Management 5.x and 6.x before 6.2.5.3, 6.3.x before 6.3.2, 6.4.x before 6.4.2, and 7.1.x before 7.1.0.3 on Linux and AIX, and 5.x and 6.x before 6.1.5.6 on Solaris and HP-UX, does not preserve file permissions across backup and ...

CVE-2014-0480
Published: 2014-08-26
The core.urlresolvers.reverse function in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not properly validate URLs, which allows remote attackers to conduct phishing attacks via a // (slash slash) in a URL, which triggers a scheme-relative URL ...

CVE-2014-0481
Published: 2014-08-26
The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation process when a file with a conflicting name is uploaded, which allows remote attackers to cause a d...

CVE-2014-0482
Published: 2014-08-26
The contrib.auth.middleware.RemoteUserMiddleware middleware in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3, when using the contrib.auth.backends.RemoteUserBackend backend, allows remote authenticated users to hijack web sessions via vectors relate...

CVE-2014-0483
Published: 2014-08-26
The administrative interface (contrib.admin) in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not check if a field represents a relationship between models, which allows remote authenticated users to obtain sensitive information via a to_field ...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Three interviews on critical embedded systems and security, recorded at Black Hat 2014 in Las Vegas.