The tool's deployment is easy and takes four to five hours to complete. The deployment process has become much simpler with implementing a playbook or checklist. Upon receiving a new device, thorough testing and configuration are conducted.

The initial setup isn't too complex. We require some credentials from the cloud. It takes three or four engineers to do a PoC unless we're doing something critical where we need L2 engineers. 

We do not do anything in production. In a PoC, we initially focus on a specific area for the customer. You can take 50 or a few hundred people in a segment, and we will address those credentials before deploying at a high level in the next phase. They will do a POC or a test for a particular use case and then go through the same process at a higher level to deploy the solution in production.

Initially, I would rate the initial setup around a four out of ten. However, as we've become more familiar with the platform, I would now rate it closer to an eight out of ten. There was just a slight learning curve at the beginning.

FortiGate is straightforward to implement and configure. It doesn't require any special qualifications. You just need to practice it a bit, but it's not hard to understand. You can use a GUI or a command line if you prefer that. The command line isn't user-friendly, but the GUI is excellent. I would give the GUI a perfect 10, but I would only rate the command line interface six out of 10. 

The solution does require some staff to deploy and maintain, but it's not that many. African countries don't have a lot of people with cybersecurity skills, so it's challenging when we get an issue from that side. That's why we end up deploying a mobile hub strategy. We are supplying the skills that they may not have the branch offices. Four people are enough to manage the whole empire.

Setting up FortiGate Cloud is straightforward and simple if you have experience withcloud environments. The time needed to deploy varies depending on the size of the customer or project, and it takes some preparation. 

On our end, setting up Fortinet FortiGate was easy. It was not complex.

You can deploy the firewall in an hour without difficult requirements. You can set up the firewall in an hour. It's plug-and-play, ready to use.

The initial installation is straightforward. The time it takes for the implementation depends if you start building from scratch or not. However, it takes a maximum of two hours using two people, this includes the configuration, OS upgrades, and FCL configuration.

The initial setup is straightforward.

Our implementation strategy was to get the world's best cybersecurity, perimeter firewall. We searched the internet to find this and we selected FortiGate. It took a maximum of one month for the implementation. It was not very challenging.

FortiGate is quite user-friendly. It's not that complicated.

The initial setup is not complex. 

A configuration takes about 30 minutes to restore and deploy.  

Most of our customers prefer to deploy the solution on Azure. The deployment and maintenance team consists of around eight technical engineers responsible. The process requires coordination between operators and engineers, with expertise ranging from web sharing to troubleshooting. It takes ten to thirty minutes to complete.

There is a learning curve, but on a scale of one to five, with one being almost impossible and five being extremely easy, I would rate the setup process as a three or four. We deploy new firewalls for our customers using this solution about once a month.

Fortinet FortiGate Cloud's initial setup is not complex.

Fortinet FortiGate Cloud is very easy to set up. The initial setup for Fortinet FortiGate Cloud takes around 10 to 15 minutes. I rate Fortinet FortiGate Cloud a nine out of ten for its initial setup.

The initial setup was kind of difficult. We didn't do it. The company, our ISP, installed them and configured them initially.

It took two days to deploy everything.

We handle the maintenance. We establish the policy, and then only if we find something to fix, do we change that. If not, we don't touch that. We have four people capable of maintenance activities, one engineer, and three specialists.

It's very easy to maintain. You just go on the web, you click is there a newer software and they'll tell you yes. Then you're supposed to make a backup of your configuration file and then you download it.

The initial setup is pretty simple. You just sign up and select your licenses.

We didn't encounter any challenges during the tool's deployment. 

The initial setup was straightforward and pretty simple. It was not overly complex. It didn’t take long at all to get everything up and running.

The initial setup is not overly complex or difficult. It's pretty straightforward and simple. 

The solution is very easy to implement. It's not complex at all. 

The implementation strategy usually depends on the customer. It varies from customer to customer, depending on the requirements. That said, usually, it shouldn't take more than a couple of days.

Usually, first, we have to collect feedback or collect requirements from customers in terms of the different networks that they have, the policies, the allowed protocols, the disallowed protocols, the allowed content, the blocked content, et cetera. We will get, from the customer, a unique account for Active Directory, which is required for the user's onboarding. After we do the physical implementation, we start by implementing the policy and building out the policies. First, we will test them out during off-business hours. Then, if everything is working as expected, we move it to production, and customers can start using it.

One person is all you need to handle deployment and maintenance. 

When it comes to the initial setup, I have found Fortinet products to be quite easy.

Deployment is easy. The endpoints are modular and the installation pretty straightforward. Most devices come with a graphical user interface. It is GUI and is pretty easy to configure and deploy.

The installation and configuration of the solution is easy.

The solution is deployed on a private cloud.

The deployment process takes one or two hours.

Regarding the steps for deployment, we created an interface and then attached an IP to the interface. Then we created some ACL rules to connect the endpoints to the internet and created a VPN solution. We used the features of VPN in Fortinet FortiGate Cloud.

We need two or three people for deployment and maintenance.

I'm not the end user for these tools. However, I do know about the deployment. It's easy to set up and not complex at all. It takes three to four days. 

The deployment was handled by three people. 

Fortinet FortiGate Cloud's initial configuration is very straightforward. After the deployment, it does not take more than a week to have it fully configured and in production.

Setting up FortiGate Cloud is complex, but the Fortinet team completely set the solution up, so we didn't need to do anything on our end. They only gave us the username and password.

The initial setup is easy. Configurations take longer for large companies due to their complex infrastructures. 

It was a straightforward setup as we had a third party manage the process. 

The initial setup of Fortinet FortiGate Cloud is simple.

The initial setup is largely simple. The time it takes depends on the size of the site. The way we standardized the process for ordering is that we order the same things for every site. Same thing for every size site, and I think we have four that we typically use plus the big hospitals. Basically, there are five levels, and we order the level that's appropriate. We order any wireless that's appropriate, and then we have a standardized set up for that, for the three wireless types of service that serve our clients. Then, because they have one that's dedicated, one that's dedicated but not managed, and then one that's dirty and everybody can get onto it, because they're a hospital, and they need access. The management for the actual individual firewalls is set, and we basically copy that into each one, as we take it out. So it has a consistent setup at every single site.

The deployment depends upon the requirements. Generally, if there is a standalone infrastructure, and someone wants to configure Fortinet, then it shouldn't take more than one day. However, if you have multi-locations, there might be multiple dependencies or local issues and other stuff, and the configurations may be different. There may be some pools that need to get access from this to that. That might take a few more days. That said, from an implementation aspect, Fortinet implementation is much easier as compared to Palo Alto.

How many people you need for maintenance depends on the nature of the business. For example, in banking, you need 24/7 uptime. You need at least one engineer in a shift to manage the Fortinet devices. Otherwise, two engineers are enough - one for deployment, and the same person can also manage the firewall. Therefore, one to two engineers are more than enough to manage firewalls, Fortinet, the traffic, and to do whitelisting, blacklisting, et cetera. They can do the troubleshooting part and open the ports according to the application requirements.

For a system administrator, the initial setup is straightforward. I didn't face any issue configuring it. It was so easy. There are videos and tutorials, which helps a lot.

It took one hour for the installation at the cabinet and the wiring, approximately five hours for the full configuration for the VPN tunneling, and subnetting the IP.

The initial setup is relatively straightforward and took us a couple of days. We did it ourselves and once it was up and running, everything went smoothly. 

It's easy to set up the solution, and I would give it five out of five. In general, it takes about one to two months, and in our case, it took two months.

The initial setup is straightforward.

The initial setup was really straightforward, and deployment took no longer than half an hour.

The initial setup process is easy. It is already integrated into the cloud.

The initial setup of Fortinet FortiGate required a lot of stages over a few days. We installed it first on the cloud and checked in for the request. Once we were sure that we were rejecting suspicious intrusions and traffic we made the full installation for the cloud integrated with the local system at headquarters.

We have three engineers that are responsible for deployment and maintenance.

The Fortinet FortiGate Cloud installation was not a problem but we have some local laws which make some restrictions for deployment cloud solutions. A lot of our customers use the premise version, not the cloud. The full deployment is not in one day, because we need to agree on a lot of details with our customers and it takes time. A typical time of the deployment can take approximately two to four weeks.

Unfortunately, we bought this solution for our main customer, and we had some problems deploying it correctly because its features didn't want to work. We have a lot of experience to install FortiGate and Fortinet solutions. However, we have faced some problems with  Fortinet mainly. 

The initial setup was easy. 

The initial setup is easy. Provided that you have your requirements clear, it is not complex. If you do not have clear requirements then it's like any other technology and it will be complex.

If you have your requirements ready and you what you want to achieve then it's straightforward.

The initial setup is straightforward and fast if you have the Fortinet FortiGate Cloud infrastructure.

This initial setup is pretty straightforward. I don't think that it is complex.

The entire firewall implementation will take a couple of days, maximum. This is with everything, all together.

The overall setup was complex.

Initially the set up is not that easy. At first, you are familiar with the product and then it has some difficulty in setting it up.

It requires a lot of research before you can finally make it work.

The initial setup was straightforward. I didn't find there were any complexities.

Deployment only took a few minutes and then it was ready to use.

When the template is used deployment takes less than two minutes. What is nice about the template is that it provides FortiGate with load balancer capabilities, with the input and output rules relating to it. This will save time from being wasted on load balancing. In contrast, Azure requires that a load balancer be created between two or three VMs. The template provides all of these features, meaning that there is no need to do anything extra. It will create everything by default. The Azure template, not so much. 

The initial setup is not complex at all. I found it to be quite straightforward. We didn't have any issues with the implementation.

We have an internal team that handles the maintenance of Fortigate. We have 40 employees that deal with that aspect of the solution.

The initial setup is straightforward. I don't find it to be complex at all.

Once we went through the documentation and all of the other items, it might have taken a day or so to set everything up and deploy the solution.

It is easy to deploy.

The initial setup is complex because the customer is using several technologies, and it is a matter of security. A typical deployment will take between three and four months.

The choice of deployment model, whether public or private cloud, depends on the customer.