Skip to main content

Beyond RBAC?

Kuppinger Cole recently had a discussion covering the potential boundaries of standard RBAC and if there are any potential next steps.  The talk focused on why RBAC projects fail and what are the main limitations of a static RBAC implementation. 

Most projects tend to fall foul of the main RBAC confusions:  What is the role supposed to represent?  A user? A job function? A set of entitlements?  In some cases the role will represent all of these things, but to different people.

One of the common scenarios we have seen during our deployments, tends to be the concept of role explosion.  The rapid increase in the number of entitlement carrying roles that attempts to match every possible access scenario within the organization.  In addition every department, area or even user adds to the concept of role exceptions where new and unique roles need to be created to match a particularly different set of entitlements or scenarios.

(Rock and) Role Explosion??

A lot of the underlying confusion manifests itself from the idea of access context.  Babak Sadighi from Axiomatics describes this concept as "..not always about who? and what? but also when? where? and why?.." access permissions are required and used.  His argument is to focus on 'privilege giving attributes' or Attribute Based Access Control (ABAC), with each of these attributes covering non-application specific characteristics such as environmental or resource based.

This allows Fine Grained Authorisation (FGA) to be done based on a users characteristics, their intent, the time of execution and also against the objects context.  If this scenario were to be managed using static RBAC, this would result in role explosion due to roles covering every possible combination of users,
 environments and sessions being created.

The role explosion arises due to the assumption that a role is simply used for static provisioning.  Once a user is associated with a role, they will receive the entitlements of that role.  If a separation of duty needs to be fulfilled, multiple accounts or roles could be used to cover the multiple combinations associated with the context.

One of the ways to overcome this scenario is to use XACML and the concept of ABAC.
XACML has seen prominence in recent years with increasing emphasis placed on interoperability and E2E access control with
several vendors entering this space, including Cisco with it's December 2007 acquisition of Securent.
The main idea with XACML is to allow authZ decisions to be made using the subject, action, resource and environmental characteristics extending the static RBAC and user model with a real time Policy Decision Point.

As more and more organisations deploy an RBAC model of some description, be it to aide provisioning or to simplify administration tasks, the need for a more dynamic and extensible access control framework will develop and the maturity of something like XACML maybe help this process.


Popular posts from this blog

2020: Machine Learning, Post Quantum Crypto & Zero Trust

Welcome to a digital identity project in 2020! You'll be expected to have a plan for post-quantum cryptography.  Your network will be littered with "zero trust" buzz words, that will make you suspect everyone, everything and every transaction.  Add to that, “machines” will be learning everything, from how you like your coffee, through to every network, authentication and authorisation decision. OK, are you ready?

Machine Learning I'm not going to do an entire blog on machine learning (ML) and artificial intelligence (AI).  Firstly I'm not qualified enough on the topic and secondly I want to focus on the security implications.  Needless to say, within 3 years, most organisations will have relatively experienced teams who are handling big data capture from an and identity, access management and network perspective.

That data will be being fed into ML platforms, either on-premise, or via cloud services.  Leveraging either structured or unstructured learning, data fr…

Customer Data: Convenience versus Security

Organisations in both the public and private sector are initiating programmes of work to convert previously physical or offline services, into more digital, on line and automated offerings.  This could include things like automated car tax purchase, through to insurance policy management and electricity meter reading submission and reporting.

Digitization versus Security

This move towards a more on line user experience, brings together several differing forces.  Firstly the driver for end user convenience and service improvement, against the requirements of data security and privacy.  Which should win?  There clearly needs to be a balance of security against service improvement.  Excessive and prohibitive security controls would result in a complex and often poor user experience, ultimately resulting in fewer users.  On the other hand, poorly defined security architectures, lead to data loss, with the impact for personal exposure and brand damage.

Top 5 Security Predictions for 2016

It's that time of year again, when the retrospective and predictive blogs come out of the closet, just before the Christmas festivities begin.  This time last year, the 2015 predictions were an interesting selection of both consumer and enterprise challenges, with a focus on:

Customer Identity ManagementThe start of IoT security awarenessReduced Passwords on MobileConsumer PrivacyCloud Single Sign On
In retrospect, a pretty accurate and ongoing list.  Consumer related identity (cIAM) is hot on most organisation's lips, and whilst the password hasn't died (and probably never will) there are more people using things like swipe login and finger print authentication than ever before.

But what will 2016 bring?

Mobile Payments to be Default for Consumers

2015 has seen the rise in things like Apple Pay and Samsung Pay hitting the consumer high street with venom.  Many retail outlets now provide the ability to "tap and pay" using a mobile device, with many banks also offer…