---
title: "Findings"
description: "Browse and filter every finding across every application in your organization from a single table."
url: https://docs.stackhawk.com/platform/findings/
---

# Findings

The [Findings page](https://app.stackhawk.com/findings) shows every finding across every application and environment in your organization in one filterable, sortable table.

## Findings Table

Each row represents a single finding on a specific path, in a specific environment of a specific application. Rows come from the most recent completed scan of each application and environment pair.

![StackHawk Platform - Findings table](https://docs.stackhawk.com/images/platform/findings/findings-table.png)

For each finding, the table shows:

- **Application** — The application the finding belongs to.
- **Environment** — The environment the finding was detected in.
- **Vulnerability** — The type of vulnerability (for example, SQL Injection or Cross Site Scripting).
- **Severity** — High, Medium, or Low.
- **Path** — The HTTP method and URL where the finding was detected.
- **Last Seen** — When the finding was most recently detected.

Click a row to open the [Finding Details](https://docs.stackhawk.com/platform/scans/#finding-details-page) page, where you can inspect the request and response, validate the attack, and triage the finding.

## Filtering and Sorting

Filter the table by **Application**, **Environment**, or **Severity**. Filters combine with AND semantics — only findings matching every active filter are shown. You will only see findings for applications your [team](https://docs.stackhawk.com/platform/teams/) has access to.

Sort by **Last Seen** (default), **Severity**, **Vulnerability**, **Application**, or **Environment**. Severity sorts by rank (High → Low), not alphabetically.

> **Note:** Triage actions are taken from the [Finding Details](https://docs.stackhawk.com/platform/scans/#finding-details-page) page. Status changes are reflected on the Findings page after the next successful scan of the affected environment.

## How the Page Updates

When a scan completes, its findings replace the previous entries for that application and environment — fixed findings drop off, and new ones appear. Error scans don’t update the page, so prior findings stay visible until a successful scan runs.