Arquitecto De Seguridad at a tech vendor with 10,001+ employees
Real User
Top 20
Aug 9, 2026
Dragos basically helped us get to know the entire infrastructure because there were many devices that not even the client themselves knew existed or that were still active, making it a very good tool; however, it requires a lot of hardware and knowledge, especially expertise from people who have worked in the industry and know security, which was lacking in the company where it was implemented, leading to lucky hits but ultimately prompting my decision to change companies. My advice to companies considering implementing Dragos is to evaluate the tool but ensure they have a person who truly understands the industry, what operates within their OT infrastructure, and cybersecurity expertise, rather than someone who has simply taken a course or has a casual connection selling them the product.
Risk detection is something where I identify that incident response planning is one of the options in risk detection, which has reduced to 18.5% from 40%. Using ICS visibility has helped a lot, and a 60% improvement has been done overall. There are some features like automated asset discovery where I have proper visibility of the vendor and model context, determining what is automated to that particular option or for banking usage. Protocol-aware detection tunes to iOS or IoT OT environments, knowing what protocols and what aware detections exist. If any improper detection happens, the protocol gives awareness that something is going wrong. Incident response playbooks guide investigations of what is happening across banking systems, especially servers and databases. Scalability is another important feature. It supports monitoring of hundreds of thousands of assets across multiple sites. More customers or different users who come and access different monitors, especially banking systems, have been enabled through this scalability. False positive reduction is another feature that understands behavior analytics tuned to OT protocols, minimizing alert fatigue. If false positive reductions or any deductions happen, they are tracked. Governance alignment has been very much improved in my organization by using Dragos. It supports formats like NERC, CIP, IEC, and standards called NIST and CFC compliances. These are government and governance compliance according to banking sector requirements based on unique identifiers and are always valid toward any system. Broad-level reporting provides risk scoring and incident records for audits. If any risk happens, I know what should be improved next time. If anything changes, I know what needs improvement. The reporting level, especially at board level in a high-level capacity controlling branches, especially from headquarters, is one of the benefits Dragos has provided. Operational resilience is another benefit where continuous monitoring of Dragos ensures reduced downtime and financial risk. Operational resilience is continuous monitoring. Metrics-wise, it helped me achieve downtime reduction of less than two hours of downtime per year for critical banking services. The Reserve Bank of India guidelines require banks to set impact tolerances for critical operations like payment processing. Recovery time objective helped me achieve under 30 minutes for core banking systems. Earlier it was around 3-4 hours and now it has reduced to 30 minutes. Dragos should be improved in deployment complexity as it requires OT engineering coordination. One needs to have proper engineering coordination to understand the system, deploy it, integrate it, and make all the complex things into one system. This is very challenging, and one should be really skillful and have experience to do that. Cost is another area for improvement as it is higher due to site-based licensing and expert services. The licensing is very heavy, and expert services are required. Integration needs alignment with IT security systems and compliance frameworks where controlling cybersecurity to prevent fraudulent persons or third parties from accessing the system is complex. Accuracy and dependency-wise, the tool is very accurate. The percentage of error-free transactions processed in banking achieving 99% is one of the most important metrics for millions of daily transactions. Fraud detection accuracy is another metric where AI-driven fraud helps identify and especially 95% of detection happens through this accuracy. Data accuracy, especially in KYC, helps banks identify what type of KYC information like ID proofs is present, avoiding regulatory penalties at 99% accuracy. Reliability-wise, the core banking system is always at 99.9% uptime and gives the right measures toward any customer. Mean time between failure (MTBF) is another metric where ATM networks achieve more than 5,000 plus hours. I use AWS cloud for my hybrid deployment and have purchased Dragos from the AWS marketplace. Dragos especially ensures systems recover quickly, providing resilience. It handles all the operational resilience in banking, with metrics of 99.9% uptime, 30 minutes recovery time, and 99% transaction accuracy. I would rate this review an 8 out of 10 overall.
I have experience managing the tools Clarity, Nozomi, Dragos, Sangfor, and I am familiar with these products. My customers are already working with Devo, Dragos, Nozomi, Clarity, and these are locally deployed in the client sites, not bought on the AWS Marketplace. I have not used Devo, but I have used Nozomi and Dragos, so I do have experience with those products. I completed my certification in Dragos and recommend it to my customers already, and I have been dealing with Dragos for a while now. Dragos offers a threat intelligence subscription called worldview, so if a customer subscribes to that, they will get regular threat intelligence. I have not used much of the detailed analytics and reporting functionalities of Dragos. Dragos is a good option to choose, as it performs well in the market. Dragos is a big name, and there is room for Dragos in the India market, and they should promote it more. The company that I'm working for is a partner with Dragos. I also have partnerships with other vendors including Clarity, Nozomi, and Fortinet. I was learning FortiSIEM three months back, but I am not certified in it, so I have been dealing with Fortinet products in a somewhat limited manner. FortiGate is what I mostly deal with from Fortinet. On a scale of 1-10, I would rate this solution a 6 or 6.5.
Dragos offers a comprehensive cybersecurity platform specializing in industrial control systems. It provides advanced threat detection and response capabilities tailored for sectors like energy, manufacturing, and water.Dragos enhances security by providing specialized solutions that address the unique vulnerabilities present in industrial environments. With a robust framework, it monitors networks for threats, offers advanced analytics, and delivers actionable insights. This makes it...
Dragos basically helped us get to know the entire infrastructure because there were many devices that not even the client themselves knew existed or that were still active, making it a very good tool; however, it requires a lot of hardware and knowledge, especially expertise from people who have worked in the industry and know security, which was lacking in the company where it was implemented, leading to lucky hits but ultimately prompting my decision to change companies. My advice to companies considering implementing Dragos is to evaluate the tool but ensure they have a person who truly understands the industry, what operates within their OT infrastructure, and cybersecurity expertise, rather than someone who has simply taken a course or has a casual connection selling them the product.
I have not used Dragos's AI capabilities before. I gave this review a rating of 8.
Risk detection is something where I identify that incident response planning is one of the options in risk detection, which has reduced to 18.5% from 40%. Using ICS visibility has helped a lot, and a 60% improvement has been done overall. There are some features like automated asset discovery where I have proper visibility of the vendor and model context, determining what is automated to that particular option or for banking usage. Protocol-aware detection tunes to iOS or IoT OT environments, knowing what protocols and what aware detections exist. If any improper detection happens, the protocol gives awareness that something is going wrong. Incident response playbooks guide investigations of what is happening across banking systems, especially servers and databases. Scalability is another important feature. It supports monitoring of hundreds of thousands of assets across multiple sites. More customers or different users who come and access different monitors, especially banking systems, have been enabled through this scalability. False positive reduction is another feature that understands behavior analytics tuned to OT protocols, minimizing alert fatigue. If false positive reductions or any deductions happen, they are tracked. Governance alignment has been very much improved in my organization by using Dragos. It supports formats like NERC, CIP, IEC, and standards called NIST and CFC compliances. These are government and governance compliance according to banking sector requirements based on unique identifiers and are always valid toward any system. Broad-level reporting provides risk scoring and incident records for audits. If any risk happens, I know what should be improved next time. If anything changes, I know what needs improvement. The reporting level, especially at board level in a high-level capacity controlling branches, especially from headquarters, is one of the benefits Dragos has provided. Operational resilience is another benefit where continuous monitoring of Dragos ensures reduced downtime and financial risk. Operational resilience is continuous monitoring. Metrics-wise, it helped me achieve downtime reduction of less than two hours of downtime per year for critical banking services. The Reserve Bank of India guidelines require banks to set impact tolerances for critical operations like payment processing. Recovery time objective helped me achieve under 30 minutes for core banking systems. Earlier it was around 3-4 hours and now it has reduced to 30 minutes. Dragos should be improved in deployment complexity as it requires OT engineering coordination. One needs to have proper engineering coordination to understand the system, deploy it, integrate it, and make all the complex things into one system. This is very challenging, and one should be really skillful and have experience to do that. Cost is another area for improvement as it is higher due to site-based licensing and expert services. The licensing is very heavy, and expert services are required. Integration needs alignment with IT security systems and compliance frameworks where controlling cybersecurity to prevent fraudulent persons or third parties from accessing the system is complex. Accuracy and dependency-wise, the tool is very accurate. The percentage of error-free transactions processed in banking achieving 99% is one of the most important metrics for millions of daily transactions. Fraud detection accuracy is another metric where AI-driven fraud helps identify and especially 95% of detection happens through this accuracy. Data accuracy, especially in KYC, helps banks identify what type of KYC information like ID proofs is present, avoiding regulatory penalties at 99% accuracy. Reliability-wise, the core banking system is always at 99.9% uptime and gives the right measures toward any customer. Mean time between failure (MTBF) is another metric where ATM networks achieve more than 5,000 plus hours. I use AWS cloud for my hybrid deployment and have purchased Dragos from the AWS marketplace. Dragos especially ensures systems recover quickly, providing resilience. It handles all the operational resilience in banking, with metrics of 99.9% uptime, 30 minutes recovery time, and 99% transaction accuracy. I would rate this review an 8 out of 10 overall.
I have experience managing the tools Clarity, Nozomi, Dragos, Sangfor, and I am familiar with these products. My customers are already working with Devo, Dragos, Nozomi, Clarity, and these are locally deployed in the client sites, not bought on the AWS Marketplace. I have not used Devo, but I have used Nozomi and Dragos, so I do have experience with those products. I completed my certification in Dragos and recommend it to my customers already, and I have been dealing with Dragos for a while now. Dragos offers a threat intelligence subscription called worldview, so if a customer subscribes to that, they will get regular threat intelligence. I have not used much of the detailed analytics and reporting functionalities of Dragos. Dragos is a good option to choose, as it performs well in the market. Dragos is a big name, and there is room for Dragos in the India market, and they should promote it more. The company that I'm working for is a partner with Dragos. I also have partnerships with other vendors including Clarity, Nozomi, and Fortinet. I was learning FortiSIEM three months back, but I am not certified in it, so I have been dealing with Fortinet products in a somewhat limited manner. FortiGate is what I mostly deal with from Fortinet. On a scale of 1-10, I would rate this solution a 6 or 6.5.
Overall, I would rate Dragos around nine. It is crucial to use anonymous information in reviews to avoid internal distractions.