Closed MadameSheema closed 2 years ago
Pinging @elastic/security-threat-hunting (Team:Threat Hunting)
Pinging @elastic/security-solution (Team: SecuritySolution)
This is the same behavior on 8.3.x.
@MadameSheema does this mean that the bug also exists in 8.3.x, or that the behavior is correct in 8.3.x?
Edit: I see the working rule is named "IM 8.3"; I'm assuming that means the latter. Please let me know if that's incorrect.
@MadameSheema are there any errors to be seen? In the JS console or elsewhere? Can you share the full alert JSON for both working and non-working cases? If they're identical, mappings would also be useful.
@rylnd I was meaning that the behavior is correct on 8.3.3 since we are displaying on the alert details flyout all the matches, but on 8.4.0 is not like that.
Right now I'm doing the following, creating an IM alert on 8.3.3 and then upgrade to 8.4.0 so we can have the same alert on both versions.
I don't know if it is intended or not, but there is a clear mismatch on the Threat Intel
number for the same alert after the upgrade is performed. I can provide you access to the instance if needed.
@MadameSheema @rylnd @YulNaumenko I haven't dug into the code yet, but I'm thinking what's happened is the removal of _source
in favor of the fields
api. The UI code that probably traverses the response may have traversed _source to show all the results and may not have been adapted to use fields
instead, but that's my initial guess based on the alert json's provided
@MadameSheema could you please test it after the fix PR merged. The problem should disappear.
@YulNaumenko I checked it on BC2 and looks like is working fine. I would like a couple of extra eyes to take a look at it and run a bit of exploratory testing on it. @deepikakeshav-qasource @karanbirsingh-qasource can you please help? Thanks
Hi @MadameSheema,
We have validated above issue on 8.4.0 BC2 and it's fixed. 🟢
Build Details:
VERSION: 8.4.0 BC2
BUILD: 55166
COMMIT: 9e9e0d6a685cbc2858a85a357f93dcb76259fdee
Screenshots:
Rule Details
Alerts Page
Thanks!
Describe the bug:
Kibana/Elasticsearch Stack version:
Initial setup:
Steps to reproduce:
Threat Matched Detected
sectionCurrent behavior:
Expected behavior: