IBM Security Identity Governance and Intelligence, Version 5.2

IBM Security Identity Governance and Intelligence integration interface

As a centralized RBAC repository for IBM® Security Identity Governance and Intelligence platform authorizations, the AG Core must be integrated with an organization's previous architecture. Typically, in such pre-existing architectures, the available repositories that contain users' personal information and authorizations are not well-formed RBAC repositories.

The AG Core thus interacts with the surrounding environment in various ways:

AG Core Administration Module: Through the administration module, all main aspects of an organization can be described and translated to the IBM Security Identity Governance and Intelligence data model.
Provisioning: The AG Core can interface with a provisioning module that integrates a component for authorization workflow management.
Batch: A batch is group of procedures for bulk data loading and realignment.
External Repository: An external repository is a generic repository for data that must be kept aligned with data in the AG Core. By maintaining data alignment, the AG Core can propagate authorizations to other systems.

Figure 1. AG Core integration

The external repositories connect to the AG Core through a dedicated integration interface (II). Any number of external repositories can connect through this interface.

A flexible interface synchronizes and aligns the AG Core with the external repositories.

AG Core interacts with two types of repositories:

Personal data repository
Authorization repository

Figure 2. Types of external repositories

The basic framework has an input interface that passes information from personal data systems to the AG Core. Through the output interface, the AG Core transmits authorization information to the target systems. Any number of target systems can be connected to both the input and the output. The interface distinctly manages communication with each of them.