DNIF HYPERCLOUD vs Mezmo comparison

"The benefit of DNIF was that the solution was able to detect any anomalies and identify and prevent any possible security threats or attacks."

"The solution is quite stable and offers good performance, it also works on a virtual machine and we haven't found any issues with it so far, it's been reliable."

"The User Behavior Analytics is a built-in threat-hunting feature. It detects and reports on any kind of malware or ransomware that enters the network."

"Great for scaling productivity for log monitoring purposes."

"It was one of the first SIEM tools I saw that had that particular MITRE table."

"The dashboard is helpful, and it creates visualizations to let staff review event data and identify patterns and anomalies."

"Has a great search capability."

"If you're an enterprise company and want to scale your productivity for log monitoring purposes, I found DNIF a better option than Splunk which has more complex software."

"LogDNA consolidates all logs into one place, which is super valuable."

"With LogDNA, which brings all the logs together in an interleaved stream, it allows us to take a transaction and relate it to other contextual events making the gathering of evidence for auditors and our internal RCA much more productive."

"The solution aggregates all event streams, so that if there are any issues, it's all in the same interface."

"We haven't had anything yet that we couldn't do through LogDNA."

"The vendor is fairly new and it's not as big as some of the international competitors. It's not a mature product."

"I think DNIF HYPERCLOUD can implement the ability to export more than 100,000. At the moment, we can't go beyond that. So many times, if you're checking for the firewall logs and working on something related to authentication or network-related traffic, while that log count is low, the account goes beyond that. You can't restrict the logs or the amount of data you can export. It's very important for my situation. It would be better if they could increase the capacity of exports. Although there are many more types of searching in DNIF HYPERCLOUD, people still struggle to query out what they want because not everyone is good at SQL or DQL. The easiest way to query out in DNIF is using the GUI-based interface. But in the GUI interface, you can use operator calls. It gets tricky when you want to search for a specific type of event. You don't know where it will be passed and whether it will be consistent. In the initial phase, it's tough for us to use DNIF. You cannot pass every event in a stable DNIF. When we used that particular tool, we used to get those logs, but sometimes many things are not getting passed. So, we used to export the sheet or export the data into Excel and weigh the required details. In the next release, I would like them to improve the export of the columns and make the application more user-friendly. I would also like a threat-hunting feature in the next release."

"The solution should be able to connect to endpoints, such as desktops and laptops."

"The EBA could be improved."

"There are currently some issues with machine learning plug-ins."

"I used version 8 which was not at all stable. The services and processor keep going down, we had to manually keep them up increasing storage space because services are down, and logs not processed."

"DNIF HYPERCLOUD is not a stable product compared to other tools like IBM QRadar."

"I feel that DNIF needs to invest more in marketing, considering that it operates at a very competitive speed."

"Every once in a while, our IBM cloud operational implementation gets behind. Sometimes, when we have a customer event, we do not get access to the latest logs for about 30 minutes, particularly for the sites that are heavily utilized."

"Every once in a while, our IBM cloud operational implementation gets behind. Sometimes, when we have a customer event, we do not get access to the latest logs for about 30 minutes, particularly for the sites that are heavily utilized. This is clearly not good. It is impossible to RCA when you can't look at the logs that pertain to the time period in which the event occurred. It could be more of an operational problem than a feature problem. I don't have visibility about whether it is a LogDNA issue or just an operational issue."

"No ability to encapsulate a query or a filter, and communicate or share that among the team."

"Scalability could be improved; we are using it through the IBM cloud deployment and on some of the data centers that are very heavily used, there is a significant lag in the event stream, sometimes 10, 15 minutes behind, which makes the RCA impossible."

"Price-wise, the product is quite economical. I rate the solution's price as three or four on a scale of one to ten, where one is considered to be a very economically priced tool."

"The solution requires a huge infrastructure and that is costly."

"The pricing is based on the log size."