-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
auditbeat/socket returns incorrect process information #17165
Comments
Pinging @elastic/siem (Team:SIEM) |
I'm running auditbeat 7.10.1 and have recently enabled the socket module and have also noticed that auditbeat reports incorrect process information for some socket flow events periodically. I've noticed that this is more noticeable on hosts with a high amount of network activity occurring. Has this issue gained any traction since April of last year? |
This appears to be a pretty serious flaw in Auditbeat. If we can't trust the process information being logged into our SIEM, its really makes me question whether this data could be used in any official legal capacity. |
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
I've just had a look at this with a view that it is probably a data aliasing issue. Initially I looked at building with the race detector on ( fatal error: checkptr: converted pointer straddles multiple allocations There is a bunch of unsafe shenanigans going on in This turns out to be unrelated. I was able to reliably replicate the original issue by running a number of instances of |
This is a result of sockets being shared between processes resulting in PIDs/processes colliding for a flow and then having a skewed update. I have a partial fix that is reliable that is based on stratifying socket and flows by PID as well as socket address and network address. I'll clean it up and send it soon. |
Please include configurations and logs if available.
auditbeat info
auditbeat
was started using systemd service filesystem module configuration
locally
remotely
View logs in Kibana using the following filter, substituting in the pid printed above (it was 20785 in this test case).
agent.type: auditbeat and process.pid: (20785) and event.action: network_flow
snipped to just process object:
In this case, the Kafka process above has a pid of
7268
The text was updated successfully, but these errors were encountered: