Duty analyst on shift

UK Cyber Defence

Wazuh consulting · Guide · Installation

How to install Wazuh:a step-by-step guidefor UK organisations

Wazuh is a free, open-source security platform that collects logs and events from servers, laptops and cloud services, detects threats and raises alerts. Installing it is the easy part: on a suitable server the installation assistant finishes in well under an hour. This guide covers the decisions that come first, the installation itself with the commands, enrolling agents, the security settings to change before anything goes live, the checks that prove alerts work, and an honest view of the effort needed afterwards.

Wazuh 4.14Updated November 2026Commands includedHardening and validation

01The short answer

A Wazuh installation takes an hour. Making it a working security monitoring service takes planning, hardening, tuning and someone to read the alerts.

For a small estate, a single Linux server with 4 vCPUs and 8 GiB of memory, and one command, will give you a working Wazuh indexer, server and dashboard. Agents are then installed on each machine you want to watch. What decides whether the result protects anyone is the work around that command: which systems and logs to include, how long to keep data, how the platform itself is secured, whether the alerts are tested, and who responds when one fires at three in the morning. This guide is written for the IT manager or engineer doing the work, and for the person deciding whether to do it in-house at all.

Current release
Wazuh 4.14, with 4.14.10 the latest when this guide was checked
Components
Indexer, server (manager), dashboard, and an agent on each monitored machine
Quickest route
The installation assistant, all components on one host
Real effort
Tuning, updates, storage and responding to alerts, every day

50 GB

Storage Wazuh suggests for 90 days of data from up to 25 agents on a single server

14 days

Median time an attacker went undetected inside an organisation in 2025

29 min

Average time for a criminal intruder to move beyond the first machine

40%

Of our SOC's investigations were raised outside UK office hours

  1. Storage Wazuh suggests for 90 days of data from up to 25 agents on a single server: Wazuh 4.14 quickstart requirements
  2. Median time an attacker went undetected inside an organisation in 2025: Mandiant M-Trends 2026
  3. Average time for a criminal intruder to move beyond the first machine: CrowdStrike 2026 Global Threat Report
  4. Of our SOC's investigations were raised outside UK office hours: UK Cyber Defence SOC, August to October 2026, 25 of 63

Plan first

Plan the Wazuh installation before you run anything

Wazuh has four parts. The indexer stores and searches the alerts and events. The server, also called the manager, receives data from agents, decodes it and applies the detection rules. The dashboard is the web interface. The agent runs on each endpoint or server you want to monitor and sends its logs, file changes, inventory and configuration checks to the server. Network devices and some cloud services send logs without an agent, by syslog or through an integration.

Settle these questions before the first command:

  • What you will monitor. Servers, laptops, domain controllers, firewalls, Microsoft 365, cloud accounts. The list sets the size of the platform and the work of onboarding.
  • How long you will keep data. Retention drives storage more than anything else. Decide it with whoever owns your data protection obligations: security logs contain personal data under the UK GDPR, so keep what you need for security and no more, and write the period down.
  • Where it will run. On your own servers, in a UK cloud region, or as a hosted service. For many UK organisations the location of the data is part of the decision.
  • Who will look at the alerts. If the honest answer is "nobody out of hours", plan for that now rather than after the first incident.

Hardware for a single-server installation

Wazuh's quickstart gives these figures for all components on one host, with 90 days of data:

AgentsCPUMemoryStorage (90 days)
1 to 254 vCPU8 GiB50 GB
26 to 508 vCPU8 GiB100 GB
51 to 1008 vCPU8 GiB200 GB

Beyond about 100 agents, or where you need resilience, Wazuh recommends a distributed deployment with clusters of servers and indexers. Treat the figures as a starting point: a busy domain controller or firewall can produce more data than fifty quiet laptops.

Operating system

The central components need 64-bit Linux on Intel, AMD or ARM processors. Supported systems include Ubuntu 22.04 and 24.04, Red Hat Enterprise Linux 8, 9 and 10, CentOS Stream 10 and Amazon Linux 2023. Use a current long-term support release, a dedicated host with nothing else on it, and the operating system's own hardening baseline before Wazuh goes on.

Network ports

ComponentPortPurposeWho needs to reach it
Server1514/TCPAgent connectionEvery agent
Server1515/TCPAgent enrolmentNew agents, during enrolment
Server1516/TCPCluster communicationOther Wazuh servers only
Server514/UDP or TCPSyslog collection, off by defaultNetwork devices that send syslog
Server55000/TCPWazuh APIThe dashboard and administrators only
Indexer9200/TCPIndexer APIWazuh components only
Indexer9300 to 9400/TCPIndexer clusterOther indexers only
Dashboard443/TCPWeb interfaceAdministrators and analysts only

Deployment options

Wazuh deployment options compared

OptionWhat it isSuits
All-in-oneIndexer, server and dashboard on one host, installed by the assistantUp to about 100 agents, pilots, smaller organisations
DistributedSeparate hosts or clusters for indexer, server and dashboardLarger estates, resilience, high event volumes
DockerOfficial container images, single-node or multi-nodeTeams already running containers who want repeatable builds
KubernetesOfficial deployment manifests for a clusterOrganisations with an existing Kubernetes platform and skills
Virtual machine or cloud imageA pre-built virtual appliance or cloud machine imageEvaluation and labs; harden before any production use
Wazuh CloudWazuh's own hosted service, paid forOrganisations that want the platform without running servers
AutomationAnsible and Puppet roles from WazuhRepeatable builds and changes across several environments

Not every part has to be Wazuh's. Detection happens in the manager; the indexer and dashboard can be replaced. Our own SOC uses the Wazuh manager as its signal and alert engine throughout, but stores the data in Graylog in place of the Wazuh indexer, for better scaling at the data lake level, and uses a front end we wrote ourselves. That suits a SOC serving many clients. For a single organisation the standard components are the simpler choice, and they are what this guide installs. Our Wazuh and Graylog guide explains the alternative.

Which version? Install the current 4.x release for anything in production. Wazuh 5.0, a major redesign, had reached release candidate stage by October 2026 but was not yet generally available when this guide was checked, and its documentation says an in-place upgrade from 4.x is not supported. Our Wazuh consulting page sets out what 5.0 changes and when to plan the move.

Installation

Step by step: installing Wazuh with the installation assistant

These steps are for an all-in-one installation of Wazuh 4.14 on a fresh Ubuntu 24.04 LTS server. Run them as a user with sudo rights, on a host that has its operating system updates applied, a fixed IP address and a DNS name, and accurate time from NTP. Check the commands against Wazuh's current documentation before you run them: version numbers in the paths change with each release.

1. Download and run the assistant

curl -sO https://packages.wazuh.com/4.14/wazuh-install.sh
sudo bash ./wazuh-install.sh -a

The -a option installs and configures all three central components on this host. The assistant checks the hardware, generates certificates, installs the packages and starts the services. At the end it prints the dashboard address, the admin user name and a generated password.

2. Keep the generated passwords safe

The passwords for every built-in user are stored in an archive in the directory where you ran the assistant. To read them:

sudo tar -O -xvf wazuh-install-files.tar wazuh-install-files/wazuh-passwords.txt

Move them into your password manager, then remove the archive from the server or restrict it so that only administrators can read it.

3. Sign in and check the services

Browse to https://<server-name> and sign in as admin. The browser will warn about the certificate until you replace it, which is covered below. On the server, check that all three services are running:

sudo systemctl status wazuh-indexer wazuh-manager wazuh-dashboard

4. Stop unplanned upgrades

Wazuh recommends disabling its package repository after installation, so that routine operating system updates do not upgrade Wazuh components out of step with each other. On Ubuntu, comment out the repository:

sudo sed -i "s/^deb /#deb/" /etc/apt/sources.list.d/wazuh.list
sudo apt-get update

Upgrades then become a planned change: indexer first, then server, then dashboard, then agents.

Agent enrolment

Enrolling Wazuh agents

An agent has to be installed on each machine and enrolled with the server before it sends anything. Protect enrolment first, so that only your machines can join.

Require a password to enrol

On the server, turn on password authentication for enrolment by adding this to the <auth> section of /var/ossec/etc/ossec.conf:

<auth>
  <use_password>yes</use_password>
</auth>

Then store a long random password and restart the server:

echo "<ENROLMENT_PASSWORD>" | sudo tee /var/ossec/etc/authd.pass > /dev/null
sudo chmod 640 /var/ossec/etc/authd.pass
sudo chown root:wazuh /var/ossec/etc/authd.pass
sudo systemctl restart wazuh-manager

For larger or more sensitive estates, Wazuh also supports enrolment with certificates signed by your own certificate authority.

Install the agent on Linux

After adding Wazuh's signed package repository on the machine, as Wazuh's agent documentation describes, install the agent with deployment variables that point it at your server, supply the enrolment password and place it in a group:

sudo WAZUH_MANAGER="wazuh.example.internal" \
  WAZUH_REGISTRATION_PASSWORD="<ENROLMENT_PASSWORD>" \
  WAZUH_AGENT_GROUP="linux-servers" \
  apt-get install wazuh-agent
sudo systemctl daemon-reload
sudo systemctl enable --now wazuh-agent

Disable the repository afterwards on agents too, for the same reason as on the server.

Windows and macOS

Windows agents are installed from Wazuh's MSI package, which accepts the same deployment variables, so the install can be pushed through Microsoft Intune, Group Policy or your usual software deployment tool. macOS agents use Wazuh's installer package with the same settings. Whatever the method, use agent groups to give servers, laptops and domain controllers the configuration each needs from the server, rather than editing each machine.

Check the agents have arrived

In the dashboard, the agents list shows each machine and its status. On the server:

sudo /var/ossec/bin/agent_control -l

An agent that stays disconnected is usually a firewall blocking port 1514 or 1515, a wrong server name, or an enrolment password that does not match. Our Wazuh troubleshooting guide goes through each.

Hardening

Initial security configuration: what to change before going live

A security monitoring platform holds a detailed record of your estate and can, if misused, run commands on it. Secure it as carefully as a domain controller.

  • Change every default and generated password. Use the Wazuh passwords tool to set strong, unique passwords for the indexer and API users, and keep them in your password manager. On an all-in-one host, bash wazuh-passwords-tool.sh -a changes them all.
  • Replace the self-signed certificates with certificates from your own certificate authority, so that browsers and agents can verify they are talking to the real server.
  • Restrict who can reach what. Only agents need ports 1514 and 1515. The dashboard on 443 and the API on 55000 should be reachable only from an administration network or VPN, never from the internet.
  • Put the dashboard behind single sign-on with multi-factor authentication, give each person their own account, and use Wazuh's role-based access so that analysts see what they need and fewer people can change rules or run commands.
  • Be careful with active response. Wazuh can block addresses or run scripts automatically when rules fire. Start with it off or limited to clear-cut cases, and test every response before enabling it on production systems.
  • Turn on the capabilities that matter: file integrity monitoring on the paths that hold configuration and important data, security configuration assessment against CIS benchmarks, vulnerability detection, and collection of the logs that matter most, such as Windows Security events and Sysmon.
  • Set data retention with an index state management policy in the indexer, so old data is deleted on the schedule you decided, and keep an eye on disk space.
  • Back up the configuration and the data. Back up /var/ossec/etc and the rules and decoders you write, and take indexer snapshots, then restore them once to prove it works.
  • Keep the host itself patched and monitored, including by Wazuh.

Our Wazuh consulting page describes how we keep the platform itself secure in client deployments.

Validate

Practical checks that prove Wazuh alerts are working

  1. Stage 01

    Every service is healthy

    The indexer, server and dashboard services are running, the dashboard loads without errors, and the indexer reports a green or yellow cluster health with free disk space.

  2. Stage 02

    Every agent is active

    The number of active agents matches the number of machines you meant to enrol. Chase every agent that is disconnected or never connected before going further.

  3. Stage 03

    Failed logins raise alerts

    Make several failed SSH logins to a Linux test machine, and several failed Windows sign-ins to a test account. Authentication failure alerts should appear in the dashboard within a minute or two.

  4. Stage 04

    File changes are noticed

    Change a test file in a directory you placed under file integrity monitoring. The change should appear as an alert, in real time if you configured it so, otherwise after the next scan.

  5. Stage 05

    Configuration and vulnerability results appear

    Security configuration assessment scores and vulnerability findings should be listed for each agent after the first scans complete.

  6. Stage 06

    Network devices are heard

    If firewalls or switches send syslog, generate a known event on one and find it in the dashboard. Silence here is common and easily missed.

  7. Stage 07

    Custom rules behave

    Test any decoder or rule you write against real log lines with the wazuh-logtest tool on the server before relying on it.

  8. Stage 08

    Someone is told

    Send a high-severity test alert all the way to the people who must act on it, by email, chat or ticket, and confirm they received it. An alert nobody sees is not detection.

The effort after

The ongoing effort: what running Wazuh really involves

The installation is a day. Running Wazuh well is a permanent commitment, and it is worth being clear-eyed about it before deciding to do it in-house.

Tuning. A fresh installation produces a lot of alerts that matter to nobody and misses some that would matter to you. The first months are spent removing noise, adding the data sources that were forgotten, and writing rules for your own systems and risks.

Updates and upgrades. The 4.x series receives regular releases with fixes, and each must be planned and applied in order across indexer, server, dashboard and agents. The move to 5.0 will be a migration, not an upgrade.

Capacity. Data volumes grow as you add sources. Disks fill, indexes need managing, and a platform sized for today will need more storage or another node within a year or two.

Watching and responding. This is the largest part and the easiest to underestimate. Mandiant found intruders stayed hidden for a median of 14 days in 2025, and CrowdStrike found criminal intruders moving beyond the first machine in 29 minutes on average. In our own SOC, 40% of the investigations we raised between August and October 2026 began outside UK office hours. A platform that alerts at three in the morning needs someone awake to read it, decide what it means and act.

Skills and cover. Writing rules, investigating alerts and running the platform are specialist skills, and one engineer is a single point of failure for holidays, illness and resignations.

Choosing

Run it yourself, get help, or hand over the watching

There are three sensible ways to approach this, and many organisations move between them.

ApproachWhat you doWhat you needWhere we help
Run Wazuh in-houseInstall, tune, update and respond yourselvesEngineers with time and Linux and security skills, plus out-of-hours coverNothing, or a review now and then
Run it with expert helpYou own and operate Wazuh; specialists design, build, harden, write rules and take support callsA named internal owner and someone to read alertsWazuh consulting: design, installation, rules, integrations and support retainers
Hand over detection and responseA managed SOC watches your estate around the clock and responds with youA contract and a clear escalation routeSOC365, our managed detection and response service

SOC365 is for organisations that want the outcome rather than the platform: round-the-clock monitoring of endpoints, identities, cloud services and networks by analysts who investigate every alert before it reaches you, with incident response included. Detection runs on the Wazuh manager, with Graylog as the store of client data, and it can take feeds from the tools you already run, including a SIEM you keep. Clear-cut attacks are blocked automatically at the firewall and on blocklists; isolating a machine or locking an account is decided by an analyst, with your approval or under authority agreed in advance. Our guide to managed detection and response explains the options, and indicators of compromise explains what the watching involves.

Questions

Questions about Wazuh installation

How long does a Wazuh installation take?

The installation assistant sets up an all-in-one Wazuh server in well under an hour on a suitable host. Planning, hardening, enrolling agents and testing alerts usually takes days for a small organisation and weeks for a larger estate, and tuning continues for months.

What are the system requirements for Wazuh?

For all components on one server, Wazuh suggests 4 vCPUs, 8 GiB of memory and 50 GB of storage for up to 25 agents with 90 days of data, rising to 8 vCPUs and 200 GB for up to 100 agents. Larger estates should use a distributed deployment.

Which operating system should we install Wazuh on?

A current 64-bit Linux long-term support release on a dedicated host, such as Ubuntu 24.04 LTS or Red Hat Enterprise Linux 9 or 10. Agents run on Windows, macOS, Linux and other systems.

Is Wazuh free?

Yes. Wazuh is open source and free to download and use, with no licence fee per agent. The costs are the servers or cloud resources it runs on and the people to install, tune and watch it. Wazuh also sells a hosted service and support.

What ports does Wazuh use?

Agents connect to the server on TCP 1514 and enrol on TCP 1515. The dashboard uses 443, the Wazuh API 55000 and the indexer API 9200, and clusters use 1516 and 9300 to 9400. Only the agent ports should be open to monitored machines; the rest should be restricted to administrators and Wazuh components.

How do I install a Wazuh agent?

Install the agent package on each machine with deployment variables that set the server address, enrolment password and agent group, then enable and start the service. On Windows the MSI package accepts the same variables, so agents can be pushed through Intune or Group Policy.

How do I change the Wazuh admin password?

Use the Wazuh passwords tool on the server, which changes the password for the indexer user and updates the components that depend on it. Change all the generated passwords before the platform goes live.

Should we install Wazuh 5.0?

Not for production yet. Wazuh 5.0 was at release candidate stage in November 2026, and its documentation says an in-place upgrade from 4.x is not supported. Install the current 4.x release now and plan the move to 5.0 as a migration once it is generally available. A readiness review tells you what the move will involve.

Should we use Docker or packages?

Packages installed by the assistant are simplest for most organisations. Docker or Kubernetes suit teams who already run containers and want repeatable builds. Both need the same hardening and the same attention afterwards.

Does a Wazuh installation need watching around the clock?

If it is your main way of detecting attacks, yes. Intruders work at night and at weekends, and an alert that waits until Monday may be too late. Either arrange out-of-hours cover in-house or use a managed detection and response service.

Wazuh installation

Install it once, properly, and know who will read the alerts.

Thirty minutes on your estate, your retention, whether to run Wazuh yourselves or hand over the watching, and what we would build. No slides.