I like the management aspect of this solution. You don't want to have end-users tweak or set it themselves, so the fact that you could do it from a central point helped us a lot.
We really liked the vanilla flavor set up. It is stable as well.
I like the management aspect of this solution. You don't want to have end-users tweak or set it themselves, so the fact that you could do it from a central point helped us a lot.
We really liked the vanilla flavor set up. It is stable as well.
What I didn't find helpful in the version we used is the fact that all devices had to be on the same network for us to push through the encryption. With lockdowns and people working from home nowadays because of the COVID-19 pandemic, there's no way to deploy a solution in that manner.
It should be easier to classify documents that should be encrypted, that is, to create policies for documents that should be encrypted. Maybe, it should be according to departments as well.
Customization should be a bit more granular because nowadays, things are very dynamic. Environments are very fluid. So, the policies should reflect that.
In terms of the policies you can apply, there should be a bit more granularity to it, and it should be something that you can turn on and turn off as needed.
I had used Symantec Endpoint Encryption for three months. We used the version before the last version.
It is a stable solution.
For me, the initial setup was intuitive, but then again, I'd had experience with deploying software for 10 years prior to that point.
Back then, deploying software was not like what it is today; it was much harder. You had to do a lot more customization. However, I have a lot experience, so I wouldn't have been phased by any issue I may have encountered.
I'm in Nigeria, and we also serve Ghana, Sierra Leone, Kenya, and a bit of South Africa. Whenever you're deploying security solutions such as Symantec Endpoint Encryption, there has to be a lot more focus on sensitizing the people who are going to be affected.
We train the IT staff on how to manage it, but we don't train the end-users on what it involves and the advantages of the solution. We also don't inform them of the changes they may have to make in terms of their behavior, how they access data, how they use the data, etc. We need to let them know that it doesn't mean that they are completely secure. The biggest issue about security is human error. So, I think sensitizing the users should also go hand in hand with deployment.
I would rate Symantec Endpoint Encryption at eight on a scale from one to ten.
Its management is good, and it is also scalable and mostly stable.
Its decryption time needs to be improved. Currently, its decryption time is very long, and it takes double time than encryption. They need to work on that. Its encryption time is fine.
I have been using this solution for four to five years. I am using its latest version.
There are minor challenges related to the updates for Windows and Mac systems, but it is mostly stable.
It is scalable.
I didn't contact their technical support.
I would recommend this solution. I would rate Symantec Endpoint Encryption an eight out of ten.
The primary use case is for protecting accounts.
Protecting accounts.
We would like some advanced security protection features.
The stability has been good, so far.
The scalability is good.
The technical support is good.
The initial support was straightforward.
The solution has helped to increase staff productivity.
It is a good product.
We are currently working with companies in the financial sector which is why we are using this on-premises solution, because their compliance policies do not allow for cloud-based servers. Our clients are using the full encryptions. They're using Symantec Endpoint Encryption to secure their data. If someone loses their laptop, for example, they can wipe their disk and save their data from ending up with a third party.
I like all the features in Symantec Endpoint because they provide four or five features for end-users. They have three consoles for managing the data. Symantec also provides the licensing with the software. There is no need to enter the licensing or install files manually because it's bundled with the software. This is a good feature. Also, you get updates and other encrypted files easily. I also like the manage keys.
There is no need to add any features, because they are developing their own encryption methods.
Currently, all the software has been managed by BitLocker, but Windows does not suit every encryption management software.
There are many apps that do that kind of thing. All the features are there so I don't think that needs to be on encryption software. I'm working with some end point management software and they are managing the software and connections, what can be installed and what is restricted, etc... But more features need to be included in the encryption software.
I have been using Symantec Endpoint Encryption for one year.
Their scalability is good. They are using three consoles and have full-consoling end point users for our solutions.
On a scale of one to ten I would rate Symantec Endpoint an eight.
The following measurements were taken with a Lenovo Thinkpad W500 with 8Gb ram & running Windows 7 SP1+fixes. The CPU is a 2.5 Ghz core duo.
Whilst not intending to do a thorough controlled test, I thought it would be interesting to see what the effect of Symantec PGP encryption might be on I/O performance
Here’s my SSD before encryption
And here’s the same afterwards
Write speed has roughly been quartered whilst read speed is a little over half
Given this is an SSD the overall throughput is still decent, though this came with a significant increase in CPU – in fact this is now the limiting factor it seems, with the “System” (ie kernel) showing maxed out CPU whilst previously this CPU wasn’t noticeably high
With the hard drive the before measurements were :
Pretty consistent and average for a hard drive. Now adding encryption
Nowhere near such a bad effect – less consistency, but due to the lower data rates the cpu load was lower, and not so close to being maxed out.
This was all done on an idle machine – so the biggest impact will be heavy UI when the system is busy. I expect bootup to be quite a bit slower for this reason