First Setup

Change your password

The first thing to do is to change your login information by going to your profile /pages/user

Configure a Cloud Provider

SSH Key

An SSH key will be required by Hunt3r to deploy and manage your servers, however it is possible to configure a specific SSH key for Hunt3r and by provider

To be able to launch a scan you will first have to configure a Cloud Provider on the page /admin/cloud/settings.

Scaleway configuration

First of all it is necessary to add an SSH key on https://console.scaleway.com/project/credentials

As well as a Keys API for Hunt3r, still on the same page

AWS configuration

You need to add a user here with EC2 rights

You have to register your SSH key (without passphrase) here with the name 'hunt3r' (required), the key must be registered in the same region as the region used on the dashboard.

The default group security must be modified to allow SSH connections (Inbound rules) at least here

Nuclei configuration

If you want to use Nuclei, we advise you to use a custom configuration file to add template exclusions on /admin/tools/settings. In case no file is filled in, all templates will be used

If necessary, you can use our suggested configuration

Amass configuration

The last step is to add your Amass configuration on /admin/tools/settings, it is indeed not possible to start a scan without putting a configuration file. Since this tool is the heart of the recognition, we advise you to have as many API keys as possible.

See How to Use Amass More Effectively for Bug Bounties

The default configuration file can be found here.