Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Sarthak Jain <Sarthak.Jain@microfocus.com>
Subject: Re: Regarding Auditing on RHEL 7.1
Date: Thu, 25 Feb 2016 14:52:09 -0500	[thread overview]
Message-ID: <2113594.6K0R9tGoXX@x2> (raw)
In-Reply-To: <5078D98067B1B340BEE9F4F5FF71B8A733E824@BLRXMB02.microfocus.com>

On Wednesday, February 24, 2016 07:04:08 AM Sarthak Jain wrote:
> I am Sarthak Jain working in MicroFocus. I want your small help to clarify
> one of my doubt regarding the kernel auditing on RHEL 7.1. I hope you are
> the right person to contact. It will just 2 min (max :P) to go through the
> problem.
> 
> Assumption: Ideally, if we change the configuration file (for ex-
> /etc/hosts), we should be getting audit events for it.
> 
> Scenario: By default, the permissions for '/etc/hosts' is (rw-r-r--). If we
> modify this file, then audit events are coming as attached in file -
> 'file1.txt'.
> 
> Problem: Let say if we change the permissions of the '/etc/hosts' to
> (rw-rw-rw), then audit system is not recording the "CONFIG_CHANGE" event at
> all.

That is because the audit configuration has not changed. Config change events 
are specific to changes in the audit system itself. What you get on this is 
syscall event with a path

If you want to get events on changing permissions on a file, then you would put 
a rule like this:

-a always,exit -F path=/etc/hosts -F perms=a -F key=permission-change

After modifying the file with chmod, then run:

ausearch --start today -k permission-change


> I have attached the file - 'file2.txt' for your reference. Can you
> please clarify this ? Is it a kernel level bug?

No. Its doing what it should.

-Steve

  reply	other threads:[~2016-02-25 19:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24  7:04 Regarding Auditing on RHEL 7.1 Sarthak Jain
2016-02-25 19:52 ` Steve Grubb [this message]
2016-02-26  6:28   ` Sarthak Jain

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=2113594.6K0R9tGoXX@x2 \
    --to=sgrubb@redhat.com \
    --cc=Sarthak.Jain@microfocus.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