---
title: "How Filters Work in Unique Views"
slug: "how-filters-work-in-unique-views"
updated: 2026-10-22T15:02:28Z
published: 2026-10-22T15:02:28Z
canonical: "docs.safe.security/how-filters-work-in-unique-views"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.safe.security/llms.txt
> Use this file to discover all available pages before exploring further.

# How Filters Work in Unique Views

In **Unique Control Findings** and **Unique AppSec Findings**, filters are applied at the **instance level** and then aggregated (pivoted) into the unique view.

## **Filtering Logic**

- **All filters operate on individual instances first.**
  - Every finding instance has its own attributes (e.g., Exposure Score, CVSS, EPSS)
  - For example, if you apply a filter such as “Exposure Score ≥ 30,” the system selects all individual instances that meet that condition.
- After filtering, results are **aggregated (pivoted) into the unique view.**
  - A unique control or application is shown once, even if multiple findings exist underneath it.
  - Where applicable, the unique table may display **summary columns** (such as Min and Max) to represent the range of values across all the filtered instances.

## **Example with Exposure Score**

If a control has three underlying findings with Exposure Scores of 29, 30, and 32:

- Applying a filter Exposure Score ≥ 30 removes the instance with score 29.
- The unique control still appears, but now the summary values are:
  - **Min Exposure Score = 30**
  - **Max Exposure Score = 32**

## **Key Points**

- This behavior applies to **all filters in unique view**, not just Exposure Score.
- Filters always operate on raw instance values.
- Aggregated values shown in the unique table (such as Min/Max) are summaries of the filtered instances, not the inputs to the filter.
- Depending on the table design, summary columns may or may not be visible in the unique view.