Add parsed timestamps to alerts - #870
Open
besendorf wants to merge 3 commits into
Open
Conversation
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
Some alerts omitted their event time even though the source module had already parsed a suitable timestamp. This kept otherwise timestamped detections out of the alert timeline.
For AppOps, an IOC match applies to the package name rather than to a particular permission entry. A package can have multiple last-access and last-rejection timestamps across its operations and UID states, so the alert uses the latest of those timestamps. This places the package-level alert at its most recent known AppOps activity without depending on permission iteration order. It does not represent the package installation time, compromise time, or IOC detection time.