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

[RAC] Event Renderer: Some rows do not have default reason statement included #108987

Closed
mdefazio opened this issue Aug 17, 2021 · 9 comments
Closed
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting Security Solution Threat Hunting Team Theme: rac label obsolete v7.15.0

Comments

@mdefazio
Copy link
Contributor

A few rule rows do not seem to have default reason statements on them:
image

Whether we show them in the table or not, these would still be needed when opening the flyout.

@mdefazio mdefazio added bug Fixes for quality problems that affect the customer experience Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Theme: rac label obsolete labels Aug 17, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-threat-hunting (Team:Threat Hunting)

@michaelolo24
Copy link
Contributor

michaelolo24 commented Aug 23, 2021

Hey @mdefazio, the reason the field isn't showing up is because the alert is missing the fields necessary to generate that statement. Taking a look at filtering for alerts that don't have reason defined, you see the severity and risk score are also missing. As this message expands to include a bit more data or depend on different data, it could be shown more consistently

image

cc @paulewing

@mdefazio
Copy link
Contributor Author

What is the recommended path forward here? Would we be able to provide a more broad reason statement that reads similarly to our others, but just doesn't include severity or risk score? (Though I believe it was mentioned that there should be a severity on these).

@michaelolo24
Copy link
Contributor

@mdefazio can you check if you're still seeing this issue? I've been un able to reproduce it and I'm assuming it may have had to do with the alert table showing data from other developers systems and their code being out of sync.

@marshallmain
Copy link
Contributor

Severity and risk score are both required fields on the rules so they should be present on every alert - if there's a way to reproduce those alerts without severity and risk score that would be a bug.

@michaelolo24
Copy link
Contributor

@marshallmain I haven't been able to reproduce it and only ever saw it on the dev instance, but I haven't seen it there anymore either even when I filter for alerts without the signal.reason field. I lean towards closing this issue until we see it again?

@mdefazio
Copy link
Contributor Author

mdefazio commented Sep 3, 2021

I don't seem to be able to reproduce this either.

@MadameSheema
Copy link
Member

Closing as this is not happening anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting Security Solution Threat Hunting Team Theme: rac label obsolete v7.15.0
Projects
None yet
Development

No branches or pull requests

6 participants