Namespace SecurityAssessment

The OCID of the compartment that contains the security assessment.

Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags

Example: {@code {\"Operations\": {\"CostCenter\": \"42\"}}}

The description of the security assessment.

The display name of the security assessment.

Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags

Example: {@code {\"Department\": \"Finance\"}}

The OCID of the security assessment.

List containing maps as values. Example: {@code {"Operations": [ {"CostCenter": "42"} ] }}

List containing maps as values. Example: {@code {"Operations": [ {"CostCenter": "42"} ] }}

Indicates whether or not the security assessment is set as a baseline. This is applicable only for saved security assessments.

Indicates if the assessment has deviated from the baseline.

The OCID of the baseline against which the latest security assessment was compared.

Details about the current state of the security assessment.

The current state of the security assessment.

The summary of findings for the security assessment

Schedule to save the assessment periodically in the specified format: ;

Allowed version strings - \"v1\" v1's version specific schedule - Each of the above fields potentially introduce constraints. A workrequest is created only when clock time satisfies all the constraints. Constraints introduced: 1. seconds = (So, the allowed range for is [0, 59]) 2. minutes = (So, the allowed range for is [0, 59]) 3. hours = (So, the allowed range for is [0, 23]) can be either '*' (without quotes or a number between 1(Monday) and 7(Sunday)) 4. No constraint introduced when it is '*'. When not, day of week must equal the given value can be either '*' (without quotes or a number between 1 and 28) 5. No constraint introduced when it is '*'. When not, day of month must equal the given value

The OCID of the security assessment that is responsible for creating this scheduled save assessment.

System tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example: {@code {"orcl-cloud": {"free-tier-retained": "true"}}}

Array of database target OCIDs.

The version of the target database.

The date and time the security assessment was created, in the format defined by RFC3339.

The date and time the security assessment was last executed, in the format defined by RFC3339.

The date and time the security assessment was last updated, in the format defined by RFC3339.

Indicates whether the security assessment was created by system or by a user.

The type of this security assessment. The possible types are:

LATEST: The most up-to-date assessment that is running automatically for a target. It is system generated. SAVED: A saved security assessment. LATEST assessments are always saved in order to maintain the history of runs. A SAVED assessment is also generated by a 'refresh' action (triggered by the user). SAVE_SCHEDULE: The schedule for periodic saves of LATEST assessments. COMPARTMENT: An automatically managed assessment type that stores all details of targets in one compartment. This type keeps an up-to-date assessment of all database risks in one compartment. It is automatically updated when the latest assessment or refresh action is executed. It is also automatically updated when a target is deleted or move to a different compartment.