Exporting project data¶
The platform offers exports at two levels: a single table, or the whole project.
Exporting a single table¶
The result tables in Scope, Assets, Intel, and Darknet carry an Export control above the table on the right. Tables in Discovery do not support table exports.
Administrative and overview tables, such as the projects overview, Search Jobs, the Companies tabs, and the Administrator Settings tabs, offer only Manage columns and, where applicable, Filter; use the project-level export or the API for those.
- Apply the filters that define the set of rows you want.
- Select Export.
- Choose JSON or CSV.
The export contains the rows matching the current filter and the columns currently shown, which makes the column selection and the filter part of the export definition. See Working with the interface.
| Format | Suitable for |
|---|---|
| CSV | Spreadsheets, reporting, and ticket imports. |
| JSON | Scripts, pipelines, and further processing that requires nested attributes. |
Exporting a whole project¶
The Export control in the project header offers two options.
| Option | Result |
|---|---|
| Excel | A workbook containing the results of the project across the individual views. Suitable for a report or a handover. |
| Export project | A complete export of the project data. Suitable for archiving or for processing outside the platform. |
When the project has e-mail security results, the Excel workbook also contains the sheet Email Security with the ratings of every mail domain. The E-mail security sub-tab itself exports its results as JSON.
Practical notes¶
- Apply the filter first, then export. Exporting a large unfiltered table and filtering afterwards produces files that are harder to review and to share.
- The export reflects the state at the moment of the request. Where a project is under active monitoring, note the date of the export in your report.
- Exports may contain personal data from Intel and credentials from Darknet. Treat the files as confidential and store them accordingly.