We have on-premises as well as public cloud environments. We have Azure, OCI, and GCP. 

Its initial setup is straightforward. It takes a little bit more time the first time because we have to set up the subscription, etc. Next time, it takes only around four hours.

There are limited options with FortiWeb, and there's not much you can configure incorrectly. So it's easier in that sense – you go next, next, next, and it works.

So, the initial setup was pretty easy. I would rate my experience with the initial setup an eight out of ten, with ten being easy to set it up. That's really what I like about it.

In my understanding, I'd position FortiWeb as a first line of defense, a tier-one solution. It would remove all the known attacks easily. I set it up once, and it handles probably 80% to 90%of undesirable traffic. But then, for the remaining ten percent, where specialized attacks require more tailored protection, I'd need a second line of defense – something more specialized. 

It passed all the standard attacks; now I need to detect those malicious actors who are deliberately trying to stay under the radar of published detection mechanisms.

That's something FortiWeb could improve upon for advanced users. And it's really about advanced features for specialized applications or specific business models. It's for those companies where they need deeper protection.

I initially deployed a lot of the applications. It was so quick and easy. FortiWeb took about a week to deploy, including assessment and testing. We had to create a new environment. Much of our on-premise infrastructure was closed off in the past, so we required no WAF for regulatory compliance. 

To create this new environment, we onboarded some new services that were classified within the scope of PCI. They were deployed in the old way with firewalls. However, our QSA said we needed to have services behind the WAF, and we were being assessed in a week. We had to find and deploy a WAF before we were audited. 

I have a team, but I and one other engineer were involved in the deployment. After the setup, FortiWeb requires minimal maintenance, which is one aspect we like about it. We've occasionally had to open a support ticket for the odd bug that's come up. There's typically no maintenance on our end. I can't think of a time when we've had issues with availability from FortiWeb. 

The initial setup is very easy. 

Initial configurations take a maximum of four hours. 

I have done on-prem, hybrid, and cloud deployments of FortiWeb. The deployment was straightforward for most features, but a few features require some customization and configuration in the console. That's where we ran into problems because the documentation isn't thorough in some areas.

It takes around three or four days to deploy FortiWeb for a simple website. It takes longer for a complex website, but it depends on the level of complexity. We deployed FortiWeb in-house with two people and some help from Fortinet support. It's deployed across multiple data centers and locations.

There was no initial setup because it's a SaaS solution. We only needed to configure it for our environment. The configuration was straightforward and only took a couple of hours. The only maintenance required is updating the templates. 

I did the initial setup, which was very straightforward; the process includes putting an instance in the cloud and then adding the URLs of the domains to the template. The initial deployment took under two hours, but we needed to spend time reconfiguring the template later to reduce the number of false positives. One staff member can complete the setup, and it only requires basic knowledge.

Outside of updates and the initial reconfiguration, the solution requires minimal maintenance. 

The initial setup was a piece of cake, done step-by-step. We just had to add some DNS entries and that was about it. It tells you exactly what you need to do. I didn't need to contact support or ask for any help.

There were a lot of additional modules that I wanted to check out and that took a little bit of time. But getting a basic setup running was very quick.

There is no maintenance involved.

The initial setup is easy. It's not overly complex or difficult. 

It can be deployed in about half an hour. It doesn't take long to have it up and running. 

The installation was straightforward and it took us approximately one month. There are a lot of services, approximately 15, and other parts to configure.

How easy or difficult the implementation is depends on the deployment type. It is very easy if you employ reverse proxy. However, it can be a little complex depending on what you need to do. 

There was a team that helped deploy the solution, however, for maintenance, you only need one network security engineer.

The initial setup was a bit complex for us because we were new to the solution. 

Technical support helped and trained us so we now handle setups with ease. 

It was fairly straightforward. It was fairly easy to implement, but the documentation with some examples might have made it simpler. Overall, it was fairly easy to get the initial implementation in place and get things worked out.

The initial setup is straightforward, it's a matter of choosing the architecture, the deployment mode, and configuring. Deployment time depends on the client's application. If it's a matter of one or two applications, deployment can take between two or three days. If there are many more applications that require protection, it can take over a month.

We had some difficulties at the beginning in terms of setting it up. It was a very new product for us. We never had web protection firewalls before. We had some support from our supplier, so we referred to the initial implementation to get it done with external support.

I'd rate the ease of implementation at a three out of five. 

From a technical perspective, the deployment does not take a long time. Our problem internally was the organization and the planning as well as the communication with the other teams. That's what took so long. We started maybe one and a half years ago with the implementation and productive status was reached at the end of 2021. That's a long time. That said, one would say the management is at fault, not the actual technical staff.

At a cluster, so single point of failure, all this stuff, it kind of took around 24 hours to get it up. The offline time was very difficult, however.

We have two good people on staff that can handle deployment and maintenance. We are looking for another employee in the market, however, it's been very difficult to find someone.

The initial setup was not straightforward. You need an expert to set it up with you and to configure it for you. I think the more you work with it, the better accustomed you are to it. The initial setup did not take longer than a week.

The deployment was done in a team of three people.

The implementation took about two months. It's not so hard to set everything up. It's easier than, for example, F5, to set up.

In terms of maintenance, for WAF, I need about three people to handle various tasks. 

In general, the initial setup is easy, and I would rate it at four out of five.

The initial setup depends on technical knowledge.

In the initial setup of Fortinet FortiWeb, we wanted to deploy it with WCCP mode, but we cannot do it because of the limitation with our Cisco ASA firewalls. It's difficult to integrate with FortiWeb. It is difficult to integrate Fortinet FortiWeb with other vendors other than Fortinet solutions. We cannot integrate it into our existing Cisco Firewall environment. We had to change the system to true transparent deployment mode.

The initial setup of Fortinet FortiWeb was easy. The full implementation took approximately one week.

FortiWeb's configuration process is more difficult than Sophos. I rate the process a one out of ten.

The initial setup is very straightforward. It took about 30 to 40 minutes for one web application for default settings. If you want to go with complex settings, then it would probably take three to four days to understand the application backend and everything else.

The initial setup We Fortinet FortiWeb is straightforward. The full process of the deployment took approximately two weeks to 16 days.

The initial setup was not complex. Like all Fortinet devices, it is user-friendly.

The initial setup is complex and takes between three to six months.

The initial setup has a moderate level of difficulty.

We only need one person to deploy and maintain the product.

It takes about a week to have the entire solution set up.

Setup for this solution is easy, with one being easy and five being hard I would rate it a two out of five. Deployment took a few days. 

We found the initial setup to be easy. It's straightforward. It's not complex or difficult at all. A company shouldn't have any issues with the setup at all.

The installation and deployment process is fast. It doesn't take more than a day.

We have two engineers on staff that can handle deployment and maintenance. 

I think it's quite complex because we need to know how the application works.  

The initial setup is straightforward.

Any FortiWeb deployment needs about two weeks because when it is first implemented, in phase one, machine learning takes place. It is needed because every application needs some customization. FortiWeb needs approximately two weeks to build this profile. After that, an expert will do some fine-tuning on the profile and the appliance will start to work.

It is complex to set up in learning mode. It takes a lot of time to learn the pattern of the web application before we put in the rule. The rule itself is a bit complex. We had to go by trial and error because there is nothing standard on the device.

The deployment took almost six hours to get up and running.

The deployment was very easy. Since it concerns hardware, one only need plug in the firewall and bring it up by connecting the device. It is pretty easy and not time consuming. The deployment takes, perhaps, one hour. But, the configuration and machine learning are important. 

It was quite easy to do the initial setup and apply basic rules. Administratively, keeping an AWS firewall and applying the Fortinet rules made it quite simple for the difficulty level of this particular requirement.  

The initial setup is not simple for all the products. Some Fortinet products vary, but overall it is straightforward.

The initial setup was straightforward. The deployment didn't take much time. The support guys were really good. The transition from Cisco to Fortinet was a bit challenging but they had tools to make it easier. 

We require three staff for the deployment and maintenance. 

The installation of Fortinet FortiWeb is straightforward. The time it takes to do the installation depends on the environment of the customer and if there are any additional configurations needed. However, a typical basic installation takes approximately one hour.

We had a complex environment, with multiple offices across the globe with all the data in and out from our HQ.

The initial setup was straightforward, it was easy.

There were no issues and it was deployed in six months.

We have a team of 20 providing the IT infrastructure, including switching, firewalls, and maintenance.

Initial setup was straightforward.

Initial setup for what we need to use it is very straightforward. There are certain features (such as TACACS) where you need to use CLI, but most things can be done with the GUI.

The initial setup was quite straightforward. The GUI is user-friendly and it's easy to understand how to manage it. We used an expert to finalize the last 10% of the configuration because we wanted specific settings regarding the security. We knew what we wanted to block and we needed an expert for the specific rules. Otherwise, 90% of the setup was done in-house. 

The deployment only took two to three days. We only needed one employee to install it. 

Selecting the appropriate deployment topology is a major task. Initial configuration settings are little difficult to implement but overall management is easy.

FortiWeb provides a wide variety of deployment options such as

• Reverse proxy
• Inline transparent
• True transparent proxy
• Offline sniffing
• WCCP (Web Cache Communication Protocol)

It depends on the customer and the use case. Usually, it's straightforward, but as you add more applications, it can become more and more complex.

The deployment duration varies. Usually, designing, building, and putting in production take about four weeks, but it also depends on the application type.

It requires maintenance all the time. Everything requires maintenance. Usually, we build it and operationalize it, and we then hand it over to the customer.

It is straightforward, but we still need good training.

The initial setup was not easy but not exactly complex.

We maintain the system ourselves.

The initial setup was rather straightforward because we had some help setting up the unit in the first place. The initial setup, if you're using a VM, is really easy to roll out, if you know the Fortinet command line. It's not easy to configure an IP address and get it started. Then there was a rather steep learning curve in what you exactly have to do to have a really secure solution. It's rather easy to make it a reverse proxy and do nothing, but to get it monitoring in the right way, it takes some time. You have to think about it.

Deployment was a one-time setup. I think it took us about two days including one solution for configuring. For now, there is a new solution we need behind FortiWeb, and I think it takes about four to eight hours to set up. We require just one staff member for maintenance.

The initial setup is straightforward, the deployment took us about two hours. We currently have 16 users. 

In our data center and with the complexity of it, it takes one or two days to implement and fine-tune.

The initial setup was very easy. We use the proxy reverse schema; I think it is the best for almost all situations. The last firmware 5.5.x permits customers to deploy in different configurations in the same box.

Even from the early days, Fortigate/Fortiweb was easy to set up. It had an ugly interface but it has been improved every year. 

The initial setup is very simple to configure. Our customers are very happy with that.

The time it takes to deploy depends on how deep our project is. Sometimes it can take a week and sometimes a month. Minimum a week though.

Initial setup is not very complex. But if we have problems with configuration, we ask support.

The installation is easy. It takes one day for the implementation, and after 14 days one day for tuning.

Some customer needs to go to production fast, it can take me one day for the installation, and after seven days I can do the tuning quickly.

It was straightforward for minimal configuration and requirements, CLI for complex configuration.

The initial implementation is simple and the configuration is straightforward.

Very complex. More security features.

Initial setup was straightforward and easy to manage.

It has an auto-learn module that makes it easy to establish the first policy, after which you can customize it. It is straightforward to configure the FortiWeb. We have encountered that it is especially difficult to work with URL rewriting, because of regular expressions.

The initial setup is straightforward, although integration is more difficult. For example, if you want to have DDoS attack support then you need to integrate with the firewall. With the solution from Barracuda, the DDoS capability is already included.

A little bit complex, as understanding the GUI arrangement and terms took more time and effort than we expected.

The installation is easy and straightforward, and the timeframe depends on the application

I don't get involved in implementation and installation.

The initial setup was straightforward.

It takes less time to deploy compared with other competitors.

One person is enough to maintain this solution.

Initial setup complexity depends on the network. The admin console is easy to use.

Generally, the solution is easy to set up. It's not overly complex. 

It was simple and functional.

The setup for one application is sort of complex but based on the automatic profiling, they're learning. You are provided with a set of policies that meet best practices and security recommendations, so you are good to go in a very short time.

The initial setup is straightforward and the deployment can be completed within a couple of hours.

The initial setup was straightforward.

I would rate the setup as five out of ten.

Initial setup was very straightforward and simple.

Initial setup is straightforward, and it is not too complex.

It's very easy.

Initial setup was not that difficult. It was different to my previous solution; I could do it on my own.

Initial setup was straightforward.

The initial setup isn't too complex. It's pretty straightforward. The product has a model deployment. You just need one port. After that, access is simple.

The deployment and installation took about one day. It is pretty fast because the setup is pretty easy to execute on.

For deployment, you just need two people. You don't need a bunch of staff to handle it.

We have not had any problems with deployment.