4 ms·
This is similar to Katie Moussouris's argument from the article: > Moussouris, who created the bug bounty at Microsoft, warned that if badly implemented such p
by geofft 8y ago
This is similar to Katie Moussouris's argument from the article:
> Moussouris, who created the bug bounty at Microsoft, warned that if badly implemented such programmes could see talent leaving organisations in favour of pursuing bug bounties, and thus damage the talent pipeline.
I've seen her argue this on Twitter before - the argument IIRC is that bug bounties should always pay less than getting a job helping the blue team / writing secure code in the first place, otherwise the incentives are all wrong. It's great that you know about bugs, but it would be better not to have them. And, also, there's a bit of a prisoner's dilemma involved in that you don't want to let the rest of the industry drive up the expected payouts of bug bounties beyond the expected salaries of secure developers, but you also don't want to lose out on vulnerability reports either.
- yen223 8y agoStep one: Work at a company with a bug bounty program Step two: Introduce subtle vulnerabilities Step three: Claim bug bounty under a pseudonym (or just get someone else to claim it)
- nickpsecurity 8y agoThat's actually a great spin on old concept of subversion. I wonder if anyone is doing it. It should be easier for C apps where someone could say they didn't know about a specific kind of undefined behavior.