Skip to main content

Finding Versions

Understand how Hyver handles versioning for recurring findings across assessments.

Updated over 5 months ago

Overview

This article explains how finding versions work in Hyver — especially in engagements with recurring assessments (e.g., monthly scans or testing cycles).
Hyver automatically tracks changes to findings over time, creating new versions when meaningful differences are detected. This ensures visibility into how issues evolve — without duplicating unchanged data.


How versions are created

In repeated assessments, findings that haven't been closed (i.e., fixed) will be detected again.
However, a new version is created only if something has changed in the finding's data.


A new version is created if:

  • Severity, description, or supporting evidence changes

  • The finding affects the same remediation asset but has updated attributes

  • Any attribute used in risk calculation or decision-making is updated


A new version is not created if:

  • The same finding is detected again with no differences


Viewing and editing versions

  • The latest version is always shown by default in the Findings list

  • You can view previous versions of a finding from the details pane

  • You can only edit the most recent version


Fields that stay the same across all versions

These attributes are shared by all versions and cannot be changed individually:

  • Name

  • Status (including customer-defined statuses)

  • Security Domain

  • Priority

  • ID

  • Type

  • Probability

  • Edges

  • Permissions & Engagement

  • List of remediation assets

  • Customer inputs:

    • Tags

    • Owner

    • Cost and Effort

    • Remediation Date


Fields that can differ between versions

Each version can have unique values for fields such as:

  • Severity

  • Description

  • Supporting evidence

  • Mitigation recommendations

  • Version-specific metadata


Example

If your first assessment detects 50 findings, and your team closes 20, the second assessment might create 30 new versions of the remaining unresolved findings — but only if they changed. New findings from the second assessment will be added alongside these updated versions.


Wrap-up / Next Steps

Finding versions help track change over time without cluttering your dashboard. Use them to see how issues progress — and focus only on what’s changed.

Did this answer your question?