Skip to content

[New] Elastic Defend Alert from GenAI Utility or Descendant#5793

Merged
Samirbous merged 15 commits intomainfrom
HOR-Alerts-from-GenAI
Mar 9, 2026
Merged

[New] Elastic Defend Alert from GenAI Utility or Descendant#5793
Samirbous merged 15 commits intomainfrom
HOR-Alerts-from-GenAI

Conversation

@Samirbous
Copy link
Copy Markdown
Contributor

Detects Elastic Defend alerts (behavior, malicious file, memory signature, shellcode) where the alerted process or its direct parent is a GenAI coding or assistant utility.

Detects Elastic Defend alerts (behavior, malicious file, memory signature, shellcode) where the alerted process or its direct parent is a GenAI coding or assistant utility
@Samirbous Samirbous self-assigned this Feb 27, 2026
@Samirbous Samirbous added the Rule: New Proposal for new rule label Feb 27, 2026
@github-actions
Copy link
Copy Markdown
Contributor

Rule: New - Guidelines

These guidelines serve as a reminder set of considerations when proposing a new rule.

Documentation and Context

  • Detailed description of the rule.
  • List any new fields required in ECS/data sources.
  • Link related issues or PRs.
  • Include references.

Rule Metadata Checks

  • creation_date matches the date of creation PR initially merged.
  • min_stack_version should support the widest stack versions.
  • name and description should be descriptive and not include typos.
  • query should be inclusive, not overly exclusive, considering performance for diverse environments. Non ecs fields should be added to non-ecs-schema.json if not available in an integration.
  • min_stack_comments and min_stack_version should be included if the rule is only compatible starting from a specific stack version.
  • index pattern should be neither too specific nor too vague, ensuring it accurately matches the relevant data stream (e.g., use logs-endpoint.process-* for process data).
  • integration should align with the index. If the integration is newly introduced, ensure the manifest, schemas, and new_rule.yaml template are updated.
  • setup should include the necessary steps to configure the integration.
  • note should include any additional information (e.g. Triage and analysis investigation guides, timeline templates).
  • tags should be relevant to the threat and align/added to the EXPECTED_RULE_TAGS in the definitions.py file.
  • threat, techniques, and subtechniques should map to ATT&CK always if possible.

New BBR Rules

  • building_block_type should be included if the rule is a building block and the rule should be located in the rules_building_block folder.
  • bypass_bbr_timing should be included if adding custom lookback timing to the rule.

Testing and Validation

  • Provide evidence of testing and detecting the expected threat.
  • Check for existence of coverage to prevent duplication.

@tradebot-elastic
Copy link
Copy Markdown

tradebot-elastic commented Feb 27, 2026

⛔️ Test failed

Results
  • ❌ Elastic Defend Alert from GenAI Utility or Descendant (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

…o initial_access_elastic_defend_genai_utility_descendant.toml
@tradebot-elastic
Copy link
Copy Markdown

tradebot-elastic commented Feb 27, 2026

⛔️ Test failed

Results
  • ❌ Elastic Defend Alert from GenAI Utility or Descendant (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link
Copy Markdown

tradebot-elastic commented Feb 27, 2026

⛔️ Test failed

Results
  • ❌ Elastic Defend Alert from GenAI Utility or Descendant (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

… initial_access_elastic_defend_alert_genai_utility_descendant.toml
@tradebot-elastic
Copy link
Copy Markdown

tradebot-elastic commented Feb 27, 2026

⛔️ Test failed

Results
  • ❌ Elastic Defend Alert from GenAI Utility or Descendant (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link
Copy Markdown

tradebot-elastic commented Feb 27, 2026

⛔️ Test failed

Results
  • ❌ Elastic Defend Alert from GenAI Utility or Descendant (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link
Copy Markdown

tradebot-elastic commented Feb 27, 2026

⛔️ Test failed

Results
  • ❌ Elastic Defend Alert from GenAI Utility or Descendant (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link
Copy Markdown

tradebot-elastic commented Feb 27, 2026

⛔️ Test failed

Results
  • ❌ Elastic Defend Alert from GenAI Utility or Descendant (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link
Copy Markdown

tradebot-elastic commented Feb 27, 2026

⛔️ Test failed

Results
  • ❌ Elastic Defend Alert from GenAI Utility or Descendant (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link
Copy Markdown

tradebot-elastic commented Feb 27, 2026

⛔️ Test failed

Results
  • ❌ Elastic Defend Alert from GenAI Utility or Descendant (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link
Copy Markdown

tradebot-elastic commented Mar 3, 2026

⛔️ Test failed

Results
  • ❌ Elastic Defend Alert from GenAI Utility or Descendant (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link
Copy Markdown

tradebot-elastic commented Mar 3, 2026

⛔️ Test failed

Results
  • ❌ Elastic Defend Alert from GenAI Utility or Descendant (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

…_utility_descendant.toml

Co-authored-by: Terrance DeJesus <99630311+terrancedejesus@users.noreply.github.com>
@tradebot-elastic
Copy link
Copy Markdown

tradebot-elastic commented Mar 9, 2026

⛔️ Test failed

Results
  • ❌ Elastic Defend Alert from GenAI Utility or Descendant (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

Samirbous and others added 2 commits March 9, 2026 14:10
…_utility_descendant.toml

Co-authored-by: Eric Forte <119343520+eric-forte-elastic@users.noreply.github.com>
@tradebot-elastic
Copy link
Copy Markdown

tradebot-elastic commented Mar 9, 2026

⛔️ Test failed

Results
  • ❌ Elastic Defend Alert from GenAI Utility or Descendant (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@tradebot-elastic
Copy link
Copy Markdown

tradebot-elastic commented Mar 9, 2026

⛔️ Test failed

Results
  • ❌ Elastic Defend Alert from GenAI Utility or Descendant (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

Copy link
Copy Markdown
Contributor

@eric-forte-elastic eric-forte-elastic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Main comment addressed, looks good 👍

@tradebot-elastic
Copy link
Copy Markdown

tradebot-elastic commented Mar 9, 2026

⛔️ Test failed

Results
  • ❌ Elastic Defend Alert from GenAI Utility or Descendant (esql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta

@Samirbous Samirbous merged commit 2276987 into main Mar 9, 2026
17 of 19 checks passed
@Samirbous Samirbous deleted the HOR-Alerts-from-GenAI branch March 9, 2026 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport: auto Rule: New Proposal for new rule

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants