DNIF HYPERCLOUD vs ManageEngine Log360 comparison

"The most valuable feature of the solution is the number of EPS it can handle."

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

"I like the MITRE table, a feature I saw for the first time in the same solution. There was one MITRE tactic table, which can be used to identify threats if you have all kinds of rules enabled or if you have rules for all the tactics in the MITRE table. There are 14 tables in MITRE, and those 14 tables consist of multiple columns, tactics, and techniques. It was one of the first SIEM tools I saw that had that particular MITRE table. On that basis, you can create new rules and identify existing ones. At any point, if an alert is triggered, it will try to match it to any of those MITRE tactics. I liked that creating a workbook on MITRE business was straightforward. I also like that you can search using SQL or DQL."

"The response time on queries is super-fast."

"Great for scaling productivity for log monitoring purposes."

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

"Has a great search capability."

"The beauty of the solution is that you can develop infrastructure for a data lake using open sources that are separate from the licenses."

"My main objective for using ManageEngine Log360 is its powerful and real-time capabilities for managing security and other tasks efficiently."

"It basically helps us. We have to stay in compliance with certain issues with some of our customers. We have to have these types of tools in place for protecting our network and our data. We're in the aerospace industry, so we have a lot of defense contracts. So, all those guys will make sure that we're protecting their information, and it does a good job in that aspect."

"The most valuable features for us are the application logs monitoring and the dashboard, which provides a single-pane view of all the ongoing activities."

"The most valuable feature is that this solution is more secure than others, and there are more applications and features as well."

"The reporting is great. Everything you need is in the report for you already."

"The product is very user-friendly."

"You can have all of the logs from servers to network and it gets sent out to the correct owners. This is very helpful."

"ManageEngine Log360 is not difficult to deploy."

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

"The EBA could be improved."

"The vendor is fairly new and it's not as big as some of the international competitors. It's not a mature product. If you ask them to move data, it might take a lot of time."

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

"Dependency on the DNIF support team was frustrating."

"The solution's command line should be simpler so that routine commands can be used."

"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... If this solution had a smart connector to these logs- Windows, Linux, or any other logs - without affecting the performance of the connector, that would be wonderful."

"While ManageEngine Log360 is a significant improvement, there could be enhancements in terms of integrating more user-friendly training materials and better deployment documentation."

"The solution needs to improve hub storage. It should integrate AI and ML capabilities."

"Log360 currently cannot gather information from Intune logs or cloud-integrated systems."

"The graphical interface could be made easier to use when you are connecting to different network equipment."

"We can log in as a local user, and it's fine, but when we login with an Active Directory user, we cannot."

"Most times log sheets are not assigned well."

"The integration with SharePoint and Teams should be improved."

"It is not expensive compared to other solutions."

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

"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 pricing is based on the log size."

"Its pricing is definitely huge compared to some of the other SIEMs. Its price should be improved."

"My client has a yearly license. I think the cost is not expensive compared to that of other SIEMs, given the service it is providing."

"Affordable pricing is provided by the solution."

"ManageEngine Log360 is expensive compared to other products."

"There is a cost for each feature used."