Every computer, server and cloud service in your company keeps a log of what happens: who signs in, what software gets installed, which file is touched. That log exists whether or not anyone looks at it. A SIEM is the tool that looks at it.
What a SIEM is
SIEM stands for security information and event management. It does four things:
- Collects the logs from computers, servers, firewalls and services such as Microsoft 365, and brings them into one place.
- Correlates them. Ten failed password attempts are not news. Ten failed attempts followed by a successful sign-in from another country are.
- Alerts you when a rule is triggered, with the priority it deserves.
- Keeps a record of what happened for as long as needed, so you can reconstruct an incident or show it to an auditor.
What it isn't
It isn't an antivirus. An antivirus protects one device. A SIEM sees the whole picture and spots what looks normal on a single device.
Nor is it a security team. A SIEM that nobody looks after is just a machine for sending alerts. Someone has to tune the rules so they don't fire at everything, review the alerts and act on them. That work can be done in-house or outsourced.
And it doesn't stop an attack on its own. What changes is how long it takes you to find out and how much you know afterwards about what happened.
Wazuh, the one we use
Wazuh is an open-source SIEM. You install an agent on each device, which sends its events to a central server with its own dashboard. As well as collecting logs, it watches for changes to sensitive files, detects software with known vulnerabilities and comes with ready-made reports for standards such as the GDPR or PCI DSS.
There is no licence fee, so what you pay for is deployment, tuning and operation. For an SME, that changes the numbers. We work with Wazuh for our clients and we also use it on our own infrastructure.
When an SME needs one
Size doesn't decide it. These are the signs:
- A large client asks you for it. Many companies send their suppliers a security questionnaire, and one of the questions is whether you log and review activity on your systems.
- You are going for ISO 27001 certification. The standard includes controls for activity logging and monitoring. You can meet them without a SIEM, but with one it is much easier to prove. We explain it in ISO 27001.
- NIS2 applies to you, directly or as a supplier. The directive requires the organisations in its scope to manage incidents and look after the security of their supply chain. If you sell to one of them, they will pass that on to you. More in NIS2.
- You have had an incident and couldn't work out what happened or how they got in.
- You hold other people's sensitive data: health or financial data, or your clients' intellectual property.
If none of these sounds like you, you probably have other things higher up the list: tested backups, two-factor authentication on email and up-to-date devices. A SIEM on weak foundations only tells you in detail what you already knew.
What to ask whoever sets it up
- Which sources it will collect besides the devices: email, firewalls, servers.
- Who reviews the alerts and during what hours. Be wary of anyone who promises round-the-clock monitoring and doesn't explain who is on the other end.
- What report you will receive and how often.
- How long the logs are kept and where.
How we do it
We offer it as a service. We deploy Wazuh, tune the rules to your environment, review the alerts and send you a regular report on what has happened and what has been done. Your team doesn't need to learn how to use the tool.
The details are in SIEM with Wazuh. And if your concern is who gets into your applications and from where, have a look at Zero Trust access with Cloudflare.
Shall we look at your case?
Tell us what you have today and what you would like to have.