From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Audit log decode
Date: Tue, 11 Sep 2018 08:21:44 -0400 [thread overview]
Message-ID: <8355452.a5mgvV1NuZ@x2> (raw)
In-Reply-To: <AA0F5F9A-E607-44F5-A40A-5DA0FA9926E5@gmail.com>
On Tuesday, September 11, 2018 8:14:05 AM EDT khalid fahad wrote:
> Hi,
> I need help to decode the following records in audit.log. Thanks
> type=PROCTITLE msg=audit(100000000.000:000):
> proctitle=726D002F7661722F6C6F672F736563757265 type=PATH
> msg=audit(100000000.000:000): item=1 name="/var/log/secure" inode=34679270
> dev=fd:00 mode=0100600 ouid=0 ogid=0 rdev=00:00
> obj=system_u:object_r:var_log_t:s0 objtype=DELETE type=PATH
> msg=audit(100000000.000:000): item=0 name="/var/log/" inode=33586091
> dev=fd:00 mode=040755 ouid=0 ogid=0 rdev=00:00
> obj=system_u:object_r:var_log_t:s0 objtype=PARENT type=CWD
> msg=audit(100000000.000:000): cwd="/home/adminuser"
> type=SYSCALL msg=audit(100000000.000:000): arch=c000003e syscall=263
> success=no exit=-13 a0=ffffffffffffff9c a1=b830c0 a2=0 a3=7ffc9bd9d600
> items=2 ppid=3493 pid=35055 auid=1000 uid=1000 gid=1000 euid=1000
> suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 tty=pts2 ses=1
> comm="rm" exe="/usr/bin/rm"
> subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
> key="secure_log"
The ausearch program is able to decode this and is meant to display the audit
loags. If you have that in a file named log, you can just do something like
ausearch -if log -i
and that should decode your event.
-Steve
next prev parent reply other threads:[~2018-09-11 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 12:14 Audit log decode khalid fahad
2018-09-11 12:19 ` Osama Elnaggar
2018-09-11 12:21 ` Steve Grubb [this message]
2018-09-11 14:05 ` khalid fahad
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=8355452.a5mgvV1NuZ@x2 \
--to=sgrubb@redhat.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