ADORSYS-GIS / ADORSYS-GIS/wazuh-agent

False positive: Rule 600005 (macOS kernel panic) matches benign Docker Desktop QEMU parameter `panic=0`

Abierto
#217 7 comentarios 0 reacciones 2 asignados Reclamado por @Calebasah Ver en GitHub
SIEM SOC
Lenguaje dominante
Shell
Estrellas
10
Forks
6
Merge medio
2 h 51 min
PR fusionados (30 d)
10

Descripción

### Summary

A level‑12 alert (`600005 – macOS: Critical kernel panic or fatal error detected`) is incorrectly triggered on a **Linux** agent when Docker Desktop launches its internal QEMU virtual machine. The alert is caused by the safe kernel boot parameter `panic=0`, which appears in the QEMU command line.

### Environment

- **Agent OS:** Linux (hostname: `said-ws`, ID: `037`)
- **Agent software:** Docker Desktop with internal QEMU/linuxkit VM
- **Log source:** `/var/log/syslog`
- **Wazuh manager:** 4.x

### Example alert (full_log)
```
2026-07-28T07:41:37.149202+01:00 said-ws com.docker.backend[688774]: ... -append init=/initd ... panic=0 ... console=ttyS0 ...
```

The keyword `panic=0` is part of the QEMU `-append` kernel arguments – it tells the Linux kernel to halt on panic, not reboot. No actual panic or kernel fault has occurred.

### Alert produced

- **Rule ID:** 600005
- **Level:** 12
- **Description:** `macOS: Critical kernel panic or fatal error detected`
- **Groups:** `macos, syslog, kernel, system_error`
- **Compliance:** PCI DSS, GDPR, HIPAA, etc. (inherited)

### Root cause

The rule’s PCRE2 regex `(?:panic|kernel\s+trap|fatal(?:\s+error)?|critical(?:\s+error)?)` matches the substring `panic` anywhere in the log. It does not exclude the safe kernel parameter `panic=0`, and it applies to all agents regardless of operating system.

### Expected behaviour

- `panic=0` in a kernel command line should **never** trigger a kernel panic alert.
- Docker Desktop’s QEMU start‑up messages should be excluded, or the rule should be restricted to macOS agents.

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Start by locating rule 600005 and inspecting its PCRE2 matching against the provided syslog example. Reproduce the Docker Desktop QEMU message, then verify that panic=0 no longer alerts while a genuine macOS kernel panic still does; check the relevant rule validation or alert tests if present.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
docker, linux, macos, shell
Área
security
Tipo de issue
Error
Dificultad
3/5
Tiempo estimado
1-2 días
Estado de actividad
Tranquilo
Claridad
Bastante claro
Aptitud para principiantes
42/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.