All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: "Wieprecht, Karen M." <Karen.Wieprecht@jhuapl.edu>
Subject: Re: [RFC] NISPOM audit rules - first draft
Date: Wed, 18 Apr 2007 17:16:06 -0400	[thread overview]
Message-ID: <200704181716.06196.sgrubb@redhat.com> (raw)
In-Reply-To: <FC11D747323EB24493CDC753367EEB92019FA742@aplesnation.dom1.jhuapl.edu>

On Wednesday 18 April 2007 16:41, Wieprecht, Karen M. wrote:
> 1. auditd complained about using  the -k (keyword) flag on lines that
> were not file watch lines.

Yes, this was mentioned on IRC last week and fixed in my development copy. It 
will be in 1.5.3.

> This could be a newer feature not supported by our audit subsystem  (we
> are running RHEL4 update 4 with audit-1.0.14 I believe).  Can you verify
> if this is a general syntax problem or a
> your-audit-version-doesn't-support-this problem ?  Thanks.

1.5.2 does not work with RHEL4.

> 2. We had two additional lines in out audit.rules to capture failed
> chown, chgrp, and chmod:
>
> -a exit,always -S 90 -F exit=-1
> -a exit,always -S 92 -F exit=-1

I think you want 90-94 on x86_64. I guess they do return -EPERM. The way that 
we are doing this for 1.5.2 is using special syntax allowed by the newer 
kernels:

-a exit,always -F perm=a -F exit=-13

This tells the kernel to select any syscall that changes file attributes. We 
should probably add another line with -F exit=-1

> If these actions aren't already being captured by another NISPOM audit
> rule, you might consider adding them since failed attempts to chown,
> chgrp, chmod are indications of someone possibly trying to open up
> access to  files they don't have rights to which would fall into the
> "failed file access attempts" category. 

Yep, I'll add a line.

-Steve

      reply	other threads:[~2007-04-18 21:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01 18:33 [RFC] NISPOM audit rules - first draft Steve Grubb
2007-04-13 18:24 ` Timothy R. Chavez
2007-04-13 18:31   ` Steve Grubb
2007-04-13 21:45     ` Brian K. Whatcott
2007-04-13 21:54       ` Steve Grubb
2007-04-18 20:41         ` Wieprecht, Karen M.
2007-04-18 21:16           ` Steve Grubb [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=200704181716.06196.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=Karen.Wieprecht@jhuapl.edu \
    --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.