Solaris Benchmark v1.2.

0

Copyright 2001-2003, The Center for Internet Security http://www.CISecurity.org/

Solaris Benchmark v1.2.0 February 19, 2003
Copyright 2001-2003, The Center for Internet Security (CIS) Agreed Terms of Use Background. CIS provides benchmarks, scoring tools, software, data, information, suggestions, ideas, and other services and materials from the CIS website or elsewhere (“Products”) as a public service to Internet users worldwide. Recommendations contained in the Products (“Recommendations”) result from a consensus-building process that involves many security experts and are generally generic in nature. The Recommendations are intended to provide helpful information to organizations attempting to evaluate or improve the security of their networks, systems and devices. Proper use of the Recommendations requires careful analysis and adaptation to specific user requirements. The Recommendations are not in any way intended to be a “quick fix” for anyone’s information security needs. No representations, warranties and covenants. CIS makes no representations, warranties or covenants whatsoever as to (i) the positive or negative effect of the Products or the Recommendations on the operation or the security of any particular network, computer system, network device, software, hardware, or any component of any of the foregoing or (ii) the accuracy, reliability, timeliness or completeness of any Product or Recommendation. CIS is providing the Products and the Recommendations “as is” and “as available” without representations, warranties or covenants of any kind. User agreements. By using the Products and/or the Recommendations, I and/or my organization (“we”) agree and acknowledge that: 1. No network, system, device, hardware, software or component can be made fully secure; 2. We are using the Products and the Recommendations solely at our own risk;

ii

3. We are not compensating CIS to assume any liabilities associated with our use of the Products or the Recommendations, even risks that result from CIS’s negligence or failure to perform; 4. We have the sole responsibility to evaluate the risks and benefits of the Products and Recommendations to us and to adapt the Products and the Recommendations to our particular circumstances and requirements; 5. Neither CIS, nor any CIS Party (defined below) has any responsibility to make any corrections, updates, upgrades or bug fixes or to notify us if it chooses at its sole option to do so; and 6. Neither CIS nor any CIS Party has or will have any liability to us whatsoever (whether based in contract, tort, strict liability or otherwise) for any direct, indirect, incidental, consequential, or special damages (including without limitation, loss of profits, loss of sales, loss of or damage to reputation, loss of customers, loss of software, data, information or emails, loss of privacy, loss of use of any computer or other equipment, business interruption, wasted management or other staff resources or claims of any kind against us from third parties) arising out of or in any way connected with our use of or our inability to use any of the Products or Recommendations (even if CIS has been advised of the possibility of such damages), including without limitation any liability associated with infringement of intellectual property, defects, bugs, errors, omissions, viruses, worms, backdoors, Trojan horses or other harmful items. Grant of limited rights. CIS hereby grants each user the following rights, but only so long as the user complies with all of the terms of these Agreed Terms of Use: 1. Except to the extent that we may have received additional authorization pursuant to a written agreement with CIS, each user may download, install and use each of the Products on a single computer; 2. Each user may print one or more copies of any Product or any component of a Product that is in a .txt, .pdf, .doc, .mcw, or .rtf format, provided that all such copies are printed in full and are kept intact, including without limitation the text of this Agreed Terms of Use in its entirety. Retention of intellectual property rights; limitations on distribution. The Products are protected by copyright and other intellectual property laws and by international treaties. We acknowledge and agree that we are not acquiring title to any intellectual property rights in the Products and that full title and all ownership rights to the Products will remain the exclusive property of CIS or CIS Parties. CIS reserves all rights not expressly granted to users in the preceding section entitled “Grant of limited rights.” Subject to the paragraph entitled “Special Rules” (which includes a waiver, granted to some classes of CIS Members, of certain limitations in this paragraph), and except as we

iii

or other similar mechanism or device. and in such case. or otherwise attempt to derive the source code for any software Product that is not already in the form of source code. encumber. affiliates. employees. bulletin board. hardware suppliers. development or maintenance of the Products or Recommendations (“CIS Parties”) harmless from and against any and all liability. or (viii) represent or claim a particular level of compliance with a CIS Benchmark. (ii) distribute. (iii) post any Product or any component of a Product on any website. whether by manual or electronic means. or otherwise transfer or exploit rights to any Product or any component of a Product. at our expense. lend. to assume the exclusive defense and control of any matter subject to this indemnification. Each such Member acknowledges and agrees that iv . disassemble. We hereby agree to indemnify. we agree to cooperate with CIS in its defense of such claim. logo. newsgroup. symbols or labels in any Product or any component of a Product.htm). The distribution of the NSA Security Recommendations is subject to the terms of the NSA Legal Notice and the terms contained in the NSA Security Recommendations themselves (http://nsa2. We further agree that all CIS Parties are third-party beneficiaries of our undertakings in these Agreed Terms of Use. sublicense. sell. including without limitation CIS’s right. defend and hold CIS and all of its officers. contributors.www. (vii) use any Product or any component of a Product with other products or applications that are directly and specifically dependent on such Product or any component for any part of their functionality. agents. directors. or alter these Agreed Terms of Use as they appear in. We will not facilitate or otherwise aid other individuals or entities in any of the activities listed in this paragraph. (vi) use any Product or any component of a Product with any derivative works based directly on a Product or any component of a Product. without regard to whether such mechanism or device is internal or external. and all other persons who aided CIS in the creation.conxion. CIS hereby grants each CIS Security Consulting or Software Vendor Member and each CIS Organizational User Member. members. losses. any Product or any component of a Product. information and service providers. scoring tool or other Product.may have otherwise agreed in a written agreement with CIS. Special rules. legends. Those special rules will override and supersede these Agreed Terms of Use with respect to the users who are covered by the special rules. costs and expenses (including attorneys' fees and court costs) incurred by CIS or any CIS Party in connection with any claim arising out of any violation by us of the preceding paragraph. licensors. rent. but only so long as such Member remains in good standing with CIS and complies with all of the terms of these Agreed Terms of Use. (v) remove these Agreed Terms of Use from. the right to distribute the Products and Recommendations within such Member’s own organization. redistribute. we agree that we will not (i) decompile.com/cisco/notice. copyright or other proprietary notices. lease. reverse engineer. developers. ftp server. (iv) remove or alter trademark. software suppliers. CIS has created and will from time to time create special rules for its members and for other persons and organizations with which CIS has a written contractual relationship. authors.

Choice of law. Agreed Terms of Use .2 (March 20. therefore. jurisdiction. We acknowledge and agree that we have read these Agreed Terms of Use in their entirety. be modified or terminated by CIS at any time. venue. 2003) v . We acknowledge and agree that these Agreed Terms of Use will be governed by and construed in accordance with the laws of the State of Maryland. then such terms shall be deemed severable and shall not affect the validity and enforceability of any remaining provisions.the foregoing grant is subject to the terms of such Member’s membership arrangement with CIS and may. If any of these Agreed Terms of Use shall be determined to be unlawful. that any action at law or in equity arising out of or relating to these Agreed Terms of Use shall be filed only in the courts located in the State of Maryland. understand them and agree to be bound by them in all respects. that we hereby consent and submit to the personal jurisdiction of such courts for the purposes of litigating any such action.Version 1. or for any reason unenforceable. void.

....2 Install TCP Wrappers......... 21 3........19 Only enable SNMP if absolutely necessary............................................. 25 4 Kernel Tuning ........................... 9 2..14 Only enable the LDAP cache manager if absolutely necessary ................12 Only enable Kerberos server daemons if absolutely necessary ............6 Use better TCP sequence numbers .........................2 Set daemon umask .............8 Only enable CDE-related daemons if absolutely necessary ....... 22 3..................................................................... 9 2............................15 Only enable the printer daemons if absolutely necessary................ 17 3..................................................................................... 14 3............6 Disable boot services if possible.........................................5 Only enable TFTP if absolutely necessary .................................... 11 2................... 6 2........................................................................................10 Only enable Kerberos-related daemons if absolutely necessary........................ 15 3................................1 Disable standard services..........3 Only enable FTP if absolutely necessary......3 Install SSH ..........11 Only enable other RPC-based services if absolutely necessary................................................................................................5 Disable email server............................................. 13 3.....................4 Network Parameter Modifications................................... 2 1..4 Only enable rlogin/rsh/rcp if absolutely necessary.........18 Only enable Web server if absolutely necessary .................................................1 Apply latest OS patches .................................................17 Only enable GUI login if absolutely necessary ...... 7 2..................................... 8 2...................................................................................................................11 Minimize inetd. 18 3.........................................................8 Only enable Windows-compatibility servers if absolutely necessary ......................................20 Only enable DHCP server if absolutely necessary ..........................................7 Only enable rquotad if absolutely necessary....................................... 23 3....................................3 Restrict NFS client requests to privileged ports .. 10 2......................1 Disable login: prompts on serial ports................. disable inetd if possible................................................................................................ 19 3.......... 26 4......................................................... 10 2.................................. 23 3............................... 5 2 Minimize inetd network services ........................ 29 vi 1 .......................... 7 2...................................................... 20 3.............................2 Enable stack protection ................ 21 3.......................10 Only enable NFS client processes if absolutely necessary ......3 Turn on inetd tracing.................................2 Only enable telnet if absolutely necessary ........ 12 2.........................9 Only enable NFS server processes if absolutely necessary ................. 20 3............................................................................................. 13 3.........................conf file.... 12 3 Minimize boot services ........................................ 27 4............ 2 1......... 19 3...................... 13 3..... 24 3........ 28 4.......................1 Disable core dumps.................. 26 4.....................................4 Prevent Syslog from accepting messages from network ..........9 Only enable Solaris Volume Manager daemons if absolutely necessary . 24 3.................13 Only enable directory server if absolutely necessary ............ 3 1.................................... 25 4............5 Additional network parameter modifications ...............................6 Only enable printer service if absolutely necessary................................. 25 4............................................................................ 6 2....................................................................................... 16 3..................7 Disable other standard boot services....................16 Only enable the volume manager if absolutely necessary ........................................................................ 22 3.................CIS Solaris Benchmark Patches and Additional Software ..................... if possible ..

...............................8 Restrict at/cron to authorized users .....2 Verify that there are no accounts with empty password fields ......12 Limit number of failed login attempts ..........7 Set default locking screensaver timeout .......... 41 7..................................................................................... 44 7......... 36 6..............9 Remove empty crontab files and restrict file permissions ................................................................4 Use full path names in /etc/dfs/dfstab file .......... 43 7................7 User home directories should be mode 750 or more restrictive ........................ 39 7. 38 6....9 Run fix-modes ........... 41 7.............. 51 8...............6 Prevent X server from listening on port 6000/tcp............................. 50 8.......2 Add 'logging' option to root file system .......................................................... 48 8............................ 31 5........................... 38 7 System Access.............3 Create /var/adm/loginlog ...... and group files ....5 Verify passwd......... 42 7.... 36 6..............5 Enable system accounting.............................................................8 Find unauthorized SUID/SGID system executables............... 30 5.................Logging ..................................................... 53 8....................4 Verify no legacy '+' entries exist in passwd.................3 Create /etc[/ftpd]/ftpusers ..................8 No user dot-files should be group/world writable ..........3 Set account expiration parameters on active accounts................................10 Set default umask for users ........................................ 40 7.......................................................................13 Set EEPROM security-mode and log failed access........................................................................................... 33 6 File/Directory Permissions/Access ................7 Confirm permissions on system log files.................................. 32 5.............................. 46 7............................................................................................. 50 8.............1 Capture messages sent to syslog AUTH facility ..... 52 8................ 44 7.' or group/world-writable directory in root $PATH .......................... 34 6.........................4 Turn on cron logging.......................4 Create /etc/shells...................... 51 8......................... 36 6..... and Authorization..10 Create appropriate warning banners ............................conf.........................................6 No '..................................6 World-writable directories should have their sticky bit set .....................................................3 Add 'nosuid' option to /etc/rmmount............................................................................................................. 48 8................ 35 6................netrc files .....................1 File systems are mounted either 'ro' or 'nosuid' .............. 37 6...................................................................................... 48 8............... 29 5....5 Prevent remote XDMCP access... and group file permissions ......................... 30 5................. 39 7..................................................................................7 Find unauthorized world-writable files.... 31 5.. Authentication.. 39 7........................................ shadow.................................................5 Verify that no UID 0 accounts exist other than root............................ 47 8 User Accounts and Environment ............. 43 7.............. 52 8............. 54 vii 5 .............................. 34 6.................. 53 Appendix A: Log Rotation Script ..........11 Restrict root logins to system console ........................................................................1 Block system accounts................................................................11 Set "mesg n" as default for all users ... 49 8..conf ............... 35 6..........9 Remove user ....................................................2 Capture FTP and inetd Connection Tracing Info.......................6 Enable kernel-level auditing ................ shadow.......................rhosts support in /etc/pam............................................................................................................................... 46 7...........................................1 Remove .............................................................................................................................................................2 Create symlinks for dangerous files................. 29 5...................................

CIS Solaris Benchmark A Word about Shaded Items Desktop systems typically have different security expectations than server-class systems. Root Shell Environment Assumed The actions listed in this document are written with the assumption that they will be executed by the root user running the /sbin/sh shell and without noclobber set.conf \ /etc/shadow /etc/shells /etc/syslog.resources \ /etc/dt/config/*/Xresources.conf \ /etc/dfs/dfstab /etc/ssh/ssh*_config /.rhosts \ /. shaded text has been used to indicate questions and/or actions that are typically not applicable to desktop systems in a large enterprise environment. Some actions may need to be modified if the order is changed.shosts /etc/cron.conf /etc/system \ /etc/vfstab /etc/default/cron /etc/default/ftpd \ /etc/default/inetinit /etc/default/init \ /etc/default/login /etc/default/sendmail \ /etc/default/telnetd /etc/inet/inetd. Reboot Required Rebooting the system is required after completing all of the actions below in order to complete the re-configuration of the system.login /etc/motd /etc/pam.allow /etc/cron.d/*.equiv /etc/inittab \ /etc/issue /etc/.conf \ /etc/passwd /etc/profile /etc/rmmount. Backup Key Files Before performing the steps of this benchmark it is a good idea to make backup copies of critical configuration files that may get modified by various benchmark items: for file in /etc/ftpusers /etc/hosts. These shaded items may be skipped on these desktop platforms. In many cases. In an effort to facilitate use of this benchmark on these different classes of machines.d/*. Actions are written so that they may be copied directly from this document into a root shell window with a "cut-and-paste" operation.deny \ /etc/dt/config/Xaccess /etc/dt/config/Xservers \ /etc/dt/config/*/sys. do [ -f $file ] && cp $file $file-preCIS done 1 . Executing Actions The actions listed in this document are written with the assumption that they will be executed in the order presented here. the changes made in the steps below will not take effect until this reboot is performed.

com/pub/patches/ -look for files named <osrel>_Recommended./install_cluster -q Action (Solaris 2. Execute the following commands: cd /tmp zcat *_Recommended.6 and earlier): 1.zip.com/service/support/sw_only/patchmanager. or functionality patches that may be required on the local system.zip cd *_Recommended . see http://www.PatchReport file (available from the same FTP site as the patch clusters) for additional security.sun. Y2K. Execute the following commands: cd /tmp unzip -qq *_Recommended.tar. such as the Solaris Patch Manager tool (for more info. administrators may ignore patch individual patch installs that fail with either return code 2 (indicates that the patch has already been installed on the system) or return code 8 (the patch applies to an operating system 2 ./install_cluster -q Discussion: Developing a procedure for keeping up-to-date with vendor patches is critical for the security and reliability of the system. During the cluster installation process.sun. Automated tools for maintaining current patch levels are also available. Vendors issue operating system updates when they become aware of security vulnerabilities and other serious functionality issues. 2. 2.Z. Download Sun Recommended Patch Cluster into /tmp (Sun Recommended Patch Clusters can be obtained from ftp://sunsolve. Note that in addition to installing the Solaris Recommended Patch Clusters as described above. Download Sun Recommended Patch Cluster into /tmp (Sun Recommended Patch Clusters can be obtained from ftp://sunsolve. where <osrel> is the Solaris OS release number).1 Patches and Additional Software 1. where <osrel> is the Solaris OS release number).html).Z | tar xf cd *_Recommended . but it is up to their customers to actually download and install these patches. administrators may wish to also check the Solaris<osrel>.com/pub/patches/ -look for files named <osrel>_Recommended.tar.1 Apply latest OS patches Action (Solaris 7 and later): 1. Administrators are also encouraged to check the individual README files provided with each patch for further information and post-install instructions.sun.

Remove package file after installation: rm -f tcp_wrappers-*-local 1. Use the command "pkgadd –d gzip-*-local all" to install the gzip software from this package file after downloading.0") represents one network block in use by your organization.5-sol7-sparc-local (depending on the current version number of the gzip software and the OS revision). <net>/<mask>. 2. Create /etc/hosts. …" \ >/etc/hosts.g.255. e.sunfreeware. Pre-compiled binaries for various Solaris releases may be obtained from the URL given above. 4.8". Download pre-compiled TCP Wrappers software package from ftp://ftp. the read-only setting on /usr will cause patch installs to fail.1. "5.com/pub/freeware/<proc>/<osrel>/ (here <proc> is the processor type—"sparc" or "intel"— and <osrel> is the Solaris version number of your system.1 for information on making the file system writable before applying patches. "192.3. The gzip utilities are included with the Solaris OS as of Solaris 8 (though the local site may have chosen not to install these utilities as part of their standard install image).2 Install TCP Wrappers Action (Solaris 8 and earlier): 1. The file name will be slightly different depending on the version of the software and the OS release. tcp_wrappers-7. Please refer to the Discussion section in Item 6. Note that Item 6.deny 3 .allow: echo "ALL: <net>/<mask>.gz Note that the gzip compression utilities must be installed in order to install the TCP Wrappers software package. If a patch install fails with any other return code. consult the patch installation log in /var/sadm/install_data. e.255. where the package name would again be something like gzip-1.g.6-sol8-sparc-local.168.package which is not installed on the machine).deny: echo "ALL: ALL " >/etc/hosts. Install package: gunzip tcp_wrappers-*-local.0/255. 1. Create /etc/hosts.allow where each <net>/<mask> combination (for example.gz pkgadd -d tcp_wrappers-*-local all 3. When applying patches to a system that has already been secured according to the steps in this document. etc.).1 below recommends mounting the /usr file system read-only.

TCP Wrappers are generally triggered out of /etc/inet/inetd.deny: echo "ALL: ALL" >/etc/hosts.5.conf.conf Discussion: TCP Wrappers allow the administrator to control who has access to various network services based on the IP address of the remote end of the connection.new inetd. TCP Wrappers also provide logging information via Syslog about both successful and unsuccessful connections. 3.new mv inetd. …" \ >/etc/hosts.255. $6 = "/usr/sfw/sbin/tcpd" }.allow: echo "ALL: <net>/<mask>. <net>/<mask>.conf: cd /etc/inet awk '($3 ~ /^(udp|tcp)/) && \ ($6 != "internal") \ { $7 = $6. Modify inetd.0/255.new mv inetd.conf chown root:sys inetd.255. \ { print }' inetd.conf > inetd.conf > inetd. Create /etc/hosts.conf. but other options exist for "wrappering" non-inetdbased software (see the documentation provided with the source code release). Solaris 9 now includes the TCP Wrappers distribution as part of the operating system (assuming the administrator has installed the SUNWtcpd software package). \ { print }' inetd.conf.conf: cd /etc/inet awk '($3 ~ /^(udp|tcp)/) && \ ($6 != "internal") \ { $7 = $6. Create /etc/hosts.conf chmod 444 inetd.new inetd. "192.0") represents one network block in use by your organization.conf. Modify inetd.conf chown root:sys inetd.conf. $6 = "/usr/local/bin/tcpd" }.deny 4.1.conf Action (Solaris 9): 2.allow where each <net>/<mask> combination (for example.conf chmod 444 inetd.168. 4 .

8. where <vers> is the OS version number as returned by "uname –r" (e..Z pkgadd -d OpenSSH-pkg-* all 3. /^PermitRootLogin/ { $2 = "no" }. /^IgnoreRhosts/ { $2 = "yes" }. etc). /^MaxAuthTriesLog/ { $2 = "0" }. /^RhostsAuthentication/ { $2 = "no" }.new sshd_config chown root:sys sshd_config chmod 600 sshd_config \ \ \ \ \ \ \ \ \ } \ Action (Solaris 8 and earlier): 1. which allow secure encrypted network logins and file transfers. which is available in Solaris package format (the package contains 32-bit executables that should run on all releases of 5 . 5.3 Install SSH Action (Solaris 9 systems): cd /etc/ssh cat <<EOCliConfig >>ssh_config Host * Protocol 2 EOCliConfig awk '/^Protocol/ { $2 = "2" }.org/pub/pkgs/Solaris. compilation of OpenSSH is complicated by the fact that it is dependent upon several other freelyavailable software libraries which also need to be built before OpenSSH itself can be compiled. Remove package file after installation: rm -f OpenSSH-pkg-* Discussion: OpenSSH is a popular free distribution of the standards-track SSH protocols.g. In order to simplify the installation process for Solaris 8 and earlier.new mv sshd_config. The package file name will be OpenSSH-pkg-<vers>. /^PermitEmptyPasswords/ { $2 = "no" }. /^#Banner/ { $1 = "Banner" { print }' sshd_config > sshd_config. 2. 5.CISecurity. However. Install package: uncompress OpenSSH-pkg-*.1. /^RhostsRSAAuthentication/ { $2 = "no" }. Download pre-compiled OpenSSH software from ftp://ftp. /^X11Forwarding/ { $2 = "yes" }. /^MaxAuthTries/ { $2 = "3" }.Z.7. we make use of a pre-compiled version of OpenSSH.

conf done for svc in 100068 100146 100147 100150 100155 100221 \ 100232 100235 rstatd rusersd sprayd walld.openssh.conf.pdf). Indeed.1 onwards). {print}" \ inetd. since Sun is now distributing OpenSSH with the Solaris operating system as of this release.conf.new inetd.conf.conf file shipped with Solaris contains many services which are rarely used.conf.conf.conf done for svc in 100083 100229 100230 100242 \ 100234 100134 kerbd rquotad. since SSH provides both a secure login mechanism and a means of 6 .new inetd.new inetd.conf. do awk "(\$1 == \"$svc\") { \$1 = \"#\" \$1 }.new mv inetd.sun. 2 Minimize inetd network services 2.conf >inetd.Solaris from 2. { print }" \ inetd. { print }" \ inetd.conf.new inetd.com.conf >inetd. {print}" \ inetd. after enabling SSH (see Item 1.conf chmod 444 inetd.conf >inetd. For more information on building OpenSSH from source.conf >inetd. see www.5.conf Discussion: The stock /etc/inet/inetd. do awk "/^$svc\\// { \$1 = \"#\" \$1 }. do awk "/^$svc\\// { \$1 = \"#\" \$1 }.new mv inetd.conf done chown root:sys inetd.3) it may be possible to completely do away with all inetdbased services. This package is not required on Solaris 9 systems.new mv inetd. or which have more secure alternatives. do awk "(\$1 == \"$svc\") { \$1 = \"#\" \$1 }.com/solutions/blueprints/0701/openSSH. Sun also publishes information on building OpenSSH for Solaris as part of its Blueprints series (see http://www.1 Disable standard services Action: cd /etc/inet for svc in time echo discard daytime chargen fs dtspc \ exec comsat talk finger uucp name xaudio.conf.new mv inetd.conf done for svc in printer shell login telnet ftp tftp.

new inetd. rather than the more secure SSH protocol? If the answer to this question is yes.conf >inetd.2 Only enable telnet if absolutely necessary Question: Is there a mission-critical reason that requires users to access this system via telnet. In fact.conf Discussion: telnet uses an unencrypted network protocol. and also that the session can be hijacked by outsiders to gain access to the remote system.conf 7 .conf > inetd.new mv inetd. 2.new inetd. proceed with the action below. the services that are disabled in the last two loops in the "Action" section above. the actions above will disable all standard services normally enabled in the Solaris inetd. The freely-available SSH utilities (see http://www.new mv inetd.conf. Rather than disabling and then re-enabling these services.conf.conf. which means data from the login session (such as passwords and all other data transmitted during the session) can be stolen by eavesdroppers on the network.conf. 2. proceed with the actions below. or is there a mission-critical reason why data must be transferred to and from this system via ftp.openssh. rather than scp? If the answer to this question is yes. The rest of the actions in this section give the administrator the option of re-enabling certain services—in particular.transferring files to and from the system.com/) provide encrypted network logins and should be used instead. Action: awk '!/^#ftp/ { print } /^#ftp/ { $1 = "ftp".3 Only enable FTP if absolutely necessary Question: Is this machine an (anonymous) FTP server. Action: sed 's/^#telnet/telnet/' inetd. experienced administrators may wish to simply disable only those services that they know are unnecessary for their systems.conf file. print $0 " -d -l" }' \ inetd.

3 below.new inetd.com/). Action: sed 's/^#shell/shell/. Given the wide availability of free SSH implementations. see Item 7.4 Only enable rlogin/rsh/rcp if absolutely necessary Question: Is there a mission-critical reason why rlogin/rsh/rcp must be used instead of the more secure ssh/scp? If the answer to this question is yes. If these protocols are left enabled. For further configuration information.2 below. but the system must be configured to capture these messages. Information about FTP sessions will be logged via Syslog. s/^#login/login/' \ inetd. 8 .new mv inetd. which means passwords and other data transmitted during the session can captured by sniffing the network.conf >inetd. consider requiring non-anonymous users on the system to transfer files via SSH-based protocols. Note that if the FTP daemon is left on.conf. it is recommended that the "debugging" (-d) and connection logging (-l) flags also be enabled to track FTP activity on the system.conf Discussion: SSH was designed to be a drop-in replacement for these protocols. see Item 5. see http://www.Discussion: Like telnet. please also see Item 7. 2.1 for additional securityrelated configuration settings. For further information on restricting FTP access to the system.openssh. it seems unlikely that there is ever a case where these tools cannot be replaced with SSH (again. and that the FTP session itself can be hijacked by an external attacker.conf. Even if FTP is required because the local system is an anonymous FTP server. the FTP protocol is unencrypted. SSH provides two different encrypted file transfer mechanisms—scp and sftp—and should be used instead. proceed with the actions below.

new mv inetd. and other similar devices (TFTP is also used during network installs of systems via the Solaris Jumpstart facility).new inetd.conf mkdir –p –m 711 /tftpboot chown root:root /tftpboot Discussion: TFTP is typically used for network booting of diskless workstations. it is best to leave the TFTP service disabled.new mv inetd.conf Discussion: in.new inetd. proceed with the actions below. Even machines that are print servers may wish to leave this service disabled if they do not need to support BSD-style printing.5 Only enable TFTP if absolutely necessary Question: Is this system a boot server or is there some other mission-critical reason why data must be transferred to and from this system via TFTP? If the answer to this question is yes.6 Only enable printer service if absolutely necessary OS Revisions: This item only applies to Solaris 2. 9 .conf. However.conf.conf.6 and later systems. X-terminals. Routers and other network devices may copy configuration data to remote systems via TFTP for backup.conf. proceed with the actions below.conf >inetd.2.conf >inetd. unless this system is needed in one of these roles. Question: Is this machine a print server for your network? If the answer to this question is yes. Action: sed 's/^#tftp/tftp/' inetd. Action: sed 's/^#printer/printer/' inetd.lpd provides a BSD-compatible print server interface. 2.

Action: sed 's/^#100083/100083/' inetd. If your site does not use disk quotas. but also never enable this service on any system which is not well protected by a complete network security infrastructure (including network and host-based firewalls.new mv inetd.conf Discussion: rquotad allows NFS clients to enforce disk quotas on file systems that are mounted from the local system.conf.conf >inetd. but has historically been a major security issue for Solaris systems. packet filters. 10 . not only is it vital to keep up to date on vendor patches.conf Discussion: The rpc.ttdbserverd process supports many tools and applications in Sun's CDE windowing environment. proceed with the actions below. If you do plan to leave this service enabled. 2. Action: sed 's/^#rquotad/rquotad/' inetd. then you may leave the rquotad service disabled. proceed with the actions below.new inetd. and intrusion detection infrastructure).8 Only enable CDE-related daemons if absolutely necessary Question: Is there a mission-critical reason to run a GUI on this system? If the answer to this question is yes.2.conf >inetd.conf.7 Only enable rquotad if absolutely necessary Question: Is this system an NFS file server with disk quotas enabled? If the answer to this question is yes.new inetd.conf.conf.new mv inetd.

This functionality can either be controlled via the GUI administration tools provided with the operating system. administrators are strongly urged to leave these daemons disabled and administer volumes directly from the command line. proceed with the actions below. the GUI tools cannot function without several daemons enabled in inetd. \ s/^#100230/100230/.conf. 11 . Since the same functionality that is in the GUI is available from the command line interface. Question: Is the Solaris Volume Manager GUI administration tool required for the administration of this system? If the answer to this question is yes.2. However.conf Discussion: The Solaris Volume Manager (formerly Solaris DiskSuite) provides software RAID capability for Solaris systems. \ s/^#100242/100242/" inetd.conf. Action: sed "s/^#100229/100229/.conf.9 Only enable Solaris Volume Manager daemons if absolutely necessary OS Revisions: This item only applies to Solaris 9 systems (or systems which have the Solaris Volume Manager or Solaris DiskSuite products installed).conf >inetd.new mv inetd. or via the command line.new inetd.

mit.conf Discussion: With the release of Solaris 8.conf file devoted to comments.conf >inetd.conf. Kerberos support has been added to Solaris. Question: Is the Kerberos security system in use at this site? If the answer to this question is yes. Note that the original inetd. s/^#100234/100234/' \ inetd.conf file to only the "active" service entries. However.conf file Action: mv inetd.2. they can 12 . it can be very difficult to see when new services have been added to the file.complete. By reducing the inetd.new mv inetd.conf. 2. automated exploit scripts have been known to automatically re-enable inetd-based services by removing the comment character from disabled entries. Should the administrator wish to enable additional services in the future. For more information on Kerberos see http://web.conf chown root:sys inetd.conf Discussion: With so much of the stock inetd.new inetd. Kerberos may not be in use at all sites.conf. Action: sed 's/^#kerbd/kerbd/.complete grep –v '^#' inetd. Also.conf.10 Only enable Kerberos-related daemons if absolutely necessary OS Revisions: This item only applies to Solaris 2.conf chmod 444 inetd.conf. s/^#100134/100134/.edu/kerberos/www/.complete >inetd.conf file is saved as inetd. we thwart these exploit scripts and make it much easier for administrators to audit the file for new service entries that may have been added. proceed with the actions below.11 Minimize inetd.conf inetd.6 and later systems.

d/umask.conf. 3./init. Note that this action may safely be performed even if console access to the system is provided via the serial ports.complete file and then re-run the grep command line given above. Action (Solaris 7 and earlier): echo "umask 022" >/etc/init..new mv inittab. because the login: prompt on the console device is provided through a different mechanism.2 Set daemon umask Action (Solaris 8 and later): The CMASK parameter in /etc/default/init should be at least 022 (note that this is the default setting for Solaris 8 and later). 13 .simply edit the inetd. More restrictive umask values (such as 077) can be used but may cause problems for certain applications—consult vendor documentation for further information.new inittab chown root:sys inittab chmod 644 inittab Discussion: By disabling the login: prompt on the system serial devices we make it more difficult for unauthorized users to attach modems.sh $dir/S00umask.d do ln -s .d/umask. and other remote access devices to these ports.sh done Discussion: The system default umask should be set to at least 022 in order to prevent daemon processes from creating world-writable files by default.d/umask. 3 Minimize boot services 3. terminals.sh chmod 744 /etc/init.1 Disable login: prompts on serial ports Action: cd /etc grep -v /usr/lib/saf/sac inittab >inittab.sh for dir in /etc/rc?.

Note that running PortSentry may result in the CIS testing tools reporting "false positives" for "active" ports that are actually being held by the PortSentry daemon.com/products/portsentry.3 Turn on inetd tracing.psionic.notice to some other log file destination.conf.conf 2>/dev/null | \ wc -l | sed 's/ //g'` if [ "$lines" != "0" ].d/newinetsvc /etc/rc2. disable inetd if possible Action: cd /etc/init. This information is logged via Syslog and by default Solaris systems deposit this logging information in /var/adm/messages with other system log messages. then /usr/sbin/inetd -s -t & fi EONewInetd chown root:sys newinetsvc chmod 744 newinetsvc rm -f /etc/rc2.d grep -v /usr/sbin/inetd inetsvc >newinetsvc cat <<'EONewInetd' >>newinetsvc lines=`grep -v '^#' /etc/inet/inetd.d/S72inetsvc ln -s /etc/init.html) can be used to monitor access attempts on unused ports.conf to log daemon. If inetd is running. then the revised boot script created here will prevent the inetd daemon from even being started.d/S72inetsvc Discussion: If the actions in Section 2 of this benchmark resulted in no services being enabled in /etc/inet/inetd. In addition to the information provided by inetd tracing. the popular free PortSentry tool (http://www. 14 . Should the administrator wish to capture this information in a separate file. simply modify /etc/syslog. it is a good idea to make use of the "tracing" (-t) feature of the Solaris inetd that logs information about the source of any network connections seen by the daemon.3.

d/newsyslog rm -f /etc/rc2. Question: Is this machine a log server. 15 .d/S74syslog Discussion: By default the system logging daemon. then do not perform the action below.d/syslog >/etc/init. or does it need to receive Syslog messages via the network from other systems? If the answer to this question is yes. listens for log messages from other systems on network port 514/udp. However. so a malicious outsider could simply barrage the local system's Syslog port with spurious traffic—either as a denialof-service attack on the system. \ { print }' /etc/init. syslogd.d/S74syslog ln -s /etc/init. unless a system is set up to be one of these "log server" systems. Note that it is considered good practice to set up one or more machines as central "log servers" to aggregate log traffic from all machines at a site. or to fill up the local system's logging file systems so that subsequent attacks will not be logged.3.4 Prevent Syslog from accepting messages from network OS Revisions: This item only applies to Solaris 8 and later systems. Unfortunately.d/newsyslog /etc/rc2.d/newsyslog chown root:sys /etc/init. the protocol used to transfer these messages does not include any form of authentication.d/newsyslog chmod 744 /etc/init. it should not be listening on 514/udp for incoming log messages. Action: awk '$1 ~ /syslogd/ && !/-(t|T)/ { $1 = $1 " -t" }.

does this machine receive and process email from other hosts? If the answer to this question is yes. if possible Question: Is this system a mail server—that is.5 Disable email server.d/S88sendmail /etc/rc2.pdf and at http://www. 16 . Find the line that reads “D{MTAHost}localhost” and change localhost to the name of some other local mail server for the organization.tmp echo '0 * * * * /usr/lib/sendmail -q' >>root.org/. receiving and processing email from other hosts on the network.12 or later) it is also necessary to modify the /etc/mail/submit.NOS88sendmail cd /var/spool/cron/crontabs crontab -l >root. then do not perform the action below.tmp crontab root.3.sendmail. Note that if the system is an email server. Some information is available at http://www.tmp Discussion: It is possible to run a Unix system with the Sendmail daemon disabled and still allow users on that system to send email out from that machine.deer-run. the administrator is encouraged to search the Web for additional documentation on Sendmail security issues. Running Sendmail in "daemon mode" (with the –bd command-line option) is only required on machines that act as mail servers. Action (Solaris 8 and later): cd /etc/default cat <<END_DEFAULT >sendmail MODE= QUEUEINTERVAL="15m" END_DEFAULT chown root:sys sendmail chmod 744 sendmail Action (Solaris 7 and earlier): mv /etc/rc2.tmp rm -f root.com/~hal/dns-sendmail/DNSandSendmail. This will cause email generated on the local system to be relayed to that mail server for further processing and delivery. Note that after disabling the –bd option on the local mail server on Solaris 9 (or any system running Sendmail v8.cf file.d/.

d/newnfs.server rm –f /etc/rc3.server Action (Solaris 8 and earlier): cd /etc/init.bootparamd should only be enabled if the machine is actually going to be acting as a boot server.d/. in.d/S15nfs.3.d/S16boot. Action (Solaris 9): mv /etc/rc3.") next } { print }' nfs.. the in./ { if ($1 != ".rarpd and rpc.. many sites use TFTP to back up configuration files from their network routers).server /etc/rc3.server /etc/rc3. the system may be running TFTP and have a /tftpboot directory but not be acting as a boot server (for example.d/S15nfs.5 above). These services are designed to assist machines and devices that need to download their boot images over the network from some central server.rarpd and rpc.server chown root:sys newnfs.server Discussion: If the /tftpboot directory exists (see Item 2.6 Disable boot services if possible Question: Is this machine a network boot server or Jumpstart server? If the answer to this question is yes.bootparamd services will be enabled.server ln –s /etc/init. However.NOS16boot. 17 .server >newnfs./.server chmod 744 newnfs.d awk '/tftpboot/. then do not perform the action below.

The rest of the actions in this section give the administrator the option of re-enabling certain services—in particular. The scripts are merely renamed (rather than removed outright) so that the local administrator can easily "restore" any of these files if they discover a mission-critical need for one of these services.d for file in S77dmi S80mipagent.d directories—it is always a good idea to check these boot directories and remove any scripts that may have been added by the patch installation process.daemon S93cacheos.client S80lp S80spc S92volmgt \ S91afbinit S91ifbinit S99dtlogin S42ncakmod.NO$file done cd /etc/rc3.server S13kdc. 18 . the services that are disabled in the last two loops in the "Action" section above. others only exist if certain OEM vendor software is installed).3.d for file in S72autoinstall S85power S89bdconfig \ S73cachefs.NO$file done cd /etc/rc2. do [ -s $file ] && mv $file . Note also that vendor patches may restore some of the original entries in the /etc/rc*. do [ -s $file ] && mv $file .NO$file done cd /etc/rc3.d for file in S73nfs.finish S40llc2 S47pppd \ S47asppp S70uucp S72slpd S75flashprom S80PRESERVE \ S89PRESERVE S90wbem S94ncalogd S95ncad.NO$file done Discussion: Renaming these scripts in the system boot directories will effectively disable a wide variety of infrequently used subsystems.d for file in S90samba S15nfs.7 Disable other standard boot services Action: cd /etc/rc2. Not all of the scripts listed above will exist on all systems (some are only valid for certain releases. do [ -s $file ] && mv $file . experienced administrators may wish to simply disable only those services that they know are unnecessary for their systems. do [ -s $file ] && mv $file .client S74autofs S71rpc \ S72directory S71ldap. Rather than disabling and then re-enabling these services.master S14kdc \ S50apache S76snmpdx S34dhcp.

server /etc/rc3.NOS15nfs. the service should be disabled. file sharing. proceed with the actions below. if this functionality is not required by the site.d/. Action: mv /etc/rc3.NOS90samba /etc/rc3. If the system is an NFS server. For more information consult the share_nfs manual page. 3. Question: Does this machine provide authentication. 19 . Clearly there is no need to run the NFS server-related daemons on hosts that are not NFS servers.d/. However.9 Only enable NFS server processes if absolutely necessary Question: Is this machine an NFS file server? If the answer to this question is yes.d/S15nfs.d/S90samba Discussion: Solaris 9 now includes the popular Open Source Samba server for providing file and print services to Windows-based systems. or printer sharing services to systems running Microsoft Windows operating systems? If the answer to this question is yes. This allows a Solaris system to act as a file or print server on a Windows network. and even act as a Domain Controller (authentication server) to older Windows operating systems.server Discussion: NFS is frequently exploited to gain unauthorized access to files and systems.8 Only enable Windows-compatibility servers if absolutely necessary OS Revisions: This item only applies to Solaris 9 systems. Action: mv /etc/rc3. the admin should take reasonable precautions when exporting file systems. including restricting NFS access to a specific range of local IP addresses and exporting file systems "read-only" and "nosuid" where appropriate. proceed with the actions below.3.

Veritas. proceed with the actions below. Solaris DiskSuite) If the answer to this question is yes.client /etc/rc2. Unless one of the services listed above is required on this machine. Action: mv /etc/rc2.d/.d/S74autofs Discussion: Again. 3. Note that other file transfer schemes (such as rdist via SSH) can often be preferable to NFS for certain applications. best to disable RPC-based tools completely.3.NOS71rpc /etc/rc2. consult with the application vendor.d/S71rpc Discussion: RPC-based services typically use very weak or non-existent authentication and yet may share very sensitive information.d/.d/S73nfs.NOS73nfs. administrators should disable NFS-related services. proceed with the actions below.11 Only enable other RPC-based services if absolutely necessary Question: Are any of the following statements true? • This machine is an NFS client or server • This machine is an NIS (YP) or NIS+ client or server • The Kerberos security system is in use at this site • This machine runs a GUI or GUI-based administration tool • This machine is a network boot server or Jumpstart server • The machine runs a third-party software application which is dependent on RPC support (examples: FlexLM License managers.client mv /etc/rc2. unless there is a significant need for this system to acquire data via NFS.NOS74autofs /etc/rc2. Action: mv /etc/rc2.d/. 20 .10 Only enable NFS client processes if absolutely necessary Question: Is there a mission-critical reason why this system must access file systems from remote servers via NFS? If the answer to this question is yes. If you are unsure whether or not a particular third-party application requires RPC services.

NOS72directory /etc/rc2.NOS14kdc /etc/rc3.master mv /etc/rc3. proceed with the actions below.d/. the Kerberos server daemons have been bundled with the core operating system. 21 . there is no reason to enable this service.13 Only enable directory server if absolutely necessary OS Revisions: This item only applies to Solaris 9 systems.NOS13kdc. Question: Is this system an LDAP directory server for this site? If the answer to this question is yes. this service only needs to be running on the machines that have been designated as LDAP servers for the organization. Action: mv /etc/rc3.master /etc/rc3.12 Only enable Kerberos server daemons if absolutely necessary OS Revisions: This item only applies to Solaris 9 systems. proceed with the actions below. In particular. Question: Is this system a Kerberos Key Distribution Center (KDC) for the site? If the answer to this question is yes.d/S72directory Discussion: Solaris 9 has included the iPlanet Directory Server product as part of the operating system. the administrator is encouraged to search the Web for additional documentation on LDAP security issues.d/.3. However.d/S14kdc Discussion: Solaris 9 includes greater support for the Kerberos authentication system.d/. If the machine is an LDAP server. Action: mv /etc/rc2. However. 3. if the site is not using Kerberos or if this machine is not configured as one of the site's Kerberos servers.d/S13kdc.

3. proceed with the actions below.3.14 Only enable the LDAP cache manager if absolutely necessary OS Revisions: This item only applies to Solaris 8 and later systems. Action: mv /etc/rc2. then there is no need to keep LDAP-related daemons running on the local machine. and is this machine an LDAP client? If the answer to this question is yes. 22 .d/S80lp mv /etc/rc2.d/S71ldap.NOS80lp /etc/rc2. proceed with the actions below.lprng.NOS71ldap.d/. The Unix print service has generally had a poor security record—be sure to keep up-to-date on vendor patches.NOS80spc /etc/rc2. Action: mv /etc/rc2.d/.15 Only enable the printer daemons if absolutely necessary Question: Is this system a print server. if the local site is not currently using LDAP as a naming service. then it is safe to disable these services.org/) which was designed with security in mind and is widely portable across many different Unix platforms. The administrator may wish to consider converting to the LPRng print system (see http://www.client Discussion: Clearly. or is there a mission-critical reason why users must submit print jobs from this system? If the answer to this question is yes.d/.client /etc/rc2. Question: Is the LDAP directory service in use at this site.d/S80spc Discussion: If users will never print files from this machine and the system will never be used as a print server by other hosts on the network.

d/. Action: mv /etc/rc2.NOS91afbinit /etc/rc2.16 Only enable the volume manager if absolutely necessary Question: Is there a mission-critical reason why CD-ROMs and floppy disks should be automatically mounted when inserted into system drives?? If the answer to this question is yes.d/.d/S99dtlogin mv /etc/rc2.d/.NOS99dtlogin /etc/rc2. 3.17 Only enable GUI login if absolutely necessary OS Revisions: This item only applies to Solaris 2.d/S91ifbinit Discussion: The X Windows-based CDE GUI on Solaris systems has had a history of security issues.d/S92volmgt Discussion: The Solaris volume manager automatically mounts CD-ROMs and floppy disks for users whenever a disk is inserted in the local system's drive (the mount command is normally a privileged command which can only be performed by the superuser). Action: mv /etc/rc2. Be aware that allowing users to mount and access data from removable media drives makes it easier for malicious programs and data to be imported onto your network. Question: Is there a mission-critical reason to run a GUI on this system? If the answer to this question is yes. Note that the S91afbinit and S91ifbinit scripts enable support for high-end frame buffer devices—these will not be required if this system is not running a GUI.6 and later releases.NOS91ifbinit /etc/rc2.NOS92volmgt /etc/rc2. proceed with the actions below.3.d/. 23 . Never run any GUI-oriented service or application on a system unless that machine is protected by a strong network security infrastructure. proceed with the actions below.d/S91afbinit mv /etc/rc2.

Question: Is there a mission-critical reason why this system must run a Web server? If the answer to this question is yes..6 and later systems.d/. On Solaris systems.0/misc/security_tips.org/docs-2.d/S42ncakmod Discussion: Even if this machine is a Web server.g.NOS76snmpdx /etc/rc3. A good starting point is http://httpd. HP OpenView.NOS42ncakmod /etc/rc2.19 Only enable SNMP if absolutely necessary OS Revisions: This item only applies to Solaris 2.html. MRTG.NOS50apache /etc/rc3.d/S76snmpdx Discussion: If you are using SNMP to monitor the hosts on your network. proceed with the actions below. the administrator is encouraged to search the Web for additional documentation on Web server security. Cricket) that relies on SNMP? If the answer to this question is yes. the local site may choose not to use the Web server provided with Solaris in favor of a locally developed and supported Web environment.apache. 3. this parameter can be changed by modifying the system-group-readcommunity parameter in /etc/snmp/conf/snmpd.d/S50apache mv /etc/rc2. Action: mv /etc/rc3. Question: Are hosts at this site remotely monitored by a tool (e.18 Only enable Web server if absolutely necessary OS Revisions: This item only applies to Solaris 8 and later systems.conf 24 . Action: mv /etc/rc3.d/. proceed with the actions below. experts recommend changing the default community string used to access data via SNMP. If the machine is a Web server.d/.3.

If you need to allow developers to obtain core files. However. 25 . investigate the coreadm utility.20 Only enable DHCP server if absolutely necessary OS Revisions: This item only applies to Solaris 9 systems.1 Disable core dumps Action: cat <<END_CFG >>/etc/system * Prevent core dumps set sys:coredumpsize = 0 END_CFG Discussion: Core dumps can consume large amounts of disk space and may contain sensitive data.d/. there is no need to be running this service. Question: Does this machine act as a DHCP server for the network? If the answer to this question is yes. if this system is not a DHCP server for the network. 4 Kernel Tuning 4. developers using this system may require core files in order to aid in debugging. Action: mv /etc/rc3.NOS34dhcp /etc/rc3.3.d/S34dhcp Discussion: DHCP is a popular protocol for dynamically assigning IP addresses and other network information to systems on the network (rather than having administrators manually manage this information on each host). which is available on Solaris 7 and 8 systems. proceed with the actions below. On the other hand.

26 . Many of the automated tools in use by system crackers exploit well-known buffer overflow problems in vendor-supplied and third-party software. Enabling stack protection prevents certain classes of buffer overflow attacks and is a significant security enhancement. Action: cat <<END_CFG >>/etc/system * Attempt to prevent and log stack-smashing attacks set noexec_user_stack = 1 set noexec_user_stack_log = 1 END_CFG Discussion: Buffer overflow exploits have been the basis for many of the recent highly publicized compromises and defacements of large numbers of Internet connected systems.3 Restrict NFS client requests to privileged ports Action: cat <<END_CFG >>/etc/system * Require NFS clients to use privileged ports set nfssrv:nfs_portmon = 1 END_CFG Discussion: Setting this parameter causes the NFS server process on the local system to ignore NFS client requests that do not originate from the privileged port range (ports less than 1024).2 Enable stack protection OS Revisions: The configuration steps below may only be applied on Solaris 2.6 and later systems.4. 4. This should not hinder normal NFS operations but may block some automated NFS attacks that are run by unprivileged users.

d/netconfig chmod 744 /etc/init.d/netconfig ln -s /etc/init.d/S69netconfig 27 .d/netconfig /etc/rc2.d/netconfig chmod 744 /etc/init.d/netconfig ln -s /etc/init.d/netconfig #!/sbin/sh ndd -set /dev/ip ip_forward_src_routed 0 ndd -set /dev/ip ip6_forward_src_routed 0 ndd -set /dev/tcp tcp_rev_src_routes 0 ndd -set /dev/ip ip_forward_directed_broadcasts 0 ndd -set /dev/tcp tcp_conn_req_max_q0 4096 ndd -set /dev/tcp tcp_ip_abort_cinterval 60000 ndd -set /dev/ip ip_respond_to_timestamp 0 ndd -set /dev/ip ip_respond_to_timestamp_broadcast 0 ndd -set /dev/ip ip_respond_to_address_mask_broadcast 0 ndd -set /dev/arp arp_cleanup_interval 60000 ndd -set /dev/ip ip_ire_arp_interval 60000 ndd -set /dev/ip ip_ignore_redirect 1 ndd -set /dev/ip ip6_ignore_redirect 1 END_SCRIPT chown root:root /etc/init.d/netconfig #!/sbin/sh ndd -set /dev/ip ip_forward_src_routed 0 ndd -set /dev/ip ip_forward_directed_broadcasts 0 ndd -set /dev/tcp tcp_conn_req_max_q0 4096 ndd -set /dev/tcp tcp_ip_abort_cinterval 60000 ndd -set /dev/ip ip_respond_to_timestamp 0 ndd -set /dev/ip ip_respond_to_timestamp_broadcast 0 ndd -set /dev/ip ip_respond_to_address_mask_broadcast 0 ndd -set /dev/arp arp_cleanup_interval 60000 ndd -set /dev/ip ip_ire_flush_interval 60000 ndd -set /dev/ip ip_ignore_redirect 1 END_SCRIPT chown root:root /etc/init.d/netconfig /etc/rc2.4.4 Network Parameter Modifications Action (for Solaris 8 and later): cat <<END_SCRIPT >/etc/init.d/S69netconfig Action (for Solaris 7 releases and earlier): cat <<END_SCRIPT >/etc/init.

sun.5 Additional network parameter modifications Question: Is this system going to be used as a firewall or gateway to pass network traffic between different networks? If the answer to this question is yes.pdf 4.com/software/solutions/blueprints/1200/netw ork-updt1. For a more complete discussion of these parameters and their effect on the security of the system. then do not perform the action below.d/netconfig ip_forwarding 0 ip6_forwarding 0 ip_strict_dst_multihoming 1 ip6_strict_dst_multihoming 1 ip_send_redirects 0 ip6_send_redirects 0 Action (for Solaris 7 and earlier): >>/etc/init.Discussion: Note that we are creating a new script that will be executed at boot time to reconfigure various network parameters. see: http://www.d/netconfig ip_forwarding 0 ip_strict_dst_multihoming 1 ip_send_redirects 0 Discussion: For a more complete discussion of these parameters and their effect on the security of the system. 28 . Action (for Solaris 8 and later): cat <<END_SCRIPT ndd -set /dev/ip ndd -set /dev/ip ndd -set /dev/ip ndd -set /dev/ip ndd -set /dev/ip ndd -set /dev/ip END_SCRIPT cat <<END_SCRIPT ndd -set /dev/ip ndd -set /dev/ip ndd -set /dev/ip END_SCRIPT >>/etc/init. see the URL noted in the previous item.

new inetinit chown root:sys inetinit chmod 444 inetinit Discussion: Setting this parameter in /etc/default/inetinit causes the system to use a better randomization algorithm for generating initial TCP sequence numbers. root 29 . More information on NTP can be found at http://www.1 Capture messages sent to syslog AUTH facility Action: echo "auth. successful and failed su attempts.pdf..6 Use better TCP sequence numbers OS Revisions: Required for Solaris 2.org and http://www. This makes remote session hijacking attacks more difficult.info\t\t\t/var/log/authlog" >>/etc/syslog. which is supported by most network-ready devices. a great deal of important security-related information is sent via this channel (e. Solaris systems do not capture logging information that is sent to the LOG_AUTH facility. Because it is often necessary to correlate log information from many different systems (particularly after a security incident) experts recommend establishing some form of time synchronization among systems and devices connected to the local network. as well as any other networkbased attack that relies on predicting TCP sequence number information.sun. not supported in earlier releases Action: cd /etc/default awk '/^TCP_STRONG_ISS/ { $1 = "TCP_STRONG_ISS=2" }.conf touch /var/log/authlog chown root:sys /var/log/authlog chmod 600 /var/log/authlog Discussion: By default. failed login attempts.4.g.com/solutions/blueprints/0701/NTP.6 and later. However. \ { print }' inetinit > inetinit.new mv inetinit. 5. The standard Internet protocol for time synchronization is the Network Time Protocol (NTP).ntp. 5 Logging The items in this section cover enabling various different forms of system logging in order to keep track of activity on the system.

A sample script for archiving log files is provided as Appendix A to this document. the file /var/adm/loginlog will capture failed login attempt messages (this file does not exist by default).conf touch /var/log/connlog chown root:root /var/log/connlog chmod 600 /var/log/connlog Discussion: If the FTP service is enabled on the system. 5.2 Capture FTP and inetd Connection Tracing Info Action: echo "daemon.login attempts. Solaris 9 systems include the logadm utility for archiving log files. administrators may also 30 .new mv login. Similarly. The above action causes this information to be captured in the /var/log/authlog file (which is only readable by the superuser).debug\t\t\t/var/log/connlog" \ >>/etc/syslog. Solaris 9 systems include the logadm utility for archiving log files. A sample script for archiving log files is provided as Appendix A to this document. \ { print }' login >login. etc.).3 also enables the "debugging" (-d) and connection logging (-l) flags to track FTP activity on the system. but the Syslog daemon must be configured to capture this information to a file. Item 2.3 Create /var/adm/loginlog Action: touch /var/adm/loginlog chown root:sys /var/adm/loginlog chmod 600 /var/adm/loginlog cd /etc/default awk '/SYSLOG_FAILED_LOGINS=/ \ { $1 = "SYSLOG_FAILED_LOGINS=0" }.3 above. the tracing (-t) option to inetd was enabled in Item 3. 5. Starting with Solaris 8. The connlog file should be reviewed and archived on a regular basis. All of this information is logged to Syslog.new login chown root:sys login chmod 444 login Discussion: If it exists. The authlog file should be reviewed and archived on a regular basis.

new mv cron.d/newperf rm -f /etc/rc2.d/S21perf ln -s /etc/init. 5.) every 20 minutes.40 * * * * /usr/lib/sa/sa1 45 23 * * * /usr/lib/sa/sa2 -s 0:00 -e 23:59 -i 1200 -A END_ENTRIES Discussion: System accounting gathers baseline system data (CPU utilization.d/S21perf /usr/bin/su sys -c crontab <<END_ENTRIES 0. Log data can be found in /var/cron/log and this file should be reviewed on a regular basis.d/newperf /etc/rc2. Once a normal baseline for the 31 .d/newperf #!/sbin/sh /usr/bin/su sys -c \ "/usr/lib/sa/sadc /var/adm/sa/sa\`date +%d\`" END_SCRIPT chown root:sys /etc/init.d/newperf chmod 744 /etc/init.4 Turn on cron logging Action: cd /etc/default awk '/CRONLOG/ { $1 = "CRONLOG=YES" }.new cron chown root:sys cron chmod 444 cron Discussion: Setting the CRONLOG parameter to YES in /etc/default/cron causes information to be logged for every cron job that gets executed on the system.modify the SYSLOG_FAILED_LOGINS parameter in /etc/default/login to control how many login failures are allowed before log messages are generated—if set to zero then all failed logins will be logged. 5. disk I/O. The loginlog file should be reviewed and archived on a regular basis.20. A sample script for archiving log files is provided as Appendix A to this document. or by reviewing the nightly report files named /var/adm/sa/sar*. \ { print }' cron > cron. The data may be accessed with the sar command. Solaris 9 systems include the logadm utility for archiving log files.5 Enable system accounting Action: cat <<END_SCRIPT >/etc/init. etc.

arge' \ >>audit_startup.new mv audit_startup.fm.nt minfree:20 END_PARAMS echo root:lo.tmp crontab root.ex.-fw. The audit trail may be reviewed with the praudit command.-fd" and "naflags:lo.ad. A less aggressive audit policy could be used by setting "flags:lo.ad:no >audit_user awk '/^auditconfig/ { $1 = "/usr/sbin/auditconfig" }. \ { print }' audit_startup >audit_startup.-fd. unauthorized activity (password crackers and other CPUintensive jobs. The 32 . Note that enabling kernel-level auditing on Solaris disables the automatic mounting of CD-ROMs and floppy disks via the Solaris volume manager daemon (vold).ad.-fc.6 Enable kernel-level auditing Action: echo y | /etc/security/bsmconv cd /etc/security cat <<END_PARAMS >audit_control dir:/var/audit flags:lo.tmp rm -f root.-fm.-fc.-fw. Sites may wish to consider logging less information to help reduce the amount of disk space and other system resources consumed by the auditing process. Note that this data is only archived for one week before being automatically removed by the regular nightly cron job.ad.ad.tmp echo '0 * * * * /usr/sbin/audit -n' >>root. Kernel-level auditing can consume large amounts of disk space and even cause a system performance impact.-fw. and activity outside of normal usage hours) may be detected due to departures from the normal system performance curve.-fd.system has been established.new audit_startup chmod 744 audit_startup chown root:sys audit_startup cd /var/spool/cron/crontabs crontab -l >root.na naflags:lo. particularly on heavily used machines.nt" instead of the values shown above.ex.-fc.fm.tmp Discussion: Kernel-level auditing provides information on commands and system calls which are executed on the local system. 5. Administrators may wish to archive the /var/adm/sa directory on a regular basis to preserve this data for longer periods.new echo '/usr/sbin/auditconfig -setpolicy +argv.

Note that sites using the runacct script for generating billing reports and other data from the system process accounting logs will notice that the script incorrectly sets the mode on the wtmpx file to 664 (adds the "group writability" bit). Also. The local site may wish to "chmod g-w /var/adm/wtmpx" after running the runacct script. certain logs contain sensitive data that should only be available to the system administrator. 5. 33 .<Stop>-A keyboard abort sequence is also disabled via an entry in the /etc/system file.7 Confirm permissions on system log files Action: chown root:sys /var/log/syslog /var/log/authlog \ /var/adm/loginlog chown root:root /var/cron/log /var/adm/messages chmod go-wx /var/log/syslog /var/adm/messages chmod go-rwx /var/log/authlog /var/adm/loginlog \ /var/cron/log cd /var/adm chown root:bin utmpx chown adm:adm wtmpx chmod 644 utmpx wtmpx chown sys:sys /var/adm/sa/* chmod go-wx /var/adm/sa/* dir=`awk -F: '($1 == "dir") { print $2 }' \ /etc/security/audit_control` chown root:root $dir/* chmod go-rwx $dir/* Discussion: It's critical to protect system log files from being modified by unauthorized individuals.

but must reboot the system to return the file system to read-only mode). the "nosuid" flag cannot be applied to the root file system. } ($3 != "/") { $7 = "nosuid".tripwire. it may be possible to mount these file systems read-only as well. 34 . Since all of the standard set-UID utilities. If a file system is mounted "nosuid" then the set-UID bit on executables in that file system is ignored—these programs will execute with the privileges of the user running the program.tripwire. Other file systems that must be configured to allow writing should be mounted "nosuid" where possible in order to prevent the introduction of rogue set-UID programs. experts recommend using a file system integrity checking tool such as Tripwire™.org/ for information on obtaining free versions of this software). rather than the privileges of the owner of the binary. If /opt and /usr/local (or other directories containing third-party software applications) are configured as distinct partitions on a given system.com/products/tripwire_asr/ and http://www. are provided under the /usr file system. which means that device files cannot operate in a "nosuid" file system. } ($3 == "/usr" || $3 == "/opt" || $3 == "/usr/local")\ { $7 = "ro". Under Solaris.new vfstab chown root:sys vfstab chmod 664 vfstab Discussion: It is important to protect the system from the introduction of unauthorized software.rw /usr command. next. print.6 File/Directory Permissions/Access 6. The root file system is the home of the /devices hierarchy where the standard system device files live. which is available in both free and commercial versions (see http://www.1 File systems are mounted either 'ro' or 'nosuid' Action: cd /etc awk '($4 != "ufs" || $3 == "/") { print. "nosuid" implies "nodev". Unfortunately. }' \ vfstab >vfstab.new mv vfstab. Beyond simple file system level protections. particularly set-UID programs. next. we mount this partition read-only ("ro") to help prevent tampering (administrators may make the file system read-write with the mount –o remount. print. as well as other critical operating system tools.

By forcing these file systems to be mounted with the "nosuid" option.new mv /etc/vfstab.6. the administrator prevents users from bringing set-UID programs onto the system via CDROMs and floppy disks.conf OS Revisions: This action does not usually need to be performed on Solaris 8 and later systems. 35 .conf` echo mount \* $fs -o nosuid >>/etc/rmmount. Note that the administrator may also wish to add the "logging" option to other ufs type file systems in /etc/vfstab. thwarting this particular type of attack. Action: fs=`awk '($1 == "ident") && ($2 != "pcfs") \ { print $2 }' /etc/rmmount.logging" }.3 Add 'nosuid' option to /etc/rmmount. \ { print }' /etc/vfstab >/etc/vfstab.conf Discussion: Removable media is one vector by which malicious software can be introduced onto the system.2 Add 'logging' option to root file system OS Revisions: This step may only be performed on Solaris 8 and later systems Action: awk '($4 == "ufs" && $3 == "/") \ { $7 = "remount. This will help the system to reboot faster in the event of a crash at the cost of some disk overhead (up to a maximum of 64MB per partition) for the file system transaction log file. it is much more difficult for the root file system to become corrupted at all.new /etc/vfstab chown root:sys /etc/vfstab chmod 664 /etc/vfstab Discussion: A corrupted root file system is one mechanism that an attacker with physical access to the system console can use to compromise the system. 6. as it is the default configuration for these platforms. By enabling the "logging" option on the root file system.

5 Verify passwd.new dfstab chmod 644 dfstab chown root:sys dfstab Discussion: The commands in the dfstab file are executed via the /usr/sbin/shareall script at boot time.4 Use full path names in /etc/dfs/dfstab file Action: cd /etc/dfs awk '($1 == "share") { $1 = "/usr/sbin/share" }. 6.new mv dfstab. Administrators who wish to obtain a list of these directories may execute the following commands for part in `awk '($4 == "ufs" || $4 == "tmpfs") \ { print $3 }' /etc/vfstab` do find $part -xdev -type d \ \( -perm -0002 -a ! -perm -1000 \) -print done 36 . shadow. It seems prudent to use the absolute pathname to the share command to protect against an exploits stemming from an attack on the administrator's PATH environment. etc.6 World-writable directories should have their sticky bit set Action: The automated tool supplied with this benchmark will flag world-writable directories that do not have the sticky bit set.6. \ { print }' dfstab >dfstab. and group file permissions Action: cd /etc chown root:sys passwd shadow group chmod 644 passwd group chmod 400 shadow Discussion: These are the default owners and access permissions for these files. 6. as well as by administrators executing the shareall command during the uptime of the machine.

6. then only the owner of a file may remove that file from the directory (as opposed to the usual behavior where anybody with write access to that directory may remove the file). and is generally appropriate for most world-writable directories.7 Find unauthorized world-writable files Action: The automated testing tool supplied with this benchmark will flag unexpected worldwritable files on the system. 37 . Administrators who wish to obtain a list of the world-writable files currently on the system may run the following commands: for part in `awk '($4 == "ufs" || $4 == "tmpfs") \ { print $3 }' /etc/vfstab` do find $part -xdev -type f -perm -0002 -print done Discussion: Data in world-writable files can be modified and compromised by any user on the system. consult appropriate vendor documentation before blindly applying the sticky bit to any world writable directories found in order to avoid breaking any application dependencies on a given directory. World writable files may also indicate an incorrectly written script or program that could potentially be the cause of a larger compromise to the system's integrity. Generally removing write access for the "other" category (chmod o-w <filename>) is advisable. Setting the sticky bit prevents users from overwriting each other's files. but always consult relevant vendor documentation in order to avoid breaking any application dependencies on a given file.Discussion: When the so-called "sticky bit" is set on a directory. However. whether accidentally or maliciously.

tar.9 Run fix-modes Action: 1.tar. Administrators may wish to run the tool periodically out of cron. Note that the actions below recommend using a pre-compiled version of fix-modes.Z | tar xf cd fix-modes . Unpack the software and run the fix-modes program zcat fix-modes.ca/security/howto/ 6.uva.6.CISecurity.tar. or patches are applied.science. 38 . This program should be re-run every time packages are added to the system.8 Find unauthorized SUID/SGID system executables Action: The automated testing tool supplied with this benchmark will flag unexpected set-UID and set-GID applications on the system. the source code is available from ftp://ftp.Z 2.nl/pub/solaris/fix-modes./fix-modes Discussion: The fix-modes software corrects various ownership and permission issues with files throughout the Solaris OS file systems. Information on the set-UID and set-GID applications that normally ship with Solaris systems can be found at http://ist. Administrators who wish to obtain a list of the set-UID and set-GID programs currently installed on the system may run the following commands: for part in `awk '($4 == "ufs" || $4 == "tmpfs") \ { print $3 }' /etc/vfstab` do find $part -xdev -type f \ \( -perm -04000 -o -perm -02000 \) -print done Discussion: The administrator should take care to ensure that no rogue set-UID programs have been introduced into the system.gz. Download the pre-compiled fix-modes software from ftp://ftp.org/pub/pkgs/Solaris/fix-modes. For sites that wish to build the tool themselves from source.uwaterloo.

conf OS Revisions: Required for Solaris 2. Disabling .1 Remove . In fact.rhosts support is required for some reason.rhosts entries should always specify a specific trusted host name along with the user name of the trusted account on that system (e.. .new mv pam. Authentication.conf chmod 644 pam.conf chown root:sys pam.new pam. If .rhosts files.rhosts files implement a weak form of authentication based on the network address or host name of the remote computer (which can be spoofed by a potential attacker to exploit the local system). "trustedhost alice" and not just "trustedhost").shosts /etc/hosts. rcp). Firewalls and other network security elements should actually block rlogin/rsh/rcp access from external hosts.conf > pam. Avoid establishing trust relationships with systems outside of the organization's security perimeter and/or systems not controlled by the local administrative staff.conf. 7.7 System Access. make sure that .conf..rhosts support in /etc/pam.equiv do rm -f $file ln -s /dev/null $file done 39 . Finally. some basic precautions should be taken when creating and managing .e.rhosts /.rhosts files.2 Create symlinks for dangerous files Action: for file in /. rsh. Never use the "+" wildcard character in . and Authorization 7.conf Discussion: Used in conjunction with the BSD-style “r-commands” (rlogin.rhosts support helps prevent users from subverting the system’s normal access control mechanisms. .g.6 and later. not supported in earlier releases Action: cd /etc grep -v rhosts_auth pam.rhosts files are only readable by the owner of the file (i. these files should be mode 600).

but the path name of the file has been changed to /etc/ftpd/ftpusers in this release. any data that an attacker writes to these files is simply discarded (though an astute attacker can still remove the link prior to writing their malicious data).rhosts. /. Action: for user in root daemon bin sys adm lp uucp nuucp \ smmsp listen nobody noaccess nobody4 do echo $user >>/etc/ftpusers done chown root:root /etc/ftpusers chmod 600 /etc/ftpusers Discussion: ftpusers contains a list of users who are not allowed to access the system via FTP.Discussion: The /.equiv files enable a weak form of access control (see the discussion of .shosts. Generally. Certainly the root account should never be allowed to transfer files directly via FTP.3 Create /etc[/ftpd]/ftpusers OS Revisions: Solaris 8 systems ship with this /etc/ftpusers file by default. By linking these files to /dev/null. Consider also adding the names of other privileged or shared accounts which may exist on your system such as user oracle and the account which your Web server process runs under. and /etc/hosts. only normal users should ever access the system via FTP—there should be no reason for “system” type accounts to be transferring information via this mechanism. 40 . 7. Solaris 9 systems also ship with this file. Attackers will often target these files as part of their exploit scripts.rhosts files in the item above).

7.4

Create /etc/shells

Action:
echo /sbin/sh >/etc/shells for shell in sh csh ksh bash tcsh zsh; do [ -f /bin/$shell ] && echo /bin/$shell >>/etc/shells [ -f /usr/bin/$shell ] && \ echo /usr/bin/$shell >>/etc/shells done chown root:root /etc/shells chmod 644 /etc/shells

Discussion:
/etc/shells contains a list of valid login shells for user account entries in /etc/passwd. If /etc/shells does not exist, then any program is valid as a user shell in /etc/passwd. It's best to restrict /etc/shells to a list of known good shell programs provided by Sun or installed locally by the System Administrator. Note that it may be necessary to add other locally-installed shells to the /etc/shells file (for example if bash is installed in /opt or /usr/local/bin), depending on the needs of a particular organization.

7.5

Prevent remote XDMCP access

OS Revisions:
This action is only required on Solaris 2.6 and later releases.

Action:
mkdir -p /etc/dt/config cat <<EOXaccess >/etc/dt/config/Xaccess !* !* CHOOSER BROADCAST EOXaccess

Discussion:
The standard GUI login provided on most Unix systems can act as a remote login server to other devices (including X terminals and other workstations). Access control is handled via the Xaccess file—by default under Solaris, this file allows any system on the network to get a remote login screen from the local system. We can override this behavior in the /etc/dt/config/Xaccess file.

41

7.6

Prevent X server from listening on port 6000/tcp

OS Revisions:
This action is only required on Solaris 9 systems.

Action:
if [ -f /etc/dt/config/Xservers ]; then file=/etc/dt/config/Xservers else file=/usr/dt/config/Xservers fi awk '/Xsun/ && !/^#/ \ { print $0 " -nolisten tcp"; next }; \ { print }' $file > $file.new cp $file.new /etc/dt/config/Xservers chown root:sys /etc/dt/config/Xservers chmod 444 /etc/dt/config/Xservers

Discussion:
X servers listen on port 6000/tcp for messages from remote clients running on other systems. However, X Windows uses a relatively insecure authentication protocol—an attacker who is able to gain unauthorized access to the local X server can easily compromise the system. Invoking the "-nolisten tcp" option causes the X server not to listen on port 6000/tcp by default. This does prevent authorized remote X clients from displaying windows on the local system as well. However, the forwarding of X events via SSH will still happen normally. This is the preferred and more secure method transmitting results from remote X clients in any event.

42

7.7

Set default locking screensaver timeout

OS Revisions:
This action is only required on Solaris 2.6 and later releases.

Action:
for file in /usr/dt/config/*/sys.resources; do dir=`dirname $file | sed s/usr/etc/` mkdir -p $dir echo 'dtsession*saverTimeout: 10' >>$dir/sys.resources echo 'dtsession*lockTimeout: 10' >>$dir/sys.resources done

Discussion:
The default timeout is 30 minutes of keyboard/mouse inactivity before a passwordprotected screen saver is invoked by the CDE session manager. The above action reduces this default timeout value to 10 minutes, though this setting can still be overridden by individual users in their own environment.

7.8

Restrict at/cron to authorized users

Action:
cd /etc/cron.d rm -f cron.deny at.deny echo root >cron.allow echo root >at.allow chown root:root cron.allow at.allow chmod 400 cron.allow at.allow

Discussion:
The cron.allow and at.allow files are a list of users who are allowed to run the crontab and at commands to submit jobs to be run at scheduled intervals. On many systems, only the system administrator needs the ability to schedule jobs. Note that even though a given user is not listed in cron.allow, cron jobs can still be run as that user (e.g., the cron jobs running as user sys for system accounting tasks—see Item 5.5 above). cron.allow only controls administrative access to the crontab command for scheduling and modifying cron jobs.

43

7. All activity may be \ monitored and reported.1): eeprom oem-banner="Authorized uses only." eeprom oem-banner\?=true echo "Authorized uses only. Allowing unprivileged users to read or (even worse) modify system crontab files can create the potential for a local user on the system to gain elevated privileges. All activity \ may be monitored and reported.9 Remove empty crontab files and restrict file permissions Action: cd /var/spool/cron/crontabs for file in * do lines=`grep -v '^#' $file | wc -l | sed 's/ //g'` if [ "$lines" = "0" ].7. All activity may be \ monitored and reported. then rm $file fi done chown root:sys * chmod 400 * Discussion: The system crontab files are accessed only by the cron daemon (which runs with superuser privileges) and the crontab command (which is set-UID to root)." >/etc/motd echo "Authorized uses only.10 Create appropriate warning banners Action (for Solaris 2.5." >/etc/issue chown root:sys /etc/motd chown root:root /etc/issue chmod 644 /etc/motd /etc/issue 44 .

and that use of the system implies consent to such monitoring.labelString: Authorized uses \ only."\ >>$dir/Xresources done chown root:sys /etc/motd /etc/dt/config/*/Xresources chown root:root /etc/issue chmod 644 /etc/motd /etc/issue /etc/dt/config/*/Xresources chown root:sys /etc/default/telnetd /etc/default/ftpd chmod 444 /etc/default/telnetd /etc/default/ftpd Discussion: Presenting some sort of statutory warning message at login time may assist the prosecution of trespassers on the computer system. then cp $file $dir/Xresources fi echo "Dtlogin*greeting. All activity \ may be monitored and reported. All activity may be \ monitored and reported.6 and later): eeprom oem-banner="Authorized uses only." >issue echo "BANNER=\"Authorized uses only." eeprom oem-banner\?=true cd /etc echo "Authorized uses only." >motd echo "Authorized uses only. Changing some of these login banners also has the side effect of hiding OS version information and other detailed system information from attackers attempting to target specific attacks at a system. Clearly. All activity may be monitored and reported. All activity may \ be monitored and reported." \ >>$dir/Xresources echo "Dtlogin*greeting. Guidelines published by the US Department of Defense require that warning messages include at least the name of the organization that owns the system. 45 . the organization’s local legal counsel and/or site security administrator should review the content of all messages before the above modifications are made.\\\n\\\n\"" >default/telnetd echo "BANNER=\"Authorized uses only.\"" >default/ftpd for file in /usr/dt/config/*/Xresources do dir=`dirname $file | sed s/usr/etc/` mkdir -p $dir if [ ! -f $dir/Xresources ]. All activity may be \ monitored and reported.Action (for Solaris 2.persLabelString: Authorized \ uses only. All activity may \ be monitored and reported. the fact that the system is subject to monitoring and that such monitoring is in compliance with local statutes. All activity may be monitored and reported.

11 Restrict root logins to system console Action: cd /etc/default awk '/CONSOLE=/ { print "CONSOLE=/dev/console".new mv login.org as well as www. These mechanisms provide at least some limited audit trail in the event of problems. or the freely-available sudo package) to gain additional privilege.sunfreeware.com) contains shell commands to help produce properly formatted banner messages. 46 .Makefile file provided with the TCP Wrappers source distribution (available from ftp.new login chown root:sys login chmod 444 login Discussion: Anonymous root logins should never be allowed. \ { print }' login >login. then awk '/RETRIES=/ { $1 = "RETRIES=3" } { print }' login >login. next }. The Banners. 7.Note that if TCP Wrappers are being used to display warning banners for various inetd-based services.12 Limit number of failed login attempts Action: cd /etc/default if [ "`grep RETRIES= login`" ]. the administrator should access the system via an unprivileged account and use some authorized mechanism (such as the su command. it is important that the banner messages be formatted properly so as not to interfere with the application protocol. Setting this number to a reasonably low value helps discourage brute force password guessing attacks.porcupine. 7. At all other times. except on the system console in emergency situations.new mv login.new login chown root:sys login chmod 444 login else echo RETRIES=3 >>login fi Discussion: The RETRIES parameter is the number of failed login attempts a user is allowed before being disconnected from the system and having to re-initiate their login session.

tmp rm -f root. the administrator will be prompted for a password. Action: eeprom security-#badlogins=0 cd /var/spool/cron/crontabs crontab -l >root.e.7.13 Set EEPROM security-mode and log failed access Hardware Compatibility: This action only applies to SPARC-based systems (not Solaris x86 or Solaris PPC).8..tmp echo "0 0.tmp crontab root.tmp eeprom security-mode=command Discussion: After entering the last command above. 47 .info \ \`/usr/sbin/eeprom security-#badlogins\`" >>root. If the password is lost or forgotten.16 * * * /usr/bin/logger -p auth. This helps prevent attackers with physical access to the system console from booting off some external device (such as a CD-ROM or floppy) and subverting the security of the system. simply run the command "eeprom security-mode=none" as root to erase the forgotten password. Note that the administrator should write down this password and place the password in a sealed envelope in a secure location (note that locked desk drawers are typically not secure). the system will be able to reboot unattended). and then set a new password with "eeprom security-mode=command". This password will be required to authorize any future command issued at boot-level on the system (the ‘ok’ or ‘>’ prompt) except for the normal multi-user boot command (i.

/dev/null is a good choice because it is not a valid login shell.CISecurity. ongoing basis—perhaps in an automated fashion via cron. 8. 8. do passwd -l $user /usr/sbin/passmgmt -m -s /dev/null $user done Discussion: Accounts that are not being used by regular users should be locked. but also the shell field in the password file should contain an invalid shell. and should an attacker attempt to replace it with a copy of a valid shell the system will not operate properly.8 User Accounts and Environment Note that the items in this section are tasks that the local administrator should undertake on a regular.org/. The automated hostbased scanning tools provided from the Center for Internet Security can be used for this purpose.1 Block system accounts Action: passwd -l sys passwd –l daemon for user in adm bin lp smmsp nobody noaccess \ uucp nuucp smtp listen nobody4. These scanning tools are typically provided with this document. Not only should the password field for the account be set to an invalid string. 48 . Discussion: An account with an empty password field means that anybody may log in as that user without providing a password at all. but are also available for free download from http://www. All accounts should have strong passwords or should be locked by using a password string like "NP" or "*LOCKED*".2 Verify that there are no accounts with empty password fields Action: The command logins -p should return no lines of output.

and then prevent password changes for seven days (one week) thereafter. Note that due to the fact that /etc/default/passwd sets defaults in terms of number of weeks (even though the actual values on user accounts are kept in terms of days).8. The commands above will set all active accounts (except the root account) to force password changes every 91 days (13 weeks). it is probably best to choose interval values that are multiples of 7. 49 . particularly the –f option). Users will begin receiving warnings 28 days (4 weeks) before their password expires. These are recommended starting values.3 Set account expiration parameters on active accounts Action: logins -ox |awk -F: '($1 == "root" || $8 == "LK") { next } { $cmd = "passwd" } ($11 <= 0 || $11 > 91) { $cmd = $cmd " -x 91" } ($10 < 7) { $cmd = $cmd " -n 7" } ($12 < 28) { $cmd = $cmd " -w 28" } ($cmd != "passwd") { print $cmd " " $1 }' \ > /etc/CISupd_accounts /sbin/sh /etc/CISupd_accounts rm -f /etc/CISupd_accounts cat <<EO_DefPass >/etc/default/passwd MAXWEEKS=13 MINWEEKS=1 WARNWEEKS=4 PASSLENGTH=6 EO_DefPass Discussion: It is a good idea to force users to change passwords on a regular basis. Sites also have the option of expiring idle accounts after a certain number of days (see the on-line manual page for the usermod command. but sites may choose to make them more restrictive depending on local policies.

and group files Action: The command grep '^+:' /etc/passwd /etc/shadow /etc/group should return no lines of output. and it should be accessed by logging in as an unprivileged user and using the su command to gain additional privilege. For more information on Solaris RBAC. The only superuser account on the machine should be the root account. shadow. Finer granularity access control for administrative access can be obtained by using the freely-available sudo program (http://www. These entries may provide an avenue for attackers to gain privileged access on the system.sun.8. and should be deleted if they exist. Discussion: Any account with UID 0 has superuser privileges on the system. 8.com/sudo/) or Sun's own Role-Based Access Control (RBAC) system.4 Verify no legacy '+' entries exist in passwd.com/software/whitepapers/wp-rbac/.5 Verify that no UID 0 accounts exist other than root Action: The command logins -o | awk -F: '($2 == 0) { print $1 }' should return only the word “root”.courtesan. but may exist in files that have been imported from other platforms. 50 . Discussion: '+' entries in various files used to be markers for systems to insert data from NIS maps at a certain point in a system configuration file. see http://wwws. These entries are no longer required on Solaris systems.

51 .') or other writable directory in root's executable path makes it likely that an attacker can gain superuser access by forcing an administrator operating as root to execute a Trojan horse program.6 No '. 8.' or group/world-writable directory in root $PATH Action: The automated testing tool supplied with this benchmark will alert the administrator if action is required.8. making global modifications to user home directories without alerting your user community can result in unexpected outages and unhappy users. Discussion: Including the current working directory ('. Disabling "read" and "execute" access for users who are not members of the same group (the "other" access category) allows for appropriate use of discretionary access control by each user.7 User home directories should be mode 750 or more restrictive Action: for dir in `logins -ox | \ awk -F: '($8 == "PS" && $1 != "root") { print $6 }'` do chmod g-w $dir chmod o-rwx $dir done Discussion: Group or world-writable user home directories may enable malicious users to steal or modify other users' data or to gain another user's system privileges. While the above modifications are relatively benign.

then chmod go-w "$file" fi done done Discussion: Group or world-writable user configuration files may enable malicious users to steal or modify other users' data or to gain another user's system privileges.8.netrc files Action: for dir in `logins -ox | \ awk -F: '($8 == "PS") { print $6 }'` do rm -f $dir/.netrc files may contain unencrypted passwords which may be used to attack other systems. making global modifications to user home directories without alerting your user community can result in unexpected outages and unhappy users. While the above modifications are relatively benign. 52 . 8. making global modifications to user home directories without alerting your user community can result in unexpected outages and unhappy users.[A-Za-z0-9]*.8 No user dot-files should be group/world writable Action: for dir in `logins -ox | \ awk -F: '($8 == "PS") { print $6 }'` do for file in $dir/.netrc done Discussion: . do if [ ! -h "$file" -a -f "$file" ]. While the above modifications are relatively benign.9 Remove user .

8. The user creating the file has the discretion of making their files and directories readable by others via the chmod command. the incremental security increase is worth the loss of functionality.10 Set default umask for users Action: cd /etc/default awk '/UMASK=/ { $1 = "UMASK=077" }. . but has the side effect of slightly strengthening permissions on the user's tty device. 53 . files and directories created by users will not be readable by any other user on the system. Since write and talk are no longer widely used at most sites. while a umask of 022 would make files readable by every user on the system.cshrc.11 Set "mesg n" as default for all users Action: echo mesg n >>/etc/profile echo mesg n >>/etc/. A umask of 027 would make files and directories readable by users in the same Unix group.login Discussion: "mesg n" blocks attempts to use the write or talk commands to contact the user at their terminal.profile.login Discussion: With a default umask setting of 077. etc.) in their home directories.new mv login. 8.new login chown root:sys login chmod 444 login echo UMASK=077 >>ftpd echo umask 077 >>/etc/profile echo umask 077 >>/etc/. \ { print }' login >login. Users who wish to allow their files and directories to be readable by others by default may choose a different default umask by inserting the umask command into the standard shell configuration files (.

then echo "$DIR: Path does not exist" exit 255 fi cd $DIR while [ $DEPTH -gt 0 ] do OLD=$(($DEPTH .1)) if [ -f $LOG.1)) if [ ! -d $DIR ].$OLD $LOG.A script to roll over log files # Usage: rotate /path/to/log/file [mode [#revs] ] FILE=$1 MODE=${2:-644} DEPTH=${3:-4} DIR=`dirname $FILE` LOG=`basename $FILE` DEPTH=$(($DEPTH . then mv $LOG $LOG.$OLD ].$DEPTH fi DEPTH=$OLD done if [ $DEPTH -eq 0 -a -f $LOG ]. then mv $LOG.d/syslog start 54 .0 fi cp /dev/null $LOG chmod $MODE $LOG /etc/init.Appendix A: Log Rotation Script #!/bin/ksh # rotate -.d/syslog stop /etc/init.

org/ Information on MIT Kerberos – http://web.com/solutions/blueprints/0701/NTP.org/docs-2.html Information on Sendmail and DNS: http://www.ca/security/howto/ Primary source for information on NTP – http://www.pdf NTP white paper: http://www.com/software/whitepapers/wp-rbac/ OpenSSH white paper: http://www.org/ http://www.org/ Pre-compiled software packages for various OS platforms: ftp://ftp.sun.sun.mit.uwaterloo.apache.pdf 55 .cisecurity.deer-run.edu/kerberos/www/ Apache "Security Tips" document: http://httpd.ntp.sendmail.com/solutions/blueprints/0701/openSSH.com/pub/patches/ Sun Patch Manager tool: http://www.org/ Sun Microsystems Patches and related documentation: ftp://sunsolve.pdf Other Misc Documentation Various documentation on Solaris security issues: http://ist.sun.sun.sun.cisecurity.html Kernel (ndd) settings for network-layer security: http://www.References The Center for Internet Security Free benchmark documents and security tools for various OS platforms and applications: http://www.pdf Role-Based Access Control (RBAC) white paper: http://wwws.com/~hal/dns-sendmail/DNSandSendmail.0/misc/security_tips.com/service/support/sw_only/patchmanager.com/software/solutions/blueprints/1200/network-updt1.sun.

com/products/portsentry.tripwire.uva.org TCP Wrappers source distribution: ftp.com/products/tripwire_asr/ http://www.org PortSentry (monitors unused network ports for unauthorized access): http://www.science.sunfreeware.nl/pub/solaris/fix-modes.Software Pre-compiled software packages for Solaris: http://www.org/ fix-modes (free tool to correct permissions and ownerships in the Solaris OS): ftp://ftp.com/ ftp://ftp.cisecurity.tripwire.html Open Source Sendmail (email server) distributions: ftp://ftp.org/ LPRng (Open Source replacement printing system for Unix): http://www.lprng.gz sudo (provides fine-grained access controls for superuser activity): http://www.org/ Tripwire (free and commercial file system integrity checking software): http://www.sendmail.com/sudo/ 56 .psionic.openssh.courtesan.porcupine.tar.org/ OpenSSH (secure encrypted network logins): www.

Sign up to vote on this title
UsefulNot useful