BugBase Documentation
  • πŸ‘‹Welcome to BugBase Docs
  • Overview
    • πŸ’‘What we do
    • ⚑Changelogs
    • ✨Our Features
    • πŸ“‚Programs at BugBase
      • Vulnerability Disclosure Program (VDP)
      • Bug Bounty Program
      • Private Bounty Program
      • Pentest Program (VAPT)
  • Report Lifecycle
    • Bug Report
    • Report Status
  • How To
    • πŸ‘¨β€πŸ’»Invite Organization Members to BugBase (RBAC)
    • 🚩Setup a Campaign for better program engagement
    • πŸ›Submit a Bug Report on BugBase
    • πŸ“‘Create a Bug Bounty Program on BugBase
    • ⬇️Download the mobile app
  • Company Guide
    • πŸ‘¨β€πŸ’ΌCreate a Company Account
    • 🧭Navigation
    • πŸ›‘οΈAssets Dashboard
    • πŸ—οΈCredential Vaults
      • Creating a Credential Vault
      • Adding Credentials to Vault
      • Connect Credential Vault to an Asset
      • Require Whitelisting for a Credential
    • πŸ”VPN Servers
      • Create, Configure and Deploy VPN server
      • Monitor Live Statistics and Logs
    • πŸ—‚οΈPrograms Dashboard
      • β›³Create a Program
    • πŸ“’Customer Support
    • πŸ’΅Bounty Bin
    • βš™οΈCompany Settings
      • πŸ‘¨β€πŸ«Profile
      • 🏒Organisation
      • πŸ‘¨β€πŸ­Roles and Permissions
      • πŸ”Security & Authentication
        • Multi-Factor Authentication
        • SSO with SAML
          • Okta SSO setup via SAML
          • Google SSO setup via SAML
      • 🎨Customization
        • Automations
        • Report Tags
      • πŸ“™Manage Access
    • πŸ“ˆInsights Dashboard
    • πŸ”ŠCampaigns
    • πŸ’²Understanding Currencies Used in BugBase
    • 🀝Whitelist
  • Program guide
    • Bug Bounty Dashboard
      • Program Reports Section
        • Report Components
        • Report Actions
        • Duplicating Reports
        • Assigning Swags
        • Assigning Bounties
        • Assigning Thanks to Reporters
        • Assigning Bonus Bounty
        • Automatic Response Generator using ChatGPT
      • Program Policy
        • Editing Program Policy
          • Best Practices For Designing Policy
          • Best Practices For Bounty Tables
      • Payouts
      • Settings
    • Private Bug Bounty Dashboard
      • Invite Hackers
      • Manage Credentials
    • VDP Dashboard
    • Pentest Dashboard
      • Pentest Overview
      • Vulnerabilities Section
        • Pentest Report Components
        • Pentest Report Actions
      • Global Pentest Chat
    • Competition Dashboard
      • Dashboard
      • Creating a Competition
        • Adding Challenges
      • Manage Competitions
        • Statistics
        • Leaderboard
        • Manage Users
  • Bounty Hunter Guide
    • Bounty Hunter Dashboard
    • Bounty Hunter Profile
    • Programs Directory
      • Program Policy Page
      • Credentials
      • VPN Access
      • Whitelist
      • Collaborate
    • Bounty Hunter Reports Section
      • Submitting Reports
      • Interaction with Program Representees
      • Collaboration
      • Response Generation through ChatGPT on Report Chat
    • Competitions
    • Discord Community
    • Leaderboard
    • Multi-Factor Authentication
    • Settings
      • Verify KYC
    • Email Alias
    • πŸš€Apollo Community
  • Integrations
    • πŸ”—Supported Integrations
    • Webhooks
    • JIRA
      • Creating a JIRA Issue
    • Slack
      • Managing Integration
    • Microsoft Teams
    • Github
    • Asana
    • Sumo Logic
    • PagerDuty
  • on-premise
    • Running Automated Testing
    • Sandbox Environment
Powered by GitBook
On this page
  • Steps to Assign a Bounty
  • Assigning Bonuses
  • Collaborative Reports
  • Best Practices for Awarding Bounties
  • Approval for Bounty Assignment:

Was this helpful?

  1. Program guide
  2. Bug Bounty Dashboard
  3. Program Reports Section

Assigning Bounties

PreviousAssigning SwagsNextAssigning Thanks to Reporters

Last updated 5 months ago

Was this helpful?

Assigning bounties is a way for program managers to reward security researchers for their contributions in finding and reporting vulnerabilities. These bounties are monetary rewards given to security researchers for identifying and reporting valid vulnerabilities.

In BugBase, program managers can assign bounties to hackers through the "Assign Reward" feature. This feature allows managers to choose the bounty amount and assign it to the hacker. Program managers can set up different bounty amounts based on the type or severity of vulnerabilities.

Steps to Assign a Bounty

  1. Navigate to the Report:

    • Open the specific report page to which you want to assign the bounty.

  2. Click on "Assign Rewards":

    • At the top of the report page, click the "Assign Rewards" button.

  3. Select Reward Type:

    • Choose either:

      • Bounty Only: Assign only a monetary reward.

      • Bounty + Swag: Assign a monetary reward along with swag to the security researcher.

  4. Enter Bounty Details:

    • Enter the bounty amount manually or select from predefined bounty amounts.

  5. Save Changes:

    • Click "Save Changes" to finalize and assign the bounty.

Currency for Bounties

  • Bounties are assigned in the public currency selected by the program admin for the program.

  • At the time of assignment, the public currency is converted to the banking currency.

Assigning Bonuses

Once a bounty is assigned to a report, it cannot be modified. However, program managers can assign a bonus to the security researcher as an additional reward.

To assign a bonus:

  1. Click the "Assign Rewards" button again.

  2. Select the option to assign a bonus.

  3. Enter the bonus amount.

  4. Click "Save Changes" to confirm.

Collaborative Reports

When vulnerabilities are reported collaboratively by multiple hackers, BugBase automatically splits the bounty among the contributors. The split is based on the percentage of contribution decided by the hackers themselves.

Best Practices for Awarding Bounties

  1. Follow Program Policy:

    • Award bounties as per the program's guidelines. Ensure the report is valid and non-duplicate before assigning the bounty.

  2. Reward Significant Out-of-Scope Findings:

    • Consider awarding bounties for out-of-scope vulnerabilities if they have a significant impact.

  3. Communicate Clearly:

    • If the awarded bounty differs from the program policy or if a bounty is declined, provide clear explanations to hackers. This offers valuable feedback and encourages better submissions in the future.

Approval for Bounty Assignment:

  • Company Admins can configure bounty approval settings under Company Dashboard > Settings > Access > People.

  • When bounty approval is required:

    • Bounties won’t be directly assigned.

    • The bounty assignment can either be accepted or declined by members who have the necessary permissions.

Learn more about public currency, preferred currency, and banking currency here.