A white and black box made up of smaller boxes has a blue circle in the middle that is shooting small data points out of it.

IBM Security Identity and Governance Intelligence (ISIGI) allows organizations to have a centralize solution to be able to manage accounts, request accesses, review accesses, reset passwords, generate out-of-box or custom reports and etc. As the solution matures these features would need further customization to meet complex business requirements.

This is where the ISIGI rules engine extends the functionality of ISIGI to meet these complex business requirements. The ISIGI rules engine is a powerful feature as it is called in majority of the workflows. On-boarding, Off-Boarding, Access Requests, Adoption of Accounts, Reporting, and many more. These rules are Java code implemented with the Drools Rules Engine embedded in ISIGI.

Creating and Adding Custom Rules

Cache Time

This is an important part of ISIGI's rule engine, by default this time is set to 120. This means that once you have created a custom rule and have inserted this in the rule flow ISIGI would not recognize this rule as the cache timer has not reset yet.

Step 1: Navigate to the Task Planner Module.

Step 2: Click the Manage Tab, then under Tasks select Rule Engine.

Step 3: Stop the Rules Engine Task.

Step 4: Select Rules Engine, then Event IN Dispatcher.

Step 5: On the right window set the cacheTime to a different value.

ISIGI Rules Reference

Have the ISIGI Rules Reference Guide with you at all times. You can download the sdk within ISIGI's appliance console in:

Step 1: Navigate to ISIGI's Appliance Dashboard.

Step 2: Click Configure, then Custom File Management.

Step 3: Select the sdk directory and download the .zip file in the folder.

Step 4: Once the .zip has been downloaded and extracted, the classes used in ISIGI rules engine can be viewed. (Or you can also access the link created by Stephen Swann.)

The Rule Flow

ISIGI's rule flow is sequential. You would need to understand the function of each rule and find the best position to insert your created rule. In the image below the custom class that was created is the Modify DN ATTR rule. This rule calculates the DN attribute of the ISIGI person record if one is not provided.

Debugging Logs

In ISIGI's Access Governance Core Module the Monitor tab displays all requests, from requests made within ISIGI and requests to Target Applications. The rule engine requests however are found in a separate location. This is where the you can view the debug messages, dump entries and troubleshoot errors on the custom rule.

Step 1: Navigate to ISIGI's Appliance Dashboard.

Step 2: Click Configure, then Custom File Management.

Step 3: Select and expand the log directory.

Step 4: Select iga_core directory.

Step 5: Select the accessgovernancecore_event_in.log to see latest log.

Customizing ISIGI’s Rules Engine for Complex Business Needs

Services

Solutions

Pricing

Resources

Events

About Us

Get Started