Overview

Product video
Wazuh is a free, open source and enterprise-ready security monitoring solution for threat detection, integrity monitoring, incident response, and regulatory compliance.
The solution includes the Wazuh server, which is in charge of analyzing the data received from the agents, processing events through decoders and rules, and using threat intelligence to look for well-known IOCs (Indicators Of Compromise). A single Wazuh server can analyze data from hundreds or thousands of agents. Alerts generated by Wazuh are sent to Wazuh indexer, where they are indexed and stored. The unique integration between Wazuh and Wazuh dashboard provides a powerful user interface for data visualization and analysis. The server is also used to manage the agents, configuring and upgrading them remotely when necessary. Additionally, the server is capable of sending orders to the agents, for example, to trigger a response when a threat is detected.
Wazuh provides a security solution capable of monitoring your infrastructure, detecting threats, intrusion attempts, system anomalies, poorly configured applications, and unauthorized user actions. It also provides a framework for incident response and compliance, all in one platform.
Highlights
- Open Source Security Platform
- Host Based Intrusion Detection Solution
- Endpoint Detection and Response
Details
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Dimensions summary
Top-of-mind questions for buyers
Vendor refund policy
We do not currently support refunds.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Additional details
Usage instructions
See the instructions below
Hardware requirements: https://documentation.wazuh.com/current/quickstart.html#hardware
The instance needs to have the following protocols and ports configured for its correct operation. These requirements are provided in a default Security Group: https://documentation.wazuh.com/current/getting-started/architecture.html#required-ports
To access the instance by ssh, you will need to use the user: wazuh-user
When the instance is launched, the user passwords are automatically changed to the instance ID with the first letter capitalized. For example: I-07f25f6afe4789342. This ensures that only the creator has access to the interface. This process can take an average of five minutes, depending on the type of instance. During this time, both SSH access and access to the Wazuh dashboard are disabled.
It is highly recommended to change the default passwords of Wazuh indexer users. To perform this action, see our Password management section: https://documentation.wazuh.com/current/user-manual/user-administration/password-management.html#changing-the-passwords-for-all-users
To access the Wazuh dashboard UI, navigate to the address https://<instance_ip> and log in with:
- Username: admin
- Password: <your_instance_id>
The password is the instance ID with the first letter capitalized. For example: I-07f25f6afe4789342
Resources
Vendor resources
Support
Vendor support
Wazuh has one of the largest open source security communities in the world. You can become part of it to learn from other users, participate in discussions, talk to our development team, and contribute to the project.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Similar products
Customer reviews
Hands-on SOC log monitoring, agent management, and alert triage
Highly customizable SIEM and XDR without the enterprise price tag
All-in-One Open-Source SIEM/XDR with Powerful Customization and Integrations
File integrity monitoring has strengthened our data protection and supports compliance needs
What is our primary use case?
Our organization is focusing on the integrity part for implementing Wazuh. We were checking solutions for File Integrity Monitoring systems that are available online. Wazuh caught my attention as a very cool solution for verifying file integrity. We decided to try Wazuh for focusing on the integrity part. While implementing it, our objective was achieved. We were able to monitor entire file integrity. Because our organization's business requires core concepts of integrity to be maintained, this was very important for us. Wazuh did this very well. We were not able to make it available to all endpoints. Instead, we tried it with servers. We changed our business requirements by storing all files that are processing into the server as a shared server and then we put File Integrity Monitoring and Wazuh in a single server. This worked out very well.
What is most valuable?
The dashboards in Wazuh are very cool and they provided whatever data is required.
I would give ten out of ten for the technical suggestion that I received from the documentation of Wazuh. The documentation provides everything that we are expecting. I have not tried any support from staff for Wazuh, but the documentation was very clear and I can give it ten out of ten.
What needs improvement?
I expected one thing from the dashboard in Wazuh. In ManageEngine, when you use ManageEngine, you can assign a unique ID to all employees. Then with the unique ID, if you search any unique ID in the dashboard itself, you can get the unique ID everywhere, including where the laptop has been logged in, when the logout happened, and what actions have been done for that unique ID. I expected the same in Wazuh, but whenever we want to check any monitoring activities for a specific person, we need to search for the endpoint and then get the endpoint details from our Active Directory or wherever we have the endpoint name stored in our resources, and then search for the endpoint to see the history for that specific endpoint only. This made a simple thing a bit complex. If we had a correlation of logs where I could just search one unique ID and then the unique ID pulls every system in a time-wise manner, that would be a great improvement I would suggest.
For how long have I used the solution?
I have been using Wazuh for around seven to eight months. In my previous organization, I was about to install and work with Wazuh. Since it is open source, I was fully configuring it for the organization.
What do I think about the scalability of the solution?
When we use a very good configuration laptop, it functions very smoothly. However, when we use low-end laptops for low-level employees, then the laptops become slow. This is because of the backend work the agent is collecting and processing, causing the laptop to slow down and the bandwidth to decrease.
Which solution did I use previously and why did I switch?
We had FortiNet and then we had McAfee.
What other advice do I have?
I have not worked very well with Wazuh's threat detection capabilities because we already had some solution in place. Our focus was to implement Wazuh for integrity only and File Integrity Monitoring only. I have worked earlier with Wazuh and ManageEngine. When I was working with Wazuh, there was no artificial intelligence introduced. My overall review rating for Wazuh is eight out of ten.