> For the complete documentation index, see [llms.txt](https://docs.xygeni.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xygeni.io/xygeni-products/code-security-cs/cs-user-interface-guide/risks-sast.md).

# SAST Risks

The **Risks (SAST) page** can be accesed by selecting the SAST option in the [**Risks**](/xygeni-products/application-security-posture-management-aspm/all-risks.md) tab. This tab offers an in-depth overview of all SAST security issues, clearly presented for ease of assessment.

{% hint style="info" %}
Xygeni provides two functionalities related to SAST scanning

1. Xygeni provides a [SAST Scanner](/xygeni-products/code-security-cs/ci-cd-scanner.md) that can perform static analysis over your application code. Please visit [Xygeni SAST Scanner](/xygeni-products/code-security-cs/ci-cd-scanner.md) for further information.
2. Xygeni also provides the functionality to [import scan results from 3rd-party tools](/xygeni-products/application-security-posture-management-aspm/importing-reports-from-3rd-party-tools.md). This way, you can integrate 3rd-party data into Xygeni and benefit from the [Xygeni ASPM](/xygeni-products/application-security-posture-management-aspm.md) functionalities. The **supported SAST scanners** are listed in the [supported SAST scanners](/xygeni-products/application-security-posture-management-aspm/importing-reports-from-3rd-party-tools/external-scanners-supported.md#sast_software_application_security_testing) section.
   {% endhint %}

By default, this page will display all the SAT issues, regardless of the tool that found the issues (Xygeni SAST Scanner or any other 3rd party tool).

If you click on **More filter fields**, you can find the **Tools** filter where you can select a tool and only those issues reported by the selected tool will be displayed.

{% hint style="info" %}
You can reach the **Risks (SAST)** results under Code Security >> Risks (SAST) section.
{% endhint %}

<figure><img src="https://4096647782-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUTz59rJLkJBjiRWAMknU%2Fuploads%2Fgit-blob-4f872cd2d90cd1d1fbed7876e500a38bfca0690b%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

In the issues table, click on an issue to view its details.

<figure><img src="https://4096647782-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUTz59rJLkJBjiRWAMknU%2Fuploads%2Fgit-blob-0775a6e59cbc34df3dcbcc2c40ae805be095a432%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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://docs.xygeni.io/xygeni-products/code-security-cs/cs-user-interface-guide/risks-sast.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.