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 rules and identity audit
One Identity Manager users for identity audit
Basic data for setting up rules
Mitigating controls
Configuration parameters for Identity Audit
Rule groups
Compliance frameworks
Schedules for checking rules
Extended properties and property groups
Functional areas
Attestors
Rule supervisors
Exception approvers
Standard reasons
Setting up a rule base
Creating rules
rule check
Setting up a rule
Risk assessment
Extended rule input
Rule comparison
IT Shop properties for a rule
Additional tasks for working copies
Creating rule conditions
Overview of the working copy
Assigning compliance frameworks
Mitigating controls
Enabling working copies
Recalculating
Copy rule
Comparing a rule working copy with the original
Maintaining exception approvers
Maintaining rule supervisors
Enabling SQL definition
Additional tasks for rules
Basics for using the Rule Editor
Specifying the affected employee group
Specifying affected entitlements
A simple rule example
Rule conditions in advanced mode
Rule condition as SQL query
Deleting rules
Checking a rule
Creating custom mail templates for notifications
Scheduled rule checking
Rule checking rule modifications
Ad-hoc rule checking
Speeding up rule checking
Rule check analysis
Reports about rule violations
Granting exception approval
Notifications about rule violations
Determining potential rule violations
Additional tasks for compliance frameworks
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
- Select the Identity Audit | Basic configuration data | Compliance frameworks category.
- Select the compliance framework from the result list.
- 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
- Select the Identity Audit | Basic configuration data | Compliance frameworks category.
- Select the compliance framework from the result list.
- Select the Assign rules task.
- 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.
- 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
- Select the Identity Audit | Basic configuration data | Schedules category.
The result list shows all schedules configured for the ComplianceRule table.
- Select a schedule in the result list. Select the Change master data task.
– OR –
Click
in the result list.
- Edit the schedule’s master data.
- Save the changes.
Enter the following properties for a schedule.
|
Property |
Meaning |
|---|---|
|
Name |
Schedule ID. Translate the given text using the |
|
Description |
Detailed description of the schedule. Translate the given text using the |
|
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.
|
|
Occurs |
Interval in which the task is run. Permitted interval types are 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. |
button.