What is our primary use case?
To deploy it as a proxy, we use this solution for content filtering, URL filtering, and solution filtering on the user end.
When the user is connecting to the internet and should not access some social media website or malware sites, we can block it through SonicWall CFS. CFS is our content filtering solution.
What needs improvement?
It has to be able to control more than just web traffic.
Malware, scanning, capture, and integration should be included with the content filtering.
For how long have I used the solution?
We have been using the latest version of SonicWall CFS in the last year.
What do I think about the stability of the solution?
It is very stable. It's reliable.
What do I think about the scalability of the solution?
We have 10 employees in our organization who are using this solution.
How are customer service and technical support?
I have not contacted technical support.
Which solution did I use previously and why did I switch?
I have worked with ContentKeeper, Gateway as a proxy, and Blue Coat as a proxy, but SonicWall is much more reliable. It is much more stable.
How was the initial setup?
The initial setup was not very straightforward, but it was easy.
It is a very simple setup. It is very easy to deploy, configure, and implement.
What's my experience with pricing, setup cost, and licensing?
Licensing is on a yearly basis and the pricing is very reasonable.
Which other solutions did I evaluate?
We have evaluated ContentKeeper and another solution.
What other advice do I have?
I would recommend this solution if they are going to procure any type of URL filtering solution.
I would rate SonicWall CFS a seven out of ten.
Which deployment model are you using for this solution?
Find out what your peers are saying about SonicWall, Barracuda Networks, Forcepoint and others in Web Content Filtering. Updated: July 2021.
522,281 professionals have used our research since 2012.