A versatile and powerful tool for protecting supported SaaS applications
Use Cases and Deployment Scope
Pros
- Data Loss Prevention - files accessed from outside of the organization can be audited or blocked based on content, file type, and regex
- Policy Management - policy options are sophisticated and give great control over the actions to be taken and when the policy should be triggered
- Behavioral Analysis - cloudlock is usually the first place we learn about suspicious activity in our SaaS applications, such as login attempts from outside the country
Cons
- Ease of use - the UI is not the easiest to grok. Some customers install it and expect it to just work, when in fact most of the policies are not enforced by default. Something like a basic tutorial wizard for policies would help tremendously.
- Dashboard organization - CloudLock does a number of things, but in the UI they are all jumbled together with a single click moving you out of the feature you intended to configure and into a totally different part of the application
- Limited Supported Offerings - internally and with customers a lot of additional cloud vendors have been requested, but the product only supports a small number of core services, with no roadmap for adding more that I am aware of.
Likelihood to Recommend
A situation where it is wholly inappropriate is for monitoring AWS, Google Cloud, or Azure environments. These services are not supported at all, but my customers and coworkers expect them to be.

