Guilgo Blog

Notes from my daily work with technology.

Wazuh without Elasticsearch: lightweight dashboard in Grafana with the REST API

Agents, security alerts (SCA, MITRE), AdGuard and parental control in one dashboard. No Indexer or official Dashboard.

Use Grafana as frontend for Wazuh Lite: agents, security alerts (SCA, MITRE), AdGuard and parental control. NodePort, JSON plugin, JWT, alerts proxy and panels in one dashboard. No Indexer or Elastic/OpenSearch.

Auditing Kubernetes with Wazuh: API server audit logs to the SIEM step by step

Webhook, audit policy and rules to send Kubernetes audit logs to Wazuh and alert on resource create/delete

Step-by-step guide to audit Kubernetes with Wazuh: API server audit logs to the SIEM, webhook listener, audit policy and rules in local_rules.xml. Kubernetes security monitoring.

Prioritize critical patches in WSUS when Wazuh detects CVEs

From Vulnerability Detector alerts to controlled deployment on Windows

Practical workflow to approve and deploy only critical updates in WSUS when Wazuh alerts on vulnerabilities, with pilot groups and prioritization criteria.

Parental control with Wazuh, AdGuard and Telegram

Implementation of a full open-source parental control system using Wazuh as SIEM, AdGuard Home for DNS filtering and Telegram for real-time alerts.

Monitoring WireGuard logs with Wazuh

Practical guide to integrate WireGuard log monitoring with Wazuh, using rsyslog to capture kernel events and custom decoders for security alerts.

Wazuh releases 4.9.1 to mitigate Mirai botnet attacks (CVE-2025-24016)

Wazuh has released 4.9.1, which fixes the CVE-2025-24016 vulnerability (insecure deserialization in the Wazuh Server) that was later exploited by Mirai variants against exposed servers. Effective mitigation is to upgrade to 4.9.1 or later on manager, indexer and dashboard, then upgrade agents to maintain compatibility.

Executive summary

  • CVE-2025-24016 allows RCE on wazuh-manager (v ≥ 4.4.0 and < 4.9.1). Fixed in 4.9.1.
  • There was active exploitation by Mirai botnets in 2025 against servers with exposed API.
  • Wazuh stated that the bug requires API credentials; with panel or API exposed and weak keys, the risk is critical.

Sources: CVE/NVD, Release notes 4.9.1, Akamai/Censys advisories and official upgrade guide.