Scan Images in Sonatype Nexus Registry
Table of Contents
Expand all | Collapse all
-
- Getting started
- System Requirements
- Cluster Context
-
- Prisma Cloud Container Images
- Kubernetes
- Deploy the Prisma Cloud Console on Amazon ECS
- Console on Fargate
- Onebox
- Alibaba Cloud Container Service for Kubernetes (ACK)
- Azure Container Service (ACS) with Kubernetes
- Azure Kubernetes Service (AKS)
- Amazon Elastic Kubernetes Service (EKS)
- IBM Kubernetes Service (IKS)
- OpenShift v4
-
- 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
-
- Agentless Scanning Modes
-
- Onboard AWS Accounts for Agentless Scanning
- 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
- Configure custom certs from a predefined directory
- Customize terminal output
- Collections
- Tags
- Logon settings
- Reconfigure Prisma Cloud
- Subject Alternative Names
- WildFire Settings
- Log Scrubbing
- Clustered-DB
- Permissions by feature
-
- Logging into Prisma Cloud
- Integrating with an IdP
- Integrate with Active Directory
- Integrate with OpenLDAP
- Integrate Prisma Cloud with Open ID Connect
- Integrate with Okta via SAML 2.0 federation
- Integrate Google G Suite via SAML 2.0 federation
- Integrate with Azure Active Directory via SAML 2.0 federation
- Integrate with PingFederate via SAML 2.0 federation
- Integrate with Windows Server 2016 & 2012r2 Active Directory Federation Services (ADFS) via SAML 2.0 federation
- Integrate Prisma Cloud with GitHub
- Integrate Prisma Cloud with OpenShift
- Non-default UPN suffixes
- Compute user roles
- Assign roles
-
- 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
- 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 Sonatype Nexus Registry
To scan a repository in Sonatype Nexus Registry, create a new registry scan setting.
Prerequisites
- You have installed a Container Defender somewhere in your environment.
- Configure the connector port for the Docker engine to connect to the Nexus registry.The Docker client needs the Docker registry exposed at the root of the host together with the port that it is accessing. Nexus offers several methods to overcome this limitation, one of which is the connector port method, which Prisma Cloud supports.
- From the Nexus web portal, select the Administration screen.
- Select the Nexus Repository.
- SelectOnlineto allow the Nexus repository to accept the incoming requests.
- Configure the Docker repository connector to use an HTTP or HTTPS port.
- The Defender can establish a connection with the Nexus registry over the connector port that you configured in the Nexus registry.Ensure that the port is open for the image to be accessed successfully.
Configure a Nexus Registry in Prisma Cloud
- Log in to Console, and selectCompute > Defend > Vulnerabilities > Images > Registry settings.
- SelectAdd registry.
- In theAdd New Registry Setting Specification, enter the following values:
- In theVersiondrop-down list, selectSonatype Nexus.
- InRegistry, enter the hostname, or Fully Qualified Domain Name (FQDN), and the connector port for the Nexus registry’s login server.The format for the FQDN is<hostname>:<connector_port>, where<hostname>is a unique value specified when the registry was created, and the<connector_port>is the one you configured in the Nexus repository administration.Example:<http|https://<nexus_hostname>:<HTTP/HTTPS connector port for the specific Nexus repo>.
- Leave theRepositoryblank or include a pattern to match the Docker repositories inside the Nexus registry.For example: To scan all the images under a path, include thepath/tostring.
- Optionally enter the Repositories to exclude them from being scanned.
- InTag, enter an image tag. Leave this field blank to scan all images, regardless of their tag.
- Optionally, enter Tags to exclude, to avoid scanning images with specified tags.
- InCredential, configure how Prisma Cloud authenticates with Nexus registry.Select a credential from the drop-down list.If there are no credentials in the list,Addnew credentials and select the Basic authentication.
- You can optionally enter a customCA certificatein PEM format for Prisma Cloud to validate the Nexus 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.
- 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.
- InCap, limit the number of images to scan.SetCapto5to scan the five most recent images, or enter a different value to increase or decrease the limit. SetCapto0to scan all images.
- SelectAdd and scan.Verify that the images in the repository are being scanned underMonitor > Vulnerabilities > Images > Registries.
Troubleshooting
Prisma Cloud failed to pull images from the Nexus repository
Monitor > Vulnerabilities > Images > Registries
shows the following error:
- Ensure that you have installed Defender on the host on which the Nexus registry is installed.
- Verify that you can pull the nexus registry using the docker command.
- Create a Nexus repository connector port as mentioned in the Prerequisites.
- Configure a Nexus Registry in Prisma Cloud using the connector port in the Registry URL.