S105121GC10 SME Ops Lab09
S105121GC10 SME Ops Lab09
S105121GC10 SME Ops Lab09
Overview
Oracle Cloud Infrastructure Vulnerability Scanning Service improves your security posture by
checking hosts for potential vulnerabilities on a regular schedule. The service provides
comprehensive visibility into misconfigured or vulnerable resources and creates reports with
metrics and information about these vulnerabilities, including remediation information, for
developers, operations, and security administrators.
Assumptions
• Select the region that’s available in the tenancy allotted to you. In this lab, we are
considering US East (Ashburn) (IAD) as your region.
• You must be familiar with navigating the OCI Console.
Note: If you have already created VCN in the previous practice and have it in your
compartment, you can skip this practice.
Tasks
1. Open the navigation menu and click Networking. Under Networking, click Virtual Cloud
Network.
2. In the left navigation pane, under List Scope, Select the assigned compartment from the
drop-down menu.
4. Select Create VCN with Internet Connectivity and click Start VCN Wizard.
a. Name: IAD-OP-LAB09-1-VCN-01
c. Click Next.
7. Click View Virtual Cloud Network to verify the creation of the VCN and its resources.
You can now see that the VCN was successfully created and is in the Available state, with
the following components:
VCN, Public subnet, Private subnet, Internet gateway, NAT gateway, and Service gateway.
In this practice, you will provision compute instances with vulnerability scanning plugin
enabled.
Note: If you already created/provisioned a compute instance in the previous practice and
have it in your compartment, you can skip this practice. Refer to step 7 in this task to enable
the vulnerability scanning plugin.
Tasks
1. Open the navigation menu and click Compute. Under Compute, click Instances.
2. In the left navigation pane, under List Scope, select the assigned compartment from the
drop-down menu.
3. Click Create Instance. On the Create Instance dialog box, provide the following details:
a. Name: IAD-OP-LAB09-1-VM-01
2) Select VM.Standard.A1.Flex.
2) Click Save private key. This will save the private key to your local workstation.
3) Click Save public key. This will save the public key to your local workstation.
4) Select the Upload public key (.pub) option button. Upload the recently
downloaded public key. Either drag the key to the Drop .pub files here window,
or click Browse, select the key and click Upload.
5. On the Oracle Cloud Agent tab, select the Vulnerability Scanning check box.
6. Click Create.
Note: After a couple of minutes, you can see that the instance is successfully created, and
the state is Running.
It can take up to 5-10 minutes for the change to take effect. After a few moments, the
status Running for Vulnerability Scanning enabled service will be displayed.
Tasks
1. Open the navigation menu and click Identity & Security. Under Scanning, click Scan
Recipes.
2. In the left navigation pane, under List Scope, select your assigned compartment from
the drop-down menu.
b. Name: IAD-OP-LAB09-1-CSC-01
1) CIS benchmark profile: Select Strict (More than 20% of the benchmarks
failing is a critical risk).
You will see that the scan recipe is successfully created, and the status is Active.
Tasks
1. Open the navigation menu and click Identity & Security. Under Scanning, click Targets.
2. In the left navigation pane, under List Scope, select your assigned compartment from
the drop-down menu.
b. Name: IAD-OP-LAB09-1-CTRG-01
Note: Click Change compartment and select assigned compartment to locate scan
recipe, if not available by default.
g. Under Targets:
You will see that the target is successfully created, and the status is Active.
Scanning service may take up to 10-15 minutes to check your compute instance for
security vulnerabilities and open ports, based on the parameters and schedule configured
in the scan recipe.
Tasks
1. Open the navigation menu and click Identity & Security. Under Scanning, click Scanning
Reports.
2. In the left navigation pane, under List Scope, select your assigned compartment from
the drop-down menu.
5. Locate the Scan start date and Scan end date filter drop-down menus.
By default, only the most recent scan reports are displayed. To view older reports, choose
specific start and end dates.
6. Locate the Reset button. Click Reset at any time to set the risk level and date ranges back
to the default values.
7. (Optional) Click the table columns to sort the container image scans by:
• Risk level
• Issues found
• Scan completed
8. To view a compute scan report, click the name of the compute instance.
Example: IAD-OP-LAB09-1-VM-01
A host scan includes metrics, open ports, vulnerabilities, and benchmarks for a selected
Compute instance.
9. In the left navigation pane, under Resources, click Metrics if not already selected.
a. In Host scan information tab, locate the number of CIS benchmarks passed.
10. In the left navigation pane, under Resources, click Open ports.
a. The first panel shows the number of open ports that are detected on each Virtual
Network Interface Card (VNIC) in the selected compute instance.
b. The second panel shows the specific port numbers that were detected in this
compute instance.
12. The following details are shown for each issue that were detected in the selected compute
instance:
• CVE ID
• Risk level
• CVE description
• Last detected
• First detected
• Cause and remediation
Click any View detail button in the Cause and remediation column to get more
information on how to address this vulnerability.
13. In the left navigation pane, under Resources, click CIS benchmarks.
14. The following details are shown for each CIS benchmark the Scanning service tested on
the selected compute instance:
• Benchmark ID
• Result - Pass or Fail
• Summary
Tasks
1. Open the navigation menu and click Identity & Security. Under Scanning, click
Vulnerability Reports.
2. In the left navigation pane, under List Scope, Select your assigned compartment from
the drop-down menu.
3. In the left navigation pane, under Filters, select the Risk level, All.
5. To view a description of a specific vulnerability, click Show in the CVE description column.
This will show a vulnerability report for the selected CVE, which includes details about the
affected resources and CVE information.
7. On the Vulnerabilities report page, under Vulnerability information tab, click the CVE ID
link.
It will redirect to the source of the CVEs database and provide more information about it.
8. In the left navigation pane, under Resources, select Hosts to view a list of compute
instance that are affected by the selected vulnerability.
Note: Before using Cloud Guard, at least one Scanning target must exist before the Scanning
service creates any reports. These reports are used by the Cloud Guard detector.
Tasks
1. Open the navigation menu and click Identity & Security. Under Identity & Security, click
Cloud Guard.
2. In the left navigation pane, under Scope, Select the <Tenancy Name>root compartment
from the drop-down menu.
3. In the left navigation pane, under Cloud Guard, click Detector Recipes.
5. Under Detector Rules, in the Filter by detector rule field, enter scan.
Note: If you already have a specific target set for your compartment, delete it.
Note: Before using Cloud Guard, at least one Scanning target must exist before the Scanning
service creates any reports. These reports are used by the Cloud Guard detector.
Tasks
1. Open the navigation menu and click Identity & Security. Under Identity & Security, click
Cloud Guard.
2. In the left navigation pane, under List Scope, Select the assigned compartment from the
drop-down menu.
4. View the list of problems Cloud Guard has identified with the resources in your assigned
compartment based on your previous practices. The Problems page displays information
about each problem, including:
• Problem Name
• Risk Level
• Detector Type
• Resource affected
• Target
• Region
• Labels
• First Detected
• Last Detected
Example:
• The Vulnerability Scanning service did not create any reports yet. The schedule
(daily/weekly) is configured in the Scanning target.
• You recently enabled Cloud Guard or the Vulnerability Scanning detector rules, and
Cloud Guard has not run them yet.
7. You can take the necessary steps to eliminate the detected vulnerability and mark the
problem as resolved.