public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Michael Mather <michael.mather@teksavvy.com>
To: linux-audit <linux-audit@redhat.com>
Subject: Re: Sucess or failure?
Date: Sun, 22 Jul 2012 10:18:17 -0400	[thread overview]
Message-ID: <1342966697.2518.9.camel@debian.domain_name> (raw)
In-Reply-To: <CAH5b-BUfXu-vTvNuuXD6SJJtW9djK0sEvZQqBUAKk5jG784Onw@mail.gmail.com>

Thanks for the replies.

The problem is that the PCI requirements say:

10.3 Record at least the following audit trail entries for all system
components for each event:
...
10.3.4 Success or failure indication.

I don't know if PCI would accept the notion that this was success.

Michael
-------

On Sun, 2012-07-22 at 07:52 +0200, yersinia wrote:
> >From the point of view of the linux kernel, and of the audit, you have
> the right to execute the cp, you don't have permission denied. So the
> result is success.
> 
> Best regards
> 
> 2012/7/22, Michael Mather <michael.mather@teksavvy.com>:
> > Hi,
> >
> > I enter the command "sudo cp qwerty /etc/xxx"
> > and get the reply:  "cp: cannot stat `qwerty': No such file or directory."
> >
> > A number of log entries are written. The last two are, in part:
> >
> > type=SYSCALL success=yes
> > type=EXECVE  argc=3 a0="cp" a1="qwerty" a2="/etc/xxx"
> >
> > My problem is with "success=yes".
> >
> > What is happening?
> >
> > Thanks - Michael Mather
> > -----------------------
> >
> >
> >
> > --
> > Linux-audit mailing list
> > Linux-audit@redhat.com
> > https://www.redhat.com/mailman/listinfo/linux-audit
> >
> 

  reply	other threads:[~2012-07-22 14:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-22  1:48 Sucess or failure? Michael Mather
2012-07-22  2:34 ` Peter Moody
2012-07-22  3:44 ` Giang Nguyen
2012-07-22  5:52 ` yersinia
2012-07-22 14:18   ` Michael Mather [this message]
     [not found]   ` <1342966522.2518.7.camel@debian.domain_name>
2012-07-22 17:44     ` yersinia

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=1342966697.2518.9.camel@debian.domain_name \
    --to=michael.mather@teksavvy.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox