> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/ai-sca/prezero/ui/application-details/findings.md).

# Findings

The **findings** tab of the application page allows you to see the findings discovered during Qwiet AI by Harness analyses. Currently, Qwiet AI by Harness identifies the following types of findings: vulnerabilities, OSS vulnerabilities, container findings, secrets, and security issues.

For each finding on the list, you'll see the following fields:

* Finding ID (e.g. `42`)
* Severity level (e.g., `Critical`)
* Title (e.g. `SQL Injection: Attacker-controlled Data Used in SQL Query`)
* Tags (e.g., `OWASP a1-injection` or `CVSS 9`)
* Type (e.g. `Vulnerability`, `Secret`)
* Status (e.g., `Fixed`)
* Reachability: `Reachable`, `Unreachable`, or `N/A`&#x20;
* Dependency Scope: `Direct` or `Indirect`
* Exploitability: `Exploitable`, `No Exploits`, or `N/A`
* App name (e.g. `shiftleft-java-demo`)
* Team name (e.g. `Engineering`)
* App groups (e.g. `Code Science`)

You can sort your list based on **Finding ID** or **Severity** level (ascending or descending).

Right above the sorting options, on the top-right corner, you can see whether or not there are new [SCA results](https://developer.harness.io/ai-sca/prezero/oss-vulnerabilities.md) available. Qwiet AI by Harness continually checks your application and alerts you if there are new OSS vulnerabilities affecting your application. The timestamp displayed lets you know when the latest check for new OSS vulnerabilities was performed by Qwiet. If there are new results, you should rescan your application to populate the findings to the dashboard.

![The Qwiet AI by Harness Findings tab](https://1323456121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJwuqV3Cg06KbulvSaUS%2Fuploads%2Fgit-blob-f8c5553abfcab50f08ef7a057f8b3489cd5c6aeb%2Ffindings-vuln-cd7a1cde5c.png?alt=media)

## Qwiet the Noise <a href="#qwiet-the-noise" id="qwiet-the-noise"></a>

To help prioritize the review and fixing of findings, you can toggle on **Qwiet the Noise**, which filters for only **critical**, **high**, **reachable** (if applicable), and **exploitable** (if applicable) findings.

## Filtering findings <a href="#filtering-findings" id="filtering-findings"></a>

You can filter the findings list by the following criteria:

* **Finding Type**: Under **Finding Type**, choose one or more of the following options:
  * **SAST**: Filters findings identified through static application security testing.
  * **SCA**: Filters findings related to software composition analysis.
  * **OSS Risk**: Filters findings associated with open source risks.
  * **Container**: Filters findings identified in container images.
  * **Security Issue**: Filters security issues identified by Harness.
  * **Secret**: Filters findings related to exposed or detected secrets.
  * **AI Risk**: Filters findings associated with AI-related risks.
* **Language**: Click the **Language** dropdown menu and select one or more of the following:
  * **Java**: Filters findings associated with Java.
  * **JavaScript**: Filters findings associated with JavaScript.
  * **Python**: Filters findings associated with Python.
* **Severity:** Click the **Severity** dropdown menu and select one or more of the following:
  * **Critical**: Filters findings with critical severity.
  * **High**: Filters findings with high severity.
  * **Medium**: Filters findings with medium severity.
  * **Low**: Filters findings with low severity.
* **Status**: Click the **Status** dropdown menu and select one or more of the following:
  * **Any**: Includes findings with any status.
  * **Open**: Filters findings with an open status.
  * **Fixed**: Filters findings with a fixed status.
  * **Ignored**: Filters findings with an ignored status.
  * **3rd Party**: Filters findings with a 3rd-party status.
* **Assigned To**: Under **Assigned To**, search for and select a user from the list of available users to filter findings associated with that user.
* **AutoFix**: Under **AutoFix**, select the **AutoFix Available** checkbox to filter findings with an available AutoFix.&#x20;
* **AI Findings**: Under **AI Findings**, select one of the following checkboxes:
  * **All**: Includes all findings.
  * **AI Findings**: Filters findings identified as AI findings.
* **Exploitability**: Under **Exploitability**, select one of the following checkboxes:
  * **All**: Includes findings regardless of exploitability.
  * **Exploitable**: Filters findings that are exploitable.
  * **No Exploits**: Filters findings with no known exploits.
* **Reachability**: Under **Reachability**, select one of the following checkboxes:
  * **All**: Includes findings regardless of reachability.
  * **Reachable**: Filters reachable findings.
  * **Unreachable**: Filters unreachable findings.
* **Dependency Scope**: Under **Dependency Scope**, select one of the following checkboxes:
  * **All**: Includes findings regardless of dependency scope.
  * **Direct**: Filters findings associated with direct dependencies.
  * **Indirect**: Filters findings associated with indirect dependencies.
* **AI Confidence**: Under **AI Confidence**, select one or more of the following checkboxes:
  * **Confirmed Risk**: Filters findings identified as confirmed AI risks.
  * **Potential Risk**: Filters findings identified as potential AI risks.
  * **Contextually Safe**: Filters findings identified as contextually safe.
* **OSS Risks**: Under **OSS Risks**, select one or more of the following checkboxes:
  * **Abandoned**: Filters findings associated with abandoned open source components.
  * **End-of-Life**: Filters findings associated with end-of-life components.
  * **Malicious**: Filters findings associated with malicious components.
  * **Squatted**: Filters findings associated with squatted components.
  * **Hijackable Repository**: Filters findings associated with hijackable repositories.
* **CVSS Score**: Under **CVSS Score**, enter the minimum and maximum CVSS scores in the **Min** and **Max** fields, respectively. \
  You can also drag either end of the slider to set the minimum and maximum scores. The position of each slider handle determines the corresponding score.
* **EPSS Score**: Under **EPSS Score**, enter the minimum and maximum EPSS scores in the **Min** and **Max** fields, respectively.\
  You can also drag either end of the slider to set the minimum and maximum scores. The position of each slider handle determines the corresponding score.
* **Source Method**: Click the **Source Method** dropdown menu and select one or more source method to filter findings based on the source method. \
  The available options depend on the application being scanned.
* **Sink User Method**: Click the **Sink User Method** dropdown menu and select one or more sink user methods to filter findings based on the sink user method. \
  The available options depend on the application being scanned.
* **Sink Method**: Click the **Sink Method** dropdown menu and select one or more sink methods to filter findings based on the sink method. \
  The available options depend on the application being scanned.
* **Package URL**: Click the **Package URL** dropdown menu and select one or more package URLs to filter findings based on the package URL. \
  The available options depend on the application being scanned.
* **Package Group**: Click the **Package Group** dropdown menu and select one or more package groups to filter findings based on the package group. \
  The available options depend on the application being scanned.
* **Package Component**: Click the **Package Component** dropdown menu and select one or more package components to filter findings based on the package component.\
  The available options depend on the application being scanned.
* **OWASP 2025 Category**: Click the **OWASP 2025 Category** dropdown menu and select one or more categories to filter findings based on the selected categories. \
  For more information on OWASP 2025 categories, go to [OWASP Top 10:2025](https://top10.owasp.org/2025/).
* **OWASP 2021 Category**: Click the **OWASP 2021 Category** dropdown menu and select one or more categories to filter findings based on the selected categories. \
  For more information on OWASP 2021 categories, go to [OWASP Top 10:2021](https://top10.owasp.org/2021/).
* **OWASP Category**: Click the **OWASP Category** dropdown menu and select one or more categories to filter findings based on the selected OWASP categories.\
  The available options include categories from [OWASP Top 10 2021](https://top10.owasp.org/2021/) and [OWASP Top 10 2017](https://owasp.github.io/www-project-top-ten/2017/).
* **CWE Category**: Click the **CWE Category** dropdown menu and select one or more categories to filter findings based on the selected categories. \
  For more information on CWE categories, go to [CWE Top 25](https://cwe.mitre.org/data/definitions/1435.html).
* **CVSS Score**: Click the **CVSS Score** dropdown menu and select one or more scores to filter findings based on the selected scores. \
  For more information on CVSS score, go to [Vulnerability Metrics](https://nvd.nist.gov/vuln-metrics/cvss).
* **CVE**: Click the **CVE** dropdown menu and select one or more CVEs to filter findings based on the selected CVEs. \
  The available CVEs depend on the findings identified in the application being scanned. For more information on CVEs, go to [CVE Record User Guide](https://www.cve.org/CVERecord/UserGuide).
* **Category**: Click the **Category** dropdown menu and select one or more categories to filter findings based on the selected categories:
  * **Data Exfiltration**: Filters findings related to the unauthorized extraction or transfer of data.
  * **Privilege Escalation**: Filters findings related to gaining higher privileges than intended.
  * **Tool Misuse**: Filters findings related to the improper or unsafe use of tools.
  * **YARA Match**: Filters findings that match a YARA rule.
  * **Command Injection**: Filters findings related to the injection of commands into an application or system.
  * **Deserialization**: Filters findings related to insecure or unsafe deserialization of data.
  * **Remote Code Execution**: Filters findings that could allow an attacker to execute code remotely.
  * **Cross-Site Scripting**: Filters findings related to cross-site scripting (XSS) vulnerabilities.
  * **Sensitive Data Leak**: Filters findings involving the exposure or leakage of sensitive data.
  * **Timing Attack**: Filters findings related to timing-based attacks.
  * **Weak Hash**: Filters findings related to the use of weak or insecure hashing algorithms.
  * **Directory Traversal**: Filters findings related to unauthorized access to files or directories through path manipulation.
  * **Hardcoded Credentials**: Filters findings involving credentials embedded directly in source code.
  * **Header Injection**: Filters findings related to the injection or manipulation of HTTP headers.
  * **Insecure Direct Object Reference**: Filters findings where an application exposes direct access to objects without adequate authorization checks.
  * **Log Forging**: Filters findings related to the manipulation or injection of data into application logs.
  * **Open Redirect**: Filters findings that could allow an attacker to redirect users to an unintended URL.
  * **Race Condition**: Filters findings caused by the improper handling of concurrent operations.
  * **Security Best Practices**: Filters findings related to violations of recommended security practices.

{% hint style="info" %}
You can combine multiple filters to narrow down the findings based on your requirements.
{% endhint %}

The **Saved Searches** panel allows you to save and recall a set of filters. Each user can save up to 10 searches. Once a search is recalled, it can also be edited and deleted as needed.

To quickly remove all filters, click the **Findings** tab title.

## Viewing detailed finding information <a href="#viewing-detailed-finding-information" id="viewing-detailed-finding-information"></a>

Clicking on a finding in your results list will open a new window pane on the right with detailed information. Note that some tabs are only available for some findings types (e.g. SAST), and only when certain capabilities are enabled (e.g. [AutoFix](https://developer.harness.io/ai-sca/prezero/autofix.md)).

![A view of the detailed findings tab for a specific vulnerability](https://1323456121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJwuqV3Cg06KbulvSaUS%2Fuploads%2Fgit-blob-b7cf3ed8d0147ff6235e9c47a87729740c6dca61%2Ffindings-vuln-detail-173e460f64.png?alt=media)

* **Description**: The **Description** tab features an in-depth write-up of what the issue is and why it is a problem, as well as mitigation suggestions for securing your app.
* **AutoFix**: If enabled for your organization and application, this tab shows available AutoFix suggestions, AutoFix pull request link (if enabled and available), and additional information that you can use to address a SAST finding.
* **Data Flow**: The **Data Flow** tab shows you the path from the source (which is the portion of the code that "allows" a vulnerability to occur) to the sink (where the vulnerability happens).

  For example, suppose the vulnerability is a command injection vulnerability. The source could be a function accepting user input, while the sink would be where a command execution occurs using the user input. The data flow is the path between these two spots in the code.
* **Reachability**: The **Reachability** tab provides information about data flow and function calls associated with a vulnerable dependency:
  * **Data Flow**: Indicates whether the flow of untrusted data from the source to the sink has been established, including where the data is processed or passed between functions.
  * **Call path**: Indicates whether the sequence of function calls from the source function to the sink function has been established, showing how the sink can be reached.
  * **Library call**: Displays function calls made using the vulnerable dependency identified during the SCA scan. Under **View by**, select one of the following options:
    * **Source Functions**: Groups function calls by the source function in your application code that makes the call. Use the **Search calls** field to find a specific sink.
    * **Library Sinks**: Groups library calls by the sink functions in the vulnerable dependency that are called by the source functions. Use the **Search calls** field to find a specific sink.
* **Related Dependencies**: The **Related Dependencies** tab lists the dependencies related to the finding in a table. The table displays the **dependency**, its **relationship**, and the **number of vulnerabilities** associated with each dependency. You can also search for a specific dependency using the **Search Dependency** field. If a listed dependency is an indirect dependency of the selected dependency, the entry also shows its relationship to the direct dependency.
  * Click a dependency to filter the findings list and view findings associated with that dependency.<br>

    <figure><img src="https://1323456121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJwuqV3Cg06KbulvSaUS%2Fuploads%2Fpq8zcmj2ZxyefPS7psIU%2Frelated-dependency-tab.png?alt=media&amp;token=944d4f4c-2dba-4161-915d-192c446abdfd" alt="Related dependency tab"><figcaption><p>Related dependency tab</p></figcaption></figure>
* **Exploits (Blacklight)**: The **Exploits** tab includes up-to-date exploitability information on the vulnerability, including the:

  * **Date** reported
  * The **source** providing a proof of concept of the exploit
  * The **availability** of the exploit (e.g., public, private, or commercial)

  The [Exploit Prediction Score System (EPSS) score](https://www.first.org/epss/) shown for the vulnerability can help you determine the severity and priority of a given vulnerability. The EPSS score falls between 0 and 1, and we recommend focusing on findings with a high EPSS score and high CVSS score. The presence of a **CISA KEV** tag indicates that the vulnerability is part of the United States of America's Cybersecurity & Infrastructure Security Agency (CISA)'s [Known Exploited Vulnerabilities Catalog (KEV)](https://www.cisa.gov/known-exploited-vulnerabilities-catalog). This can help you determine the importance of an OSS finding.

  ![A view of the exploits tab for a specific OSS vulnerability](https://1323456121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJwuqV3Cg06KbulvSaUS%2Fuploads%2Fgit-blob-fa0eac90efe45338a7552f9852b78e5cfb5e5574%2Ffindings-exploitability-68091f6171.png?alt=media)
* **Comments**: The comments tab allows you and your team members to make notes specifically about this finding; if there are multiple comments for this finding, Qwiet displays them in reverse chronological order.

{% hint style="info" %}
The **Reachability**, **Exploits**, and **Related Dependencies** tabs are available only for SCA findings.
{% endhint %}

### Filtering by sources and sinks <a href="#filtering-by-sources-and-sinks" id="filtering-by-sources-and-sinks"></a>

Using the filter by sources/sinks feature available in the **Data Flow** tab or panel (see Expanded details below), you can triage vulnerabilities faster and determine which findings your code fixes would affect.

![Option to filter by sources and sinks](https://1323456121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJwuqV3Cg06KbulvSaUS%2Fuploads%2Fgit-blob-447513d4e667bdc8f35ebc37a921358cb9c45b14%2Ffindings-source-sink-filters-e69eafb0bf.png?alt=media)

For each source/sink identified by Qwiet AI by Harness, you'll see an option to **Add as Filter**.

When set, you'll notice that the vulnerabilities list updates to only include vulnerabilities that feature that same source/sink. If you were to patch that specific code portion, these would be the vulnerabilities affected by your code change.

![Filtered vulnerabilities by sources/sinks](https://1323456121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJwuqV3Cg06KbulvSaUS%2Fuploads%2Fgit-blob-78ec32fcef9dabc627060051c428b4be6e4811a9%2Ffindings-source-sink-filtered-results-f6470e2260.png?alt=media)

## Expanded details <a href="#expanded-details" id="expanded-details"></a>

Click **Details** in the top-left corner of the Finding panel to switch to an expanded view of the finding. This allows you to see data side by side and make quick decisions on how to address a finding.

![A view of the expanded findings tab for a specific vulnerability](https://1323456121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJwuqV3Cg06KbulvSaUS%2Fuploads%2Fgit-blob-4060af4ee30304fb55054b4b2df53d61cd9b40e1%2Ffindings-vuln-expanded-50134f0eb4.png?alt=media)

To return to the summary view, click **Minimize** in the top-left.

## Changing status <a href="#changing-status" id="changing-status"></a>

Set the finding **status** to reflect work that's been done (e.g., set the finding status to **Fixed** if you've mitigated the issue):

* **Open**: The default status value for a finding
* **Fixed**: Mark the finding as **fixed** if you've applied remediation of some type (note that setting this status does not *fix* the finding) so that Qwiet doesn't include the finding in the scan results
* **Ignored**: Mark the finding as **ignored** so it doesn't show up in scan results again. Used to indicate that something is a false positive or is unlikely to impact the application's security. If you set the status to **ignored**, you must also provide a **comment** that includes information on your reasoning for choosing this status
* **3rd Party**: Mark the finding as **3rd Party** to indicate that the finding is in a third-party library; you can't fix the finding at the moment, but you should return to it at a later date

## Additional actions <a href="#additional-actions" id="additional-actions"></a>

You can also perform the following actions:

* **Assign to** a team member the vulnerability for further research and work
* Get a **link to issue** that's specific to this finding that you can share with others
* [Launch **Security Training**](https://developer.harness.io/ai-sca/prezero/security-training.md) that's specific to this type of finding (if available and applicable)
* Click the **Send to Jira** button (if the Jira integration is enabled) to create a Jira issue with the finding details

{% @harness-feedback/feedback %}
