We have two main use cases: wired networks and wireless networks. In the wireless scenario, our main focus is on authenticating users to ensure compliance before granting access to our private network.
We use the Forescout Platform for device visibility and control in our network. It's very helpful for tracking malicious or unusual activity. We use it to track which ports are open, which machines are running specific services, and to identify vulnerabilities. For example, there was a vulnerability related to SMB, and we could use the product to determine which machines inside our organization were allowing SMB traffic.
The tool's most valuable feature is its ease of configuring and controlling endpoints, particularly in building policies for endpoint management. Its interface is simple to use and offers good visibility.
When compared with other solutions, the Forescout Platform's standout feature is its ability to integrate with various systems. This capability is particularly valuable as it supports the implementation of a zero-trust architecture. We are currently in the process of constructing our zero-trust architecture, wherein the tool serves as a pivotal component.
The solution's compliance capabilities have indeed been very beneficial for our organization. Unlike other solutions, it allows us to implement controls swiftly. Typically, transitioning to a blocking mode with other solutions would take around six months. However, we achieved this with the Forescout Platform within just one month.
The product needs to improve its support. I know a case that dragged on for about one and a half years. They eventually suggested professional services and closed the ticket. We followed their advice, engaging the account manager and professional service team, only to discover that the issue was a bug. After reopening the case, it's been about six months, and the problem still hasn't been resolved.
Forescout Platform's support often takes a long time to respond to tickets. Even after we reply, there's another lengthy wait for feedback, and their responses sometimes seem to delay resolution with unnecessary questions. For instance, they might ask for details about previous issues. Meanwhile, competitors may offer temporary solutions but often lack or are unsatisfactory regarding technical or research and development support from Forescout Platform's team.
Another area where it can improve is when dealing with multiple sites and overlapping subnets. While it works well for individual sites, it struggles when managing several sites with overlapping subnets, especially with authentication portals.
I think the Forescout Platform could use some extra features or improvements in the future. Specifically, it could be better at working with other security tools. For example, when it connects with VPNs or security scanners, it could work a bit better. The tool has already made some efforts in this area, but I think it could do even more to make these devices work together
I have been working with the product for two years.
I rate the product's stability a ten out of ten.
My company has 800 to 1000 endpoints and approximately 500 users. I rate the tool's scalability an eight out of ten. Forescout Platform is fully operational in our company, managing all our devices. We plan to use it more in the future because we're setting up a zero-trust architecture. This will allow our staff to work remotely, even from home.
I have used Cisco before. When deciding which product to switch to, we picked the Forescout Platform because it was more stable and easier to upgrade.
I rate the tool's ease of deployment a ten out of ten. It is easy to manage and implement. With the help of our partner, it took about one to two weeks at most to deploy this solution. This includes setting up the policies, implementing them, and ensuring the product is operational. Building the policies initially took around two to five days. However, refining and enhancing the policies took approximately three weeks in total.
We required a team of one senior engineer and one regular engineer to deploy this solution. The regular engineer was primarily responsible for implementing the Forescout Platform. In contrast, the senior engineer was involved in specific areas, such as integration and troubleshooting issues during deployment.
We currently only need one engineer for maintenance. The solution is mostly up and running, requiring minimal intervention. On average, the engineer spends about five minutes daily checking for issues or addressing complaints.
I rate the overall product an eight out of ten.