linux-audit.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: Rohit <cola.vn@gmail.com>
Cc: linux-audit@redhat.com
Subject: Re: Mapping of Audit rule to Record Type Generated + chmod log query
Date: Tue, 11 Jan 2022 10:42:54 -0500	[thread overview]
Message-ID: <5533133.DvuYhMxLoT@x2> (raw)
In-Reply-To: <CAHvE9BJp4M3XVSFTrXdu79bizRiiO9fumWX-uE5aC2Om=9djOA@mail.gmail.com>

On Tuesday, January 11, 2022 1:37:18 AM EST Rohit wrote:
> Hello Steve,
> 
> Thank you, that's very helpful.
> 
> > The compound events always have a syscall event, but as to the auxiliary
> 
> records,
> it really depends on the path the syscall takes through the kernel. Various
> places are hooked and collect information
> Would you have any reference links that would help me understand where
> these hooks that collect information are placed?

They start somewhere in this general area:
https://elixir.bootlin.com/linux/latest/source/include/linux/audit.h#L330

There are many hooks. The auxiliary record types are in the 1300 block:
https://elixir.bootlin.com/linux/latest/source/include/uapi/linux/audit.h#L89

The one exception is AUDIT_REPLACE which was mistakenly placed in this block. 
It should have been in the 1000 block.

-Steve


--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit


      reply	other threads:[~2022-01-11 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 20:32 Mapping of Audit rule to Record Type Generated + chmod log query Rohit
2022-01-10 21:17 ` Steve Grubb
2022-01-11  6:37   ` Rohit
2022-01-11 15:42     ` 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=5533133.DvuYhMxLoT@x2 \
    --to=sgrubb@redhat.com \
    --cc=cola.vn@gmail.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;
as well as URLs for NNTP newsgroup(s).