All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: NetLabel audit messages
Date: Fri, 22 Sep 2006 14:43:47 -0400	[thread overview]
Message-ID: <45142EE3.4010704@hp.com> (raw)
In-Reply-To: <200609221406.04068.sgrubb@redhat.com>

Steve Grubb wrote:
> On Friday 22 September 2006 13:38, Paul Moore wrote:
>>In order to meet certain certification requirements, the NetLabel kernel
>>subsystem needs to write a small number of audit messages. 
> 
> What are the requirements you are addressing? (I have a feeling that its 
> similar to what we have to do to file systems.)

This is for LSPP certification, directly from our evaluator.  If it is
important that you know the exact requirement in CC terms I can dig that
up.  The basic motivation is that we need to generate an audit record
whenever there is a security relevant configuration change.

>>For the messages themselves, here is what I was thinking:
>>
>> "netlabel: <protocol> op=<operation> pid=<pid> tty=<tty> comm=<name>
>>            exe=<path> uid=<uid> auid=<auid> euid=<euid> suid=<suid>
>>            fsuid=<fsuid> gid=<gid> egid=<euid> sgid=<suid>
>>            fsgid=<fsuid> [<cipsov4 extras>|<managment extras>]"
> 
> This look very much like a syscall record...would it make sense to do this as 
> an aux record?

It looks like this is going to be discussed on irc.

-- 
paul moore
linux security @ hp

      reply	other threads:[~2006-09-22 18:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-22 17:38 NetLabel audit messages Paul Moore
2006-09-22 18:06 ` Steve Grubb
2006-09-22 18:43   ` Paul Moore [this message]

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=45142EE3.4010704@hp.com \
    --to=paul.moore@hp.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.