Solaris 10 x86 Security Technical Implementation Guide

Checks: C-35835r1_chk

This can be checked in the /etc/default/sulogin file (on Solaris 5.X systems) to check if the system runs sulogin, or an equivalent, when booting into single-user mode.

Fix: F-31076r1_fix

Edit /etc/default/sulogin and set PASSREQ=YES or remove /etc/default/sulogin entirely. NOTE: This is a default on Solaris 5.5.1 and later.

Generate Mitigation Statement:

Checks: C-27975r1_chk

Use the last command to check for multiple accesses to an account from different workstations/IP addresses. If users log directly onto accounts, rather than using the su command from their own named account to access them, this is a finding (such as logging directly on to Oracle). Also, ask the SA or the IAO if shared accounts are logged into directly or if users log on to an individual account and switch user to the shared account.

Fix: F-24339r1_fix

Use the switch user (su) command from a named account login to access shared accounts. Maintain audit trails that identify the actual user of the account name. Document requirements and procedures for users/administrators to log into their own accounts first and then switch user (su) to the shared account.

Generate Mitigation Statement:

Checks: C-27977r4_chk

Check the system for duplicate account names. Example: # passwd -sa | sort | uniq -c | awk '$1 > 1 {print $2}' If any duplicate account names are found, this is a finding.

Fix: F-24342r1_fix

Change user account names, or delete accounts, so each account has a unique name.

Generate Mitigation Statement:

Checks: C-27982r1_chk

Perform the following to ensure there are no duplicate UIDs. # logins -d If any duplicate UIDs are found, this is a finding.

Fix: F-24344r1_fix

Edit user accounts to provide unique UIDs for each account.

Generate Mitigation Statement:

Checks: C-28845r1_chk

Access the system console and make a logon attempt. Check for either of the following login banners based on the character limitations imposed by the system. An exact match is required. If one of these banners is not displayed, this is a finding. "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. " OR "I've read & consent to terms in IS user agreem't."

Fix: F-25868r1_fix

Edit /etc/issue and add one of the DoD login banners (based on the character limitations imposed by the system). DoD Login Banners: "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." OR "I've read & consent to terms in IS user agreem't."

Generate Mitigation Statement:

Checks: C-27994r1_chk

Determine if successful logons are being logged. # last | more Determine if unsuccessful logons are being logged. # more /var/adm/loginlog If the commands do not return successful and unsuccessful logins, this is a finding. Check the syslog daemon configuration for authentication logging. # egrep "auth\.(info|debug)" /etc/syslog.conf If there are no entries in syslog for the auth service, this is a finding.

Fix: F-33970r1_fix

Verify that login logs are handled correctly in the /etc/syslog.conf file. Edit the /etc/syslog.conf file and add one of the entries below. auth.debug /var/log/authlog OR auth.* /var/log/authlog Verify that service startup scripts for syslog and utmp (if present) are enabled.

Generate Mitigation Statement:

Checks: C-38685r1_chk

Verify RETRIES is set in the login file. # grep RETRIES /etc/default/login If RETRIES is not set or is more than 3, this is a finding. Verify the account locks after invalid login attempts. # grep LOCK_AFTER_RETRIES /etc/security/policy.conf If LOCK_AFTER_RETRIES is not set to YES, this is a finding.

Fix: F-33972r1_fix

Set RETRIES to 3 in the /etc/default/login file. #vi /etc/default/login Set LOCK_AFTER_RETRIES to YES in the /etc/security/policy.conf file. #vi /etc/security/policy.conf

Generate Mitigation Statement:

Checks: C-28006r1_chk

Check the SLEEPTIME parameter in the /etc/default/login file. # grep SLEEPTIME /etc/default/login If SLEEPTIME is not listed, commented out, or less than 4, this is a finding.

Fix: F-24360r1_fix

Edit the /etc/default/login file and set SLEEPTIME to 4.

Generate Mitigation Statement:

Checks: C-229r2_chk

If there is an application running on the system continuously in use (such as a network monitoring application), ask the SA what the name of the application is. Execute the following to determine which user owns the process(es) associated with the application. If the owner is root, this is a finding. # ps -ef | more

Fix: F-923r2_fix

Configure the system so the owner of a session requiring a continuous screen display, such as a network management display, is not root. Ensure the display is also located in a secure, controlled access area. Document and justify this requirement. Ensure the terminal and keyboard for the display (or workstation) are secure from all but authorized personnel by maintaining them in a secure area, in a locked cabinet where a swipe card, or other positive forms of identification, must be used to gain entry.

Generate Mitigation Statement:

Checks: C-38691r1_chk

Check the system for duplicate UID 0 assignments by listing all accounts assigned UID 0. Procedure: # awk -F: '$3 == 0' /etc/passwd If any accounts other than root are assigned UID 0, this is a finding.

Fix: F-24403r1_fix

Remove or change the UID of accounts other than root that have UID 0.

Generate Mitigation Statement:

Checks: C-28063r1_chk

Check the mode of the root home directory. Procedure: # grep "^root" /etc/passwd | awk -F":" '{print $6}' # ls -ld <root home directory> If the mode of the directory is not equal to 0700, this is a finding. If the home directory is /, this is not applicable.

Fix: F-929r2_fix

The root home directory will have permissions of 0700. Do not change the protections of the / directory. Use the following command to change protections for the root home directory. # chmod 0700 /rootdir.

Generate Mitigation Statement:

Checks: C-236r6_chk

To view the root user's PATH, log in as the root user, and execute the following. # env | grep PATH This variable is formatted as a colon-separated list of directories. If there is an empty entry, such as a leading or trailing colon or two consecutive colons, this is a finding. If an entry begins with a character other than a slash (/), or has not been documented with the ISSO, this is a finding.

Fix: F-930r3_fix

Edit the root user's local initialization files. Remove any empty path entries. Remove any relative path entries that have not been documented with the ISSO. Edit the root user’s local initialization files and remove any empty entry that is defined.

Generate Mitigation Statement:

Checks: C-35857r1_chk

Check for world-writable permissions on all directories in the root user's executable search path. Procedure (on multiple lines): # echo $PATH | sed 's/ /\\ /g; s/:/ /g' | xargs ls -ld If any of the directories in the PATH variable are world-writable, this is a finding.

Fix: F-24415r1_fix

For each world-writable path in root's executable search path, perform one of the following. 1. Remove the world-writable permission on the directory. Procedure: # chmod o-w <path> 2. Remove the world-writable directory from the executable search path. Procedure: Identify and edit the initialization file referencing the world-writable directory and remove it from the PATH variable.

Generate Mitigation Statement:

Checks: C-28066r1_chk

Check the CONSOLE setting in /etc/default/login # grep CONSOLE /etc/default/login If CONSOLE is set to a value other than /dev/console, this is a finding.

Fix: F-24417r1_fix

Edit the /etc/default/login file and uncomment the line containing /dev/console if it is commented out.

Generate Mitigation Statement:

Checks: C-29001r1_chk

# more /etc/passwd Confirm all accounts with a GID of 99 and below are used by a system account. If a GID reserved for system accounts (0 - 99) is used by a non-system account, this is a finding.

Fix: F-25999r1_fix

Change the primary group GID numbers for non-system accounts with reserved primary group GIDs (those less or equal to 99). # usermod -g <new_group> <user>

Generate Mitigation Statement:

Checks: C-285r3_chk

Ask the SA or IAO if a host-based intrusion detection application is loaded on the system. Determine if the application is loaded on the system. Procedure: # find / -name &lt;daemon name&gt; -print Determine if the application is active on the system. Procedure: # ps -ef | grep &lt;daemon name&gt; If no host-based intrusion detection system is installed on the system, this is a finding.

Fix: F-936r3_fix

Install a host-based intrusion detection tool.

Generate Mitigation Statement:

Checks: C-39532r2_chk

Use the smpatch(1m) utility to check for available security updates from Oracle. # smpatch analyze If there are security updates available, this is a finding.

Fix: F-34668r2_fix

Apply available security updates from Oracle. # smpatch update

Generate Mitigation Statement:

Checks: C-38710r1_chk

Check system directories for uneven file permissions. Procedure: # ls -lL /etc /bin /usr/bin /usr/ucb /sbin /usr/sbin Uneven file permissions exist if the file owner has less permissions than the group or other user classes. If any of the files in the above listed directories contain uneven file permissions, this is a finding.

Fix: F-24427r1_fix

Change the mode of files with uneven permissions so owners do not have less permission than group or world users.

Generate Mitigation Statement:

Checks: C-290r2_chk

Check the system for files with no assigned owner. Procedure: # find / -nouser -print If any files have no assigned owner, this is a finding.

Fix: F-939r2_fix

All directories and files (executable and data) will have an identifiable owner and group name. Either trace files to an authorized user, change the file's owner to root, or delete them. Determine the legitimate owner of the files and use the chown command to set the owner and group to the correct value. If the legitimate owner cannot be determined, change the owner to root (but make sure none of the changed files remain executable because they could be Trojan horses or other malicious code). Examine the files to determine their origin and the reason for their lack of an owner/group.

Generate Mitigation Statement:

Checks: C-28109r1_chk

Check the mode of network services daemons. # ls -la /usr/bin /usr/sbin If the mode of a network services daemon is more permissive than 0755, this is a finding. NOTE: Network daemons not residing in these directories (such as httpd or sshd) must also be checked for the correct permissions. A way to locate network daemons, such as httpd and sshd, is with the ps command. # ps -ef | egrep '(sshd|httpd)'

Fix: F-940r2_fix

Change the mode of the network services daemon. # chmod 0755 <path>

Generate Mitigation Statement:

Checks: C-38709r2_chk

Check the mode of log file hierarchies. Procedure: # ls -lLRa /var/log /var/adm If any of the log files or their directories have modes more permissive than "0640", and these are not documented, this is a finding.

Fix: F-941r3_fix

Change the mode of the system log file(s) to 0640 or less permissive. Procedure: # chmod "0640" /path/to/system-log-file NOTE: Do not confuse system log files with audit logs. Any subsystems that require less stringent permissions must be documented.

Generate Mitigation Statement:

Checks: C-293r2_chk

Check skeleton files permissions. # ls -alL /etc/skel If a skeleton file has a mode more permissive than 0644, this is a finding.

Fix: F-942r2_fix

Change the mode of skeleton files with incorrect mode. # chmod 0644 <skeleton file>

Generate Mitigation Statement:

Checks: C-28120r1_chk

Perform the following to check NIS file ownership. # ls -lRa /usr/lib/netsvc/yp /var/yp If the file ownership is not root, sys, or bin, this is a finding.

Fix: F-34044r1_fix

Change the ownership of NIS/NIS+/yp files to root, bin, or sys. Procedure: # chown -R root /usr/lib/netsvc/yp /var/yp

Generate Mitigation Statement:

Checks: C-28133r1_chk

Perform the following to check NIS file ownership. # ls -lRa /usr/lib/netsvc/yp /var/yp If the file group owner is not root, sys, or bin, this is a finding.

Fix: F-34043r1_fix

Change the group owner of the NIS files to root, bin, or sys. Procedure: # chgrp -R root /usr/lib/netsvc/yp /var/yp

Generate Mitigation Statement:

Checks: C-28139r1_chk

Perform the following to check NIS file mode. # ls -lRa /usr/lib/netsvc/yp /var/yp If the file's mode is more permissive than 0755, this is a finding.

Fix: F-34672r1_fix

Change the mode of NIS/NIS+/yp command files to 0755 or less permissive. Procedure: # chmod -R 0755 /usr/lib/netsvc/yp /var/yp

Generate Mitigation Statement:

Checks: C-38693r1_chk

Check the mode of library files. Procedure: # ls -lLR /usr/lib /lib /usr/sfw/lib If any of the library files have a mode more permissive than 0755, this is a finding.

Fix: F-947r2_fix

Change the mode of library files to 0755 or less permissive. Procedure (example): # chmod 0755 /path/to/library-file NOTE: Library files should have an extension of .a or .so, possibly followed by a version number.

Generate Mitigation Statement:

Checks: C-298r6_chk

Check the permissions for files in /etc, /bin, /usr/bin, /usr/lbin, /usr/ucb, /sbin, and /usr/sbin. Procedure: # ls -lL /etc /bin /usr/bin /usr/lbin /usr/ucb /sbin /usr/sbin If any command file is listed and has a mode more permissive than 755, this is a finding. Note: Elevate to Severity Code I if any command file listed is world-writable.

Fix: F-948r3_fix

Change the mode for system command files to 755 or less permissive. Procedure: # chmod 755 <filename>

Generate Mitigation Statement:

Checks: C-8014r2_chk

Check the ownership of system files, programs, and directories. Procedure: # ls -lLa /etc /bin /usr/bin /usr/lbin /usr/ucb /sbin /usr/sbin If any of the system files, programs, or directories are not owned by a system account, this is a finding.

Fix: F-949r2_fix

Change the owner of system files, programs, and directories to a system account. Procedure: # chown root /some/system/file (A different system user may be used in place of root.)

Generate Mitigation Statement:

Checks: C-8015r2_chk

Check the group ownership of system files, programs, and directories. Procedure: # ls -lLa /etc /bin /usr/bin /usr/lbin /usr/ucb /sbin /usr/sbin If any system file, program, or directory is not group-owned by a system group, this is a finding.

Fix: F-950r2_fix

Change the group owner of system files to a system group. Procedure: # chgrp root /path/to/system/file (System groups other than root may be used.)

Generate Mitigation Statement:

Checks: C-301r2_chk

Check the ownership of the /etc/shadow file. # ls -lL /etc/shadow If the /etc/shadow file is not owned by root, this is a finding.

Fix: F-34673r1_fix

Change the ownership of the /etc/shadow file. # chown root /etc/shadow

Generate Mitigation Statement:

Checks: C-8016r2_chk

Check the mode of the /etc/passwd file. Procedure: # ls -lL /etc/passwd If /etc/passwd has a mode more permissive than 0644, this is a finding.

Fix: F-952r2_fix

Change the mode of the passwd file to 0644. Procedure: # chmod 0644 /etc/passwd Document all changes.

Generate Mitigation Statement:

Checks: C-303r2_chk

Check the mode of the /etc/shadow file. # ls -lL /etc/shadow If the /etc/shadow file has a mode more permissive than 0400, this is a finding.

Fix: F-954r2_fix

Change the mode of the /etc/shadow (or equivalent) file. # chmod <mode> <file>

Generate Mitigation Statement:

Checks: C-527r2_chk

Files with the setuid bit set will allow anyone running these files to be temporarily assigned the user or group ID of the file. If an executable with setuid allows shell escapes, the user can operate on the system with the effective permission rights of the user or group owner. List all setuid files on the system. Procedure: # find / -perm -4000 -exec ls -l {} \; | more NOTE: Executing these commands may result in large listings of files; the output may be redirected to a file for easier analysis. Ask the SA or IAO if files with the setuid bit set have been documented. If any undocumented file has its setuid bit set, this is a finding.

Fix: F-955r2_fix

Document the files with the setuid bit set or unset the setuid bit on the executable.

Generate Mitigation Statement:

Checks: C-8026r2_chk

Locate all setgid files on the system. Procedure: # find / -perm -2000 If the ownership, permissions, location, and ACLs of all files with the setgid bit set are not documented, this is a finding.

Fix: F-956r2_fix

All files with the setgid bit set will be documented in the system baseline and authorized by the Information Systems Security Officer. Locate all setgid files with the following command. find / -perm -2000 -exec ls -lLd {} \; Ensure setgid files are part of the operating system software, documented application software, documented utility software, or documented locally developed software. Ensure none are text files or shell programs.

Generate Mitigation Statement:

Checks: C-528r2_chk

Determine if a weekly automated or manual process is used to generate a list of setuid files on the system and compare it with the prior list. If no such process is in place, this is a finding.

Fix: F-957r2_fix

Establish a weekly automated or manual process to generate a list of setuid files on the system and compare it with the prior list. To create a list of setuid files use the following command. # find / -perm -4000 > setuid-file-list

Generate Mitigation Statement:

Checks: C-8027r2_chk

Determine if a weekly automated or manual process is used to generate a list of setgid files on the system and compare it with the prior list. If no such process is in place, this is a finding.

Fix: F-958r2_fix

Establish a weekly automated or manual process to generate a list of setgid files on the system and compare it with the prior list. To create a list of setgid files use the following command. # find / -perm -2000 > setgid-file-list

Generate Mitigation Statement:

Checks: C-38683r4_chk

Check /etc/vfstab and verify the "nosuid" mount option is used on any user filesystem (such as /export/home) or filesystems mounted from removable media or network shares. # cat /etc/vfstab Check zfs filesystems for setuid mounts. #zfs get setuid

Fix: F-33969r1_fix

Use the following procedure for UFS filesystems. Edit /etc/vfstab and add the "nosuid" mount option to any user filesystem (such as /export/home) or filesystems mounted from removable media or network shares. Use the following procedure for ZFS filesystems. # zfs setuid = off < file system >

Generate Mitigation Statement:

Checks: C-8028r2_chk

Check the ownership of all public directories. Procedure: # find / -type d -perm -1002 -exec ls -ld {} \; If any public directory is not owned by root or an application user, this is a finding.

Fix: F-961r2_fix

Change the owner of public directories to root or an application account. Procedure: # chown root /tmp (Replace root with an application user and/or /tmp with another public directory as necessary.)

Generate Mitigation Statement:

Checks: C-28907r3_chk

NOTE: The following commands must be run in the BASH shell. Check global configuration: # find /etc -type f | xargs grep -i umask Check local initialization files: # cut -d: -f6 /etc/passwd | xargs -n1 -iHOMEDIR sh -c "grep umask HOMEDIR/.*" If the system and user default umask is not 077, this a finding. Note: If the default umask is 000 or allows for the creation of world writable files this becomes a CAT I finding..

Fix: F-25929r2_fix

Edit the /etc/default/login file for Solaris. Set the variable UMASK=077. Edit local and global initialization files containing "umask" and change them to use "077".

Generate Mitigation Statement:

Checks: C-38711r3_chk

Determine if default system accounts (such as, those for sys, bin, uucp, nuucp, daemon, smtp, gdm, lp, nobody) have been disabled. # cat /etc/shadow If an account's password field is "*", "*LK*", "NP", or is prefixed with a "!", the account is locked or disabled. If any default system account is not locked and its use is not justified and documented with the ISSO, this is a finding.

Fix: F-964r2_fix

Lock the default system account(s). # passwd -l <user>

Generate Mitigation Statement:

Checks: C-28344r2_chk

Determine the type of zone that you are currently securing. # zonename If the output of "zonename" is "global", then auditing must be enabled. Determine if auditing is enabled. # ps -ef |grep auditd If the auditd process is not found, this is a finding. If the output of "zonename" is not "global", then the "perzone" policy must be determined. # auditconfig –getpolicy audit policies = cnt,perzone If "perzone" is not listed then this requirement is not applicable. If "perzone" is listed then determine if auditing is enabled. # ps -ef |grep auditd If the auditd process is not found, this is a finding.

Fix: F-24513r1_fix

Use /etc/security/bsmconv to enable auditing on the system.

Generate Mitigation Statement:

Checks: C-28369r1_chk

Perform the following to determine the location of audit logs and then check the ownership. # more /etc/security/audit_control # ls -lLa &lt;audit log dir&gt; If any audit log file is not owned by root, this is a finding.

Fix: F-966r2_fix

Change the ownership of the audit log file(s). Procedure: # chown root <audit log file>

Generate Mitigation Statement:

Checks: C-28380r1_chk

Perform the following to determine the location of audit logs and then check the mode of the files. # more /etc/security/audit_control # ls -lLa &lt;audit log dir&gt; If the audit log directory has a mode more permissive than 0750 or any audit log file has a mode more permissive than 0640, this is a finding.

Fix: F-967r2_fix

Change the mode of the audit log directories/files. # chmod 0750 <audit directory> # chmod 0640 <audit file>

Generate Mitigation Statement:

Checks: C-28395r1_chk

Check the system audit configuration to determine if failed attempts to access files and programs are audited. # more /etc/security/audit_control If flags -fr or fr are not configured, this is a finding.

Fix: F-24523r1_fix

Edit /etc/security/audit_control and add the fr or -fr flags to the flags list. Load the new audit configuration. # auditconfig -conf

Generate Mitigation Statement:

Checks: C-28401r1_chk

# grep flags /etc/security/audit_control Confirm flags fd or +fd and -fd are configured.

Fix: F-24528r1_fix

Edit /etc/security/audit_control and add the fd to the flags list. Load the new audit configuration. # auditconfig -conf

Generate Mitigation Statement:

Checks: C-28413r1_chk

Check the auditing configuration of the system. # grep flags /etc/security/audit_control If the am flag is not present, and either of the -am or +am flags is not present, this is a finding.

Fix: F-24539r1_fix

Edit /etc/security/audit_control and add am to the flags list. Load the new audit configuration. # auditconfig -conf

Generate Mitigation Statement:

Checks: C-28419r1_chk

Check the system's audit configuration. # grep lo /etc/security/audit_control If the lo flag is not set, and both the +lo and -lo flags are not set, this is a finding. If the lo naflag is not set, and both the +lo and -lo naflags are not set, this is a finding.

Fix: F-24546r1_fix

Edit /etc/security/audit_control and add lo to the flags list and naflags list. Load the new audit configuration. # auditconfig -conf

Generate Mitigation Statement:

Checks: C-28437r1_chk

Check the system's audit configuration. # grep flags /etc/security/audit_control Confirm flags fm or +fm and -fm are configured.

Fix: F-24552r1_fix

Edit /etc/security/audit_control and add fm to the flags list. Load the new audit configuration. # auditconfig -conf

Generate Mitigation Statement:

Checks: C-39293r1_chk

Check the ownership of inetd.conf file. Procedure: # ls -lL /etc/inet/inetd.conf This is a finding if any of the above files or directories are not owned by root or bin.

Fix: F-34404r1_fix

Change the ownership of the inetd.conf file to root or bin. Procedure: # chown root /etc/inet/inetd.conf

Generate Mitigation Statement:

Checks: C-39292r1_chk

Check the mode of inetd.conf file. # ls -lL /etc/inet/inetd.conf If the mode of the file is more permissive than 0440, this is a finding.

Fix: F-34403r1_fix

Change the mode of the inetd.conf file. # chmod 0440 /etc/inet/inetd.conf

Generate Mitigation Statement:

Checks: C-28612r1_chk

Check the ownership of the services file. Procedure: # ls -lL /etc/services If the services file is not owned by root or bin, this is a finding.

Fix: F-977r2_fix

Change the ownership of the services file to root or bin. Procedure: # chown root /etc/services

Generate Mitigation Statement:

Checks: C-8030r2_chk

Check the mode of the services file. Procedure: # ls -lL /etc/services If the services file has a mode more permissive than 0444, this is a finding.

Fix: F-978r2_fix

Change the mode of the services file to 0444 or less permissive. Procedure: # chmod 0444 /etc/services

Generate Mitigation Statement:

Checks: C-39287r1_chk

Solaris uses the "IPP" print service and can also use the Samba print service. Verify remote host access is limited. Procedure: # grep -i Listen /etc/apache/httpd-standalone-ipp.conf The /etc/apache/httpd-standalone-ipp.conf file must not contain a Listen *:&lt;port&gt; or equivalent line. If the network address of the "Listen" line is unrestricted, this is a finding. # grep -i "Allow From" /etc/apache/httpd-standalone-ipp.conf The "Allow From" line within the "&lt;Location /&gt;" element should limit access to the printers to @LOCAL and specific hosts. If the "Allow From" line contains "All", this is a finding. Verify guest access to printers shared via Samba is restricted according to GEN006235.

Fix: F-34391r1_fix

Configure IPP to use only the localhost or specified remote hosts. Procedure: Modify the /etc/apache/httpd-standalone-ipp.conf file to "Listen" only to the local machine or a known set of hosts (i.e., Listen localhost:631). Modify the /etc/apache/httpd-standalone-ipp.conf file "<Location />" element to "Deny From All" and "Allow from 127.0.0.1" or allowed host addresses. Restart the IPP service: # svcadm restart ipp-listener

Generate Mitigation Statement:

Checks: C-36123r6_chk

Check the owner of the print service configuration files. Procedure: # ls -lL /etc/apache/httpd-standalone-ipp.conf /etc/printers.conf /etc/smb.conf /etc/sfw/smb.conf /etc/samba/smb.conf /etc/sfw/samba/smb.conf If the owner of any of the print service configuration files is not root, this is a finding.

Fix: F-34392r2_fix

Change the owner of the print service configuration files. Procedure: # chown root /etc/apache/httpd-standalone-ipp.conf /etc/printers.conf /etc/sfw/smb.conf

Generate Mitigation Statement:

Checks: C-36125r3_chk

Check the mode of the print service configuration files. Procedure: # ls -lL /etc/apache/httpd-standalone-ipp.conf /etc/printers.conf /etc/smb.conf /etc/sfw/smb.conf /etc/samba/smb.conf /etc/sfw/samba/smb.conf If the mode of any of the print service configuration file is more permissive than 0644, this is a finding.

Fix: F-34395r3_fix

Change the mode of the print service configuration files to 0644 or less permissive. Procedure: # chmod 0644 /etc/apache/httpd-standalone-ipp.conf /etc/printers.conf /etc/smb.conf /etc/sfw/smb.conf /etc/samba/smb.conf /etc/sfw/samba/smb.conf

Generate Mitigation Statement:

Checks: C-39300r1_chk

Find the alias file on the system. Procedure: # egrep '^O(A| AliasFile)' /etc/mail/sendmail.cf If the "alias file" is an NIS or LDAP map, this check is not applicable. The default location is /etc/mail/aliases. Check the ownership of the alias file. Procedure: # ls -lL &lt;alias file&gt; If the alias file is not owned by root, this is a finding.

Fix: F-34503r1_fix

Change the owner of the /etc/mail/aliases file (or equivalent, such as /usr/lib/aliases) to root. Procedure: # chown root /etc/mail/aliases

Generate Mitigation Statement:

Checks: C-39390r1_chk

Find the alias files on the system. Procedure: # egrep '^O(A| AliasFile)' /etc/mail/sendmail.cf If the alias file is an NIS or LDAP map, this check is not applicable. The default location is /etc/mail/aliases. Check the permissions of the alias file and the hashed version of it used by sendmail. Procedure: # ls -lL /etc/mail/aliases /etc/mail/aliases.db If the alias files have a mode more permissive than 0644, this is a finding.

Fix: F-34508r1_fix

Change the mode of the /etc/mail/aliases files (or equivalent, such as /usr/lib/aliases) to 0644. Procedure: # chmod 0644 /etc/mail/aliases /etc/mail/aliases.db

Generate Mitigation Statement:

Checks: C-40028r1_chk

Check the syslog configuration file for mail.crit logging configuration. Procedure: # more /etc/syslog.conf Verify a line similar to one of the following lines is present in syslog.conf is configured so that critical mail log data is logged. (Critical log data may also be captured by a remote log host in accordance with GEN005460.) mail.crit /var/adm/messages *.crit /var/log/messages Less severe syslog levels (err, warning, info, and debug) may be substituted for crit, since they will also capture crit level syslog messages. If syslog is not configured to log critical Sendmail messages, this is a finding.

Fix: F-990r2_fix

Edit the syslog.conf file and add a configuration line specifying an appropriate destination for mail.crit syslogs.

Generate Mitigation Statement:

Checks: C-8034r2_chk

Locate any mail log files by checking the syslog configuration file. Procedure: # more /etc/syslog.conf Identify any log files configured for the mail service at any severity level, or those configured for all services. Check the ownership of these log files. Procedure: # ls -lL &lt;file location&gt; If any mail log file is not owned by root, this is a finding.

Fix: F-991r2_fix

Change the ownership of the Sendmail log file. # chown root <sendmail log file>

Generate Mitigation Statement:

Checks: C-8035r2_chk

Check the mode of the SMTP service log file. Procedure: # more /etc/syslog.conf Check the configuration to determine which log files contain logs for mail.crit, mail.debug, or *.crit. Procedure: # ls -lL &lt;file location&gt; If the log file permissions are greater than 0644, this is a finding.

Fix: F-992r2_fix

Change the mode of the SMTP service log file. Procedure: # chmod 0644 <sendmail log file>

Generate Mitigation Statement:

Checks: C-28647r1_chk

Check for the existence of the ftpusers file. # ls -l /etc/ftpd/ftpusers If the ftpusers file does not exist, this is a finding.

Fix: F-25675r1_fix

Create a /etc/ftpd/ftpusers file containing a list of accounts not authorized for FTP.

Generate Mitigation Statement:

Checks: C-28661r1_chk

Check the contents of the ftpusers file. Procedure: # more /etc/ftpd/ftpusers If the system has accounts not allowed to use FTP that are not listed in the ftpusers file, this is a finding.

Fix: F-25692r1_fix

Add accounts not allowed to use FTP to the /etc/ftpd/ftpusers file.

Generate Mitigation Statement:

Checks: C-28665r1_chk

Check the ownership of the ftpusers file. # ls -l /etc/ftpd/ftpusers If the ftpusers file is not owned by root, this is a finding.

Fix: F-25695r1_fix

Change the owner of the ftpusers file to root. # chown root /etc/ftpd/ftpusers

Generate Mitigation Statement:

Checks: C-28669r1_chk

Check the permissions of the ftpusers file. # ls -l /etc/ftpd/ftpusers If the ftpusers file has a mode more permissive than 0640, this is a finding.

Fix: F-25698r1_fix

Change the mode of the ftpusers file to 0640. # chmod 0640 /etc/ftpd/ftpusers

Generate Mitigation Statement:

Checks: C-711r2_chk

Attempt to log into this host with a user name of anonymous and a password of guest (also try the password of guest@mail.com). If the logon is successful, this is a finding. Procedure: # ftp localhost Name: anonymous 530 Guest login not allowed on this machine.

Fix: F-1000r2_fix

Configure the FTP service to not permit anonymous logins.

Generate Mitigation Statement:

Checks: C-38704r2_chk

Verify the tftp service is enabled. # svcs tftp If the tftp service is not installed or enabled, this check is not applicable. Check the /etc/passwd file to determine if TFTP is configured properly. Procedure: # grep tftp /etc/passwd If a "tftp" user account does not exist and TFTP is active, this is a finding. Check the user shell for the "tftp" user. If it is not /bin/false or equivalent, this is a finding. Check the home directory assigned to the "tftp" user. If no home directory is set, or the directory specified is not dedicated to the use of the TFTP service, this is a finding.

Fix: F-1003r2_fix

Create a TFTP user account if none exists. Assign a non-login shell to the TFTP user account, such as /bin/false. Assign a home directory to the TFTP user account.

Generate Mitigation Statement:

Checks: C-718r2_chk

Check for .Xauthority files being utilized by looking for such files in the home directory of a user that uses X. Procedure: # cd ~someuser # ls -la .Xauthority If the .Xauthority file does not exist, ask the SA if the user is using X Windows. If the user is utilizing X Windows and the .Xauthority file does not exist, this is a finding.

Fix: F-1004r2_fix

Ensure the X Windows host is configured to write .Xauthority files into user home directories. Edit the Xaccess file. Ensure the line that writes the .Xauthority file is uncommented.

Generate Mitigation Statement:

Checks: C-851r2_chk

Perform the following to determine if NIS is active on the system. # ps -ef | egrep '(ypbind|ypserv)' If NIS is found active on the system, this is a finding.

Fix: F-1021r2_fix

Disable the use of NIS. Possible replacements are NIS+ and LDAP.

Generate Mitigation Statement:

Checks: C-8017r3_chk

Check the home directory mode of each user in /etc/passwd. Procedure: # cut -d : -f 6 /etc/passwd | xargs -n1 ls -ld | more If a user's home directory's mode is more permissive than 0750, this is a finding. NOTE: Application directories are allowed and may need 0755 permissions (or greater) for correct operation.

Fix: F-1055r2_fix

Change the mode of users' home directories to 0750 or less permissive. Procedure (example): # chmod 0750 <home directory>

Generate Mitigation Statement:

Checks: C-38697r3_chk

Check the ownership of each user's home directory listed in the /etc/passwd file. Procedure: # cut -d : -f 6 /etc/passwd | xargs -n1 ls -ld | more If any user's home directory is not owned by the assigned user, this is a finding.

Fix: F-1056r2_fix

Change the owner of a user's home directory to its assigned user. Procedure: # chown <user> <home directory>

Generate Mitigation Statement:

Checks: C-38698r3_chk

Check the group ownership for each user in the /etc/passwd file. Procedure: # cut -d : -f 6 /etc/passwd | xargs -n1 ls -ld | more If any user's home directory is not group-owned by the assigned user's primary group, this is a finding. Home directories for application accounts requiring different group ownership must be documented using site-defined procedures.

Fix: F-1057r3_fix

Change the group owner for user's home directories to the primary group of the assigned user. Procedure: # chgrp groupname directoryname (Replace examples with appropriate group and home directory.) Document all changes.

Generate Mitigation Statement:

Checks: C-395r4_chk

NOTE: The following commands must be run in the BASH shell. Check the ownership of local initialization files. Procedure (using a shell that supports ~USER as USER's home directory): # cut -d : -f 1 /etc/passwd | xargs -n1 -IUSER sh -c "ls -l ~USER/.[a-z]*" # cut -d : -f 1 /etc/passwd | xargs -n1 -IUSER find ~USER/.dt ! -fstype nfs ! -user USER -exec ls -ld {} \; If local initialization files are not owned by the home directory's user, this is a finding.

Fix: F-1058r3_fix

Change the ownership of the startup and login files in the user's directory to the user or root, as appropriate. Examine each user's home directory and verify all file names beginning with "." are owned by the owner of the directory or root. If they are not, use the chown command to change the owner to the user and research the reasons why the owners were not assigned as required. Procedure: # chown username .filename Document all changes.

Generate Mitigation Statement:

Checks: C-8020r2_chk

Check the modes of local initialization files. Procedure: # ls -al /&lt;usershomedirectory&gt;/.login # ls -al /&lt;usershomedirectory&gt;/.cshrc # ls -al /&lt;usershomedirectory&gt;/.logout # ls -al /&lt;usershomedirectory&gt;/.profile # ls -al /&lt;usershomedirectory&gt;/.bash_profile # ls -al /&lt;usershomedirectory&gt;/.bashrc # ls -al /&lt;usershomedirectory&gt;/.bash_logout # ls -al /&lt;usershomedirectory&gt;/.env # ls -al /&lt;usershomedirectory&gt;/.dtprofile (permissions should be 0755) # ls -al /&lt;usershomedirectory&gt;/.dispatch # ls -al /&lt;usershomedirectory&gt;/.emacs # ls -al /&lt;usershomedirectory&gt;/.exrc # find /&lt;usershomedirectory&gt;/.dt ! -fstype nfs \( -perm -0002 -o -perm -0020 \) -exec ls -ld {} \; (permissions not to be more permissive than 0755) If local initialization files are more permissive than 0740, the .dt directory or the .dtprofile file is more permissive than 0755, this is a finding.

Fix: F-1059r3_fix

Ensure user startup files have permissions of 0740 or more restrictive. Examine each user's home directory and verify all file names beginning with "." have access permissions of 0740 or more restrictive. If they do not, use the chmod command to correct the vulnerability. Procedure: # chmod 0740 .filename NOTE: The period is part of the file name and is required.

Generate Mitigation Statement:

Checks: C-28179r3_chk

Check run control script modes. # ls -lL /etc/rc* /etc/init.d /lib/svc/method If any run control script has a mode more permissive than 0755, this is a finding.

Fix: F-39582r1_fix

Ensure all system startup files have mode 0755 or less permissive. Examine the rc files, and all files in the rc1.d (rc2.d, and so on) directories, and in the /etc/init.d and /lib/svc/method directories to ensure they are not world-writable. If they are world-writable, use the chmod command to correct the vulnerability and to research why. Procedure: # chmod go-w <startupfile>

Generate Mitigation Statement:

Checks: C-38716r5_chk

Verify run control scripts' executable search paths. Procedure: # find /etc/rc* /etc/init.d /lib/svc/method -type f -print | xargs grep -w PATH This variable is formatted as a colon-separated list of directories. Relative path entries must be document with the ISSO. If there is an empty entry, such as a leading or trailing colon or two consecutive colons, this is a finding. If an entry begins with a character other than a slash (/), or has not been documented with the ISSO, this is a finding.

Fix: F-1061r4_fix

Edit the run control script and remove the relative path entries from the executable search path variable that are not documented with the ISSO. Edit the run control script and remove any empty entry that is defined.

Generate Mitigation Statement:

Checks: C-404r2_chk

Check the system for the existence of any .netrc files. Procedure: # find / -name .netrc If any .netrc file exists, this is a finding.

Fix: F-1067r3_fix

Remove the .netrc file(s). Procedure: # rm .netrc

Generate Mitigation Statement:

Checks: C-432r2_chk

Verify /etc/shells exists. # ls -l /etc/shells If the file does not exist, this is a finding.

Fix: F-34658r1_fix

Create a /etc/shells file containing a list of valid system shells. The list below contains the default shells from the shells(4) man page. Procedure (the command is 24 lines long): cat >/etc/shells <<EOF /bin/bash /bin/csh /bin/jsh /bin/ksh /bin/pfcsh /bin/pfksh /bin/pfsh /bin/sh /bin/tcsh /bin/zsh /sbin/jsh /sbin/sh /usr/bin/bash /usr/bin/csh /usr/bin/jsh /usr/bin/ksh /usr/bin/pfcsh /usr/bin/pfksh /usr/bin/pfsh /usr/bin/sh /usr/bin/tcsh /usr/bin/zsh EOF

Generate Mitigation Statement:

Checks: C-433r2_chk

Confirm the login shells referenced in the /etc/passwd file are listed in the /etc/shells file. Procedure: # more /etc/passwd # more /etc/shells The /usr/bin/false, /bin/false, /dev/null, /sbin/nologin, (and equivalents), and sdshell will be considered valid shells for use in the /etc/passwd file, but will not be listed in the /etc/shells file. If a shell referenced in /etc/passwd is not listed in the shells file, excluding the above mentioned shells, this is a finding.

Fix: F-1071r2_fix

Use the chsh utility or edit the /etc/passwd file and correct the error by changing the default shell of the account in error to an acceptable shell name contained in the /etc/shells file.

Generate Mitigation Statement:

Checks: C-38703r1_chk

Indications of inactive accounts are those without entries in the last log. Check the date in the last log to verify it is within the last 35 days. Obtain a listing of user accounts. #cat /etc/passwd | cut -f1 -d ":" Run the last command for each user account. # last &lt; user account &gt; If any user's account has not been accessed in the last 35 days and the account is not disabled via an entry in the password field in the /etc/passwd or /etc/shadow (or equivalent), check the /etc/passwd file to check if the account has a valid shell. If an inactive account is found that is not disabled, this is a finding.

Fix: F-33980r1_fix

All inactive accounts will have /bin/false, /usr/bin/false, or /dev/null as the default shell in the /etc/passwd file and have the password disabled. Disable the inactive accounts. Examine the inactive accounts using the last command. Note the date of last login for each account. If any (other than system and application accounts) exceed 35 days, then disable them by placing a shell of /bin/false or /dev/null in the shell field of the passwd file entry for that account. An alternative, and preferable method, is to disable the account using smc or the passwd command. # passwd -l < account to lock >

Generate Mitigation Statement:

Checks: C-8024r2_chk

Check the ownership of the system shells. # cat /etc/shells | xargs -n1 ls -lL If any shell is not owned by root or bin, this is a finding.

Fix: F-1075r2_fix

Change the ownership of the shell with incorrect ownership. # chown root <shell>

Generate Mitigation Statement:

Checks: C-465r3_chk

Find all device files existing anywhere on the system. Procedure: # find / -type b -print &gt; devicelist # find / -type c -print &gt;&gt; devicelist Check the permissions on the directories above subdirectories containing device files. The following list of device files are intended to be world-writable and if present are not a finding. /dev/arp /dev/conslog /dev/crypto /dev/dtrace/dtrace /dev/dtrace/helper /dev/dtrace/provider/fasttrap /dev/fd/* /dev/kstat /dev/null /dev/poll /dev/pool /dev/ptmx /dev/sad/user /dev/tcp /dev/tcp6 /dev/ticlts /dev/ticots /dev/ticotsord /dev/tty /dev/udp /dev/udp6 /dev/zero /dev/zfs If any device file or their parent directory is world-writable and it is not intended to be world-writable, this is a finding.

Fix: F-1078r3_fix

Remove the world-writable permission from the device file(s). Procedure: # chmod o-w <device file> Document all changes.

Generate Mitigation Statement:

Checks: C-466r2_chk

Check the system for world-writable device files. Procedure: # find / -perm -2 -a \( -type b -o -type c \) -exec ls -ld {} \; If any device file(s) used for backup are writable by users other than root, this is a finding.

Fix: F-1079r2_fix

Use the chmod command to remove the world-writable bit from the backup device files. Procedure: # chmod o-w backdevicefilename Document all changes.

Generate Mitigation Statement:

Checks: C-852r2_chk

If the system is not using NIS+, this is not applicable. Check the system to determine if NIS+ security level 2 is implemented. Procedure: # niscat cred.org_dir If the second column does not contain DES, the system is not using NIS+ security level 2, and this is a finding.

Fix: F-1080r2_fix

Ensure the NIS+ server is operating at security level 2 by editing /usr/lib/nis/nisserver and ensuring the line containing SEC= is set to the numeral 2, for example: SEC=2 # 2=DES or 3=RSA Security Level 0 is designed for testing and initial setup of the NIS+ namespace. When running at level 0, the daemon does not enforce access control. Any client is allowed to perform any operation, including updates and deletions. Security level 1 accepts AUTH_SYS and AUTH_DES credentials for authenticating clients and authorizing them to perform NIS+ operations. This is not a secure mode of operation since AUTH_SYS credentials are easily forged. It should not be used on networks in which any untrusted user may potentially have access. Security level 2 accepts only AUTH_DES credentials for authentication and authorization. This is the highest level of security currently provided by the NIS+ service and the default security level if the -S option is not used.

Generate Mitigation Statement:

Checks: C-28737r1_chk

Check the ownership of the dfstab file. Example: # ls -lL /etc/dfs/dfstab If the export configuration file is not owned by root, this is a finding.

Fix: F-25755r1_fix

Change the owner of the dfstab file to root. Example: # chown root /etc/dfs/dfstab

Generate Mitigation Statement:

Checks: C-39153r1_chk

Check for NFS exported file systems. Procedure: # exportfs -v OR # more /etc/dfs/sharetab This will display all of the exported file systems. For each file system displayed, check the ownership. Procedure: # ls -lLa &lt;exported file system path&gt; If the files and directories are not owned by root, this is a finding.

Fix: F-1085r2_fix

Change the ownership of exported file systems not owned by root. Procedure: # chown root <path>

Generate Mitigation Statement:

Checks: C-39154r1_chk

Check if the anon option is set correctly for exported file systems. List exported file systems. # exportfs -v OR # more /etc/dfs/sharetab Each of the exported file systems should include an entry for the 'anon=' option set to -1 or an equivalent (60001, 60002, 65534, or 65535). If an appropriate 'anon=' setting is not present for an exported file system, this is a finding.

Fix: F-25768r1_fix

Edit /etc/dfs/dfstab and add the "anon=-1" option for exports lacking it. Re-export the filesystems.

Generate Mitigation Statement:

Checks: C-39155r1_chk

Check the permissions on exported NFS file systems. Procedure: # exportfs -v OR # more /etc/dfs/sharetab If the exported file systems do not contain the rw or ro options specifying a list of hosts or networks, this is a finding.

Fix: F-25770r1_fix

Edit /etc/dfs/dfstab and add ro and/or rw options (as appropriate) specifying a list of hosts or networks which are permitted access. Re-export the file systems.

Generate Mitigation Statement:

Checks: C-39156r2_chk

Perform the following on NFS servers: # grep "^default" /etc/nfssec.conf Check to ensure the second column does not equal 0. This would indicate the default is set to none. Perform the following to check currently exported file systems. # more /etc/dfs/dfstab If the option sec=none is set on any of the exported file systems, this is a finding.

Fix: F-1088r2_fix

Edit the /etc/dfs/dfstab file and add the sec=XXX option to the share line as an option. XXX must be a valid option for the system other than none.

Generate Mitigation Statement:

Checks: C-39157r2_chk

Determine if the NFS server is exporting with the root access option. Procedure: # exportfs -v | grep "root=" OR # more /etc/dfs/sharetab If an export with the root option is found and is not properly documented with the IA staff, this is a finding.

Fix: F-25776r1_fix

Edit the /etc/dfs/dfstab file and remove the root= option from all exports. Re-export the file systems.

Generate Mitigation Statement:

Checks: C-39152r2_chk

Check the system for NFS mounts not using the nosuid option. Procedure: # mount -v | grep " type nfs " | grep -v nosetuid OR # grep nfs /etc/mnttab | grep -v nosuid | grep -v :vold If the mounted file systems do not have the nosetuid/nosuid option, this is a finding. NOTE: Mount options for the volume management daemon (vold) are controlled by the /etc/rmmount.conf file.

Fix: F-25777r1_fix

Edit /etc/vfstab and add the nosuid option for all NFS file systems. Remount the NFS file systems to make the change take effect.

Generate Mitigation Statement:

Checks: C-28783r3_chk

# svcprop -p defaults svc:/network/inetd | grep tcp_wrappers This should return a line with the following: defaults/tcp_wrappers boolean true If the above line contains the word false, this is a finding.

Fix: F-25785r1_fix

Enable tcp_wrappers. # svccfg -s svc:/network/inetd setprop defaults/tcp_wrappers=true # svcadm refresh inetd

Generate Mitigation Statement:

Checks: C-888r2_chk

Normally, TCPD logs to the mail facility in /etc/syslog.conf. Determine if syslog is configured to log events by TCPD. Procedure: # more /etc/syslog.conf Look for entries similar to the following: mail.debug /var/adm/maillog mail.none /var/adm/maillog mail.* /var/log/mail auth.info /var/log/messages The above entries would indicate mail alerts are being logged. If no entries for mail exist, then TCPD is not logging and this is a finding.

Fix: F-1095r2_fix

Configure the access restriction program to log every access attempt. Ensure the implementation instructions for TCP_WRAPPERS are followed, so system access attempts are logged into the system log files. If an alternate application is used, it must support this function.

Generate Mitigation Statement:

Checks: C-2249r2_chk

Determine if ASET is being used. # crontab -l | grep aset Check the configuration of ASET. # more /usr/aset/asetenv OR Check that asetenv has not been modified since installation. # pkgchk SUNWast If there are any changes below the following two lines that are not comments, this is a finding. # Don't change from here on down ... # # there shouldn't be any reason to. # In addition, if any of the following lines do not match, this is a finding. TASKS="firewall env sysconf usrgrp tune cklist eeprom" CKLISTPATH_LOW=${ASETDIR}/tasks:#${ASETDIR} \ /util:${ASETDIR}/masters:/etc CKLISTPATH_MED=${CKLISTPATH_LOW}:/usr/bin:/usr/ucb CKLISTPATH_HIGH=${CKLISTPATH_MED}:/usr/lib:/sbin: \ /usr/sbin:/usr/ucblib YPCHECK=false PERIODIC_SCHEDULE="0 0 * * *" UID_ALIASES=${ASETDIR}/masters/uid_aliases (The default asetenv file can be found on the Solaris installation media.)

Fix: F-1107r2_fix

Restore the ASET configuration to vendor default and only modify the portions of the configuration designated as customizable.

Generate Mitigation Statement:

Checks: C-2250r2_chk

Perform the following to determine if ASET is configured to check NIS+. # grep YPCHECK /usr/aset/asetenv If NIS+ is running and the YPCHECK variable is set to false, then this is a finding.

Fix: F-31075r1_fix

Edit the ASET configuration and set YPCHECK to true on systems running NIS. (If NIS+ is configured, YPCHECK must only be set to false to avoid going into NIS compatibility mode.) Configure NIS to use YPCHECK.

Generate Mitigation Statement:

Checks: C-28803r1_chk

Determine if ASET is being used. # crontab -l | grep aset If ASET is not used on the system, this is not applicable. If ASET is being used, but is not invoked with the "-u /usr/aset/userlist" option, this is a finding. Check the /usr/aset/userlist file. # ls -lL /usr/aset/userlist If /usr/aset/userlist file does not exist, this is a finding. An empty /usr/aset/userlist file, while not optimal, is not a finding.

Fix: F-1109r2_fix

Create the /usr/aset/userlist file and populate it with a list of authorized users.

Generate Mitigation Statement:

Checks: C-28804r1_chk

If ASET is not used on the system, this is not applicable. Check the ownership of the /usr/aset/userlist file. # ls -lL /usr/aset/userlist If the owner of the file is not root, this is a finding.

Fix: F-1110r2_fix

Use the chmod command to change the owner of the /usr/aset/userlist file. # chown root /usr/aset/userlist

Generate Mitigation Statement:

Checks: C-2252r2_chk

# ls -lL /usr/aset/userlist If /usr/aset/userlist has a mode more permissive than 0600, this is a finding.

Fix: F-1111r2_fix

Change the mode of the /usr/aset/userlist file to 0600. # chmod 0600 /usr/aset/userlist

Generate Mitigation Statement:

Checks: C-28454r1_chk

Check for the existence of the cron.allow and cron.deny files. # ls -lL /etc/cron.d/cron.allow # ls -lL /etc/cron.d/cron.deny If neither file exists, this is a finding.

Fix: F-24557r1_fix

Create /etc/cron.d/cron.allow and/or /etc/cron.d/cron.deny with appropriate content.

Generate Mitigation Statement:

Checks: C-28459r1_chk

Check mode of the cron.allow file. Procedure: # ls -lL /etc/cron.d/cron.allow If either file has a mode more permissive than 0600, this is a finding.

Fix: F-24563r1_fix

Change the mode of the cron.allow file to 0600. Procedure: # chmod 0600 /etc/cron.d/cron.allow

Generate Mitigation Statement:

Checks: C-28464r1_chk

List all cronjobs on the system. Procedure: # ls /var/spool/cron/crontabs/ If cron jobs exist under any of the above directories search for programs executed by cron. Procedure: # more &lt;cron job file&gt; Determine if the file is group-writable or world-writable. Procedure: # ls -la &lt;cron program file&gt; If cron executes group-writable or world-writable files, this is a finding.

Fix: F-1130r2_fix

Remove the world-writable and group-writable permissions from the cron program file(s) identified. # chmod go-w <cron program file>

Generate Mitigation Statement:

Checks: C-28466r1_chk

List all cronjobs on the system. Procedure: # ls /var/spool/cron/crontabs/ If cron jobs exist under any of the above directories search for programs executed by cron. Procedure: # more &lt;cron job file&gt; Determine if the directory containing programs executed from cron is world-writable. Procedure: # ls -ld &lt;cron program directory&gt; If cron executes programs in world-writable directories, this is a finding.

Fix: F-1131r2_fix

Remove the world-writable permission from the cron program directories identified. Procedure: # chmod o-w <cron program directory>

Generate Mitigation Statement:

Checks: C-28476r1_chk

Check the mode of the crontab files. # ls -lL /var/spool/cron/crontabs/ If any crontab file has a mode more permissive than 0600, this is a finding.

Fix: F-24579r1_fix

Change the mode of the crontab files. # chmod 0600 /var/spool/cron/crontabs/*

Generate Mitigation Statement:

Checks: C-28478r1_chk

Check the mode of the crontab directory. # ls -ld /var/spool/cron/crontabs If the mode of the crontab directory is more permissive than 0755, this is a finding.

Fix: F-24581r1_fix

Change the mode of the crontab directory. # chmod 0755 /var/spool/cron/crontabs

Generate Mitigation Statement:

Checks: C-28480r1_chk

Check the owner of the crontab directory. # ls -ld /var/spool/cron/crontabs If the owner of the crontab directory is not root or bin, this is a finding.

Fix: F-24583r1_fix

Change the owner of the crontab directory. # chown root /var/spool/cron/crontabs

Generate Mitigation Statement:

Checks: C-28487r1_chk

Check the group owner of the crontab directories. Procedure: # ls -ld /var/spool/cron/crontabs If the directory is not group-owned by root, sys, or bin, this is a finding.

Fix: F-24590r1_fix

Change the group owner of the crontab directories to root, sys, or bin. Procedure: # chgrp root /var/spool/cron/crontabs

Generate Mitigation Statement:

Checks: C-28489r1_chk

# ls -lL /var/cron/log If this file does not exist, or is older than the last cron job, this is a finding. # more /etc/default/cron If a CRONLOG=YES line does not exist, this is a finding.

Fix: F-24594r1_fix

Edit /etc/default/cron and set CRONLOG=YES.

Generate Mitigation Statement:

Checks: C-28497r1_chk

Check the mode of the cron log file. # ls -lL /var/cron/log If the mode is more permissive than 0600, this is a finding.

Fix: F-24598r1_fix

Change the mode of the cron log file. # chmod 0600 /var/cron/log

Generate Mitigation Statement:

Checks: C-28530r1_chk

Check for the existence of at.allow and at.deny files. # ls -lL /etc/cron.d/at.allow # ls -lL /etc/cron.d/at.deny If neither file exists, this is a finding.

Fix: F-11346r2_fix

Create at.allow and/or at.deny files containing appropriate lists of users to be allowed or denied access to the "at" daemon.

Generate Mitigation Statement:

Checks: C-28534r1_chk

# more /etc/cron.d/at.deny If the at.deny file exists and is empty, this is a finding.

Fix: F-1139r2_fix

Add appropriate users to the at.deny file, or remove the empty at.deny file if an at.allow file exists.

Generate Mitigation Statement:

Checks: C-28540r1_chk

# more /etc/cron.d/at.allow If default accounts (such as bin, sys, adm, and others) are listed in the at.allow file, this is a finding.

Fix: F-1140r2_fix

Remove the default accounts (such as bin, sys, adm, and others) from the at.allow file.

Generate Mitigation Statement:

Checks: C-28547r1_chk

Check the mode of the at.allow file. # ls -lL /etc/cron.d/at.allow If the at.allow file has a mode more permissive than 0600, this is a finding.

Fix: F-24632r1_fix

Change the mode of the at.allow file. # chmod 0600 /etc/cron.d/at.allow

Generate Mitigation Statement:

Checks: C-39267r1_chk

List the "at" jobs on the system. Procedure: # ls -la /var/spool/cron/atjobs For each "at" job file, determine which programs are executed. Procedure: # more &lt;at job file&gt; Check each program executed by "at" for group- or world-writable permissions. Procedure: # ls -la &lt;at program file&gt; If "at" executes group- or world-writable programs, this is a finding.

Fix: F-1142r2_fix

Remove group-write and world-write permissions from files executed by "at" jobs. Procedure: # chmod go-w <file>

Generate Mitigation Statement:

Checks: C-39268r1_chk

List any "at" jobs on the system. Procedure: # ls /var/spool/cron/atjobs For each "at" job, determine which programs are executed. Procedure: # more &lt;at job file&gt; Check the directory containing each program executed by "at" for world-writable permissions. Procedure: # ls -la &lt;at program file directory&gt; If "at" executes programs in world-writable directories, this is a finding.

Fix: F-1143r2_fix

Remove the world-writable permission from directories containing programs executed by "at". Procedure: # chmod o-w <at program directory>

Generate Mitigation Statement:

Checks: C-39118r1_chk

Check the mode of the SNMP daemon configuration files. Procedure: # ls -lL /etc/sma/snmp/snmpd.conf /etc/snmp/conf/snmpd.conf /var/sma_snmp/snmpd.conf /usr/sfw/lib/sma_snmp/snmpd.conf If any of the snmpd.conf files have a mode more permissive than 0600, this is a finding.

Fix: F-1148r2_fix

Change the mode of the SNMP daemon configuration file to 0600. Procedure: # chmod 0600 <snmpd.conf>

Generate Mitigation Statement:

Checks: C-39541r1_chk

Check the modes for all Management Information Base (MIB) files on the system. # find /etc/sma/snmp/ /etc/snmp/conf/ /var/sma_snmp/ /usr/sfw/lib/sma_snmp/ -type f | grep -i mib | egrep -v '\.conf$' | xargs ls -lL If any file is returned that does not have mode 0640 or less permissive, this is a finding.

Fix: F-1149r2_fix

Change the mode of MIB files to 0640. Procedure: # chmod 0640 <mib file>

Generate Mitigation Statement:

Checks: C-467r3_chk

Check the system for world-writable files and directories. Procedure: # find / -perm -2 -a \( -type d -o -type f \) -exec ls -ld {} \; If any world-writable files or directories are located, except those required for proper system or application operation, such as /tmp and /dev/null, this is a finding.

Fix: F-1164r2_fix

Remove or change the mode for any world-writable file or directory on the system that is not required to be world-writable. Procedure: # chmod o-w <file/directory> Document all changes.

Generate Mitigation Statement:

Checks: C-2043r2_chk

# ps -ef | egrep "innd|nntpd" If an INN server is running, this is a finding.

Fix: F-1177r2_fix

Disable the INN server.

Generate Mitigation Statement:

Checks: C-40643r1_chk

Verify the SWAT daemon is running under inetd. # svcs swat If SWAT is disabled or not installed, this is not applicable. Verify that TCP_wrappers is enabled for the SWAT daemon. # inetadm -l swat | grep tcp_wrappers If the tcp_wrappers value is unset or is set to FALSE, this is a finding. Verify access to the SWAT daemon is limited to localhost through the use of TCP_Wrappers. # more /etc/hosts.allow # more /etc/hosts.deny If the hosts.allow and hosts.deny access control files are configured such that remote access to SWAT is enabled, this is a finding. Ask the SA if SSH port forwarding is used to enable remote access to SWAT. If it is, this is not a finding. If all access to SWAT is via localhost using a local web browser, this is not a finding.

Fix: F-35945r1_fix

Enable tcp_wrappers for the SWAT daemon. # inetadm -m swat tcp_wrappers=true OR # inetadm -M tcp_wrappers=true Relfresh the inetd daemon. # svcadm refresh inetd Configure the hosts.allow and hosts.deny files to limit access to SWAT to localhost. Example: # echo ALL: ALL >> /etc/hosts.deny # echo swat: localhost >> /etc/hosts.allow

Generate Mitigation Statement:

Checks: C-39145r2_chk

Check the ownership of the smb.conf file. Default locations for this file include /etc, /etc/sfw, /etc/samba, and /etc/sfw/samba. If the system has Samba installed in non-standard locations, also check the smb.conf in those locations. Procedure: # ls -l /etc/smb.conf /etc/sfw/smb.conf /etc/samba/smb.conf /etc/sfw/samba/smb.conf If a smb.conf file is not owned by root, this is a finding.

Fix: F-34289r2_fix

Change the ownership of the smb.conf file. Procedure: # chown root /etc/smb.conf /etc/sfw/smb.conf /etc/samba/smb.conf /etc/sfw/samba/smb.conf

Generate Mitigation Statement:

Checks: C-39146r2_chk

Check the mode of the smb.conf file. Default locations for this file include /etc, /etc/sfw, /etc/samba, and /etc/sfw/samba. If the system has Samba installed in non-standard locations, also check the smb.conf in those locations. Procedure: # ls -lL /etc/smb.conf /etc/sfw/smb.conf /etc/samba/smb.conf /etc/sfw/samba/smb.conf If the smb.conf has a mode more permissive than 0644, this is a finding.

Fix: F-34291r2_fix

Change the mode of the smb.conf file to 0644 or less permissive. Procedure: # chmod 0644 /etc/smb.conf /etc/sfw/smb.conf /etc/samba/smb.conf /etc/sfw/samba/smb.conf

Generate Mitigation Statement:

Checks: C-39130r1_chk

Check the ownership of the smbpasswd file. # ls -lL /etc/sfw/private/smbpasswd If the smbpasswd file is not owned by root, this is a finding.

Fix: F-34280r1_fix

Use the chown command to configure the smb passwd file. # chown root /etc/sfw/private/smbpasswd

Generate Mitigation Statement:

Checks: C-39151r3_chk

Examine the smb.conf file. Default locations for this file include /etc, /etc/sfw, /etc/samba, and /etc/sfw/samba. If the system has Samba installed in non-standard locations, also check the smb.conf in those locations. Procedure: # more /etc/smb.conf /etc/sfw/smb.conf /etc/samba/smb.conf /etc/sfw/samba/smb.conf If the hosts option is not present to restrict access to a list of authorized hosts and networks, this is a finding.

Fix: F-1184r4_fix

Edit the smb.conf file and set the hosts option to permit only authorized hosts to access Samba.

Generate Mitigation Statement:

Checks: C-38680r1_chk

Check the minimum time period between password changes for each user account is 1 day or greater. # awk -F: '$4 &lt; 1 {print $1}' /etc/shadow If any results are returned that are not associated with a system account, this is a finding.

Fix: F-33968r1_fix

Edit the /etc/default/passwd file and set the variable "MINWEEKS" to 1 or greater. Set the per-user minimum password change times by using the following command on each user account. # passwd -n <number of days> <accountname>

Generate Mitigation Statement:

Checks: C-38681r1_chk

Determine if the SSH daemon is configured to permit root logins. Procedure: # grep -v "^#" /etc/ssh/sshd_config | grep -i permitrootlogin If the PermitRootLogin entry is not found or is not set to "no", this is a finding.

Fix: F-24426r1_fix

Edit the configuration file and set the PermitRootLogin option to no.

Generate Mitigation Statement:

Checks: C-28265r1_chk

Check the mode of audio devices. # ls -lL /dev/audio If the mode of audio devices are more permissive than 0660, this is a finding.

Fix: F-34401r1_fix

Change the mode of the audio device. # chmod -R 0660 /dev/audio

Generate Mitigation Statement:

Checks: C-28271r1_chk

Check the owner of audio devices. # ls -lL /dev/audio If the owner of any audio device file is not root, this is a finding.

Fix: F-1203r2_fix

Change the owner of the audio device. # chown root <audio device>

Generate Mitigation Statement:

Checks: C-38910r4_chk

Check the group ownership of the smb.conf file. Default locations for this file include /etc, /etc/sfw, /etc/samba, and /etc/sfw/samba. If the system has Samba installed in non-standard locations, also check the smb.conf in those locations. Procedure: # ls -l /etc/smb.conf /etc/sfw/smb.conf /etc/samba/smb.conf /etc/sfw/samba/smb.conf If an smb.conf file is not group-owned by root, bin, or sys, this is a finding.

Fix: F-34290r4_fix

Change the group owner of the smb.conf file. Procedure: # chgrp root /etc/smb.conf /etc/sfw/smb.conf /etc/samba/smb.conf /etc/sfw/samba/smb.conf

Generate Mitigation Statement:

Checks: C-39131r1_chk

Check smbpasswd ownership. # ls -lL /etc/sfw/private/smbpasswd If smbpasswd is not group-owned by root, this is a finding.

Fix: F-34282r1_fix

Use the chgrp command to ensure the group owner of the smbpasswd file is root. # chgrp root /etc/sfw/private/smbpasswd

Generate Mitigation Statement:

Checks: C-39133r1_chk

Check smbpasswd mode. Procedure: # ls -lL /etc/sfw/private/smbpasswd If smbpasswd has a mode more permissive than 0600, this is a finding.

Fix: F-34284r1_fix

Change the mode of the smbpasswd file to 0600. Procedure: # chmod 0600 /etc/sfw/private/smbpasswd

Generate Mitigation Statement:

Checks: C-28283r1_chk

Check the group-owner of audio devices. Procedure: # ls -lL /dev/audio If the group-owner of an audio device is not root, sys, or bin, this is a finding.

Fix: F-1215r2_fix

Change the group owner of the audio device. Procedure: # chgrp system <audio device>

Generate Mitigation Statement:

Checks: C-38684r3_chk

Examine the dtsession timeout variable setting: # cat /etc/dt/config/C/sys.resources | grep -i dtsession | grep -i lockTimeout If the dtsession timeout is greater than 15, commented or does not exist, this is a finding. Examine the Open Windows timeout settings, both global and for every user. # cat /usr/openwin/lib/app-defaults/XScreenSaver | egrep -i '\*(lock|timeout):' If the global Open Windows timeout is greater than 15 minutes, commented or does not exist, this is a finding. If the global lock setting is not true, this is a finding. # cut -d: -f6 /etc/passwd | xargs -iX egrep -i '^(lock|timeout):' X/.xscreensaver If the Open Windows timeout is greater than 15 minutes for any user, this is a finding. If the lock setting is not true for any user, this is a finding.

Fix: F-33971r1_fix

Configure the CDE lock manager to lock your screen after a certain amount of inactive time. To configure the CDE lock manager to lock the screen after 15 minutes of inactive time, enter the following commands (be sure NOT to overwrite an existing file). # cp /usr/dt/config/C/sys.resources /etc/dt/config/C/sys.resources # vi /etc/dt/config/C/sys.resources Locate and add/uncomment/change the line to N=15. dtsession*lockTimeout: <N> dtsession*lockTimeout: 15 Log out of CDE and log back in to verify that the timeout is in effect. The timeout parameter in /usr/openwin/lib/app-defaults/XScreenSaver and all users' .xscreensaver files should also be confirmed to be uncommented and set to 0:15:00.

Generate Mitigation Statement:

Checks: C-28050r1_chk

Check the HISTORY setting. # grep HISTORY /etc/default/passwd If HISTORY is not set to 5 or more, this is a finding.

Fix: F-24399r1_fix

Edit /etc/default/passwd and set HISTORY to 5.

Generate Mitigation Statement:

Checks: C-38682r1_chk

Check local initialization files for any executed world-writable programs or scripts. Procedure: # find / -perm -002 -type f | egrep -v '^(/proc|/system/contract)' &gt; wwlist # fgrep -f wwlist /&lt;usershomedirectory&gt;/.* If any local initialization file executes a world-writable program or script, this is a finding.

Fix: F-4020r2_fix

Remove the world-writable permission of files referenced by local initialization scripts, or remove the references to these files in the local initialization scripts.

Generate Mitigation Statement:

Checks: C-28185r1_chk

Check run control scripts' ownership. # ls -lL /etc/rc* /etc/init.d If any run control script is not owned by root, this is a finding.

Fix: F-4022r2_fix

Change the ownership of the run control script(s) with incorrect ownership. # chown root <run control script>

Generate Mitigation Statement:

Checks: C-28191r1_chk

Check run control scripts' group ownership. Procedure: # ls -lL /etc/rc* /etc/init.d If any run control script is not group-owned by root, sys, or bin, this is a finding.

Fix: F-24459r1_fix

Change the group ownership of the run control script(s) with incorrect group ownership. Procedure: # chgrp root <run control script>

Generate Mitigation Statement:

Checks: C-28197r2_chk

Determine the programs executed by system start-up files. Determine the ownership of the executed programs. # cat /etc/rc* /etc/init.d/* | more Check the ownership of every program executed by the system start-up files. # ls -l &lt;executed program&gt; If any executed program is not owned by root, sys, bin, or in rare cases, an application account, this is a finding.

Fix: F-34270r1_fix

Change the ownership of the file executed from system startup scripts to root, bin, or sys. # chown root <executed file>

Generate Mitigation Statement:

Checks: C-8285r2_chk

Check /etc/security/audit_user permissions. # ls -lL /etc/security/audit_user If /etc/security/audit_user is more permissive than 0640, this is a finding.

Fix: F-4156r2_fix

Change the mode of the audit_user file to 0640. # chmod 0640 /etc/security/audit_user

Generate Mitigation Statement:

Checks: C-2056r3_chk

On systems with a BIOS or system controller, verify a supervisor or administrator password is set. If a password is not set, this is a finding. If the BIOS or system controller supports user-level access in addition to supervisor/administrator access, determine if this access is enabled. If so, this is a finding. The exact procedure will be hardware-dependent, and the SA should be consulted to identify the specific configuration. In the event the BIOS or system controller is not accessible without adversely impacting (e.g., restarting) the system, the SA may be interviewed to determine compliance with the requirement.

Fix: F-4157r2_fix

Access the system's BIOS or system controller. Set a supervisor/administrator password if one has not been set. Disable a user-level password if one has been set.

Generate Mitigation Statement:

Checks: C-2060r3_chk

This check applies to the global zone only. Determine the type of zone that you are currently securing. # zonename If the command output is "global", this check applies. Check the permission of the menu.lst file. On systems that have a ZFS root, the menu.lst file is typically located at /pool-name/boot/grub/menu.lst where "pool-name" is the mount point for the top-level dataset. On systems that have a UFS root, the menu.lst file is typically located at /boot/grub/menu.lst . Procedure: # ls -lL /pool-name/boot/grub/menu.lst or # ls -lL /boot/grub/menu.lst If menu.lst has a mode more permissive than 0600, this is a finding.

Fix: F-25796r2_fix

Change the mode of the menu.lst file to 0600. # chmod 0600 /pool-name/boot/grub/menu.lst or # chmod 0600 /boot/grub/menu.lst

Generate Mitigation Statement:

Checks: C-2090r3_chk

Check the system for unnecessary user accounts. Procedure: # more /etc/passwd Some examples of unnecessary accounts include games, news, gopher, ftp, and lp. If an unnecessary account is found and its use is not justified and documented with the ISSO, this is a finding.

Fix: F-4180r2_fix

 Remove all unnecessary accounts, such as games, from the /etc/passwd file before connecting a system to the network. Other accounts, such as news and gopher, associated with a service not in use should also be removed.

Generate Mitigation Statement:

Checks: C-2092r2_chk

Check /etc/news/hosts.nntp permissions. # ls -lL /etc/news/hosts.nntp If /etc/news/hosts.nntp has a mode more permissive than 0600, this is a finding.

Fix: F-4184r2_fix

Change the mode of the /etc/news/hosts.nntp file to 0600. # chmod 0600 /etc/news/hosts.nntp

Generate Mitigation Statement:

Checks: C-2093r2_chk

Check /etc/news/hosts.nntp.nolimit permissions. # ls -lL /etc/news/hosts.nntp.nolimit If /etc/news/hosts.nntp.nolimit has a mode more permissive than 0600, this is a finding.

Fix: F-4185r2_fix

Change the mode of /etc/news/hosts.nntp.nolimit to 0600. # chmod 0600 /etc/news/hosts.nntp.nolimit

Generate Mitigation Statement:

Checks: C-2094r2_chk

Check /etc/news/nnrp.access permissions. # ls -lL /etc/news/nnrp.access If /etc/news/nnrp.access has a mode more permissive than 0600, this is a finding.

Fix: F-4186r2_fix

Change the mode of the /etc/news/nnrp.access file to 0600. # chmod 0600 /etc/news/nnrp.access

Generate Mitigation Statement:

Checks: C-2095r2_chk

Check /etc/news/passwd.nntp permissions. # ls -lL /etc/news/passwd.nntp If /etc/news/passwd.nntp has a mode more permissive than 0600, this is a finding.

Fix: F-4187r2_fix

Change the mode of the /etc/news/passwd.nntp file. # chmod 0600 /etc/news/passwd.nntp

Generate Mitigation Statement:

Checks: C-39298r1_chk

Check the ownership of the files in /etc/news. Procedure: # ls -al /etc/news If the /etc/news directory or any files in it are not owned by root, this is a finding.

Fix: F-34405r1_fix

Change the ownership of the /etc/news directory and the files in it to root. Procedure: # chown -R root /etc/news

Generate Mitigation Statement:

Checks: C-39299r1_chk

Check /etc/news directory and files group ownership. Procedure: # ls -al /etc/news If the /etc/news directory and the files in it are not group-owned by root, this is a finding.

Fix: F-34406r1_fix

Change the group owner of the /etc/news directory and the files in it to root. Procedure: # chgrp -R root /etc/news

Generate Mitigation Statement:

Checks: C-28072r1_chk

Verify no auxiliary consoles are defined. # consadm -p If any output is generated, this is a finding.

Fix: F-24421r1_fix

Remove each auxiliary console. # consadm -d <console device>

Generate Mitigation Statement:

Checks: C-39054r1_chk

To enable NFS server logging the log option must be applied to all exported file systems in the /etc/dfs/dfstab. Perform the following to verify NFS is enabled. # share The preceding command will display all exported filesystems. Each line should contain a log entry to indicate logging is enabled. If the log entry is not present, this is a finding. If the share command does not return anything, then this is not an NFS server and this is considered not applicable. NFS version 4 does not support server logging. Verify NFS_SERVER_VERSMAX in /etc/default/nfs. # grep NFS_SERVER_VERSMAX /etc/default/nfs If NFS_SERVER_VERSMAX is commented out or set to any value but 2 or 3, this is a finding.

Fix: F-34153r1_fix

Edit /etc/dfs/dfstab and add the log option to all exported filesystems. Run the shareall command for the changes to take effect. NFS version 2 or 3 must be forced by updating the NFS_SERVER_VERSMAX variable appropriately in /etc/default/nfs and restarting the NFS daemon.

Generate Mitigation Statement:

Checks: C-39053r4_chk

NTP must be used and used only in the global zone. Determine the zone that you are currently securing. # zonename If the command output is not "global", NTP must be disabled. Check the system for a running NTP daemon. # svcs ntp | grep online If the output from "zonename" is "global", NTP must be enabled. Check the system for a running NTP daemon. # svcs ntp | grep online If NTP is not online, this is a finding. If NTP is running confirm the servers and peers or multicast client (as applicable) are local or an authoritative U.S. DoD source. # more /etc/inet/ntp.conf If a non-local/non-authoritative (U.S. DoD source) time-server is used, this is a finding.

Fix: F-4212r4_fix

Use a local authoritative time server synchronizing to an authorized DoD time source. Ensure all systems in the facility feed from one or more local time servers that feed from the authoritative time server.

Generate Mitigation Statement:

Checks: C-39033r1_chk

Logging should be enabled for those types of files systems that do not turn on logging by default. Procedure: # mount -v UFS, JFS, VXFS, HFS, XFS, reiserfs, EXT3 and EXT4 all turn logging on by default and will not be a finding. The ZFS file system uses other mechanisms to provide for file system consistency, and will not be a finding. For other file systems types, if the root file system does not have the 'logging' option, this is a finding. If the 'nolog' option is set on the root file system, this is a finding.

Fix: F-4215r2_fix

Implement file system journaling for the root file system, or use a file system using other mechanisms to ensure consistency. If the root file system supports journaling, enable it. If the file system does not support journaling or another mechanism to ensure consistency, a migration to a different file system will be necessary.

Generate Mitigation Statement:

Checks: C-8289r2_chk

Perform the following to determine if ASET is being used. # crontab -l |grep aset A returned entry would indicate ASET is being utilized. Determine if ASET is configured to check firewall settings. # grep TASKS /usr/aset/asetenv | grep firewall If an entry is not returned, this is a finding.

Fix: F-4220r2_fix

If the system is used as a firewall and ASET is used, ensure the firewall parameter is configured in /usr/aset/asetenv.

Generate Mitigation Statement:

Checks: C-8288r2_chk

# more /usr/aset/masters/uid_aliases If the /usr/aset/masters/uid_aliases file is not empty or all contents are not commented out, this is a finding.

Fix: F-4223r2_fix

Empty or comment out the entries in the uid_aliases file.

Generate Mitigation Statement:

Checks: C-35834r1_chk

Verify ASET is being used. # crontab -l |grep aset If there is an output, then check to make sure the files in question are in the /usr/aset/masters directory.       #       ls -l /usr/aset/masters The following files should be in the listing: tune.high, tune.low, tune.med, and uid_aliases. If any of the files are not in the directory listing, this is a finding.

Fix: F-4224r2_fix

Install the default ASET configuration files.

Generate Mitigation Statement:

Checks: C-2132r2_chk

Check the system for a running Samba server. Procedure: # ps -ef |grep smbd If the Samba server is running, ask the SA if the Samba server is operationally required. If it is not, this is a finding.

Fix: F-4232r2_fix

If there is no functional need for Samba and the daemon is running, disable the daemon by killing the process ID as noted from the output of ps -ef |grep smbd. The utility should also be removed or not installed if there is no functional requirement.

Generate Mitigation Statement:

Checks: C-8283r2_chk