The initial setup was "in-between." It wasn't so complex, but it also was not so easy that anybody could do it. It had a learning curve, but the learning curve was not that bad. I tackled the learning curve by asking questions of my SE. He was able to give me directions about the best way to configure it.

The kinds of things I asked about were best practices around which categories to enable. I needed to better understand what all the categories were, and what they mean. The default settings were too rigid and we had to make some changes. The SE helped us to understand all the categories, which categories were redundant and which categories should be more relaxed.

We had a PoC deployment and then production. All together, they took about two to three working days.

Our implementation strategy was to set it up the way we believed it should be set up. We put it in a test environment and then realized that some of the categories were too restricted. We got on the phone and then made some changes to those categories. After a couple of weeks of testing, we put it into production. All the settings that needed to be enabled were enabled at that point.

The team that logs in, in administrative roles, includes about eight people, and I don't think they're in there that often. We're usually in there if there's a report of domains being blocked that shouldn't be blocked. For all intents and purposes, it is set-it-and-forget-it. It has been that simple. We don't go in there unless there is a very specific reason for taking a look at something.

For deployment, it was the networking team, so that everybody was aware of how it was set up. BloxOne doesn't require any maintenance because it's in the cloud and Infoblox is maintaining it.

The initial setup was fairly complex. We have a bit of a non-standard deployment and it was suggested that we take training prior to it when we're able to. So, part of that's self-inflicted, but going back to the documentation, some things are not as clear as they could be either.

Our implementation was done in a phased approach that started with a pilot that ran for a couple of months. In total, it took us approximately three months to deploy.

At the time, we were doing a hardware refresh so we implemented the BloxOne Threat Defense along with the new servers and ran it on them until they were rolled into the architecture of our NIOS implementation. 

The initial setup is pretty easy and straightforward. All we had to do was just create a device name with an IP address and then allow the firewall to communicate between the cloud and our on-prem hosts, which was pretty straightforward. Then, Threat Defense Cloud does everything else for us.

Overall, it was a pretty big deployment. It took about 30 days. There were a lot of components, like firewall policy, that just can't be done tomorrow. We have 30-plus devices that connect from our on-prem host into the cloud. Going through all the iterations of getting approvals and the normal standard stuff probably took about 30 business days overall. 

The initial setup is easy. We provide both cloud and on-premise solutions. The deployment takes one to two weeks.

The initial setup is very straightforward. It is a SaaS solution designed for cloud security. The on-premises part is easily implemented. It facilitates a complete migration for comprehensive use cases. It takes about a month to get everything migrated, with fine-tuning and thorough testing.

Deployment involves planning, testing scenarios, defining acceptance policies, and then gradually migrating small network parts to utilize them effectively.

I rate the initial setup a nine out of ten, where one is difficult and ten is easy.

The initial setup was fairly straightforward. It took us a day to deploy because we have 18 hospitals, each with their own setup. Each setup probably took around 30 to 45 minutes.

The initial setup is not a simple "click-click-next" installation. It requires some level of experience and technical know-how. So the installation process is quite challenging. 

The time taken to install the solution could be days because it is a project-based installation. So it's not like a firewall where you can simply set it up and start monitoring. It would involve several days or even professional services consulting, depending on the specific requirements of the customer.

We did have to do implementation on our side. We did it with professional services assistance. It was a bit complex. There was some back and forth on it. We had to get some network information, and we had to work around some unusual configurations on our Infoblox setup to integrate properly. There is basically an easy setting that probably works for over half of customers, but we were not able to use that, so we had to go through a more complex alternative procedure.

The primary deployment took about six to eight hours, which wasn't bad. For adding additional devices, we have a worked-out procedure, and it literally takes 10 to 20 minutes a device.

We implemented it as part of an overall system upgrade. So, it was basically an add-on to where we were upgrading hardware appliances and VMs onsite, and we did BloxOne as part of that.

For its maintenance, it is pretty much just me, and it requires very little active maintenance. Once it is set up, it pretty much runs on its own. It is very maintenance-free. It is essentially a web application, so it is run by Infoblox. They basically just check it every now and then.

The DNS and DHCP are actually not that complicated. They make sense. On a scale between one and 10, it is a five in terms of complexity. Since using Infoblox, I came to the conclusion that there is more inside of DNS than simply resolving a name into an IP address and the other way around. These are things that I didn't know before.

The preparation took us two months or so. The actual implementation was done within two days. We deployed all the DNS and DHCP systems, together with the Threat Defense, in a parallel way. Then, within these two days, we switched over from the old infrastructure to the new infrastructure, and kept the old infrastructure as caching-only systems. We then switched one server after another over to the new systems.

The initial setup was straightforward. The options for the appliances were clearly documented. The onsite logging is actually a virtual host in our network. The setup for that was pretty straightforward as well. There was good documentation.

It took basically one day to start communicating with the portal and verify that all the appliances were actually, in fact, sending data to the portal and their traffic was being inspected. It didn't take a whole day to set that up, most of the time was just, it was a few hours of setup and several hours of monitoring, just learning what to look for. But it was pretty straightforward.

The setup was horrible. About a year ago, Infoblox made us re-enroll all our on-prem DNS servers by a set date to a specific version, or it would stop working. I told my colleague, "Oh, here, we have to upgrade the servers and reconnect them to the CSP." That did not go well at all. 

That went so horribly wrong that we had to have three sessions with Infoblox support and start again. The overall upgrade experience was awful. That problem took us about a week or two to fix.

The initial setup of this solution is very straightforward.

In regards to on-premises appliances, the cloud solution is very straightforward.

With the internal infrastructure complete, the basic setup should be up and running in about an hour.

Infoblox BloxOne Threat Defense is very straightforward. The initial setup is easy, but it might be because I have been using it for a quite long time. The viewer is perfectly fine. Reporting is also fine. It is very easy to set up.

The deployment hardly took two days. It also depends on the size of the organization. If you have only four to five instances of DNS servers, four to five VM sets will not take more than two days. If you have a big setup, in which you have multiple instances of DNS, and you have physical appliances, it will obviously take time.

The initial setup is straightforward. It's not trivial or easy to implement it, but it's also not that complicated. It's somewhere in between. Deployment typically takes two to three days. You don't need more than one or two people for deployment and maintenance.

The setup was fairly straightforward. Deployment took about two days.