It seems like the same question comes up with just about every customer or prospect: "Will your product introduce additional latency into our cloud app environment?" It's a legitimate question since our hybrid CASB architecture includes proxies for real-time policy enforcement. If you guessed that the Bitglass proxy would be slower, you would be wrong!
By definition, a proxy includes an additional network hop, so how is that possible? First, let's look at some data.
When most people think about cloud app security, they think about controlling access to apps like Salesforce and Office 365, providing visibility into who's doing what in ServiceNow and Workday, and even encrypting data at rest in Box and Google Apps. These are all solutions to protecting data in cloud applications. Bitglass was founded to solve these types problems - the data security problems that arise when enterprises move from internal, premises-based applications, to external cloud apps.
SSL encrypted traffic has increased tremendously over the last 5 years, representing 50% of traffic on some networks. The increased adoption of cloud applications during the same time period, apps like Google Apps, SalesForce, Workday, ServiceNow, etc also increases SSL traffic. Even social networking and consumer apps like Facebook, Gmail, and Google search now utilize SSL.
This has created a blind spot for enterprise IT if they have not rolled out a mechanism to decrypt SSL traffic.
What happens when your security infrastructure no longer sees what it's supposed to protect?