Before launching a program with HackerOne, it’s important that known unremediated issues are imported into the platform to properly identify duplicate reports when they come.
To import these unremediated vulnerabilities, you can import a CSV file or use our API. These instructions are for the CSV file. The file needs to be correctly formatted with details of each vulnerability to your program manager. Enterprise customers have the option to perform a continuous import of vulnerabilities.
Note: All vulnerabilities to be imported should currently be unremediated and be in scope for your program.
Your CSV file should follow the format listed below:
Note: You don't need to include all columns when importing your vulnerabilities unless you want to provide additional details. But, be sure to include all of the required columns as shown in the image above.
Here’s a table to help you see which fields are required and what should go underneath each field:
Field | Details | Accepted Values | Example |
title | (Required) The title of the vulnerability report | Any string < 150 characters | Reflected XSS on q parameter at search.example.com |
description | (Required) All information required in order to reproduce the vulnerability and understand the impact. Include any relevant endpoints and parameters. As this is a multi-line field, wrap your input in quotes. | Any multi-line string | "# Summary
The endpoint at
# Steps to reproduce
|
state | (Required) Whether the report is open or closed | The word Open or Closed | Open |
substate | (Required) The specific substate of the report - whether the report is new, triaged, resolved, etc. | You can choose from: new, triaged, needs-more-info, resolved, not-applicable, duplicate | triaged |
hacker_email | (Optional) The email address of the hacker. By including the email address, HackerOne is able to send an invite to the hacker to claim any report they've submitted. | A valid email address | |
severity_score | (Optional) The severity rating of the report. | A decimal number between 0 and 10 | 7.2 |
priority | (Optional) The severity rating description label. | You can choose from: none, low, medium, high, critical | medium |
view_reference_url | (Optional) The link to the report in your ticketing system (when the reference URL integration is not set up). | A valid URL | |
reference | (Optional) The reference to the report in your ticketing system. | A string < 255 characters | BBP-1234 |
asset_identifier | (Optional) The asset identifier that can be linked to an asset defined on HackerOne. | A string | ".hackerone.com" |
weakness_name | (Optional) The name of the weakness for the vulnerability. You can choose from HackerOne's subset list from the Common Weakness Enumeration (CWE)list. | A string matching the name from the CWE list | Cross-Site Request Forgery (CSRF) |
created_at | (Required field if the report state isn't closed) The timestamp of when the report was submitted | Timestamp in the format: YYYY-MM-DD
You can also include hours/minutes/seconds in 24-hour format: HH:MM:SS | 2020-09-18 |
triaged_at | (Required field if the report state isn't closed) The timestamp of when the submission was triaged. | Timestamp in the format: YYYY-MM-DD
You can also include hours/minutes in 24-hour format: HH:MM | 2020-09-18 |
closed_at | (Optional) The timestamp of when the submission was closed. | Timestamp in the format: YYYY-MM-DD
You can also include hours/minutes in 24-hour format: HH:MM | 2020-09-18 |
Common Mistakes
Here are some common formatting details that can break your CSV upload.
(Please double-check to confirm all formatting is correct before sending the CSV)
No formatting (bold, colors, cell merging, wrap text, etc.)
No commas
Do not change the column headers
Title must be less than 150 characters
Multi-line fields in CSV files need to be wrapped in quotes in order to keep their formatting
Dates must be formatted YYYY-MM-DD
Asset identifier name should match the asset in your program scope
Weakness type must match the weakness type title in the HackerOne submission form
All known issues should currently be open and confirmed valid (open, triaged) and should only be related to in-scope assets in your program.
Required fields: title, description, state, substate, created_at, triaged_at