Findings CSV Export
Export all findings from a test as a CSV file for use in external tools, ticketing systems, and custom workflows.
The Findings CSV Export provides a flat-file export of all findings from a given test. It is useful for importing findings into external tools, building custom reports, or processing data programmatically.
Columns
| Column | Description |
|---|---|
| ID | Unique hex identifier for the finding (e.g. 0x57c9). Links directly to the finding in the Ethiack Portal. |
| Title | Name of the vulnerability. |
| Asset | The asset the finding was discovered on. |
| Status | Current workflow status: triaged, informative, fixed, or open. |
| Severity | Severity level: critical, high, medium, low, or none. |
| CVSS | Numeric CVSS score (0.0–10.0). |
| CVSS Vector | Full CVSS vector string (e.g. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). May be empty for findings without a standard vector. |
| CWE | CWE identifier for the vulnerability class. -1 indicates no CWE mapping. |
| CVE | CVE reference, if the finding is tied to a known vulnerability. Empty if not applicable. |
| Created | Timestamp of when the finding was first recorded (UTC). |
| URL | Direct link to the finding in the Ethiack Portal. |
Notes
- The file uses
;as the column delimiter. - All findings from the test are included regardless of status — active, triaged, and informative findings all appear in the export.
- Findings without a CVSS vector or CWE mapping will have empty or
-1values in those columns respectively. - The ID and URL columns can be used together to cross-reference findings between the CSV and the Portal.
PCI DSS Report
A compliance-specific report mapping findings to PCI DSS control requirements, designed for QSAs, payment processors, and internal compliance teams.
Asset Inventory
Export a full inventory of all assets in your organization's surface, including type, importance, infrastructure details, and discovery date.