> 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-posture-management-aspm/manage-code-weakness-issues/navigate-to-sast-code-weakness-issues.md). # Navigate to SAST code weakness issues To access SAST code violation issues, under **Modules**, select **Application Security** → **Issues** → **Code Weaknesses**. You an also view SAST issues in dedicated tabs in the [Repositories](/application-security/application-security-posture-management-aspm/repository-as-an-asset/understanding-repository-assets-via-the-ui/investigate-repository-assets.md) and [Business Applications](/application-security/application-security-posture-management-aspm/applications/business-application-assets.md#UUID-a7ca1d82-92ce-ff24-80bd-59b229e2ac47) asset side cards, or the **All Issues** inventory, filtering by **Detection Method =SAST Scanner**. The Code Weaknesses page displays a filterable, sortable table of all code weakness issues detected across monitored repositories. {% hint style="info" %} ### Note The default sort order is by **Severity** (descending). The default filter shows issues with a status of **New** and **In Progress**. Resolved issues are hidden by default. {% endhint %} The Code Weaknesses page contains two tabs: **Issues** and **Findings**. * **Issues tab**: Displays deduplicated, policy-evaluated code weakness issues. The Issues tab is the default view and the primary workspace for triage and remediation. Issues are created when a raw scanner finding matches a unified policy * **Findings tab**: Displays all raw code weakness findings detected by the SAST scanner before policy evaluation. The Findings tab provides visibility into the complete scanner output, including findings that did not generate issues because no matching unified policy exists. Use the Findings tab to audit scanner coverage, review findings excluded by current policy configurations, and identify opportunities to create new policies for uncovered finding patterns. For more information, refer to [Ingest third-party data sources](/application-security/application-security/onboard-data-sources/ingest-third-party-data-sources.md)

Note

Findings in the Findings tab are raw scanner output and do not have resolution statuses, SLA tracking, or assignees. To track remediation for a specific finding, create or update a unified policy that matches the finding pattern to generate an actionable issue in the Issues tab.

--- # 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-posture-management-aspm/manage-code-weakness-issues/navigate-to-sast-code-weakness-issues.md?ask=&goal= ``` `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.