What is our primary use case?
I primarily use Nozomi Networks for two main use cases in our environment: OT asset visibility and inventory management, as well as threat detection and anomaly monitoring, which is very important for our operations.
For OT asset visibility, in our compressor stations, we are connected to Nozomi via a span port in the Nozomi collector, and that collector sends data to Guardian, which we use there. With this setup, we can easily investigate our alert triggers. For threat detection at our pipeline block valve station, which is very useful for us, the baseline is the SCADA system, specifically the Honeywell SCADA we use. In this SCADA, periodical read commands on RTUs arrive, and sometimes these commands are unusual. For anomaly control command detection, which identifies unauthorized sources from different places, Nozomi is very helpful with Guardian as well as the CMC, which also shows us the dashboard.
Additional high-impact use cases for Nozomi Networks that I see in pipeline operations include Nozomi flagging some PLCs receiving new types of commands that we sometimes have never seen before. The inbuilt root cause analysis incidents and the IT/OT attack path vector detection are features I need to add to our use cases, making it much easier to maintain our window validation and related processes.
Regarding the learning curve for new users of Nozomi Networks in my organization, training is required, but the platform is user-friendly. I recommend training for all site locations, which is very helpful. The learning curve is moderate, and users can learn effectively with the necessary training.
Nozomi Networks plays a critical role in my environment for incident response and remediation by providing early detection, deep visibility, and actionable insights. In an OT environment, where responses must be controlled and careful, Nozomi proves to be invaluable, and I appreciate its capabilities.
How has it helped my organization?
Nozomi Networks has positively impacted our organization since we are in the asset owner environment. The first thing I noticed before was the lack of full OT visibility, which is the biggest impact to gain and understand more deeply our asset-related environment, and it is also facilitating faster threat detection and response, which I appreciate. This capability enables me to create a stronger incident response capability or response procedure for our OQGN environment, which is very helpful in reducing operational risks and enhancing our OQGN environment.
Regarding the reduction in operational risk, I have seen a significant example where the mean time to detect has reduced to minutes. Before, the mean time to detect was almost 30 minutes to one hour, but now it typically takes five to ten minutes, which is substantial. The response time has also reduced by 50 to 60 percent after implementing Nozomi Networks; those are the two key improvements I observe before and after its implementation.
Nozomi Networks significantly supports collaboration between IT and OT teams in my organization by providing a unified visibility platform. Both teams are able to see everything Nozomi offers on a single platform, the CMC, which I mentioned earlier. This facilitates our collaboration and provides actionable insights to our IT teams, helping maintain the operational context of our OT environment and coordinate effectively with the SIEM.
I have seen a clear return on investment with Nozomi Networks, as it measures and manages our risk reduction as well as operational continuity and efficiency. It significantly aids in time-saving; for example, before Nozomi, identifying the root cause of network or process issues took several hours or even days, especially with limited visibility for IT or OT teams. After implementing Nozomi Networks, those issues are resolved within minutes rather than hours due to real-time visibility and traffic analysis enabled by Nozomi Networks.
What is most valuable?
The best feature Nozomi Networks offers, in my opinion, is deep OT protocol intelligence, which is very effective for our OT environment. The second important feature is the agentless and passive OT visibility, which creates a very crucial role in critical environments because if you set up something inbuilt in your environment, it is not worth and not acceptable for all asset owners. Due to this reason, the third feature is the behavioral baseline with very low false positive alerts, which detects issues and does not show false alarms on the CMC dashboard.
Overall, Nozomi Networks is effective at identifying unknown threats or zero-day vulnerabilities. It has strong performance in that area, although I did encounter one case where something abnormal was not detected immediately. However, overall, it is strong for zero-day detection and unknown threat visibility, though the false positives remain a challenge that all organizations face, especially in the initial stages.
What needs improvement?
I see challenges with Nozomi Networks mainly as a detection or visibility tool, but it does not actively block traffic by design for safety reasons. If it detects any abnormalities, it suggests using firewalls, NAC, or manual actions at the time of threat detection. For deeper asset context beyond the network layer, it does not provide that for engineering systems, and sometimes it falls short in SMTP. The main challenges I have noted are cost and scaling considerations; sometimes, clients directly deny requests for additional integration due to Nozomi Networks' high costs.
Regarding Nozomi Networks' AI capabilities, I have a mixed opinion. On one hand, I think it is very effective and helpful in strengthening Nozomi Networks itself, but on the other hand, I see potential risks and gaps in governance that are easily detectable. For AI in governance, I recommend creating strong controls along with privacy awareness, data security, operational safety, and most importantly, AI transparency. Much transparency with limited external visibility would be beneficial.
Integrating Nozomi Networks with our existing systems was relatively easy at level three due to established tie-ups, but I faced issues when integrating at level two with some OEMs, like Emerson, who do not allow deep dives for monitoring and collecting all data from Nozomi Networks from the tap one.
For how long have I used the solution?
I have been using Nozomi Networks for almost more than four years.
What do I think about the stability of the solution?
Nozomi Networks has proven to be very stable and comfortable in my experience.
What do I think about the scalability of the solution?
In terms of scalability, Nozomi Networks is well-suited for large-scale OT environments, accommodating hundreds and thousands of assets and nodes. This suitability applies particularly to the oil and gas sector as well as manufacturing and utilities, so my recommendation is that it has very high scalability capacity, ease of scaling, and flexibility.
How are customer service and support?
In the Middle East, the customer support provided by Nozomi Networks is very good. However, I personally faced some minor delays a couple of times, but they were acceptable and not much of an issue.
Which solution did I use previously and why did I switch?
I worked with different organizations and used various solutions previously, including Armis, Microsoft Defender for IoT, and Claroty. There was no particular reason to switch solutions because I simply changed organizations, which used different solutions for their IDS and IPS.
How was the initial setup?
Nozomi Networks is easy to manage updates and maintenance for since it is deployed on-premises, providing us internal control. This offers flexibility, but it also requires proper planning and coordination with Nozomi Networks vendors and teams directly involved in integration. This makes it helpful to manage manual efforts effectively and supports our critical infrastructure environment.
What's my experience with pricing, setup cost, and licensing?
My experience with Nozomi Networks in terms of pricing and licensing is that it is generally a premium solution, not a standard one for all organizational needs. It is more than a typical premium solution, specifically focused on IT and OT systems in our critical infrastructure environment. The pricing is slightly high, which influences smaller organizations' decisions against implementing Nozomi Networks.
Which other solutions did I evaluate?
Prior to choosing Nozomi Networks, I evaluated a few options, including Claroty, which I deemed not considerable in the Middle East. I also looked at Armis, where I found limited visibility and poor service in the region, and Dragos, which has higher pricing compared to Nozomi Networks. Therefore, I recommended implementing Nozomi Networks for our needs at OQGN.
What other advice do I have?
I rate Nozomi Networks overall a nine out of ten.
I give it a nine because, while it excels not just for asset inventory detection and related areas, there is one gap I have noted and shared with you. That is why I deduct a point, making my rating nine out of ten.
For me, Nozomi Networks has high reliability and moderate to high accuracy, which I believe is the right trade-off for our OT environment.
I advise others looking into using Nozomi Networks that it is scalable and provides excellent support and services, so I recommend configuring Nozomi Networks in your environment, whether for large-scale or small-scale industries.
Which deployment model are you using for this solution?
On-premises