The deployment is pretty seamless. Sometimes we do have some issues with Palo Alto Fireworks, where when it comes to deploying, it's not as intuitive. It doesn't work correctly, and there are some bugs that come up. So we have to troubleshoot that aspect. Cisco Secure Firewalls is pretty pretty seamless.

My experience with the deployment of Cisco Secure Firewall has been awesome. I come in when they have the old network and deploy it. I install a cabinet and new drops. I configure the Meraki gear onto their old network side by side. Especially during downtime, I can plug the firewall into that rack to get the external IP configured. Once my ISP comes in, I apply those IP addresses to the firewall.

Deploying Duo is quite simple because Duo has very good documentation for all integrations. It typically takes a couple of days to deploy because we need to schedule meetings with our clients. When we gather all the information, we can integrate it, then test it and put it in production.

Deployment-wise, Cisco Secure Firewall is straightforward, as all Cisco products are straightforward. It takes roughly two months to deploy Cisco Secure Firewall, but it depends on the type of implementation and the specific data center involved.

Deploying Cisco Secure Firewalls is quite straightforward, as Cisco provides a lot of available documentation online, extensive support, and training, which makes it easy for engineers and customers to use Cisco products effectively. The deployment time for Cisco Secure Firewalls varies. Currently, I am going through a refresh where we are replacing older Firepower systems with newer ones, but in the past, it has been relatively simple, typically taking within an hour or two to get everything up and running.

I find deploying Cisco Secure Firewall to be a little bit challenging, but once it is implemented on our network, it is stable with no problems or issues. It is not that complex, and if we know our network, the Cisco team is helpful in guiding us to achieve the best design and implementation.

I find the implementation of Cisco Secure Firewall depends on the requirements; there are two approaches. To deploy a new firewall is easy if we are using cloud-based management. However, the same functionality applies to both whether it's cloud-based or on-prem. The plug-and-play feature is useful for onboarding new firewalls. That makes it easy to onboard a firewall in the management center automatically without any CLI. We just have to plug in the device and connect the cable for the network.

When setting up Cisco Secure Firewall, I encounter significant challenges, especially with on-premise Next-Generation Firewalls. There is lacking clarity in documentation, particularly when changing internet service providers or external IP addresses.

The initial deployment was most difficult because there were some compatibility issues. At the time I came to the team, we were transitioning from Cisco ASA to the new Firepower solution, and the tools for migrating the configuration about the objects were not working properly. I did not have the time to work out why since I was not the main architect of the network and was in a lesser role, but this was one of the main challenges I worked on. We had to do a lot of scripting and manual work to migrate the objects and configure the new solution because Cisco ASA was not very capable of extracting the information to push to a newer generation of firewalls.