Cisco Meraki MX Firewalls is a combined UTM and Software-Defined WAN solution. Meraki is managed via the cloud, and provides core firewall services, including site-to-site VPN, plus network monitoring.
$595
per appliance
FireMon
Score 7.9 out of 10
Enterprise companies (1,001+ employees)
FireMon is a real-time security policy management solution built for today’s complex multi-vendor, enterprise environments. Supporting the latest firewall and policy enforcement technologies spanning on-premises networks to the cloud, FireMon delivers visibility and control across the entire IT landscape to automate policy changes, meet compliance standards, to minimize policy-related risk. Since creating their policy management solution in 2004, FireMon states they've helped…
N/A
Pricing
Cisco Meraki MX
FireMon
Editions & Modules
MX64
$595
per appliance
MX67
$695
per appliance
MX68
$995
per appliance
MX84
$1,995
per appliance
MX100
$4,995
per appliance
MX250
$9,995
per appliance
MX450
$19,995
per appliance
No answers on this topic
Offerings
Pricing Offerings
Cisco Meraki MX
FireMon
Free Trial
Yes
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
—
More Pricing Information
Community Pulse
Cisco Meraki MX
FireMon
Features
Cisco Meraki MX
FireMon
Firewall
Comparison of Firewall features of Product A and Product B
Cisco Meraki MX
7.9
Ratings
9% below category average
FireMon
-
Ratings
Identification Technologies
8.30 Ratings
00 Ratings
Visualization Tools
8.70 Ratings
00 Ratings
Content Inspection
8.10 Ratings
00 Ratings
Policy-based Controls
7.50 Ratings
00 Ratings
Active Directory and LDAP
7.90 Ratings
00 Ratings
Firewall Management Console
6.50 Ratings
00 Ratings
Reporting and Logging
7.70 Ratings
00 Ratings
VPN
8.80 Ratings
00 Ratings
High Availability
9.10 Ratings
00 Ratings
Stateful Inspection
7.40 Ratings
00 Ratings
Proxy Server
6.80 Ratings
00 Ratings
Best Alternatives
Cisco Meraki MX
FireMon
Small Businesses
pfSense
Score 9.9 out of 10
NinjaOne
Score 9.0 out of 10
Medium-sized Companies
Quantum Firewalls and Security Gateways
Score 9.6 out of 10
NinjaOne
Score 9.0 out of 10
Enterprises
Palo Alto Networks Virtualized Next-Generation Firewalls - VM Series
We used Meraki MX with our remote sites and connected the MX 68 to our main MX 85. We routed traffic to our enterprise network and shared application and internet access to remote sites. We have routed traffic and allow only trusted IP address sources using the firewall rules implemented in the Meraki MX. In other scenarios, if the internet is lost, the Meraki will go offline; thus, stable internet access is important to maintain connectivity
FireMon is best used in a large environment (for example, I have >100 firewalls in my environment). It's best used when trying to improve security posture and showing changes in firewall security over time. It might not be the best choice for smaller environments or those that aren't concerned about security management.
It provides a really good single pane of glass so you can really easily identify end to end, what is going on in your environment.
It provides the ability for someone that doesn't necessarily need a really deep level of knowledge to be able to operate and maintain it. I think that's probably a big selling point, but I think definitely for the people that I'm selling the products who just having a dashboard and being able to log onto it and see if things are good or bad is quite key. So it does that really well.
PCI Reporting - After identifying which firewalls and rulesets are in scope, producing a report artifact to satisfy PCI requirements on Firewall reviews is literally a two-click operation.
Storing Rule Metadata - FireMon stores metadata (prefilled fields, standard fields, and custom fields) for each rule in each policy which is valuable for context during firewall reviews in particular
API - FireMon exposes most if not all of its functionality via REST API
Layer seven firewall rules. Just making them more granular. We've been in meetings with Cisco SES where I've said feature requests many times and that's one of the big ones where it's just a little cumbersome to implement layer seven rules right now.
Just making them more granular. We've been in meetings with Cisco SES where I've said feature requests many times and that's one of the big ones where it's just a little cumbersome to implement layer seven rules right now.
It is already in place and the client is happy with it. We don't see a need to change what is already working. We want the Meraki to stay out of the way and keep things operating, and that's what it does.
Once all the customization has been completed, the business is starting to see the return on investment. The visibility it provides into the network gear that is owned by other IT groups is immeasurable and has allowed us to apply standards across the board. The only thing I have concern with is their support documentation.
The Cisco Meraki MX series is very easy to use. Setting up user VPN access, site to site VPN to tie multiple locations together and managing all your devices. You can even download the latest firmware and install without ever leaving the dashboard. Meraki is the very definition of easy to use
Meraki MX devices support high availability (HA) configurations, which ensures minimal downtime if one device goes offline. This feature has helped us maintain a stable and reliable network, even in cases of hardware failures. ince Meraki is cloud-managed, we've noticed that the cloud infrastructure is generally highly reliable, with minimal service interruptions or downtime. This makes it easier to manage the network remotely without significant availability concerns. Meraki automatically pushes firmware updates and patches, which helps maintain system stability without requiring manual intervention. These updates are rolled out in a manner that ensures minimal disruption to service.
FireMon has been relatively stable overall. However, there have been a handful of times where we had issues with the console. For example, we couldn't update which devices to include in a security assessment. The initial suggestion from support was to just reboot it. It seems like there weren't many other options available such as to restart services before going to the extreme of a complete reboot.
The interface is pretty responsive. The lower end devices are easy to overwhelm if you have a lot of throughput. Be sure the model you get is rated for the amount of traffic you will have. Overbuild if possible, otherwise you won't be fully leveraging the connection from your ISP.
I'm not sure we have the largest implementation of FireMon out there but we do have a few 1000 devices being probed by FireMon. Overall, the system's performance has been rock solid. The console refreshes quickly and reports are generated within an expected timeframe.
I haven't ever had a bad experience with Meraki support. On the few occasions where I wasn't understanding the UI or needed some clarification about what a setting actually would do, I contacted them and they were very quickly able to provide help. Returns are simple and fast, too. We had to return a defective device one time and they shipped the replacement before we had even un-racked the one that was faulty. Unlike many other vendors, they didn't ask use to a do long list of scripted diagnostics, they just took my word for it that the device was broken and sent out a replacement immediately
FireMon technical support is awesome! They respond quickly to our requests and they are well trained and very knowledgeable about the tool. Some issues have to be referred to the development team, but technical support largely provides solutions for any issues that we may have.
great when they offered it, really tested your knowledge with hands on and see what your peers from other orgs know. glad to see that we were ahead of the curve of what our peers knew
Implementing Meraki MX devices in phases—starting with a pilot group or select branch offices—was invaluable. This allowed us to identify potential configuration issues, troubleshoot problems, and refine our setup before rolling it out company-wide. It also helped to get feedback from early users and adjust the deployment strategy accordingly. The SD-WAN capabilities in Meraki MX were essential for optimizing our WAN traffic and ensuring better application performance across various locations.
We previously evaluated WatchGuard Firebox Cloud, but we needed a solution that was a bit more straightforward to deploy and manage. The MX met that need for us. However licensing costs for both solutions are still a bit high.
I has worked with AlgoSec and while they are very similar product, I find the FireMon is easier to understand and get rolling with. While both require some learning, FireMon is by far the easier one. Once you have an understanding of how things are arranged and labeled you can easily import firewalls and begin to work on them to improve them
When I first started with my company we had various infrastructure and a mix of tech. Since going to Cisco Meraki MX we have noticed better network performance and our new sites are much easier to bring online. Users have noticed an improvement in VPN connection and getting into all our systems.
Firemon Is easily scalable and maintainable with any size team. Although it requires some tech debt, it is well worth the time to invest to ensure compliance is visible and reports are accurate. Although our environment is very large we do not fully utilize the scalability of the Firemon product.
From a positive impact? Basically it allows us to set up shop very quickly. It allowed us to add sites to our network very quickly. From a negative perspective, I think the only thing is that I can see from a negative perspective is I have a preference to working with ACLI in terms of how I engage with the youth tool At the moment, the only way to actually engage with a tool is on a gui and sometimes what I'd actually like is more detailed information in terms of actual configuration that you'll actually get out of ACLI.
It helps us save us time in determining what change was made and by whom.
Real time alerting is a great convenience in helping us know if something went wrong, we can immediately review the last report to determine what has changed.
Allows us to determine what rules are not used and if said rules are still required.