[Rule Tuning] User Account Creation

Abierto Apto para principiantes
#7,204 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
72/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Área
security

Línea de trabajo

Abre rules/windows/persistence_user_account_creation.toml; la lista index está en el bloque de consulta y integration bajo [metadata]. Usa grep sobre otras reglas de Windows que hagan referencia a una integración EDR de terceros (grep -rn "logs-" rules/windows/ | head) para copiar la convención local de nombres y orden de índices. Añade logs-symantec_endpoint_security.event-* y symantec_endpoint_security, y luego ejecuta python -m detection_rules test rule rules/windows/persistence_user_account_creation.toml — listo cuando la regla siga validando y el nuevo índice aparezca listado.

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

Descripción

I work on the Symantec Endpoint Security (SES) integration in elastic/integrations. I am not part of the rules team, so this is a suggestion and a heads-up, not a request to change anything quickly.

Link to rule

https://github.com/elastic/detection-rules/blob/main/rules/windows/persistence_user_account_creation.toml

Rule tuning type

False negatives: the rule cannot see SES process events.

Description

A customer ran a purple-team exercise that included net user ... /add on hosts with SES, and this rule did not alert. Two things were missing.

  1. The SES integration did not set the ECS process fields the rule needs. That is fixed in elastic/integrations#22455 (merged 2026-11-18; symantec_endpoint_security package version 1.18.0). For process launches it now sets process.name, process.executable, process.command_line, process.args, process.args_count, the process.parent equivalents, and event.type: start. It applies to SES type 8001 (Process Activity, launched) and type 8027 (Process Detection, launch).
  2. The rule does not search the SES data. logs-symantec_endpoint_security.event-* is not in index, and symantec_endpoint_security is not in integration in [metadata]. As of origin/main at 0133427f6 no rule in this repository mentions it.

I compared the new integration test output with this rule's query. The event below, a net user /add launch from cmd.exe, meets every term: host.os.type is windows, event.type contains start, process.name is net.exe, process.parent.name is not net.exe, and process.args contains user and /add. I have not run the rule itself against SES data.

Suggestion: add logs-symantec_endpoint_security.event-* to index and symantec_endpoint_security to integration for this rule.

Some things you may want to weigh:

  • Many other Windows rules use process.args (137 Windows rule queries on main at the time of writing), so the same two additions would let them run on SES data too. I do not know which of them you would want to cover.
  • SES process activity (type 8001) can be very high volume, since it includes opens and terminations as well as launches. Rules that need event.type: start only match launches.
  • Type 8027 events are SES detections, so they cover only launches that SES flagged.
  • process.args is set only for Windows endpoints. That fits this rule.

If it helps, I am happy to open a PR for this one rule and leave the wider question to you.

Example data

Anonymised event from the integration's pipeline tests (only the fields the rule uses):

{
  "event": {
    "category": [
      "process"
    ],
    "type": [
      "info",
      "start"
    ],
    "dataset": "symantec_endpoint_security.event"
  },
  "host": {
    "os": {
      "type": [
        "windows"
      ]
    }
  },
  "process": {
    "name": "net.exe",
    "executable": "c:\\windows\\system32\\net.exe",
    "command_line": "net  user /add testuser1 NotARealPassword",
    "args": [
      "net",
      "user",
      "/add",
      "testuser1",
      "NotARealPassword"
    ],
    "args_count": 5,
    "parent": {
      "name": "cmd.exe",
      "executable": "c:\\windows\\system32\\cmd.exe",
      "command_line": "\"C:\\WINDOWS\\system32\\cmd.exe\" "
    }
  }
}
Lenguaje dominante
Python
Estrellas
3k
Forks
759
Merge medio
3 d 4 h
PR fusionados (30 d)
52

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de elastic/detection-rules

Todos los issues de elastic/detection-rules

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.