Need Zero Trust for a Remote Workforce? There's a Missing Link.

Think you've secured every part of your remote employee's access? Think again. Here is what typical remote workforce security looks like:

  • the employee logs in to your network through the secure VPN - check.
  • employee uses cloud services and manipulates data, protected by the SaaS vendors - check.
  • employee access to data in the SaaS apps is limited by access controls - check.
  • employee exports data from the cloud service, and now has unfettered access to share or leak that data - OOPS!

Many enterprises have perimeter security, identity and access management, and contracts with SaaS vendors to protect their data while it is in the cloud. The weak link is the moment that data is exported by a user from a cloud service - whether Box, Dropbox, Salesforce, Github, AWS folders, SAP, etc. From the moment of export, the SaaS app vendor is no longer responsible for the data or its security, and other security tools like CASB do little to protect the data that has been exported. This allows ordinary users to accidentally share the data where it doesn’t belong, and malicious users to purposefully extract data with ease! 

This problem has been referred to as "last mile security", suggesting it is a minor edge case to be addressed down the line. However with the explosion of remote workers, contractors and 3rd party vendors working for most enterprises, and the fact that most data is now hosted in cloud services - this problem is now anything but "last mile". Securing data as it’s being exported into the user’s hands - data at the point of egress, in other words - is now front and center as the big challenge of enterprise data protection today.

What Security Tools Exist to Protect Data Exported From Cloud Services?

There are technologies that are commonly used to protect data exported from cloud services and SaaS applications, however as we will see, the problem with these technologies is that they do not work at scale. This is why cloud data leaks are so rampant, and only increasing in today's world of remote work. 

Cloud Access Security Brokers, or CASB, are installed by enterprises to filter data that passes to and from the cloud. 

By default, they allow all data to pass through unfettered, but run algorithms to attempt to identify and classify sensitive data and block the sensitive data from being shared, based on a rule set. Unfortunately, the automatic identification of data is highly error prone, often blocking data that should not have been blocked, while missing highly sensitive data that is allowed to pass without a word. 

CASBs have some practical uses. They can be useful to identify "shadow IT" - unsanctioned cloud services that employees are using. CASBs can apply classification to data that passes in and out of the cloud, which can be useful for enterprise data management and analytics, privacy and compliance programs. But as a way of solving the last mile problem, CASB does not begin to protect data accurately, and imposes a heavy burden on productivity along the way. 

Digital Rights Management, or DRM, is another technology that traditionally attempts to protect data exported from cloud services. DRM manipulates the data that has been exported from the cloud, encrypting files and embedding access control information into the header such that any attempt to access the file requires a callback to the enterprise server to allow the file to be decrypted. Unfortunately, this technology still relies on identification and classification to accurately identify what files to encrypt, which is highly error prone. And files that do get encrypted impose a heavy usability burden. Only certain file types can be encrypted, they can only be read by certain applications, they require special access credentials, there is no interoperability between DRMs, and access rights are often too restrictive, just to name a few limitations - rendering DRM-protected data unusable at scale. In practice, there are virtually no real-world examples of DRM deployments in the enterprise.

DASB Provides Zero Trust Data Protection, at Scale

Data Access Security Broker (DASB) is the missing link to protect data exported from cloud services, and more generally, to protect any data. 

There are 3 keys to the DASB paradigm:

  1. Data is protected by default. Much like a firewall that protects by default and allows by exception, DASB protects all data exported from cloud services by default. This is very different from CASB that is heavy and error-prone data classification techniques. 
  2. DASB is completely transparent to the end-user. DASB is able to protect by default because it can do so without the end-user even knowing that it is working behind the scenes. 
  3. DASB protects any type of data. Not just office files, but all formats including source code, specialized CAD, MOV and other formats, even home-grown and legacy data formats. 

When you can protect all data by default, any data type, and do that in a way that is completely transparent to the end-user, you have a paradigm that scales

With DASB, enterprises are now able to achieve zero-trust data protection, even on data exported from their SaaS apps into the hands of remote workers, contractors and third-party vendors. At scale, this means the largest enterprises enable productivity of their remote workforce with total protection. That data remains persistently protected wherever it goes, only accessible to those who have permissions to access it. However, DASB is completely invisible to end-users. This is true for any data type, without modifying applications or the data itself.

In today's work-from-anywhere world, there is a missing link. Controlling data once it is exported out of your perimeter and out of your SaaS apps. This is a rampant source of data leaks because no technology exists that can solve the problem at scale - until now. Welcome to DASB.

Zero Trust for a Remote Workforce