Scan Images in GitLab Container Registry
Table of Contents
Prisma Cloud Enterprise Edition
Expand all | Collapse all
-
- Getting started
- System Requirements
- Cluster Context
-
- Defender Types
- Manage your Defenders
- Redeploy Defenders
- Uninstall Defenders
-
- Deploy Orchestrator Defenders on Amazon ECS
- Automatically Install Container Defender in a Cluster
- Deploy Prisma Cloud Defender from the GCP Marketplace
- Deploy Defenders as DaemonSets
- VMware Tanzu Application Service (TAS) Defender
- Deploy Defender on Google Kubernetes Engine (GKE)
- Google Kubernetes Engine (GKE) Autopilot
- Deploy Defender on OpenShift v4
- Deploy Defender with Declarative Object Management
-
- Agentless Scanning Modes
-
- Onboard AWS Accounts for Agentless Scanning
- Configure Agentless Scanning for AWS
- Onboard Azure Accounts for Agentless Scanning
- Configure Agentless Scanning for Azure
- Onboard GCP Accounts for Agentless Scanning
- Configure Agentless Scanning for GCP
- Onboard Oracle Cloud Infrastructure (OCI) Accounts for Agentless Scanning
- Configure Agentless Scanning for Oracle Cloud Infrastructure (OCI)
- Agentless Scanning Results
-
- Rule ordering and pattern matching
- Backup and Restore
- Custom feeds
- Configuring Prisma Cloud proxy settings
- Prisma Cloud Compute certificates
- Configure scanning
- User certificate validity period
- Enable HTTP access to Console
- Set different paths for Defender and Console (with DaemonSets)
- Authenticate to Console with Certificates
- Customize terminal output
- Collections
- Tags
- WildFire Settings
- Log Scrubbing
- Permissions by feature
-
- Prisma Cloud Vulnerability Feed
- Scanning Procedure
- Vulnerability Management Policies
- Vulnerability Scan Reports
- Scan Images for Custom Vulnerabilities
- Base images
- Vulnerability Explorer
- CVSS scoring
- CVE Viewer
-
- Configure Registry Scans
- Scan Images in Alibaba Cloud Container Registry
- Scan Images in Amazon Elastic Container Registry (ECR)
- Scan images in Azure Container Registry (ACR)
- Scan Images in Docker Registry v2 (including Docker Hub)
- Scan Images in GitLab Container Registry
- Scan images in Google Artifact Registry
- Scan Images in Google Container Registry (GCR)
- Scan Images in Harbor Registry
- Scan Images in IBM Cloud Container Registry
- Scan Images in JFrog Artifactory Docker Registry
- Scan Images in Sonatype Nexus Registry
- Scan images in OpenShift integrated Docker registry
- Scan Images in CoreOS Quay Registry
- Trigger Registry Scans with Webhooks
- Configure VM image scanning
- Configure code repository scanning
- Malware scanning
- Windows container image scanning
- Serverless Functions Scanning
- VMware Tanzu Blobstore Scanning
- Scan App-Embedded workloads
- Troubleshoot Vulnerability Detection
-
- Compliance Explorer
- Enforce compliance checks
- CIS Benchmarks
- Prisma Cloud Labs compliance checks
- Malware Scanning
- Serverless functions compliance checks
- Windows compliance checks
- DISA STIG compliance checks
- Custom compliance checks
- Trusted images
- Host scanning
- VM image scanning
- App-Embedded scanning
- Detect secrets
- OSS license management
-
- Alert Mechanism
- AWS Security Hub
- Cortex XDR alerts
- Cortex XSOAR alerts
- Email alerts
- Google Cloud Pub/Sub
- Google Cloud Security Command Center
- IBM Cloud Security Advisor
- JIRA Alerts
- PagerDuty alerts
- ServiceNow alerts for Security Incident Response
- ServiceNow alerts for Vulnerability Response
- Slack Alerts
- Splunk Alerts
- Webhook alerts
- API
Scan Images in GitLab Container Registry
Configure Prisma Cloud to scan your GitLab Container Registry on GitLab without using administrator credentials.
You can use GitLab Personal access token method to authenticate Prisma to access the GitLab Container Registry to manage and get a full list of all container registries/images.
Create a New Registry Scan
Prerequisites
- Install a Defender somewhere in your environment.
- Enable the GitLab Container Registry under your GitLab project settings if it’s not enabled already. See the GitLab administrator documentation to enable GitLab Container Registry across your GitLab instance.
- Create a GitLab Personal access token with at least "read_api" scope permission.
- Log in to Console, and selectDefend > Vulnerabilities > Images > Registry settings.
- SelectAdd registry.
- InAdd New Registry, enter the following values:
- InVersion, selectGitLab Container Registry.
- InRegistry, enter your custom domain URL address to scan. If you don’t have a custom GitLab domain, enter the URL as "https://registry.gitlab.com".
- InRepository, enter the name of the repository to scan, or leave this blank to scan all repositories.
- Optionally enter theRepositories to excludethem from being scanned.
- InRepository types, select the repository types that Prisma Cloud should scan.
- EnterTagnumbers to scan, leave blank, or enter a wildcard (*) to scan all the tags.
- Optionally, enterTags to exclude, to avoid scanning images with specified tags.
- Enter the details for at least one of the fields based on your GitLab configuration:
- User ID: GitLab user account. The user ID is used to get all registries associated with the user.
- Group ID: Enter a single group ID, or a list of group IDs. The group ID is used to locate all the registries within a specific group.
- Project ID: Enter a GitLab Project ID, or a list of project IDs. The project ID is used to locate all the registries located within a specific project.
- To trigger a full scan, including all repositories associated with the User ID you provided, enter the User ID.
- When you enter all 3 IDs, Prisma Cloud uses the Project ID and the Group ID to query the GitLab registry. The User ID is not used.
- When you enter any of the following two choices, the ID used to query is
- User ID and Group ID, Prisma Cloud uses the Group ID to query the registry.
- User ID and Project ID, the Project ID is used.
- Group ID and Project ID, both IDs (AND logic) are used.
- Group IDs to exclude- Only top-level groups should be set here. When user set top-level group to exclude, sub-groups will also be excluded.
- InCredential, select the GitLab access token credentials that you created in the prerequisites section.
- InOS type, specify whether the repo holdsLinuxorWindowsimages.
- InScanners 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 theNumber of scannerssetting. For more information, see deployment patterns.
- InNumber of scanners, enter the number of Defenders across which scan jobs can be distributed.
- SetCapto the number of most recent images to scan. LeavingCapset to the default value of5will scan the most recent 5 images. Setting this field to0will scan all images.
- SelectAdd and scan.Verify that the images in the repository are being scanned underMonitor > Vulnerabilities > Images > Registries.