I'm working with Elastic Security and have a recurring alert that triggers for the same user and behavior roughly once a week.
We've investigated it and currently consider the activity benign. However, I don't want to suppress the alert entirely, because I still want analysts to see every new occurrence and be able to track its history.
Keeping one case open indefinitely feels awkward, but closing each occurrence separately makes it difficult to maintain a continuous history.
How do you handle this in your SOC? Is there a common approach or feature in Elastic Security for tracking recurring activity while preserving visibility into every occurrence?
A pattern that works: keep one long-running case as the "known activity" record and attach each new occurrence to it, closing the individual alerts as benign while referencing the case ID in a tag, note or custom field. You keep per-occurrence visibility and one continuous timeline. Worth noting that alert suppression and matching rule exceptions both trade away some per-occurrence visibility — suppression collapses duplicates within a window, and exceptions can close or hide matches — so they fit the opposite goal. A saved search or tag filtered to that activity ID also makes history easy to pull up.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.