-
Notifications
You must be signed in to change notification settings - Fork 15
usage hackerone
reNgine-ng automatically sends vulnerability report to the Hackerone program which the target belongs to, if it finds Critical or High vulnerability.
In order for reNgine-ng to achieve this, it needs 3 things.
- Your HackerOne Username
- Hackerone API Token
- And Target team_handle
To generate hackerone api token, visit the official documentation/instructions from Hackerone. https://docs.hackerone.com/hackers/api-token.html
Once you have generated your hackerone api token, you can add them to Hackerone Setting, under Settings menu from top navigation bar.
Team handle is a unique identifier for your target generated by hackerone. Suppose if your target belongs to a vulnerability program called 'Stripe', the target team_handle will be the 'stripe' generated from https://hackerone.com/stripe.
You need to add the team_handle to your target when you add, you can also update the target later.
How to add team_handle to your target?
Caution
team_handle must be provided to the targets for reNgine-ng to automatically report vulnerability.
You can also test hackerone api token to see if it works correctly. Once you have generated api token, you can verify by clicking on the button "Test my hackerone api key".
By default, reNgine-ng will report only Critical and High severity Vulnerabilities. You can choose to select what severity to report among Critical, High and Medium Severities.
You can customize the vulnerability report template using markdown. Replace the below syntax wherever you require. Curly braces are must!
-
{vulnerability_name}
Vulnerability Title/Name. -
{vulnerable_url}
Vulnerable URL. -
{vulnerability_severity}
Vulnerability Severity. -
{vulnerability_description}
Description of vulnerability generated by Nuclei. -
{vulnerability_extracted_results}
Vulnerabty Results extracted by Nuclei. -
{vulnerability_reference}
Additional Reference to vulnerability.
- Home - Introduction to reNgine-ng with workflows and features
- Installation - Install reNgine-ng in different ways
- Usage - Common usage and best practices
- Backup-Restore - Backup and restore reNgine-ng easily
- Dependencies - Information about used third-party libraries and tools
- Security - Security best practices and reporting issues
- Support - Troubleshooting guide and common issues
- Changelog - Complete changelog
- Community - Get help on social networks
- Contributing - How to contribute to the project
- Presentations - Materials regarding reNgine presented at conferences
- Screenshots - Collection of screenshots demonstrating features