Sponsored Content
Full Discussion: Unix Security and auditing
Special Forums Cybersecurity Unix Security and auditing Post 16532 by GW01 on Monday 4th of March 2002 03:46:16 AM
Old 03-04-2002
Unix Security and auditing

I am starting an audit of unix security within our company and am looking for any information that may assist me with this. I am looking for any tips or pointers that I should be aware of when looking at unix. I am very new to unix so any help will do. Maybe there is someone out the that has had some audit experience on unix. Thanks.
 

8 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

Basic Unix Security

Has anyone got any info on Unix security - I'm after the very basics as I'm a complete beginner (OS level) Thanks Dutt'O (2 Replies)
Discussion started by: DuttO
2 Replies

2. UNIX Desktop Questions & Answers

Unix Security

Sorry, Unix file security Thanks (1 Reply)
Discussion started by: DuttO
1 Replies

3. HP-UX

unix security

Was wondering if anyone could answer two quick questions... 1) What is the best way to impliment password triviality checking and also checking to make sure a user does not use the same password twice. 2) is there any nice software out there to manage users on multiple machine as far as security... (6 Replies)
Discussion started by: breigner
6 Replies

4. Cybersecurity

Unix Security Alerts

Hi everyone, Does anyone use a good unix security alert provider (such as CERT/SANS) that caters specifically to Unix and would provide a similar method of alert reporting? Any suggestions (with links!! :) ) would be helpful and appreciated. Thanks in advance :p (4 Replies)
Discussion started by: cbalemba
4 Replies

5. Cybersecurity

Unix Security

this is a pretty good article that is a little dated, but still very informative at freeos.com. since this is Network Security for Dummies Q&A, maybe this should be the first step for unix.com users to check for general and more specific info on how to 'harden' their linux box. some of this... (8 Replies)
Discussion started by: norsk hedensk
8 Replies

6. UNIX for Advanced & Expert Users

Unix Auditing.

I need to log or 'audit' any access to a shared directory which is stored on a NetApp appliance. I need to be able to 'prove' who has acessed the data in this directory at any time. I am just not sure how to do this. The systems that will be accessing this are Linux systems. Any help is... (2 Replies)
Discussion started by: frankkahle
2 Replies

7. HP-UX

Unix security

Is there anyway to trace where a user has logged in from. Someone this morning deleted some data but I only have the following info from the last command cromread pts/ta Wed Jul 22 06:55 - 06:57 (00:02) cromread pts/ta Wed Jul 22 06:43 - 06:46 (00:02) cromread pts/ta ... (3 Replies)
Discussion started by: spiers
3 Replies

8. Solaris

Unix file, folder permissions, security auditing tools.

I want to periodically check if ASCII password/config files on Unix have 400 or 600 access. Folders and files are owned by designated group and user. Folders and Files do not have world write access. Are there any tools/scripts available for this kind of auditing that I can use on Solaris? (7 Replies)
Discussion started by: kchinnam
7 Replies
audit(1M)                                                                                                                                audit(1M)

NAME
audit - control the behavior of the audit daemon SYNOPSIS
audit -n | -s | -t | -v [path] The audit command is the system administrator's interface to maintaining the audit trail. The audit daemon can be notified to read the con- tents of the audit_control(4) file and re-initialize the current audit directory to the first directory listed in the audit_control file or to open a new audit file in the current audit directory specified in the audit_control file, as last read by the audit daemon. Reading audit_control also causes the minfree and plugin configuration lines to be re-read and reset within auditd. The audit daemon can also be signaled to close the audit trail and disable auditing. -n Notify the audit daemon to close the current audit file and open a new audit file in the current audit directory. -s Notify the audit daemon to read the audit control file. The audit daemon stores the information internally. If the audit daemon is not running but audit has been enabled by means of bsmconv(1M), the audit daemon is started. -t Direct the audit daemon to close the current audit trail file, disable auditing, and die. Use -s to restart auditing. -v path Verify the syntax for the audit control file stored in path. The audit command displays an approval message or outputs specific error messages for each error found. The audit command will exit with 0 upon success and a positive integer upon failure. /etc/security/audit_user /etc/security/audit_control See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Stability |Evolving | +-----------------------------+-----------------------------+ bsmconv(1M), praudit(1M), audit(2), audit_control(4), audit_user(4), attributes(5) The functionality described in this man page is available only if the Basic Security Module (BSM) has been enabled. See bsmconv(1M) for more information. The audit command does not modify a process's preselection mask. It functions are limited to the following: o affects which audit directories are used for audit data storage; o specifies the minimum free space setting; o resets the parameters supplied by means of the plugin directive. For the -s option, audit validates the audit_control syntax and displays an error message if a syntax error is found. If a syntax error message is displayed, the audit daemon does not re-read audit_control. Because audit_control is processed at boot time, the -v option is provided to allow syntax checking of an edited copy of audit_control. Using -v, audit exits with 0 if the syntax is correct; otherwise, it returns a positive integer. The -v option can be used in any zone, but the -t, -s, and -n options are valid only in local zones and, then, only if the perzone audit policy is set. See auditd(1M) and auditconfig(1M) for per-zone audit configuration. 25 May 2004 audit(1M)
All times are GMT -4. The time now is 08:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy