It was a straightforward setup. We had no hiccups.

The initial deployment of Radware's solution was simple. Radware typically sends its team to assist with the setup. Our implementation strategy involved a day for configuration, another for installation, and a third day dedicated to monitoring the solution. This three-day strategy is our go-to when implementing any Radware platform. It took us three days to get everything up and running.

As for staffing during the deployment, one person from Radware was present, along with two members of our IT team.

There is no maintenance required from us.

It is deployed on-premises in our environment, but we are selling it as a cloud to the customer.

Its deployment was a little bit complex because we did not have in-house expertise. The Radware team and their partner helped us to deploy it. The next deployment will be easy for us because we understand the technology now. The first time deployment was a little bit tedious for us because we did not have the knowledge of the product. In terms of duration, it took a couple of weeks after delivery.

We have not had many problems after the implementation because we had the support of their team.

There is maintenance from the upgrade point of view. Otherwise, there is no maintenance.

I'm not a technical guy. From my perspective, the initial setup is not easy. However, it's not hard. Someone who would like to have a good security policy should have enough knowledge to configure it using the security policy. The knowledge is essential since it's not possible to implement a security policy without knowledge about the traffic, including what kind of traffic, what kind of application, what kind of parameters, et cetera. It's not a hammer. It's a security appliance. For our people, it's not as hard since we use it. We know how to use it. It's maybe more important to integrate it with additional systems like a CM.

It offers an easy initial setup. It's not overly complex. You shouldn't have an issue with the implementation process. 

I'd rate it 4.5 out of five in terms of ease of implementation. 

The initial setup was very straightforward. Maintenance requirements depend on the size of the environment. If it's deployed in an ISP environment then it requires one or two administrators. If it's a single appliance for an enterprise environment, then one person is enough for maintenance.

The initial setup is simple. The deployment should take no more than one or two days. There are sometimes challenges during the implementation, which is why it takes this long to complete. The support from Radware is very helpful.

Radware DefensePro is easy to deploy and integrate with different technologies. It is simple. 

For the deployment strategy, sometimes we have to use the line mode, and sometimes we use a different structure. The configuration is purely dependent upon the network, i.e. which segment that you are deploying. 

Sometimes, in order to establish automation in a cloud data center, we have to take the product and design some custom settings. Sometimes, we have in-house data center requirements, so we have to design those accordingly.

We can setup Radware DefensePro within one or two days, i.e. easily within one day. The product does not take more than two days at a time to integrate.

Initial setup is easy.

The initial setup isn't too easy. Know-how is very important when implementing the solution and without that, the solid security policy is risky. It's not worth it to do it without a good amount of technical knowledge.

The initial setup was easy.

I was not here when the initial setup was completed, although I'm assuming that it was pretty straightforward. My understanding is that the deployment took less than 24 hours to do because they were under attack. They contacted Radware to stop the DDoS attack at the time, and they came in and installed it. By the time that it was installed and put into place, the attack had stopped, and it hasn't really been utilized since that time.

The initial setup was straightforward and much easier than the AppWall. You are able to install this solution on-premise in three to five days. There is a baseline that is based on the traffic of your network that can be adjusted and configured to your specific needs.

The whole process can be completed by a single engineer.

The initial setup is not complex. It's very straightforward and very easy. The configuration process, as well, is excellent and very straightforward. A company shouldn't face any issues when they are implementing the solution.

That said, we have a pretty complex environment. Our implementation process could have been easier.

The deployment process was very fast and took about one week.

The initial setup was straightforward. The deployment took about three days and the plan was executed such that there was minimal disruption to the business services.

We had been satisfied with the outcome of the simulation and everything we did before actually migrating to the production environment.

Two staff members, both system administrators, are handling maintenance. The same two people focus primarily on the edge protection devices.

Setup is very easy. It has a simple interface and it has good resources. It is a simple step-by-step process. It is very fast. We did use two people for the deployment.

It was a straightforward setup. Deployment was not a challenge, and it took a few weeks.

We needed support for testing and implementation. They will point you to tutorials and assist you where needed.

My understanding is that the initial setup is not overly complex. I've heard it's straightforward. I'm not actually the person that does the implementation, and therefore I don't have direct experience in the matter. The equipment seems pretty simple and straightforward.

Implementation is straightforward, once you have all the necessary documentation. I couldn't find any documentation until I was registered, however. They don't have enough public information about the solution. Before registering, I couldn't do anything. This was a new product for me, so it was important for me to have access to the implementation guide before starting. 

You only need one person to handle the implementation.