From: Kohei KaiGai <kaigai@kaigai.gr.jp>
To: Linux-audit@redhat.com
Subject: How to track process invocation history using audit
Date: Mon, 20 Jun 2011 17:51:10 +0200 [thread overview]
Message-ID: <BANLkTikdGQZe_kYaRJs=PQZk9dTYnbFdMg@mail.gmail.com> (raw)
Hi,
I tried to track what process launches what other programs using audit
mechanism.
Then, I want to write up a tree diagram using audit logs eventually.
However, the auditctl does not work as I expected.
I tried to track all the fork(2) system call to record relationship
between ppid and pid
on processes with a particular loginuid.
[root@ls3029v0 ~]# auditctl -a task,always -F arch=b64 -S fork -F auid=1234
Error: syscall auditing being added to task list
But, it does not works.
I also tried to use 'exit' list, but it seems to me the following rule
is ignored.
(tail -f /var/log/audit/audit.log does not report anything)
[root@ls3029v0 ~]# auditctl -a exit,always -F arch=b64 -S fork
What is the best way to track process invocation history using audit mechanism?
Thanks,
--
KaiGai Kohei <kaigai@kaigai.gr.jp>
next reply other threads:[~2011-06-20 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 15:51 Kohei KaiGai [this message]
2011-06-20 16:04 ` How to track process invocation history using audit 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='BANLkTikdGQZe_kYaRJs=PQZk9dTYnbFdMg@mail.gmail.com' \
--to=kaigai@kaigai.gr.jp \
--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