All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH 0/2] audit: log binding and unbinding to netlink multicast socket
Date: Fri, 24 Jul 2015 18:42:29 -0400	[thread overview]
Message-ID: <CAHC9VhQamNmHO=PF5o_XuGk3qgS_pG8KCYE0kSx_WdAfGu5BdA@mail.gmail.com> (raw)
In-Reply-To: <1470011.Rp6MUNe0GI@x2>

On Thu, Jul 23, 2015 at 4:45 PM, Steve Grubb <sgrubb@redhat.com> wrote:
> Hello,
>
> I am resurrecting this old patch. Its been cleaned up by adding a simple task
> logging function which should, in the future, serve almost all kernel logging
> needs. The cleaned up bind and unbind functions call it to create the preamble
> and then finish with specific data items for bind/unbinding.
>
> In essence, this patch logs connecting and unconnecting to the audit netlink
> multicast socket. This is needed so that during investigations a security
> officer can tell who or what had access to the audit trail. This helps to meet
> the FAU_SAR.2 SFR for Common Criteria.

Hi Steve,

I knew we would get you writing kernel patches eventually ;)

A little birdie mentioned to me offlist that there are issues with
application bind/unbind events not being audited based on how they do
the audit, have you run into this in your testing of this patch?

-- 
paul moore
www.paul-moore.com

  reply	other threads:[~2015-07-24 22:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 20:45 [PATCH 0/2] audit: log binding and unbinding to netlink multicast socket Steve Grubb
2015-07-24 22:42 ` Paul Moore [this message]
2016-11-30 19:23 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='CAHC9VhQamNmHO=PF5o_XuGk3qgS_pG8KCYE0kSx_WdAfGu5BdA@mail.gmail.com' \
    --to=paul@paul-moore.com \
    --cc=linux-audit@redhat.com \
    --cc=sgrubb@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.