No more typing reviews! Try our Samantha, our new voice AI agent.

DNIF HYPERCLOUD vs Logpoint comparison

Why PeerSpot?
Sponsored
 

Comparison Buyer's Guide

Executive SummaryUpdated on Sep 18, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Torq
Sponsored
Average Rating
8.8
Reviews Sentiment
6.6
Number of Reviews
20
Ranking in other categories
AI-SOC (1st), AI-Powered Security Automation (1st)
DNIF HYPERCLOUD
Average Rating
7.6
Reviews Sentiment
6.7
Number of Reviews
8
Ranking in other categories
Log Management (42nd), Security Information and Event Management (SIEM) (46th), User Entity Behavior Analytics (UEBA) (20th), Security Orchestration Automation and Response (SOAR) (28th)
Logpoint
Average Rating
7.6
Reviews Sentiment
6.7
Number of Reviews
24
Ranking in other categories
Log Management (33rd), Security Information and Event Management (SIEM) (29th), User Entity Behavior Analytics (UEBA) (14th), Endpoint Detection and Response (EDR) (39th), Security Orchestration Automation and Response (SOAR) (20th)
 

Featured Reviews

AD
Solutions Architect at ProArch
Automation has streamlined multi-tenant SOC workflows and improves alert handling efficiency
Although the reporting within Torq is not that great, we did ask for many features regarding reporting in Torq, but due to some platform constraints, they could not make the whole dataset available for us to be used in reporting. Except for that, we used some basic reporting. When I used Torq, it was indeed in the early stages of AI capabilities. Only a few customers were allowed to use it, and we were among them. It functioned well as long as we summarized the data properly. If you input garbage, you would get garbage out. Thus, we had to do significant fine-tuning regarding what data context we provided to the AI orchestrator to get meaningful results. In terms of Torq's unified platform approach to AI SOC automation and case management compared to managing multiple point solutions across my security stack, I find it case-centric. The unified view in case management is good since it provides clarity, although there are limitations regarding how many items in case management can be modified at once. Bulk operations are very limited, potentially due to their back-end database or data retrieval processes that can be improved. Regarding improvements for Torq, when we were onboarded, there were aspects we were uncertain about, such as the number of cases that could be generated, what data we could bring in, how many clients we could onboard, and similar concerns. Initially, we also lacked clarity about the number of playbooks or workflows we could build. Different triggers like system triggers, case-based triggers, and others can be employed without restrictions, but when it comes to on-demand and scheduled jobs, there is a limitation based on the subscription and pricing tier that notably caps the number of workflows we can create. No bulk editing across cases was one issue, along with limited filtering related to single grouping constraints. Additionally, the out-of-the-box case templates provided require substantial modifications before they become usable. There is also a feature in the cases for notes that cannot be searched. They are only visible through the UI, which is another area for improvement. The workflow and execution-based charges seem misleading as this was not discussed initially. I am not sure if new customers are made aware of this. It seems that workflows revolving around cases hinder functionality outside of case management, as we have many use cases needing on-demand triggers and schedules for functions like reporting or polling devices. Creating additional workflows to achieve basic functionalities raises costs significantly, which disadvantages customers. While they facilitate optimization and scaling, the support received tends to be very basic. Improvements can be made in that area as well.
Kishore Tiwari - PeerSpot reviewer
Deputy General Manager - Information Security (Lead ISA) at a energy/utilities company with 1,001-5,000 employees
Development from open sources is very valuable but a huge infrastructure is required
The solution's command line should be simpler so that routine commands can be used. The search configuration is a bit different than other OEMs or SIEM solutions like ArcSight or QRadar that are easy to search because they operate similarly. The logic is there and the solution supplies a pretty good explanation. Basically, DNIF spelled out is the opposite of FIND. You have to find commands whenever you want to search something. For example, a highway gets you to your destination but there is an alternate way people don't yet know about. Gartner or Forrester haven't yet studied it. We were a bit nervous when we were trying to get familiar with the solution. We wondered if we could realize ROI because the commands and ways of pulling data were different to us. We raised a case with the support team and their professionals provided the needed support. The command line is user friendly once you understand it. If you need immediate use, then you might want to get assistance from someone who is well-versed in methods for using key patterns to find things. Lengthier files for threat hunting or analysis are needed. The correlation happens, but exporting a large number of files to abstract them is not possible. For example, I want to present raw data to management so I should be able to customize a date range in my query and download the files.
Rifat Hasan - PeerSpot reviewer
System Engineer at Corporate Projukti Limited
Has lacked proper integration and consistent support communication
I selected Logpoint for the pricing as it is reasonable. I am located in Bangladesh, South Asia, Dhaka. I have tried to contact Exabeam by mail repeatedly, but there has been no response. My company, Corporate Projukti Limited, including my Bangladesh area head, technical director, and team manager, have sent emails to contact Exabeam solution, but there is no response. There is already a distributor in Bangladesh. The weakness with Logpoint is UEBA. UEBA is recommended, but not extra. Exabeam's UEBA is an extra feature. SOAR is extra, but Logpoint's product measurement is 40 or 50. There is a 10% difference with the UEBA and SOAR, so Logpoint is weak there. I would appreciate extra features in Logpoint such as SOAR. SOAR and UEBA are included features in Logpoint. Logpoint's UEBA is a weak point, while Exabeam's UEBA has extra AI through automation. Exabeam has a license included, and the extra license is an add-on. In Logpoint, it is included, which makes it a weak point.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Torq has exceeded expectations by delivering workflows in a timely and lower effort manner than XSOAR, and it meets all my needs while saving a ton of time and targeting $600,000 saved this year, which is a substantial amount of money."
"What I liked the most about Torq is the actual workflow builder, which is really great because they offer a lot of features and convenience features that are useful for any automation engineer."
"Torq offers the best feature through integration with AI."
"Almost four or five hours of work is now completed in four or five minutes."
"Torq has changed the day-to-day experience for my security analysts and me by saving literally thousands of man-hours per month since we have implemented some of these use cases."
"With Torq, I automate actions while achieving SLA compliance and streamline alert investigation processes much better."
"Under one SOC tool in Torq, analysts get to know everything within the context of an alert or incident they are working on, and this ability to view the whole picture within Torq is one of the major breakthroughs and best offerings of Torq."
"Using that one piece of AI, we auto-closed 511 cases in quarter four alone."
"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."
"Great for scaling productivity for log monitoring purposes."
"The benefit of DNIF was that the solution was able to detect any anomalies and identify and prevent any possible security threats or attacks."
"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."
"It was one of the first SIEM tools I saw that had that particular MITRE table."
"The beauty of the solution is that you can develop infrastructure for a data lake using open sources that are separate from the licenses."
"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."
"Has a great search capability."
"The search feature is valuable. The dashboards are also valuable for our bosses. Another valuable feature, which is the main feature of the product, is the centralization of all the logs."
"Technical support is responsive and very friendly."
"It is a very comprehensive solution for gathering data. It has got a lot of capabilities for collecting logs from different systems. Logs are notoriously difficult to collect because they come in all formats. LogPoint has a very sophisticated mechanism for you to be able to connect to or listen to a system, get the data, and parse it. Logs come in text formats that are not easily parseable because all logs are not the same, but with LogPoint, you can define a policy for collecting the data. You can create a parser very quickly to get the logs into a structured mechanism so that you can analyze them."
"The UEBA component, as well as the SOAR component, are some of the most valuable features of Logpoint."
"The most beneficial was being able to prove, with proper reports, that from a compliance perspective, the company is in control. The service part of LogPoint did modifications or did some additional work to have the proper reports defined."
"Log collection, dashboards and reporting are good."
"The flexibility of the search feature and the solution's analytics features are the most valuable parts of the solution, and it's also very user-friendly."
"The integration is very user-friendly. There are not many CLI commands. Everything is directly accessible from the web interface."
 

Cons

"Even now, we have workflows that are in production that use AI steps and I get different results, making it unusable to some degree."
"There are some issues and bugs that I think need to be fixed, but they are currently not focused on it."
"It was able to capture data but was unable to differentiate between the agent hostname we are using and the hostname that resides on the back end of the Internet."
"Additionally, the documentation for Torq is not very clear. Most of the information is presented in videos, which are not ideal for reading; there are mostly paragraphs and other text-based content."
"Torq can probably use more ML and look at what can be closed and what cannot be closed in terms of data classification."
"The workflow and execution-based charges seem misleading as this was not discussed initially, and creating additional workflows to achieve basic functionalities raises costs significantly, which disadvantages customers."
"Regarding the pricing of Torq, I would say it is expensive."
"What has not worked as well as I hoped with Torq is related to product data management and storing data, although it still provides faster response and saves time."
"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."
"We have some issues with machine learning plug-ins and I believe they're working on a solution for that."
"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 should be able to connect to endpoints, such as desktops and laptops."
"There are currently some issues with machine learning plug-ins."
"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."
"The EBA could be improved."
"One of the things we faced last year was that we had some memory issues with the server running. We were running them as virtual services, and we were facing some performance issues. Back then, there were some things that had already been solved at the end, but one of the small issues we had was that it was quite memory-consuming. After one upgrade that we did, we faced some performance issues."
"Dashboards could be developed further."
"The interface needs things like wizards that will assist with creating complex correlation rules."
"Logpoint is not flexible. Its documentation is not user-friendly."
"I know that they have user behavior analytics, but it's an extra cost for this feature. It would be nice if it was in with the standard products."
"The thing that makes it a little bit challenging is when you run into a situation where you have logs that are not easily parsable."
"My issues with the product are mainly with regard to how it handles collecting logs."
"The thing that makes it a little bit challenging is when you run into a situation where you have logs that are not easily parsable. If a log has a very specific structure, it is very easy to parse and create a parser for it, but if a log has a free form, meaning that it is of any length or it can change at any time, handling such a log is very challenging, not just in LogPoint but also in everything else. Everybody struggles with that scenario, and LogPoint is also in the same boat. One-third of logs are of free form or not of a specific length, and you can run into situations where it is almost impossible to parse the log, even if they try to help you. It is just the nature of the beast."
 

Pricing and Cost Advice

Information not available
"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."
"The solution requires a huge infrastructure and that is costly."
"It was on a yearly basis at about $100K. It was not a huge environment. We were running it on our own virtual server environment, which, of course, had a cost. There was hardware and some energy cost, and then there were Microsoft Windows licenses for servers. That's all, but there was nothing in comparison to the licensing costs."
"Logpoint's pricing is mid-ranged and depends on the number of devices."
"Our licensing fees are about $10,000 USD per month, which I think is fair."
"On a scale of one to ten, where one is cheap, and ten is expensive, I would rate LogPoint's pricing a seven. It is not very expensive compared to some of the more costly products, and it is not very cheap compared to some of the cheaper products in the SIEM market."
"My company used to pay for LogPoint costs annually. It's a cost-effective solution. I'm not part of the Finance team, though, so I'm not sure exactly what the licensing fee is or what license my company had."
"It has a fixed price, which is what I like about LogPoint. I bought the system and paid for it, and I pay maintenance. It is not a consumption model. Most SIEMs or most of the log management systems are consumption-based, which means that you pay for how many logs you have in the system. That's a real problem because logs can grow very quickly in different circumstances, and when you have a variable price model, you never know what you're going to pay. Splunk is notoriously expensive for that reason. If you use Splunk or QRadar, it becomes expensive because there are not just the logs; you also have to parse the logs and create indexes. Those indexes can be very expensive in terms of space. Therefore, if they charge you by this space, you can end up paying a significant amount of money. It can be more than what you expect to pay. I like the fact that LogPoint has a fixed cost. I know what I'm going to pay on a yearly basis. I pay that, and I pay the maintenance, and I just make it work."
"For a hundred user deployment the cost is about $10,000. The next year it would be the same because it's a subscription-based license. There are separate costs as well, for example, if a customer asks for training for their staff."
"LogPoint seemed like it was a good product, but it was expensive and there wasn't any room to move the pricing when customers needed a lower-costing solution."
report
Use our free recommendation engine to learn which Security Information and Event Management (SIEM) solutions are best for your needs.
920,769 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
11%
Outsourcing Company
11%
Comms Service Provider
11%
Manufacturing Company
10%
Construction Company
14%
Outsourcing Company
14%
Comms Service Provider
11%
Financial Services Firm
8%
Construction Company
14%
Outsourcing Company
12%
Manufacturing Company
11%
Comms Service Provider
11%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise6
Large Enterprise13
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise1
Large Enterprise3
By reviewers
Company SizeCount
Small Business18
Midsize Enterprise3
Large Enterprise4
 

Questions from the Community

What needs improvement with Torq?
What has not worked as well as I hoped with Torq is related to product data management and storing data, although it ...
What is your primary use case for Torq?
My main use case for Torq is for managing IT services and providing faster response.
What advice do you have for others considering Torq?
I would rate Torq a 10 on a scale of 1 to 10. I chose this rating because customer service is excellent. I suggest to...
Ask a question
Earn 20 points
What is your experience regarding pricing and costs for LogPoint?
I rate the pricing at eight, suggesting it's relatively good or affordable.
What needs improvement with LogPoint?
I selected Logpoint for the pricing as it is reasonable. I am located in Bangladesh, South Asia, Dhaka. I have tried ...
What is your primary use case for LogPoint?
I had experience with Logpoint before, and I contacted the Exabeam solution, but there was no response; they did not ...
 

Overview

 

Sample Customers

Information Not Available
Mahindra & Mahindra, Tata Consultancy Services (TCS), ICICI Bank, Yes Bank, Tata Motors, RBL Bank
AP Pension, Copenhagen Airports, KMD, Terma, DISA, Danish Crown, Durham City Council, Game, TopDanmark, Lahti Energia, Energi Midt, Synoptik, Eissmann Group Automotive, Aligro, CG50...
Find out what your peers are saying about DNIF HYPERCLOUD vs. Logpoint and other solutions. Updated: October 2026.
920,769 professionals have used our research since 2012.