Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A bug bounty programme pays independent security researchers for valid vulnerability reports. Learn how programmes run and how they compare with a VDP and a pen test.

What Is a Bug Bounty Programme?
A bug bounty programme is an arrangement in which an organisation invites independent security researchers to find vulnerabilities in its systems and pays them for valid, responsibly reported findings. Rewards scale with severity, so a critical remote code execution flaw earns far more than a missing security header. Run well, a programme gives you continuous testing from a large and varied pool of skills; run badly, it gives you a flood of noise and a growing backlog.
Netscape launched what is generally regarded as the first bug bounty in 1995, for its Navigator browser. Google’s Vulnerability Reward Program followed in 2010, and the US military’s “Hack the Pentagon” pilot in 2016 showed that even defence bodies could work productively with outside hackers. Today most programmes run through platforms such as HackerOne, Bugcrowd, Intigriti, and YesWeHack, which handle researcher vetting, triage, and payment.
*.example.co.uk, but not a third-party payment page), which tests are banned (denial of service, social engineering, physical access), and how findings must be reported.These three are often confused, but they answer different questions.
| Aspect | Vulnerability disclosure policy (VDP) | Bug bounty | Penetration test |
|---|---|---|---|
| Payment | None, or recognition only | Per valid finding | Fixed fee for the engagement |
| Timing | Always open | Continuous or time-boxed | Agreed testing window |
| Testers | Anyone who finds an issue | Public crowd or invited researchers | Named, vetted consultants |
| Coverage | Opportunistic | Wherever rewards are highest | Systematic, against a defined methodology |
| Audit evidence | Limited | Limited | Formal report with coverage and risk ratings |
A VDP is the baseline. Publishing one, together with a security.txt file as described in RFC 9116, tells finders where to send reports. For manufacturers of consumer connectable products sold in the UK, the Product Security and Telecommunications Infrastructure (PSTI) regime, in force since 29 April 2024, makes a published vulnerability disclosure policy a legal requirement. ISO/IEC 29147 and ISO/IEC 30111 describe how to receive and handle reports.
A bounty adds financial incentive on top. It does not replace a penetration test: researchers chase the findings that pay best, rarely test authenticated business logic in depth, and will not produce the scoped, methodical evidence that PCI DSS or ISO 27001 auditors expect.
Private, invitation-only programmes suit organisations that are starting out: a small group of proven researchers, a manageable volume of reports, and time to tune internal processes. Public programmes open the doors to anyone on the platform, increasing coverage and noise in roughly equal measure. Many organisations run privately for a year or more before going public, and some never do.
Healthy programmes measure time to first response, time to fix, and the ratio of valid to invalid reports, and they feed recurring findings back into secure development training so the same class of bug stops appearing. Researchers notice how they are treated: fast, respectful triage and fair payouts attract the best talent, while slow or dismissive handling drives them away and can turn a private report into a public complaint.
Most mature organisations combine all three approaches: a VDP for everyone, a bounty for broad, continuous coverage, and scheduled penetration test services for depth and compliance evidence.
Rewards depend on severity, asset value, and how competitive you need to be for researchers’ attention. Smaller programmes may pay a few hundred pounds for medium issues and a few thousand for critical ones, while large technology companies pay far more. Publish a clear reward table by severity, budget for platform fees and triage effort, and remember that low payouts attract less experienced researchers and more noise.
No. A bounty provides broad, ongoing coverage, but researchers focus on whatever pays best and rarely test every function, authenticated workflow, or internal system. A penetration test follows an agreed scope and methodology, covers areas a crowd would not reach, and produces the formal evidence auditors and regulators expect. Most organisations use a bounty to complement scheduled penetration tests rather than replace them.
Unauthorised access is an offence under the Computer Misuse Act 1990, and the Act contains no general public-interest defence for security research. A well-written programme reduces the risk by explicitly authorising testing within a defined scope and promising not to pursue good-faith researchers who follow the rules. Researchers who go beyond the published scope lose that protection.
Your rules should tell researchers to stop, access no more data than needed to prove the issue, report immediately, and delete anything they retained. On your side, treat the finding as a potential personal data breach: assess the risk, decide whether the ICO must be notified within 72 hours under UK GDPR, and record your reasoning even if notification is not required.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.