Have you attempted to consolidate or rationalize your organization's identity management tools? What are the main hurdles to addressing IAM tool sprawl?

I've taken a somewhat unconventional approach by removing all IAM tools, focusing on simplifying internal processes and fixing integration jobs. We now rely entirely on the current Microsoft toolset. I have asked my team to revisit our IAM landscape around September this year, anticipating changes in the environment and toolsets, and expecting announcements from Microsoft. This approach aims to streamline our IAM processes and prepare for future developments.

Our organization is relatively immature in the IAM space, with numerous legacy systems and clunky software. We've faced several failed attempts to comply with audit requirements, such as access reviews and addressing extraneous access. Automation has been a significant challenge, and we are still learning from others in this space. A recent project to automate timesheet access setup, which would save time and allow employees to focus on critical security tasks, was halted due to unaddressed issues from the software provider. Legacy systems and outdated or overly customized software versions pose significant challenges, leaving us unsure where to begin the consolidation process.

Consolidation is a challenge. We have embarked on a journey towards implementing an identity fabric in our organization. We are currently in the phase of creating an interconnected mesh, as outlined by Gartner, to unify all our identity management (IAM) tools into a single platform for IAM-related requests and management. One of the main hurdles is demonstrating the benefits of this consolidation to management and other teams. For instance, with ServiceNow handling all types of requests, it can be challenging to justify the creation of an additional system that overlaps in functionality. Showcasing the intangible benefits and value of such a consolidation is a significant challenge.