> For the complete documentation index, see [llms.txt](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/findings/cloud/findings.md).

# Cloud Findings

The Findings by Resource tab under Security → Cloud — one row per failing cloud resource, with the checks it fails.

**Security → Cloud → Findings by Resource** lists every cloud resource that fails at least one check, worst first.

<figure><img src="https://414480750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXP3dp2kecwKA2KvYkntz%2Fuploads%2Fgit-blob-6e8846a377f075ddddceb1d6c15dc3491efdd056%2Fcc-cs-findings.png?alt=media" alt="The Findings by Resource tab with the Connected clouds only filter in the filter bar, listing 882 failing resources with Resource, Severity, Failing Checks, Account, Region and First Identified columns; the demo-development AWS account row is expanded to show its nine failing checks with their severity, frameworks and first-identified date."><figcaption><p>Findings by Resource — one row per failing resource; expand a row for its failing checks.</p></figcaption></figure>

## Columns

| Column               | What it shows                                       |
| -------------------- | --------------------------------------------------- |
| **Resource**         | The resource name.                                  |
| **Severity**         | The resource's failing checks, counted by severity. |
| **Failing Checks**   | The number of checks the resource fails.            |
| **Account**          | The cloud account.                                  |
| **Region**           | The region.                                         |
| **First Identified** | When the resource first failed a check.             |

The list sorts by severity, worst first: critical count, then high, medium and low. **Severity**, **Failing Checks**, **Resource** and **First Identified** are sortable. Search matches the check name, the resource name, the provider ID or the Heeler ID.

Expand a row to list the resource's failing checks, with **Failing Check**, **Severity**, **Frameworks** and **First Identified**. Select a check to open the [check drawer](/mrecEO40m5D6bt7Pq5pE/findings/cloud/checks.md#check-drawer). Select the row to open the [resource drawer](/mrecEO40m5D6bt7Pq5pE/catalog/infrastructure/resource-detail.md).

A resource that an approved **All frameworks** [exemption](/mrecEO40m5D6bt7Pq5pE/findings/cloud/exemptions.md) covers for a check does not count as failing that check.

## Filters

The tab shares its filters with the [Checks](/mrecEO40m5D6bt7Pq5pE/findings/cloud/checks.md#filters) tab, and adds **Region**. Filters set on one tab stay set on the other.

These links open this tab with their filters applied:

* **View Findings** on [Dashboards → Cloud Posture](/mrecEO40m5D6bt7Pq5pE/operate/dashboards/cloud-posture.md#summary-cards).
* An account name under [Accounts by posture](/mrecEO40m5D6bt7Pq5pE/operate/dashboards/cloud-posture.md#accounts-by-posture).
* **View failing resources →** on a framework's [heatmap](/mrecEO40m5D6bt7Pq5pE/standards-and-compliance/cloud-frameworks.md#heatmap-tab).

## Related

* [Cloud Checks](/mrecEO40m5D6bt7Pq5pE/findings/cloud/checks.md) — one row per check.
* [Resource Detail](/mrecEO40m5D6bt7Pq5pE/catalog/infrastructure/resource-detail.md) — the resource drawer.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/findings/cloud/findings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.