Overview
This article provides a general overview of how asset importing works in Hyver. You’ll learn what types of assets can be imported, how they're used, and where they show up across the platform. A separate article covers the exact steps for performing the import.
1. What importing does
Hyver allows you to import regular assets from external tools using a CSV file. Once imported, these assets appear in the platform just like automatically discovered assets — in the Assets list, the Mitigation Graph, and other views.
Imported assets are fully integrated and treated like any other potential access point.
2. What can be imported
This process supports importing technical assets, such as:
Servers
Routers
IP addresses
Domains
Applications
Any other access points
Important: This does not apply to Business assets (e.g., intellectual property, customer data, or employee records). Those are managed separately.
3. File format requirements
Your import file must be in CSV format
Fields must be separated by commas
A wizard will guide you through field mapping during the import process
Using a template is optional, but helpful for consistency
4. Where imported assets appear
After import, assets are visible across Hyver’s core views:
Assets list
Mitigation Graph
Findings association, if linked manually or via matching criteria
Important notes
This article is focused on concept and context. For step-by-step instructions, refer to the linked article below.
All imported assets behave exactly like discovered assets — you can edit, tag, or assign them to findings as needed.
Wrap-up / Next Steps
Importing assets gives you flexibility to include data from outside systems — no need to rely on automatic discovery alone. Whether you're enriching an engagement or syncing from another tool, this capability keeps your view complete and current.
Related articles
See also: [Import Assets (CSV)]
