FireMon vs. ServiceNow IT Operations Management

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.

Incentivized

[...] is changing the way our internal support staff (not only in the IT field) work and enhancing the experience for employees seeking IT assistance through ServiceNow IT Operation Management. We have moved the usual and personalized IT tools and functions from [...] service-desk to ServiceNow IT Operations Management. These advancements have sparked innovation in various aspects of our IT support management, such as enhancing accessibility, managing incidents, optimizing IT workflows and procedures, enforcing service level agreements (SLAs), incorporating AI/ML technology, utilizing virtual agents, streamlining automation, and sharing knowledge throughout the support team via data visualization, monitoring, and reporting. In brief, our collaboration with ServiceNow IT Operations Management is enhancing the effectiveness of our internal system and benefiting our shared clients.

Incentivized

• Give good real time reporting for anyone making a change to any of our firewalls
• Provides good reporting tools that are out of box
• Provide good customization tools that is specific to our needs
• Upgrades are a simple process and support does relatively well with assisting us.

Incentivized

• In platform expertise and workflows, so we don't allows have to build everything from scratch.
• Tight integration within ServiceNow (especially ITSM) but also brings information and data in from other sources, so I don't feel we are stuck in a proprietary hole.
• Increased investment in AIOps and automation
• Relatively fast time to value with out-of-the-box capabilities and automation.

• Some features could be added to the existing functionality which include NAT rules usage
• Rule expiration normalization from firewalls rather than entering them in rule documentation
• .csv exports of the files from the firewall pane only gives usage for 30 days by default and that should be increased

Incentivized

• With the introduction of AIOps, we hope triaging outage impact can become more proactive
• The UI could be greatly enhanced and simplified for daily operations
• ServiceNow API access licenses are usually very limited bottlenecking use cases to build dashboards out from it

Incentivized

The shell is locked out and we can't run any general centos commands. The implementation and maintainence of the arch is very complex. Even with the right identifiers on log messages the log collection keeps failing. The warning messages on the device are ambiguous. The log messages on firemon are a bit confusing and don't show the exact issue.

Incentivized

It save me time and I'm able to have the review - review the rule independently with using my time.

Incentivized

We achieved in financial what we are aiming for, as our targets are fulfilled, we solved many issues using ServiceNow, Creation of knowledge article improved, Ticket system got customized, overall survey from the customer is 4 out of 5, customization is done without any hustle and integration was very easy.

Incentivized

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.

Incentivized

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.

Incentivized

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.

Incentivized

Implementation is fairly simple. Most issues can be resolved by referencing manuals.

Incentivized

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

Incentivized

We wanted it integrated with ITSM and ITBM. Prioir to that we used JIRA for agile development and SysAid for ticketing. So we started with converting SysAid. We went live with Vanilla ITSM. Then we could have a basis for ITOM. However, we needed to migrated from JIRA to ITSM. Only then we felt mature enough to examine ITOM, which required quite a lot of resources. You need networking, motoring, IT and Cyber security team members in your project!!

Incentivized

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.

Incentivized

• FireMon's Compliance Reporting provided an immediate and tangible benefit
• FireMon helps identify egregious or erroneous rules quickly across multiple platforms
• FireMon took our audit process from an Excel spreadsheet into a far more advanced process with readily available context for reviewers

Incentivized

• Makes it MUCH easier to understand impact between application and server
• Makes it easier to understand impact from a change and what all it affects

Incentivized