> 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/software-supply-chain-security/visibililty-and-inventory/supply-chain-assets/vcs-organization-assets/understand-and-prioritize-vcs-organization-assets.md).

# Understand and prioritize VCS organization assets

## How to access VCS organization assets

To access VCS organization assets, under **Inventory**, select **All Assets** → **Code** → **VCS Organizations**.

The VCS Organizations assets page includes a dashboard and an inventory.

### VCS organization dashboard

The dashboard includes the following widget:

* **Providers:** Displays connected version control providers, such as GitHub, GitLab, Bitbucket, and Azure DevOps, and the number of organizations found in each provider.

Selecting an item in the widget filters the table accordingly.

### VCS organization asset inventory

The following table describes the default exposed properties of the VCS Organization asset table. Select **Menu Settings** to view additional properties.

| Property                   | Description                                                                                                                                                     |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| VCS Organization Name      | The name of the VCS organization as discovered from the VCS integration. The Organization Name serves as the primary identifier for the VCS organization asset. |
| VCS Organization Provider  | The VCS platform hosting the organization, such as GitHub, GitLab, Bitbucket, or Azure DevOps, displayed with a provider icon.                                  |
| First Observed             | The date and time the asset was initially detected and registered into the unified asset inventory during its first scan.                                       |
| Observation Time           | The date and time the asset was last updated, scanned, or seen by the platform's discovery and scanning mechanisms.                                             |
| VCS Organization URL       | The direct web address to the organization within the VCS provider platform. This enables direct navigation from the inventory to the provider console.         |
| Business Application Names | The business applications associated with the asset. VCS organizations inherit these applications from child repositories and CI/CD instances.                  |

## Filter and prioritize VCS organizations

The VCS Organizations page displays a table of all VCS organizations. Use the search bar to find specific organizations by name. Apply filters to narrow the inventory by operational and security metadata.

#### High-priority filtering workflows

Use the following filters to prioritize remediation:

* **Scope by VCS provider:** Use the **Provider** filter or dashboard widget to isolate a provider, such as GitHub or GitLab. This helps evaluate provider-specific risks and enforce platform security standards
* **Identify access control risks:** Filter by **Is MFA needed = No** to identify VCS organizations without Multi-Factor Authentication. Prioritize these foundational organization boundaries for review

## Next steps

[Investigate and manage VCS organization assets](/application-security/software-supply-chain-security/visibililty-and-inventory/supply-chain-assets/vcs-organization-assets/investigate-and-manage-vcs-organization-assets.md)


---

# 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/software-supply-chain-security/visibililty-and-inventory/supply-chain-assets/vcs-organization-assets/understand-and-prioritize-vcs-organization-assets.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.