Skip to content

Support for new fields in correlation rule form context #1175

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
2 tasks
mjabascal10 opened this issue Apr 23, 2025 · 0 comments
Open
2 tasks

Support for new fields in correlation rule form context #1175

mjabascal10 opened this issue Apr 23, 2025 · 0 comments
Assignees

Comments

@mjabascal10
Copy link
Contributor

Describe the feature

The correlation rule form allows users to define conditions to detect complex patterns of events. To enhance rule precision and event management, two new fields will be added to the rule schema and UI.

New Fields
AfterEvents ([]SearchRequest):
A list of additional conditions that must occur after the main event. Each condition can have its own index pattern, expression list, optional OR blocks, time window (within), and occurrence count. This enables modeling of sequences or follow-up actions.

DeduplicatedBy ([]string):
A list of fields used to deduplicate correlated events, such as "source_ip" or "hostname". This helps avoid generating multiple incidents for the same root pattern.

Use Case

Adding support for afterEvents and deduplicatedBy enables more accurate and flexible correlation rules by:

Allowing the definition of multi-step attack sequences through post-event conditions.

Reducing alert noise by deduplicating events based on custom criteria, improving detection quality and operational efficiency.

Proposed Solution

No response

Other Information

No response

Acknowledgements

  • I may be able to implement this feature request
  • This feature might incur a breaking change
@mjabascal10 mjabascal10 added needs-triage Needs to be triaged and removed needs-triage Needs to be triaged labels Apr 23, 2025
@mjabascal10 mjabascal10 self-assigned this Apr 23, 2025
@mjabascal10 mjabascal10 moved this to 🏗 In progress in UTMStack OSS Apr 23, 2025
@mjabascal10 mjabascal10 moved this from 🏗 In progress to 👀 In review in UTMStack OSS Apr 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 👀 In review
Development

No branches or pull requests

1 participant