What is our primary use case?
I have been working with Wazuh for two years, and I can explain how I use Wazuh. I did not use Wazuh as a SIEM solution. I use Wazuh as a tool for services we provide. This service is called compromise assessment. I use Wazuh because Wazuh agent has EDR agent capabilities and some EDR capabilities on their agents. I use Wazuh beside some tools in my toolset. I implement deception engines using it.
Compromise assessment activity requires collecting logs and analyzing everything involved. Regarding threat detection capabilities, I speak honestly about it. When I say I use it for compromise assessment, I use it for that because Wazuh agent has great, very powerful capabilities to collect logs and correlate them against your environment to help detect threats or maybe future threats. Wazuh has an agent with EDR capabilities and some XDR capabilities also. That's why it's very good for me in terms of usage. It helps me in compromise assessment activity as a service we provide in our company.
I find the real-time dashboard in Wazuh to be very good, but I do not recommend Wazuh for day-to-day operations. I recommend it for fast activities. I do not recommend Wazuh for long-term use or building your own SOC based on it.
What is most valuable?
When we talk about functionality, the most valuable feature or function I have found in Wazuh is Wazuh EDR agent with EDR capabilities. This is the most valuable single feature in Wazuh - Wazuh agent capabilities.
In my opinion, the main benefit Wazuh provides to users is visibility into user behavior. If you use it well, taking advantage of all agent features and capabilities, and using your own rules, it will give you full visibility of user behavior and user activity through the network or the environment.
What needs improvement?
Regarding compliance, I find it not stable. I do not recommend it for that purpose. It can comply with Wazuh NCA, which we have here in Saudi Arabia. Wazuh NCA has many frameworks starting with ECC Essential Cybersecurity Controls, ending with controls about social media. They have their own frameworks and regulations, and Wazuh can comply with all Saudi regulations. However, in the long term, if you want to build a SOC center on Wazuh, I do not recommend it because it's not stable. It's not stable in the long term, especially with a huge amount of logs, day-to-day activity, or monitoring, log retention. For example, here in Wazuh ECC, we have one control we have to comply with that states you should have hot log retention for at least one year. It consumes a huge amount of resources from your storage; in a small client setup, it took more than three terabytes for me.
If I had to mention one area for improvement in Wazuh, it would be the hot log retention policies. They should reduce the volume and size of hot logs.
For how long have I used the solution?
I have been working with Wazuh for two years.
What do I think about the stability of the solution?
When it comes to stability, from one to ten, I would rate Wazuh a six. Wazuh reason I give it a six is that, during compromise assessment activity, I usually finish this activity in a maximum of four weeks, and I do not feel any issues regarding stability. However, the sizing and log retention issues make the stability of this product very bad. In one year, we faced about twelve tickets regarding the system going down due to storage issues. That is not a normal number for one year.
What do I think about the scalability of the solution?
As for scalability in Wazuh, I think it's scalable, and I would give it a seven.
How was the initial setup?
Wazuh initial setup is very, very easy.
In terms of deployment, I prefer to work on-premises. Here in Saudi Arabia, there are concerns about cloud services outside Wazuh country. They want everything in Wazuh cloud but inside Saudi Arabia, not outside it. For over five years, all my implementations have been on-prem. Now we only have Google Cloud and Alibaba Cloud; we still do not have Microsoft tenant availability in Saudi Arabia, but they claim it will be available next year. However, up until now, all my implementations are on-premises, and it's very, very easy and smooth.
Which other solutions did I evaluate?
If you want to build it with an open-source SIEM solution, you can build it on QRadar or ELK, which are good options.
Machine learning in Wazuh is very, very good, but for your knowledge, IBM QRadar significantly improved their UBA when it comes to machine learning and AI. Their focus is almost entirely on user behavior analytics. In QRadar, they concentrate on using machine learning algorithms and AI only for UBA.
What other advice do I have?
I do not work with Wazuh compliance management tools honestly.
I cannot speak about Wazuh pricing for Wazuh paid version since I do not know Wazuh price. It's totally on Wazuh client side to purchase Wazuh product. I usually use Wazuh open-source or free version because my day-to-day activities only involve providing one service that's dependent on Wazuh called compromise assessment. I use Wazuh as part of my toolset for that purpose, which includes deception engines and other tools.
My overall review rating for Wazuh is seven.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other