-
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] auditd not receiving event when outside of host network namespace #28063
Comments
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
Just faced the same problem while configuring auditbeat in Kubernetes. That'd be great to add a note about it in auditbeat documentation until it is fixed |
@andrewkroh I happened to run
In the container -
Logs -
|
@r00tu53r I wonder if something changed in the kernel. Your tests were on |
Thanks @andrewkroh I will confirm my tests on a few older versions. |
Hi! We're labeling this issue as |
Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform) |
While running Auditbeat's
auditd
module in a container it will not receive events unless I put it into the host's network namespace. I believe this used to work because the docs don't mention anything about the network namespace requirement.While doing some brief searching I found a newer flag
NETLINK_F_LISTEN_ALL_NSID
that I wonder if it is related. And some commits like torvalds/linux@7212462. This needs more research, but the goal would be to see if we can still run Auditbeat in its own namespace and receive audit events. If we can't, then we should update the docs to mention the requirement to run in the host's network namespace.Version: 7.14.2
OS: Linux akroh-beats-dev 5.11.0-1018-gcp #20~20.04.2-Ubuntu SMP Fri Sep 3 01:01:37 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Discuss: https://discuss.elastic.co/t/auditbeat-on-docker-fails-to-run-auditd-module/284399
Config:
The text was updated successfully, but these errors were encountered: