A Tale of Two CASBs

This post was originally published here by  Nat Kausik.

‘Twas the summer of 2016, when the two largest healthcare providers in the US selected CASBs.  One selected the Next-Gen CASB Bitglass, whilst the other selected a First-Gen CASB.  Skip ahead to 2018 and…

The organization that selected Bitglass is in full production with close to 200,000 users. Every employee at the organization accesses any and all cloud applications inline via Bitglass.  They even use our native SSO with step-up multi-factor authentication.  BYOD or Grandma’s laptop? No problem, real-time inline access control and DLP.

And what of the other organization?  They too have about 200,000 users.  But as of today, they have ten users in production via the CASB.  Yes, 10.  Despite repeated attempts to deploy. Turns out the First-Gen CASB requires agents on every device in order to be deployed.  No BYOD. No Grandma’s laptop.  No SSO.  Undeployable.

To quote Dickens,

It was the best of times,
it was the worst of times,
it was the age of wisdom,
it was the age of foolishness…

Photo:Fortinet Blog


No posts to display