Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
A bug bounty is a program in which you pay a reward to people who find and report weaknesses in your own systems. A bug is a mistake in a program. The NIST glossary gives the definition from SP 800-216: a way of paying rewards for reports of mistakes or flaws that could lead to security exploits or vulnerabilities.
How does a bug bounty work?
Imagine a restaurant that hands a gift voucher to anyone who points out a hygiene problem. The idea is to use eyes outside the shop to help protect it.
CISA's directive BOD 20-01 explains that in a bug bounty, an organization pays for valid, high-impact findings about certain kinds of vulnerabilities. The same directive treats a vulnerability disclosure policy, or VDP, as similar to a bug bounty but separate. A VDP permits good-faith research and promises to respond to reports. Both approaches rely on outside people who report what they find, and they differ in whether a reward is attached.
The directive is addressed to US federal agencies. It does not require agencies to run a reward scheme. It adds an explanation that money can also motivate people who would not otherwise look for vulnerabilities. To see what is visible from outside your own site first, use the free URL check.
Why does a bug bounty matter?
It may let outside eyes find holes that you cannot notice from inside. A clear point of contact for reports can also help the finder tell you before making the finding public.
On the other side, the load on the organization that runs one is not small. You need a team that receives reports, checks them, fixes the problem, and replies. If you announce a reward without such a team, you cannot handle the reports.
Testing another party's site without permission can become a problem. That is why the basic form is for the operator to state the range that may be tested and to give permission. The related law is explained in the Unauthorized Access Prohibition Act term page. The meaning of the word "weakness" is in the vulnerability term page.
Related terms
- Vulnerability: a weakness in software or settings that an attack can exploit
- Unauthorized Access Prohibition Act: the Japanese law against improper access that uses another person's ID
Next step
Before you think about such a program, confirm what is visible from outside with the free URL check. For how to find and fix holes, contact us. We can also discuss how to set up a contact point that receives reports.
Frequently asked questions
Are a bug bounty and a vulnerability disclosure policy the same thing?
No. CISA's directive BOD 20-01 says a disclosure policy is similar to a bug bounty but separate. A disclosure policy sets how reports are received and permits good-faith research, and it does not assume a reward.
Must I start a bug bounty?
You do not have to. CISA's directive does not require federal agencies to set up a bug bounty either. You can begin by preparing a contact point for reports and a procedure for handling them.
Frequently asked questions
Are a bug bounty and a vulnerability disclosure policy the same thing?
No. CISA's directive BOD 20-01 says a disclosure policy is similar to a bug bounty but separate. A disclosure policy sets how reports are received and permits good-faith research, and it does not assume a reward.
Must I start a bug bounty?
You do not have to. CISA's directive does not require federal agencies to set up a bug bounty either. You can begin by preparing a contact point for reports and a procedure for handling them.