systemd daemon and auid

systemd daemon and auid

[MAUPERTUIS, PHILIPPE]

[-- Attachment #1.1: Type: text/plain, Size: 1274 bytes --]

Hello,
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 ?
Otherwise what would be the best way to monitor a specific daemon ?
Regards
Philippe
Worldline, equensWorldline and Ingenico are registered trademarks and trade names owned by the Worldline Group. This e-mail and any documents attached are confidential and intended solely for the addressee. If you are not the intended recipient of this e-mail, you are not authorized to copy, disclose, use or retain it. Please notify the sender immediately and delete this e-mail (including any attachments) from your systems. As e-mails may be intercepted, amended or lost, they are not secure. Worldline and its subsidiaries therefore cannot accept liability for any errors in their content. Although the Worldline Group endeavours to maintain a virus-free network, we do not warrant that this e-mail is virus-free and do not accept liability for any damages or losses resulting from any transmitted virus if any. The risks are deemed to be accepted by anyone who communicates with Worldline or its subsidiaries by e-mail.

[-- Attachment #1.2: Type: text/html, Size: 6289 bytes --]

[-- Attachment #2: Type: text/plain, Size: 106 bytes --]

--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit

Re: systemd daemon and auid

[Steve Grubb]

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