Conversation
|
⛔️ Test failed Results
|
Rule: Tuning - GuidelinesThese guidelines serve as a reminder set of considerations when tuning an existing rule. Documentation and Context
Rule Metadata Checks
Testing and Validation
|
There was a problem hiding this comment.
Pull request overview
This PR tunes the existing Windows ES|QL rule “First Time Seen DNS Query to RMM Domain” by expanding the known RMM parent-domain allowlist/lookup list (sourced from lolrmm.io) to improve coverage for non-browser DNS lookups to RMM infrastructure.
Changes:
- Updated the rule
updated_dateto2026/07/02. - Added
https://lolrmm.io/to rule references. - Expanded the
parent_domain IN (...)RMM domain list used by the ES|QL query.
|
|
|
⛔️ Test failed Results
|
|
⛔️ Test failed Results
|
|
none of the 65 excluded parent domains appear in the query's WHERE parent_domain IN (...) list, so they'll never trigger the rule. The two lists are deliberately disjoint. tailscale.io (excluded) vs tailscale.com (included) — different TLD, so the exclusion comment doesn't actually suppress Tailscale traffic on .com, and the query would still alert on tailscale.com lookups. If the intent behind excluding tailscale.io was to suppress Tailscale noise generally, you may want to also exclude tailscale.com from the include list (or vice versa, decide if tailscale.com traffic is meaningful RMM-abuse signal you want to keep). |
|
Clarified with Samir that this is expanding the domain list, and the exclusion refers to the lolrmm dataset and not the existing query. g2g |
|
⛔️ Test failed Results
|
Issues
Part of https://github.com/elastic/ia-trade-team/issues/896
Summary
Expand the domain list based of lolrmm.io (Excluded about 30 domains which seemed too generic and would cause FPs)