Skip to main content

Findings

The Findings page is the main working list for everything the scanner has detected.

Shared Jira visibility

Visibility follows the configured Jira service account. Every signed-in scanner user can see findings from projects that account may browse; the scanner does not impersonate individual Jira users. Grant the scanner's USER role only to people who may see that full scope.

Two views​

A toggle switches how results are presented:

  • Grouped by issue - findings collapsed under their Jira issue, with the issue and finding totals shown together. This is the view you land on, because whoever fixes an issue fixes all of its findings in one visit.
  • Findings - a flat list, one row per detection. Best for working through a single rule or severity.

Filtering​

Filter by project, issue key, rule, severity, review status, and whether suppressed findings are included. Project and rule filters are autocomplete dropdowns over what actually exists in your data, rather than free text you have to spell correctly.

The list​

  • The flat list has ten columns: issue, project, location, rule, severity, review status, detection state, state (a Suppressed badge when the finding is suppressed), a link into Jira, and the row actions. The grouped view drops issue, project, and the Jira link, which the group header already carries.
  • There is no excerpt column, because the scanner stores no excerpt.
  • Open the related Jira issue directly from a finding.
  • Select authorized findings and apply bulk review actions.
  • Restricted findings hide their details and cannot be selected. The row still exists, so counts stay honest.

Finding detail​

Opening a finding shows where the match sat and what produced it: rule and rule version, field, text variant, character offsets, severity, scan history, and review history. A finding that came from an attachment carries the attachment ID as part of its location.

No part of the matched text is shown, because none is stored - not the match and not the text around it. To inspect the actual content, follow the link to the Jira issue.

Reviewing findings​

Classify each finding to separate real risk from noise:

  • False positive - the detection is not actually sensitive data
  • Accepted risk - real sensitive data that the business accepts
  • Fixed - resolved in Jira; a future full scan no longer finds it
  • Reopen - return a classified finding to open

Each action can carry a reason or note. Status changes are audited and the review history stays visible on the finding.

Reviewing requires the ADMIN role. A user with only the USER role reads this page and the finding detail, but cannot classify, suppress, or unsuppress - see Sign in.

Review status is your decision about a finding. Whether the finding is still there is tracked separately as its detection state - see the glossary.

Suppressing and unsuppressing​

Authorized findings can be suppressed when a recurring match is known-safe. The suppression dialog records scope and reason. A suppression is forward-facing and broader than a false positive - it hides a whole class of matches. See Suppressions.

Suppressed findings can also be unsuppressed directly from the findings list, with a reason, when the exception no longer applies.

Exporting​

Findings are exported per scan run as CSV, containing metadata and source locators only - never matched values. See CSV export.