Skip to content
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

SIEM Signals Index: Unique "incident id" or "signal id" per signal fired instead of just _id for doc record. #75129

Open
Tracked by #165878
SimSama opened this issue Aug 17, 2020 · 2 comments
Labels
enhancement New value added to drive a business result Feature:Detection Rules Security Solution rules and Detection Engine Team:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SIEM

Comments

@SimSama
Copy link

SimSama commented Aug 17, 2020

Describe the feature:
The signals index has an _id field, that uniquely identifies the signal document, but we'd like to have a human readable, incrementing unsigned integer for signal.incident_id. e.g. Incident_id 1234567890, 1234567891, etc.

Describe a specific use case for the feature:
If one team member or user is investigating an incident, they should be able to quickly share the given "signal id", or incident id in more general terms, that uniquely identifies the individual signal that fired.

In the SIEM tab, an analyst should be able to search by pasting in an "incident_id", and it should retrieve the underlying signal document.

Just as well programmatic systems should be able to poll (incidents_ids > last_incident_id_seen) and retrieve the latest incidents.

Thanks,

@elasticmachine
Copy link
Contributor

Pinging @elastic/siem (Team:SIEM)

@spong spong added the Feature:Detection Rules Security Solution rules and Detection Engine label Aug 17, 2020
@peluja1012 peluja1012 added the enhancement New value added to drive a business result label Sep 16, 2020
@MindyRS MindyRS added the Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. label Oct 27, 2020
@peluja1012 peluja1012 added the Team:Detection Alerts Security Detection Alerts Area Team label Oct 26, 2021
@MindyRS MindyRS added the Team:Detections and Resp Security Detection Response Team label Feb 23, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@yctercero yctercero added Team:Detection Engine Security Solution Detection Engine Area and removed Team:Detection Alerts Security Detection Alerts Area Team labels May 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:Detection Rules Security Solution rules and Detection Engine Team:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:SIEM
Projects
None yet
Development

No branches or pull requests

7 participants