Identity, Security and Risk Requirements for a New IAM Architecture
The identity world circa 2015 still operates in stovepipes -- mobile, API, and web identities are often managed and secured using separate processes and technologies. The holy grail for the future of identity is a single standards-based federated Identity and Access Management (IAM) system with a high degree of automation. This would give IT leaders the visibility they need to monitor and identify patterns of use and abuse across the entire system, significantly reducing security risk and lowering IT costs with a focus on automation.
Join Pamela Dingle of Ping Identity's CTO Office as she discusses what kinds of design principles and opportunities exist to reduce risk for the enterprise. Pamela will walk through:
- Why existing IAM architectures could be improved;
- Identity, security and risk requirements for a new IAM architecture;
- Next generation architecture and protocol stack;
- Example use cases.
2015 marks a shift in how organizations architect identity solutions. This shift is a result of the ratification of modern identity standards that enable scale and automation, while normalizing the actual plumbing used to create trusted connections.
A next generation architecture attempts to propose a set of patterns for managing trust connections of every kind in a fully automated paradigm. Architects will construct a single identity platform, founded on a single protocol stack, capable of both distributing identities and securing identities within mobile, web and API contexts. New and existing architectural patterns can and will co-exist, giving architects the options they need to choose the best solution for their organization.
By creating a single platform and using a single protocol stack, organizations create a stable layer with which distributed entities of all kinds can communicate, freeing organizations from connection management, and instead allowing them to focus on security.
You might also be interested in …