Fortinet FortiSIEM vs Statseeker comparison

"The event correlation is pretty robust. The GUI is pretty good."

"The CMDB and the device discovery features are most valuable."

"Fortinet FortiSIEM is highly scalable. I would rate its scalability nine out of ten."

"The most valuable feature is auto-discovery. When you send logs from any device to port 514, it helps register those devices automatically."

"Fortinet FortiSIEM provides good detection against advanced threats."

"FortiSIEM helped us discover all the threats at the time that were attacking the IT services of the company. We now have multiple-level authentication."

"The most valuable feature is the dashboard. CMDB database collects data from a lot of pre-configured devices."

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

"We are a smaller enterprise, but we're watching approximately fifteen-thousand switchboards with no problem at all."

"This solution helps in terms of troubleshooting, and you can do capacity planning with it."

"This solution has helped us to proactively identify issues and push some of those fixes down to tier one."

"The most valuable feature of this solution is the simplicity of adding new devices into it."

"The most important feature is just the fact that it doesn't aggregate the information up, and I can look at detailed information going back quite a long time."

"The product simplifies monitoring by providing real-time alerts through a GUI dashboard, email and texts."

"We were having some issues with a certain site, and it was only Statseeker that showed us what the problem was."

"We're able to recover more expensive ports on our access line devices."

"The UI could improve in Fortinet FortiSIEM. Humans view the UI frequently for data and if it was more visually pleasing it would be beneficial."

"We expect the latest patch from Fortinet FortiSIEM to give the ability to work with signature files."

"It's difficult to integrate unsupported devices with FortiSIEM compared to QRadar. It's easier to integrate and develop processes in QRadar. It's harder to develop a custom process in FortiSIEM."

"The process of installing Fortinet FortiSIEM and the customization of the alerts take too long."

"When an alert triggers in Fortinet FortiSIEM, the layout or format can feel limited"

"FortiSIEM needs to expand its integration with third-party vendors. I don't know if Forcepoint has been added, but there were limited resources for integrating Forcepoint solutions when we implemented FortiSIEM. It integrates well with other Fortinet products and solutions from established cybersecurity companies like Palo Alto but doesn't integrate with some of the newer vendors."

"The dashboards need to be improved. It gives you so much detail, but sometimes too much detail, especially to an executive, it's too much."

"Fortinet FortiSIEM could improve by having better integration and extensions. This would benefit by allowing us to give more rules."

"I'd say the interface could improve a little bit. I find with new users, I tend to have to spend a bit of time walking them through how to use the interface. It could be a little more user friendly."

"We haven't seen an ROI."

"Detailed data can be hard to extract in CSV form. Sometimes, being able to dump down raw data would be good so various time periods across a longer period could be analysed. At present, data can be presented within Statseeker, but there is lots of "white space" between data points."

"I would like the ability to update the dashboard. I would also like the ability to access via an API. Then I could produce a dashboard that my C level can understand. This is just so they can go and refresh whenever they want to and see what things look like."

"I would like to see the solution incorporate diagnosis of the workstation."

"Technical support for this solution is bad, as is everything with Cisco support."

"It doesn't do absolutely everything and it will require some additional software or hardware support to be a complete single solution."

"I would like to have soft alarming. If an inner-base all of a sudden triggers a threshold, we have to rely on a lot of other tools and then we go into Statseeker to verify it. If Statseeker would confirm it preemptively and trigger it into our network panel, that would be nice."

"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."

"The tool is really expensive. For what the tool does for our team, the price is fair."

"The price of Fortinet FortiSIEM was reasonable compared to other solutions."

"FortiSIEM's licensing is based on EPS, and its pricing is competitive in the market."

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

"There are additional features that cost more than the standard licensing fees."

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

"Please be cheaper and more simplified."

"It's probably $5K a year for the license."

"We now feel the pricing is a good value. Previously we had a just a normal license but now we've got an Enterprise license. Since the Enterprise, it's been a lot better value. We did think it was pretty expensive before, but with the Enterprise license it's almost less than half that price. If you have a number of accounts within the organization that use Statseeker, I would suggest get the Enterprise license."

"This tool would probably be priced well if it had deeper NetFlow capabilities, but for our use case, in particular, we're only recovering ports after ninety days and looking at circuit congestion, it's pretty pricey."

"The licensing cost is yearly and it's $5,000 to $8,000, I think."

"It would definitely be a yearly licensing cost, but I don't know what it is."

"We have permanent licenses so there's really no cost, other than ongoing maintenance. When I think about it, that's running us about $20,000 a year."

"One thing that needs improvement is how it's licensed. I understand historically the company licensed it off a same charge for everyone. I understand the company needs to make money, but how they introduced the tiered licensing model, and then multiple layers of licensing was a bit of an issue. So, on the whole, coming up with a licensing model that isn't confusing and complicated and is easy to understand would be one way to improve the product. They have told me lately that they're changing how they license stuff, but they haven't made that - as I understand it - in their marketing material public knowledge as of yet. I would say that at the moment it's a bit convoluted. It's confusing. Some of their basic licensing model is a bit of a ripoff. If you go over five or ten support calls in the basic licensing model they start charging you for support calls. I think that's a bit rich."

"We paid $5,000 to $10,000 a year in maintenance."