The reconciliation capabilities available in the solution examine and compare actual state versus desired state. If a difference is detected the system automatically initiates a predefined process to address the issue. This action is performed for all systems, connected or unconnected to automated processes such as provisioning.

The fundamental principle of Omada’s reference architecture is importing and capturing of all identity and access related data from target systems. This data import provides an overview of the actual state of identities, entitlements, or access rights. 

Based on the overview of the actual state of data, reporting and analytics can be applied, and surveys can be initiated for recertification of access rights by a line manager or system owner, role owner or whoever has that knowledge, getting verification of the proper state of access. 

When the actual state has been verified, processed and enriched, it becomes the desired state. Using this generated  overview of the desired state, policies and workflows can be applied to make changes using the solution and  maintain full control of your environment.
 

Automated Reconciliation Process 

Once changes have been made in the target system, the new dataset is imported once again to compare and reconcile the actual state, ensuring that all the changes from the desired state was applied into the actual state, and that the target systems are in sync. 
 

Continuous Compliance

The reconciliation process means that system owners are automatically presented with information if certain entitlements in their systems need to be de-provisioned. Based on this information the problematic entitlements are removed. After this step the solution runs an import that validates the de-provisioning.