Setting up a SIEM
During my internship at Xbline, I built a SIEM on Proxmox: Graylog to centralise logs, Wazuh to detect intrusions.
- Status
- Completed
- Year
- 2026
- Type
- Cybersecurity / Monitoring
1 / 3
Project overview
During the last week of my internship at Xbline, a colleague suggested I set up a SIEM. The goal: bring together the logs of every machine (Proxmox host, virtual machines, Windows computers) to spot a security incident in real time. I installed Graylog, with Elasticsearch and MongoDB, on a Debian 12 VM, then Wazuh on a second VM for intrusion detection. I also wrote an installation guide for each tool.
My role
I installed and configured everything myself, from the two VMs to the agents, then documented the setup.
What I learned
- Context
- A project carried out during the sixth week of my internship at Xbline, in June 2026. A colleague suggested I build a SIEM on a Proxmox server to monitor the security of the machines.
- Need
- Centralise and analyse the logs of several machines to detect security incidents in real time, with a second tool dedicated to intrusions.
- Solution
- A Debian 12 VM with Elasticsearch, MongoDB and Graylog, receiving the logs of the Proxmox host and of a Windows 11 computer (through Winlogbeat). A second VM with Wazuh (manager, indexer and dashboard), and Wazuh agents on the machines to monitor.
- Challenges
- Versions. Graylog only works with one specific Elasticsearch version, 7.10.2: I had to pin it to avoid an automatic upgrade. I also ran into Elasticsearch keystore errors, and found out that Wazuh had to be on a separate VM, because it uses the same ports (9200 and 9300).
- Takeaways
- How a SIEM works, from collecting logs to raising alerts. I learned to read a Linux service's errors to troubleshoot it, and to write documentation a colleague can follow on their own.