What is our primary use case?
We use it to enforce maintenance tasking orders or time compliance network orders that are passed down.
How has it helped my organization?
We can do a lot with Forescout. We use it to quarantine non-compliant machines. We use it to mitigate vulnerabilities. We can push patches, and we can push scripts through Forescout. For example, if we need to know how many Windows machines are using the 10.9 image or whatever, we can look that up easily.
What is most valuable?
We like pretty much everything that it does. Vulnerability remediation is valuable. We can narrow down a system and its properties. We can go granular on the properties of each endpoint, such as which operating system you're using.
What needs improvement?
Logging would be one area for improvement. When we're troubleshooting, there are not a lot of clear things on Google that we can look up for ourselves. When we have an issue with it, we have to call the company to get the vendors involved. The logging of Forescout is horrible compared to other things that we've used. We don't use ISE, but based on what we heard from the users we've reached out to who do use ISE, the logging capabilities of ISE are better, and troubleshooting is so much easier with ISE than it is with Forescout.
It doesn't have a lot of end-user support after the purchase of the license. There is no training either for Forescout. That's something that it's lacking. We need refresher training. The vendors came out and trained us whenever we first set up Forescout, but we have people coming and going all the time.
There are some things that we wish that it would do. We use ACAS, which is a reporting tool that scans our network and then lets us know what kind of vulnerabilities are on the network. It would be nice if there was a way to connect Forescout. I know ISE connects with our configuration management tools to push patches and things like that out to a large array of machines. With Forescout, we can push some patches out, but it can't handle anything on a large scale. So, we wish that Forescout would be able to handle more and connect to some of the other tools that we use. We have 15 different tools that do pretty much the same thing but in a different way to get a good picture of our network. It would be nice if we can condense that down or have something that is a central hub-type tool that can reach out to some of our other tools, compile the data better, and have that data in one place.
For how long have I used the solution?
We've been using Forescout for probably four years.
What do I think about the stability of the solution?
It's pretty stable. We had some unexplained issues. We lost our ability to authenticate. So, about 30,000 phones went down. We had to get the Forescout vendors in here to figure out why that happened, and then we sent the logs up, but I don't think we got any clear answers on why it happened.
What do I think about the scalability of the solution?
I'd like to see Forescout play well with some of our other tools to be able to link up.
In terms of its usage, from what we heard, there are around 14 bases that are using Forescout currently. For its maintenance, just one or two people are required. When you get too many hands in a cookie jar, you end up having problems. So, we got a couple of people in here who know Forescout and dig into it. We have a few people who just have read-only accounts. They go in and look up things, but they can't make any administrative changes.
How are customer service and support?
When we had the authentication issue, they were already in the area. So, we got lucky when we called them. They don't offer a lot of vendor support, but one of our guys is Forescout certified and about to get out of the service. They're trying to recruit him onto their team. Anytime he calls, he can get a vendor here. The vendor will actually make a detour if they're somewhere else. If they're flying, they'll fly here to help us out with our Forescout. So, I can't say from an unbiased perspective how they are with other customers, but for us, anytime we call the vendor, the vendor will come and fix our stuff, but we're a unique case because we are a government organization.
How was the initial setup?
The initial setup for Forescout is complex if you don't know anything about it. It took a couple of weeks to set it up. We were a test base, so we had the vendors out here setting it up. They did all the training and everything with us. It took a couple of weeks.
What about the implementation team?
Forescout came out and helped us with its implementation.
What was our ROI?
We have seen a return on investment. It has helped us out with what we need to do. Our main job here is to make the network more secure by getting after our vulnerabilities and everything else. It has definitely helped us, especially with the quarantining machines and helping out with some of the vulnerabilities. The ability to push PowerShell scripts and batch scripts through Forescout is key because we can target vulnerabilities through scripting. So, it's definitely worth it as a product.
What's my experience with pricing, setup cost, and licensing?
It's about $160,000, but I'm not sure how long that is for or what it includes. Because we were a test base, we were provided with servers, but now, Forescout wants us to buy servers because those servers are now end-of-life or end-of-service. For our lifecycle management program, in order to get a refresh on those servers, we would have to buy servers or use our own network resources to house Forescout. Forescout takes up about 13 or 14 virtual CPUs. The RAM and other things are quite similar to ISE. I don't know if it's as demanding as ISE, but the hardware and software requirements for both products are quite similar.
ISE is probably more expensive. Our network is about 22,000 endpoint devices. So, three years with 25,000 endpoint devices with ISE was about $363,000. With Forescout, we're only paying $160,000, but I don't know if that's for a year. I know the last time we were provided Forescout licenses was probably four years ago, maybe even longer. We had purchased it, but the people who were involved in setting up Forescout had left and gone to another assignment. We didn't even know that we had Forescout. The servers were sitting on our server floor for probably a year and a half before we were finally like, "Hey, what's this?" We dug into it a little bit, found the contract, and then we were able to contact Forescout and get the vendors to come out and help us set them up and get Forescout running. Because we spent about $140,000 last time, it's going to be $160,000 now, but I'm not sure if that's a four or five-year contract. I'm not sure how long that contract would be for.
What other advice do I have?
I would advise doing research on both ISE and Forescout.
I would rate Forescout an eight out of ten because it doesn't have a lot of end-user support after the purchase of the license. There are not a whole lot of training resources, and there is not a whole lot of troubleshooting help.
Which deployment model are you using for this solution?
On-premises