Skip to content

[Rule Tuning] Suspicious Access to LDAP Attributes - Ignored Fields #4698

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
w0rk3r opened this issue May 5, 2025 · 0 comments
Open

[Rule Tuning] Suspicious Access to LDAP Attributes - Ignored Fields #4698

w0rk3r opened this issue May 5, 2025 · 0 comments
Assignees
Labels
Rule: Tuning tweaking or tuning an existing rule Team: TRADE

Comments

@w0rk3r
Copy link
Contributor

w0rk3r commented May 5, 2025

Link to Rule

https://github.com/elastic/detection-rules/blob/main/rules/windows/discovery_high_number_ad_properties.toml

Rule Tuning Type

False Negatives - Enhancing detection of true threats that were previously missed.

Description

We need to investigate the behavior of this rule when winlog.event_data.Properties is marked as ignored due to the length of the field. When a field is marked as ignored, you cannot query it using either KQL or EQL, but we should validate the behavior on ES|QL.

Example Data

No response

@w0rk3r w0rk3r added Rule: Tuning tweaking or tuning an existing rule Team: TRADE labels May 5, 2025
@w0rk3r w0rk3r self-assigned this May 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Rule: Tuning tweaking or tuning an existing rule Team: TRADE
Projects
None yet
Development

No branches or pull requests

1 participant