Identity Management in 2017#

Identity Management has been around for a long time, even before we started automatting Web Blog_blogentry_030117_1.

In a typical Identity Management installation, we create users in LDAP and apply some Access Control Model ro control access to various Target Resources.

We may synchronize the Digital Identity from one repository to another. There are probably several methods used in most Organizational Entity from some perl scripts to sophisticated IDM Vendor Products.

Well, it is now 2017 and we have better, safer methods available.

Today a Organizational Entity must implement a dynamic IAM solution that serves employees, customers, partners and devices, regardless of location. This is the evolution of IAM to Identity Relationship Management (IRM).[1]

As customers look for and expect more ways to engage with businesses, companies are making the shift from the closed, protective world of IAM to the open, evolving, and confidently secure IRM universe. This is because identity and access management tools are a necessity for managing trust relationships with parties inside and outside of a company – relationships that are now tied directly to the business’ top line.

This shift in business emphasis has a direct technical impact on how we think about identity and access management. As a result, we need to take into account the following business-focused pillars when choosing an IRM solution:

  • CONSUMERS AND THINGS over employees
  • ADAPTABLE over predictable
  • TOP LINE REVENUE over operating expense
  • VELOCITY over process

Changing Business Values & A New Technical Approach to IAM#

IRM solutions that are able to satisfy the business needs of an organization and the new values of the CIO will shape the future of IAM. The shift to cloud, social, moble, and SaaS is revolutionizing the Organizational Entity, and IAM needs to evolve to help businesses capture new opportunities without worrying about the associated complexities that are a result of this change.

This shift in business emphasis has a direct technical impact on how we think about identity Management and Access Management. Through this shift we have must come to value:

  • INTERNET SCALE over enterprise scale
  • DYNAMIC INTELLIGENCE over static intelligence
  • BORDERLESS over perimeter
  • MODULAR over monolithic

Where do We Go in 2017#

To address the need for Identity Management or more so Identity Relationship Management, we have to build on a solid base.

We need to establish your security infrastructure on protocols and standards that have been peer-reviewed and are seeing market adoption.

For a long time, lack of such standards has been the main impediment for large organizations wanting to adopt RESTful APIs in earnest. This is no longer the case since the advent of the Neo-Security Stack:

These protocols gives us all the capabilities we need to build a secure and INTERNET SCALE API platform using OAuth 2.0 and OpenID Connect for the base.

Ran Across Today#

More Information#

There might be more information for this subject on one of the following: ...nobody

Add new attachment

Only authorized users are allowed to upload new attachments.
« This page (revision-13) was last changed on 03-Jan-2017 14:20 by jim