> 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/vulnerability-management/registry-scanning/scan-google-artifact-registry.md).

# Google Artifact Registry

Although Artifact Registry supports a number of content types (for example, Java, Node.js, and Python language packages), Prisma Cloud only supports discovering and scanning Docker images.

Prisma Cloud doesn’t support scanning Helm charts saved as OCI images and stored in Artifact Registry. Helm charts saved as OCI images have a single layer that contains the Helm package. It is only a way to store a Helm chart, but it has no meaning in terms of a container. Therefore, Prisma Cloud can’t scan it.

## Create a new registry scan

**Prerequisites:**

* [Deploy a Defender](/admin-guide/install/deploy-defender/defender-types.md) somewhere in your environment.
* Create GCP credentials (service account) with, at minimum, the [Artifact Registry Reader role(`roles/artifactregistry.reader`)](https://cloud.google.com/artifact-registry/docs/access-control#roles).
* Add the service account credentials to the Prisma Cloud Compute Console credentials store under **Manage > Cloud accounts**.

1. Open Console, then go to **Defend > Vulnerabilities > Images > Registry settings**.
2. Select **Add registry**.
3. In **Version**, select **Google Artifact Registry**.
4. In **Registry**, enter the registry address.

   The format for the address is \<GCP-region>-docker.pkg.dev.

   For example, europe-north1-docker.pkg.dev

   Multi-region registry addresses are also supported, \<GCP-multi-region>-docker.pkg.dev. For example, us-docker.pkg.dev, europe-docker.pkg.dev, and asia-docker.pkg.dev.
5. In **Credential**, select the service account you created in **Manage > Cloud accounts**.

   If the credentials haven’t been created already, click **+** to create them now. If creating credentials:

   1. In **Cloud accounts onboarding**, select **GCP** for the cloud provider.
   2. Enter a credential name.
   3. Select the credential level.
   4. Paste the JSON token blob from your service account into the **Service Account** field. Leave the **API Token** field blank.
   5. Select **Next**.
   6. Disable agentless scanning, then select **Next**.
   7. Disable cloud discovery, then select **Add account**.
6. (Optional) Refine which images Prisma Cloud should scan with the **Repositories**, **Repositories to exclude**, **Tags**, and **Tags to exclude** fields.

   [Pattern matching](/admin-guide/configure/rule-ordering-pattern-matching.md) is supported.
7. In **OS type**, specify whether the repo holds **Linux** or **Windows** images.
8. In **Scanners scope**, select the Defenders to use for the scan.

   Console selects the available Defenders from this scope to execute the scan job. For more information, see [deployment patterns](/admin-guide/vulnerability-management/registry-scanning/configure-registry-scanning.md#deployment-patterns).
9. In **Number of scanners**, enter the number of Defenders across which scan jobs can be distributed.
10. Set **Cap** to the number of most recent images to scan.

    Leaving **Cap** set to **5** will scan the 5 most recent images. Setting this field to **0** will scan all images.
11. Select **Add and scan**.

    Verify that the images in the repository are being scanned under **Monitor > Vulnerabilities > Images > Registries**.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.prismacloud.io/admin-guide/vulnerability-management/registry-scanning/scan-google-artifact-registry.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.