Security Event Correlation: Normalised Events & Incident Aggregation Layer #174
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
This PR introduces the foundation for security event correlation by adding a normalised security event model and an initial incident aggregation layer.
The goal of this change is to prepare the backend for correlating related authentication and security events into higher-level incidents, supporting future security analysis and reporting features.
Key Changes
SecurityEventmodel to standardise security telemetry.SecurityEventTypedefinitions to unify event classification across sources.Design Notes
Testing / Validation
Scope
This change is self-contained and safe to merge. It establishes the groundwork for subsequent security insights and reporting features.
Primary contributor: King Hei Law