We previously used an on-premise proxy or a secure web gateway, but our employees were forced to do hybrid work during the pandemic. To connect to the office, they needed to connect to our VPN, and by doing so, they had to disable the proxy. That introduced a security risk because turning off the proxy exposes us to clickbait risks and phishing. We needed a solution that would cater to our needs but close those risks. Menlo Secure Web Gateway was the answer to that because it's cloud-based, and it provides a web isolation feature compared to other products on the market. Right now, we're just looking at the private access and SaaS solutions. The solution is invisible to our end users, so it doesn't have any impact on their work or performance. As far as friction with users, it only exists because we have to replicate our authentication in the cloud as well. They have to log in using a slightly different domain name from what we have in the office. As far as internet usage or speed is concerned, it's been pretty good so far. This feature is very important because part of my objective when implementing information security is that the more invisible my tools are to the users, the better it is. The deployment model is SaaS because it's provided by Menlo. We are licensed for about 3,600 users, and we are deployed nationwide. We have a head office in Manila with about 2,000 users, and 1,600 users are deployed around the country. When users need to work from home, they can have safe Internet access from wherever they are.
We use it to secure the internet connection of all of our users, ensuring that they can connect as transparently as possible to all of the websites that are, of course, not hazardous. And anything hazardous is prevented as much as possible.
We are using it to protect our users as they navigate the web. It is their cloud service, and we have set up a proxy to go through their service. The way we have it configured is that our staff basically logs into the internet to go out and surf. We have integrated it with Active Directory, and the users just provide their credentials. We have a screen that prompts them for those and also reminds them of how to behave on the internet. I believe we can change that now, but that was the way we rolled it out years ago. It is a good reminder for our staff. Generally, we like it. We even updated the landing page for that screen earlier this year. It works well for us. Other than that, the users don't really notice it.
Open browsing of systems on the web from endpoints within our network that could be vulnerable as a pretty quick avenue to exploitation is the primary issue that we are addressing. What I like about the Menlo Security solution is that it isolates all that browsing activity well and away from our infrastructure, keeping all of the noise out. Therefore, if our security tools hit on something, then it is something worth looking at, not just a bunch of garbage. All our endpoints are designed to hit the Forcepoint proxies, then the Forcepoint proxy directs it out to the Menlo Security Cloud environment.
Menlo Security Secure Application Access
Menlo Security Secure Application Access makes zero trust access easy, giving users secure connectivity to private applications, including web and legacy applications. At the core of Secure Application Access is the Menlo Secure Cloud Browser, which fetches, secures and delivers the content for users.
In addition to providing simple-to-deploy, clientless ZTA, Secure Application Access and the Menlo Secure Cloud Browser protect applications from...
We previously used an on-premise proxy or a secure web gateway, but our employees were forced to do hybrid work during the pandemic. To connect to the office, they needed to connect to our VPN, and by doing so, they had to disable the proxy. That introduced a security risk because turning off the proxy exposes us to clickbait risks and phishing. We needed a solution that would cater to our needs but close those risks. Menlo Secure Web Gateway was the answer to that because it's cloud-based, and it provides a web isolation feature compared to other products on the market. Right now, we're just looking at the private access and SaaS solutions. The solution is invisible to our end users, so it doesn't have any impact on their work or performance. As far as friction with users, it only exists because we have to replicate our authentication in the cloud as well. They have to log in using a slightly different domain name from what we have in the office. As far as internet usage or speed is concerned, it's been pretty good so far. This feature is very important because part of my objective when implementing information security is that the more invisible my tools are to the users, the better it is. The deployment model is SaaS because it's provided by Menlo. We are licensed for about 3,600 users, and we are deployed nationwide. We have a head office in Manila with about 2,000 users, and 1,600 users are deployed around the country. When users need to work from home, they can have safe Internet access from wherever they are.
We use it to secure the internet connection of all of our users, ensuring that they can connect as transparently as possible to all of the websites that are, of course, not hazardous. And anything hazardous is prevented as much as possible.
We are using it to protect our users as they navigate the web. It is their cloud service, and we have set up a proxy to go through their service. The way we have it configured is that our staff basically logs into the internet to go out and surf. We have integrated it with Active Directory, and the users just provide their credentials. We have a screen that prompts them for those and also reminds them of how to behave on the internet. I believe we can change that now, but that was the way we rolled it out years ago. It is a good reminder for our staff. Generally, we like it. We even updated the landing page for that screen earlier this year. It works well for us. Other than that, the users don't really notice it.
Open browsing of systems on the web from endpoints within our network that could be vulnerable as a pretty quick avenue to exploitation is the primary issue that we are addressing. What I like about the Menlo Security solution is that it isolates all that browsing activity well and away from our infrastructure, keeping all of the noise out. Therefore, if our security tools hit on something, then it is something worth looking at, not just a bunch of garbage. All our endpoints are designed to hit the Forcepoint proxies, then the Forcepoint proxy directs it out to the Menlo Security Cloud environment.