It's deployed on the cloud, but I wasn't involved in its deployment.

It was pretty straightforward. We loaded the client into Meraki Systems Manager, and then we were able to push it to all devices inside our network that had Systems Manager. It was pretty much three clicks.

We had full Meraki stacks as most of our network deployment. We were 100 percent cloud on our solutions. Umbrella sits in between our on-premises networks or between our users at home and between our cloud applications that we use at our clinic and office locations.

I wasn't involved in the solution's setup phase. I do the sales in my company, and the ones responsible for deployment in my company are from another sales team. In the past, during the initial years of Cisco, I was involved in deployment.

Regarding the ease of deployment, I am 100 percent sure that it is the easiest solution. Also, I have already worked before, even in Cisco Portfolio.

In my environment, the initial deployment was not as easy as we expected it to be. The delivery of the client in a Mac environment was not that easy, and the fact that we do not have a directory made things a bit more complicated. On the other hand, as soon as we were able to deliver the client, everything went well. We were able to deploy the solution in one week.

It was very complex because of a little bit of immaturity of the Cisco Umbrella solution in the beginning. All the features were not already enabled. In addition, we also had a moving target where we said, "We would like to have this, and we would like to have that," and when it was not there, we insisted to have it in. It was very difficult and challenging.

Our initial setup was very easy.

I was a hundred percent involved in its deployment. We had a couple of issues. The proof of concept was done without a lot of planning. So, there were some mistakes made along the way. If I was doing it again the second time, I wouldn't make the same mistakes. 

The default configurations have your baselines. Those are never supposed to get changed, and I changed and tweaked those for our proof of concept. After a couple of weeks, I had some additional guidance from the Cisco Umbrella team. You leave the baseline configuration, and then you clone and create a new configuration that sits in front of it. So, everyone gets the baseline, and you don't change that. If you want to change it, you make a new policy and then make the changes to that. If you change the baseline default policy and you make a mistake in it, you've to back that all out. If you make it in the new policy, in the worst case, you just delete it, and automatically everyone goes back to baseline. So, there's still a policy in effect. That was a training issue that should have been resolved. Now that I've done it, if somebody asks me, I would say that this is the way you've got to do it.

I wasn't part of the deployment, but it seems to be straightforward based on what I have seen. It requires a few adjustments to the firewalls and some integration, but it seems relatively simple. We needed to help the users working from home install the agents for Umbrella and AnyConnect, and this was also straightforward to deploy with Kandji, our MDM system.

After deployment, Umbrella doesn't require much maintenance because it's a SaaS application like Gmail. You don't have to do anything except the admin work, such as adding websites or categories. However, Umbrella uses an agent, so we need to update the engine. We can automate all these things, so the maintenance is minimal. 

Deploying Cisco Umbrella proved to be a hassle-free experience for us. Since our SD-WAN is based on Cisco Meraki products, integrating Cisco Umbrella with Cisco Meraki was an effortless process. This integration has enabled us to implement the first SASE solution in our organization, and the combined solution of Cisco Umbrella and Cisco Meraki has helped us to set up new offices in less than 30 days, which is a significant improvement compared to the five to six months it used to take us earlier. This has led to a remarkable enhancement in our deployment speed, which is truly amazing.

I was involved in its deployment although I had a technical team working underneath me. It was easier than Zscaler because Zscaler made us have two instances, one for staff and one for students. It was very complicated, and we had to route traffic in different ways. Being able to do it by DNS with Cisco Umbrella was just easy.

I managed the team that was deploying it. My role involved making decisions about what traffic and which groups of users we put through first, some early field tests, and things like that.

The initial setup is straightforward and only required one person. Setting up the solution usually takes between 30 minutes to an hour. However, the rules are always changing, so we never truly finish setting it up. We're always changing the configuration of the sites by blocking or allowing or adding new sites to the blacklist or whitelist. 

To change the local DNS settings to use the Cisco Umbrella service, we only need to make a few changes. If the computers are connected to Active Directory, we can deploy the configuration through Active Directory so we don't have to mess with anything else. The solution is based on the cloud, so we get a lot of detail and granularity in what sites the computers can access. However, if we want more detail, we can install a small agent on the computer so they can report to the servers.

The initial setup was pretty straightforward. The solution's documentation is great. My environment needed a little bit of customization to match the deployment configuration or documentation, and it worked fine.

One of the great advantages of Umbrella DNS is that it's really simple to deploy. It's easy to install, the users do not notice that it's there, and it doesn't interfere with your work. The simplicity and transparency are great advantages of Cisco Umbrella. Cisco could take Umbrella DNS as a good example and also improve on other products.

Deploying Umbrella is really easy. The initial deployment can be done in one to two days. More advanced deployment including creating policies is also quick and can take a few hours to two days because it is cloud-based.

You don't always have to deploy Umbrella live straightaway. Umbrella can be deployed in monitor or audit mode so you can see what's going. You can then use the data to create the policies. That is, you can deploy it without affecting anyone initially just for the visibility and then build policies on the back of it.

Testing is easy as well, which means that you can test the data you've gathered on a small set of pilot users.

There were two pieces of the deployment. One was the cloud deployment, which got us set up in the cloud to begin with. We also had gateways that were installed on-prem, in-house.

We were able to get the gateways up and running in about an hour. The cloud deployment was all done by the Umbrella organization on the back-end side. To deploy to the end users, all we needed to do is set up a policy that said, "This is what you use for DNS." Once that was set up, we were done. Deploying that was done in a group policy and that group policy was pushed in a matter of minutes. The entire solution was probably deployed in just a few hours.

I found it easy to implement. Cisco Umbrella has great documentation and great support teams, and implementing it was very easy for us. We just deployed the appliances, and we got through the initial basic policies. We were prepared to do it, so for us, it was very easy.

We were already using Cisco AnyConnect, and for us, it was a simple plugin. We didn't spend much time. We did some tests. We worked with a local French team, and after that, we deployed it. For us, it was very simple to deploy.

The deployment was straightforward.

The initial deployment could take a couple of days depending on the deployment model. Cisco Umbrella could be up and running quickly. You can instantly point your DNS servers to use Umbrella's DNS as its recursive DNS, and immediately, you'll be protected by Umbrella. You can take it further and get more granular controls by using AD integration, which can take a little bit longer. From an engineering point of view, it's a very light touch, which is unusual for security solutions. They're normally pretty complex. Cisco Umbrella, however, is a simple but powerful solution.

Given that it's a cloud-delivered platform, Cisco takes care of the upgrades. It requires a pretty light touch in terms of maintenance.

It was super easy. I'm a general IT person, and I was able to deploy it. I read the documentation, changed some settings, changed the DNS on my servers, and then rolled it out to the team. It was a pain-free implementation.

What a simple product. It's a fast deployment. Then, you can start designing how you want to do your policies and what you're going to block. But once we told them what public addressing they were going to see, within a few hours we would see them go green. We said, "It's already seeing the data. Let's start applying policies, and we can start controlling all this."

We deployed it by configuring local devices to redirect the DNS request to the SAS service Umbrella provides.

The solution is cloud-based. You just send your DNS request or your traffic to it. You can start with a monitoring-only mode. So for example, you can redirect the DNS request and start observing what Umbrella recognizes. Later, you can start defining the policies, setting up the enforcements, etc. You can very quickly get to the first results.

In our environment, it was straightforward and simple to implement Umbrella. We had SCCM for the end devices for mass deployment. Our domain controllers were connected to the server. The initial parameterization only took us three days. Currently, we are in the most difficult part of fine-tuning the solution so we can take full advantage of its features.

In the typical deployment model, we integrate it with, for example, the Meraki product line for using Cisco Umbrella directly within the Meraki dashboard. So, you can link it to an API. That's a nice integration. You're not having separate Meraki access points or Meraki MX. You can bring it all together in one place, so you've got a single dashboard. Typically, we've done that. In the bigger organizations, we have done deployments of the virtual appliances because essentially, you want to be able to identify individual users at that point. By using the VAs, you should be able to identify users on the network, and then you can deploy policies based on those user groups.

Cisco Umbrella can be deployed in minutes. In its simplest form, all you need to do is point at the Cisco Umbrella DNS servers, and that's it. It can be literally deployed in minutes. If you want to go to a different use case, for example, where you've got to deploy VAs, that's a bit more difficult, but there's something for everybody. It can be as simple or as complex as your environment requires.

It's continuously deployed because, if we wipe out a computer, we've got to put the agent back on it. If we have to put it on a Windows machine, it's easy. If we're trying to deploy it to a Mac through Meraki, it's impossible. The method of deployment for a Mac, and the features available in Meraki, are not compatible at all. Getting it to the point where you could deploy a Cisco product with a Cisco product would be beneficial.

It is easy to implement. It is not straightforward, but it is easy. It is easier than before. 

It is very easy to maintain network connectivity. For medium- and large- enterprises, it is not going to take more than a week or so to deploy the solution. Or, you can deploy it with fewer complexities in a couple of hours. Therefore, it is not that hard to gel it into your existing network. So, it works like a charm for us.

In our environment, all traffic was going to the data center. It didn't take us much time, or the complexity of the network wasn't much, so it didn't bother us to pre-plan its migration. We just had to change all our DNSs on the perimeter firewalls and point them towards Umbrella, and that was it.

We've had to deploy connectors across certain locations, but [in] all the locations we have a domain controller and that needs to be deployed on those domain controllers throughout all of our different places. I've done a couple of deployments. Most of it was already deployed just by the time I got here. 

[In] my experience of how deployment went, it was very easily laid out, very simple. The instructions were super clear. I didn't have any issues with that. As more of a newcomer to the entire industry, this has been much easier than I expected it to be. Umbrella, as a product, is very simply laid out, very user-friendly. I couldn't praise it enough for helping me out with my job. 

While the support [can] sometimes take a while, overall they're super helpful, they make it very easy and they make you feel like you're not doing anything wrong. They're super friendly and make everything super easy for you. Umbrella as a product, overall, is very user-friendly, as a newcomer to my company.

The initial setup is easy. There is good documentation. I can deploy it within a day or two. There's a page that shows you the health of the agent. It makes me more comfortable knowing that my configuration is healthy. 

I did the deployment myself. 

I work for customers, and this was set up by our internal IT department. 

The initial setup is not simple. It is quite difficult and cannot be implemented by everyone. You need to have some basic understanding of the product to deploy it. You need to understand DNS filtering and domain blocking and have a working knowledge of DNS and how it works. You should also have experience with virtual machines and VM detecting because Cisco Umbrella is on a VM. 

The initial setup is very straightforward. There is a lot of documentation available.

The initial deployment was straightforward.

The solution is on-premises but the management is cloud-based.

The solution’s initial setup is straightforward.

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup a seven out of ten.

Our clients deploy on public cloud, private cloud, hybrid cloud, on-premise, or SaaS.

I am an engineer and do the initial deployment for them and make tweaks until it works for them. 

The complexity of the deployment will depend on the client's requirements. Some of them have straightforward requirements and some of them are quite detailed. The implementation itself is fine but there can be details where we need to check the documentation and make sure we're following what they require. 

Customers use the Firewall Migration for the migration mostly from the ASAs. We do the ASA to FTD migration, which doesn't work well.

Two or three engineers are required for the deployment. The installation is done by different engineers.  

We also do the maintenance. So whatever we deployed, we also support. We do all the support requirements, updating and reviewing the deployment that we did. We do the config that is required. For example, for the migration, if we deploy something, we come back to review what we did because we want to make sure that the customer is more secure than it was before. So we just rerun the same configuration, trying to find out if there's a gap that we can fix and make sure that the customer is secure.

The initial setup is very easy.

The initial setup was simple. Deployment at our main sites took about three to four weeks. 

The implementation is easy.

The tool's deployment is easy; I rate it a nine out of ten. The speed of deployment depends on various factors, including our communication with other customer contacts.

The initial deployment is quite easy. It's internal, and with a few clicks, Cisco Umbrella can be up and running.

We just did one deployment through a virtual machine and that manages all of our routers and all of our users. We haven't had to do multi-site configurations or deployments. It goes towards the organization, uploads all of our users, and all of our statistics, and maintains things from there.

We did some testing. Network connectivity was a bit of a challenge at the beginning, but we were able to get the right help from Cisco. The POC probably took a month or so

One of the key aspects of Umbrella is the deployment. It takes a matter of just 30 minutes to deploy it in any enterprise and, as soon as it is deployed, it starts to work, so it is seamless. The benefits are realized immediately.

The implementation strategy is pretty straightforward. On the customer's existing hardware you just have to make the entries that will enable the connection to Umbrella and it starts to run. It's a single-person deployment, a single network engineer. That is the beauty of it; you don't require a huge team to deploy it.

Umbrella doesn't require any maintenance. All the updates happen automatically. The configuration is a one-time process.

It can be deployed on the public cloud and private cloud. These are two of the selling factors, although public cloud is more common. It's a multi-location solution but can also be used by a single headquarters. On average, our deployments are for 2,000 endpoints.

Its initial setup is very straightforward. It is a DNS redirect, so it takes literally about five minutes to configure it. The only thing that is tricky is going in and defining your policies, but that's what I call the evolution of the product. You start with simple monitoring, and then you refine it over time.

The initial setup of this solution is straightforward.

It is not really easy, but because we have experts with us, it was not complex for us. We did this in one month because it was really important to give good services to the users.

For organizations in which I have been involved, I start off easy and then proceed to compliant, since there is a need to ensure that one does not overly complicate his work. The deployment for each person is generally very difficult. We start with easy, at which point we are encouraged to have a good grasp of the technology, without which the entire environment will be locked down and nobody will be able to do anything. As such, I start with easy and migrate the customers to compliant over time. 

Cisco Umbrella is such a solution and can be implemented very fast and easily. All that we must do is redirect the DNS registers in their routers, or the active directory service of the enterprise that is going to use in Umbrella services. If you buy the service now, in two hours you are protected by the service because it's very fast to put in service.

The setup was straightforward and was easy to implement.

They have different setups. For example, you can integrate with the Cisco Firewall and I believe you can integrate with any platform with an agent, on each device. So, it really depends on how comfortable you feel with the setup. If you need to get more information and analytics, I believe it says the agent is the best way to go. The agent gives you every machine: for example, what has been blocked? What kind of security breaches have been attempted? Open DNS has defended this particular endpoint, but there are definitely many flexible, different integration methods to integrate a solution.

The initial setup is advertised as pretty easy, but we did run into some kinks. It shouldn't be that hard, it's just that we had some issues.

The initial setup is straightforward and there is no complexity to it. This is a cloud-based system, so just install it, mount it, and the policies get applied. The installation requires that you log into the portal using your ID, and then it just starts working.

I believe, for the most part, initial setup was straightforward. You just have to look around and set it up, link it to the device, etc. It’s not too difficult where you couldn’t just figure it out, but to be sure, we called support and they confirmed what we were doing. They even helped by showing us the policy setup area.

I was not a part of the installation and deployment.

I have not received any complaints, it appears that it was seamless.

The initial setup is very simple. We usually have one engineer per customer for deployment and maintenance.

The setup is not too complex. It's pretty straightforward. They make configuration and onboarding relatively easy.

Deployment only takes a matter of days. You simply deploy the agent to the active directory, to all the installations and you're done.

The initial setup is straightforward.

The initial setup is quite straightforward and easy, and the deployment can be completed in a matter of days. You deploy the agent to Active Directory, for all of the installations, and you're done.

For us, the installation was very easy. 

We had the option of using the on-premises device, which would give you better visibility, but we didn't use it. This choice made the installation very easy.

The initial setup can vary in complexity depending on the size of the agency, as well as other factors including what they already have in place.

Initial setup was straightforward. Any questions I had were already answered on the forums.

The initial setup was quite straightforward. When you subscribe to the Cisco Umbrella services they give you some public IPs. With these IPs you have a few options:

• You can copy these IPs and user features for the DNS and the communication will happen directly through the cloud. 
• You can install the VMs in your corporate environment having all of the communication through the VMs and the VMs will communicate to the cloud. 
• You can install a Cisco Umbrella application on your PC and install the external script that has the public IP for the DNS for the Cisco Umbrella.

The deployment strategy was straightforward, and it took approximately two days for deployment.

Because we had over two thousand users, we created a script on SSCM. This is a software center manager for Microsoft, making the script accessible to all of the users. This script changed all the DNS IPs to the Cisco IP addresses. Once this was complete, we installed the Virtual machines, which are the DNS proxies for Cisco Umbrella and we configured the public IPs for Cisco Umbrella. These were the only two steps that were required, taking two days for two-thousand-plus users. It was quite simple, but, if you had to do it manually, it might take some time having to do one at a time for more than two thousand users.

If you have some automation, it is quite easy.

It has a public cloud and it is like a hybrid type of deployment. We have umbrella VMs installed in our enterprise areas, in DNS, in our remote offices, and our main HQ.

These VMs, are like proxy DNS servers. They will save a URL resolution and has a policy-based engine as well. For example, if you are searching google.com or something that is being searched quite frequently, it will store that data, and it doesn't communicate to the cloud every time, giving you a faster response with limited cloud access.

Our service provider is Cisco. They have their Telos Cloud, hosting the Cisco Umbrella Solution.

After this deployment, you need to do quite a lot of fine-tuning because there will be many false positives blocks, especially if you're using the malware engine. It will keep blocking some ADME files that are used in your corporate environment, or if it's an in-house developed application, it will be blocked because the code of the application is not registered with the Cisco Umbrella Cloud, It will keep on blocking, until you whitelist that code and whitelist that UUID, just to have this application running.

Initial OpenDNS setup is straightforward if you have a static IP address and you apply the DNS forwarders appropriately. This is literally a five-minute-or-less change.

This solution was deployed across different locations for different users. 
We have six remote locations, and we have two data centers. It's deployed across all of those locations.

A couple of clicks that we have had it up and running. Cisco requires more documentation regarding to the basic configurations. That is what I can say. I don't think I'm expecting it from Cisco's side.

Deployment and implementation are straightforward for anyone going for the basic certificate for networking, meaning CCNS or CCNP security. The implementation resources are readily available for it. We don't think Cisco has a difficult deployment. Umbrella is very easy. Everything is straightforward. There is no need to Google much for every feature because there is a tab where you can go and configure them. One thing I would like to improve in Umbrella is to have a Linux client available.

I wasn't involved in that.

The initial setup is very simple, you can set up Umbrella within two minutes I would say. You just have to point the DNS to Umbrella and that is it. So it is very easy to deploy and set up.  

Actually, I am from the research team. We make the solution requirements, then the product moves on to the process team. Once I have made a solution, then the product team takes care of rolling out the implementation.  

As this solution is a public cloud solution, there is very little maintenance which the customer has left to do. The setup is relatively easy and it is very good for the client.  

The installation is pretty straightforward and it only took 10 minutes to deploy.

We require only one person for the deployment and the maintenance of this solution, who understands it technically.

Initial setup was straightforward. I simply downloaded the client, installed it on a host and that was it.

The solution’s initial setup is easy.

We have our experts to complete the installation. 

If you have the skills from a network point of view, then the implementation is not complex.

The initial setup was very simple because it was just the installation of agents on the system, and it can communicate with the cloud easily. It didn't give me any problem.

it was very straightforward.

The initial setup was not complex. It was pretty straightforward. We found it to be rather easy, from beginning to end.

The deployment times vary and depend on which Umbrella you use. However, we've found it should only take about a day to get up and running. An IT team can manage it. They don't necessarily need an integrator.

The solution doesn't really require too much maintenance. You probably wouldn't need a dedicated person to maintain it.

With a basic understanding of networking, implementation should be straightforward. For non-technical people, there is probably enough documentation floating around that basic configuration is possible for anybody motivated enough.

The initial setup was relatively straightforward. We had an implementation strategy and it wasn't particularly difficult.

The initial setup is easy. It took a day to deploy.

The initial setup was very straightforward. I did not have any issues.

The initial setup was pretty straightforward. It was simple. 

The initial setup is very easy. Even the integrations are very easy.

The initial setup is not complex at all. It's a very straightforward installation. In terms of the deployment, it hardly will take more than an hour to two. At that point, it is up and running. A company shouldn't have any trouble with the initial setup. 

That said, security is always an ongoing process. It's a security product and therefore there's always work to do with it.

The initial setup was quite straightforward. 

Deployment depends on the number of features and the degree of integration you're looking for. Deployment can take anywhere from 30 seconds, simply to redirect your recursive DNS service, up to several days for a full-blown enterprise setup. So it depends on the use case.

The initial setup of this solution is not complex. It is easy to configure and use as a whole. The deployment took approximately one day, which involved configuring the access.

One person is enough for deployment and maintenance.

The initial setup is a simple process. If you build on-premises, the deployment will take half-an-hour. If you build on the cloud it is like 10 minutes. it could be even less than 10 minutes. It is really fast. It will take five minutes to sync to the endpoint, to the cloud, and to collect the data. The syncing is what takes the time.  

I have gone through the documents for Cisco Umbrella. So I have been deploying the product myself without the help of a technician and we are doing the implementation on our own.  

The initial setup is straightforward.

Initial setup was easy; just forward your DNS.

Initial setup was straightforward for the most part, but it can become complex depending on the granular content filtering features that need to be implemented for each client.

I wasn't involved in the initial setup, so I can't comment on that.

Implementation was straightforward with minimal changes to existing infrastructure.

The initial setup is traightforward. There is no complexity in the setup. The setup took minutes only.

Initial setup is simple, although some pre-requisites were not communicated to us, and they can make the final solution a bit more complicated.