Case 59F80A · Blue team / DFIR · L2 Practitioner
New Rule Floods the Queue
Live alertYou deployed a rule for encoded PowerShell yesterday. It has fired 4,100 times in 24 hours; spot checks show most come from the endpoint management agent running signed maintenance scripts. Analysts have started bulk-closing it.
Interview questionA detection you shipped is flooding the queue and analysts are ignoring it. What do you do?
- 01 What happened?
- 02 What is the impact?
- 03 What do you do?
What a strong answer covers
Try it out loud first. Then check yourself:
- Stop the damage: switch the rule to monitor-only or lower its severity, so real alerts are not buried while you fix it.
- Find the top contributors by parent process, signer, path and host, and confirm they are benign.
- Exclude narrowly: the management agent parent plus its signer and script path, never the whole host or all PowerShell.
- Re-test against known-bad samples so the exclusion did not create a blind spot, then redeploy and record why.
If the interviewer pushes back
- An attacker learns about your exclusion. How could they abuse it, and how do you make that harder?