What is our primary use case?
It is used internally in my company. The main purpose of DLP is to have full visibility and control over endpoints and network-attached devices.
How has it helped my organization?
DeviceLock didn't consume too many resources. There were no issues with device performance or anything like that.
What is most valuable?
The most useful feature is the control and limiting of users sending documentation. It works with classification. When you classify your data, DeviceLock identifies it and, depending on your policy, can notify you where the data is going and who's using it.
Another useful feature is applying controls for attached devices, like storage devices or removable media. This adds another layer of authorization and control. These are the most important email features to look at.
What needs improvement?
DeviceLock has been problematic and not very effective for us so far, maybe due to configuration issues. It was already in place when I joined and wasn't performing well. We need more control over data, which DeviceLock hasn't provided yet.
I remember they moved to Acronis from another company. There were features related to network traffic visibility, which could improve the DLP significantly. Other solutions already offer this kind of network visibility for data loss prevention.
They are limited compared to before. Some features were removed from the current version.
Policy management with DeviceLock was not very user-friendly. The IT team had to access two servers to make changes. The way the platform and solution are presented requires time to understand and get familiar with.
For how long have I used the solution?
I have been using it for more than two years.
What do I think about the stability of the solution?
It has been stable. We haven't experienced server downtime or anything like that.
I would rate the stability a seven out of ten.
What do I think about the scalability of the solution?
I would rate the scalability a four out of ten, with one being not scalable and ten being very scalable.
It is not very scalable. There are around 2500 end users. We are planning to expand the usage.
How are customer service and support?
The customer service and support are okay. When we contact them with a problem, they usually solve the issue or have a solution within two to three days.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We've tried others. Next year, we plan to implement Forcepoint, and we've also tried Cisco.
The first difference is network visibility. The other solutions offer better visibility and control over data on the network. They also have better integration capabilities, either with their own classification tools or by integrating with others easily. The third difference is in external storage controls. While DeviceLock offers them, it's missing some use cases that we need.
How was the initial setup?
The installation was medium, not too hard. We saw most solutions installed on two servers in our environment: one for the DLP and one for the database. So, I'd estimate a day or two for installation. Configuration is separate and takes longer, maybe a week or two, depending on the complexity.
- Integration into the existing environment: We dealt with it as software initially, a platform to be installed and then implemented. The configuration wasn't difficult. It was medium complexity. It was easy to integrate DeviceLock DLP into the existing security framework
- Deployment model: It's on-premises. We usually prefer on-premises, but we are open to going on the cloud.
What's my experience with pricing, setup cost, and licensing?
It's not cheap, but it's not overly expensive either. So, the pricing is medium-priced.
Which other solutions did I evaluate?
We are currently evaluating DLP products to replace the current one. Limited network visibility is the main reason. We decided to change to a different solution about a year ago because of this.
What other advice do I have?
Overall, I would rate the solution a six out of ten.
My recommendation:
Users should first focus on developing full visibility of their data. They need to determine if their data is fully visible and understand where their data resides. There are three types of data: data at rest, data in motion, and data in use. Users need to know the addresses of their data and categorize it accordingly.
Secondly, users should ensure that controls are applied to all wireless devices. For example, if a user transfers a file via Bluetooth and the DeviceLock DLP solution does not detect or disable this action, that's a problem. Any unauthorized data transfer is a problem that the DLP solution should control.
Another example is when users upload content to the internet, such as via email or file-sharing websites. The DLP solution must also provide controls over these actions. Otherwise, the DLP solution would be lacking in this aspect.
I hope to see these features in DeviceLock DLP because other DLP solutions are already providing them.
Which deployment model are you using for this solution?
On-premises
*Disclosure: I am a real user, and this review is based on my own experience and opinions.
