> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/findings.md).

# Findings

**Findings** lists the open findings from the latest assessment of every application you can see, across Platform Analysis and Code Analysis, in one list grouped by rule. Use it to see which rules cause the most findings anywhere in your estate, then open a group for its occurrences or an application for its full evidence.

Open it from **Findings** in the sidebar, below **Dashboards**.

{% hint style="info" %}
Requires the **Platform Analysis** or **Code Analysis** licence. The list shows the findings of the applications your roles let you see in each of them.
{% endhint %}

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FPNEhIu6UpLLJ4VnZ4LRJ%2Fv2-findings-top.png?alt=media&amp;token=801c0443-7238-47c1-aa2a-0d631e04f17a" alt="Findings across Platform Analysis and Code Analysis: tiles, filters and the list grouped by rule"><figcaption></figcaption></figure>

## Filters

| Filter                       | Description                                                                                                                                  |
| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| **Product**                  | **All products**, **Platform Analysis** or **Code Analysis**. Shown when you can see both.                                                   |
| **Asset type**               | The asset types of the chosen product that you can see.                                                                                      |
| **Severity**                 | **All severities**, **Critical + Blocker**, or one severity.                                                                                 |
| **Security standard**        | Findings mapped to a standard (CWE, OWASP, AWS Foundational Security Best Practices); once you choose one, you can also choose its category. |
| **Filters** → **Issue type** | Findings of one type, such as vulnerabilities, bugs or code smells. Choose it, then click **Apply filters**.                                 |

A finding must match every filter you set. Every filter is kept in the page address, so you can share the link or save the set with **Save filters** and choose it later from **Saved filters**.

## Tiles

| Tile                               | Description                                                                                                              |
| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| **Open finding occurrences**       | Every open occurrence that matches the filters, except severity. When a severity is set, click it to clear the severity. |
| **Critical + Blocker occurrences** | The Critical and Blocker occurrences. Click it to show only those in the list.                                           |
| **Rules with open findings**       | The number of rules with open findings: each rule is one group in the list.                                              |

## Open Findings

Use the list above the table to group findings **By rule** (the default), **By file**, or as single **Occurrences**. Turn on **New code only** to keep only the findings a change introduced: for a pull request, findings not open on its target branch; for a branch, findings new since its previous assessment.

The list has the same columns, grouping and finding detail as the [Platform Analysis Findings](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/platform-analysis/findings.md) tab. Each row is tagged with its product. Opening an application takes you to its dossier in the workspace it belongs to.

{% hint style="info" %}
**Time to fix** and **Exceptions** are kept per product. Use the **Findings** tab of [Platform Analysis](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/platform-analysis/findings.md) or [Code Analysis](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/findings.md) for them.
{% endhint %}

## Next Steps

* [Platform Analysis Findings](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/platform-analysis/findings.md): effort estimates and the exceptions register for deployed applications.
* [Code Analysis Findings](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/findings.md): findings of branches and pull requests.
* [Quality Gates](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/quality-control/quality-gates.md): decide which findings fail an assessment.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/findings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
