Chat now with support
Chat mit Support

Identity Manager 8.1.5 - Compliance Rules Administration Guide

Compliance rules and identity audit
One Identity Manager users for identity audit Basic data for setting up rules Setting up a rule base rule check Creating custom mail templates for notifications
Mitigating controls Configuration parameters for Identity Audit

Additional tasks for compliance frameworks

After you have entered the master data, you can run the following tasks.

In the Rule violation overview report, you get an overview of all rule violations for a compliance framework.

Compliance framework overview

You can see the most important information about a compliance framework on the overview form.

To obtain an overview of a compliance framework

  1. Select the Identity Audit | Basic configuration data | Compliance frameworks category.
  2. Select the compliance framework from the result list.
  3. Select the Compliance framework overview task.

Assigning rules

Use this task to assign compliance rules to the selected compliance framework.

To assign a compliance rule to compliance frameworks

  1. Select the Identity Audit | Basic configuration data | Compliance frameworks category.
  2. Select the compliance framework from the result list.
  3. Select the Assign rules task.
  4. In the Add assignments pane, double-click on the compliance rules to be assigned.

    – OR –

    In the Remove assignments pane, double-click on the compliance rules that you want to remove.

  5. Save the changes.

Schedules for checking rules

Cyclical checking of all rules is controlled through schedules. One Identity Manager provides two default schedules for rule checking. This ensures that the auxiliary table for object assignments are regularly updated and that rule checking is started. You can set up more schedules to do this. Ensure that the schedules are assigned to the rules.

To edit schedules

  1. Select the Identity Audit | Basic configuration data | Schedules category.

    The result list shows all schedules configured for the ComplianceRule table.

  2. Select a schedule in the result list. Select the Change master data task.

    – OR –

    Click in the result list.

  3. Edit the schedule’s master data.
  4. Save the changes.

Enter the following properties for a schedule.

Table 5: Schedule properties

Property

Meaning

Name

Schedule ID. Translate the given text using the button.

Description

Detailed description of the schedule. Translate the given text using the button.

Enabled

Specifies whether the schedule is enabled or not.

NOTE: Only active schedules are run.

Time zones

Unique identifier for the time zone that is used for running the schedule. Choose between Universal Time Code or one of the time zones in the menu.

NOTE:

When you add a new schedule, the time zone is preset to that of the client from which you started the Manager.

Start (date)

The day on which the schedule should be run for the first time. If this day conflicts with the defined interval type, the first run is on the next available day based on the start date.

Validity period

Period within which the schedule is run.

  • If the schedule will be run for an unlimited period, select the Unlimited duration option.

  • To set a validity period, select the Limited duration option and enter the day the schedule will be run for the last time in End (date).

Occurs

Interval in which the task is run. Permitted interval types are Every minute, Hourly, Daily, Weekly, Monthly, and Yearly.

For the Weekly interval type, specify the precise weekday. For the Monthly interval type, specify the day of the month (1st to 31st day of the month). For the Yearly interval type, specify the day of the year (1st to 366th day of the year).

NOTE: If the schedule is not going to be run until next month because the interval type is Monthly with sub-interval 29, 30, or 31, the last day of the current month is used.

Example:

A schedule that is run on the 31st day of each month is run on 30th April. In February, the schedule is run on the 28th (or 29th in leap year).

Schedules with the interval type Yearly with sub interval 366 are only run in leap year.

Start time

Fixed start type for the Daily, Weekly, Monthly, and Yearly interval types. Enter the time in local format for the chosen time zone.

For the interval types Every minute and Hourly, the start time is calculated from the rate of occurrence and the interval type.

Repeat every

Rate of occurrence for running the schedule within the selected time interval. For the Weekly interval type, select at least one weekday.

Last planned run/Next planned run

Execution time calculated by the DBQueue Processor. Execution times are recalculated whilst the schedule is running. The time of the next run is calculated from the interval type, rate of occurrence, and the start time.

NOTE: One Identity Manager provides the start information in the time zone of the client where the program was started. Changes due to daylight saving are taken into account.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen