[Rule Tuning] User Account Creation
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
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.
- 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_securitypackage version 1.18.0). For process launches it now setsprocess.name,process.executable,process.command_line,process.args,process.args_count, theprocess.parentequivalents, andevent.type: start. It applies to SES type 8001 (Process Activity, launched) and type 8027 (Process Detection, launch). - The rule does not search the SES data.
logs-symantec_endpoint_security.event-*is not inindex, andsymantec_endpoint_securityis not inintegrationin[metadata]. As oforigin/mainat0133427f6no 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 onmainat 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: startonly match launches. - Type 8027 events are SES detections, so they cover only launches that SES flagged.
process.argsis 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
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de elastic/detection-rules
-
[Rule Tuning] DNS-over-HTTPS Enabled via RegistryPosiblemente ocupada @SeoJunLee-code la tomó hace 4 días. Abiertocommunity Rule: Tuning Team: TRADE
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
elastic/detection-rules#7184 ·
Los mantenedores suelen responder en 1 día
-
[Rule Tuning] AdFind Command ActivityPosiblemente ocupada @TT5H la tomó hace 2 días. Abiertocommunity Rule: Tuning Team: TRADE
Dificultad 1/5 Menos de una hora Aptitud para principiantes 65/100
elastic/detection-rules#7183 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
[Rule Tuning] Add documented Nizlo processes to Multiple Remote Management Tool Vendors on Same HostAbiertocommunity
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
elastic/detection-rules#7147 ·
Los mantenedores suelen responder en 1 día
-
Improve protocol validation for Kerberos port-88 alertsPosiblemente ocupada @eric-forte-elastic la tomó hace 9 días. Abiertocommunity Rule: Tuning Team: TRADE
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
elastic/detection-rules#7145 · 1 reacción · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
community Rule: Tuning Team: TRADE
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
elastic/detection-rules#6953 ·
Los mantenedores suelen responder en 1 día
Todos los issues de elastic/detection-rules
Issues similares
-
CI flake: test-windows times out spawning Node in tests/test_antigravity_node_hooks.py (develop red)Abiertoarea/ci P2
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 2 días
-
benchmark
Dificultad 1/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
mozilla-ai/cq#601 ·
Los mantenedores suelen responder en 1 día
-
Bump Python to 3.14 or 3.15Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día