linux-audit.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com, varun gulati <gitmevg@yahoo.co.in>
Subject: Re: How to Audit ssh Commands --> wget, scp
Date: Mon, 09 May 2016 16:02:09 -0400	[thread overview]
Message-ID: <1735441.Z8U2sxjTp5@x2> (raw)
In-Reply-To: <1090410784.877995.1462810399474.JavaMail.yahoo@mail.yahoo.com>

On Monday, May 09, 2016 04:13:19 PM varun gulati wrote:
> Hi Team,
> We have requirement where we have to monitor and log any read operations
> performed on a file. e.g. /a/b/c/xyz.log

-a always,exit -F path=/a/b/c/xyz.log -F perm=r -F key=log-access


> This file is usually copied and downloaded by many users using various
> operations, like, wget, ssh, jsp Download link provided. These commands are
> fired from different hosts. With the auditd we want to create a rule which
> auditctl can leverage to log the User ID that is reading (and copying) it
> from a different host may be.

You will get the local auid/uid that the kernel sees when the request triggers 
the rule. There is nothing more that can be done from the audit system.

-Steve


> I have gone through many of the rules but didn't find anything fruitful as
> such (which logs wget, scp commands from remote hosts). May be I am missing
> on something. Since it is a very crucial requirement, appreciate your
> guidance and directions with this. Let me know in case you require any
> further information from my end. Many thanks in advance.
> 
> 
> 
> Thanks and Regards,Varun Gulati

  reply	other threads:[~2016-05-09 20:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1090410784.877995.1462810399474.JavaMail.yahoo.ref@mail.yahoo.com>
2016-05-09 16:13 ` How to Audit ssh Commands --> wget, scp varun gulati
2016-05-09 20:02   ` Steve Grubb [this message]
2016-05-10 10:39     ` varun gulati
2016-05-10 12:56       ` Burn Alting
2016-05-10 13:46         ` varun gulati
2016-05-10 13:55           ` 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=1735441.Z8U2sxjTp5@x2 \
    --to=sgrubb@redhat.com \
    --cc=gitmevg@yahoo.co.in \
    --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;
as well as URLs for NNTP newsgroup(s).