I like how easy it is to manage the filtering software from the web portal. It's super straightforward to set up my networking equipment with clear instructions. I like that it automatically blocks threats without me having to do anything. It also lets me remotely manage both of our locations and networks from the same portal with the same policies. Very useful for saving time setting up content filtering.
Google cloud is well suited to access and collaborate on documents where more than 2 people are required to contribute and in instances where feedback from individuals is captured on the document itself. If a team is working on an end of year report for funders, a few key members may need to finalise a report by offering suggestions that can be viewed and resolved by other team members. Housing documents on Google Cloud is the most appropriate platform I have ever used for tasks like these. If minimal collaboration needs engagement from just 2 individuals, it may be easier to simply email the information between each other, rather than using time to create a folder, ensure access control and upload the information to Google Cloud for collaborative input
Improved scalability: As an organization's needs grow and evolve, the software should be able to scale up and handle an increasing number of users and devices.
More granular controls: The ability to set more detailed and specific policies, such as the ability to block certain types of content for specific groups of users, would give organizations more flexibility and control over their internet usage.
Advanced threat protection: Increasing the software's ability to detect and protect against advanced threats such as zero-day exploits and APTs would provide a more comprehensive security solution.
This is exceptionally simple to utilize in the event that you are as of now utilizing Google Cloud Services or you are important for the Google Ecosystem as of now. I accept this is likely the primary goal of Google Cloud DNS, to give a more complete set-up of devices to Google Cloud clients. Consequently, I would rate convenience a 9.
When compared to Kerio Control we found Central Management of filtering to be much easier, it also allowed us to apply filtering to remote devices like laptops and had better logging. We found DNSFilter to be much easier to deploy then Webroot DNS Protection because Webroot required the Anti Virus to be installed before deployment was even possible, and reporting features were very lacking.
Amazon Route 53 offers almost equal or slightly more features than Google Cloud DNS; we selected Google Cloud DNS because the rest of our projects use Google Cloud Platform.
Also, since AWS is a bigger service provider, their pricing is also higher; since Google Cloud DNS pricing is better, we went for it.
We used to deploy Cisco Umbrella before switching to DNSFilter. I feel like you need an advanced degree to set up and manage Cisco Umbrella. Not the case with DNSFilter. You will save time and money by leveraging a very easy to use product.
