From: Steve Grubb <sgrubb@redhat.com>
To: "linux-audit@redhat.com" <linux-audit@redhat.com>
Cc: "MAUPERTUIS, PHILIPPE" <philippe.maupertuis@equensworldline.com>
Subject: Re: systemd daemon and auid
Date: Wed, 07 Apr 2021 09:23:01 -0400 [thread overview]
Message-ID: <5450942.DvuYhMxLoT@x2> (raw)
In-Reply-To: <5F4EE10832231F4F921A255C1D9542981572221E@DEERLM99EX7MSX.ww931.my-it-solutions.net>
On Wednesday, April 7, 2021 3:20:22 AM EDT MAUPERTUIS, PHILIPPE wrote:
> I understand that daemons started by systemd have a uid -1.
> For a specific daemon, I would like to have a different auid to trace what
> the daemon is doing. By having a distinct auid it would be monitored
> without specific rules. Is that possible ?
While it may be possible, that violates how the audit system was designed to
operate. Setting the loginuid also sets the session ID. The utilities look
for those events to determine that a login has occurred and then track that.
> Otherwise what would be the best way to monitor a specific daemon ?
There is auditing by application.
-a always,exit -F exe=/usr/sbin/httpd -F arch=b64 -S open,openat, ...
-Steve
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
prev parent reply other threads:[~2021-04-07 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 7:20 systemd daemon and auid MAUPERTUIS, PHILIPPE
2021-04-07 13:23 ` Steve Grubb [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5450942.DvuYhMxLoT@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=philippe.maupertuis@equensworldline.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox