Reference for Vulnerability Scanning

This guide lists the predefined objects in OCI Resource Analytics for the Vulnerability Scanning service. You can find information about views, entity relationships, subject areas, and sample queries.

Views

This section provides information about views within OCI Resource Analytics Vulnerability Scanning and their columns, data types, keys, and the referred view and column names. The following views are available:

Vulnerability Scanning Views
Name Description
VULNERABILITY_SCANNING_CONTAINER_SCAN_RECIPE_DIM_V This view stores information about a container scan recipe (collection of container scanning configuration settings).
VULNERABILITY_SCANNING_CONTAINER_SCAN_TARGET_DIM_V This view stores information about a container scan target (application of a container scan recipe to the registry or list of repos).
VULNERABILITY_SCANNING_HOST_SCAN_RECIPE_DIM_V This view stores information about a host scan recipe (collection of host scanning configuration settings).
VULNERABILITY_SCANNING_HOST_SCAN_TARGET_DIM_V This view stores information about a host scan target (application of a host scan recipe to a compartment or list of hosts).
VULNERABILITY_SCANNING_CONTAINER_SCAN_TARGET_FACT_V Fact table for vulnerability scanning container scan targets.
VULNERABILITY_SCANNING_HOST_SCAN_TARGET_FACT_V Fact table for Vulnerability Scanning host scan targets.

The suffixes in the view names designate the view type:

  • FACT_V: Fact
  • DIM_V: Dimension

The contents of each view and their relationships are listed in the following file: Vulnerability Scanning views.

Each tab in the Excel spreadsheet contains the details of a view.

Relationship Diagram

This section provides diagrams that define the logical relationship of a fact table with different dimension tables.

These diagrams show the relationship of Vulnerability Scanning fact views with different dimension views.

VULNERABILITY_SCANNING_CONTAINER_SCAN_TARGET_FACT_V
Relationship diagram showing the fact table, VULNERABILITY_SCANNING_CONTAINER_SCAN_TARGET_FACT_V.

VULNERABILITY_SCANNING_HOST_SCAN_TARGET_FACT_V
Relationship diagram showing the fact table, VULNERABILITY_SCANNING_HOST_SCAN_TARGET_FACT_V.

Sample Queries

Sample queries for Vulnerability Scanning.

List the number of container scan targets associated with each container scan recipe ID.
SELECT
    CONTAINER_SCAN_RECIPE_ID,
    COUNT(CONTAINER_SCAN_TARGET_ID) AS CONTAINER_SCAN_TARGET_COUNT
FROM OCIRA.VULNERABILITY_SCANNING_CONTAINER_SCAN_TARGET_FACT_V F
GROUP BY CONTAINER_SCAN_RECIPE_ID;
List the number of host scan targets associated with each host scan recipe ID.
SELECT
    HOST_SCAN_RECIPE_ID,
    COUNT(HOST_SCAN_TARGET_ID) AS HOST_SCAN_TARGET_COUNT
FROM OCIRA.VULNERABILITY_SCANNING_HOST_SCAN_TARGET_FACT_V F
GROUP BY HOST_SCAN_RECIPE_ID;

Data Lineage

The Customer Experience Semantic Model Lineage spreadsheet and Metric Calculation Logic spreadsheet for Vulnerability Scanning provides an end-to-end data lineage summary report for physical and logical relationships in your data.

For more information, see Data Lineage.

Subject Areas

This section provides information on the subject areas with data you maintain in Vulnerability Scanning. These subject areas, with their corresponding data, are available for you to use when creating and editing analyses and reports. The information for each subject area includes:

  • Description of the subject area.

  • Business questions that can be answered by data in the subject area, with a link to more detailed information about each business question.

  • Job-specific groups and duty roles that can be used to secure access to the subject area, with a link to more detailed information about each job role and duty role.

  • Primary navigation to the work area that's represented by the subject area.

  • Time reporting considerations in using the subject area, such as whether the subject area reports historical data or only the current data. Historical reporting refers to reporting on historical transactional data in a subject area. With a few exceptions, all dimensional data are current as of the primary transaction dates or system date.

  • The lowest grain of transactional data in a subject area. The lowest transactional data grain decides how data are joined in a report.

  • Special considerations, tips, and things to look out for in using the subject area to create analyses and reports.

The subject area is: