10-13-2009
Audit in Solaris Servers.
Hi Friends
I am a Solaries newbie and I am looking out for a software or command or config that can capture all commands run by all users on a server on a daily basis. I believe that this Audit is being done in almost all enterprises and would like to know how the same is done there.
Any inputs,links,suggestions are highly appreciated.
Note 1-Currently i have written a shell script that copies the .sh_history and .bash_history file of all users who have logged into the server on a day. But it doesn't have the time stamp and looks an awkward way to get the audit done.
Note 2- My solaris only farm has around 30 Sol9 & 10 machines.
Thanks-in-advance,
HG
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
Anyone know how to turn on Solaris 8 audt trial
Thank (2 Replies)
Discussion started by: civic2005
2 Replies
2. Solaris
Is there a command to find out all the commands ran by a certain user id?
TiA (5 Replies)
Discussion started by: PapaPark
5 Replies
3. Solaris
How do I know that audit is enabled in soalris. in AIX 'audit query' command gives me the info whether auditing is on or not.
Raghav (1 Reply)
Discussion started by: raghavender_sri
1 Replies
4. Solaris
can you please share what you use to audit what files are deleted, when files are deleted and who deleted them?
thx (1 Reply)
Discussion started by: melanie_pfefer
1 Replies
5. Solaris
Hello
We have recently been through an audit of our solaris servers.
All our solaris servers are running version 10.
We have been told to close down all the services and we have closed what we could by using svcadm disable
We only wish to let ssh and the ftp service to run.
Below is a... (3 Replies)
Discussion started by: sollyshah
3 Replies
6. Solaris
Dear All,
I have one of my Servers, running Solaris 9. I wanna enable the Audit log enabling, the way I did in Solaris 10 Servers.
After running, the bsmconv script, giving the reboots, modifying all the audit files in /etc/security, the audit is enabled, but the audit file which shall be... (3 Replies)
Discussion started by: sumeet1806
3 Replies
7. Solaris
Does anyone know if there is software written to view the audit logs generated by Solaris? I am referring the the logs created by auditd. It produces an unreadable log. I am familiar with auditreduce and praudit, but I am looking for something that produces a report, much like logwatch looks at the... (4 Replies)
Discussion started by: brownwrap
4 Replies
8. Solaris
Hello,
I've installed solaris audit on a Solaris 10 SPARC system.
Latest patch 143962-04 is installed.
My problem is that while I can catch all arguments and processes created, I cannot catch a redirection. ie
cat /tmp/test.txt > /tmp/test2.txtCatches the first part but not the redirection.... (5 Replies)
Discussion started by: gowron
5 Replies
9. Solaris
Linux audits in syslog, any time a user is deleted or added. However, I'm running a Solaris11 VM, and find no such entries. How can I enable auditing for useradd and userdel? Oracle's documentation on managing the auditing service, has been of no assistance. Thanks.
Customizing What Is... (7 Replies)
Discussion started by: Nvizn
7 Replies
10. Solaris
hi,
I enabled bsm modules (/etc/security/bsmconv) and rebooted Solaris 10. But service is going into maintenance state. I rebooted server and I see one error saying "sys/c2audit:audit_kssl() not defined properly". I am not sure, what it is indicating and how it should be fixed. Please suggest, how... (5 Replies)
Discussion started by: solaris_1977
5 Replies
auditd(1m) auditd(1m)
NAME
auditd - Starts the DCE Audit Daemon.
SYNOPSIS
auditd [-t trail_file] [-a] [-s size] [-wrap] [-w svc_route] [-d debug_level]
OPTIONS
Specifies the pathname of the audit trail file used by the Audit daemon. The default path of the audit trail file is dcelo-
cal/var/aud/adm/central_trail. If an audit trail file name (instead of an absolute pathname) is specified, the file will be created in the
dcelocal/var/aud/adm/ directory. Audits the Audit daemon's control interface access. Sets a warning threshold on the size of the audit
trail file. The Audit daemon displays a warning message each time an audit record is appended to the audit trail after the threshold has
been reached. Wraps the recording of audit events to the beginning of the audit trail file when its size limit is reached. The default
action when the size limit has been reached is to stop auditing. Specifies where each level of serviceability messages are routed. The
svc_route argument is divided into three fields, separated by colons - the level, a routing identifier, and a routing parameter:
severity:how:where
See svcroute(5) for possible values for these fields. Specifies debugging level of sub-components. The debug_level argument contains four
fields separated by a colon:
component:flags:how:where
See svcroute(5) for possible values of these fields.
DESCRIPTION
The auditd command starts the Audit daemon. The Audit daemon must be run on the host before the audit clients.
The Audit daemon can only service audit clients that are on the host where it is running. Thus, an Audit daemon must be installed and run
on every host in the cell that has audit clients (audit clients include DCE servers and user-written application servers).
The Audit daemon has two functions. It maintains the filter files which are shared by all audit clients running on the host. It also pro-
vides an audit record logging service to these clients.
The Audit daemon runs under the local host's machine principal identity (host/hostname/self).
A DCE Host daemon (dced) must be running on the local host when auditd is started. Typically, dced and auditd are started at boot time.
The auditd process places itself in the background and sends messages indicating it is ready to service requests for updating or querying
filters and logging audit records.
Privileges Required
You must be logged into a privileged account (cell_admin or a member of the audit-admin group) to be able to run auditd.
EXAMPLES
The following example starts the Audit daemon using the default audit trail file (dcelocal/var/aud/adm/central_trail): $ auditd
The following example starts the Audit daemon and specifies my_trail_file as the audit trail file. $auditd -t my_trail_file
The following example starts the Audit daemon and specifies where each level of serviceability messages is going to be routed. $ auditd -w
FATAL:FILE:/dev/console -w NOTICE:FILE:/opt/dcelocal/var/audit/adm/svc_log
The following example starts the Audit daemon and specifies the debugging level. $ auditd -d 1,esl.9
RELATED INFORMATION
aud(1m), audevents(1m), audfilter(1m), audtrail(1m), dcecp(1m).
auditd(1m)