oracle.oci.oci_data_safe_security_assessment_comparison_facts – Fetches details about a SecurityAssessmentComparison resource in Oracle Cloud Infrastructure

Note

This plugin is part of the oracle.oci collection (version 4.10.0).

You might already have this collection installed if you are using the ansible package. It is not included in ansible-core. To check whether it is installed, run ansible-galaxy collection list.

To install it, use: ansible-galaxy collection install oracle.oci.

To use it in a playbook, specify: oracle.oci.oci_data_safe_security_assessment_comparison_facts.

New in version 2.9.0: of oracle.oci

Synopsis

  • Fetches details about a SecurityAssessmentComparison resource in Oracle Cloud Infrastructure

  • Gets the details of the comparison report on the security assessments submitted for comparison.

Requirements

The below requirements are needed on the host that executes this module.

Parameters

Parameter Choices/Defaults Comments
api_user
string
The OCID of the user, on whose behalf, OCI APIs are invoked. If not set, then the value of the OCI_USER_ID environment variable, if any, is used. This option is required if the user is not specified through a configuration file (See config_file_location). To get the user's OCID, please refer https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/apisigningkey.htm.
api_user_fingerprint
string
Fingerprint for the key pair being used. If not set, then the value of the OCI_USER_FINGERPRINT environment variable, if any, is used. This option is required if the key fingerprint is not specified through a configuration file (See config_file_location). To get the key pair's fingerprint value please refer https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/apisigningkey.htm.
api_user_key_file
string
Full path and filename of the private key (in PEM format). If not set, then the value of the OCI_USER_KEY_FILE variable, if any, is used. This option is required if the private key is not specified through a configuration file (See config_file_location). If the key is encrypted with a pass-phrase, the api_user_key_pass_phrase option must also be provided.
api_user_key_pass_phrase
string
Passphrase used by the key referenced in api_user_key_file, if it is encrypted. If not set, then the value of the OCI_USER_KEY_PASS_PHRASE variable, if any, is used. This option is required if the key passphrase is not specified through a configuration file (See config_file_location).
auth_purpose
string
    Choices:
  • service_principal
The auth purpose which can be used in conjunction with 'auth_type=instance_principal'. The default auth_purpose for instance_principal is None.
auth_type
string
    Choices:
  • api_key ←
  • instance_principal
  • instance_obo_user
  • resource_principal
The type of authentication to use for making API requests. By default auth_type="api_key" based authentication is performed and the API key (see api_user_key_file) in your config file will be used. If this 'auth_type' module option is not specified, the value of the OCI_ANSIBLE_AUTH_TYPE, if any, is used. Use auth_type="instance_principal" to use instance principal based authentication when running ansible playbooks within an OCI compute instance.
cert_bundle
string
The full path to a CA certificate bundle to be used for SSL verification. This will override the default CA certificate bundle. If not set, then the value of the OCI_ANSIBLE_CERT_BUNDLE variable, if any, is used.
comparison_security_assessment_id
string / required
The OCID of the baseline security assessment.

aliases: id
config_file_location
string
Path to configuration file. If not set then the value of the OCI_CONFIG_FILE environment variable, if any, is used. Otherwise, defaults to ~/.oci/config.
config_profile_name
string
The profile to load from the config file referenced by config_file_location. If not set, then the value of the OCI_CONFIG_PROFILE environment variable, if any, is used. Otherwise, defaults to the "DEFAULT" profile in config_file_location.
region
string
The Oracle Cloud Infrastructure region to use for all OCI API requests. If not set, then the value of the OCI_REGION variable, if any, is used. This option is required if the region is not specified through a configuration file (See config_file_location). Please refer to https://docs.us-phoenix-1.oraclecloud.com/Content/General/Concepts/regions.htm for more information on OCI regions.
security_assessment_id
string / required
The OCID of the security assessment.
tenancy
string
OCID of your tenancy. If not set, then the value of the OCI_TENANCY variable, if any, is used. This option is required if the tenancy OCID is not specified through a configuration file (See config_file_location). To get the tenancy OCID, please refer https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/apisigningkey.htm

Examples

- name: Get a specific security_assessment_comparison
  oci_data_safe_security_assessment_comparison_facts:
    # required
    security_assessment_id: "ocid1.securityassessment.oc1..xxxxxxEXAMPLExxxxxx"
    comparison_security_assessment_id: "ocid1.comparisonsecurityassessment.oc1..xxxxxxEXAMPLExxxxxx"

Return Values

Common return values are documented here, the following are the fields unique to this module:

Key Returned Description
security_assessment_comparison
complex
on success
SecurityAssessmentComparison resource

Sample:
{'baseline_id': 'ocid1.baseline.oc1..xxxxxxEXAMPLExxxxxx', 'id': 'ocid1.resource.oc1..xxxxxxEXAMPLExxxxxx', 'lifecycle_state': 'CREATING', 'targets': [{'auditing': [{'added_items': [], 'baseline': {'details': {}, 'key': 'key_example', 'references': {'cis': 'cis_example', 'gdpr': 'gdpr_example', 'stig': 'stig_example'}, 'remarks': 'remarks_example', 'severity': 'HIGH', 'summary': 'summary_example', 'title': 'title_example'}, 'current': {'details': {}, 'key': 'key_example', 'references': {'cis': 'cis_example', 'gdpr': 'gdpr_example', 'stig': 'stig_example'}, 'remarks': 'remarks_example', 'severity': 'HIGH', 'summary': 'summary_example', 'title': 'title_example'}, 'modified_items': [], 'removed_items': [], 'severity': 'HIGH'}], 'authorization_control': [{'added_items': [], 'baseline': {'details': {}, 'key': 'key_example', 'references': {'cis': 'cis_example', 'gdpr': 'gdpr_example', 'stig': 'stig_example'}, 'remarks': 'remarks_example', 'severity': 'HIGH', 'summary': 'summary_example', 'title': 'title_example'}, 'current': {'details': {}, 'key': 'key_example', 'references': {'cis': 'cis_example', 'gdpr': 'gdpr_example', 'stig': 'stig_example'}, 'remarks': 'remarks_example', 'severity': 'HIGH', 'summary': 'summary_example', 'title': 'title_example'}, 'modified_items': [], 'removed_items': [], 'severity': 'HIGH'}], 'baseline_target_id': 'ocid1.baselinetarget.oc1..xxxxxxEXAMPLExxxxxx', 'current_target_id': 'ocid1.currenttarget.oc1..xxxxxxEXAMPLExxxxxx', 'data_encryption': [{'added_items': [], 'baseline': {'details': {}, 'key': 'key_example', 'references': {'cis': 'cis_example', 'gdpr': 'gdpr_example', 'stig': 'stig_example'}, 'remarks': 'remarks_example', 'severity': 'HIGH', 'summary': 'summary_example', 'title': 'title_example'}, 'current': {'details': {}, 'key': 'key_example', 'references': {'cis': 'cis_example', 'gdpr': 'gdpr_example', 'stig': 'stig_example'}, 'remarks': 'remarks_example', 'severity': 'HIGH', 'summary': 'summary_example', 'title': 'title_example'}, 'modified_items': [], 'removed_items': [], 'severity': 'HIGH'}], 'db_configuration': [{'added_items': [], 'baseline': {'details': {}, 'key': 'key_example', 'references': {'cis': 'cis_example', 'gdpr': 'gdpr_example', 'stig': 'stig_example'}, 'remarks': 'remarks_example', 'severity': 'HIGH', 'summary': 'summary_example', 'title': 'title_example'}, 'current': {'details': {}, 'key': 'key_example', 'references': {'cis': 'cis_example', 'gdpr': 'gdpr_example', 'stig': 'stig_example'}, 'remarks': 'remarks_example', 'severity': 'HIGH', 'summary': 'summary_example', 'title': 'title_example'}, 'modified_items': [], 'removed_items': [], 'severity': 'HIGH'}], 'fine_grained_access_control': [{'added_items': [], 'baseline': {'details': {}, 'key': 'key_example', 'references': {'cis': 'cis_example', 'gdpr': 'gdpr_example', 'stig': 'stig_example'}, 'remarks': 'remarks_example', 'severity': 'HIGH', 'summary': 'summary_example', 'title': 'title_example'}, 'current': {'details': {}, 'key': 'key_example', 'references': {'cis': 'cis_example', 'gdpr': 'gdpr_example', 'stig': 'stig_example'}, 'remarks': 'remarks_example', 'severity': 'HIGH', 'summary': 'summary_example', 'title': 'title_example'}, 'modified_items': [], 'removed_items': [], 'severity': 'HIGH'}], 'privileges_and_roles': [{'added_items': [], 'baseline': {'details': {}, 'key': 'key_example', 'references': {'cis': 'cis_example', 'gdpr': 'gdpr_example', 'stig': 'stig_example'}, 'remarks': 'remarks_example', 'severity': 'HIGH', 'summary': 'summary_example', 'title': 'title_example'}, 'current': {'details': {}, 'key': 'key_example', 'references': {'cis': 'cis_example', 'gdpr': 'gdpr_example', 'stig': 'stig_example'}, 'remarks': 'remarks_example', 'severity': 'HIGH', 'summary': 'summary_example', 'title': 'title_example'}, 'modified_items': [], 'removed_items': [], 'severity': 'HIGH'}], 'user_accounts': [{'added_items': [], 'baseline': {'details': {}, 'key': 'key_example', 'references': {'cis': 'cis_example', 'gdpr': 'gdpr_example', 'stig': 'stig_example'}, 'remarks': 'remarks_example', 'severity': 'HIGH', 'summary': 'summary_example', 'title': 'title_example'}, 'current': {'details': {}, 'key': 'key_example', 'references': {'cis': 'cis_example', 'gdpr': 'gdpr_example', 'stig': 'stig_example'}, 'remarks': 'remarks_example', 'severity': 'HIGH', 'summary': 'summary_example', 'title': 'title_example'}, 'modified_items': [], 'removed_items': [], 'severity': 'HIGH'}]}], 'time_created': '2013-10-20T19:20:30+01:00'}
 
baseline_id
string
on success
The OCID of the security assessment that is set as a baseline.

Sample:
ocid1.baseline.oc1..xxxxxxEXAMPLExxxxxx
 
id
string
on success
The OCID of the security assessment that is being compared with a baseline security assessment.

Sample:
ocid1.resource.oc1..xxxxxxEXAMPLExxxxxx
 
lifecycle_state
string
on success
The current state of the security assessment comparison.

Sample:
CREATING
 
targets
complex
on success
A target-based comparison between two security assessments.

   
auditing
complex
on success
A comparison between findings belonging to Auditing category.

     
added_items
list / elements=string
on success
This array identifies the items that are present in the current assessment, but are missing from the baseline.

     
baseline
complex
on success

       
details
dictionary
on success
The details of the finding. Provides detailed information to explain the finding summary, typically results from the assessed database, followed by any recommendations for changes.

       
key
string
on success
A unique identifier for the finding. This is common for the finding across targets.

Sample:
key_example
       
references
complex
on success
Provides information on whether the finding is related to a CIS Oracle Database Benchmark recommendation, STIG rule, or related to a GDPR Article/Recital.

         
cis
string
on success
Relevant section from CIS.

Sample:
cis_example
         
gdpr
string
on success
Relevant section from GDPR.

Sample:
gdpr_example
         
stig
string
on success
Relevant section from STIG.

Sample:
stig_example
       
remarks
string
on success
The explanation of the issue in this finding. It explains the reason for the rule and, if a risk is reported, it may also explain the recommended actions for remediation.

Sample:
remarks_example
       
severity
string
on success
The severity of the finding.

Sample:
HIGH
       
summary
string
on success
The brief summary of the finding. When the finding is informational, the summary typically reports only the number of data elements that were examined.

Sample:
summary_example
       
title
string
on success
The short title for the finding.

Sample:
title_example
     
current
complex
on success

       
details
dictionary
on success
The details of the finding. Provides detailed information to explain the finding summary, typically results from the assessed database, followed by any recommendations for changes.

       
key
string
on success
A unique identifier for the finding. This is common for the finding across targets.

Sample:
key_example
       
references
complex
on success
Provides information on whether the finding is related to a CIS Oracle Database Benchmark recommendation, STIG rule, or related to a GDPR Article/Recital.

         
cis
string
on success
Relevant section from CIS.

Sample:
cis_example
         
gdpr
string
on success
Relevant section from GDPR.

Sample:
gdpr_example
         
stig
string
on success
Relevant section from STIG.

Sample:
stig_example
       
remarks
string
on success
The explanation of the issue in this finding. It explains the reason for the rule and, if a risk is reported, it may also explain the recommended actions for remediation.

Sample:
remarks_example
       
severity
string
on success
The severity of the finding.

Sample:
HIGH
       
summary
string
on success
The brief summary of the finding. When the finding is informational, the summary typically reports only the number of data elements that were examined.

Sample:
summary_example
       
title
string
on success
The short title for the finding.

Sample:
title_example
     
modified_items
list / elements=string
on success
This array contains the items that are present in both the current assessment and the baseline, but are different in the two assessments.

     
removed_items
list / elements=string
on success
This array identifies the items that are present in the baseline, but are missing from the current assessment.

     
severity
string
on success
The severity of this diff.

Sample:
HIGH
   
authorization_control
complex
on success
A comparison between findings belonging to Authorization Control category.

     
added_items
list / elements=string
on success
This array identifies the items that are present in the current assessment, but are missing from the baseline.

     
baseline
complex
on success

       
details
dictionary
on success
The details of the finding. Provides detailed information to explain the finding summary, typically results from the assessed database, followed by any recommendations for changes.

       
key
string
on success
A unique identifier for the finding. This is common for the finding across targets.

Sample:
key_example
       
references
complex
on success
Provides information on whether the finding is related to a CIS Oracle Database Benchmark recommendation, STIG rule, or related to a GDPR Article/Recital.

         
cis
string
on success
Relevant section from CIS.

Sample:
cis_example
         
gdpr
string
on success
Relevant section from GDPR.

Sample:
gdpr_example
         
stig
string
on success
Relevant section from STIG.

Sample:
stig_example
       
remarks
string
on success
The explanation of the issue in this finding. It explains the reason for the rule and, if a risk is reported, it may also explain the recommended actions for remediation.

Sample:
remarks_example
       
severity
string
on success
The severity of the finding.

Sample:
HIGH
       
summary
string
on success
The brief summary of the finding. When the finding is informational, the summary typically reports only the number of data elements that were examined.

Sample:
summary_example
       
title
string
on success
The short title for the finding.

Sample:
title_example
     
current
complex
on success

       
details
dictionary
on success
The details of the finding. Provides detailed information to explain the finding summary, typically results from the assessed database, followed by any recommendations for changes.

       
key
string
on success
A unique identifier for the finding. This is common for the finding across targets.

Sample:
key_example
       
references
complex
on success
Provides information on whether the finding is related to a CIS Oracle Database Benchmark recommendation, STIG rule, or related to a GDPR Article/Recital.

         
cis
string
on success
Relevant section from CIS.

Sample:
cis_example
         
gdpr
string
on success
Relevant section from GDPR.

Sample:
gdpr_example
         
stig
string
on success
Relevant section from STIG.

Sample:
stig_example
       
remarks
string
on success
The explanation of the issue in this finding. It explains the reason for the rule and, if a risk is reported, it may also explain the recommended actions for remediation.

Sample:
remarks_example
       
severity
string
on success
The severity of the finding.

Sample:
HIGH
       
summary
string
on success
The brief summary of the finding. When the finding is informational, the summary typically reports only the number of data elements that were examined.

Sample:
summary_example
       
title
string
on success
The short title for the finding.

Sample:
title_example
     
modified_items
list / elements=string
on success
This array contains the items that are present in both the current assessment and the baseline, but are different in the two assessments.

     
removed_items
list / elements=string
on success
This array identifies the items that are present in the baseline, but are missing from the current assessment.

     
severity
string
on success
The severity of this diff.

Sample:
HIGH
   
baseline_target_id
string
on success
The OCID of the target that is used as a baseline in this comparison.

Sample:
ocid1.baselinetarget.oc1..xxxxxxEXAMPLExxxxxx
   
current_target_id
string
on success
The OCID of the target to be compared against the baseline target.

Sample:
ocid1.currenttarget.oc1..xxxxxxEXAMPLExxxxxx
   
data_encryption
complex
on success
Comparison between findings belonging to Data Encryption category.

     
added_items
list / elements=string
on success
This array identifies the items that are present in the current assessment, but are missing from the baseline.

     
baseline
complex
on success

       
details
dictionary
on success
The details of the finding. Provides detailed information to explain the finding summary, typically results from the assessed database, followed by any recommendations for changes.

       
key
string
on success
A unique identifier for the finding. This is common for the finding across targets.

Sample:
key_example
       
references
complex
on success
Provides information on whether the finding is related to a CIS Oracle Database Benchmark recommendation, STIG rule, or related to a GDPR Article/Recital.

         
cis
string
on success
Relevant section from CIS.

Sample:
cis_example
         
gdpr
string
on success
Relevant section from GDPR.

Sample:
gdpr_example
         
stig
string
on success
Relevant section from STIG.

Sample:
stig_example
       
remarks
string
on success
The explanation of the issue in this finding. It explains the reason for the rule and, if a risk is reported, it may also explain the recommended actions for remediation.

Sample:
remarks_example
       
severity
string
on success
The severity of the finding.

Sample:
HIGH
       
summary
string
on success
The brief summary of the finding. When the finding is informational, the summary typically reports only the number of data elements that were examined.

Sample:
summary_example
       
title
string
on success
The short title for the finding.

Sample:
title_example
     
current
complex
on success

       
details
dictionary
on success
The details of the finding. Provides detailed information to explain the finding summary, typically results from the assessed database, followed by any recommendations for changes.

       
key
string
on success
A unique identifier for the finding. This is common for the finding across targets.

Sample:
key_example
       
references
complex
on success
Provides information on whether the finding is related to a CIS Oracle Database Benchmark recommendation, STIG rule, or related to a GDPR Article/Recital.

         
cis
string
on success
Relevant section from CIS.

Sample:
cis_example
         
gdpr
string
on success
Relevant section from GDPR.

Sample:
gdpr_example
         
stig
string
on success
Relevant section from STIG.

Sample:
stig_example
       
remarks
string
on success
The explanation of the issue in this finding. It explains the reason for the rule and, if a risk is reported, it may also explain the recommended actions for remediation.

Sample:
remarks_example
       
severity
string
on success
The severity of the finding.

Sample:
HIGH
       
summary
string
on success
The brief summary of the finding. When the finding is informational, the summary typically reports only the number of data elements that were examined.

Sample:
summary_example
       
title
string
on success
The short title for the finding.

Sample:
title_example
     
modified_items
list / elements=string
on success
This array contains the items that are present in both the current assessment and the baseline, but are different in the two assessments.

     
removed_items
list / elements=string
on success
This array identifies the items that are present in the baseline, but are missing from the current assessment.

     
severity
string
on success
The severity of this diff.

Sample:
HIGH
   
db_configuration
complex
on success
Comparison between findings belonging to Database Configuration category.

     
added_items
list / elements=string
on success
This array identifies the items that are present in the current assessment, but are missing from the baseline.

     
baseline
complex
on success

       
details
dictionary
on success
The details of the finding. Provides detailed information to explain the finding summary, typically results from the assessed database, followed by any recommendations for changes.

       
key
string
on success
A unique identifier for the finding. This is common for the finding across targets.

Sample:
key_example
       
references
complex
on success
Provides information on whether the finding is related to a CIS Oracle Database Benchmark recommendation, STIG rule, or related to a GDPR Article/Recital.

         
cis
string
on success
Relevant section from CIS.

Sample:
cis_example
         
gdpr
string
on success
Relevant section from GDPR.

Sample:
gdpr_example
         
stig
string
on success
Relevant section from STIG.

Sample:
stig_example
       
remarks
string
on success
The explanation of the issue in this finding. It explains the reason for the rule and, if a risk is reported, it may also explain the recommended actions for remediation.

Sample:
remarks_example
       
severity
string
on success
The severity of the finding.

Sample:
HIGH
       
summary
string
on success
The brief summary of the finding. When the finding is informational, the summary typically reports only the number of data elements that were examined.

Sample:
summary_example
       
title
string
on success
The short title for the finding.

Sample:
title_example
     
current
complex
on success

       
details
dictionary
on success
The details of the finding. Provides detailed information to explain the finding summary, typically results from the assessed database, followed by any recommendations for changes.

       
key
string
on success
A unique identifier for the finding. This is common for the finding across targets.

Sample:
key_example
       
references
complex
on success
Provides information on whether the finding is related to a CIS Oracle Database Benchmark recommendation, STIG rule, or related to a GDPR Article/Recital.

         
cis
string
on success
Relevant section from CIS.

Sample:
cis_example
         
gdpr
string
on success
Relevant section from GDPR.

Sample:
gdpr_example
         
stig
string
on success
Relevant section from STIG.

Sample:
stig_example
       
remarks
string
on success
The explanation of the issue in this finding. It explains the reason for the rule and, if a risk is reported, it may also explain the recommended actions for remediation.

Sample:
remarks_example
       
severity
string
on success
The severity of the finding.

Sample:
HIGH
       
summary
string
on success
The brief summary of the finding. When the finding is informational, the summary typically reports only the number of data elements that were examined.

Sample:
summary_example
       
title
string
on success
The short title for the finding.

Sample:
title_example
     
modified_items
list / elements=string
on success
This array contains the items that are present in both the current assessment and the baseline, but are different in the two assessments.

     
removed_items
list / elements=string
on success
This array identifies the items that are present in the baseline, but are missing from the current assessment.

     
severity
string
on success
The severity of this diff.

Sample:
HIGH
   
fine_grained_access_control
complex
on success
Comparison between findings belonging to Fine-Grained Access Control category.

     
added_items
list / elements=string
on success
This array identifies the items that are present in the current assessment, but are missing from the baseline.

     
baseline
complex
on success

       
details
dictionary
on success
The details of the finding. Provides detailed information to explain the finding summary, typically results from the assessed database, followed by any recommendations for changes.

       
key
string
on success
A unique identifier for the finding. This is common for the finding across targets.

Sample:
key_example
       
references
complex
on success
Provides information on whether the finding is related to a CIS Oracle Database Benchmark recommendation, STIG rule, or related to a GDPR Article/Recital.

         
cis
string
on success
Relevant section from CIS.

Sample:
cis_example
         
gdpr
string
on success
Relevant section from GDPR.

Sample:
gdpr_example
         
stig
string
on success
Relevant section from STIG.

Sample:
stig_example
       
remarks
string
on success
The explanation of the issue in this finding. It explains the reason for the rule and, if a risk is reported, it may also explain the recommended actions for remediation.

Sample:
remarks_example
       
severity
string
on success
The severity of the finding.

Sample:
HIGH
       
summary
string
on success
The brief summary of the finding. When the finding is informational, the summary typically reports only the number of data elements that were examined.

Sample:
summary_example
       
title
string
on success
The short title for the finding.

Sample:
title_example
     
current
complex
on success

       
details
dictionary
on success
The details of the finding. Provides detailed information to explain the finding summary, typically results from the assessed database, followed by any recommendations for changes.

       
key
string
on success
A unique identifier for the finding. This is common for the finding across targets.

Sample:
key_example
       
references
complex
on success
Provides information on whether the finding is related to a CIS Oracle Database Benchmark recommendation, STIG rule, or related to a GDPR Article/Recital.

         
cis
string
on success
Relevant section from CIS.

Sample:
cis_example
         
gdpr
string
on success
Relevant section from GDPR.

Sample:
gdpr_example
         
stig
string
on success
Relevant section from STIG.

Sample:
stig_example
       
remarks
string
on success
The explanation of the issue in this finding. It explains the reason for the rule and, if a risk is reported, it may also explain the recommended actions for remediation.

Sample:
remarks_example
       
severity
string
on success
The severity of the finding.

Sample:
HIGH
       
summary
string
on success
The brief summary of the finding. When the finding is informational, the summary typically reports only the number of data elements that were examined.

Sample:
summary_example
       
title
string
on success
The short title for the finding.

Sample:
title_example
     
modified_items
list / elements=string
on success
This array contains the items that are present in both the current assessment and the baseline, but are different in the two assessments.

     
removed_items
list / elements=string
on success
This array identifies the items that are present in the baseline, but are missing from the current assessment.

     
severity
string
on success
The severity of this diff.

Sample:
HIGH
   
privileges_and_roles
complex
on success
Comparison between findings belonging to Privileges and Roles category.

     
added_items
list / elements=string
on success
This array identifies the items that are present in the current assessment, but are missing from the baseline.

     
baseline
complex
on success

       
details
dictionary
on success
The details of the finding. Provides detailed information to explain the finding summary, typically results from the assessed database, followed by any recommendations for changes.

       
key
string
on success
A unique identifier for the finding. This is common for the finding across targets.

Sample:
key_example
       
references
complex
on success
Provides information on whether the finding is related to a CIS Oracle Database Benchmark recommendation, STIG rule, or related to a GDPR Article/Recital.

         
cis
string
on success
Relevant section from CIS.

Sample:
cis_example
         
gdpr
string
on success
Relevant section from GDPR.

Sample:
gdpr_example
         
stig
string
on success
Relevant section from STIG.

Sample:
stig_example
       
remarks
string
on success
The explanation of the issue in this finding. It explains the reason for the rule and, if a risk is reported, it may also explain the recommended actions for remediation.

Sample:
remarks_example
       
severity
string
on success
The severity of the finding.

Sample:
HIGH
       
summary
string
on success
The brief summary of the finding. When the finding is informational, the summary typically reports only the number of data elements that were examined.

Sample:
summary_example
       
title
string
on success
The short title for the finding.

Sample:
title_example
     
current
complex
on success

       
details
dictionary
on success
The details of the finding. Provides detailed information to explain the finding summary, typically results from the assessed database, followed by any recommendations for changes.

       
key
string
on success
A unique identifier for the finding. This is common for the finding across targets.

Sample:
key_example
       
references
complex
on success
Provides information on whether the finding is related to a CIS Oracle Database Benchmark recommendation, STIG rule, or related to a GDPR Article/Recital.

         
cis
string
on success
Relevant section from CIS.

Sample:
cis_example
         
gdpr
string
on success
Relevant section from GDPR.

Sample:
gdpr_example
         
stig
string
on success
Relevant section from STIG.

Sample:
stig_example
       
remarks
string
on success
The explanation of the issue in this finding. It explains the reason for the rule and, if a risk is reported, it may also explain the recommended actions for remediation.

Sample:
remarks_example
       
severity
string
on success
The severity of the finding.

Sample:
HIGH
       
summary
string
on success
The brief summary of the finding. When the finding is informational, the summary typically reports only the number of data elements that were examined.

Sample:
summary_example
       
title
string
on success
The short title for the finding.

Sample:
title_example
     
modified_items
list / elements=string
on success
This array contains the items that are present in both the current assessment and the baseline, but are different in the two assessments.

     
removed_items
list / elements=string
on success
This array identifies the items that are present in the baseline, but are missing from the current assessment.

     
severity
string
on success
The severity of this diff.

Sample:
HIGH
   
user_accounts
complex
on success
Comparison between findings belonging to User Accounts category.

     
added_items
list / elements=string
on success
This array identifies the items that are present in the current assessment, but are missing from the baseline.

     
baseline
complex
on success

       
details
dictionary
on success
The details of the finding. Provides detailed information to explain the finding summary, typically results from the assessed database, followed by any recommendations for changes.

       
key
string
on success
A unique identifier for the finding. This is common for the finding across targets.

Sample:
key_example
       
references
complex
on success
Provides information on whether the finding is related to a CIS Oracle Database Benchmark recommendation, STIG rule, or related to a GDPR Article/Recital.

         
cis
string
on success
Relevant section from CIS.

Sample:
cis_example
         
gdpr
string
on success
Relevant section from GDPR.

Sample:
gdpr_example
         
stig
string
on success
Relevant section from STIG.

Sample:
stig_example
       
remarks
string
on success
The explanation of the issue in this finding. It explains the reason for the rule and, if a risk is reported, it may also explain the recommended actions for remediation.

Sample:
remarks_example
       
severity
string
on success
The severity of the finding.

Sample:
HIGH
       
summary
string
on success
The brief summary of the finding. When the finding is informational, the summary typically reports only the number of data elements that were examined.

Sample:
summary_example
       
title
string
on success
The short title for the finding.

Sample:
title_example
     
current
complex
on success

       
details
dictionary
on success
The details of the finding. Provides detailed information to explain the finding summary, typically results from the assessed database, followed by any recommendations for changes.

       
key
string
on success
A unique identifier for the finding. This is common for the finding across targets.

Sample:
key_example
       
references
complex
on success
Provides information on whether the finding is related to a CIS Oracle Database Benchmark recommendation, STIG rule, or related to a GDPR Article/Recital.

         
cis
string
on success
Relevant section from CIS.

Sample:
cis_example
         
gdpr
string
on success
Relevant section from GDPR.

Sample:
gdpr_example
         
stig
string
on success
Relevant section from STIG.

Sample:
stig_example
       
remarks
string
on success
The explanation of the issue in this finding. It explains the reason for the rule and, if a risk is reported, it may also explain the recommended actions for remediation.

Sample:
remarks_example
       
severity
string
on success
The severity of the finding.

Sample:
HIGH
       
summary
string
on success
The brief summary of the finding. When the finding is informational, the summary typically reports only the number of data elements that were examined.

Sample:
summary_example
       
title
string
on success
The short title for the finding.

Sample:
title_example
     
modified_items
list / elements=string
on success
This array contains the items that are present in both the current assessment and the baseline, but are different in the two assessments.

     
removed_items
list / elements=string
on success
This array identifies the items that are present in the baseline, but are missing from the current assessment.

     
severity
string
on success
The severity of this diff.

Sample:
HIGH
 
time_created
string
on success
The date and time when the security assessment comparison was created. Conforms to the format defined by RFC3339.

Sample:
2013-10-20T19:20:30+01:00


Authors

  • Oracle (@oracle)