Services · Wazuh consulting · UK
Wazuh consulting,from engineers whorun it every day.
Wazuh is the platform our own SOC has been built on since 2012. We design, deploy, tune and support it for UK organisations of every size, from a single server watching a small office to multi-node clusters across an enterprise estate, and we connect it to the firewalls, intrusion prevention, identity and data loss prevention systems you already run.
Deployment and upgradesRules and decodersFirewall, IPS, IAM and DLPSupport from £595 a month£1,050 + VAT a day
Wazuh is free to download. Making it useful is engineering work, and that is what we sell.
Most Wazuh deployments we are asked to look at were installed in an afternoon and have not been touched properly since. The dashboard works, the agents report in, and the alerts are either too many to read or too few to trust. We bring the same engineering we use in our own multi-tenant SOC: an architecture sized for your estate, the right data sources, rules written and tested for your environment, noise taken out, upgrades planned, and a named team to call when something breaks. You can keep running it yourselves afterwards, retain us to look after it, or hand the watching to SOC365, our managed SOC, which uses the Wazuh manager as its detection engine.
- Platform
- Wazuh 4.14 in production, and readiness work for Wazuh 5.0
- Sizes
- All-in-one servers to multi-node clusters
- Integrations
- Firewalls, IPS, identity, DLP, cloud and Microsoft 365
- Commercials
- £1,050 + VAT a day; fixed prices from £2,100; support plans from £595 a month
14 years
Running Wazuh, and OSSEC before it, as the core of our SOC
11
Countries our Wazuh-based SOC serves clients in
240+
Data loss prevention rules in our own Wazuh library
7
Operating system families our agents run on
- Running Wazuh, and OSSEC before it, as the core of our SOC: In production since 2012
- Countries our Wazuh-based SOC serves clients in: Multi-tenant, with per-client managers and data
- Data loss prevention rules in our own Wazuh library: Each mapped to MITRE ATT&CK
- Operating system families our agents run on: Linux, Windows, macOS, Unix, Oracle, VAX/VMS and HP-UX
What is Wazuh
What is Wazuh?
Wazuh is a free, open source security platform that combines SIEM (security information and event management) and XDR (extended detection and response). It collects security data from servers, laptops, cloud services and network devices, analyses it against rules, and raises alerts when something looks wrong. It grew out of the OSSEC intrusion detection project and is maintained by Wazuh Inc.
The platform has four parts. The Wazuh agent runs on each monitored machine. The Wazuh server (the manager) receives the data, decodes it and applies the rules. The Wazuh indexer stores and searches the alerts, and the Wazuh dashboard is the web interface. Devices that cannot run an agent, such as firewalls, switches and intrusion detection sensors, send their logs by syslog or are read through an API, which Wazuh's documentation calls agentless monitoring.
Out of the box it offers log analysis, intrusion and malware detection, file integrity monitoring, security configuration assessment against benchmarks such as CIS, vulnerability detection, active response, and dashboards mapped to PCI DSS, HIPAA, NIST 800-53, GDPR and the Trust Services Criteria. Wazuh's own documentation is careful to say those mappings are indicative and do not certify compliance on their own.
What Wazuh costs
The software costs nothing. The costs are the servers or cloud capacity to run it, the storage for the data you keep, and the engineering time to deploy, tune and look after it. That last cost is the one most organisations underestimate, and it is where a consultant earns their fee or does not. If you would rather not run the central components at all, Wazuh Inc. offers Wazuh Cloud, a hosted service in which it manages the platform and you manage the agents and the rules. We work with both.
What we do
Wazuh services, from first install to daily support
Each can be bought on its own. Most engagements start with a health check or a design, and the rest follows from what it finds.
Architecture and deployment
An all-in-one server for a small estate, separate nodes for a medium one, or clustered managers and indexers behind a load balancer for an enterprise. Sized for your event volume and retention, built and documented. Doing it yourselves? Our Wazuh installation guide has the steps. Fixed prices are on the Wazuh deployment page.
Upgrades and migrations
Planned upgrades across the 4.x line, moves from OSSEC or an ageing all-in-one box to a cluster, re-platforming to new hardware or cloud, and readiness reviews for Wazuh 5.0 from £3,150 + VAT.
Rule and decoder development
Custom decoders for the logs Wazuh does not understand, and rules written for your environment, tested against real samples, mapped to MITRE ATT&CK and kept under version control.
Integrations
Firewalls, IPS and IDS sensors, Entra ID and other identity providers, DLP tools, cloud platforms, Microsoft 365, ticketing, chat and threat intelligence feeds.
Tuning and noise reduction
We find the rules that fire thousands of times a day and tell nobody anything, and change them so that what reaches a person is worth reading.
Health check and hardening
A review of an existing deployment: versions, cluster health, disk and index lifecycle, agent coverage, credentials, exposure and backups, with the fixes in order. From £2,100 + VAT: see the Wazuh health check.
Support and maintenance
Two support plans. Standard: business hours, response within 8 hours, from £595 + VAT a month. Premium: critical issues 24/7, response within 4 hours, from £1,495 + VAT a month.
Compliance reporting
Wazuh's configuration assessment, file integrity and vulnerability data, arranged as evidence for Cyber Essentials, ISO 27001, PCI DSS and the NHS toolkit.
Training and handover
Your team taught to read the dashboard, write and test a rule, onboard a source and recover the platform, using your own deployment.
Integrations
Wazuh with firewalls, IPS, IAM and DLP: not a problem
Wazuh reads syslog, calls cloud APIs and runs agents, so almost anything that produces a log can be brought in. The work is in the decoders, the rules and the plumbing that keeps a busy source from swamping the manager, and we have done it for each of these. If yours is not listed, ask.
Firewalls
Fortinet FortiGate, Palo Alto Networks, Check Point, Cisco, Sophos, pfSense and OPNsense, by syslog through a collector, with decoders for each vendor's format and rules for the events that matter: admin logins, policy changes, VPN abuse and blocked scans.
Intrusion prevention and detection
Suricata, Snort and Zeek sensors, and the IPS engines inside next-generation firewalls, correlated with what the endpoint agents see on the same hosts.
Identity and access management
Microsoft Entra ID sign-ins and audit logs, Active Directory, Okta, Duo and Google Workspace: impossible travel, password spraying, new privileged roles and changes to conditional access.
Data loss prevention
Microsoft Purview DLP alerts through the Microsoft Graph module, and endpoint DLP built from our own rule library: removable media, cloud uploads, mass file access and sensitive file movement.
Cloud and Microsoft 365
Microsoft 365 audit data, Defender alerts through Microsoft Graph, Azure Log Analytics, AWS logs from S3 buckets and Google Cloud, with the permissions kept to what the module needs.
Tickets, chat and intelligence
Alerts sent to the tools your team already watches, such as Jira, ServiceNow, Teams or Slack, and enrichment from VirusTotal, MISP or your own threat intelligence.
Works with
The products we connect Wazuh to
A selection of the firewalls, sensors, identity providers, cloud platforms and tools we have integrated with Wazuh. Product names are trademarks of their owners and describe compatibility, not a partnership.
- Check Point
- Okta
- Microsoft 365
- Sophos
- Suricata
- Microsoft Purview
- Microsoft Teams
- Google Cloud
- Google Workspace
- Fortinet
- Snort
- MISP
- Microsoft Entra ID
- AWS
- Zeek
- Cisco
- Duo
- Palo Alto Networks
- Jira
- Slack
- OPNsense
- pfSense
- VirusTotal
- ServiceNow
Rule development
How we write Wazuh rules
A Wazuh deployment is only as good as its rules. The default ruleset is broad and well maintained, but it does not know your environment: which administrator logs in from where, which service account should never touch a file share, which firewall message means a configuration has changed. Custom rules close that gap, and badly written ones open new ones. Our practice:
- Never edit the default ruleset. Wazuh overwrites files under its own ruleset directory on every upgrade. Custom rules live in their own files, and where a default rule has to change, we copy it and use
overwrite="yes"so the change survives. - Keep to the custom ID range. Wazuh reserves 100000 to 120000 for custom rules. We allocate a block to each client and each library, so rules from different sources never collide.
- Test before deploying. Every rule is run against real log samples with
wazuh-logtest, and the full ruleset is checked to load cleanly before a manager is restarted. A rule that does not load can stop the analysis engine. - Map and explain. Each rule carries its MITRE ATT&CK technique, a description a tired analyst can act on, and a level that reflects how urgent it is in your environment.
- Version everything. Rules and decoders live in a repository, are pushed to the managers by configuration management, and can be rolled back.
You can see the result in our articles. Our write-ups of exploited flaws carry working Wazuh detection rules, such as those for the Elementor CSRF flaw and the Citrix NetScaler zero-days, written the same way we write them for clients.
From the engine room
Problems we have solved running Wazuh at scale
- _01Agent enrolment stormsA load balancer sent enrolment traffic on port 1515 to worker nodes instead of the master, so thousands of agents retried at once. Enrolment now goes only to the node that issues keys, and event traffic is balanced with Wazuh's own load balancer helper.Clusters
- _02A cluster master that stopped answeringFile descriptor exhaustion on the master node under a large agent population, fixed by raising and monitoring the limits before the next growth spurt.Scale
- _03Decoders that broke on large cloud eventsEntra ID conditional access records are big enough to overrun a regular expression's buffer. Decoders anchored on fields near the start of the JSON fixed it without losing the data.Identity
- _04Search storage that stalledOpenSearch shards, the technology under the Wazuh indexer, left unassigned by a lifecycle policy that never moved older data, fixed with tiering rules and a nightly check that keeps hot storage for recent data.Storage
- _05Data loss rules that cried wolfEndpoint DLP rules escaping Windows paths wrongly and matching everything. Rewritten with PCRE2, tested against live event streams, and suppressed where the business has a reason.Tuning
Wazuh 5.0
Wazuh 5.0: what changes, and when to move
The current production release is Wazuh 4.14, most recently 4.14.10 of 5 November 2026. Wazuh 5.0 is at release candidate stage, with general availability expected soon. It is the largest change to the platform in years, and it is worth planning for rather than meeting on the day.
| Area | Wazuh 4.x | Wazuh 5.0 |
|---|---|---|
| Data model | Wazuh's own alert format | The Wazuh Common Schema, derived from the Elastic Common Schema |
| Detection | XML rules and decoders | A new engine with a more readable rule syntax and support for Sigma rules |
| Agent connection | Ports 1514 and 1515 | HTTPS on port 1517 for 5.0 agents; 4.x agents still use the old ports |
| Custom decoders | Can write any field | The indexer rejects fields outside the schema, so custom decoders must write schema fields |
| Manager | ossec.conf, wazuh- daemons | A new manager configuration file and renamed daemons |
Our advice is plain. Do not run a release candidate in production. Do list every custom rule, decoder and integration you depend on now, because those are what a 5.0 migration has to rewrite or replace, and test them in a lab against 5.0 before you plan the move. A 4.x deployment that is current and well documented will migrate far more easily than one nobody has touched since it was installed. A Wazuh 5.0 readiness review gives you that inventory, the size of the rewrite, and a plan.
Security
Keeping the platform itself secure
A SIEM holds credentials, reaches every monitored machine and can run commands on them through active response, which makes it a valuable target. In 2025 a critical flaw in the Wazuh server's API, CVE-2025-24016, was used by botnets against servers that had not been updated; it had been fixed in version 4.9.1 months before. The fix for that kind of problem is routine maintenance, not alarm, and it is part of every deployment we build and every retainer we run:
- current versions on the managers, indexers, dashboard and agents, upgraded on a planned schedule;
- the API, the dashboard and the indexer kept off the internet, with only the agent ports reachable, and only from where agents live;
- default and installer-generated passwords replaced, named accounts with the least privilege they need, and the API's role-based access control used rather than one shared administrator;
- certificates managed and renewed, agent enrolment protected by a password or certificate, and active response limited to the commands you have agreed;
- backups of configuration, rules and keys, and a recovery that has been tried.
Engagement
How a Wazuh engagement works
Stage 01
A 30-minute call
What you run, what you want Wazuh to tell you, what exists already and what has gone wrong. You leave with a view on the right next step, even if that step is not us.
Stage 02
Review or design
For an existing deployment, a health check with the fixes in order. For a new one, a design: sizing, sources, retention, availability and where it will run.
Stage 03
Fixed price
The work is broken into stages and quoted at a fixed price built from our day rate, so the price does not move if it takes us longer.
Stage 04
Build in stages
Central components first, then agents by group and sources one at a time, each confirmed in the dashboard before the next is added.
Stage 05
Tune
A period of watching what fires, removing noise and adding the rules your environment needs, before anyone is expected to act on every alert.
Stage 06
Hand over or look after
Documentation, training and a runbook for your team, or a support retainer with us, or monitoring by SOC365. Your choice, and you can change it later.
What it costs
What Wazuh consulting costs
Wazuh consulting is priced at our published consulting rate. Defined pieces of work, such as a health check, a deployment, an integration or a 5.0 readiness review, are quoted at a fixed price built from that rate after the first call. Ongoing support is one of two published support plans, and further work for plan holders is charged at the retainer rate, 30% off the day rate.
| Price | Suits | |
|---|---|---|
| Day rate | £1,050 + VAT a day | Advice and work that cannot be scoped in advance |
| Fixed price | Quoted from the day rate | A health check, a deployment, a migration, an integration, a set of rules |
| Retainer rate | £735 + VAT a day, twelve-month term | Further engineering for support plan holders and retained clients |
| Support plan | From | Cover |
|---|---|---|
| Standard | £595 + VAT a month | Business hours, response within 8 hours, two health checks a year |
| Premium | £1,495 + VAT a month | Critical issues 24/7, response within 4 hours, four health checks a year, an engineering day a month |
| Fixed-price work | From |
|---|---|
| Health check | £2,100 + VAT, credited against a support plan signed within 60 days |
| Wazuh 5.0 readiness review | £3,150 + VAT |
| Deployment | £4,200 + VAT |
For three days of work, that is £3,150 + VAT at the day rate or £2,205 + VAT on a retainer; for ten days, £10,500 + VAT or £7,350 + VAT. We work remotely as standard and come on site when the work needs it; any travel cost is named in the quote. The consulting cost guide explains how the three ways of buying compare, and every price we charge is on the pricing page.
The wider picture
Wazuh and the rest of your cyber defence
SOC365, our managed SOC
If you would rather someone else watched the alerts at three in the morning, our SOC uses Wazuh as its detection and alerting engine, and can take over yours or bring its own.
EmilyAI for your own SOC
Our AI SOC analyst can read your Wazuh data and review it hour by hour, alongside your own team.
Penetration testing
A test shows whether an attacker could get in; Wazuh should show that someone tried. Compare the tester's timeline with what was detected.
Incident response
When Wazuh raises something serious, our responders can investigate from the same data, with a retainer if you want guaranteed response times.
Deploying the Wazuh agent at scale
Our free guide to rolling the agent out with Group Policy or Intune, checking it worked, upgrading it and removing it.
MDR, SIEM and XDR explained
Where a SIEM such as Wazuh fits beside EDR, XDR and a managed SOC, in plain English.
Wazuh and Graylog
How our SOC runs the Wazuh manager with Graylog in place of the indexer, and when that design is worth it.
Wazuh troubleshooting
Agents that never connect, a yellow or red indexer, full disks and a dashboard that is never ready, with the fixes.
Wazuh vs Splunk, Sentinel and Elastic
How the four are priced, hosted and run, and where each fits, including where Wazuh does not.
Questions
Questions about Wazuh and Wazuh consulting
What is Wazuh used for?
Wazuh collects and analyses security data from servers, laptops, cloud services and network devices, and alerts on signs of attack or misconfiguration. Organisations use it as their SIEM, for file integrity monitoring, vulnerability detection, configuration assessment against benchmarks, and as evidence for compliance.
Is Wazuh really free?
The software is free and open source, with no licence fee per agent or per gigabyte. You pay for the servers or cloud capacity, the storage, and the time to run it well. Wazuh Inc. sells support and a hosted service, Wazuh Cloud, for those who want them.
Can we install Wazuh ourselves?
Yes. On a suitable Linux server the installation assistant sets up an all-in-one platform in well under an hour. The work that decides whether it protects anyone is the planning, hardening, agent enrolment, testing and tuning around it. Our step-by-step Wazuh installation guide covers each, and we can review or finish an installation you have started.
Is Wazuh a SIEM or an EDR?
Both, in part. It is a SIEM in that it collects and correlates logs from across an estate, and its agent provides endpoint detection, file integrity monitoring and active response. It does not replace a dedicated EDR product's deep behavioural analysis and rollback, and many organisations run the two together, with the EDR's alerts brought into Wazuh.
How does your own SOC use Wazuh?
The Wazuh manager is the signal and alert engine throughout our SOC: agents and collectors feed it, and its decoders and rules, our own libraries included, decide what becomes an alert. We replaced the Wazuh indexer with Graylog, which scales better for us at the data lake level, and we wrote our own front end in place of the Wazuh dashboard. For a single organisation, Wazuh's own indexer and dashboard are usually the simpler choice, and they are what we build as standard. Our Wazuh and Graylog guide explains the design and when it is worth copying.
Can Wazuh replace Microsoft Sentinel or Splunk?
For many organisations, yes, and the saving can be large. The trade is that you, or someone you pay, run the platform. If you are heavily invested in Microsoft's security tools, Wazuh can also sit alongside Sentinel. We will tell you which we think suits you on the first call. Our comparison of Wazuh, Splunk, Sentinel and Elastic sets out the trade-offs.
Can you take over a deployment someone else built?
Yes; much of our work starts that way. A health check tells us what is there, what is missing and what is at risk, and we fix it in order of importance without starting again unless that is cheaper.
How much does Wazuh support cost?
Standard support, covering business hours with a response within 8 hours, starts at £595 + VAT a month for up to 100 agents. Premium, covering critical issues 24/7 with a response within 4 hours, starts at £1,495 + VAT a month. Every band is on our Wazuh support page.
Do you support Wazuh for small businesses?
Yes. A small business can run Wazuh well on a single server, and the work is smaller to match. We size the deployment, and the price, for the estate you have, not for the one in a vendor's reference design.
Where is our data kept?
Where you choose. A self-hosted Wazuh keeps its data on servers you control, in the UK or anywhere else. If you use Wazuh Cloud or our SOC, we will tell you exactly where the data lives before you decide.
Should we wait for Wazuh 5.0?
Not for a new deployment you need now: build on the current 4.x release and plan to move once 5.0 is generally available and your integrations have been tested against it. For an existing deployment, start the inventory of custom rules and decoders now, because that is what the migration depends on.
Wazuh consulting
Talk to an engineer who runs Wazuh.
Thirty minutes on what you have, what you want it to tell you and what is getting in the way. No slides.