Overview
This article addresses frequently asked questions about importing findings into Hyver using a CSV file. Whether you're moving data from a pen test report, spreadsheet, or non-integrated security tool, this guide helps clarify key steps and limitations.
Can findings be imported into Hyver from non-integrated sources?
Yes. You can import findings from external sources like pen testing reports, risk registers, or tools that don’t currently integrate with Hyver.
Just export the data into a CSV file using Hyver’s structured template and import it directly into the platform.
Is there a size limit for uploaded files?
Yes. The maximum file size for imports is 50MB.
If your file exceeds this limit, split it into smaller files before uploading.
What file formats are supported?
Hyver currently supports CSV files only for importing findings.
How does Hyver handle column names and field mapping during import?
When importing a file:
The column names in your CSV (top row) must be mapped to Hyver fields in the interface during the import step.
Some fields are mandatory and must be mapped to proceed.
If required mappings are missing or incomplete, Hyver will generate an error and block the import until resolved.
What if a client’s field names don’t match Hyver’s fields?
If there’s a mismatch, the data must be aligned with Hyver’s field structure using the import interface.
Any unmapped fields will be ignored, and if required fields are missing, the import will fail until corrected.
Which metrics are affected by imported findings?
Imported findings affect core Hyver metrics, including:
Exposure
Cybersecurity maturity
These findings are included in dashboards, reports, and risk calculations — helping provide a more complete view of your security posture.
Wrap-up / Next Steps
Importing findings is a powerful way to bring in data from across your security ecosystem. Just make sure your file format and fields match Hyver’s template for a smooth experience.