The Wazuh Server & Client Install
Wazuh watching up to 25 of your machines, with two documented tuning passes before handover so the alerts that reach you are worth reading.
Most security monitoring fails the same way. Someone installs it, it works, and a fortnight later it throws so many alerts that your team has stopped looking. You end up paying for a dashboard nobody opens.
We install Wazuh on a machine you supply and put agents on up to twenty-five of your Linux, Windows and Mac machines. You see changes to your system files, failed logins and package installs as they happen. You also get each machine scored against the security configuration policy for its own operating system, with the known vulnerabilities in the software already on it listed beside the score.
Then we spend three days taking the noise out. Twelve hours after the agents go live we measure what is firing and silence what is wrong, then repeat it a day later. You get the before-and-after numbers, the ten loudest rules we chose to leave alone, and the exact line to silence each of them yourself.
What's included
Wazuh running on your own machine, sized from your real host count against a formula we show you, and proven to come back on its own after a reboot
Up to 25 of your Linux, Windows and Mac machines reporting, plus the command to add the twenty-sixth yourself, because that takes about five minutes and we are not going to charge you for it
Changes to your system files, boot files, SSH keys and Windows startup registry caught and alerted, proven on a real machine of each kind before we hand over
Every machine scored against the security configuration policy for its own operating system, with the vulnerabilities in its installed software listed beside the score
Two tuning passes across three days, with the alert rate measured before and after each one and every rule we silenced written down with the reason
Alerts arriving wherever you want them, tested with a message you confirm receiving, and the compliance dashboards switched on and reading your own data
A plain-English handover covering how much you can keep and for how long, how to add machines yourself, and a written statement of who is watching afterwards
Before you order
Have these ready so we can start the moment you order. The delivery clock only runs while we have them.
A clean Linux machine for Wazuh (Debian, Ubuntu, RHEL, Rocky or AlmaLinux) with root or sudo access over SSH
A count of the Linux, Windows and Mac machines to watch with their versions, and either access to them or an administrator of yours to run our install command
Where alerts go: an email address with your mail relay details, or a Slack, Teams or other webhook
A certificate for the dashboard's hostname, or your agreement to the built-in one and its browser warning
A window for the agent installs and one reboot of the Wazuh machine, and the person who receives the passwords we generate
How it works
Book it — pay the fixed price and tell us the target environment. No scoping call first.
We deliver — an experienced specialist runs our standard workflow for this exact task. You can watch progress and message them in the portal.
Hand-off — you get the deliverables, the documentation, a rollback snapshot, and a walkthrough if you want one.
Who does it
A salaried Support Resort specialist with more than ten years in the field, working from a runbook we've been refining since 2003 — supervised by senior management, never a marketplace contractor. You'll see who is assigned and can message them about this task directly in your portal.
FAQ
Ask about this task
Our assistant knows the scope document and runbook behind this service. Ask what's covered, what isn't, or whether it's the right task for your situation.
Answers come from our published scope documents. Prefer a person? Switch to the "Email us" tab — a senior manager replies personally, usually the same weekday.
Related services
The Wazuh Monitoring Plan
Somebody outside your team reads your Wazuh alerts every month, writes down what each one was, and keeps tuning out the noise your install was never running long enough to see.
The Linux Server Hardening
One production Linux server closed off at the operating-system level to the break-in routes attackers rely on — with before-and-after evidence of every change we make.
The FleetDM/osquery Install
One page that tells you what is installed on every laptop and server you own, and which of them are unpatched or running unencrypted. Fleet and osquery on a machine of yours, with every agent installer proven on a real endpoint before it reaches your fleet.