CloudSSO:Configure alert notifications of SCIM credential expiration and SAML signing certificate expiration

Scenarios

Procedure

Perform the following operations as a CloudSSO administrator:

Step 1: Create a rule in Cloud Config

1. Log on to the Cloud Config console.

2. Click Activate Now to activate Cloud Config.

   Note

   If you have activated Cloud Config, skip this step.

3. Create a rule.

   1. In the left-side navigation pane, choose Compliance & Audit > Rules.

   2. On the Rules page, click Create Rule.

   3. In the Select Create Method step, select Based on managed rule, select a rule, and then click Next.

      Select cloudsso-scim-credential-expired-check or cloudsso-directory-saml-expired-check.

   4. In the Set Basic Properties step, configure the parameters and click Next.

      In the Parameter Settings section, specify a value in the Expect Value column. The value specifies the number of days before the expiration date during which expiration notifications are sent. The default value is 90 days. You can change the value based on your business requirements.

      Retain the default values for other parameters.

   5. In the Set Effective Scope step, view the selected resource types and click Next.

   6. In the Set Remediation step, click Submit.

      You can turn on Set Remediation and configure template remediation or custom remediation for the rule as prompted. For more information about how to configure remediation, see Overview of remediation settings.

Step 2: Configure a system event-triggered alert rule in the CloudMonitor console

1. Log on to the Cloud Monitor console.

2. Create an alert contact.

   For more information, see Create an alert contact.

3. Create an alert contact group.

   For more information, see Create an alert contact group.

4. Create an event subscription policy.

   After Cloud Config delivers all non-compliance events to CloudMonitor, you can create an event subscription policy based on your business requirements to receive alert notifications for non-compliance events in emails.

   1. In the left-side navigation pane, choose Event Center > Event Subscription.

   2. On the Subscription Policy tab, click Create Subscription Policy.

   3. On the Create Subscription Policy page, configure the parameters.

      • Basic Information: Enter a name for the subscription policy.

      • Alert Subscription: Set the Subscription Type parameter to System events. In the Subscription Scope section, set the Products parameter to CloudConfig, the Event Type parameter to Notifications, the Event name parameter to ConfigurationNonCompliantNotification, and the Event Level parameter to Notification (Info). Enter one or more keywords in the Event Content field or leave this parameter empty. Leave the Application grouping and Event Resources parameters empty.

        Note

        • For more information about the system events supported by Cloud Config, see the events listed on the CloudConfig page.

        • The information that you enter in the Event Content field is used to match the events. For example, if you enter Critical in the Event Content field, only rules whose Risk Level is High in Cloud Config are matched. You can leave this parameter empty or enter one or more keywords based on your business requirements.

      • Noise Reduction: Use the default settings.

      • Notification: Select the alert contact group that you created in Step 2 from the Notification Configuration drop-down list. Use the default settings for the Custom Notification Method parameter.

        Note

        • For more information about how to create a notification configuration, see the Create a notification configuration policy section of the "Manage notification configurations" topic.

        • CloudMonitor automatically sends alert notifications based on the notification methods for the alert contacts in the specified alert contact group and the corresponding alert levels in the custom notification method.

      • Push and Integration: No configuration is required.

   4. Click Submit.

References

• Create a rule based on a managed rule

• Use CloudMonitor to trigger alert notifications for non-compliance events