> 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/application-security-scans-management/manage-scans-through-the-tenant-ui/pull-request-scans.md).

# Pull Request scans

Pull Request (PR) scans are initiated by events triggered by version control systems such as GitHub, GitLab, Bitbucket and Azure Repos, or via webhooks. These scans are run on default or non-default branches containing open PRs or Merge Requests (MR) from your integrated repositories.

The system executes scans based on the following logic:

* **Initial Scan (PR/MR Open)**: When a new PR or MR is opened, the system performs a full scan of all files included in the request
* **Subsequent Scan (New Commits)**: For any new commit pushed to an existing open PR/MR, the system executes a delta analysis (diff scan). This focused scan analyzes only the modified files, which prevents redundant findings. The PR comments are updated according to the results of the latest commit scan

Scan results are based on default enforcement thresholds. You can analyze PR scans directly from the dedicated inventory table, which displays detailed metrics including code context, scan date, health, status, detected findings, and generated issues.

## How to access Pull Request scans

Under **Modules** select **Application Security** → **Pull Request Scans (under Scans)**.

#### Pull Request scan inventory

The pull request scan inventory displays the following details:

* **Repository**: Identifies the scanned repositories
* **Organization**: Specifies the organization owning the repository
* **Scanned Branch**: Indicates the branch analyzed during the scan
* **Scan Date**: Records the timestamp of the last scan execution
* **Pull Request ID**: The unique identifier of the PR
* **Commit**: The commit included in the PR
* **Scan Health**: Displays the health of the scan. Values include:
  * Error
  * Partially: Indicates that the scan execution resulted in a partial completion, with some scan modules (for example IaC) succeeding and others (such as Secrets) failing
  * Completed
* **PR Status**: Status of the PR scan. Values: "Passed', 'Blocked', 'In Progress'

{% hint style="info" %}

### Note

The inventory table displays scan issues for visibility only; remediation is not available here. To resolve issues, navigate to the dedicated issue type inventory, where you can manage and remediate them.
{% endhint %}

## Expanded Pull Request scan details

Selecting a scan from the inventory opens its side car, which displays a general overview of the scan's details and provides access to details of issues and findings via dedicated scan type tabs.

{% tabs %}
{% tab title="Overview" %}
The overview tab displays these scan details.

* **General scan information**
  * **Organization**: The specific business entity or organizational unit associated with the periodic scan
  * **Scan Date**: The date and time when the periodic scan was performed
  * **Scan Health**: The overall health status of the periodic scan, indicating its success, failure, or other relevant states
* **Code context**
  * **Repository**: The version control repository that was scanned
  * **Scanned Branch**: The specific branch within the repository that was subjected to the periodic scan
* **Scan results summary**
  * **Issues**: A breakdown by severity and count of actionable security issues identified from the scan's findings
  * **Issues by Type**: A categorization and count of identified issues based on their specific vulnerability types (such as IaC, Secrets)
  * **Findings**: A breakdown by severity and count of findings discovered by the scan before being converted into actionable issues
  * **Findings by Type**: A categorization and count of raw findings based on their specific detection types.
    {% endtab %}

{% tab title="Vulnerabilities" %}
Selecting the **Vulnerabilities** tab, the **Issues** tab is displayed by default. Selecting an entry then opens its side card (which includes remediation options) directly within Scans Management, eliminating the need to navigate to the dedicated **Vulnerabilities** issues page.

For detailed information about vulnerabilities issues, refer to [Software Composition Analysis (SCA) vulnerability issues](/application-security/code-security/code-security-scanners/software-composition-analysis-sca-scanners/software-composition-analysis-sca-vulnerability-issues.md).

Select the Findings tab to open a list of findings associated with the issue, including the name of the finding, the asset in which the finding was detected, and the repository hosting the asset.

Click on a finding for additional details, including a description of the finding the asset type and group associated with the finding, when last updated, and evidence for the finding.
{% endtab %}

{% tab title="Configurations" %}
When selecting the **Configurations** tab, the **Issues** tab is displayed by default. Selecting an issue in the table that is presented then opens its side card directly within Scans Management, eliminating the need to navigate to the dedicated **IaC misconfigurations** issues page.

For detailed information about IaC misconfiguration issues, refer to [Navigate to IaC misconfiguration issues](broken://spaces/8Z0RLJ1BFF5TQL8VtUeK/pages/Xp3R7VUb7FGxiGkDXVs8).

Select the Findings tab to open a list of findings associated with the issue, including the name of the finding, the asset in which the finding was detected, and the repository hosting the asset.

Click on a finding for additional details, including a description of the finding the asset type and group associated with the finding, when last updated, and evidence for the finding.
{% endtab %}

{% tab title="Secrets" %}
When selecting the **Secrets** tab, the **Issues** tab is displayed by default. Selecting an issue in the table that is presented then opens its side card directly within Scans Management, eliminating the need to navigate to the dedicated **Secrets** issues page.

For detailed information about Secrets issues, refer to [Navigate to secrets issues](broken://spaces/8Z0RLJ1BFF5TQL8VtUeK/pages/qK2cWoNaeXpUqeehwmmF).

Select the Findings tab to open a list of findings associated with the issue, including the name of the finding, the asset in which the finding was detected, and the repository hosting the asset.

Click on a finding for additional details, including a description of the finding the asset type and group associated with the finding, when last updated, and evidence for the finding.
{% endtab %}

{% tab title="Package Integrity" %}
When selecting the **Package Integrity** tab, the **Issues** tab is displayed by default, displaying a list of package operational risk and license issues, with detailed properties for each entry. Selecting an entry then opens its side card directly within Scans Management, eliminating the need to navigate to the dedicated **Package Integrity** issues page.

For detailed information about **Package Integrity** issues, refer to [Package operational risk scanner](/application-security/code-security/code-security-scanners/software-composition-analysis-sca-scanners/package-operational-risk-scanner.md).

Select the Findings tab to open a list of findings associated with the issue, including the name of the finding, the asset in which the finding was detected, and the repository hosting the asset.

Click on a finding for additional details, including a description of the finding the asset type and group associated with the finding, when last updated, and evidence for the finding.
{% endtab %}
{% endtabs %}


---

# 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/application-security-scans-management/manage-scans-through-the-tenant-ui/pull-request-scans.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.