Skip to main content
Be Bitwise

Choosing Your First Programme

Bug Bounty Fundamentals · Bug Bounty track

4 min read

In this module

Finding the Right Target

Your first programme choice quietly shapes the next several months. Pick something too competitive and you'll grind for weeks with nothing to show. Pick something too narrow and you'll exhaust the surface in days. This lesson is about reading a programme page like a researcher and choosing one where you actually stand a chance.

Evaluating a Programme

Every programme page on HackerOne or Bugcrowd shows you the same handful of fields. Read them critically:

Scope width is the attack surface on offer. A programme scoped to *.example.com hands you every subdomain the organisation runs — potentially hundreds of web applications, APIs, and miscellaneous services. One scoped to a single URL like https://app.example.com boxes you into a single application. Wider scope, more places to poke.

Response time tells you how the organisation actually behaves once you submit. Platforms publish metrics for time to first response, time to triage, and time to bounty. Programmes that take weeks or months frustrate researchers and stall your payment. Aim for first responses inside a few days.

Payout table is what they're paying for each severity. Compare against platform averages. Some programmes pay well above market for critical findings, others lag across the board. Factor in competitiveness, too. A lower-paying programme with empty attack surface often beats a generous one where every endpoint has been pawed over by hundreds of researchers.

Programme age and report volume are indirect tells. A programme that's been live for years with thousands of resolved reports has had its easy findings stripped clean. A newer programme, or one that recently expanded its scope, may still have fresh territory.

Starting with VDPs

For your first programme, pick a Vulnerability Disclosure Programme rather than a paid one. Sounds backwards, but there are good reasons:

  • Lower competition: experienced researchers chase money, leaving VDPs underpopulated
  • More forgiving process: you learn how to write reports, interact with triage, and handle the submission workflow without payout pressure
  • Building reputation: valid VDP reports generally still build your platform track record, though bounty-based metrics such as HackerOne's Impact only grow with paid reports; check how your platform scores them
  • Broader scope: many VDPs accept reports on a wider range of assets than their paid counterparts

Once you've shipped several valid reports through VDPs and have a feel for the full bug lifecycle, switch to paid.

Wide Scope vs Narrow Scope

Why Wide Scope Favours Beginners

Programmes with wide scope (wildcard domains, multiple applications, mobile apps, APIs) provide a larger attack surface. This means more potential targets and a higher chance of finding overlooked assets. When a programme includes all subdomains, you can discover forgotten staging environments, legacy applications, and internal tools that have received less security scrutiny than the main product.

Narrow-scope programmes box you into a small, well-defined set of assets that dozens of researchers have already crawled over. What's left tends to be subtle logic flaws and complex chains that demand deep application knowledge. That suits the specialist who lives inside one app, not the new arrival.

As a beginner, lean wide. Your reconnaissance skills (covered in Bug Bounty Methodology) are how you find the dusty corners everyone else missed.

Reading Disclosed Reports

The single most useful learning resource on any platform is the disclosed reports archive. When a vulnerability is fixed and the bounty paid, some researchers opt to make their report public. You get to read exactly what was found, how it was tested, and how it was written up.

Study disclosed reports for programmes you're considering. They reveal:

  • What vulnerability classes are commonly found in that programme's technology stack
  • What severity ratings the programme assigns to different issue types
  • The quality standard expected in reports (level of detail, proof of concept, remediation suggestions)
  • Which areas of the application have already been tested (so you can focus elsewhere)

On HackerOne you can filter disclosed reports by programme. On Bugcrowd, hunt down researcher write-ups and blog posts. Read a few each week. You'll absorb methodology, tooling, and reporting style from researchers at every skill level — and the price of admission is your reading time.

Practical Selection Checklist

Before committing to a programme, confirm these points:

  1. The scope is wide enough to give you room to explore
  2. Response times are reasonable (first response under one week)
  3. The payout table is fair for the effort required
  4. The programme has a clear safe harbour or legal protection clause
  5. There are disclosed reports you can study for context
  6. The technology stack aligns with your current skills (web, mobile, API)

Once you've narrowed it down to two or three candidates, commit to one for at least a fortnight of focused testing before switching. Hopping between programmes is the fastest way to never develop the application familiarity that real bugs are hiding behind.