Overview
Findings are the foundation of cyber risk analysis in Hyver — and there are several ways to add them. This article explains all five supported methods for adding findings to your environment, including when to use each method and how they differ.
Whether you’re uploading existing data, documenting vulnerabilities manually, or relying on integrations, this guide helps you choose the best path based on your workflow.
Prerequisites:
To add findings, you’ll need access to Hyver and the correct user permissions. Some methods (like importing or editing existing findings) also require Admin or Editor roles within the relevant engagement.
Navigating This Article
To help you find what you need, we’ve organized this guide around the three main ways findings can be added to Hyver. Each method is covered in detail below:
Importing findings from external sources
This method is ideal for uploading findings from tools that aren’t directly integrated with Hyver. While the process is straightforward, it involves multiple steps — so in this section, we’ll give you a high-level overview and link out to the full, step-by-step guide. It’s a powerful option if you’re migrating or consolidating existing data.Creating findings manually in Hyver
You can also add findings directly from the Findings page. After clicking the + button, you’ll be asked to choose one of two options:Start from a template (with pre-filled fields)
Start from scratch (with a blank form)
We’ll explain both of these in detail, including when and why to use each one.
Receiving findings from integrations
Findings can also arrive automatically through integrations with external tools like cloud platforms, vulnerability scanners, or ticketing systems. These findings appear alongside manually created ones — we’ll explain how this works and how to filter by source.
Let’s walk through each method so you can decide what works best for your workflow.
1. Import Findings from External Sources
Import findings using a CSV file — ideal for migrating from other systems or consolidating data outside existing integrations.
This method is useful when:
You’re moving from another platform or spreadsheet
You want to bulk upload a large number of findings
The source tool doesn’t integrate directly with Hyver
The import tool supports:
Field mapping with reusable templates
Inline validation and editing
Handling of errors, duplicates, and restricted data
To learn more:
See Import findings into Hyver from external sources for a full step-by-step guide.
2. Creating findings manually in Hyver
Manual creation gives you full control and flexibility — useful when documenting findings discovered outside of automated tools or integrations.
How to Start Adding a Finding
To begin, go to the Findings page from the main navigation menu.
At the top of the screen, click the + button. This opens the Create a New Finding wizard:
The first time you open it, you’ll see a short explanation of how the process works. You can choose to hide this message in the future by selecting “Don’t show this again” — totally up to you:
Click Start to proceed.
This is where you’ll choose how to create your finding. You have two options:
Blank Finding — start from scratch and fill in all fields manually
Template — choose from Hyver’s library of predefined templates, then customize as needed:
If you click Blank, you’ll enter a fully empty form where you can define the finding in your own words.
If you choose a template, many of the fields will already be filled in — but everything is editable.
We’ll walk through both of these options in the next sections.
2.1 Using a Template to Create a Finding
Use Hyver’s built-in library of predefined templates to speed up the process.
Templates include:
Pre-filled fields with expert-vetted values
Standardized structure for consistency across teams
Once you’ve selected a template from the list, Hyver opens the creation wizard with many fields already pre-filled. These values are pulled from our internal knowledge base and can be edited as needed.
Some fields are required — such as:
Engagement
Remediation Effort
Primary Framework (under the Maturity section)
Be sure to review and complete these before moving on.
You’ll also see optional fields, like description and Business impact, which you can edit yourself — or enhance using Hyver’s built-in AI suggestions. Just click the AI icon to rephrase or shorten the content automatically:
When you're ready, click Next.
This takes you to the Additional Data section. These fields are entirely optional and include things like:
Tags
CVSS Vector
Kill Chain
And other metadata that may be relevant to your workflow
You can choose to fill them in now, or skip them for later.
Once you're finished, click Done:
Hyver will then confirm that your finding was successfully created. From there, you’ll be able to:
Add remediation assets (either manually or via CSV)
Share the finding with others in your organization
View or edit the finding as needed
Note: The user who creates the finding is its default owner. If others need to view or collaborate on it, you’ll need to share it explicitly.
2.2 Creating a Finding from Scratch
If your use case isn’t covered by an existing template, you can start with a blank form and fill in all details manually.
This is best when:
The vulnerability is unique or highly specific
You want to customize every field from scratch
When you choose the Blank Finding option, the process is nearly identical to using a template — the main difference is that all fields start empty, and you'll be filling in every detail manually.
You’ll see the same layout, including required and optional fields. The required fields in the Overview tab include:
Summary
Description
Engagement
Severity
Type
Primary Framework
Once you've filled these out, you can click Next to continue, or Done to finish immediately.
Just like with templates, you can optionally use Hyver’s AI tools to help with writing or refining your summary and description. Click the AI icon to rephrase or shorten the text.
If you continue to the Additional Data section, you’ll find optional fields such as:
Tags
CVSS Vector
Kill Chain
And more
You can complete them now or leave them for later.
After clicking Done, you’ll land on the confirmation screen. From here, you can:
Add remediation assets (manually or by uploading a CSV)
Share the finding with teammates
Attach supporting evidence
View or edit the finding at any time
Tip: As the creator, you’re the only viewer by default. To collaborate or delegate, make sure to share the finding.
3. Findings from Integrations
Findings can also be added automatically through one of Hyver’s supported integrations. These allow external tools to send relevant findings directly into Hyver — no manual input required.
Currently supported tools include:
Cloud & Infra: AWS, Azure, Defender for Cloud
EDR & VM: Crowdstrike Falcon, Defender for Endpoint, SentinelOne, Tenable VM, Rapid7 InsightVM, Qualys VMDR
AppSec & Identity: WIZ, Active Directory, Storm
Awareness & Tickets: KnowBe4, Jira, ServiceNow
Depending on the integration, findings may be ingested automatically and assigned to relevant engagements based on configuration. They appear alongside other findings on the Findings page.
To view findings from a specific integration:
Use the Source filter on the Findings page
Select the relevant tool (e.g., SentinelOne or Jira)
For more on setting up or managing integrations, refer to Hyver Integrations Overview.
Wrap-up
Every organization works differently — and Hyver gives you flexibility to match. Whether you’re importing at scale, documenting manually, or syncing from external systems, the goal is always the same: get a clear, complete view of your cyber risk.
Feel free to experiment with each method, or stick to the one that fits your workflow. You can always switch approaches later or combine them as needed.
If you’re unsure which method to use — start with a template. They’re fast, easy to customize, and designed to get you moving quickly.












