Skip to content
Xint Docs

Managing Findings

The “Findings” tab on an Asset accumulates every vulnerability detected across all scans run against that Asset. When the same vulnerability piles up as multiple entries, or when you need to confirm that a remediation actually worked, you can manage Findings in two ways:

  • Merge duplicate Findings into one to consolidate the tracking unit.
  • Retest a remediated Finding to verify the fix.

Merging Findings

Section titled “Merging Findings”

Merging multiple Findings into one consolidates the tracking unit for the same underlying issue, keeping retests and status management simple.

  1. On the Asset detail page, open the “Findings” tab.

  2. Use the checkboxes to select the Findings you want to merge.

  3. Click the “Merge” button. You need to select at least 2 Findings to merge.

  4. When the “Merge findings” dialog opens, choose the Finding you want to keep after the merge.

    Every other selected Finding is merged into this one and deleted. The merged Finding inherits the status of the Finding you kept.

  5. Click the “Merge” button at the bottom of the dialog to confirm.

Warnings During Merge

Section titled “Warnings During Merge”

Depending on the combination of Findings you select, the dialog may show one of the following warnings at the top.

  • Mixed statuses: If the Finding you’re keeping is Resolved while the others are Open, the dialog warns that active Findings may be hidden inside a resolved entry once they’re merged. Confirm this is the outcome you want before proceeding.
  • Different categories: If the selected Findings belong to different vulnerability categories, the dialog warns that a single Retest can’t verify all of them at once. We generally recommend merging Findings within the same category.

Verifying Remediation With a Retest

Section titled “Verifying Remediation With a Retest”

To confirm that a remediated Finding has actually been resolved, open the Finding’s detail drawer and click the “Retest” button to run a Retest scan. A Retest scan targets only that one Finding instead of re-running a full scan against the Asset, so you get a quick verification of the fix.

When the Retest scan finishes, the Finding’s status updates automatically based on the result.

For details, see Retest Scans.