[Rule Tuning] User Account Creation

Aperta Adatta ai principianti
#7,204 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
72/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Ambito
security

Direzione di ricerca

Apri rules/windows/persistence_user_account_creation.toml; la lista index si trova nel blocco di query e integration sotto [metadata]. Esegui grep sulle altre regole Windows che fanno riferimento a un'integrazione EDR di terze parti (grep -rn "logs-" rules/windows/ | head) per copiare la convenzione locale per denominazione e ordinamento degli indici. Aggiungi logs-symantec_endpoint_security.event-* e symantec_endpoint_security, poi esegui python -m detection_rules test rule rules/windows/persistence_user_account_creation.toml — fatto quando la regola continua a validare e il nuovo indice è elencato.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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\" "
    }
  }
}
Lingua principale
Python
Stelle
3k
Fork
759
Merge medio
3g 4h
PR unite (30g)
52

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di elastic/detection-rules

Tutte le issue di elastic/detection-rules

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.