> 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.md).

# Manage scans through the tenant (UI)

The Cortex Cloud console provides a centralized, visual interface to track scan health, configure scanners, and resolve detected issues across your repositories and pipelines.

## How to access scan management

1. Under **Modules**, select **Application Security**.
2. Under **Scans**, select a scan type:
   * **Branch Periodic scanning**: Scans code branches on a schedule to identify vulnerabilities early in development. For more information about branch periodic scans, refer to [Branch periodic scans](/application-security/code-security/application-security-scans-management/manage-scans-through-the-tenant-ui/branch-periodic-scans.md)
   * **Pull Request scans**: Scans code changes within pull requests to prevent the introduction of new vulnerabilities. For more information about pull request scans, refer to [Pull Request scans](/application-security/code-security/application-security-scans-management/manage-scans-through-the-tenant-ui/pull-request-scans.md)
   * **CI scans**: Detects exposed secrets, misconfigurations, package vulnerabilities, and license non-compliance in your continuous integration pipelines. For more information, refer to [CI scans](/application-security/code-security/application-security-scans-management/manage-scans-through-the-tenant-ui/ci-scans.md)

## Scan data presentation

Periodic, pull request and CI scan details are presented on the Cortex Cloud console across two levels of granularity: an inventory table providing a list of scans, and a side panel providing general scan details including a high-level breakdown of the findings and issues detected during the scan, and an expanded description card, providing detailed information about the issues generated from these scans.

{% hint style="info" %}

### Note

While scans provide a comprehensive inventory of all issues detected during a scan, dedicated inventories are also maintained for specific scan types for more granular management. For more information, refer to [Code Security scanners](/application-security/code-security/code-security-scanners.md).
{% endhint %}


---

# 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.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.