Skip to content

Working with Findings

Audience: All client users · Where: Findings in the sidebar (/findings) for the whole organization, or the Findings tab inside any assessment.

Overview

A finding is a single security issue Canima discovered — a vulnerability, misconfiguration, weak credential, or exposure. Findings are the heart of the platform: everything else (dashboard, analytics, reports) rolls up from them. You can view findings two ways:

  •   Org-wide

    Every finding across every assessment, from Findings in the sidebar.

  •   Per-assessment

    Only the findings for one engagement, from that assessment's Findings tab.

The org-wide Findings list

Each row shows a unique Code (e.g. F-2026-AF7F), the Title, the Type (Internal / External / Web App), the Status, the Severity, and the Assessment Name it came from. Click a title (or the assessment name) to open it.

Controls:

  • Display toggle: Open / Closed / All — Open is the default working view.
  • Dropdown filters: All Statuses, All Severities, All Types.
  • Search by Code or Name to jump to a specific finding.
  • Export CSV downloads the current list for spreadsheets or ticketing.
  • Sort any column with the arrows in its header; page through results at the bottom.

The per-assessment Findings list

Inside an assessment, the Findings tab shows the same data scoped to that engagement. It leads with a severity breakdown (click a severity to filter), an Affected column keyed to the engagement type (Affected URL for web app, Affected IP / port for external, host/port for internal) and a CVSS column, and its own All severities / All categories / All statuses filters plus Export CSV. Select one or more retestable findings to reveal a Request retest bar that re-verifies them in bulk.

Reading a finding

Click any finding to open its detail page:

  • Title, with Severity and Status badges.
  • Description — what the issue is and why it matters.
  • Remediation — how to fix it.
  • Evidence — the Tool used to find it and the Raw evidence (the actual tool output that proves the finding), so you can verify and reproduce it. Where available a finding also carries CVE references and a Proof of Concept.
  • Finding Details panel — Severity, CVSS, Status, Days Open, Created, Host, Category (plus CWE / affected parameter where relevant) at a glance.
  • Retest history — past retests of this finding, with a Request retest button in the header when the finding is in a re-verifiable state.

Statuses and severities

Severity — Critical / High / Medium / Low / Info, driven by impact and (where available) CVSS score.

Status reflects where the finding stands:

Status Meaning
Draft Captured but not yet validated.
Confirmed Validated as a real issue.
False Positive Reviewed and dismissed as not a real issue.
Accepted Risk Acknowledged and accepted rather than remediated.
Fixed Resolved.

Open vs. Closed

In the org-wide list, the Open / Closed / All display toggle groups these for you so you can work the open items first.

Retesting a finding

After you remediate a finding, you can request a retest so Canima re-verifies it and updates its status. Retest is available on findings in a re-verifiable state (typically Confirmed or Fixed); it's intentionally not offered on Accepted Risk or False Positive findings.

Status Retest eligibility
Confirmed Eligible — re-verifiable state
Fixed Eligible — re-verifiable state
Accepted Risk Not offered
False Positive Not offered

You can retest a single finding from its detail page, or several at once from the assessment's Findings tab. Internal retests run on one of your OVA appliances.

Retests don't cost extra capacity

Retests on covered engagements don't consume additional capacity — see Licenses & Credits.

Tips

  • Work from the Open view and sort by Severity to triage the highest-impact issues first.
  • The Code (F-2026-…) is a stable identifier — use it when referencing a finding in a ticket, email, or with Canima support.
  • Use Export CSV to push findings into your own tracker (Jira, ServiceNow, a spreadsheet).
  • Recurring the same finding across engagements? Check Analytics → Recurring Issues to fix the root cause once.

Related: Assessment Overview · Reports · Analytics · Vulnerability Scanning