Over the last decade, IT has grown from being a support function to being at the core of any business. Car manufacturers are morphing into transportation service industries; IoT and mobile has evolved from a luxury item for the executive few to an indispensable accessory. Everything is digital: plane tickets, ledgers, medical records, bank accounts, education, credit checks, and even votes in some places.
With so many digital services being offered, so much data being generated, and so many different ways to consume it, it is easy to lose track of who’s got access to what let alone for what purpose. It’s equally hard to know who did access data about you.Yes, this is getting both personal and sensitive. The Equifax breach in 2017 was a stark reminder that collectively, we don’t have things under control: security checks have too often been built as independent silos each with its own access mechanisms.
Dynamic Authorization Management (DAM) can help us keep things under control. In this presentation, David will pull from his experiences over the last decade to illustrate how DAM can help simplify authorization management, enhance traditional access control mechanisms such as RBAC, enable new technologies e.g. microservices, and stay compliant with new rules and regulations such as GDPR and consent management.
The presentation will address existing authorization processes e.g. the joiner-mover-leaver process and how they can be simplified. It will also delve into how Dynamic Authorization Management can be used to enable a smoother, more secure digital transformation strategy by putting controls directly on the data and at the API level while letting business owners decide and implement their own business and authorization rules.
Key Takeaways:
OAuth is well established as the go to protocol for API security, but there are still a few application types out there that struggle to securely fit into the OAuth story. This includes devices where user input is tricky, where data entry uses a tv remote control, and everyone gets to see you slowly type in your password. Or devices where there is no browser, where the dreaded Resource Owner Password Credentials grant type still reigns.
Finally, there is a solution, with the all new Device flow for OAuth, specially designed for browserless platforms or devices with limited input methods. In this talk we’ll see the device flow in action by extending IdentityServer 4, an open source OpenID Connect and OAuth written in .NET, and look at how it is an improvement on existing solutions using real world scenarios where it should be used.
Key Takeaways:
Even though it may currently seem that solving GDPR challenges is all we need to take care of - there are a few more challenges related to IAM and its infrastructures that need to be solved, whether related to Consumer or Enterprise Identities or IoT Devices and many more contexts.
For sure, there is no 'one size fits it all' solution, but some of the technologies and new paradigms will help shaping tomorrows landscape and its view on identities
Key Takeaways:
