Onboard Oracle Cloud Infrastructure (OCI) Accounts for Agentless Scanning
Table of Contents
Self.Hosted 31.xx
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
Onboard Oracle Cloud Infrastructure (OCI) Accounts for Agentless Scanning
Agentless scanning lets you inspect the risks and vulnerabilities of a virtual machine without having to install an agent or affecting the execution of the instance. Prisma Cloud gives you the flexibility to choose between agentless and agent-based security using Defenders. Currently, Prisma Cloud supports agentless scanning on Oracle Cloud Infrastructure (OCI) for vulnerabilities and compliance. To learn more about how agentless scanning works, see the How Agentless Scanning Works?[How Agentless Scanning Works?]
This guide enables Agentless scanning for Prisma Cloud Compute Edition (PCCE, self-hosted) in OCI.
The procedure shows you how to complete the following tasks.
- Create an OCI compartment to run the needed instances in OCI that perform the agentless scanning.
- Create a new OCI user for Prisma Cloud to access OCI.
- Create an API key in OCI for the new user.
- Configure the Prisma Cloud console to access the OCI resources.
- Apply the needed permissions in OCI.
- Start an agentless scan.
Create an OCI Compartment
- Go to the Oracle Cloud console.
- In the menu, go toIdentity & Security > Compartments.
- ClickCreate Compartment.
- Enter a name and a description for the compartment.
- ClickCreate Compartment.To scan all resources across all regions, you must create the resources for the different regions in the compartment. Make sure to create all needed resources with the same name in all regions.
Create a New OCI User
- In the menu, go toIdentity & Security > Users.
- ClickCreate User.
- SelectIAM User.
- Enter aNameand aDescriptionfor the user.
- ClickCreate.
Create an API Access Key
- On the user page, go toResources > API Key.
- SelectGenerate API Key Pair.
- ClickDownload Private Key.
- ClickAdd.
- TheConfiguration File Previewopens.
- Copy the key-value pair for user into a text file.
- Copy the key-value pair for fingerprint into a text file.
- Copy the key-value pair for tenancy into a text file.
- Save the text file.
- ClickClose.
Configure Agentless Scanning
Complete the agentless scanning configuration for your OCI accounts.
Apply the Permissions in OCI
- Go to the Oracle Cloud console.
- Click on the terminal icon on the right hand corner and selectCloud Shell.
- Click the gear icon on the shell, and selectUpload File.
- Select the pcc-apply-permissions.sh permission template you downloaded from the Prisma Cloud Console.
- Make the file executable with the following command.chmod +x pcc-apply-permissions.shApply the permissions with the following command. Replace <OCI-Compartment> with the name of the created compartment.apply pcc-apply-permissions.sh <OCI-Compartment>Verify that the changed statements for the policy are correct and enter y to continue.Enter y to dismiss the warning about tags.Once the permissions are applied, you have an OCI user with the needed permissions.
- Go toManage > Cloud accounts.
- Click the scan icon on the top right corner of the accounts table.
- ClickStart Agentless scan.
- Click the scan icon in the top right corner of the console to view the scan status.
- View the results.
- Go toMonitor > Vulnerabilities > HostsorMonitor > Vulnerabilities > Images.
- Click on theFilter hoststext bar.
- Select theScanned byfilter.
- Select theAgentlessfilter.
Start an Agentless Scan
Agentless scans start immediately after onboarding the cloud account.
By default, agentless scans are performed every 24 hours, but you can change the interval on the
Manage > System > Scan
page under Scheduling > Agentless
.
To manually start a scan, complete the following steps.