-
Notifications
You must be signed in to change notification settings - Fork 517
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
[Rule Tuning] User Added to Privileged Group #3373
Comments
Hey @s-bt, thanks for the contribution! Do you want to create a PR for this one? I can do it if you want |
I wouldn't mind if you did :) |
Made a mistake in the rule :(. It should be: iam where winlog.api:"wineventlog" and event.action == "added-member-to-group" and |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Resolved by #3763, thanks for bringing this to our attention |
Link to rule
https://github.com/elastic/detection-rules/blob/main/rules/windows/persistence_user_account_added_to_privileged_group_ad.toml
Description
I've just started testing Elastic Security, and during my first test I have found that the rule
User Added to Privileged Group
is using names instead of SIDs/RIDs. This is probelmatic for example in non-english environments. I would suggest switching to well known RIDsExample Data
THIS RULE WILL ALSO INCLUDE CHANGES TO LOCAL GROUPS ON NON-DOMAIN CONTROLLER MACHINES, SO IDEALLY IT WILL TO BE FURTHER FILTERED TO RUN ONLY ON DOMAIN CONTROLLERS (IF THAT'S POSSIBLE). OTHERWISE, CREATE A NEW RULE THAT JUST CONTAINS THE DOMAIN SIDs
EQL
The text was updated successfully, but these errors were encountered: