We use it for web isolation. That provides an additional layer of security or an additional method for protecting the users at our company. At a high level, it's adding another security tool in the chain of controls that we have to protect our users against threats—in this case, via email.
Decreased our security alerts without impacting employees' work
What is our primary use case?
How has it helped my organization?
We have seen a decrease in the number of security alerts that our security ops team has to follow up on.
What is most valuable?
I can't say that there is one specific feature that is most valuable. It's the overall platform that is well-suited to our needs. It's something that is different from a lot of other products or platforms in the marketplace.
It provides a single console for security policy and management. That is somewhat important because we used to have other products where you would have to log in to individual appliances, devices, or clusters. Having one spot to log in to or one area to go to for doing different tasks and viewing data sources, just makes it easier from a user perspective.
Also, the fact that it's invisible to our end-users and doesn't affect their work is very important. Most companies don't want to have added friction or impact on their users.
In addition, the combination of user-friendliness for admins, and security for the organization, works well. As a cloud-hosted solution, it provides ease of use.
What needs improvement?
There are several features, such as supporting web technologies, that the company is working on implementing in the platform. There are a lot of backend web technologies in use on various websites, for example, two-way audio/video and WebGL, for which support may not be fully implemented in the product. That's an area where I could see them improving. Hopefully, in the long term, they will add some of these capabilities.
For how long have I used the solution?
I have been using Menlo Security Email Isolation for about five years.
What do I think about the stability of the solution?
Overall, it's very stable. I can't think of anything that sticks out in terms of being problematic.
What do I think about the scalability of the solution?
It's quite scalable and robust. Compared to other solutions I've dealt with, it's very much scalable. Because it's hosted with the vendor, the vendor adjusts as needed. We've had conversations about it and it seems like it's great at that.
How are customer service and support?
The solution's technical support is very good. We have support cases that we work with them on. They are very open to our partnership and working with us on feedback and features and support in general. Other vendors may not be as receptive and that's one of the things I definitely appreciate about Menlo.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We did not have a previous solution.
How was the initial setup?
The initial setup was relatively straightforward. The challenge for whoever is doing the deployment is more around the need to understand their own environment. It's nothing to do with the platform. Rather, it is the administrator's job to make sure they're aware of how their environment is structured and how it behaves, and its requirements.
The solution is hosted by the vendor. They take care of that part of it.
What was our ROI?
Generally speaking, we have seen ROI. Anytime you can reduce the number of incidents and tickets with a tool or platform, there's going to be some return.
What other advice do I have?
My advice goes back to having an understanding of the environment in which it's going to be deployed and being open to exploring different use cases for the solution.
I would give it a 10 out of 10, especially when I think of some of the comparable products that didn't have some of the feature sets that this has.
