Findings

The findings view is where Guardix lists issues discovered and validated for your audit snapshot.

Severity

Findings are grouped by severity (for example critical, high, medium, low). Use this for triage — critical and high items usually deserve the fastest review.

Note

Severity describes technical impact if the issue is real. Always combine with confidence and your own product context.

Confidence

Confidence reflects how well the evidence held up after cross-validation — not a legal guarantee. High-confidence items are usually worth fixing or formally accepting first.

Evidence

Each finding includes pointers into your code (files, functions, lines) where applicable, plus a written explanation of why it matters.

Sources

Issues may originate from different analysis paths (static tools, structured reviews, merged duplicates). The UI focuses on what to fix, not internal pipeline names.

Review labels

Your team can mark individual findings as you triage:

• Open — not yet reviewed
• True positive — confirmed real issue (labeled mitigated in the API)
• False positive — not applicable or incorrect for your deployment

Filters on the findings list can narrow by review state.

Audit verdict

At the repository level, you can set an overall audit verdict when a scan is complete — for example requires action or all clear — so the dashboard reflects whether the latest completed run still needs work.

Filtering and sorting

Use the in-app filters and sorting to focus on severity, status, or review state — exact controls match the current product.

---

Understanding findings — practical guide to prioritization.