public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.com>
To: wmealing <wmealing@redhat.com>
Cc: linux-audit@redhat.com, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org
Subject: Re: [RFC] Create an audit record of USB specific details
Date: Mon, 04 Apr 2016 08:48:39 +0200	[thread overview]
Message-ID: <1459752519.24025.5.camel@suse.com> (raw)
In-Reply-To: <1459742562-22803-1-git-send-email-wmail@redhat.com>

On Mon, 2016-04-04 at 00:02 -0400, wmealing wrote:
> From: Wade Mealing <wmealing@redhat.com>
> 
> Gday,
> 
> I'm looking to create an audit trail for when devices are added or removed
> from the system.
> 
> The audit subsystem is a logging subsystem in kernel space that can be
> used to create advanced filters on generated events.  It has partnered userspace
> utilities ausearch, auditd, aureport, auditctl which work exclusively on audit
> records.
> 
> These tools are able to set filters to "trigger" on specific in-kernel events
> specified by privileged users.  While the userspace tools can create audit 
> events these are not able to be handled intelligently (decoded,filtered or 
> ignored) as kernel generated audit events are.

That is a goal that should be debated in general.

> I have this working at the moment with the USB subsystem (as an example).
> Its been suggested that I use systemd-udev however this means that the audit
> tools (ausearch) will not be able to index these records.

Chaining this so tightly to the USB subsystem makes no sense.
If you do this, then please hook into the generic layer, that
is add_device(), and provide a method in the generic device structure
for providing information to the audit subsystem.

	Regards
		Oliver

  reply	other threads:[~2016-04-04  6:48 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-04  4:02 [RFC] Create an audit record of USB specific details wmealing
2016-04-04  6:48 ` Oliver Neukum [this message]
2016-04-04  7:47   ` Bjørn Mork
2016-04-05  8:40     ` Wade Mealing
2016-04-05 11:49       ` EXT :Re: " Boyce, Kevin P (AS)
2016-04-05 13:46         ` Greg KH
2016-04-05 13:52           ` Boyce, Kevin P (AS)
2016-04-05 15:35             ` Greg KH
2016-04-05 14:40       ` Alan Stern
2016-04-05 22:17         ` Wade Mealing
2016-04-05 17:02       ` Oliver Neukum
2016-04-05 19:38         ` Steve Grubb
2016-04-05 22:18           ` Greg KH
2016-04-04 12:56 ` Greg KH
2016-04-04 21:33   ` Steve Grubb
2016-04-04 21:48     ` Greg KH
2016-04-04 21:53       ` Greg KH
2016-04-05 13:07         ` Burn Alting
2016-04-05 13:44           ` Greg KH
2016-04-05 14:08             ` Burn Alting
2016-04-05 14:20               ` EXT :Re: " Boyce, Kevin P (AS)
2016-04-05 14:37                 ` Burn Alting
2016-04-05 14:42                   ` Boyce, Kevin P (AS)
2016-04-05 22:39                     ` Burn Alting
2016-04-04 21:37   ` Paul Moore
2016-04-04 21:50     ` Greg KH
2016-04-05  2:54       ` Paul Moore
2016-04-05  3:39         ` Greg KH
2016-04-05 14:50           ` Paul Moore
2016-04-04 21:37 ` Steve Grubb
2016-04-04 21:54   ` Greg KH
     [not found]     ` <CALJHwhR-SA7K=fD=DUXE7EFq+4gWKPaY+B5z6jdCj7180wg_vg@mail.gmail.com>
2016-04-05  1:54       ` Wade Mealing
2016-04-05  2:43         ` Greg KH
2016-04-05  2:47         ` Greg KH
2016-04-04 22:10   ` Burn Alting

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=1459752519.24025.5.camel@suse.com \
    --to=oneukum@suse.com \
    --cc=linux-audit@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=wmealing@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox