# What a finding page shows

A tour of a finding page: the header, the Overview and Activity tabs, the Go Fix button, the side panel with its properties and the Adversary attack path.

*Where in the portal: Security → Findings → a finding*

*Last updated: 2026-10-21*

Open any row of the Findings list and the finding opens as a page. This page names each part of it.

![The Findings list for payments-api on the Open tab, with findings from critical to low.](https://kelrova.com/docs/img/findings/list.png)

*The Findings list on the Open tab.*

## The list

The list has the tabs **All**, **Open**, **Fixed**, **Accepted risk** and **False positive**, each with a count. Rows show the title, the kind, the severity and the dates a finding was found and verified. On the **All** tab rows also show the status. Use **Search findings…**, **Filter** and **Sort by** to narrow it. A **Columns** menu hides the ones you do not need. See [Severities](https://kelrova.com/docs/findings/severity).

## The header

![A finding's page on the Overview tab: severity, title, location and the written overview.](https://kelrova.com/docs/img/findings/page-overview.png)

*A finding page on the Overview tab: the header, the written sections and the side panel.*

Under **All findings** you see the title and one line of facts:

- The status, which is a menu if you may change it.
- The severity.
- The kind, unless it is Vulnerability.
- **Possible duplicate** or **Merged**, when it applies.
- The project, **Kelrova Cloud** and when it was found.

Then come the tabs **Overview** and **Activity**, and the **Go Fix** button.

## Overview

The Overview is the article: the sections from **What's happening** to **How to test the fix**, then **Location** or **Attack path**, **Evidence** and **History**. See [Reading evidence](https://kelrova.com/docs/findings/evidence).

An Adversary finding replaces **Location** with **Attack path**, and its side panel says **Affects**: **One user**, **One tenant** or **All users**.

![An Adversary finding with its attack path, step by step, and the Affects section.](https://kelrova.com/docs/img/findings/attack-path.png)

*An Adversary finding with its attack path, step by step, and Affects in the side panel.*

## Activity

**Activity** lists what happened to the finding, in order, with who did it: status changes, fixes, re-checks, questions and reports from connected apps, such as **Reported fixed via** the app's name. A proposal waiting for a member appears at the top with **Accept** and **Dismiss**.

![The Activity tab of a finding: a re-check and the fix it suggests, then a connected app reporting work in progress and proposing the finding as fixed.](https://kelrova.com/docs/img/findings/page-activity.png)

*A finding's Activity: a re-check with a suggested fix, then two reports from a connected app, one of them waiting for review.*

## The side panel

The **Finding details** toggle opens a panel beside the article:

| Section | What it holds |
| --- | --- |
| **Properties** | Confidence, Affects, the number of attack path steps, the weakness (CWE), the tag, and which scan levels found it. |
| **Location** or **Attack path** | The file and line, or the first steps of the path, and the **Entry point**. |
| **Remediation** | Where a fix stands: Patch, PR, Gates, Merged. |

If the project has tags, the **Tag** row is a menu for members who may change findings. The line under a tag reads **Set by scan** or **Set by you**. See [Tags](https://kelrova.com/docs/findings/tags).

## Related

- [Reading evidence](https://kelrova.com/docs/findings/evidence)
- [Statuses and what changes them](https://kelrova.com/docs/findings/statuses)
- [Go Fix: fix, re-check, ask](https://kelrova.com/docs/findings/go-fix)
- [What Kelrova finds](https://kelrova.com/docs/findings/kinds)