A lot of people don't know about DNIF HYPERCLOUD, but they do know about products like Splunk, QRadar, ArcSight, and some other SIEM solutions. DNIF is not a known name in the market. From an improvement perspective, I feel that DNIF needs to invest more in marketing, considering that it operates at a very competitive speed.
Assistant Manager (information Security) at Tata Projects Limited
User
Dec 8, 2022
The EBA could be improved. The graphs and kill chain are not operational most of the time. Some dashboards are not showing data that is important to have for management review or meetings. The dashboard could be improved so that it is easy to understand, even for non-technical users. File integrity monitoring is missing. This may impact the data. A contingency plan should be shown against each risk to have a proper analysis of all risks in all aspects. Compliance should support log data for standards like HIPAA, ISO, PCI/DSS, HITECH, SOX, and GDPR and generate compliance reports.
Deputy General Manager - Information Security (Lead ISA) at a energy/utilities company with 1,001-5,000 employees
Real User
Nov 23, 2022
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.
The company was very dependent on the DNIF support team. Whenever we faced any backend issue in the software, we'd have to approach the support team. Unlike other SIEM tools where you can troubleshoot through the GUI, with DNIF they were all on LINUX platforms. Finding the log files and checking them had to be done manually and that was frustrating. In terms of integration, the company had a very limited list of devices that were supported on the go. They were out-of-the-box integrations that required forwarding logs to their server. Each time a new device was added, we had to request a new parcel for that device. I think things may have improved since I left the company.
Exec. VP & Head - IT at a consultancy with 11-50 employees
Real User
Mar 16, 2020
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. There needs to be more knowledge sharing with the team in order to develop out the product. The solution needs to come up with its own intelligent feeds. They had a form of tech management that they are probably not updating anymore. It's something they need to work on.
CEO at Irisk Assurance Consultancy Services Pvt Ltd
Real User
Mar 6, 2019
The solution should be able to connect to endpoints, such as desktops and laptops. Endpoints are also vulnerable to malware attacks and they generate a lot of logs. 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.
DNIF HYPERCLOUD provides efficient security monitoring with fast queries, user-friendly features, and built-in threat detection, offering open-source infrastructure support for improved performance.DNIF HYPERCLOUD integrates with network devices, servers, and applications for comprehensive log collection and security monitoring, enhancing compliance through unauthorized activity detection. Its scalability and real-time alerting align with the MITRE ATT&CK framework, making it valuable for...
A lot of people don't know about DNIF HYPERCLOUD, but they do know about products like Splunk, QRadar, ArcSight, and some other SIEM solutions. DNIF is not a known name in the market. From an improvement perspective, I feel that DNIF needs to invest more in marketing, considering that it operates at a very competitive speed.
The EBA could be improved. The graphs and kill chain are not operational most of the time. Some dashboards are not showing data that is important to have for management review or meetings. The dashboard could be improved so that it is easy to understand, even for non-technical users. File integrity monitoring is missing. This may impact the data. A contingency plan should be shown against each risk to have a proper analysis of all risks in all aspects. Compliance should support log data for standards like HIPAA, ISO, PCI/DSS, HITECH, SOX, and GDPR and generate compliance reports.
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.
The company was very dependent on the DNIF support team. Whenever we faced any backend issue in the software, we'd have to approach the support team. Unlike other SIEM tools where you can troubleshoot through the GUI, with DNIF they were all on LINUX platforms. Finding the log files and checking them had to be done manually and that was frustrating. In terms of integration, the company had a very limited list of devices that were supported on the go. They were out-of-the-box integrations that required forwarding logs to their server. Each time a new device was added, we had to request a new parcel for that device. I think things may have improved since I left the company.
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. There needs to be more knowledge sharing with the team in order to develop out the product. The solution needs to come up with its own intelligent feeds. They had a form of tech management that they are probably not updating anymore. It's something they need to work on.
The solution should be able to connect to endpoints, such as desktops and laptops. Endpoints are also vulnerable to malware attacks and they generate a lot of logs. 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.