This final episode compares Wazuh with Elastic Security, Security Onion, Splunk, Graylog, and commercial EDR, then guides you in choosing based on needs from homelab to enterprise. We also put together a production checklist, recap the entire series journey, and list further learning resources.

In episode 21 we looked at the future of Wazuh and the 5.0 roadmap. Now comes the finale of this series. In episode 22 we pull all the threads together into one complete picture: where Wazuh stands among other security tools, when you should choose it, and how to close out a project with a real production checklist.
Before choosing a tool, always ask about needs first, not trends. You already have a fairly deep understanding of Wazuh after 21 episodes, and that's valuable capital for honestly assessing alternatives. There's no one tool that's perfect for every condition; there are tools that are right for specific needs.
In this final episode we discuss comparisons with several popular tools, the open source advantages of Wazuh, guidance on when to choose it, a production checklist, a recap of the journey, and learning resources to keep growing. At this point, you've become a practitioner who can stand on your own.
Elastic Security is a security product family from the makers of Elasticsearch, using a technology base similar to the Wazuh indexer. Both handle logs, detection, and dashboards. The striking difference is focus: Wazuh ships a multi-platform agent with FIM, SCA, vulnerability detection, and active response in one integrated package.
Elastic Security excels in a broad analytics ecosystem and integration with other Elastic products, but many of its advanced security features sit behind paid licenses. Wazuh offers those XDR features for free. For organizations that want one unified platform without per-feature license costs, Wazuh is often more attractive.
On the other hand, teams already heavily invested in the Elastic Stack may find it more efficient to continue with Elastic Security. The final decision depends on budget, team expertise, and how deep your analytics needs are.
Security Onion is a complete Linux distribution for network security monitoring, bundling many tools like Suricata, Zeek, and a log search interface in one pre-assembled distro. Its strength lies in very rich network visibility, while Wazuh focuses more on endpoint and workload visibility.
Graylog is a strong log management platform for centralizing and searching logs from various sources. It's great as a log management hub, but its agent and XDR features aren't as complete as Wazuh's. Many deployments actually use both complementarily: Graylog for general log management, Wazuh for unified security detection.
Among these three tools, Wazuh sits in the middle: not as big as Security Onion for networks, not as specialized as Graylog for logs alone, but the most balanced as an all-in-one SIEM and XDR for endpoints.
On the commercial side, there are enterprise SIEMs like Splunk and Splunk ES, plus top-tier EDRs like SentinelOne and CrowdStrike. Splunk is known for its flexible queries and mature enterprise ecosystem, but its licensing cost is based on data volume and can balloon as logs grow.
SentinelOne and CrowdStrike excel at endpoint-level prevention and detection, with very light agents and fast response capabilities. However, neither is a SIEM: you still need a separate tool to receive logs from firewalls, cloud, and other systems. Their cost is also per endpoint, which can be enormous for thousands of machines.
A common pattern in large organizations is combining both: a commercial EDR on the most critical endpoints, while a SIEM like Wazuh or Splunk becomes the aggregation hub for all telemetry.
Wazuh's main advantage comes precisely from its status as an open source project. It's free to use with no limit on the number of agents or features, and development is active with regular releases as we saw in previous episodes. Its community is large, so documentation, forums, and implementation examples are easy to find.
Transparency is also an important value for security teams. Code that can be read and audited gives confidence that there are no hidden functions, and organizations with custom needs can change behavior according to internal rules. There's no vendor lock-in, and integrations with TheHive, Shuffle, or other tools can be built yourself.
That doesn't mean open source is totally free in terms of operational cost. You still spend on servers, admin time, and maintenance effort. But compared to per-endpoint or per-GB commercial licenses, the position is very different.
Wazuh is a very sensible choice for homelabs and small-to-medium organizations. One all-in-one server is enough for dozens to hundreds of agents, and there's no license cost blocking experimentation. It's also the best learning path for understanding how SIEM and XDR work.
For enterprise, Wazuh can be a strong SOC foundation, especially combined with TheHive for incident management and Shuffle for automation, as we built in episode 18. Organizations with the most advanced endpoint prevention needs can layer Wazuh with a commercial EDR on the most sensitive assets.
Conversely, if you need a very deep analytics ecosystem, a team already trained on a specific tool, or contractual vendor support, commercial solutions can be more appropriate. The key is making decisions based on needs, not brands.
To close out this series, here's a checklist for bringing your Wazuh to a production-worthy level:
A few useful commands for routine verification:
systemctl status wazuh-manager
systemctl status wazuh-indexer
systemctl status wazuh-dashboardRun this checklist periodically, not just once at initial deployment. Security is a continuous process, and a healthy Wazuh is the result of habits, not luck.
Let's trace the thread from episodes 0 to 21. You started with an introduction to Wazuh and the manager, indexer, and agent architecture, then built an all-in-one installation and enrolled the first agent. From there you understood log monitoring, rules and decoders, up to FIM for file integrity.
The journey continued to active response and malware detection, vulnerability detection, security configuration assessment, up to compliance with PCI DSS, NIST, HIPAA, and GDPR. You also explored cloud security for AWS, Azure, and GCP, plus Docker and Kubernetes integration.
At the end, you built a distributed architecture and cluster, secured the API, understood communication encryption, wrote custom rules, connected TheHive and Shuffle, tuned performance, monitored and backed up Wazuh, and read the 5.0 roadmap. All of that forms one complete capability that few people possess.
The journey isn't over. Some resources you can make your learning companions:
Pick one topic that doesn't yet feel solid and revisit it from the original source. Learning security always cycles between theory and practice, and you already have the foundation to walk both.
We've traveled 22 episodes together. You now understand Wazuh not just as software, but as a way of thinking about security detection and response: from logs that look innocent, to the big decisions that save an organization. Reaching this far is no small achievement.
Thank you for joining this journey. Keep experimenting, document what you learn, and share it with the community. What you need now is no longer a step-by-step guide, but an unquenchable curiosity and the discipline to keep practicing.
Key takeaways: