> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/application-security/application-security/onboard-data-sources/ingest-third-party-data-sources/semgrep/semgrep-static-application-security-testing-sast-data-ingestion.md).

# Understand and manage Semgrep SAST data ingestion

The Semgrep integration enables automated ingestion of Semgrep SAST scan results into Cortex Cloud. The ingested findings appear alongside findings from native Cortex scanners and other third-party integrations (such as Snyk).

## Key benefits

* **Centralizing Semgrep findings**: Semgrep SAST findings are normalized into the same data model as native Cortex code weakness findings, enabling unified triage, policy enforcement, and reporting
* **Extending Coverage visibility**: The **AppSec Coverage** page displays a dedicated **Semgrep** column that indicates which repositories have Semgrep scanning enabled, and a **Code Weaknesses** column that reflects aggregate SAST scanning status
* **Enabling policy enforcement**: Semgrep SAST findings are evaluated against Application Security policies, enabling block actions on PRs and CI pipelines based on Semgrep-detected code weaknesses

## Manage code weakness (SAST) findings and issues

The most practical workflow is to first narrow down your candidate set using a repository search, and then verify the exact attribution on a per-issue basis.

### Triage and remediate Semgrep issues by repository

1. Navigate to **Application Security** → **AppSec Coverage**.
2. In the table, filter for `is_scanned_by_semgrep=true` to identify repositories with active Semgrep scanning.
3. Select a repository in the filtered list to open its side card for details.
4. Select **Issues** to open the platform **Issues** page.

{% hint style="info" %}
The page is filtered by Semgrep issues.
{% endhint %}

5. Filter the **Category** column by **Code**.\
   All SemGrep code weakness issues are displayed.
6. Select an issue in the filtered list to open its side card for details and remediation options.

### Triage and remediate Semgrep-origin issues from the issue side panel

1. Navigate to **Modules** **→ Application Security → Code Weaknesses**.
2. Open any code weakness issue by selecting the row.
3. In the issue side panel, locate the **Scanner** field in the impact fields section, which identifies **Semgrep** as the originating scanner.
4. Select **Issues** to open the platform **Issues** page.

### Understand Semgrep-origin findings

1. Navigate to **Modules** **→ Application Security → Code Weaknesses**.
2. Switch to the **Findings** tab (using the control at the top of the **Code Weaknesses** page).
3. Filter the **Data Source** column by SEMGREP to isolate Semgrep-originated findings.

### Learn more

For detailed information about SAST findings and issues, refer to [SAST code weaknesses (CWEs)](/application-security/application-security-posture-management-aspm/manage-code-weakness-issues.md).


---

# 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://cortex-docs.paloaltonetworks.com/application-security/application-security/onboard-data-sources/ingest-third-party-data-sources/semgrep/semgrep-static-application-security-testing-sast-data-ingestion.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.