Cloudflare vs Forcepoint URL Filtering

• When you need a FREE and EASY TO SETUP SSL certificate on your page (if you don't have the locked locker icon when opening your page, you need it)
• When you want to obfuscate your webpage's IP (any connection will give the Cloudflare's IP)
• You need to speed up the connection for static content (it will not help database connections or dynamic content)
• IF your DNS isn't good (Cloudflare's DNS is amazing, quick, easy, and works pretty well)

Read full review

• It tracks user activity, which means our HR department has a tool to report on certain users' activities when their productivity vs. internet surfing habits are in question. The reports are pretty simple to create and view and the ability to export to Excel has been useful. The ability to automatically generate and email these reports on a schedule has been useful at times too.
• The ability to set quotas, such as users are allowed to spend 30minutes per day on Facebook or 30minutes a day on shopping sites, which displays the quota for the user when they enter such a site, has been a valuable reminder of our company policies for such activity.
• The ability to prevent certain types of protocols for certain groups of users, such as group xyz is not allowed on FTP sites, or only https, has allowed to consider and set security parameters for different groups of users.
• The ability to easily override any group policy setting for a certain individual if an immediate need for something outside the box arises has been useful. If a certain user is temporarily filling in for another person on vacation and needs additional internet access with less restrictions, we just call out that user specifically in the software and apply a different policy, then easily remove that the following week.

Read full review

• There is a huge jump in price between the mid-tier and enterprise solutions which is hard to justify for smaller businesses, or companies owning many small businesses.
• It is difficult to convert from a CNAME installation back to a DNS based one
• Setting up page-level caching with web workers is counterintuitive for simple websites

Read full review

• It needs the ability to measure bandwidth. I want to know how much a user is taking up. The fact that he/she has 17,000 hits doesn't help.
• Clients, Policies, Filters can be confusing. Maybe it's too complicated and can be simplified?

Read full review

• Uptime: With Cloudflare's website protection, we have avoided panic-inducing outages and downtime.
• Reduced hosting load: Cloudflare's CDN allows us to use smaller servers and greatly diminish bandwidth usage.
• Reduced domain renewal cost: Most of our domains could be transferred to Cloudflare, where domain renewals are as cheap as possible.
• Increased total website cost: All of Cloudflare's features aren't free, and they increase our monthly overall website cost. The protection and other features are helpful, just not free.

Read full review

• The websense filtering has helped us to reduce and eliminate productivity losses from some gaming and streaming services.
• We have been able to lower our liability from illegal streaming services and also adult content viewing (and also reduced the internet uses related to those services).
• The filtering service has helped us to prevent virus spread on the network and also helped as a layer to pinpoint affected endpoints, that had gone unnoticed by our antivirus solution. By alerting to those early infections, we can quarantine the device before the infection spreads or affects other endpoints.
• The solution has given the HR department reporting they needed when employees were under review without having to pull any local logs or have any local solutions installed.
• The hybrid client has worked well in a few remote offices, meaning we didn't need a separate proxy service to filter and protect that traffic.

Read full review