Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Security-Basics
[Top] [All Lists]

Re: Scripts for OS security audit

Subject: Re: Scripts for OS security audit
Date: Fri, 27 Jul 2007 13:50:42 -0400
Noaman Khan wrote:
Hi all,

I need to do OS level security audit for Linux/Solaris servers. Below
are some of things i would like to check

- Operating system resources security
- Configuration settings security for OS
- Network services security such as ssh, snmp, ftp, nfs etc security
- User resources (home directories)
- whether logging is active such as failed logs etc
- password aging settings such as max age, min age
- password complexity
- password storage file security such as /etc/passwd and /etc/shadow

I know couple of tools such as tiger and some other shell scripts
which do part of what is required. Wondering if anyone know some
tool/script which do all of above.

Thanks in advance

Noaman


Noaman,

As I just went through this process with DISA (Defense Information Systems Agency), this is dependent on the version of the OS and what specific features you want implemented and to what level.

At work I use three different versions of Solaris and two different versions of Linux. This makes writing a generic script as best challenging since you have to address the change in functionality amongst versions of the same OS. For example if I want to shut off sendmail on Solaris 8 I would use a command that would rename the /etc/init.d/sendmail and /etc/rc2.d/S81sendmail scripts so that they would not be executed at boot time. In the case of Solaris 10 I would issue the svcadm command to disable sendmail.

While there are tools available such as the CIS Security Benchmarks (http://www.cisecurity.org/), I prefer to come up with my own script for securing Solaris, which is a work in progress.

Another thing you might want to consider is locking down the machines you build during the installation through scripts run as the OS is being installed (JumpStart and KickStart).


Robert Escue System Administrator

<Prev in Thread] Current Thread [Next in Thread>