The category of the security policy
The OCID of the security policy's compartment
Defined tags for this resource. Each key is predefined and scoped to a namespace. Example: {@code {"foo-namespace": {"bar-key": "value"}}}
The security policy's description
The security policy's display name
Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. Example: {@code {"bar-key": "value"}}
Avoid entering confidential information.
A shorter version of the security policy's name
Unique identifier that can\u2019t be changed after creation
A message describing the current state in more detail. For example, this can be used to provide actionable information for a resource in a {@code Failed} state.
The current lifecycle state of the security policy
Locks associated with this resource.
The owner of the security policy
The list of services that the security policy protects
System tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. System tags can be viewed by users, but can only be created by the system.
Example: {@code {\"orcl-cloud\": {\"free-tier-retained\": \"true\"}}}
The time the security policy was created. An RFC3339 formatted datetime string.
The time the security policy was last updated. An RFC3339 formatted datetime string.
A security policy (SecurityPolicy resource) defines security requirements for resources in a security zone. If a security zone enables a security policy through a security recipe (SecurityRecipe resource), then any action that would violate that policy is blocked.