# Bug Bounty

The Resolve Platform's bug bounty workbench: public bounty reports across platforms, the researchers and weaknesses behind them, and reports naming your CVEs.

**Threat Intel › Bug Bounty** (`/resolve/bug-bounty`) aggregates the public bug bounty record from HackerOne, Bugcrowd, Intigriti and other platforms. It answers whether a vulnerability in your stack has been reported and paid for, which weaknesses attract bounties, and who reports them. A paid public report is evidence that a vulnerability is understood and worth an attacker's time.

## The lens

The headline is the number of bug bounty reports on record, split into **With a bounty listed** and **No bounty listed**. The lens also switches between the four views.

## Views

### Your CVE matches

Public bug bounty reports that name a CVE already in your scanner results.

| Control | Does |
|---|---|
| Search | **Search CVE, title or platform** |
| Bounty filter | **All** or **With a bounty** |

The inspector shows **The report**: CVE, platform, reporter, team, state, weakness, bounty and disclosed date, with **Open report** and **Look up** for the CVE in Search Console.

### Researchers and teams

Every individual and team on the public record as one queue.

| Control | Does |
|---|---|
| Type | **All**, **Individuals** or **Teams** |
| Platform | One platform or all |
| Search | **Search name or platform** |
| Sort | **Total earned** (default), **Submissions**, **Average bounty** or **Name**, ascending or descending |

The inspector shows **Standing** (rank overall, rank in this view, submissions, total earned, average bounty, and largest bounty for an individual), how the entry compares against its own platform (share of platform reports, platform average, against the average), and a **Severity mix**.

### Platforms and trend

Which platforms the reports come from, and how many were filed and paid each month over 12, 24 or 36 months. Pressing a platform opens **Researchers and teams** filtered to it. Each month bar is a button, and a readout states the month in words.

### Weakness map

A heatmap of the CWEs the reports are about, above a ranked queue. Rank by reports or by average bounty, shade by either, and choose how many weaknesses to show. Search by CWE id, such as `79`. The inspector says **How it ranks** against all weaknesses: reports, share of reports and average bounty. Shade follows rank, and each cell also shows its number.

The view, filters, sort, page and open row are kept in the address bar, so a copied link opens a colleague on the same row.

## Plan

The public bounty data (researchers, platforms, trend, weakness map) is open to everyone, signed in or not. **Your CVE matches** needs **Pro** or above because it reads your organisation's findings. Below Pro it shows sample data behind an upgrade prompt.

## Related

- [Exploit Database](/vulnerability-management/intelligence/exploit-database.md) shows **Bounty** as one of its evidence tiers.
- The same data is in the [Vulnesis API](/vdb-api.md).
