What are the major differences between Adallom and Cloudlock? Both solutions offer similar services but in terms of ratings, Adallom seems better.
Where is Cloudlock lacking in comparison to Adallom or SyferLock? If considering a Enterprise level deployment, where does Adallom have an edge and where does Cloudlock?
Regards,
Rahul
I prefer CloudLock over Adallom (I work in the Cloud Security Space with Okta ), for both strategic market reasons and technical reasons. Our experience with CloudLock has been much more positive and collaborative. In our dealings they seem to have more customers.
In terms of approach, both companies are very different. While Adallom is a CASB product, for CloudLock CASB is a subset of the addressable markets they’re going after.
Adallom's perceived strengths are their flexible deployment options, future resources of Microsoft, and analytics. Negatives include a potential focus on Office 365 post-Microsoft acquisition, lack of capabilities to handle cloud malware, lack of quarantine and encryption, and generally broad capabilities that aren't very deep. Adallom also recommends starting with their API capabilities before moving to a second phase that includes installing their proxy. Very few customers have reached that point, so are left with an API solution that isn't fully-featured.
CloudLock's strengths stem from the fact that CloudLock is a platform, not ‘just a product’. CloudLock’s platform consists of what can be described as ‘security engines’ (e.g., User and Entity Behavior Analytics, DLP, Encryption, a firewall for apps) all exposed via technically-strong APIs. What that translates to is that CloudLock offers much stronger API capabilities (as an example, they can perform analysis at the object level in Salesforce, which no one else can), the ability to handle cloud malware, community-based trust ratings for cloud apps. In addition, while most CASB vendors focus on SaaS applicaitons, CloudLock’s platform offers code-less support for applications running on AWS and Force.com environments. CloudLock further offers the ability to embed CloudLock’s ‘security engines’ within any custom app running anywhere. CloudLock's lacks the proxy installation options that Adallom has, but is partnering with organizations like Okta, Check Point and Zscaler to offer support for ‘proxy use cases’ by leveraging customer’s existing proxies / NGFWs.
Overall, the industry is very much in "wait and see" mode with Adallom. They claim that they will continue to be a cross-platform CASB, but they are rebuilding their service on Azure and will likely focus very strongly on Office 365. For a cross-platform CASB moving forward, I'd strongly recommend CloudLock.
SyferLock is an OTP/Authentication solution, so not in the same space. Did you mean CipherCloud? If so, CipherCloud is an encryption gateway, so has a very different focus than both Adallom and CloudLock. CipherCloud does tokenization, key management, and has many DLP and compliance policies. They're also very complex, very expensive, and deployment can take months. They focus only on the encryption angle and don't have the full CASB capabilities that both CloudLock and Adallom do.