[Rule Tuning] Multiple Remote Management Tool Vendors on Same Host

[w0rk3r]

Issues

Part of https://github.com/elastic/ia-trade-team/issues/896

Summary

• Updates the process list
• Uses process.name.caseless, works as lowercase on ES|QL
  • Drops Endgame support as it doesn't have the caseless field
• Fix some typos/small redundancies

[github-actions]

Rule: Tuning - Guidelines

These guidelines serve as a reminder set of considerations when tuning an existing rule.

Documentation and Context

• Detailed description of the suggested changes.
• Provide example JSON data or screenshots.
• Provide evidence of reducing benign events mistakenly identified as threats (False Positives).
• Provide evidence of enhancing detection of true threats that were previously missed (False Negatives).
• Provide evidence of optimizing resource consumption and execution time of detection rules (Performance).
• Provide evidence of specific environment factors influencing customized rule tuning (Contextual Tuning).
• Provide evidence of improvements made by modifying sensitivity by changing alert triggering thresholds (Threshold Adjustments).
• Provide evidence of refining rules to better detect deviations from typical behavior (Behavioral Tuning).
• Provide evidence of improvements of adjusting rules based on time-based patterns (Temporal Tuning).
• Provide reasoning of adjusting priority or severity levels of alerts (Severity Tuning).
• Provide evidence of improving quality integrity of our data used by detection rules (Data Quality).
• Ensure the tuning includes necessary updates to the release documentation and versioning.

Rule Metadata Checks

• updated_date matches the date of tuning PR 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. Review to ensure the original intent of the rule is maintained.

Testing and Validation

• Validate that the tuned rule's performance is satisfactory and does not negatively impact the stack.
• Ensure that the tuned rule has a low false positive rate.

[tradebot-elastic]

⛔️ Test failed

Results

• ❌ Multiple Remote Management Tool Vendors on Same Host (esql)
  • coverage_issue: no_rta
  • stack_validation_failed: no_rta

[Copilot]

Pull request overview

This PR tunes the Windows ES|QL detection rule “Multiple Remote Management Tool Vendors on Same Host” to improve RMM process matching and remove Endgame support in favor of process.name.caseless.

Changes:

• Updated the ES|QL vendor mapping list and switched matching to process.name.caseless.
• Removed Endgame as a supported data source (indices + tags) and updated updated_date.
• Minor investigation guide updates and added https://lolrmm.io/ as a reference.

[tradebot-elastic]

⛔️ Test failed

Results

• ❌ Multiple Remote Management Tool Vendors on Same Host (esql)
  • coverage_issue: no_rta
  • stack_validation_failed: no_rta

[eric-forte-elastic]

process.name.caseless I think is a endpoint enrichment right?

Not an issue per say, but I think this will cause the Sysmon (logs-windows.sysmon_operational-), Winlogbeat (winlogbeat-), and Windows Security Events (logs-system.security*) to not match on process name. Just making sure this is intentional, thanks!

[w0rk3r]

I've added (or worked with integrations to add) this field to all of the integrations, the only one that currently doesn't support it is Endgame. Related PRs:

• [Enhancement] Add ".caseless" fields to process events integrations#10533
• [Enhancement] Improve S1 Cloud Funnel Process Events compatibility integrations#11019
• [Enhancement] Add ".caseless" fields to MDE process events integrations#11020
• crowdstrike: implement enhanced field mapping logic integrations#12913