09-20-2012
To have a number of employees working in root permission is always really bad.
Tune your employees' permissions to let them do what they have to do without becoming
root.
I think you should use the HP-UX Auditing System for monitoring:
audit(5)
Since I don't know anything about HP-UX, I stop here.
--
Bye
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Team ,
using fc command we can get details of our history file .. Is it possible to get the same result for different user from root.. Actually I need to collect all the stuff from select users history file for day to day basis.
thanks in advance .. (2 Replies)
Discussion started by: rgpai9972
2 Replies
2. Shell Programming and Scripting
Hi,
I need to access a user's command history. However, the dilemma is that he is logged in and so his current history is not yet flushed to .bash_history file which gets flushed when he logs out. Is there a way I can still access his most recent history?
thank you,
S (4 Replies)
Discussion started by: sardare
4 Replies
3. UNIX for Dummies Questions & Answers
Hello every body,
Kindly inform me How Do i find out the time I executed a command previously on UNIX Solaris??
To be more specific and more clear about what i want to know is that I want a command the enables me to know the history and which command i run at this history/time.
FYI I used... (5 Replies)
Discussion started by: ahmedamer12
5 Replies
4. UNIX for Advanced & Expert Users
Hi all,
My need is :
1. To know who , when , which command used.
2. Local user should not delete this information.
I mean , with an example , i can say
i have a user user1
i need to give all the following permissions to user1, :
a. A specific directory other than his home... (3 Replies)
Discussion started by: linuxadmin
3 Replies
5. Shell Programming and Scripting
Hey guyz,
I'm trying to get the command history for my active users sessions on the local machine and i kinda hit a tough wall
Is command-line history for my current user saved somewhere else besides $HOME/.bash_history?
I have been told that there is some temporary file stored on the local... (2 Replies)
Discussion started by: mishu_cgm
2 Replies
6. Red Hat
Hi,
I have three servers,For 3 servers how i can take output,all the local accounts and details of whether the access is Root or User access.
cheers (1 Reply)
Discussion started by: ranjithm
1 Replies
7. Shell Programming and Scripting
HTML Code
archive_history() { HISTORYOLD=${HISTFILE}.archive CURTIME=`date` CURTTY=`tty` IP=$(echo $SSH_CLIENT | awk '{print $1}') if ; then echo "#-${HOSTNAME}-- ${CURBASHDATE} - ${CURTIME} ($CURTTY) ${USER} ${IP}----" >> $HISTORYOLD history... (2 Replies)
Discussion started by: rehantayyab82
2 Replies
8. Shell Programming and Scripting
HTML Code:
archive_history() { HISTORYOLD=${HISTFILE}.archive CURTIME=`date` CURTTY=`tty` IP=$(echo $SSH_CLIENT | awk '{print $1}') if ; then echo "#-${HOSTNAME}-- ${CURBASHDATE} - ${CURTIME} ($CURTTY) ${USER} ${IP}----" >> $HISTORYOLD history... (0 Replies)
Discussion started by: rehantayyab82
0 Replies
9. Shell Programming and Scripting
I'm exploring OpenBSD and want to stick to its default shell, which is ksh. My goal is for my regular user ("bruno") and root user to have a shared history file. However, it seems that when running as root, ksh refuses to write to a HISTFILE that is owned by non-root user. This illustrates the... (3 Replies)
Discussion started by: DevuanFan
3 Replies
10. What is on Your Mind?
I am pleased to announce this new video in 1080 HD for UNIX lovers honoring thirty years of UNIX history spanning from 1969 to 1999 presented in 150 seconds (two and a half minutes) in 1080 HD, celebrating the 50th anniversary of UNIX.
The Great History of UNIX (1969-1999) | 30 Years of UNIX... (8 Replies)
Discussion started by: Neo
8 Replies
LEARN ABOUT DEBIAN
auditd
AUDITD(8) System Administration Utilities AUDITD(8)
NAME
auditd - The Linux Audit daemon
SYNOPSIS
auditd [-f] [-l] [-n] [-s disable|enable|nochange]
DESCRIPTION
auditd is the userspace component to the Linux Auditing System. It's responsible for writing audit records to the disk. Viewing the logs is
done with the ausearch or aureport utilities. Configuring the audit rules is done with the auditctl utility. During startup, the rules in
/etc/audit/audit.rules are read by auditctl. The audit daemon itself has some configuration options that the admin may wish to customize.
They are found in the auditd.conf file.
OPTIONS
-f leave the audit daemon in the foreground for debugging. Messages also go to stderr rather than the audit log.
-l allow the audit daemon to follow symlinks for config files.
-n no fork. This is useful for running off of inittab
-s=ENABLE_STATE
specify when starting if auditd should change the current value for the kernel enabled flag. Valid values for ENABLE_STATE are "dis-
able", "enable" or "nochange". The default is to enable (and disable when auditd terminates). The value of the enabled flag may be
changed during the lifetime of auditd using 'auditctl -e'.
SIGNALS
SIGHUP causes auditd to reconfigure. This means that auditd re-reads the configuration file. If there are no syntax errors, it will proceed
to implement the requested changes. If the reconfigure is successful, a DAEMON_CONFIG event is recorded in the logs. If not success-
ful, error handling is controlled by space_left_action, admin_space_left_action, disk_full_action, and disk_error_action parameters
in auditd.conf.
SIGTERM
caused auditd to discontinue processing audit events, write a shutdown audit event, and exit.
SIGUSR1
causes auditd to immediately rotate the logs. It will consult the max_log_size_action to see if it should keep the logs or not.
SIGUSR2
causes auditd to attemp to resume logging. This is usually used after logging has been suspended.
FILES
/etc/audit/auditd.conf - configuration file for audit daemon
/etc/audit/audit.rules - audit rules to be loaded at startup
NOTES
A boot param of audit=1 should be added to ensure that all processes that run before the audit daemon starts is marked as auditable by the
kernel. Not doing that will make a few processes impossible to properly audit.
The audit daemon can receive audit events from other audit daemons via the audisp-remote audispd plugin. The audit daemon may be linked
with tcp_wrappers to control which machines can connect. If this is the case, you can add an entry to hosts.allow and deny.
SEE ALSO
auditd.conf(5), audispd(8), ausearch(8), aureport(8), auditctl(8), audit.rules(7).
AUTHOR
Steve Grubb
Red Hat Sept 2007 AUDITD(8)