-
Notifications
You must be signed in to change notification settings - Fork 126
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add 'Managing the audit daemon' page
- Loading branch information
Showing
2 changed files
with
29 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
= Managing the audit daemon (`auditd`) | ||
|
||
Starting with the first release based on Fedora 39, Fedora CoreOS includes the audit daemon (`auditd`) to load and manage audit rules. | ||
|
||
While the audit daemon | ||
Like all system daemons on Fedora CoreOS, the audit daemon is managed by systemd but with an exception: it can not be stopped or restarted via `systemctl stop auditd` or `systemctl restart auditd` for compliance reasons. | ||
|
||
From [Unable to restart/stop auditd service using systemctl command in RHEL](https://access.redhat.com/solutions/2664811): | ||
|
||
> The reason for this unusual handling of restart/stop requests is that auditd is treated specially by the kernel: the credentials of a process that sends a killing signal to auditd are saved to the audit log. The audit developers do not want to see the credentials of PID 1 logged there. They want to see the login UID of the user who initiated the action. | ||
|
||
To stop and restart the audit daemon, you should use the following commands: | ||
|
||
[source,bash] | ||
---- | ||
$ sudo auditctl stop | ||
$ sudo systemctl start # Only if you want to restart the daemon | ||
---- | ||
|
||
You man also use the following commands to reload the rules, rotate the logs, resume (?), fetch the state: | ||
|
||
[source,bash] | ||
---- | ||
$ sudo auditctl reload | ||
$ sudo auditctl rotate | ||
$ sudo auditctl resume | ||
$ sudo auditctl state | ||
---- |