Linux audit files to see who made changes to a file

=> auditctl - a command to assist controlling the kernel’s audit system. You can get status, and add or delete rules into kernel audit system. Setting a watch on a file is accomplished using this command:
Task: install audit package

# yum install audit
or
# up2date install auditor# up2date install audit# ntsysv
OR
# chkconfig auditd on
Now start service:
# /etc/init.d/auditd startOR# chkconfig auditd on
Now start service:
# /etc/init.d/auditd startNow start service:# /etc/init.d/auditd startHow do I set a watch on a file for auditing?# auditctl -w /etc/passwd -p war -k password-file

• -w /etc/passwd
 : Insert a watch for the file system object at given path i.e. watch file called /etc/passwd

• -p war
 : Set permissions filter for a file system watch. It can be r for read, w for write, x for execute, a for append.

• -k password-file
 : Set a filter key on a /etc/passwd file (watch). The password-file is a filterkey (string of text that can be up to 31 bytes long). It can uniquely identify the audit records produced by the watch. You need to use password-file string or phrase while searching audit logs.

$ grep 'something' /etc/passwd$ vi /etc/passwdFile System audit rules# auditctl -w /etc/shadow -k shadow-file -p rwxasyscall audit rule# auditctl -a exit,never -S mountFile system audit rule# auditctl -w /tmp -p e -k webserver-watch-tmpsyscall audit rule using pid# auditctl -a entry,always -S all -F pid=1005# ausearch -f /etc/passwd
OR
# ausearch -f /etc/passwd | less
OR
# ausearch -f /etc/passwd -i | less
Where,
OR# ausearch -f /etc/passwd | less
OR
# ausearch -f /etc/passwd -i | less
Where,
OR# ausearch -f /etc/passwd -i | less
Where,
Where,

• -f /etc/passwd
 : Only search for this file

• -i
 : Interpret numeric entities into text. For example, uid is converted to account name.

----
type=PATH msg=audit(03/16/2007 14:52:59.985:55) : name=/etc/passwd flags=follow,open inode=23087346 dev=08:02 mode=file,644 ouid=root ogid=root rdev=00:00
type=CWD msg=audit(03/16/2007 14:52:59.985:55) : cwd=/webroot/home/lighttpd
type=FS_INODE msg=audit(03/16/2007 14:52:59.985:55) : inode=23087346 inode_uid=root inode_gid=root inode_dev=08:02 inode_rdev=00:00
type=FS_WATCH msg=audit(03/16/2007 14:52:59.985:55) : watch_inode=23087346 watch=passwd filterkey=password-file perm=read,write,append perm_mask=read
type=SYSCALL msg=audit(03/16/2007 14:52:59.985:55) : arch=x86_64 syscall=open success=yes exit=3 a0=7fbffffcb4 a1=0 a2=2 a3=6171d0 items=1 pid=12551 auid=unknown(4294967295) uid=lighttpd gid=lighttpd euid=lighttpd suid=lighttpd fsuid=lighttpd egid=lighttpd sgid=lighttpd fsgid=lighttpd comm=grep exe=/bin/grep

• audit(03/16/2007 14:52:59.985:55)
 : Audit log time

• uid=lighttpd gid=lighttpd
 : User ids in numerical format. By passing -i option to command you can convert most of numeric data to human readable format. In our example user is lighttpd used grep command to open a file

• exe="/bin/grep"
 : Command grep used to access /etc/passwd file

• perm_mask=read : File was open for read operation

Other useful examples# ausearch -ts today -k password-file# ausearch -ts 3/12/07 -k password-file# ausearch -ts today -k password-file -x rm# ausearch -ts 3/12/07 -k password-file -x rmSearch for an event with the given user name (UID). For example find out if user vivek (uid 506) try to open /etc/passwd:# ausearch -ts today -k password-file -x rm -ui 506# ausearch -k password-file -ui 506

How do I audit file events such as read / write etc? How can I use audit to see who changed a file in Linux?

The answer is to use 2.6 kernel’s audit system. Modern Linux kernel (2.6.x) comes with auditd daemon. It’s responsible for writing audit records to the disk. During startup, the rules in /etc/audit.rules are read by this daemon. You can open /etc/audit.rules file and make changes such as setup audit file log location and other option. The default file is good enough to get started with auditd.

In order to use audit facility you need to use following utilities

=> ausearch - a command that can query the audit daemon logs based for events based on different search criteria.

=> aureport - a tool that produces summary reports of the audit system logs.

Note that following all instructions are tested on CentOS 4.x and Fedora Core and RHEL 4/5 Linux.

The audit package contains the user space utilities for storing and searching the audit records generate by the audit subsystem in the Linux 2.6 kernel. CentOS/Red Hat and Fedora core includes audit rpm package. Use yum or up2date command to install package

Auto start auditd service on boot

Let us say you would like to audit a /etc/passwd file. You need to type command as follows:

Where,

In short you are monitoring (read as watching) a /etc/passwd file for anyone (including syscall) that may perform a write, append or read operation on a file.

Wait for some time or as a normal user run command as follows:

Following are more examples:

Add a watch on "/etc/shadow" with the arbitrary filterkey "shadow-file" that generates records for "reads, writes, executes, and appends" on "shadow"

The next rule suppresses auditing for mount syscall exits

Add a watch "tmp" with a NULL filterkey that generates records "executes" on "/tmp" (good for a webserver)

To see all syscalls made by a program called sshd (pid - 1005):

How do I find out who changed or accessed a file /etc/passwd?

Use ausearch command as follows:

Output:

Let us try to understand output

So from log files you can clearly see who read file using grep or made changes to a file using vi/vim text editor. Log provides tons of other information. You need to read man pages and documentation to understand raw log format.

Search for events with date and time stamps. if the date is omitted, today is assumed. If the time is omitted, now is assumed. Use 24 hour clock time rather than AM or PM to specify time. An example date is 10/24/05. An example of time is 18:00:00.

Search for an event matching the given executable name using -x option. For example find out who has accessed /etc/passwd using rm command: