Overview
This article introduces the Validation Step in Hyver’s Import Findings tool — a crucial step that helps you review, edit, and verify data before it enters your system.
If you’re uploading findings in bulk, especially in high-stakes or fast-paced workflows, this step ensures you stay in control and avoid unintended changes. The validation step has been part of Hyver for a while now — and with a fresh, more intuitive interface, it’s the perfect moment to explore the real value it brings.
What changed — and why it matters
Previously, when importing findings, users would only discover issues — such as overwrites, formatting errors, or failed rows — after the import was complete. This post-import feedback meant that unintended changes could go unnoticed, and correcting them often involved manual investigation and rework. The result: frustration, inefficiency, and potential disruption, especially when managing large volumes or collaborating across teams.
The new validation step introduces a much-needed pre-import review, giving you what was previously missing: clarity, visibility, and control. Instead of discovering issues after the fact, you can now review, edit, and confirm your data before it enters Hyver — making the entire process more confident, accurate, and efficient.
Validation happens before import.
Nothing enters your system until you confirm it. The validation step is exactly that — a pause point where you can review, edit, verify, and make decisions. You’re fully in control of what gets imported, and when.
Here’s what you can do now:
1. Review all data before it's imported
You now get a full picture of your data before it’s added to Hyver — including:
Logical errors: For example, entering “82” in the Severity field, which only accepts values like High, Medium, or Low.
Duplications: Findings that are already present in the system — identical entries under the same engagement — are flagged as duplicates.
Overwrites: Cases where the import will update an existing finding. In other words, you're about to write over a record that already exists.
Each of these is clearly flagged so you can review and decide how to proceed — before anything is imported.
2. Edit rows directly within the validation table
There’s no need to jump between windows. Once you upload and map your findings file, the validation step opens up an interactive table where you can double-click and edit values directly. It’s simple, fast, and intuitive — designed to save effort and reduce context switching.
Hyver AI support is on the roadmap.
We're always thinking ahead. In future releases, the validation step will become even smarter, with Hyver AI-powered suggestions and corrections built right in. This enhancement will add intelligence and ease to the editing experience, and will be available to customers with supported Hyver packages — offering a glimpse into a more streamlined, assisted import process.
3. See what you’re about to overwrite — in real time
If a row is flagged as an overwrite, you’ll see a yellow alert icon next to it. Hovering over the icon reveals the current value in the system, so you can compare it against your new input — right there in the table. That way, you’ll know exactly what’s being changed before it happens.
Overwrite warnings show you the existing values.
As mentioned earlier, when a finding is marked for overwrite, you can hover over the alert icon to see the current data. This makes it easy to compare “what was” and “what will be” — all within the same view.
4. Choose how to proceed — overwrite or insert as new
For each finding, you can make an intentional choice: keep it as a new entry or update an existing one. This is particularly valuable in two common workflows:
Unintentional overwrites, where an update you didn’t mean to make could affect teammates or compromise accuracy.
Intentional updates, like quarterly uploads from another system — where repeated overwrites are expected and desired.
There is no undo — this step is your safety net.
At this stage, Hyver doesn’t offer an “undo” option after importing. That’s why the validation step is so essential — it gives you the opportunity to catch and correct issues before any data is committed.
But we didn’t stop there — we also refreshed the UI to make the experience more intuitive, efficient, and flexible. From bulk-friendly workflows to thoughtful touches like auto-mapping and an interface built for the people doing the work, here’s how it all comes together.
Bulk-friendly and flexible
Before this feature, findings had to be entered one by one — even in large quantities. The Validation step unlocks true bulk importing for findings, similar to what already exists for assets and remediation assets. This means faster onboarding, easier quarterly updates from other systems, and smoother transition if you're migrating from a different tool to Hyver.
If you manage your work outside Hyver and want to update several findings at once — now you can do that with confidence.
Designed for the people doing the work
This feature is built for the people who manage findings hands-on — those responsible for uploading and importing data into Hyver as part of their day-to-day workflow. Think: security analysts and security leads.
It’s not about job titles — it’s about the level of interaction with the data. While CISOs certainly play a critical strategic role, this tool is designed specifically for the operational side of things: a practical workspace for those who need control, accuracy, and speed when managing findings.
Auto-mapping for a smoother experience
To make things even easier, the facelift includes auto-mapping based on column headers. If you’ve used a consistent template before, Hyver will recognize it and automatically match the fields for you. It’s a small detail that saves real time — especially when importing findings regularly.
Auto-mapping depends on consistent templates.
Auto-mapping works when your uploaded file uses column headers that match previously used templates. If your headers are consistent, Hyver will map them automatically — no manual setup required.
And of course:
Need help with the technical side — like how to perform an import, enable auto-mapping, or save a reusable template?
You can follow the full step-by-step guide [here].
Wrap-up / Next Steps
The validation step is more than a facelift — it’s a shift in how you manage data in Hyver. By giving you control before importing, it helps reduce errors, avoid confusion, and make bulk updates a safe, confident part of your workflow.
Feel free to take your time exploring this step — or start using it right away to streamline your imports. Either way, you’re now in control.