Configure an ACR Registry Scan

Log in to Console, and select
Defend > Vulnerabilities > Images > Registry settings
.
Add registry
.
In
Add New Registry
, enter the following values:
In
Version
, select
Azure Container Registry
.
Under
Registry
, enter the Fully Qualified Domain Name (FQDN) for the registry’s ACR login server.
The format for the FQDN is
<REGISTRY_NAME>.azurecr.io
, where
<REGISTRY_NAME>
is a unique value specified when the registry was created. Example:
example.azurecr.io
.
In
Repository
, enter the name of the repository to scan. Example: 
library/alpine
.
Enter
Tag
numbers to scan, leave blank, or enter a wildcard (*) to scan all the tags.
Optionally, enter
Tags to exclude
, to avoid scanning images with specified tags.
In
Credential
, configure how Prisma Cloud authenticates with ACR.
Select a credential from the drop-down list.
If there are no credentials in the list, click
Add new
to create an Azure credential where the service principal authenticates with a password.
To scan the ACR registry in Compute, Prisma Cloud needs your Azure account credentials. Create an Azure account under
Compute > Manage > Cloud Accounts
with the permissions required to access the ACR registry, and select the same Azure credentials while configuring the registry scan for ACR.
In
OS type
, specify whether the repo holds
Linux
or
Windows
images.
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.
In
Number of scanners
, enter the number of Defenders across which scan jobs can be distributed.
In
Cap
, limit the number of images to scan.
Set
Cap
to
5
to scan the five most recent images, or enter a different value to increase or decrease the limit. Set
Cap
to
0
to scan all images.
Select
Add and scan
.
Verify that the images in the repository are being scanned under
Monitor > Vulnerabilities > Images > Registries
.