Identity Management Blog

I was re-reading an oldie-but-goodie, Frank Villavicencio’s blog titled Top 10 Common Pitfalls of an IAM Initiative. For anyone who has been responsible for an enterprise system deployment, especially an enterprise IAM system deployment, the top 10 reads like the 10 Commandments.
Read More
In Part 2 of this series, we talked about building a test plan for your IAM project implementation. Now we want to pick up where we left off and discuss conducting the testing on your system.
Today I want to talk about a very simple idea:
This post can also be found here on my personal blog.
I came across this post by David Maynor, and something really stuck out to me:
Based on feedback we've received from over 100 IAM projects, it's abundantly clear to us that organizations that have taken the up-front time to set-up an IAM Governance Body prior to detailing the specifications of the solution are typically far more successful than those that have chosen to 'play it by ear.' Unfortunately, too many organizations shy away from establishing an IAM Governance Body ...
Identropy adds a new offering as part of its well-known Advisory Services: the Identropy IAM Primer Series.  This offering not only provides access to Identropy's IAM best practices library, but also provides direct access to an Identropy IAM professional.
The best part of my job is customer interaction.  In the past 4 years, I've interacted with nearly 100 customers, and had the opportunity to see the inner workings of where the IAM rubber meets the road.  Real problems, real projects, real solutions.  Based on my experiences, I've decided to start a series that shares customers experiences that make a case for Identity-as-a-Service.
As with any market, IAM software vendors vie for business by positioning and re-position their software in front of potential customers. Ultimately, the customer selects a vendor, implements the software, and walks into the sunset...right? Wrong.
Based on my experience, most Identity and Access Management (IAM) consultancies - even the "Big 4" - tend to keep clients in the dark.  Due to the complexity of IAM projects and multiple stakeholders, it's easier to hide the gory details of a project gone wrong until its too late.  Unfortunately, this approach has given the IAM services industry a black eye.