What is our primary use case?
Our main use cases for the solution reflect that we chose Cisco because it's a unified solution. It's not just a single piece of equipment that requires extensive additional work to make everything else function. You can implement it end-to-end and it delivers comprehensive coverage.
I am using Cisco Hybrid Mesh Firewall together with several other Cisco security products and capabilities in a full Cisco environment. I had Cisco ICE, Cisco switching, Cisco ACI, Cisco UCS, and Splunk. This created a large Cisco ecosystem that we deployed, which is part of the reason we remained with Cisco Hybrid Mesh Firewall solution.
Regarding the capabilities I'm using together with Cisco Firewall, in our environment, we run an SDA environment. We have our access edge, which is our plug-and-play users. ICE forms a baseline of our entire SGT policy, with Cisco Hybrid Mesh Firewall serving as a break between our IT, OT, IOMT, and DMZ environments, creating a very full and simplified policy structure.
I am in the process of evaluating whether I use Cisco Security Cloud Control with my firewall, waiting to see where it progresses because in Australia, Triple C is coming out as a full feature release shortly. I'm weighing whether or not we adopt one or the other.
I have not started using or testing Triple C as it is not available in Australia yet. I have had some preview access through Cisco and through my account manager. It is something we are definitely considering. The question remains what benefits it brings to the organization to implement it as a fully-fledged solution.
That is something we're in the infancy of evaluating as we expand the product sets and the features we're pursuing.
I do not use Cisco AI Defense, but that's in our next roadmap. We're expecting that in Q3 of 2027.
I use Cisco Smart Switches, specifically utilizing the 9500X, which is the first generation of the Silicon One chipsets. I am about to place an order for 500 of the 9350 Smart Switches as part of our life cycle replacement.
How Cisco Smart Switches with segmentation capabilities work with Cisco Hybrid Mesh Firewall in my environment is not clear to us yet. We're still waiting to complete a production lab test.
The environment I am protecting with Cisco Hybrid Mesh Firewall includes critical water infrastructure across the entire state, as well as protecting medical endpoints. We are protecting the people of WA utilizing Cisco Hybrid Mesh Firewall.
How has it helped my organization?
The value I get from using Cisco Hybrid Mesh Firewall together with other Cisco security products is that we end up with a single unified pane of glass where anyone within the IT teams can log in and see the data set. It's one point to review. We're not logging into 15 different programs throughout the day for something we don't need. We've seen a massive uptake in ticket resolution, and ultimately, the corporate user is happier because we can identify the problem and resolve it efficiently. We're not troubleshooting 15 different applications.
I can quantify these improvements in terms of percentages. Rather than standing up new teams with this deployment, we've managed to optimize our existing team and their processes to take on the new workload and actually improve the enterprise themselves rather than spinning up dedicated teams. We've achieved about a 40 percent reduction in tickets, a 15 percent reduction in resolution times on P1 or P2 issues, and an 80 percent increase in customer satisfaction.
What is most valuable?
One of the features of Cisco Hybrid Mesh Firewall that I appreciate the most is the simplicity to deploy the device. I don't have to go to a site and do it myself. I don't have to send my senior engineers. I can get the device shipped to site, and one of my junior field support engineers can plug it in and it comes online. For us, covering such a large area of a country, that flexibility has proved invaluable.
In the context of the combination with segmentation and policy enforcement, visibility for stopping lateral movement is critical. The switching becomes the first layer within the VN structure. You have inter-VN and intra-VN capabilities. The switching is one layer, and Cisco Hybrid Mesh Firewall controls the secondary layer. For us, preventing lateral movement from a corporate end user into a patient monitoring system is crucial. It's a life-saving segmentation design.
The value I get from enforcing security closer to traffic alongside my firewall or firewall-like products is that you should always enforce closest to the egress point. You should never allow someone to get past or out of a site to begin with. The moment someone gets past that first perimeter, they're in your network. There's no stopping them from there.
What needs improvement?
As of now, there are no improvements I would like to see in how Cisco Hybrid Mesh Firewall works with other Cisco security products I use. Hopefully, as we progress through our journey, there will be things that we can work with Cisco on improving and bringing new feature sets that benefit not just us but everyone else.
As a product or solution itself, I do not want to suggest improvements or newer features at the moment. We're still building the product ourselves. We have sites running on it, but we have a lot more to accomplish before we reach a point where we finish our initial setups and designs.
For how long have I used the solution?
I've been working in my current field for about five years. I have been working with Cisco products directly within health for a year. Before that, I was in Cisco in utilities and OT environments.
What do I think about the stability of the solution?
Cisco Hybrid Mesh Firewall has demonstrated great stability. To date, we've had no major outages. We've had the occasional bug, which is standard in any evolving environment, but we've had no major outages caused by the firewalls. We've experienced power outages and WAN outages, which are standard. Recovery when power is restored is nearly instantaneous. The same applies when a WAN link goes down and comes back up. We see a brief blip and that's all.
What do I think about the scalability of the solution?
Regarding scalability, we have experienced great scalability. We are deploying across multiple sites. We deployed 100 Cisco Hybrid Mesh Firewalls in the environment as we progressed, and it was plug and play throughout, with a single unified policy across all of them.
How are customer service and support?
During the program, we did have an engaged HTOM for the whole program, so I don't want to comment on that. It's not fair to the general support.
Which solution did I use previously and why did I switch?
Before adopting Cisco Hybrid Mesh Firewall, I used some other vendors. There was a mix of firewalls in the environment. There was some Palo, some FortiGates, and some Sophos. It was very much a mixed environment. Unifying it all became a very clear requirement for the business.
How was the initial setup?
The migration was challenging due to the differences between vendors. There was no central management, so each firewall had to be reviewed individually. There were no rules against the names; they were IP addresses, so none of it made sense. There was no clean 'we're cutting from this firewall to this firewall' process, so there were syntax changes throughout. That's where we encountered most of our issues. Cisco did have their firewall migration tool available as we finished.
What was our ROI?
I have seen a return on my investment in the sense that we haven't had to retrain the engineers on new products or new ways of working. It's simplified the training model because we go, 'Hey Cisco, we've got a new engineer. When can we get them in?' We're not dealing with five different vendors for one environment.
Which other solutions did I evaluate?
I evaluated other firewalls before going with Cisco. During the evaluation, we looked at going to a full FortiNet environment. So FortiGate firewalling, Forti-switching, FortiNAC, FortiPhones, and everything else. The capabilities, while FortiGate does produce great firewalls, the overall capabilities weren't right for the company at the time, whereas Cisco had everything we needed in an easier, simpler-to-deploy package.
What other advice do I have?
If I were to rate Cisco Hybrid Mesh Firewall overall on a scale of one to ten, I would give it a solid eight. There were a few things during the deployment that challenged us while we were learning that process. One of the biggest challenges was migrating our legacy policies and structures over to Cisco Hybrid Mesh Firewall. That was a significant challenge for us. Overall, the performance is great. I can't fault what they deliver. The setup was hard for us; it doesn't mean it is for everyone else.
My advice for someone who is researching and considering purchasing Cisco Hybrid Mesh Firewall based on my experience is to buy one and put it in a lab. Experiment with it before you deploy it. You'll do the same thing I did and run with it. Get hold of one, spend six months, break it, experiment with it, challenge its limits, and don't be afraid.
Which deployment model are you using for this solution?
On-premises