[Rule Tuning] Improve Detection Compatibility with Non-English Logs

[w0rk3r]

Issues

Resolves https://github.com/elastic/ia-trade-team/issues/416
Resolves #3397
Resolves https://github.com/elastic/enhancements/issues/20078

Summary

I tested the parsing of event fields in two Active Directory (AD) environments, one using German and another using Japanese. With the exception of the message field, all other fields were populated identically to their English counterparts.

This PR introduces the following changes:

• Remove event.action redundancy where event.code is specified,
  • Although my testing suggests that we populate this correctly independently of the language settings, we already had issues with them being added at the integration and not being just parsed: [Rule Tuning] Fix event.action conditions - AD Rules #3874, and this SDH comproves that this wasn't always the case: https://github.com/elastic/sdh-security-team/issues/761, so removing this ensures that we are compatible with previous integration versions and with winlogbeat (which wasn't tested here)
• Use winlog.event_data.NewUACList instead of the message field.

[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.

[w0rk3r]

Here is some context on why we had to use the message field here: #1790 (comment)

PR that fixed the issue and enables us to use winlog.event_data.NewUACList: elastic/integrations#8361

[w0rk3r]

Here is some context on why we had to use the message field here: #1790 (comment)

PR that fixed the issue and enables us to use winlog.event_data.NewUACList: elastic/integrations#8361

[Samirbous]

nice!

[w0rk3r]

Forgot to mention this one, Detailed File Share was replaced by network-share-object-access-checked a looong time ago: elastic/integrations#3299