Pages

Sunday, October 2, 2016

Graph Advantage: Identity and Access Management

Identity and Access Management for a complex media workflow was actually my first experience with Neo4j as a graph database solution that enabled us to represent access throughout the flow in a structure realistic to the way it actually existed. During the last 4+ years since then I’ve continued to see Identity and Access Management as major beneficiary of the flexible data model and
performance of non-JOIN node traversal of the Neo4j graph database.
The access and authorization structure in enterprises today is constantly evolving and becoming increasing complex. The user structure within organizations today rarely fits well into simple tree structure, especially when dealing with approvals, collaboration across internal groups and integration with external groups where role levels of access and permission vary by business use case rather than by the position or title held within the organization.

Signs Your Identity & Access Management System Needs a Graph Makeover

If you’re seeing these signs it’s time to considering going graph:
  • Access is No Longer Static Based on Title
    In the modern enterprise access and authorization tends to be driven by function rather than position. As collaboration across departments and teams becomes the default the increasing complexity of permissions for such a user model does not fit well into traditional user and access management systems.
  • Performance Degrades as Complexity Increases
    As users have their roles and access evolving with ever more caveats driven by the function within a particular team at that time, the queries to return access and authorization for specific actions increase drastically until there becomes a need to duplicate the user account to represent their multiple functions purpose With users, permissions, and products growing, older systems no longer deliver a responsive query performance, leading to user frustration and diminished experience.
  • Adding New Users Takes Hours
    Due to increased user size and expanding metadata complexity, entering a new

No comments:

Post a Comment