Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is a Bug Bounty Programme?

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.

Illustration for the cybersecurity term Bug Bounty Programme
Home / Blog / Cybersecurity Terms / What Is a Bug Bounty Programme?
17 November 2026

What Is a Bug Bounty Programme?

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.

From Netscape to the Pentagon

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.

How a Programme Runs

  1. Scope and rules. You define which assets are in scope (for example *.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.
  2. Safe harbour. A clear statement that good-faith research within the rules will not lead to legal action. In the UK this matters because unauthorised access is an offence under the Computer Misuse Act 1990.
  3. Submission and triage. Researchers submit reports; a triage team—yours or the platform’s—reproduces the issue, removes duplicates, and rates severity, usually with CVSS.
  4. Remediation and reward. The bounty is paid, the flaw is fixed, and the researcher may be allowed to disclose publicly once a patch is available.

Bug Bounty, VDP, or Penetration Test?

These three are often confused, but they answer different questions.

AspectVulnerability disclosure policy (VDP)Bug bountyPenetration test
PaymentNone, or recognition onlyPer valid findingFixed fee for the engagement
TimingAlways openContinuous or time-boxedAgreed testing window
TestersAnyone who finds an issuePublic crowd or invited researchersNamed, vetted consultants
CoverageOpportunisticWherever rewards are highestSystematic, against a defined methodology
Audit evidenceLimitedLimitedFormal 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.

Public or Private

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.

Before You Launch

What Good Looks Like

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.

FAQ – Frequently Asked Questions

How Much Should I Pay for a Bug Bounty?

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.

Is a Bug Bounty Programme a Substitute for Penetration Testing?

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.

Can a Researcher Be Prosecuted for Testing My Site?

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.

What Happens if a Researcher Finds Personal Data?

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.

Related Terms

You May Be Interested In These

What Is Havoc C2?

Cybersecurity Terms

17 November 2026

What Is Havoc C2?

Read More
What Is VERBIS?

Cybersecurity Terms

17 November 2026

What Is VERBIS?

Read More
What Is Root Cause Analysis?

Cybersecurity Terms

17 November 2026

What Is Root Cause Analysis?

Read More