> 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/admin-guide/33/vulnerability-management/registry-scanning/scan-harbor.md). # Harbor Configure Prisma Cloud to scan your Harbor registry. ## Create a new registry scan To scan a repository in Harbor, create a new registry scan setting. 1. Open Console 2. Go to **Defend > Vulnerabilities > Images > Registry Settings**. 3. Select **Add Registry**. 4. In the dialog, enter the following information: 1. In **Version**, select **Harbor**. 2. In **Registry**, enter the FQDN of your Harbor registry. 3. In **Repository**, enter the name of the repository to scan, or leave this blank to scan all repositories. 4. Optionally enter the Repositories to exclude them from being scanned. 5. In **Tag**, enter an image tag. Leave this field blank to scan all images, regardless of any tags. 6. Optionally, enter Tags to exclude, to avoid scanning images with specified tags. 7. In **Credential**, select the credentials to use. If Console doesn’t have a copy of your credentials yet, click **Add New**. Select **Basic authentication**, and fill out the rest of the fields. The minimum required credentials for each repository is **Limited Guest**. 8. The **Bypass deployment security** toggle is applicable only when using Prisma Cloud Compute pluggable scanner. To scan Harbor projects with the deployment security setting enabled, Harbor requires additional permissions that can not be granted with a regular user credentials. When the toggle is ON, Prisma Cloud Compute scans the registry using a temporary token provided by Harbor in the scanning request, instead of the credentials provided in the settings. This token has sufficient permissions to bypass the deployment security setting, and it’s the mechanism Harbor provides to allow external security scanners to scan these projects. When the toggle is OFF, Prisma Cloud Compute uses the credentials provided in the setting to scan the registry. It will not be able to scan images in Harbor projects with the deployment security setting enabled. Harbor’s token expiration time must be at least 30 minutes so that it won’t expire during the Prisma Cloud scanning process. If you set the expiration period to less than 30 minutes, registry scanning might fail. 9. You can optionally enter a custom **CA certificate** in PEM format for Prisma Cloud to validate the Harbor registry. Custom CA certificate validation is supported only for non-Docker nodes (e.g. OpenShift). Ensure that the Custom CA certificate that you use is not revoked by the issuing authority. 10. In **OS type**, specify whether the repo holds **Linux** or **Windows** images. 11. In **Scanners scope**, specify the collections of defenders to use for the scan. Console selects the available Defenders from the scope to execute the scan job according to the **Number of scanners** setting. For more information, see [deployment patterns](/admin-guide/33/vulnerability-management/registry-scanning/configure-registry-scanning.md#deployment-patterns). 12. In **Number of scanners**, enter the number of Defenders across which scan jobs can be distributed. 13. Set **Cap** to the number of most recent images to scan. Leaving **Cap** set to the default value of **5** will scan the most recent 5 images. Setting this field to **0** will scan all images. 5. Select **Add and scan**. Verify that the images in the repository are being scanned under **Monitor > Vulnerabilities > Images > Registries**. ## Integrate Compute as pluggable scanner Configure Compute as a pluggable scanner to view vulnerability scan results in Harbor Console itself, in addition to Compute Console. To add Compute as a vulnerability scanner in Harbor, follow steps outlined above for adding Harbor registry in Compute Console. Thereafter, follow the steps below in Harbor: 1. In Harbor, go to the Administration > Interrogation Services page and click New Scanner. 2. In the pop up, enter your Compute Console details. 1. In **Name**, provide a name for the scanner. 2. In **HTTP Endpoint**: Login to your Compute Console, navigate to Defend > Vulnerabilities > Registry page. Under **Harbor scanner adapter** section, copy the URL from field b: "Use the following URL as the Harbor Scanner endpoint". This section only becomes visible after adding Harbor Registry in Compute Console as a registry as per steps outlined in section above. 3. **Authorization: None**: Due to a current bug in all Harbor versions other types of authentication methods result in error messages. See 3. Test Connection and select **Save**. You can now go to Vulnerability tab under Interrogation services and hit Scan Now for vulnerability scanning reports. Note that when a scan is revoked from Harbor Console using Compute as a vulnerability scanner, Harbor pulls scan from Compute Console. In order to receive faster results, make sure you scan the registry on Compute Console as well. --- # 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/admin-guide/33/vulnerability-management/registry-scanning/scan-harbor.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.