[Rule Tuning] First Time Seen Remote Monitoring and Management Tool

[w0rk3r]

Issues

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

Summary

• Drop Parent Logic
  • Logic will be ported to a separated rule, as in the current form, as we have the new terms settings to check process.name, a child process would only alert once, even if the parent is a complete different RMM
• Expand Signer and process list to be updated with threat reports, based on threat research blogs, lolrmm, and telem
• Reorder process and signer lists
• Adds new investigation guide + transforms

[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

• ❌ First Time Seen Remote Monitoring and Management Tool (kuery)
  • coverage_issue: no_rta
  • stack_validation_failed: no_rta

[Copilot]

Pull request overview

This PR tunes the existing Windows new terms rule “First Time Seen Remote Monitoring and Management Tool” to focus on first-time-seen RMM tool executions on a host (by host.id + process.name), while expanding the covered signer and process-name sets and modernizing the investigation guide with built-in Investigate transforms.

Changes:

• Removed the prior parent/child-of-RMM matching logic and updated the rule description accordingly.
• Expanded and reordered the RMM signer (process.code_signature.subject_name) and process-name (process.name.caseless) indicator lists.
• Added a new investigation guide (note), rule.investigation_fields, and multiple [[transform.investigate]] pivots for guided triage.