Helping One of the World's Largest Oil & Gas Companies Migrate from Sailpoint's IIQ Platform to Identity Security Cloud

The decision on whether to migrate from IIQ to ISC is not based on simple feature-to-feature comparisons.  The organization needed to understand the effort and risk involved. Change management is a critical factor.  We needed to identify and convey the impact that the migration would have on business processes and operational change.  Additional drivers included:

• Adhering to standard IGA processes
• Differentiating only where there is high value
• Simplify and reduce support
• Stay aligned with global business projects
• Train their Support organization

Our Findings

The Xalient IAM Advisory team worked to document business requirements, operational needs, current IIQ functionality, customizations made to the platform, the needs their in-house custom built applications place on their IAM program. 

We then mapped what we found against the ISC platform.

• We identified 32 important gaps…
• 22% of the gaps had simple migration paths
• 78% had more complex paths that would include multiple teams and affect how the organization performed tasks today

Gap Example: Post Approval SoD Policy Checks.  SoD checks need to happen as an access request is being submitted/approved so that any access granted during the approval time frame is checked again for SoD conflicts. ISC did not yet contain an OOTB feature to add a post-approval hook for those additional SoD checks. The gap involved enough risk and effort to require understanding and remediation, which the Xalient team provided.