You are viewing docs on Elastic's new documentation system, currently in technical preview. For all other Elastic docs, visit

Findings page

Review your cloud security posture management data.

The Findings page displays the configuration risks identified by the CSPM and KSPM integrations.

What are findings?

CSPM findings indicate whether a given resource passed or failed evaluation against a specific security guideline. Each finding includes metadata about the resource evaluated and the security guideline used to evaluate it. Each finding's result (pass or fail) indicates whether a particular part of your infrastructure meets a security guideline.

Group and filter findings

By default, the Findings page lists all findings, without grouping or filtering.

Group findings

  1. Click Group findings by: to open a list of fields by which you can group findings. Select one of the suggested group-by fields, or click Custom field to choose your own group-by field.
  2. When grouping is turned on, click a group to expand it and examine all findings within that group.
  3. To turn off grouping, click Group findings by: and select None.

Filter findings

You can filter findings data in two ways:

  • The KQL search bar: For example, search for result.evaluation : failed to view all failed findings.
  • In-table value filters: Hover over a finding to display available inline actions. Use the Filter In (plus) and Filter Out (minus) buttons.

Customize the Findings table

Use the toolbar buttons in the upper-left of the Findings table to customize the columns you want displayed:

  • Columns: Select the left-to-right order in which columns appear.
  • Sort fields or n fields sorted: Sort the table by one or more columns, or turn sorting off.
  • Fields: Select which fields to display for each finding. Selected fields appear in the table and the Columns menu.


You can also click a column's name to open a menu that allows you to perform multiple actions on the column.

Remediate failed findings

To remediate failed findings and reduce your attack surface:

  1. First, filter for failed findings.

  2. Click the arrow to the left of a failed finding to open the findings flyout.

  3. Follow the steps under Remediation.


    Remediation steps typically include commands for you to execute. These sometimes contain placeholder values that you must replace before execution.

Generate alerts for failed Findings

You can create detection rules that detect specific failed findings directly from the Findings page.

  1. Click the arrow to the left of a Finding to open the findings flyout.
  2. Click Take action, then Create a detection rule. This automatically creates a detection rule that creates alerts when the associated benchmark rule generates a failed finding.
  3. To review or customize the new rule, click View rule.

On this page