> For the complete documentation index, see [llms.txt](https://docs.bugbase.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugbase.ai/program-guide/bug-bounty-dashboard/program-policy/editing-program-policy/best-practices-for-bounty-tables.md).

# Best Practices For Bounty Tables

Bounty tables are an important tool for program managers in a bug bounty program as it allows them to define the rewards for different types of vulnerabilities and scopes. By using bounty tables, program managers can incentivize hackers to focus on specific types of vulnerabilities or areas of the application that are most critical to their organization. This helps to ensure that rewards are paid out fairly for the severity and impact of the vulnerability.

Here are some best practices to follow when using bounty tables:

1. Prioritize the most critical vulnerabilities: Prioritize the most critical vulnerabilities by assigning higher bounties to them. This will encourage hackers to focus on finding and reporting these types of vulnerabilities first.
2. Be transparent: Clearly communicate your bounty tables and rewards to hackers. Make sure that they understand the rewards they can earn and the criteria for earning them.
3. Regularly review and update: Review and update your bounty tables regularly. This will ensure that the rewards are in line with the current threat landscape and the evolving needs of your organization.
4. Assign bounties according to the scope: Assign different bounties to different scopes based on their priority and impact on the organization.
5. Communicate the changes: Keep your hackers informed about any changes made to the bounty table.

By following these best practices, program managers can ensure that their bug bounty program is effective in finding and fixing vulnerabilities, and that hackers are fairly rewarded for their efforts.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bugbase.ai/program-guide/bug-bounty-dashboard/program-policy/editing-program-policy/best-practices-for-bounty-tables.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.