A log line is finished the moment it is written. Nobody owns it, nobody closes it, and nothing about it changes afterwards. That is exactly what makes logs easy to store and exactly why an alert shouldn't be treated like one.
An alert is a piece of work. Someone has to pick it up, someone has to decide what it was, and sometimes the attacker comes back after it has been closed. A detection tool that emits alerts as write-once records leaves all of that to a spreadsheet, a chat thread or the analyst's memory.
This article looks at what an alert needs to carry once it is treated as work, and at one way to build it.
Key Takeaways
An alert needs state: who has it, what has been done, when the first response happened and what the final call was.
Repeat detections on the same host should join the existing alert, and a returning attacker should reopen a closed one, not start a second story.
Queue order and response-time measures only mean something if the lifecycle is explicit and its history is kept.
What a…