Google Ups Bug Bounty To $20,000 53
Trailrunner7 writes, quoting Threatpost: "Search giant Google said it is quintupling the top bounty it will pay for information on security holes in its products to $20,000. Google said it was updating its rewards and rules for the bounty program, which is celebrating its first anniversary. In addition to a top prize of $20,000 for vulnerabilities that allow code to be executed on product systems, Google said it would pay $10,000 for SQL injection and equivalent vulnerabilities in its services and for certain vulnerabilities that leak information or allow attackers to bypass authentication or authorization features."
A failure of conventional hack-ism ? (Score:3, Interesting)
I am sure Google is employing many many very able programmers, but if Google has to pay bounty to hackers up to $20,000 to find bugs, does that mean the programmers who are sitting in Google's offices around the world have phailed?
Re:A failure of conventional hack-ism ? (Score:5, Insightful)
Re: (Score:2)
The GMail migration tools aren't so much poorly QA'd as poorly designed.
They're quite obviously written by developers, for developers, and so "generating a useful, informative error message in plain English" appears to have totally fallen by the wayside.
Re:A failure of conventional hack-ism ? (Score:5, Insightful)
the inference to be drawn is that finding a security hole would take more than 20k of programmer time, so probably the holes remaining are _hard_ to find. Seems more like a success than a failure to me.
Re:A failure of conventional hack-ism ? (Score:4, Interesting)
This 20k figure has very little to do with programmer time.
It has a LOT more to do with googles size and customer base. When you look at just how much data google has, just how many customers (paying as well, with Google Apps) 20k is absoloute pocket change to possibly convince someone malicious to instead fix the problem than exploit it.
Re:A failure of conventional hack-ism ? (Score:4, Insightful)
It's more likely that a bug would do more than $20,000 worth if damage.
Re: (Score:2)
Re: (Score:2)
[... A] bug would do more than $20,000 worth when damage.
FTFY. (JK)
Re: (Score:2)
Hah. Ouch, I deserved that. :)
Have a good week, man.
Re: (Score:2)
Re:A failure of conventional hack-ism ? (Score:5, Insightful)
Re:A failure of conventional hack-ism ? (Score:5, Interesting)
I am sure Google is employing many many very able programmers, but if Google has to pay bounty to hackers up to $20,000 to find bugs, does that mean the programmers who are sitting in Google's offices around the world have phailed?
Not necessarily. It just means that while they're confident in their code, they believe that it's always a good idea to have things vetted in the real world. The reasoning behind this is that the developers are often so close to the code that they can't possibly see EVERY conceivable bug or vulnerability. Inviting others to poke your products with a stick on a constant basis is a good thing. It lets Google get some good press, and also a MUCH more thorough real-world trial than they could do in house.
In a way, it's somewhat remniscent of the developers who worked on the flight software for the Space Shuttle computers [fastcompany.com]. Teams would actually compete to see who could find more bugs in the other team's code. This lead to some of the most robust and bug-free software ever written.
Re:A failure of conventional hack-ism ? (Score:4, Insightful)
If, however, this were Microsoft or Apple, they would not offer such high amounts as bounties as they would soon go bankrupt from the financial burden of paying out these bounties.
So, not only is Google saying "we are confident and proud of our product" they are also saying "we know there are bugs and even though we are confident in our products we are willing to pay out for people finding them".
Re:A failure of conventional hack-ism ? (Score:4, Interesting)
I'd love to see a more vibrant market for this. The cost paid per bug (perhaps normalized by product revenue) would be a really useful measure of software reliability.
Re: (Score:2)
Re: (Score:2)
I'd love to see a more vibrant market for this. The cost paid per bug (perhaps normalized by product revenue) would be a really useful measure of software reliability.
Interesting idea but for there to be a market there needs to be something liquid. You could say that only companies willing to have a (transparent) bug bounty program are running tight software ships but thats still not enough to convince everyone out there to start bounty programs. It's not about the net value of a bug in x program to x program's owner, it's the value of the time that random hackers have to devote to finding the bugs. The higher the price the harder it was to find (and theoretically the
Re: (Score:2)
Which is a much better position than "Let's pretend there's no bugs, and hush up anyone who says there is". Nice one, Google...
Re: (Score:2)
Bogus reports; either in the form of some hack trying to grub money or somebody reporting a bug that wasn't a bug at all, perchance? Considering the amount of money on offer, I can see both being pretty goddamn prevalent.
Re:A failure of conventional hack-ism ? (Score:5, Interesting)
What they're offering is still well below the $100,000 that a digital arms dealer like Vupen [forbes.com] charges for a year's subscription plan for exploits it discovers. And according to the Forbes article I linked to, some vulnerabilities individually cost several times more than that. It's so fucked up that NATO counties pay these security firms like Vupen, HB Gary Federal, etc. for exploits in the products of legitimate software companies for their use in cyberwarfare, espionage, and other nefarious shit. They'd rather leave everyone vulnerable, not even using the info they purchase to shore up their own government's systems lest the vulnerability become public and they lose the value of their purchase. If I were Google I'd save the bounty money and give it to their lawyers to create a tsunami of FOIA requests with every government they can to get the info about whatever exploits they have. Start a PR campaign letting the public know that their own government have knowledge that could help software companies make their products more secure for the computing public at large. Maybe if some influential people in the security field and tech firms complain loudly enough, something will change. I doubt it, but what hell else is there to do?
Re: (Score:2)
I like their entrepreneurial spirit:
Google security staffers responded by scolding Bekrar for disregarding users' privacy and called him an "ethically challenged opportunist."
Bekrar shrugs off the insults. "We don't work as hard as we do to help multibillion-dollar software companies make their code secure," he says. "If we wanted to volunteer, we'd help the homeless."
It is pretty hypocritical for somebody at Google to be challenging someone else for users' privacy.
Re: (Score:3)
If, however, this were Microsoft or Apple, they would not offer such high amounts as bounties as they would soon go bankrupt from the financial burden of paying out these bounties.
Microsoft has a more cost-effective way to deal with bugs: the MVP, aka as "unpaid Level 1 support staff unleashed on forums and blogs that accept to do Microsoft's work in exchange for a title, a pin and a secret handshake instead of a salary". And when MVP cannot solve a problem or find a serious bug, they simply push them on Microsoft Connect and wait for a Service Pack or a hotfix, like the Common People.
Apple has a similar program (maybe even more brilliant) but only at the marketing level and they pro
Having been an MVP... (Score:3)
I can tell you that it depends on which product group you are active in.
some teams like the C++ product group have (at least when I was an MVP) a very good relationship with their MVPs. this included getting developers to look at weird bugs, getting lots of interesting information, technical previews, etc. From my experience, the low level groups (SDK, DDK, C++) had a very active private community going with their MVPs.
For people interested in the product they were working with (C++ and SDK for me) being an
Re: (Score:2)
If, however, this were Microsoft or Apple, they would not offer such high amounts as bounties as they would soon go bankrupt from the financial burden of paying out these bounties.
Patently ridiculous. Both Apple and Microsoft make billions of dollars per year in profits. They could pay $100,000 per bounty and only owe $100 million for 1,000 security bugs.
Re: (Score:2)
Re: (Score:3)
Re: (Score:2)
I'm one of those people. Now that I can go poke around legally and possibly get paid if I'm lucky enough to find something I will. I'd do it even if there wasn't a cash prize.
Obligatory Dilbert (Score:3)
Bug bounty: http://dilbert.com/strips/comic/1995-11-13/ [dilbert.com]
Granted it's external rather than internal pay for a bug, but at $20k a piece, it wouldn't take a sleazy employee like ratbert long to figure out...
Re:Obligatory Dilbert (Score:4, Insightful)
Yes, I'm sure a Google employee will risk their $110k+benefits job and being unemployable for life in any major tech company to gain $20k.
Re: (Score:2)
$20k is a lot of pound notes.
Re: (Score:1)
20,000 (Score:2)
Carry on Google.. (Score:1)
Re: (Score:2)
That's not their motto.
Re: (Score:1)
Re: (Score:3)
Exactly; it's "Don't be evil", not "Do no evil". And if you think about it, the difference is huge.
Three reasons (Score:4, Insightful)
1. Bugs are getting harder to find, especially ones that can be exploited
2. Criminals are paying good money for quality exploits.
3. It's cheaper than hiring more people to do it.
show me the way! (Score:2)
Also a PR move (Score:1)
Aside from being good business sense on the accounting side of things, this is also a PR move. The hip company pays the nerds who can help them out taking advantage of the CLOUD! I mean crowd. Did I say cloud?
In Soviet Russia (Score:1)
Google bugs YOU!