r/elasticsearch
Testing Elastic SIEM detections after pipeline changes
- upvotes
- 1
- comments
- 0
Post
Highlighted: the lines this signal was extracted from
Windows process events are still in Discover after an ingest pipeline update, but our PowerShell EQL rule stopped generating alerts. `process.command_line` is present, though `event.category` and a couple of other ECS fields changed. I can find the activity with a manual query, but the scheduled rule shows successful execution with zero alerts. Atomic Red Team gave us test activity, so at least we know what should have shown up. Has anyone tried cymulate for repeatable detection tests with Elastic? Not sure how much it would help here if the issue is ECS normalization rather than the rule itself. Now I'm wondering what else we broke with that pipeline update. How are you regression testing detections after changes like this? Open to any suggestions and what you r using for SIEM detections.