Skip to content

Conversation

WavyEbuilder
Copy link

auditd doesn't actually need to be able to write logs, only create, append, read, rename, and setattr them. Given that great lengths are already taken to ensure audit log confidentiality and integrity (e.g. marking as mls_systemhigh and granting cap_sys_nice to prioritise over other processes to not miss audit events), it makes sense to not grant an unnecessary permission which would allow a comprimised audit daemon to tamper with the audit logs.

auditd doesn't actually need to be able to write logs, only create,
append, read, rename, and setattr them. Given that great lengths are
already taken to ensure audit log confidentiality and integrity (e.g.
marking as mls_systemhigh and granting cap_sys_nice to prioritise over
other processes to not miss audit events), it makes sense to not grant
an unnecessary permission which would allow a comprimised audit daemon
to tamper with the audit logs.

Signed-off-by: Rahul Sandhu <[email protected]>
@WavyEbuilder
Copy link
Author

@zpytela Ping

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant