The only improvement is that it has to be a bigger part of an end-user device. It should look at how endpoints appear on the EDR rather than creating an API to integrate into the agent app which need additional development effort. We have to integrate the source code into the system endpoint and make it as part of the connected app.

The issues with CloudLock are mostly for Google to address. Google is all about trusting users, which is a nightmare for an administrator. It allows any user to intentionally or accidentally give a random third party full access to a Google account. As long as this issue exists, CloudLock or any other product is only a band-aid solution. It can only work reactively, and not stop the incident from occurring.

Like all CASB products, this product also needs to expand its capabilities and features in order to increase scope of application.

CloudLock’s security consists of eight core security services including content analysis, context analysis, user behavior monitoring, policy automation, central auditing, incident management, encryption management, and security analytics. We have been using it in Google App for work purposes. It depends on API-based, cloud-to-cloud integration. The API availability from CSP limits their option to integrate and scope for expansion, especially since the cloud service provider’s ecosystem has been growing very fast. I would recommend taking a different approach to integration which is similar to the SkyHigh or Splunk software.

The solution needs to have better integration capabilities. I have a lot of customers asking about how they can integrate it better.

• Reporting
• Simpler policy creation