Best practices for context based Authentication

The choice of an authentication mechanism is not only dictated by the security assurance level of the information being accessed. Often the choice is also influenced by the context in which the information is being used. Device type, location, time and history are only a few examples. But not only technical aspects play a role. Cost of ownership of the authentication mechanism, user experience and regulations should not be neglected either.

Challenge or Opportunity ?

Looking at the market of Identity and Access Management solutions today, organisations are forced to make a compromise between authentication enforcement mechanisms that are available out-of-the-box, and what the organisation really needs. They are facing the challenge of finding the right balance.

With TrustBuilder IDHub we turn this challenge into an opportunity.

TrustBuilder IDHub has a powerfull policy engine on board that can deal with just any set of contextual information that might influence the selection of the right authentication mechanism. Organisations often find it hard to expose sensitive data using the out-of-the-box authentication enforcement mechanisms that are provided by standard tools.

This policy engine of TrustBuilder IDHub however allows defining conditions under which such data can be made available to a large audience. The engine comes with a comprehensive and user-friendly interface that makes designing and evaluating such rules available to non-technical employees.

Business benefits

  • Ease of use: present user validation of choice, depending on the use case
  • Conditional behaviour: take context into account to determine the way a user's Identity is validated


TrustBuilder is the Number One product offering pervasive local and Cloud Access Management


To receive our new technical white paper 

Check more key topics? Go to the overview of Secure Digital Enterprise opportunities