AuditPro v4.0.0

©Network Intelligence India

http://www.niiconsulting.com
Date: 23/1/2008
Time: 11:12:9
System: linux
Hostname: 192.168.0.120

  Legend  
 
 Symbol  Description
   This represents the highest possible risk level. Such a vulnerability will in all likelihood allow an attacker partial or complete access to the system. These vulnerabilities must be  addressed immediately by either patching the system, or changing the configuration.
   This represents a medium risk vulnerability. Such a vulnerability would typically allow an attacker a limited level of access to the system, but this would not usually be a super  user or administrative level of access. These vulnerabilities must be addressed in the short term.
   This represents a low vulnerability. It may not necessarily result in a system compromise by itself. But in conjunction with other medium or high risk vulnerabilities it may allow  an attacker considerable access to the system. Such vulnerabilities must be addressed in the short to medium term.
   This sign represents adherence to the security policy. Usually, this is the case if no violations have been found.
  This represents a finding for which no policy match could be found, or it is purely for information purposes. It does not represent a vulnerability. Normally, no action needs to  be taken in such cases
WVS The Weighted Vulnerability Score (WVS) is calculated using the formula: (Low x 1) + (Medium x 2) + (High x 3)
 
     

Table of Contents


General Information

     1. Operating system information
     2. Drive information
     3. CPU information

Network Security

     4. Open ports
     5. Services
     6. Network card configuration
     7. Routing table
     8. Banners
     9. FTP users
     10. Xinetd checks
     11. .rhosts files

Users and Groups

     12. Generic accounts
     13. Members of wheel group
     14. System users having false shell
     15. System users are locked out
     16. Dangerous accounts
     17. User ID 0
     18. Users without password
     19. Password expiry

System Environment

     20. Uptime
     21. Last reboots
     22. Currently logged on users
     23. Remote root logins
     24. Allowed terminals for root login
     25. Memory status
     26. Current processes
     27. Single user boot protection
     28. PATH environment variable check
     29. Root shell IFS

Filesystem Security

     30. Mounted partitions
     31. Disk usage
     32. Rootkit detection

Log Analysis

     33. Failed logins
     34. Critical system errors

Patch Checking

     35. Apache web server
     36. Squid proxy server
     37. OpenSSH daemon
     38. Kerberos v5 server
     39. Samba daemon
     40. Sendmail daemon
     41. MySQL
     42. proftpd
     43. vsftpd
     44. wu-ftpd


Percentage severity distribution


Weighted score for each probe


  General Information  

  Check : Operating system information  
 

Description:
This is the uname information from the system, identifying the operating system, kernel version, processor type and other related information


CVE Reference No.:


Severity Kernel Name  Kernel Version  Processor Type  Hardware Platform  Operating System 
   Linux  2.6.18-8.el5  i686  i386  GNU/Linux



Solution:
This probe is purely for informational purposes, and no action is required.

 
     

  Check : Drive information  
 

Description:
This probe identifies the partitions, drive capacity and other related information.


CVE Reference No.:


Severity Drive information 
   Disk /dev/hda: 8589 MB, 8589934592 bytes
   255 heads, 63 sectors/track, 1044 cylinders
   Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
   /dev/hda1 * 1 12 96358+ 83 Linux
   /dev/hda2 13 979 7767427+ 83 Linux
   /dev/hda3 980 1044 522112+ 82 Linux swap / Solaris



Solution:
This probe is purely for informational purposes, and no action is required.

 
     

  Check : CPU information  
 

Description:
This probe displays information about the CPU, such as its speed, vendor, cache size, etc.


CVE Reference No.:


Severity Attribute  Value 
   processor   0
   vendor_id   GenuineIntel
   cpu family   15
   model   3
   model name   Intel(R) Pentium(R) 4 CPU 2.80GHz
   stepping   8
   cpu MHz   2800.355
   cache size   1024 KB
   wp   yes



Solution:
This probe is purely for informational purposes, and no action is required.

 
     

  Network Security  

  Check : Open ports  
 

Description:
This is the list of open ports along with the banners grabbed from the open ports. Any ports that are present in the disallowed list, and are found to be open are marked as high severity violations. Any ports that are in the allowed list and are found to be open are marked as compliance entries. The default disallowed list contains known Trojan and virus ports. The port scan also maps the open ports to known services. A port scan is typically the first stage in the security assessment exercise, and the output will help you determine the network exposure of your system.


CVE Reference No.: CVE-NO-MATCH


Severity Port  State  Process 
 2208  LISTEN  hpiod
 3306  LISTEN  mysqld
 111  LISTEN  portmap
 631  LISTEN  cupsd
 25  LISTEN  sendmail:
 2207  LISTEN  python
 991  LISTEN  rpc.statd
 N/A  LISTEN  sshd



Solution:
Make sure that only trusted services are keeping ports open. For instance, HTTP ports 80 or 443 should not be found open on a workstation. Ensure that there is a functional justification for keeping the ports open. If you wish to investigate a port, the first step would be to issue a 'netstat -antp' command on the target system, and determine ports that are in 'LISTENING' mode. This will also show the service that is keeping the particular port open. Make sure only known and fully patched services are responsible for the open ports. Also make sure that the services do not reveal the type and version of the software in the banner.

 
     

  Check : Services  
 

Description:
This probe lists out those services that are started through the /etc/rcx.d scripts at various Unix run-levels. Some of these services, such as 'sendmail' may not be required. You can decided which services should be disabled, and which should be enabled with the policy. Simply enter the name of the service as it shows up in the output of the 'chkconfig' command. Violations and compliance with the policy are shown in the report.


CVE Reference No.: CVE-NO-MATCH


Severity Service  RunLevel 0  RunLevel 1  RunLevel 2  RunLevel 3  RunLevel 4  RunLevel 5  RunLevel 6 



Solution:
Ensure that all the services that are started during system boot are absolutely necessary. Disable unnecessary services by issuing the following command (for Linux):
chkconfig --levels 123456 <service_name> off. Alternatively, you could locate the script that starts this service in /etc/rc{1,2,3,4,5,6}.d directories. Change the name of the script so that it starts with a letter other than an 'S' or a 'K'. Files beginning with S are those that will be executed during system startup and those beginning with a K will be executed during system shutdown.

 
     

  Check : Network card configuration  
 

Description:
This probe determines the network interfaces connected to the machine. The output gives details of the interface name, IP address, MAC address, subnet mask, broadcast address, MTU and other network parameters associated with all the network devices attached to the server. Ensure that no interfaces are in promiscuous mode.


CVE Reference No.:


Severity Name  Options  Type  IP/CIDR  Broadcast Address 
 lo  LOOPBACK,UP,LOWER_UP  loopback  127.0.0.1/8  00:00:00:00:00:00
 eth0  BROADCAST,MULTICAST,UP,LOWER_UP  ether  192.168.0.120/24  192.168.0.255
 sit0  NOARP  sit  N/A  0.0.0.0



Solution:
Ensure that only the necessary network interface cards are configured and enabled on the system, and that none of them is in Promiscuous mode, unless this is an IDS sensor.

 
     

  Check : Routing table  
 

Description:
Ensure that there are no unnecessary routes to other networks as this increases the exposure of this system to other users. Unnecessary routing entries also provide additional information to an attacker if the system has been compromised as this system can then be used to compromise other systems. The default gateway should also be checked to see if it's the legitimate gateway and that it has not been modified to some other host, which might be a compromised host on the Internet or network.


CVE Reference No.:


Severity Destination  Gateway  Netmask  Interface 
   192.168.0.0  *  255.255.255.0  eth0
   169.254.0.0  *  255.255.0.0  eth0
   default  192.168.0.100  0.0.0.0  eth0



Solution:
Ensure that the information is consistent with your network architecture, and contains the minimum possible information.

 
     

  Check : Banners  
 

Description:
This probe checks if a login banner with the appropriate content exists in the file /etc/issue. This file does not exist by default.


CVE Reference No.:


Severity General Banner 
 Red Hat Enterprise Linux Server release 5 (Tikanga)
Kernel /r on an /m



Solution:
Recommend that this file be created with a message giving the name of the organization, and warning that all access is monitored and any unauthorized access will be punishable as per the Company's Security Policy, as well as the law of the land pertaining to information systems. Ensure that the warning banner contains the following points:
1. The system is property of your organization.
2. The system is subject to monitoring.
3. Monitoring is authorized in accordance with applicable laws and regulations and conducted for purposes of systems management and protection, protection against improper or unauthorized use or access, and verification of applicable security features or procedures.
4. Use of the system constitutes consent to monitoring.
5. Unauthorized use of this computer may subject the user to criminal prosecution and penalties.

 
     

  Check : FTP users  
 

Description:
If FTP is enabled, then the /etc/ftpusers file can be used to ensure that users listed in this file are NOT allowed to connect via FTP. This check determines that all the system users and privileged user accounts such as 'root' are entered into this file.


CVE Reference No.: CVE-NO-MATCH


Severity Username 
 N/A



Solution:
Ensure that all system users on your Unix system as well as the 'root' account and any other sensitive accounts are listed in this file.

 
     

  Check : Xinetd checks  
 

Description:
The xinetd service is an enhanced version of the older inetd service, with security features that were never included in inetd. It is a super server that assists other network services such as FTP and Telnet. When a client tries to connect to an xineted-based service on the host, like telnet, it connects first to the xinetd daemon. Xinetd receives the connection request and then it starts an instance of the server program appropriate to the specific service. In the case of telnet, it starts in.telnetd. Xinetd provides service specific configuration options, such as access control (which inetd needed TCP Wrappers to provide), logging, resource utilization, binding and redirection.


CVE Reference No.:


Severity Service 



Solution:
Make sure only the necessary services are started by xinetd. If any violations are shown, you need to modify the configuration of that service in the /etc/xinetd.d folder, and then restart the xinetd service.

 
     

  Check : .rhosts files  
 

Description:
The $HOME/.rhosts (or .rlogin) file defines which remote hosts (computers on a network) can invoke certain commands on the local host without supplying a password. This file is a hidden file in the local user's home directory and must be owned by the local user.The format of the $HOME/.rhosts file is: HostNameField [UserNameField] When a remote command executes, the local host uses the local /etc/hosts.equiv file and the $HOME/.rhosts file of the local user account to validate the remote host and remote user.


CVE Reference No.:


Severity .rhosts files 
 find: /proc/15384/task/15384/fd/5: No such file or directory
 find: /proc/15384/fd/5: No such file or directory



Solution:
Although you can set any permissions for this file, it is recommended that the permissions of the .rhosts file be set to 600 (read and write by owner only). Due to serious problems rlogin was rarely used across untrusted networks (like the public internet) and even in closed deployments it has fallen into relative disuse (with many Unix and Linux distributions no longer including it by default). Many networks which formerly relied on rlogin and telnet have replaced it with SSH and its rlogin-equivalent slogin.

 
     

  Users and Groups  

  Check : Generic accounts  
 

Description:
This probe determines the local accounts on the target system. The policy allows you to set regular expression based strings, which should never occur in a account name. These typically consist of generic names such as 'test', 'guest', 'vendor', etc. We strongly recommend you add to this list by including the name of your organization, city, line of business, etc. This probe does case insensitive pattern matching, so it will detect these strings if they occur anywhere in the username.


CVE Reference No.: CVE-NO-MATCH


Severity



Solution:
It is recommended to give unique names to each user account, which positively identifies the actual user. The use of generic names such as 'test' or 'admin', must be strongly prohibited, as it takes away accountability. Investigate any suspicious or generic account names that are marked in the output, and ensure that they are renamed to represent genuine users of the system.

 
     

  Check : Members of wheel group  
 

Description:
This probe determines the members of the 'wheel' group. It lists out any users that are members, but are not in the 'allowed' list as specified by the Policy. All users in the 'wheel' group have the right to 'su' to root.


CVE Reference No.:


Severity Current members 
 root



Solution:
Make sure only trusted users are members of the 'wheel' group.

 
     

  Check : System users having false shell  
 

Description:
All system users must be given false shells to prevent an attacker from trying to create a backdoor by logging in using such account. The list of invalid shells includes /sbin/nologin, /bin/false, and any others that you specify via the policy.


CVE Reference No.: CVE-NO-MATCH


Severity System User  Login Shell 
 adm  /sbin/nologin
 bin  /sbin/nologin
 daemon  /sbin/nologin
 ftp  /sbin/nologin
 games  /sbin/nologin
 gdm  /sbin/nologin
 gopher  /sbin/nologin
 halt  /sbin/halt
 lp  /sbin/nologin
 mail  /sbin/nologin
 mailnull  /sbin/nologin
 news  N/A
 nfsnobody  /sbin/nologin
 nobody  /sbin/nologin
 nscd  /sbin/nologin
 ntp  /sbin/nologin
 operator  /sbin/nologin
 pcap  /sbin/nologin
 rpc  /sbin/nologin
 rpcuser  /sbin/nologin
 rpm  /sbin/nologin
 shutdown  /sbin/shutdown
 smmsp  /sbin/nologin
 sshd  /sbin/nologin
 sync  /bin/sync
 uucp  /sbin/nologin
 vcsa  /sbin/nologin
 xfs  /sbin/nologin



Solution:
Ensure that all system accounts (listed as inactive in the output of the 'last' command), have been assigned an invalid shell.

 
     

  Check : System users are locked out  
 

Description:
This probe checks if system users have been locked out by supplying an invalid password hash in the /etc/shadow file. This will prevent an attacker from using such an account as a backdoor for access the system.


CVE Reference No.: CVE-NO-MATCH


Severity System User  Lock Character(s) 
 adm  *
 bin  *
 daemon  *
 ftp  *
 games  *
 gdm  !!
 gopher  *
 halt  *
 lp  *
 mail  *
 mailnull  !!
 news  *
 nfsnobody  !!
 nobody  *
 nscd  !!
 ntp  !!
 operator  *
 pcap  !!
 rpc  !!
 rpcuser  !!
 rpm  !!
 shutdown  *
 smmsp  !!
 sshd  !!
 sync  *
 uucp  *
 vcsa  !!
 xfs  !!



Solution:
Ensure that all system accounts have invalid hash values in their password fields.

 
     

  Check : Dangerous accounts  
 

Description:
Usually attackers will attempt to leave backdoors on a system that they have compromised. One of the ways in which this is done is by creating new user accounts in the /etc/passwd and /etc/shadow files. This probe determines if specific accounts exist, which may indicate that the server may have been compromised. The account names that are checked for, are those supplied in the policy.


CVE Reference No.:


Severity Username 



Solution:
Investigate why and how such account(s) got created in the first place. We recommend a thorough, in-depth forensics investigation bearing in mind, that there is a high likelihood that the server has been compromised.

 
     

  Check : User ID 0  
 

Description:
A User ID of 0 on the Unix system represents a super-user. This probe determines if there are any users other than root, that have a user ID of 0 in the /etc/passwd file


CVE Reference No.: CVE-NO-MATCH


Severity Username 
 root



Solution:
If there is a violation of this policy, it must be dealt with immediately. We recommend a detailed forensics investigation to check how and under what circumstances was another account with user ID 0 created on the system. It may be the case, that this system has been completely compromised.

 
     

  Check : Users without password  
 

Description:
All non-system users on the Unix system must have a valid password. This probe determines if the account has a non-blank entry in the second column of /etc/passwd


CVE Reference No.: CVE-NO-MATCH


Severity Username 



Solution:
Ensure that all user accounts have a valid password, subject to password complexity requirements.

 
     

  Check : Password expiry  
 

Description:
This probe determines if the password expiry parameters in the /etc/shadow file are set as per the policy. The parameters considered are:


CVE Reference No.:


Severity User  Min. Days  Max. Days  Warning Days  Days Before Inactive  Last Change  Expiry 



Solution:
Ensure that the password aging parameters are set in accordance with your organizational security policy. For existing users, this can be done by using the 'chage' command, and on a system-wide level this can be done by setting the correct parameters in the /etc/login.defs file. These parameters are:
PASS_MIN_DAYS (number)
The minimum number of days allowed between password changes. Any password changes attempted sooner than this will be rejected. If not specified, a zero value will be assumed.

PASS_MIN_LEN (number)
The minimum number of characters in an acceptable password. An attempt to assign a password with fewer characters will be rejected. A zero value suppresses this check. If not specified, a zero value will be assumed.

PASS_MAX_DAYS (number)
The maximum number of days a password may be used. If the password is older than this, then the account will be locked. If not specified, a large value will be assumed.

PASS_WARN_AGE (number)
The number of days warning given before a password expires. A zero means warning is given only upon the day of expiration, a negative value means no warning is given. If not specified, no warning will be provided.

 
     

  System Environment  

  Check : Uptime  
 

Description:
Checks for the time for which the target Linux box is running.


CVE Reference No.:


Severity System Uptime and number of currently logged on users 
    09:40:05 up 57 min, 0 users, load average: 1.78, 1.49, 0.92



Solution:

 
     

  Check : Last reboots  
 

Description:
It check's when was the linux boz last rebooted.


CVE Reference No.:


Severity Day  Month  Date  Time  Relative Time 
   Wed  Jan  23  08:43  (00:56)



Solution:

 
     

  Check : Currently logged on users  
 

Description:
Checks for currently logged in users to the target linux box.


CVE Reference No.:


Severity User  TTY  Month  Date  Time  From 



Solution:

 
     

  Check : Remote root logins  
 

Description:
Check if the any user is connected to the target linux box remotely.


CVE Reference No.:


Severity USER  TTY  FROM  DAY  MONTH  DATE  IN-TIME  OUT-TIME  DURATION 



Solution:

 
     

  Check : Allowed terminals for root login  
 

Description:
Checks for allowed terminal for root logins like telnet,WinSCP etc.


CVE Reference No.:


Severity Allowed Terminals 
 console
 vc/1
 vc/2
 vc/3
 vc/4
 vc/5
 vc/6
 vc/7
 vc/8
 vc/9
 vc/10
 vc/11
 tty1
 tty2
 tty3
 tty4
 tty5
 tty6
 tty7
 tty8
 tty9
 tty10
 tty11



Solution:

 
     

  Check : Memory status  
 

Description:
This probe displays the free and consumed memory within the system


CVE Reference No.:


Severity Attribute  Size 
   Cached   37796 kB
   SwapCached   4 kB
   Active   151884 kB
   Inactive   15296 kB
   HighTotal   0 kB
   HighFree   0 kB
   LowTotal   255704 kB
   LowFree   3648 kB
   SwapTotal   522104 kB
   SwapFree   522012 kB
   Dirty   40 kB
   Writeback   0 kB
   AnonPages   85776 kB
   Mapped   36388 kB
   Slab   78616 kB
   PageTables   3092 kB
   NFS_Unstable   0 kB
   Bounce   0 kB
   CommitLimit   649956 kB
   Committed_AS   395568 kB
   VmallocTotal   770040 kB
   VmallocUsed   2556 kB
   VmallocChunk   767368 kB
   HugePages_Total   0
   HugePages_Free   0
   HugePages_Rsvd   0
   Hugepagesize   4096 kB



Solution:
Check to see if enough memory is free. If not, check the output in the 'ps' or 'top' commands to determine which processes are consuming maximum memory.

 
     

  Check : Current processes  
 

Description:
This probe displays the running processes, process IDs, CPU usage, memory usage, and other related information


CVE Reference No.:


Severity PID  RUSER  EUSER  %CPU  %MEM  DATE  ELAPSED_TIME  TTY  PROCESS 
   Warning:  bad  syntax,  perhaps  a  bogus  '-'?  See  /usr/share/doc/procps-3.2.7/FAQ
   2  root  root  0.0  0.0  08:42  57:19  ?  [migration/0]
   4  root  root  0.0  0.0  08:42  57:19  ?  [watchdog/0]
   6  root  root  0.0  0.0  08:42  57:19  ?  [khelper]
   7  root  root  0.0  0.0  08:42  57:19  ?  [kthread]
   11  root  root  0.0  0.0  08:42  57:19  ?  [kacpid]
   68  root  root  0.0  0.0  08:42  57:19  ?  [cqueue/0]
   71  root  root  0.0  0.0  08:42  57:19  ?  [khubd]
   138  root  root  0.0  0.0  08:42  57:19  ?  [aio/0]
   295  root  root  0.0  0.0  08:42  57:16  ?  [kpsmoused]
   342  root  root  0.0  0.0  08:43  57:03  ?  [kauditd]
   816  root  root  0.0  0.0  08:43  56:54  ?  [kgameportd]
   1115  root  root  0.0  0.0  08:43  56:38  ?  [kmirrord]
   1137  root  root  0.0  0.0  08:43  56:36  ?  [kjournald]
   1745  root  root  0.0  0.0  08:43  56:16  ?  [krfcommd]
   1803  root  root  0.0  0.1  08:43  56:14  ?  /usr/bin/hidd
   2070  avahi  avahi  0.0  0.1  08:44  55:59  ?  avahi-daemon:
   2375  root  root  0.0  0.1  08:46  53:50  ?  /usr/bin/ssh-agent
   2378  root  root  0.0  0.2  08:46  53:50  ?  /usr/bin/dbus-launch
   2388  root  root  0.0  0.2  08:46  53:48  ?  /usr/bin/gnome-keyring-daemon
   3  root  root  0.0  0.0  08:42  57:19  ?  [ksoftirqd/0]
   135  root  root  0.0  0.0  08:42  57:19  ?  [pdflush]
   1690  root  root  0.0  0.2  08:43  56:17  ?  rpc.idmapd
   1731  root  root  0.0  0.1  08:43  56:16  ?  /usr/sbin/sdpd
   1837  root  root  0.0  0.2  08:43  56:13  ?  /usr/sbin/acpid
   1848  root  root  0.0  0.2  08:43  56:13  ?  ./hpiod
   1961  smmsp  smmsp  0.0  0.5  08:44  56:05  ?  sendmail:
   2028  root  root  0.0  0.2  08:44  56:03  ?  anacron
   2038  root  root  0.0  0.1  08:44  56:03  ?  /usr/sbin/atd
   2088  68  68  0.0  0.3  08:44  55:56  ?  hald-addon-acpi:
   2178  root  root  0.0  0.1  08:44  55:52  ?  /usr/sbin/smartd
   2184  root  root  0.0  0.1  08:44  55:52  tty2  /sbin/mingetty
   2185  root  root  0.0  0.1  08:44  55:52  tty3  /sbin/mingetty
   2186  root  root  0.0  0.1  08:44  55:52  tty4  /sbin/mingetty
   2187  root  root  0.0  0.1  08:44  55:52  tty5  /sbin/mingetty
   2188  root  root  0.0  0.1  08:44  55:52  tty6  /sbin/mingetty
   5  root  root  0.0  0.0  08:42  57:19  ?  [events/0]
   1628  rpc  rpc  0.0  0.2  08:43  56:19  ?  portmap
   1720  root  root  0.0  0.3  08:43  56:16  ?  /usr/sbin/hcid
   1973  root  root  0.0  0.1  08:44  56:05  ?  gpm
   2183  root  root  0.0  0.1  08:44  55:52  tty1  /sbin/mingetty
   2499  root  root  0.0  0.0  08:46  53:37  ?  [netstat]
   73  root  root  0.0  0.0  08:42  57:19  ?  [kseriod]
   2093  68  68  0.0  0.3  08:44  55:55  ?  hald-addon-keyboard:
   1595  root  root  0.0  0.1  08:43  56:20  ?  klogd
   1657  root  root  0.0  0.2  08:43  56:18  ?  rpc.statd
   1984  root  root  0.0  0.4  08:44  56:04  ?  crond
   2461  root  root  0.0  0.3  08:46  53:42  ?  /usr/libexec/mapping-daemon
   1853  root  root  0.0  1.7  08:43  56:12  ?  python
   1879  root  root  0.0  0.3  08:43  56:10  ?  /usr/sbin/sshd
   2291  root  root  0.0  0.5  08:44  55:50  ?  /usr/sbin/gdm-binary
   1890  root  root  0.0  0.4  08:43  56:10  ?  /bin/sh
   2503  root  root  0.0  0.2  08:46  53:35  ?  /sbin/pam_timestamp_check
   1865  root  root  0.0  0.8  08:43  56:11  ?  cupsd
   1953  root  root  0.0  0.6  08:44  56:05  ?  sendmail:
   2017  xfs  xfs  0.0  0.6  08:44  56:03  ?  xfs
   1575  root  root  0.0  0.2  08:43  56:22  ?  auditd
   2082  root  root  0.0  0.3  08:44  55:57  ?  hald-runner
   2287  root  root  0.0  1.0  08:44  55:50  ?  /usr/sbin/gdm-binary
   2420  root  root  0.0  1.1  08:46  53:45  ?  /usr/libexec/gnome-vfs-daemon
   2466  root  root  0.0  0.8  08:46  53:42  ?  ./escd
   10  root  root  0.0  0.0  08:42  57:19  ?  [kblockd/0]
   2379  root  root  0.0  0.3  08:46  53:50  ?  /bin/dbus-daemon
   1783  root  root  0.0  0.4  08:43  56:15  ?  pcscd
   2459  root  root  0.0  0.4  08:46  53:42  ?  /usr/libexec/gam_server
   136  root  root  0.0  0.0  08:42  57:19  ?  [pdflush]
   2433  root  root  0.0  1.7  08:46  53:45  ?  bt-applet
   1592  root  root  0.0  0.2  08:43  56:21  ?  syslogd
   2189  root  root  0.0  1.6  08:44  55:52  ?  /usr/sbin/gdm-binary
   15353  root  root  0.0  0.1  09:30  09:38  ?  ./AUDITPRO
   1818  root  root  0.0  0.4  08:43  56:14  ?  automount
   2416  root  root  0.0  0.9  08:46  53:46  ?  /usr/libexec/bonobo-activation-server
   2418  root  root  0.0  3.0  08:46  53:45  ?  eggcups
   15336  root  root  0.0  0.4  09:30  09:38  ?  bash
   2465  root  root  0.0  3.2  08:46  53:42  ?  /usr/libexec/trashapplet
   2497  root  root  0.0  1.7  08:46  53:37  ?  pam-panel-icon
   1577  root  root  0.0  1.4  08:43  56:22  ?  python
   2486  root  root  0.0  2.8  08:46  53:39  ?  /usr/libexec/notification-area-applet
   1709  dbus  dbus  0.0  0.3  08:43  56:17  ?  dbus-daemon
   137  root  root  0.0  0.0  08:42  57:19  ?  [kswapd0]
   2447  root  root  0.0  3.6  08:46  53:43  ?  nm-applet
   15334  root  root  0.0  0.9  09:30  09:38  ?  sshd:
   2069  avahi  avahi  0.0  0.5  08:44  55:59  ?  avahi-daemon:
   2316  root  root  0.0  2.6  08:46  53:52  ?  /usr/bin/gnome-session
   2488  root  root  0.0  3.8  08:46  53:39  ?  /usr/libexec/clock-applet
   314  root  root  0.0  0.0  08:42  57:12  ?  [kjournald]
   2385  root  root  0.0  1.2  08:46  53:50  ?  /usr/libexec/gconfd-2
   1914  mysql  mysql  0.0  5.4  08:43  56:09  ?  /usr/sbin/mysqld
   376  root  root  0.0  0.3  08:43  57:01  ?  /sbin/udevd
   2439  root  root  0.0  5.1  08:46  53:44  ?  /usr/bin/python
   2494  root  root  0.0  2.3  08:46  53:37  ?  gnome-power-manager
   2490  root  root  0.0  4.3  08:46  53:39  ?  /usr/libexec/mixer_applet2
   2390  root  root  0.0  3.0  08:46  53:48  ?  /usr/libexec/gnome-settings-daemon
   2463  root  root  0.0  4.0  08:46  53:42  ?  /usr/libexec/wnck-applet
   2403  root  root  0.0  3.0  08:46  53:47  ?  metacity
   2509  root  root  0.0  1.3  08:46  53:22  ?  gnome-screensaver
   2057  root  root  0.0  4.6  08:44  56:00  ?  /usr/bin/python
   2081  68  68  0.0  1.3  08:44  55:58  ?  hald
   2105  root  root  0.0  0.2  08:44  55:54  ?  hald-addon-storage:
   2410  root  root  0.0  4.8  08:46  53:46  ?  gnome-panel
   1  root  root  0.1  0.2  08:42  57:19  ?  init
   2477  root  root  0.1  8.6  08:46  53:40  ?  /usr/bin/python
   2412  root  root  0.1  6.1  08:46  53:46  ?  nautilus
   2294  root  root  0.9  3.7  08:44  55:50  tty7  /usr/bin/Xorg



Solution:
Ensure that no single process is hogging maximum CPU or memory.

 
     

  Check : Single user boot protection  
 

Description:


CVE Reference No.:


Severity Status 
 Single User boot mode is not password protected through 'sulogin'



Solution:
Set a strong password for Single User boot mode.

 
     

  Check : PATH environment variable check  
 

Description:
Checks for the value of the PATH environment variable


CVE Reference No.:


Severity Status 
 No period at end of the path environment variable for 'root'
 Root directory (/) not found in path environment variable for 'root'
 Double colon (::) not found in path environment variable for 'root'



Solution:

 
     

  Check : Root shell IFS  
 

Description:
Checks for Installable File System (IFS)


CVE Reference No.:


Severity Status 
 Forward slash(/) not present in IFS environment variable for 'root'



Solution:

 
     

  Filesystem Security  

  Check : Mounted partitions  
 

Description:
This probe determines the mounted partitions and their parameters


CVE Reference No.:


Severity Filesystem  Mounted On  Type  Mode 
   /dev/hda2  /  ext3  (rw)
   proc  /proc  proc  (rw)
   sysfs  /sys  sysfs  (rw)
   devpts  /dev/pts  devpts  (rw,gid=5,mode=620)
   /dev/hda1  /boot  ext3  (rw)
   tmpfs  /dev/shm  tmpfs  (rw)
   none  /proc/sys/fs/binfmt_misc  binfmt_misc  (rw)
   sunrpc  /var/lib/nfs/rpc_pipefs  rpc_pipefs  (rw)



Solution:
This is an informational probe, and usually does not require any fix to be applied

 
     

  Check : Disk usage  
 

Description:
This probe determines if disk usage has crossed a preset limit as defined in the policy.


CVE Reference No.: