Skip to content

[Rule Tuning] Deleting Backup Catalogs with Wbadmin #4671

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
tyler-mcadam opened this issue Apr 28, 2025 · 1 comment · May be fixed by #4715
Open

[Rule Tuning] Deleting Backup Catalogs with Wbadmin #4671

tyler-mcadam opened this issue Apr 28, 2025 · 1 comment · May be fixed by #4715
Assignees
Labels
community Rule: Tuning tweaking or tuning an existing rule Team: TRADE

Comments

@tyler-mcadam
Copy link

tyler-mcadam commented Apr 28, 2025

Link to Rule

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

Rule Tuning Type

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

Description

I'm not sure if these were left out for a reason, but it would make sense to me to group any deletion of backups via wbadmin into one alert. Is it worth including 'delete backup' and 'delete systemstatebackup' or should they make separate alerts?

Example Data

Image

Image

edit: Screenshots don't show it but backup and systemstatebackup prompt for -keepVersions, -version or -deleteOldest, but I don't think these should matter for detection.

@tyler-mcadam tyler-mcadam added Rule: Tuning tweaking or tuning an existing rule Team: TRADE labels Apr 28, 2025
@w0rk3r
Copy link
Contributor

w0rk3r commented May 8, 2025

@tyler-mcadam thanks for the suggestion, I think it makes sense, I'll do a PR for it

@w0rk3r w0rk3r linked a pull request May 9, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Rule: Tuning tweaking or tuning an existing rule Team: TRADE
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants