Oracle Cloud Infrastructure Documentation
Try Free Tier

Some Common Features

As you prepare to customize Oracle Cloud Guard, there are several features that are common across more than one area.

You can preview these features in the following sections before you start customizing Cloud Guard, or you can follow links from specific tasks where the information is helpful.

Overview of Recipes

Understand the differences between Oracle-managed and user-managed recipes, how user-managed recipes work, and what settings can be changed at the recipe and target levels.

The three sections below also appear in About OCI Responder Recipes and About OCI Detector Recipes.

Using Conditional Groups with Recipe Rules

Conditional groups let you quickly set the scope for which a detector or responder rule should be activated.

Conditional Groups for Detectors

A conditional group sets parameters that you specify, to limit the scope of situations for which the violation of a detector rule actually triggers a problem:

  • For configuration detectors, conditional groups allow for inclusion or exclusion of specific resources from monitoring.
  • For activity detectors, conditional groups allow for limiting activity detectors to certain IP spaces, regions, users, groups, or resources.
  • To implement conditional groups, when you are modifying a detector recipe rule:
    1. Select the Parameter, Operator, and Custom List or a Managed List.
    2. Input one or more entries for the Value to be matched.
    • To set a condition on a parameter other than tags, follow these steps:
      1. In the Parameter list, select a parameter other than Tags.
      2. Select an Operator, a List, and a Value.
      3. To add another condition, select Another condition.
        Note

        Specifying multiple conditions acts as an AND operator. The rule is enforced only if all the conditions are met.
    • To set a condition on tags, follow these steps:
      1. In the Parameter list, select Tags.
      2. Select an Operator (In or Not In).

        If you select In, the rule affects only items that are tagged with one of the tags that are in the list that you provide.

        If you select Not In, the rule affects only items that are not tagged with one of the tags that are in the list that you provide.

      3. select Select tags.
      4. In the Select tags dialog box, set a condition for defined or free-form tags:

        To set a condition for defined tags, select a Tag namespace other than None, select a Tag key, and then select or enter the Tag value:

        To set a condition for free-form tags, for Tag namespace, select None for Tag namespace, enter a Tag key, and then optionally enter the Tag value.

        Add more tags as needed.
        Note

        When you specify multiple tags, the rule is enforced only if all the conditions are met.
      5. To add another conditional group, select Another conditional group and repeat the preceding steps.
  • You can add a condition for a single resource and input at a time using a custom list, or add multiple resources and inputs at once using managed lists.

Example: You have 10 Compute Instances. Two instances (Instance1 and Instance2) should be public, so you don't want the "Instance is publicly accessible" rule to trigger problems on these instances. You can use conditional groups to exclude these two instances, using either custom lists or managed lists.

Using Managed and Custom Lists with Recipe Rules

Managed lists let you quickly set the scope for which a recipe rule should be applied, by including or excluding a predefined list of parameters. Custom lists let you enter a short list of parameters for the same purpose.

Was this article helpful?