Export a table to CSV
Export the data in an incidents, issues, or observations table to a CSV file so you can analyze it, share it, or load it into other tools. The file includes the filters you applied and every available column, not only the columns shown in the table.
Before you begin
Actions and permissions lists the permissions you need to view and export data.
Steps
In the left navigation, select Incidents, Issues, or Observations.
To limit the export to specific data, select the Filter icon and choose one or more filters. The export includes only the data that matches your active filters.
Select Export and then CSV.
Wait for the download to finish. Your browser might be unavailable while Contrast generates the file.
Open the file in a spreadsheet application or other CSV reader.
What the CSV file contains
Filtered data: The file includes every row that matches your active filters, across all pages of the table, up to a maximum of 50000 rows. A header row at the top of the file lists the filters you applied.
All columns: The file includes every available column, not only the columns shown in the table.
Counts for multiple values: When a table cell holds more than one value, the file shows the number of values. For example, the related issues for an incident appear as a count.
Time zone: Date and time values use the time zone.
File name: The name is Contrast Security - Issues - [timestamp].csv, where the timestamp is the download time. If you applied any filter other than time, the name is Contrast Security - Issues - filtered - [timestamp].csv. The table name changes to match the table you export.
Column reference
The file contains these columns. Definitions match the descriptions in the view topics for each table.
Column | Incidents | Issues | Observations | Description |
|---|---|---|---|---|
Incident ID | Yes | Identifier in the format INC-<year>-<number> | ||
Incident name | Yes | The type of incident, for example, SQL Injection | ||
Issue ID | Yes | Identifier in the format ISS-<year>-<number> | ||
Issue title | Yes | The issue type and location | ||
Observation ID | Yes | Identifier that Contrast assigns to the observation | ||
Title | Yes | The Contrast rule or event description for the observation | ||
Associated issue ID | Yes | The issue that includes the observation | ||
Severity | Yes | Yes | Yes | The severity that Contrast assigns |
Contrast score | Yes | Yes | The risk of the issue or incident at a point in time | |
Status | Yes | Yes | Open or Closed | |
Application/Repository | Yes | Yes | The application or repository where Contrast found the data | |
Application | Yes | The application the incident affects | ||
Assigned to | Yes | The person assigned to investigate the incident | ||
Time created | Yes | When Contrast created the incident | ||
Last updated | Yes | The last time Contrast updated the incident | ||
Number of observations | Yes | How many times Contrast observed the issue | ||
Last detected | Yes | The last time Contrast detected the issue | ||
Detected | Yes | When Contrast detected the observation | ||
Most recent incident | Yes | The date of the most recent incident for the issue | ||
Environments | Yes | Yes | Development, QA, or Production | |
Environment | Yes | Development, QA, or Production | ||
Source IP | Yes | The IP address where the event originated | ||
Result | Yes | The outcome of an attack event, such as Exploited, Blocked, or Probed | ||
Value | Yes | The attack value. Vulnerability observations have no value | ||
Behavior type | Yes | The type of behavior observation | ||
Data type | Yes | Yes | Vulnerability, attack, or behavior | |
Target | Yes | Yes | What Contrast analyzed: code or library | |
Sensor | Yes | Yes | How Contrast detected the data | |
Technique | Yes | Yes | The analysis technique: static or runtime | |
Quantum unsafe | Yes | Whether Contrast observed a quantum-unsafe algorithm | ||
Language | Yes | The language of the code associated with the observation | ||
Results | Yes | The results detected for the issue |