Unix/Linux Go Back    

Security Discuss UNIX and Linux computer and network security, cyber security, cyber attacks, IT security, and more.

Log Review- SU


Thread Tools Search this Thread Display Modes
Old Unix and Linux 09-17-2015   -   Original Discussion by Tilus
Tilus's Unix or Linux Image
Tilus Tilus is offline
Registered User
Join Date: Sep 2015
Last Activity: 18 September 2015, 10:04 AM EDT
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Log Review- SU


Can some please provide some hints on what to look for in unix/Linux logs such as sulog from a Information security perspective.

Sponsored Links
Old Unix and Linux 09-17-2015   -   Original Discussion by Tilus
zaxxon's Unix or Linux Image
zaxxon zaxxon is offline Forum Staff  
code tag tagger
Join Date: Sep 2007
Last Activity: 13 April 2018, 5:31 AM EDT
Location: St. Gallen, Switzerland
Posts: 6,574
Thanks: 178
Thanked 568 Times in 482 Posts
Repetitive failed tries could be a hint for some unusual behaviour.

Else you might go look up this log when something bad has happened already to get a clue afterwards who might have been it.

If this is not enough and you are looking for some more information, which commands have been issued by whom etc., you might want to have a look at an auditing suite.
Maybe auditd is available for your Linux distribution.
Sponsored Links
Old Unix and Linux 09-22-2015   -   Original Discussion by Tilus
rbatte1's Unix or Linux Image
rbatte1 rbatte1 is online now Forum Staff  
Root armed
Join Date: Jun 2007
Last Activity: 20 April 2018, 11:00 AM EDT
Location: Lancashire, UK
Posts: 3,510
Thanks: 1,544
Thanked 689 Times in 619 Posts
Our policy is that every use of su or sudo has to be explained. Just collecting the records and challenging is a good start, however I added something in to /etc/profile that tries to log all the commands too. There are certainly some flaws with it and it depends on people doing su - or su - username to run the profile and therefore be effective, but that has always been the habit here, so I got away with that.

There were various other application specific things embedded in the code but having stripped that out, I think this might still work:-

function lgcmd
 cur_cmd_seq=`fc -l -0 | cut -f1`
 if [ "$cur_cmd_seq" != "$prev_cmd_seq" ]
    /usr/bin/logger "on $PTS as `id -un`: `fc -l -0 | cut -f2-`"

prev_cmd_seq=                  # Set as null in case shell refuses unset variables
trap lgcmd DEBUG

You would need to determine the pseudo-terminal as $PTS but the rest gives you a fairly good trace to challenge people with.

I hope that this helps,
Sponsored Links

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Linux More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
Please, review script. algernonz Shell Programming and Scripting 1 11-09-2008 08:01 PM

All times are GMT -4. The time now is 11:03 AM.