Cisco manages the solution's setup. We purchased their managed services, so they continue to handle its management.
The complexity arises when deploying various web security solutions, such as Kaspersky, with Cisco Web Security Appliance. Sometimes, transitioning from one solution to another, like Kaspersky to Cisco, can bring certificate installation complexities. 

If we opt for the Cloud version, implementation takes two months. On the other hand, deploying the on-premises solution usually takes three to four months.

The initial setup is dependent on your knowledge of how to deploy proxy. Back when I was an engineer, I was the one who actually deployed it. I'm now a director, so my role is different, but I carried over my knowledge from my previous engagement. For me, it was easy based on what I knew.

The initial setup for a basic implementation with direct access to the proxy is straightforward. 

I rate setup a ten out of ten. 

I rate the initial setup an eight out of ten because it is straightforward.

When deploying the product, first of all, you need to understand the requirement for the security concerns before deploying it in an organization, which will take some time. After that, you install the software and create the policies to ensure your client is using a secure channel to access the Internet. You will need to refine policies based on the client's requirements. The process will take time to stabilize things for a new deployment. If the policies match the organization's, deploying the solution will take a couple of hours, not much more. We needed just one person for deployment and one person for maintenance and management.

The implementation was very straightforward. The interface is really intuitive. I don't know about the new one, however. They released an interface, however, it wasn't fully released. It was a demo. Those interfaces were really good.

Getting up and running from start to finish takes about eight hours. 

The setup was pretty fast as the features that I used were pretty straightforward and all I had to do was handle custom URLs. It wasn't too complex a configuration.

The solution is very easy to set up. It's user-friendly. The process isn't difficult. It took us about a day to set up.

The initial setup is easy and our customers are satisfied with the deployment and the support we provide in that respect. We work with two or three engineers per site and deployment usually takes somewhere between 10 to 15 days.

I haven't set it up, but I believe Cisco Web Security Appliance's initial setup is easy.

I rate the product's initial setup phase a seven on a scale of one to ten, where one is a difficult setup phase, and ten is an easy setup phase.

The solution is deployed on an on-premises model.

It took quite a long time to implement the solution, maybe seven to eight months. The deployment phase took a few weeks.

Two or three specialists who are network administrators in my company were involved in the deployment and maintenance phases of the product.

The tool's deployment is very straightforward. The only process that can take time is aligning the policies as per your use case. 

The initial setup is complex. The is not much flexibility when creating policies. As per the design guide, they have provided a lot of limitations for creating policies. For example, if I create 30 access policies, 30 customization decryption policies, and 30 custom complex policies, there is a complexity in the qualification. If the policy is complex then CP gets high, which is a problem. 

Following the best practice guide, I have to follow that constraint. However, customers, are not happy with the restriction and policies. They want to create as much policy as possible. 

The implementation took approximately two weeks or ten working days.

The initial setup for Cisco Web Security Appliance was pretty easy. It usually takes just a day or two to complete the deployment if you have all the information, but it's mostly the customers performing the initial setup because it's all done remotely.

We found the initial setup to be slightly complex because it was a new product for me and my team. We installed it in the Unity environment and tested it for quite some time. Then we deployed it slowly, starting with the back office and then rolling it out to the branches. The deployment took about four months to bring it from purchase, through a PoC, and into production.

Setting up Cisco Web Security Appliance is highly complex and it takes about a week. We have to connect it to the Active Directory and configure all the policies for end users. It takes a long time to configure rules for our company data like port forwarding and separating the public and local components. 

The level of complexity of the initial setup will depend on the level of customization. If you want to start the product with the best practices presented by Cisco, it's very easy. You have to manage your own IP addresses and check that the service is okay. It's integrated with other services and then apply it to your users. It's very easy to implement. You need a high level of skills to manage it. If you want special customization or a high level of security activation, it may be a bit more complex. 

For a single appliance without any high-appliance activated and if you have all the data, DNS servers, and IP addresses, it can around an hour to implement.

The solution is very easy to implement. It's not overly complex or too difficult. Our deployment took about six months.

We have five team members that can handle setups and maintenance tasks. They are engineers.

The solution's deployment phase lasted around three months. 

Deployment and maintenance require two to three technicians. 

The initial setup is straightforward. 

The initial setup wasn't easy but not complex either.

The setup was very easy and straightforward.

The initial setup is a bit complex.

It can take two to three days to deploy.