[Rule Tuning] User Account Creation

オープン 初心者向け
#7,204 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
2/5
見積もり時間
1〜3時間
初心者へのやさしさ
72/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
領域
security

調査の方向性

rules/windows/persistence_user_account_creation.toml を開いてください。index リストは query ブロックに、integration は [metadata] の下にあります。サードパーティ EDR 統合を参照している他の Windows ルールを grep し(grep -rn "logs-" rules/windows/ | head)、インデックスの命名と並び順に関するローカルな慣例をコピーしてください。logs-symantec_endpoint_security.event-* と symantec_endpoint_security を追加し、次に python -m detection_rules test rule rules/windows/persistence_user_account_creation.toml を実行してください — ルールが引き続き検証を通り、新しいインデックスが一覧に表示されれば完了です。

索引モデルが issue の本文から書いたものです。

説明

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\" "
    }
  }
}
主要言語
Python
スター
3k
フォーク
759
平均マージ
3日 4時間
マージ済み PR(30日)
52

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

elastic/detection-rules のほかの issue

elastic/detection-rules の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。