> 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/understand-the-code-weaknesses-table.md). # Understand the Code Weaknesses table The code weaknesses table provides a consolidated view of all code weakness issues. Each row represents an issue created when a scanner finding matches a unified policy, linking the code weakness to a specific CWE identifier, detection rule, file, repository, and the policy that triggered the issue. **Visible columns (default)** | Column | Description | | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Severity** | The severity level assigned to the code weakness: Critical, High, Medium, Low, Informational, or Unknown. Severity is determined by the detection rule and may be overridden by a matched unified policy | | **Name** | The descriptive name of the code weakness (such as `SQL Injection detected in code`). The Name column serves as the primary identifier for the issue | | **File Path** | The path to the source code file containing the code weakness, including the affected line range (such as `/src/controllers/userController.js (42-48)`) | | **Branch** | The repository branch where the code weakness was detected (such as `main`) | | **Created** | The timestamp when the issue was first detected | | **CWE** | The Common Weakness Enumeration identifier classifying the type of code weakness (such as CWE-89: SQL Injection, CWE-79: Cross-site Scripting) | | **Prioritization Labels** | Contextual labels that indicate risk-amplifying factors such as deployment status, internet exposure, or application criticality | **Hidden columns (available via column picker)** | Column | Description | | ------------------------- | --------------------------------------------------------------------------------------------------------------- | | **Data Source** | The VCS provider where the repository is hosted (GitHub, GitLab, Bitbucket, Azure DevOps, and variants) | | **Last Updated** | The timestamp of the most recent update to the issue | | **Alert Description** | A detailed description of the code weakness, including the attack vector, impact, and recommended remediation | | **Asset ID** | The internal identifier of the SAST asset | | **Detection Method** | The scanner that detected the code weakness (CAS\_SAST\_SCANNER) | | **Alert Source** | The originating scanner source | | **Git User** | The Git author associated with the commit that introduced the code weakness | | **Finding ID** | The unique identifier of the underlying finding | | **Issue ID** | The internal issue identifier used for API operations and cross-referencing | | **Manual Fix Suggestion** | The recommended manual remediation steps, including secure code patterns | | **Rule ID** | The detection rule identifier associated with the code weakness | | **CWE ID** | The Common Weakness Enumeration identifier (such as CWE-89, CWE-79, CWE-22) | | **OWASP Category** | The OWASP Top 10 category the code weakness maps to (such as A03:2021 Injection, A07:2021 Cross-Site Scripting) | | **Language** | The programming language of the affected source code file (such as JavaScript, Python, Java, Go, C#) | | **Code Lines** | The specific line range within the file where the code weakness occurs | | **Code Block** | The source code snippet containing the code weakness | | **Code Highlights** | The specific lines within the code block that are flagged | | **Data Flow** | The data flow trace from the source (user input) to the sink (vulnerable function call), when available | | **Domain** | The security domain classification (such as POSTURE) | | **Assignee** | The user assigned to remediate the issue | | **Assignee Name** | The display name of the assigned user | | **Resolution Status** | The current resolution state: **New**, **In Progress**, or **Resolved** | | **Resolution Comment** | The comment provided when the resolution status was changed | | **Original Severity** | The severity assigned by the detection rule before any policy override | | **Provider Link** | A direct link to the file in the VCS provider | | **Rule ID Link** | A link to the detection rule documentation | | **Finding Category** | The category classification of the finding (such as Application Security). | | **Subcategory** | The subcategory classification of the finding | | **Tags** | User-defined or system-generated tags applied to the issue | **Filter and sort the table** Use the filter bar at the top of the Code Weaknesses table to narrow results by any filterable column. Common filtering strategies include: * **By Severity:** Filter to **Critical** and **High** severity to focus on the most impactful code weaknesses * **By CWE:** Filter to a specific CWE identifier (such as **CWE-89**) to scope remediation to a single weakness category * **By Language:** Filter to a specific programming language (such as **Java**) to scope remediation to a single technology stack * **By Branch:** Filter to the **main** or **production** branch to focus on code weaknesses that affect production-bound code * **By Resolution Status:** Filter to **New** to identify untriaged code weakness issues, or to **In Progress** to monitor active remediation * **By OWASP Category:** Filter to a specific OWASP Top 10 category (such as **A03:2021 Injection**) to focus on a specific risk class --- # 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/understand-the-code-weaknesses-table.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.