All of lore.kernel.org
 help / color / mirror / Atom feed
From: Enzo Matsumiya <ematsumiya@suse.de>
To: linux-audit@redhat.com
Subject: [RFC] audit.spec: create audit group for log read access
Date: Wed, 20 Jan 2021 14:52:24 -0300	[thread overview]
Message-ID: <20210120175224.dchx7f6z6i2bslst@hyori> (raw)

Hi,

We (SUSE) would like to introduce an "audit" group for log read access.

This would be handled only by patching the .spec file to create the
group and modify the permissions of the default log dir/file to:

drwxr-x--- 1 root audit     322 25. Okt 21:06 /var/log/audit/
-rw-r----- 1 root audit 1815972 26. Okt 22:23 /var/log/audit/audit.log

No source code modifications are required, as log_group_parser() should
handle invalid entries.

If an enforcement or warning is required for when log_group is not
using the default "audit" group, it should be easy to do as well.

For those wondering, Common Criteria seems to be fine with this
modification.

Excerpt from SUSE's CC certification (RH's seems to match):

---- begin ----
6.2.1.4 Restricted audit review (FAU_SAR.2)

FAU_SAR.2.1	The TSF shall prohibit all users read access to the audit records, except those
		users that have been granted explicit read-access.

Application Note: The protection of the audit records is based on the Unix permission bit
settings defined by FDP_ACC.1(PSO) supported by FDP_ACF.1(PSO).
---- end ----

Please let me know of your concerns, if any.

I have a working patch that I can submit right away in case this gets an
ok.


Cheers,

Enzo

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


             reply	other threads:[~2021-01-20 18:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 17:52 Enzo Matsumiya [this message]
2021-01-20 18:16 ` [RFC] audit.spec: create audit group for log read access Steve Grubb
2021-01-20 21:39   ` Enzo Matsumiya
2021-01-20 23:15     ` Steve Grubb

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=20210120175224.dchx7f6z6i2bslst@hyori \
    --to=ematsumiya@suse.de \
    --cc=linux-audit@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.