Compartment OCID
Defined tags for this resource. Each key is predefined and scoped to a namespace. Example: {@code {"foo-namespace": {"bar-key": "value"}}}
Responder recipe description
Responder recipe display name
List of currently enabled responder rules for the responder type, for recipe after applying defaults
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.
Unique identifier for the responder recip
A message describing the current state in more detail. For example, can be used to provide actionable information for a resource in Failed state.
The current lifecycle state of the example
Owner of responder recipe
List of responder rules associated with the recipe
The unique identifier of the source responder recipe
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 date and time the responder recipe was created. Format defined by RFC3339.
The date and time the responder recipe was last updated. Format defined by RFC3339.
A ResponderRecipe resource contains a specific instance of one of the supported detector types (for example, activity, configuration, or threat).
A ResponderRecipe resource: * Is effectively a copy of a Responder resource in which users can make very limited changes if it\u2019s Oracle-managed, and more changes if it\u2019s user-managed. * Can also be created by cloning an existing ResponderRecipe resource, either user-managed or Oracle-managed. * Is visible on Cloud Guard\u2019s Responder Recipes page. * Is located in a specific OCI compartment. * Can be modified by users, programmatically or through the UI. * Changes that can be made here apply globally, to resources in all OCI compartments mapped to a target that attaches the responder recipe, but are overridden by any changes made in the corresponding TargetResponderRecipe resource (effectively created when the responder recipe is attached to the target).