[Rule Tuning] Misc GenAI Tuning

[Mikaayenson]

Pull Request

Issue link(s):

Summary - What I changed

process.command_line is not always available. Typically only available for Defend alerts or when setting the advanced object.

How To Test

Checklist

• Added a label for the type of pr: bug, enhancement, schema, maintenance, Rule: New, Rule: Deprecation, Rule: Tuning, Hunt: New, or Hunt: Tuning so guidelines can be generated
• Added the meta:rapid-merge label if planning to merge within 24 hours
• Secret and sensitive material has been managed correctly
• Automated testing was updated or added to match the most common scenarios
• Documentation and comments were added for features that require explanation

[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

• ❌ GenAI Process Accessing Sensitive Files (eql)
  • coverage_issue: no_rta
  • stack_validation_failed: no_rta

[tradebot-elastic]

⛔️ Test failed

Results

• ❌ GenAI Process Connection to Unusual Domain (kuery)
  • coverage_issue: no_rta
  • stack_validation_failed: no_rta
• ❌ GenAI Process Accessing Sensitive Files (eql)
  • coverage_issue: no_rta
  • stack_validation_failed: no_rta

[tradebot-elastic]

⛔️ Test failed

Results

• ❌ GenAI Process Connection to Unusual Domain (kuery)
  • coverage_issue: no_rta
  • stack_validation_failed: no_rta
• ❌ GenAI Process Accessing Sensitive Files (eql)
  • coverage_issue: no_rta
  • stack_validation_failed: no_rta

[eric-forte-elastic]

Small tuning looks good 👍 Verified in telemetry with the process command line often not populated in logs-endpoint.events.network* and logs-endpoint.events.file*.

[imays11]

Any other way to account for the values you're removing? Or do we no longer care to include them?

[tradebot-elastic]

⛔️ Test failed

Results

• ❌ GenAI Process Connection to Unusual Domain (kuery)
  • coverage_issue: no_rta
  • stack_validation_failed: no_rta
• ❌ GenAI Process Accessing Sensitive Files (eql)
  • coverage_issue: no_rta
  • stack_validation_failed: no_rta

[tradebot-elastic]

⛔️ Test failed

Results

• ❌ GenAI Process Connection to Unusual Domain (kuery)
  • coverage_issue: no_rta
  • stack_validation_failed: no_rta
• ❌ GenAI Process Accessing Sensitive Files (eql)
  • coverage_issue: no_rta
  • stack_validation_failed: no_rta