Overview
Most attacks are not new. Exploits for published flaws, known C2 frameworks and commodity malware have signatures, written and maintained by the security community, and you may already license them for Suricata.
Thalamus runs those rules inside the agent with no translation step. It parses protocols rather than raw bytes, and writes Suricata-compatible EVE JSON, so the pipelines and dashboards you already have keep working.
When you see this
- An exploit for a published flaw is being sprayed across the internet.
- You license ET Pro or write your own Suricata rules and want them on every host.
- You need detection beyond HTTP: SMB, RDP, DNS, Modbus.
Steps
- 01
Turn on the IDS and load rules
Thalamus takes Suricata-compatible rules as they are: ET Open, ET Pro or your own. Start with enforce_block off; the shipped configuration recommends that until the rules are tuned.
/etc/synapse/config.yaml ids: enabled: true capture_mode: xdp rule_paths: - "/etc/synapse/rules/*.rules" enforce_block: false - 02
Tell it what your network is
Suricata rules are written against address variables such as HOME_NET. Define them under ids.address_vars. On Kubernetes, the operator's netvars resolver fills them from the cluster instead.
/etc/synapse/config.yaml ids: address_vars: { HOME_NET: "10.0.0.0/8" }Or, on Kubernetes: synapse-stack values operator: netvarsResolver: true - 03
Read the alerts
Alerts are Suricata-compatible EVE JSON. Thalamus never samples, but the capture layer can drop packets before the engine if traffic outruns the host. That is counted as packets_dropped: if it is not zero, you are not seeing everything.
- 04
Decide what a hit does
With enforce_block on, a hit bans the offending source through the firewall. The per-flow kernel drop is a separate key, enforce_edge_drop.
/etc/synapse/config.yaml ids: enforce_block: trueDecisionAre the rules tuned for your traffic?Yes Turn on enforce_block.
No Leave it off and act through the smart firewall, where a rule can require a second signal.
- 05
Act on a hit with a rule
IDS context is a set of rule fields. ids.sids lists the signatures that fired; ids.score runs from 0 to 100, higher is worse. ids.severity runs the other way: 1 is the most severe.
Smart firewall rule, action drop any(ids.sids[*] in {2054155 2047703})Smart firewall rule, action drop ids.score ge 70 and ml.traffic.c2 ge 50 - 06
Update rules without a restart
On the XDP IDS worker, rule paths and tuning reload with SIGHUP: the signature engine is rebuilt and swapped, and in-flight flow state is reset. On the AF_PACKET worker, IDS changes need a restart.
Reload kill -HUP $(cat /var/run/synapse.pid)
Common mistakes
- Turning on enforce_block before the rules are tuned.
- Reading ids.severity > 3 as serious: it selects the least serious alerts.
- Ignoring packets_dropped: a host that drops at capture is not inspecting everything.
Escalate when
- A hit on a C2 signature from inside your network.
- Repeated hits for an exploit against a service you run.
Where this stops working
- A signature catches what has been seen before. New tools need behaviour: see the model verdict playbook.
- Packets dropped by the capture layer are never inspected; packets_dropped says how many.