> 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/code-security/code-security-scanners/secrets-scans/secrets-findings.md). # Secrets findings **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 drift finding, create or update a unified policy that matches the finding pattern to generate an actionable issue in the Issues tab. **Reducing code weakness noise:** Urgency-based prioritization isolates the code weaknesses that affect deployed, internet-exposed, or business-critical assets from low-risk findings in development environments. CWE classification and data flow analysis further distinguish exploitable weaknesses from theoretical risks **Audit scanner coverage:** Review the full scope of IaC misconfigurations detected by the scanner to verify that detection rules are identifying the expected misconfiguration patterns across all monitored repositories and IaC frameworks. **Identify policy gaps:** Compare findings in the Findings tab against issues in the Issues tab to identify findings that are not covered by existing unified policies. Create new policies to promote high-risk findings to actionable issues. * **Audit scanner coverage:** Review the full scope of secrets detected by the scanner to verify that detection rules are identifying the expected secret types across all monitored repositories * **Identify policy gaps:** Compare findings in the Findings tab against issues in the Issues tab to identify findings that are not covered by existing unified policies. Create new policies to promote high-risk findings to actionable issues * **Review excluded findings:** Investigate findings that were excluded by policy filters to confirm that exclusions are intentional and do not suppress critical secrets exposures * **Validate detection rules:** Verify that detection rules are producing accurate findings and not generating excessive false positives for specific secret types or repositories {% hint style="info" %} ### Note **Review excluded findings:** Investigate findings that were excluded by policy filters to confirm that exclusions are intentional and do not suppress critical IaC misconfigurations. {% endhint %} #### Secrets findings inventory The Secrets **Findings** inventory includes the following properties. Use the **Table Settings Menu** to view additional properties. | Property | Description | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Name | The name or title of the finding. | | Asset Name | Name of the asset affected by the finding. Selecting an Asset Name in the table opens the asset's side card, displaying information about the asset, without having to navigate away from the Findings page. | | Risk Factors | Quantifiable attributes of a finding, allowing you to analyze and assess the risk. Options: **Found in history**, **Valid**, **Privileged** | | Data Source | Source of the finding information (the version control system) | | Rule Category | The category assigned to the rule that detected the finding | | Repository | Name of the repository hosting the asset in which the finding was detected | | Branch | The branch of code or version control branch where the finding was detected | | File Path | The file path or location within the repository where the finding was located | | Backlog Status | **Backlog Status:** Indicates if the finding is categorized as **Backlog** (pre-existing technical debt) or **New** (a recently introduced vulnerability). To understand how findings are categorized as backlog/new, refer to [Issue/Finding classification by scanner](https://app.gitbook.com/o/r4DIGbR5VLvkZy3gAYsu/sites/site_gHT7E/s/8Z0RLJ1BFF5TQL8VtUeK/~/edit/~/changes/108/application-security-posture-management-aspm/backlog-baseline/issuefinding-classification-by-scanner) | **Investigate findings details** Clicking on a finding in the table opens the **Findings** side card which provides additional details. * **Finding summary**: Found at the top of the card. Includes the finding name, ID and type (**Data** for Secrets findings) * **Description**: A description of the finding including its location * **Impact**: The potential security risk the finding poses to your environment * **Timestamp**: When the finding was last updated * **Asset details**: Includes **Asset** (The impacted asset. Clicking on the asset opens the asset side card without needing to navigate away to the asset section) and **Asset Type** (The specific asset type in which the secret was identified, , such as **JavaScript Package**) * **Evidence**: Provides evidence and contextual details within your software development lifecycle containing the finding: * **Finding source** * **Data Source:** The system or integration from which the finding data was originally pulled (such as GitHub or a CI/CD pipeline). Click the icon next to the data source to navigate to the data source itself * **Run ID:** The unique identifier of the specific scan execution during which this finding was detected * **Code context** * **Branch:** The specific branch within the repository containing the finding * **File Path:** The exact location of the finding within the repository file structure * **First Hash:** The commit hash of the first commit where this specific finding was introduced or detected * **First Commit Date**: The date of the commit that introduced the problematic code or dependency into the repository. This helps understand how long an issue has existed and for prioritizing remediation efforts based on its age * **Backlog Status**: See the inventory table above * **Collaborator**. The entity associated with the finding, contributing to or responsible for the evidence supporting it * **Code**: the code line including the finding * **Scan metadata** * **Rule ID**: The ID of the rule that triggered the finding * **Prioritization Labels**: Labels assigned to a finding (such as No Validation), which allow you to prioritize findings for further analysis or mitigation --- # 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/code-security/code-security-scanners/secrets-scans/secrets-findings.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.