The initial setup is certainly straightforward because F5 Silverline Web Application Firewall does the setup for you. All that you need to worry about doing is routing your DNS via F5 Silverline Web Application Firewall.

If I have a website, I would just make sure that it routes via F5 Silverline Web Application Firewall DNS, and then I would only whitelist the traffic between F5 Silverline Web Application Firewall and my application pool. That's the only configuration that I need to worry about, unlike a traditional WAF that you need to set up. You can't just say that it is a strength of F5 Silverline Web Application Firewall because Imperva's WAF on the cloud, Incapsula, also works the same way. 

The initial setup was easy. The solution has good documentation for the initial setup. F5 also provided us with support.

The initial setup is very simple to set up. It's not overly complex. I found it to be very easy. 

On a scale of one to five, with one being difficult and five being very easy, I would give F5 Silverline Managed Services's initial setup a four. How difficult the deployment is will depend in large part on the experience of the person on the back end. I have about 15 years of experience in IT. My journey started with small deployments and eventually included the ISP. I have been working in Serbia at an intern service provider for eight years. In other words, I may not be the best person to judge simplicity because I have seen some complex systems. I would personally classify a F5 Silverline Managed Services deployment for a common enterprise customer as easy.

Deployment does require you to have knowledge of routing protocols that are not part of the F5 solution. That is the only prerequisite that you need to meet before you start doing something in the cloud itself. You need to understand how to steer traffic towards the cloud and that requires good planning.

If a customer is currently under attack, implementation can take three to four days. If a customer had been proactive and evaluating different solutions for DDoS before getting hit with the attack, deployment could take maybe three weeks, but there is no need to waste more time than that. I'm including the regular process of onboarding the customer, configuring everything, and acceptance tests in this time frame.

The initial setup is straightforward. 

The initial setup of F5 Silverline Managed Services is simple. The full process took approximately one day.

The client does not have to do much to deploy F5 Silverline Managed Services. The services are on the cloud and not on the client's system. Their system is more responsible for the F5.

We did not have any issues with the initial setup.

The initial setup for this solution is not really complex.

We did all of the manual procedures. The design phase was kind of complex, but this was because of the complexity of our network. It has nothing to do with the product.

The deployment took about a week. We had it run in a test environment first before going into live production.

The analyzing of logs and investigation of incidents is performed by security analysts who are part of the information security department. The maintenance of this solution is the responsibility of the network group. There is a network administrator and some network juniors who take care of it. In total, four people work with this solution.

The initial setup was straightforward. There is only one way to configure the solution.

The initial setup was easy. The implementation took about two days. I have a very good team and they all know how to deploy and configure.