Fortinet FortiSIEM vs Zabbix comparison

"Fortinet FortiSIEM needs to provide better API integrations to users."

"The product is quite well-organized. The GUI makes it easy to navigate."

"The stability is very reliable. It offers very good performance."

"It works well with medium to large-scale enterprises."

"It's a very nice solution to work with."

"FortiSIEM sends an email or SMS notifications to admins when there are significant incidents. It's a highly efficient way of responding to incidents."

"The solution is easy to use and user-friendly."

"Fortinet FortiSIEM is easy to use."

"The performance and bandwidth are valuable features."

"Simple network monitoring that is easy to install and manage."

"Dashboard and the customization of the items and triggers are the most valuable features."

"The product is very stable."

"Zabbix is very easy to implement."

"We have found that Zabbix is more easy to use than other applications."

"The initial setup, while not simple, is easier than other products."

"The solution is quite mature and very stable."

"The performance can be improved. Sometimes it takes a long time to fetch data."

"I would like to see more integration with other platforms."

"The only drawback is the licensing model. It can get expensive if you want to integrate more solutions."

"The built-in APIs in Fortinet FortiSIEM are somewhat lacking and could be improved for better integration with external ITSM products."

"I would like to see easier implementation in the future."

"Fortinet FortiSIEM should broaden its remediation part to include more features for incident management. Currently, to manage repetitive incidents or for remediation, I need to use a separate software called FortiSOAR."

"An improvement would be if FortiSIEM's licensing was based on the number of nodes rather than the EPS."

"When compared with some competitors, in terms of performance, the CPU and RAM requirements and the capability of coordination with development all need some improvement."

"Zabbix is powerful, but it is difficult to understand initially. There are many things that can be improved, but we might not be using Zabbix to its fullest extent. The software has more features than we need."

"Its UI needs to be improved a little bit more so that an end-user is also able to handle it. I can handle it, but others should also be able to handle it in a better way. It becomes complex when we are growing and need to add proxies. We need more scalability features and documentation for different use cases. A lot of articles are available, but they need to be in proper documentation. For example, when you have thousands of servers that have to be monitored in different regions of the world, there should be some kind of documentation to describe how you can create proxies and add them. Sometimes, when you are using the database, it can get overloaded. When the network is growing, the number of transactions becomes very high, and the database gets overloaded. There should be information about how to reduce the load on the MySQL database, which is what Zabbix is using. The market is growing a lot, and it should be enhanced for a lot more things. We are currently bringing enhancements at our end for different use cases. For example, when dockerization is going on, how can we check the logs inside the Dockers. We should also be able to monitor and check the number of logins and add features such as SSO login and two-factor authentication as a protocol. These are the security features and concerns that we have to deal with. Currently, we are developing modules to add features to Zabbix, but they should also work on these features."

"As far as improvements, sometimes I get a bit frustrated when I move from a previous version to a new one because some configuration has changed—I need to investigate the documentation to deal with some configuration. But it doesn't take much time, so it's okay."

"I would like to remotely connect to the computer, and Zabbix doesn't have this capability."

"I would like for this solution to be more cloud-friendly."

"Implementation is always tailored to the customer and the kind of information we need from the client to carry it out can make them very uncomfortable. Sometimes the clients are not ready to share it."

"Implementing Zabbix is difficult. I've deployed many solutions over the years, and Zabbix is the hardest to implement. You have to do some development to get it to work with IBM, Micro Focus, or HP products."

"Documentation terminology could be improved."

"Pricing is acceptable for more than 90% of our customers, as they normally get discounts."

"They have a yearly subscription."

"Its price can be better. We are Fortinet partners, so we can get discounts, but its price can be an issue at the beginning for others. There is a licensing scheme for every case. There are three licensing schemes that we can choose from."

"Please be cheaper and more simplified."

"The price is competitive."

"We bought the perpetual license, so we own the product, but there is a three-year support renewal fee for that."

"We pay for a license for FortiSIEM. We pay for the license and renewal."

"Fortinet's products are not expensive, it is less than the competition."

"Zabbix is open-source so if one wishes to implement it in-house, they must have qualified professionals to set up and optimize databases, Linux/Unix OS, PHP, Apache, and depending on what is monitored, a full-stack network and systems administrator may be needed."

"There are no licenses."

"If you have 20,000 hosts, the support costs around €95,000 for a year."

"We purchased Zabbix for a good price, including support"

"There is no license but we need to pay for support."

"This solution is open-source and free to use."

"We use the open-source version of Zabbix."

"This is an open-source solution that can be used free of charge."