Oracle Cloud Infrastructure Vulnerability Scanning Service helps improve your security posture by routinely checking hosts and container images for potential vulnerabilities. The service gives developers, operations, and security administrators comprehensive visibility into misconfigured or vulnerable resources, and generates reports with metrics and details about these vulnerabilities including remediation information.
Watch a video introduction to the service.
The Scanning service identifies vulnerabilities in the following resources:
- Compute instances (also known as hosts)
- Container Registry images
The Scanning service can identify several types of security issues:
- Ports that are unintentionally left open might be a potential attack vector to your cloud resources, or enable hackers to exploit other vulnerabilities.
- OS packages that require updates and patches to address vulnerabilities.
- OS configurations that hackers might exploit.
- Industry-standard benchmarks published by the Center for Internet Security (CIS).
The Scanning service checks hosts for compliance with the section 5 (Access, Authentication, and Authorization) benchmarks defined for Distribution Independent Linux.
- Vulnerabilities in third-party applications such as
Oracle Cloud Infrastructure Vulnerability Scanning Service can help you quickly correct vulnerabilities and exposures, but the service isn’t a Payment Card Industry (PCI) compliant scanner. Don’t use the Scanning service to meet PCI compliance requirements.
The Scanning service only supports compute instances created from supported platform images. Scanning isn’t available for any image with the label end of support.
To scan a compute instance for vulnerabilities, the instance must use an image that supports Oracle Cloud Agent. Port scanning on an instance's public IP address doesn’t require an agent.
The Scanning service detects vulnerabilities in the following platforms and using the following vulnerability sources.
Because Windows scanning doesn’t include OVAL data, we don't recommend you rely solely on Oracle Cloud Infrastructure Vulnerability Scanning Service to ensure that your Windows instances are up-to-date and secure.
We don't recommend using the Scanning service to identify issues in Virtual Machine DB Systems, and then modifying the OS to address each issue. Instead, follow the instructions at Updating a DB System to apply the latest security updates to the OS.
You can't use the Scanning service on hosts that weren't created directly with the Compute service, such as Exadata Database Service on Dedicated Infrastructure or the Database service. Use the features provided with those services to ensure that hosts have the latest security updates.
The Scanning service supports the following target options:
- Individual compute instances
- All compute instances within a compartment and its subcompartments.
If you configure the Scanning service at the root compartment, then all compute instances in the entire tenancy are scanned.
- Images within a Container Registry repository
Understand key concepts and components related to the Scanning service.
The following diagram provides a high-level overview of the service.
- Scan Recipe
- Scanning parameters for a type of cloud resource, including what information to examine and how often.
- One or more cloud resources that you want to scan using a specific recipe. Resources in a target are of the same type, such as compute instances.
- Host Scan
- Metrics about a specific compute instance that was scanned, including the vulnerabilities that were found, their risk levels, and CIS benchmark compliance.
The Scanning service uses a host agent to detect these vulnerabilities.
- Port Scan
- Open ports that were detected on a specific compute instance that was scanned.
The Scanning service can detect open ports using a host agent, or using a network mapper that searches your public IP addresses .
- Container Image Scan
- Metrics about a specific Container Registry image that was scanned, including the vulnerabilities that were found and their risk levels.
- Vulnerabilities Report
- Information about a specific type of vulnerability that was detected in one or more targets, like a missing update for an OS package.
Integration with Cloud Guard
You can view security vulnerabilities identified by the Scanning service in Oracle Cloud Guard.
Cloud Guard is an Oracle Cloud Infrastructure service that provides a central dashboard to monitor all of your cloud resources for security weakness in configuration, metrics, and logs. When it detects a problem, it can suggest, assist, or take corrective actions, based on your Cloud Guard configuration.
Like the Scanning service, Cloud Guard uses recipes and targets.
- A recipe defines the types of problems that you want Cloud Guard to report
- A target defines the compartments that you want Cloud Guard to monitor, and is associated with a recipe.
A configuration detector recipe consists of detector rules. The default Cloud Guard configuration detector recipe includes rules that check for vulnerabilities and open ports found by the Scanning service.
For more information, see Scanning with Cloud Guard.
Scanning resources, like most types of resources in Oracle Cloud Infrastructure, have a unique, Oracle-assigned identifier called an Oracle Cloud ID (OCID).
For information about the OCID format and other ways to identify your resources, see Resource Identifiers.
Ways to Access Vulnerability Scanning
You can access Vulnerability Scanning using the Console (a browser-based interface), the command line interface (CLI), or the REST API. Instructions for the Console, CLI, and API are included in topics throughout this guide.
To access the Console, you must use a supported browser. To go to the sign-in page, open the navigation menu at the top of this page and click Infrastructure . You’re prompted to enter your cloud tenant, your user name, and your password.
Authentication and Authorization
Each service in Oracle Cloud Infrastructure integrates with IAM for authentication and authorization, for all interfaces (the Console, SDK or CLI, and REST API).
An administrator in your organization needs to set up groups, compartments , and policies that control which users can access which services, which resources, and the type of access. For example, policies control who can create users, create and manage a VCN (virtual cloud network) , launch instances, and create buckets .
In addition to creating IAM policies, there are other tasks related to the security of Vulnerability Scanning.
- Configure a service gateway so you can scan hosts without public IP addresses
- Perform a security audit of scanning operations
To monitor scanning activity, Vulnerability Scanning integrates with these other services in Oracle Cloud Infrastructure.
- The Audit service automatically records calls to all public Vulnerability Scanning API endpoints as log entries. See Overview of Audit.
- The Monitoring service enables you to monitor your Vulnerability Scanning resources using metrics and alarms. See Scanning Metrics.
- The Events service allows your development teams to automatically respond when a Vulnerability Scanning resource changes its state. See Scanning Events.
Limits and Quotas
Use the Scanning service to check for security vulnerabilities in the compute instances for a single compartment.
Create Scanning IAM Policies.
If you aren’t an administrator, you must be given access to the Scanning service in a policy (IAM) written by an administrator.
Create the Required IAM Policy for Compute Scanning.
An administrator must grant the Scanning service permission to activate the Scanning agent on your target compute instances.
- Open the navigation menu and click Identity & Security. Click Scanning.
- Click Create Scan Recipe.
Click Create Target.
For Target compartment, select the compartment that contains the compute instances you want to scan.
Click View Scan Result.
Results are typically available 15 minutes after creating a target, but it can take up to 24 hours.
See Viewing Host Scans.
- (Optional) Scanning with Cloud Guard
If you run into problems, see Troubleshooting the the Scanning service.