> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/application-security/get-started/connect-code-and-build-providers/add-private-registries.md).
# Package Registries
Integrate private registries to gain visibility into packages of your private registry, to provide precise dependency trees, and to scan for and fix vulnerabilities affecting images or harmful elements that have entered the registry through the software supply chain.
Currently, Prisma Cloud Application Security supports one Artifactory integration, one registry per package manager and is limited to Maven, Gradle, NPM, Yarn, and Pip.
1. Before you begin.
1. Add the Prisma Cloud IP addresses and hostname for Application Security to an [allow list](/content-collections/get-started/console-prerequisites.md) to enable access to the Prisma Cloud console.
2. Grant **Administrator** permissions from Artifactory to the Prisma user integrating Prisma Cloud with your registry. However, a read-only permission of an Artifactory will not impact the scan results on the console.
2. On the Prisma Cloud Application Security console.
1. In Application Security, select **Home** > **Settings** > **Connect Provider** > **Code & Build Providers**.
2. Select **Artifactory** (under Private Registries) in the catalog that is displayed.
The **Select a Registry** step of the integration wizard is displayed.
3. Enter your **Public Artifactory URL**, **Username** and **Password** in the provided fields.
* The URL must include the suffix `/artifactory`. For example, `https://artifactory.org-name.io/artifactory`
* The permissions associated with the username determine the scope of the scan results for private registries
4. Select **Next**.
The **Setup Package Managers** step of the wizard is displayed.
5. Select a package manager to configure a registry as private instead of the default public registry.
Package managers not listed will default to the public registry.
6. Select a **Registry** that is compatible with the package managers in use.
NOTES \* *NPM* requires you to define your repository as **Private**.
* For *Maven*, you can select **Mirror Registry** if the repository is a mirror of an existing repository.
7. Optionally, select **Add Package** to set up an additional package manager.
8. Select **Next** and then select **Done**.
3. Verify integration.
1. In **Application Security**, select **Home** > **Settings** > **Private Registries** tab.
2. View integrations and their connection under the **Status** column.
3. Additionally, you can view the dependency tree of the private packages dependency trees in the **Supply Chain**.
## Remediation
You can remediate vulnerabilities detected on private registries in **Application Security** through **Home** > **Projects** > **Vulnerabilities**.
## Manage Integrations
For each integration you can perform additional actions through **Actions**.
* **Edit integration**
* **Delete integration**: If an integration has multiple registries, you can choose to delete it.
* **Delete entire integration**
Optionally, you can choose to delete a private registry integration through the console. In \* Application Security\*, select **Home** > **Settings** > **Repositories** > **Add Repository** > **Private Registries** > **Artifactory** and then select **Delete** in the **Select a Registry** step of the wizard.
After integrating a private registry, the registry becomes the default reference for package versions on the console. If a private fix version for the registry is not available, the console will recommend a public fix version.
---
# 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://docs.prismacloud.io/content-collections/application-security/get-started/connect-code-and-build-providers/add-private-registries.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.