Cookie Settings
Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Other cookies are those that are being identified and have not been classified into any category as yet.

No cookies to display.

Shadow IT Identity Sprawl

Identity Sprawl And Shadow IT


Empowered people make pragmatic decisions to improve the productivity of themself and their team. This can often lead to the dreaded “shadow IT’, and, more specifically, “Identity Sprawl” with each system having unique login credentials, impacting security, scaling poorly, increasing end-user complexity.

The problem? Each system, introduced to fix a targetted problem, often has a new, unique, login for each new user. We call this ‘Identity Sprawl’. When the team is 3 people, this can be ok. But as the team scales, the inevitable problems arise:

  • users recycle the password
  • users do not get removed when they leave the team or organisation
  • password reset flow becomes a challenge (who do I talk with)
  • security audits fail

Solutions to Identity Sprawl exist, but are often championed by a different team, or too complex a process to obtain permission to use. OpenID Connect, SAML provide strong simple identity. Identity providers such as Azure, Google, Okta exist to harmonise the user side. However, often we are left with systems which don’t have a centralised authorisation layer (the other half of identity). Introducing the Agilicus Identity Aware Web Application Firewall can solve this in a single, central point in the network.

Let the new applications emerge, without fear of password breach, without complex retooling and rewriting to move the authorisation into them.