Hitachi ID Identity Manager includes the most advanced segregation of duties (SoD) policy engine on the market. It actually works, whereas SoD policy engines embedded in competitor product can be bypassed in cases where there are nested roles and/or nested groups.

The Identity Manager SoD policy engine supports:

  • Policy definition:
    • An SoD rule is defined as a toxic sets of entitlements.
    • Entitlements that participate in the SoD rule may themselves be roles, login IDs on specified target systems or membership in specific security groups.
    • Users who have at least N of the M SoD entitlements are considered to be in violation.

    This is a very general model. It supports rules such as "No user shall belong to more than 2 of these 30 groups."

  • Approved exceptions:
    • Users may be allowed to violate SoD rules, so long as an authorized person has approved the violation.
    • Access certification is used to periodically renew approved SoD exceptions.

    This is a practical model. It allows organizations to knowingly violate rules where there is a strong business reason to do so and where suitable compensating controls are in place.

  • Proactive enforcement:
    • Identity Manager's SoD policy engine is an integral part of the workflow engine.
    • All change requests that pass through the Identity Manager workflow engine must either:
      1. Satisfy all SoD rules (i.e., violate none); or
      2. Include a request for an approved exception to every violated rule.
    • Requesters -- via the Identity Manager UI, API or automation engine -- simply cannot ask for violations without also asking for an approved exception.

    SoD should be proactive rather than after-the-fact, wherever possible. This is supported by Identity Manager.

  • Reporting on out-of-band and pre-existing violations:
    • There are several ways to bypass the Identity Manager pro-active SoD enforcement engine:
      • Pre-existing conditions, where a user violated the SoD rule before Identity Manager was implemented.
      • Pre-existing conditions, where a user violated the SoD rule before the rule was added to Identity Manager.
      • Out of band changes, made by administrators outside of Identity Manager.
    • In these cases, there is no general way for Identity Manager to know which of the offending entitlements is inappropriate, so it cannot automatically remediate the violating users.
    • Instead, Identity Manager includes reports to identify violating users and help security staff make appropriate remediating changes.

    SoD reporting is the defense of last resort.

  • Deep inspection:

    Roles can be nested into other roles. Groups can include among their members other groups. The result of these two hierarchies is that an SoD policy may be defined at one level of a hierarchy of roles or groups, but a violation may take place at another level of the hierarchy. The Identity Manager SoD policy engine decomposes roles and groups and will always detect policy violations. SoD policy engines in competitor products cannot detect such violations.