Skip to content

Conversation

Samirbous
Copy link
Contributor

@Samirbous Samirbous commented May 20, 2025

Exclude top noisy patterns.

#4733

@Samirbous Samirbous self-assigned this May 20, 2025
@Samirbous Samirbous added Rule: Tuning tweaking or tuning an existing rule OS: Windows windows related rules labels May 20, 2025
@Samirbous Samirbous requested a review from Mikaayenson May 20, 2025 09:24
@Samirbous Samirbous requested a review from terrancedejesus May 20, 2025 09:24
Copy link
Contributor

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
Copy link

tradebot-elastic commented May 20, 2025

⛔️ Test failed

Results
  • ❌ Account Discovery Command via SYSTEM Account (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
@tradebot-elastic
Copy link

tradebot-elastic commented May 20, 2025

⛔️ Test failed

Results
  • ❌ Account Discovery Command via SYSTEM Account (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
@tradebot-elastic
Copy link

tradebot-elastic commented May 20, 2025

⛔️ Test failed

Results
  • ❌ Account Discovery Command via SYSTEM Account (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
@tradebot-elastic
Copy link

tradebot-elastic commented May 20, 2025

⛔️ Test failed

Results
  • ❌ Account Discovery Command via SYSTEM Account (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
@tradebot-elastic
Copy link

tradebot-elastic commented May 20, 2025

⛔️ Test failed

Results
  • ❌ Account Discovery Command via SYSTEM Account (eql)
    • coverage_issue: no_rta
    • stack_validation_failed: no_rta
@Samirbous Samirbous merged commit 22cf1f0 into main May 21, 2025
11 checks passed
@Samirbous Samirbous deleted the Samirbous-patch-1 branch May 21, 2025 05:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport: auto Domain: Endpoint OS: Windows windows related rules Rule: Tuning tweaking or tuning an existing rule

4 participants