Cisco Cisco Broadband Access Center Telco Wireless 3.7 Release Notes

Page of 4
Cisco BAC 3.7 Hardening Guidelines 
 
SunOS bactst-0911-v210-1 5.10 Generic_147440-01 sun4u sparc SUNW,Sun-Fire-V210 
 
bash-3.2# showrev -p | grep 147440-01 
Patch: 147440-01 Obsoletes:  Requires: 118833-36, 120011-14, 125555-10, 127127-11, 
137137-09, 139555-08, 141444-09, 142909-17, 144500-19, 142933-04 Incompatibles:  
Packages: SUNWcakr, SUNWckr, SUNWmdbr, FJSVmdbr 
 
Disabling unused network services 
1. 
Disable unused network services. All network services can be disabled except the secure shell by using the 
following command: 
# netservices limited 
 
Example: 
 
# netservices limited 
restarting syslogd 
restarting sendmail 
restarting wbem 
dtlogin needs to be restarted. Restart now? [Y] y 
restarting dtlogin 
 
Sun Solaris Security Toolkit 
1. 
The Solaris Security Toolkit (SUNWjass) is a tool designed to assist in creation and deployment of secured 
Solaris Operating Environment systems. The Toolkit is comprised of a set of scripts and directories 
implementing the recommendations made in the Sun BluePrints OnLine program. 
2. 
These scripts can be executed on Solaris systems through the JumpStart technology or directly from the 
command line. The Toolkit includes scripts to harden, patch, and minimize Solaris Operating Environment 
systems. Sun does not support the Toolkit. 
3. 
Download the package from 
. 
4. 
Change to the directory that contains the Sun Solaris Security Toolkit package and install the package 
(SUNWjass) by using the following command: 
# pkgadd -d ./ 
 
Example: 
 
# pkgadd -d ./ 
The following packages are available: 
  1  SUNWjass     Solaris Security Toolkit 4.2.0 
                  (Solaris) 4.2.0 
Select package(s) you wish to process (or 'all' to process all packages). (default: 
all) [?,??,q]: 
 
Processing package instance <SUNWjass> from </opt> 
 
Solaris Security Toolkit 4.2.0(Solaris) 4.2.0 
Copyright 2005 Sun Microsystems, Inc.  All rights reserved. 
Use is subject to license terms. 
 
Using </opt> as the package base directory. 
## Processing package information. 
## Processing system information. 
   415 package pathnames are already properly installed. 
## Verifying package dependencies. 
## Verifying disk space requirements. 
## Checking for conflicts with packages already installed.