nano SIEM
Getting Started

Add a SIEM to Your Ludus Cyber Range

Supported in:Self-hosted

Send logs from your Ludus cyber range into nano SIEM, then search them and run detections against the attacks you launch in the lab.

Build a nano lab on Ludus to collect Sysmon and Windows Event Log telemetry from an Active Directory domain through Vector. Use the Ansible roles and blueprint in nano-rs/nano-ludus, with the SIEM-box caveat below.

What you get

DC01 (Win2022) ┐
SRV01 (Win2022)┤─ Sysmon + Event Logs ─► Vector agent ─► aggregator ─► SIEM
WS01 (Win11)   ┘                          (:9000)         (.10.11)     (.10.10)
  • A lab.local Active Directory domain (1 DC, 1 member server, 1 workstation)
  • Sysmon (SwiftOnSecurity config) + Windows Event Logs collected by Vector agents
  • A Vector aggregator + optional Conduit MITM proxy on a proxy box
  • The open-core nano stack on the SIEM box, installed from the public images (see Install with Docker Compose)

Quick start

Build the templates. The blueprint needs debian-12-x64-server-template, win2022-server-x64-template, and win11-22h2-x64-enterprise-template:

ludus templates list
ludus templates build -n win11-22h2-x64-enterprise-template   # repeat per missing template

Add the roles (clone the repo first):

git clone https://github.com/nano-rs/nano-ludus && cd nano-ludus
ludus ansible role add geerlingguy.docker
ludus ansible role add -d ansible/roles/nano_sysmon
ludus ansible role add -d ansible/roles/nano_vector_aggregator
ludus ansible role add -d ansible/roles/nano_vector_agent
ludus ansible role add -d ansible/roles/nano_conduit_proxy

Deploy. First remove the NanoSIEM.nano_lean role from the SIEM box in blueprints/nanosiem/range-config.yml (see the caveat above), then:

ludus range config set -f blueprints/nanosiem/range-config.yml
ludus range deploy
ludus range logs -f

First boot provisions the VMs, builds the AD domain and sets up Sysmon, the Vector agents and the aggregator. A clean run ends with every host at failed=0. Then install nano on the SIEM box with Docker Compose.

Access over the Ludus WireGuard VPN. The whole app is served through nginx on port 80 — open http://10.<octet>.10.10 and you'll be redirected to /setup to create the admin account. (<octet> is your range's second octet.)

Windows events are tagged with the source types windows_event and windows_sysmon. Deploy the matching parsers from the in-app Parser Repository so they are parsed to OCSF, then check what arrived:

metadata.log_source="windows_sysmon" | stats count by class_name

Troubleshoot

Need help with these checks? Contact support with the affected deployment, request ID and time with timezone.

A Windows host fails during reboot

Check for a WinRM credential error during TASK [Reboot]:

The repo's README has the full list — the Windows temp-strip workaround, lab-DNS pull throttling, HTTP-vs-HTTPS notes, and more.

What's next

On this page