Auto-Discovery Infrastructure

Hitachi ID Bravura Identity includes an auto-discovery process, used to extract a list of accounts, groups, group memberships and more from every integrated system. The discovery process is scheduled to run regularly -- usually every 24 hours and can be manually triggered.

  • Every Bravura Identity connector supports list operations.
  • By default, auto-discovery is scheduled to run every night. Some organizations choose to schedule it more frequently.
  • When connecting to each managed system, an inventory of all login IDs (accounts) and all available security groups or roles is normally extracted.
  • On systems that support this, incremental listing is used to reduce runtime -- i.e., list only IDs that have been added, changed or moved since the last list.
  • The membership in those security groups or application roles which have been marked as 'Managed' in Bravura Identity is extracted.
  • Connections to target systems are made in a massively multi-threaded fashion, to minimize runtime.

The list operation in all Bravura Identity connectors writes list files to the filesystem of the relevant Bravura Identity server. Once list files are generated, a separate process determines what changed in each list file and loads appropriate updates into the Bravura Identity database. This includes:

  • Updating group, account, group membership, attribute and related data in the database, to reflect current state on target systems.
  • Creating new or disabling existing Bravura Identity user profiles, where new accounts were discovered on systems marked as 'source of profile' or existing profile accounts were disabled or disappeared.
  • Triggering automated processes, such as provisioning network access in response to newly discovered HR records.
  • Detecting out-of-band administrative changes, such as placing a user into an Administrators group and responding with e-mail alerts, workflow requests to undo or approve the change, etc.

The entire process can take from a few minutes (in smaller deployments) to 2--3 hours to run (in enterprises with tens of thousands of users and hundreds of integrated systems).

On Active Directory in particular, auto-discovery can be configured to monitor AD for changes in real time. This means that while an initial auto-discovery is performed in batch mode, subsequent changes committed to the AD database are detected by Bravura Identity, loaded and responded to in real time. A persistent connector service (PCS) keeps the AD connector signed into a local domain controller and polls for changes to accounts, groups or group memberships every few seconds.

Monitoring AD for changes in real time has several benefits:

  1. Bravura Identity can respond to changes in AD in real time.
  2. The remaining tasks in the bulk auto-discovery process take less time to complete, so auto-discovery can be scheduled to run more frequently.
  3. Integration with very large directories is possible, as a multi-hour load only takes place initially, rather than daily.

Excluding Users

User objects that are not intended to be managed by Bravura Identity can be excluded from the auto-discovery process. This is useful to exclude administrator IDs, machine IDs, service accounts, test users and user profiles for out-of-scope human users. Several methods are available to exclude such users:

  1. By identifying them individually:

    Product administrators can add users IDs to a table which enumerates users who, should they appear on target systems, should not be included in Bravura Identity.

  2. Using exclude and include files:

    Product administrators can create files in the Bravura Identity staging directory which either specify lists of users to include or exclude.

    These files are treated as filters when processing lists of users extracted from each target system.

  3. Using group memberships and organizational units:

    Bravura Identity can be configured to integrate with target systems such as LDAP or Active Directory in a manner that specifies OUs or groups to include. This allows Bravura Identity to be used to manage users in one part of a directory and not another.

  4. Using scripts:

    Product administrators can write short scripts to post-process lists of users extracted from target systems, for example to exclude users based on string pattern matching (regular expressions).

Detecting Unauthorized Changes

Bravura Identity can detect all administrative changes made to users and entitlements on target systems as a normal part of the auto-discovery process. This includes new users, terminated users, attribute changes and group membership changes.

Normally such changes are simply loaded into the Bravura Identity identity cache, so that the various Bravura Identity processes can act on correct current state data.

Such changes can also be fed into alarm systems (such as e-mail or SMS), can be reported on and can be fed as input to the auto-provisioning component of Bravura Identity, for example to automatically revoke unauthorized group memberships. Since auto-discovery on some systems (AD, AD-LDS) can be performed in real time, this can have the effect of locking down membership in certain groups, such that unauthorized changes are reversed immediately.

The auto-provisioning module (ID-Track) applies business logic to decide what to do about detected changes -- (disable unauthorized new accounts, revoke group membership changes and so on). Changes are submitted to the workflow manager, where they may be automatically approved or require human authorization before being executed.

Automated removal of detected changes is not recommended as a default strategy as it is difficult to predict a-priori what kinds of changes might be legitimately required by systems administrators. It is usually safer to report on changes than to blindly revoke them. Human beings can then decide whether to retain or back out changes made outside of Bravura Identity.