Solaris 10 SPARC Security Technical Implementation Guide

Version

GEN000000-SOL00120

Vuln IDs

V-220017
V-4313

Rule IDs

SV-220017r505925_rule
SV-36751

If ASET is used and the master files (tune.high, tune.med, tune.low, and uid_aliases) are not located in the proper place, ASET cannot operate correctly and valuable security findings could be lost.

Checks: C-21726r503771_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-21725r503772_fix

Install the default ASET configuration files.

The asetenv file YPCHECK variable must be set to true when NIS+ is configured.

AC-4 - Medium - CCI-000032 - V-220018 - SV-220018r505925_rule

RMF Control

AC-4

Severity

CCI

Version

GEN000000-SOL00200

Vuln IDs

V-220018
V-954

Rule IDs

SV-220018r505925_rule
SV-36750

If YPCHECK is not set to true in asetenv, then ypfiles may not be checked.

Checks: C-21727r482600_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-21726r482601_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.

The system must require authentication upon booting into single-user and maintenance modes.

AC-3 - Medium - CCI-000213 - V-220019 - SV-220019r505925_rule

RMF Control

AC-3

Severity

CCI

CCI-000213

Version

GEN000020

Vuln IDs

V-220019
V-756

Rule IDs

SV-220019r505925_rule
SV-36753

If the system does not require valid root authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged access to all files on the system.

Checks: C-21728r482651_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-21727r482652_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.

Direct logins must not be permitted to shared, default, application, or utility accounts.

IA-2 - Medium - CCI-000770 - V-220020 - SV-220020r505925_rule

RMF Control

IA-2

Severity

CCI

Version

GEN000280

Vuln IDs

V-220020
V-760

Rule IDs

SV-220020r505925_rule
SV-41504

Shared accounts (accounts where two or more people log in with the same user identification) do not provide identification and authentication. There is no way to provide for non-repudiation or individual accountability.

Checks: C-21729r503774_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-21728r503775_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.

The system must disable accounts after three consecutive unsuccessful login attempts.

AC-7 - Medium - CCI-000044 - V-220021 - SV-220021r505925_rule

RMF Control

AC-7

Severity

CCI

CCI-000044

Version

GEN000460

Vuln IDs

V-220021
V-766

Rule IDs

SV-220021r505925_rule
SV-39815

Disabling accounts after a limited number of unsuccessful login attempts improves protection against password guessing attacks.

Checks: C-21730r482726_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-21729r482727_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

The delay between login prompts following a failed login attempt must be at least 4 seconds.

AC-7 - Medium - CCI-002238 - V-220022 - SV-220022r505925_rule

RMF Control

AC-7

Severity

CCI

CCI-002238

Version

GEN000480

Vuln IDs

V-220022
V-768

Rule IDs

SV-220022r505925_rule
SV-27094

Enforcing a delay between successive failed login attempts increases protection against automated password guessing attacks.

Checks: C-21731r482729_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-21730r482730_fix

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

Graphical desktop environments provided by the system must automatically lock after 15 minutes of inactivity and the system must require users to re-authenticate to unlock the environment.

AC-11 - Medium - CCI-000057 - V-220023 - SV-220023r505925_rule

RMF Control

AC-11

Severity

CCI

CCI-000057

Version

GEN000500

Vuln IDs

V-220023
V-4083

Rule IDs

SV-220023r505925_rule
SV-39814

If graphical desktop sessions do not lock the session after 15 minutes of inactivity, requiring re-authentication to resume operations, the system or individual data could be compromised by an alert intruder who could exploit the oversight. This requirement applies to graphical desktop environments provided by the system to locally attached displays and input devices as well as to graphical desktop environments provided to remote systems, including thin clients.

Checks: C-21732r503777_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-21731r503778_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.

Accounts must be locked upon 35 days of inactivity.

AC-2 - Medium - CCI-000017 - V-220024 - SV-220024r505925_rule

RMF Control

AC-2

Severity

CCI

CCI-000017

Version

GEN000760

Vuln IDs

V-220024
V-918

Rule IDs

SV-220024r505925_rule
SV-39824

On some systems, accounts with disabled passwords still allow access using rcp, remsh, or rlogin through equivalent remote hosts. All that is required is the remote host name and the user name match an entry in a hosts.equiv file and have a .rhosts file in the user directory. Using a shell called /bin/false or /dev/null (or an equivalent) will add a layered defense. Non-interactive accounts on the system, such as application accounts, may be documented exceptions.

Checks: C-21733r503780_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 < user account > 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-21732r503781_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 >

The root account must be the only account having an UID of 0.

CM-6 - Medium - CCI-000366 - V-220025 - SV-220025r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000880

Vuln IDs

V-220025
V-773

Rule IDs

SV-220025r505925_rule
SV-39820

If an account has an UID of 0, it has root authority. Multiple accounts with an UID of 0 afford more opportunity for potential intruders to guess a password for a privileged account.

Checks: C-21734r482792_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-21733r482793_fix

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

The root account must not have world-writable directories in its executable search path.

CM-6 - Medium - CCI-000366 - V-220026 - SV-220026r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000960

Vuln IDs

V-220026
V-777

Rule IDs

SV-220026r505925_rule
SV-37075

If the root search path contains a world-writable directory, malicious software could be placed in the path by intruders and/or malicious users and inadvertently run by root with all of root's privileges.

Checks: C-21735r503783_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-21734r503784_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.

Library files must have mode 0755 or less permissive.

CM-5 - Medium - CCI-001499 - V-220028 - SV-220028r505925_rule

RMF Control

CM-5

Severity

CCI

Version

GEN001300

Vuln IDs

V-220028
V-793

Rule IDs

SV-220028r505925_rule
SV-39821

Unauthorized access could destroy the integrity of the library files.

Checks: C-21737r482876_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-21736r482877_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.

All interactive user's home directories must be owned by their respective users.

CM-6 - Medium - CCI-000366 - V-220029 - SV-220029r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001500

Vuln IDs

V-220029
V-902

Rule IDs

SV-220029r505925_rule
SV-39822

If users do not own their home directories, unauthorized users could access user files.

Checks: C-21738r482984_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-21737r482985_fix

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

All interactive user's home directories must be group-owned by the home directory owner's primary group.

CM-6 - Medium - CCI-000366 - V-220030 - SV-220030r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001520

Vuln IDs

V-220030
V-903

Rule IDs

SV-220030r505925_rule
SV-39823

If the GID of the home directory is not the same as the GID of the user, this would allow unauthorized access to files.

Checks: C-21739r482987_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-21738r482988_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.

All global initialization files must have mode 0644 or less permissive.

CM-6 - Medium - CCI-000366 - V-220031 - SV-220031r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001720

Vuln IDs

V-220031
V-11981

Rule IDs

SV-220031r505925_rule
SV-39829

Global initialization files are used to configure the user's shell environment upon login. Malicious modification of these files could compromise accounts upon logon.

Checks: C-21740r483029_chk

Check global initialization files permissions. # ls -l /etc/.login # ls -l /etc/profile # ls -l /etc/bashrc # ls -l /etc/environment # ls -l /etc/security/environ # ls -l /etc/csh.login # ls -l /etc/csh.cshrc If global initialization files exist and are more permissive than 0644, this is a finding.

Fix: F-21739r483030_fix

Change the mode of the global initialization file(s) to 0644. # chmod 0644 <global initialization file>

All global initialization files must be owned by root.

CM-6 - Medium - CCI-000366 - V-220032 - SV-220032r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001740

Vuln IDs

V-220032
V-11982

Rule IDs

SV-220032r505925_rule
SV-39830

Global initialization files are used to configure the user's shell environment upon login. Malicious modification of these files could compromise accounts upon logon. Failure to give ownership of sensitive files or utilities to root or bin provides the designated owner and unauthorized users with the potential to access sensitive information or change the system configuration which could weaken the system's security posture.

Checks: C-21741r483035_chk

Check the ownership of global initialization files. Procedure: # ls -lL /etc/.login /etc/profile /etc/bashrc /etc/environment /etc/security/environ /etc/csh.login /etc/csh.cshrc If any global initialization file exists and is not owned by root, this is a finding.

Fix: F-21740r483036_fix

Change the ownership of global initialization files with incorrect ownership. Procedure: # chown bin <global initialization files>

All global initialization files must be group-owned by root, sys, or bin.

CM-6 - Medium - CCI-000366 - V-220033 - SV-220033r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001760

Vuln IDs

V-220033
V-11983

Rule IDs

SV-220033r505925_rule
SV-39831

Checks: C-21742r483038_chk

Check the group ownership of global initialization files. Procedure: # ls -lL /etc/.login /etc/profile /etc/bashrc /etc/environment /etc/security/environ /etc/csh.login /etc/csh.cshrc If any global initialization file exists and is not group-owned by root, sys, or bin, this is a finding.

Fix: F-21741r483039_fix

Change the group ownership of the global initialization file(s) with incorrect group ownership. Procedure: # chgrp root <global initialization file>

Global initialization files must contain the mesg -n or mesg n commands.

CM-6 - Low - CCI-000366 - V-220034 - SV-220034r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001780

Vuln IDs

V-220034
V-825

Rule IDs

SV-220034r505925_rule
SV-39828

If the mesg -n or mesg n command is not placed into the system profile, messaging can be used to cause a Denial of Service attack.

Checks: C-21743r483041_chk

Check global initialization files for the presence of "mesg -n" or "mesg n". Procedure: # grep mesg /etc/.login /etc/profile /etc/bashrc /etc/environment /etc/security/environ /etc/csh.login /etc/csh.cshrc If no existing global initialization files contain "mesg -n" or "mesg n", this is a finding.

Fix: F-21742r483042_fix

Edit /etc/profile or another global initialization script and add the mesg -n command.

Local initialization files must be group-owned by the user's primary group or root.

CM-6 - Medium - CCI-000366 - V-220035 - SV-220035r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001870

Vuln IDs

V-220035
V-22361

Rule IDs

SV-220035r505925_rule
SV-37101

Local initialization files are used to configure the user's shell environment upon login. Malicious modification of these files could compromise accounts upon logon.

Checks: C-21744r483068_chk

Check user home directories for local initialization files group-owned by a group other than the user's primary group or root. 1. List user accounts and their primary GID. # cut -d : -f 1,4 /etc/passwd 2. Check local initialization files for each user. # ls -al /<usershomedirectory>/.login # ls -al /<usershomedirectory>/.cshrc # ls -al /<usershomedirectory>/.logout # ls -al /<usershomedirectory>/.profile # ls -al /<usershomedirectory>/.bash_profile # ls -al /<usershomedirectory>/.bashrc # ls -al /<usershomedirectory>/.bash_logout # ls -al /<usershomedirectory>/.env # ls -al /<usershomedirectory>/.dtprofile # ls -al /<usershomedirectory>/.dispatch # ls -al /<usershomedirectory>/.emacs # ls -al /<usershomedirectory>/.exrc # find /<usershomedirectory>/.dt ! -fstype nfs ! -group <primary_group> -exec ls -ld {} \; 3. If any file is not group-owned by root or the user's primary GID, this is a finding.

Fix: F-21743r483069_fix

Change the group-owner of the local initialization file to the user's primary group, or root. # chgrp [USER's primary GID] ~USER/[local initialization file]

Removable media, remote file systems, and any file system that does not contain approved setuid files must be mounted with the "nosuid" option.

CM-7 - Medium - CCI-001764 - V-220036 - SV-220036r505925_rule

RMF Control

CM-7

Severity

CCI

CCI-001764

Version

GEN002420

Vuln IDs

V-220036
V-805

Rule IDs

SV-220036r505925_rule
SV-39813

The "nosuid" mount option causes the system to not execute setuid files with owner privileges. This option must be used for mounting any file system that does not contain approved setuid files. Executing setuid files from untrusted file systems, or file systems that do not contain approved setuid files, increases the opportunity for unprivileged users to attain unauthorized administrative access.

Checks: C-21745r503786_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-21744r503787_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 >

The system must not be configured for network bridging.

CM-6 - Medium - CCI-000366 - V-220037 - SV-220037r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003619

Vuln IDs

V-220037
V-22421

Rule IDs

SV-220037r505925_rule
SV-42308

Some systems have the ability to bridge or switch frames (link-layer forwarding) between multiple interfaces. This can be useful in a variety of situations but, if enabled when not needed, has the potential to bypass network partitioning and security.

Checks: C-21746r484984_chk

Ask the system administrator if network bridging software is installed on the system or the system is configured for network bridging. If network bridging software is installed or the system is configured for network bridging, this is a finding.

Fix: F-21745r484985_fix

Remove the network bridging software and configuration from the system.

The portmap or rpcbind service must not be running unless needed.

CM-6 - Medium - CCI-000366 - V-220038 - SV-220038r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003810

Vuln IDs

V-220038
V-22429

Rule IDs

SV-220038r505925_rule
SV-26664

The portmap and rpcbind services increase the attack surface of the system and should only be used when needed. The portmap or rpcbind services are used by a variety of services using remote procedure calls (RPCs).

Checks: C-21747r485035_chk

Check the status of the rpcbind service. # svcs network/rpc/bind If the service is online and is not documented as required, this is a finding.

Fix: F-21746r485036_fix

Disable the portmap service. # svcadm disable network/rpc/bind

The rsh daemon must not be running.

AC-17 - High - CCI-000068 - V-220039 - SV-220039r505925_rule

RMF Control

AC-17

Severity

CCI

Version

GEN003820

Vuln IDs

V-220039
V-4687

Rule IDs

SV-220039r505925_rule
SV-27435

The rshd process provides a typically unencrypted, host-authenticated remote access service. SSH should be used in place of this service. Satisfies: SRG-OS-000033, SRG-OS-000505, SRG-OS-000555

Checks: C-21748r485041_chk

# svcs network/shell If the service is enabled, this is a finding.

Fix: F-21747r485042_fix

Disable the remote shell service and restart inetd. Procedure: # svcadm disable network/shell # svcadm refresh inetd

The rlogind service must not be running.

AC-17 - Medium - CCI-000068 - V-220040 - SV-220040r505925_rule

RMF Control

AC-17

Severity

CCI

Version

GEN003830

Vuln IDs

V-220040
V-22432

Rule IDs

SV-220040r505925_rule
SV-39863

The rlogind process provides a typically unencrypted, host-authenticated remote access service. SSH should be used in place of this service. Satisfies: SRG-OS-000033, SRG-OS-000505, SRG-OS-000555

Checks: C-21749r485047_chk

Determine if the rlogind service is running. # svcs rlogin If the rlogin service is enabled, this is a finding.

Fix: F-21748r485048_fix

Disable the rlogind service. # svcadm disable rlogin # svcadm refresh inetd

Network analysis tools must not be installed.

CM-7 - Medium - CCI-000381 - V-220041 - SV-220041r505925_rule

RMF Control

CM-7

Severity

CCI

Version

GEN003865

Vuln IDs

V-220041
V-12049

Rule IDs

SV-220041r505925_rule
SV-40811

Network analysis tools allow for the capture of network traffic visible to the system.

Checks: C-21750r485065_chk

Determine if any network analysis tools are installed. Procedure: # find / -name ethereal # find / -name wireshark # find / -name tshark # find / -name netcat # find / -name tcpdump # find / -name snoop If any network analysis tools are found, this is a finding.

Fix: F-21749r485066_fix

Remove the network analysis tool binary from the system. The snoop binary is part of the SUNWrcmdc package, which may also be removed if none of its components are required. Procedure: # rm <binary> # pkgrm SUNWrcmdc

The hosts.lpd (or equivalent) file must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-220043 - SV-220043r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003930

Vuln IDs

V-220043
V-22435

Rule IDs

SV-220043r505925_rule
SV-37456

Failure to give group ownership of the hosts.lpd (or equivalent) file to root, bin, sys, or system provides the members of the owning group and possible unauthorized users, with the potential to modify it. Unauthorized modifications could disrupt access to local printers from authorized remote hosts or permit unauthorized remote access to local printers.

Checks: C-21752r485073_chk

Check the group ownership of the print service configuration files. Procedure: # ls -lL /etc/printers.conf /etc/apache/httpd-standalone-ipp.conf /etc/smb.conf /etc/sfw/smb.conf /etc/samba/smb.conf /etc/sfw/samba/smb.conf If the files are not group-owned by root, bin, or sys, this is a finding.

Fix: F-21751r485074_fix

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

The aliases file must be group-owned by root, sys, smmsp, or bin.

CM-6 - Medium - CCI-000366 - V-220045 - SV-220045r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004370

Vuln IDs

V-220045
V-22438

Rule IDs

SV-220045r505925_rule
SV-37458

If the alias file is not group-owned by root or a system group, an unauthorized user may modify the file to add aliases to run malicious code or redirect email.

Checks: C-21754r485099_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 group ownership 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 file is not group-owned by root, sys, smmsp, or bin, this is a finding.

Fix: F-21753r485100_fix

Change the group owner of the /etc/mail/aliases files. Procedure: # chgrp bin /etc/mail/aliases # chgrp smmsp /etc/mail/aliases.db

The SMTP service HELP command must not be enabled.

CM-6 - Medium - CCI-000366 - V-220046 - SV-220046r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004540

Vuln IDs

V-220046
V-12006

Rule IDs

SV-220046r505925_rule
SV-42309

The HELP command should be disabled to mask version information. The version of the SMTP service software could be used by attackers to target vulnerabilities present in specific software versions.

Checks: C-21755r485132_chk

Check if Help is disabled in Sendmail. Procedure: # telnet <host> 25 > help If the help command returns any Sendmail version information, this is a finding. If telnet is unavailable for testing, check the value of the HelpFile parameter in the sendmail.cf file. # grep HelpFile /etc/mail/sendmail.cf If the contents of the file indicated by the HelpFile parameter contains any Sendmail version information, this is a finding.

Fix: F-21754r485133_fix

To disable the SMTP HELP command, clear the Sendmail help file. # echo > /etc/mail/helpfile

The SMTP services SMTP greeting must not provide version information.

CM-6 - Low - CCI-000366 - V-220047 - SV-220047r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004560

Vuln IDs

V-220047
V-4384

Rule IDs

SV-220047r505925_rule
SV-42310

The version of the SMTP service can be used by attackers to plan an attack based on vulnerabilities present in the specific version.

Checks: C-21756r503789_chk

Check for the Sendmail version being displayed in the greeting. # telnet localhost 25 If a version number is displayed, this is a finding. If telnet is unavailable for testing, check the value of the SmtpGreetingMessage parameter in the sendmail.cf file. # grep SmtpGreetingMessage /etc/mail/sendmail.cf If the value of the SmtpGreetingMessage parameter contains the $v or $Z macros, this is a finding.

Fix: F-21755r503790_fix

Ensure Sendmail or its equivalent has been configured to mask the version information. If necessary, change the O SmtpGreetingMessage line in the /etc/mail/sendmail.cf file as noted below. O SmtpGreetingMessage=$j Sendmail $v/$Z; $b Change it to: O SmtpGreetingMessage= Mail Server Ready ; $b

The system must not use .forward files.

CM-6 - Medium - CCI-000366 - V-220048 - SV-220048r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004580

Vuln IDs

V-220048
V-4385

Rule IDs

SV-220048r505925_rule
SV-39827

The .forward file allows users to automatically forward mail to another system. Use of .forward files could allow the unauthorized forwarding of mail and could potentially create mail loops which could degrade system performance.

Checks: C-21757r485138_chk

Search for any .forward files on the system. # find / -name .forward -print This is considered a finding if any .forward files are found on the system.

Fix: F-21756r485139_fix

Remove .forward files from the system. # rm .forward Update the sendmail.cf file to ignore .forward files by adding ForwardPath="".

The SMTP service must be an up-to-date version.

CM-6 - High - CCI-000366 - V-220049 - SV-220049r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004600

Vuln IDs

V-220049
V-4689

Rule IDs

SV-220049r505925_rule
SV-39819

The SMTP service version on the system must be current to avoid exposing vulnerabilities present in unpatched versions.

Checks: C-21758r485141_chk

Determine the version of the SMTP service software, using a non-privileged account. $ /usr/lib/sendmail -d0 -bt < /dev/null (Note: While this command will report the sendmail version almost immediately, it will take several moments to return to the shell prompt. Press ctrl-C to terminate the sendmail process.) Version 8.14.4 is the latest required version. Version 8.14.4+Sun is available from Oracle for Solaris. If the sendmail version is not at least 8.14.4 or Oracle's latest version, this is a finding.

Fix: F-21757r485142_fix

Obtain and install the latest version of Sendmail from Oracle through normal software update processes, as implemented locally.

The Sendmail server must have the debug feature disabled.

CM-6 - High - CCI-000366 - V-220050 - SV-220050r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004620

Vuln IDs

V-220050
V-4690

Rule IDs

SV-220050r505925_rule
SV-42311

Debug mode is a feature present in older versions of Sendmail which, if not disabled, may allow an attacker to gain access to a system through the Sendmail service.

Checks: C-21759r485144_chk

Check for an enabled debug command provided by the SMTP service. Procedure: # telnet localhost 25 debug If the command does not return a 500 error code of command unrecognized, this is a finding. If telnet is unavailable for testing, check the version of sendmail. Run the following as a non-privileged user. $ echo \$Z | /usr/sbin/sendmail -bt -d0 If the version reported is less than 8.6, this is a finding.

Fix: F-21758r485145_fix

Obtain and install a more recent version of Sendmail, which does not implement the DEBUG feature.

The SMTP service must not have a uudecode alias active.

CM-7 - High - CCI-000381 - V-220051 - SV-220051r505925_rule

RMF Control

CM-7

Severity

CCI

Version

GEN004640

Vuln IDs

V-220051
V-4691

Rule IDs

SV-220051r505925_rule
SV-42312

A common configuration for older Mail Transfer Agents (MTAs) includes an alias for the decode user. All mail sent to this user is sent to the uudecode program, which automatically converts and stores files. By sending mail to decode or uudecode aliases present on some systems, a remote attacker may be able to create or overwrite files on the remote host. This could possibly be used to gain remote access.

Checks: C-21760r485147_chk

Check the SMTP service for an active decode command. Procedure: # telnet localhost 25 decode If the command does not return a 500 error code of command unrecognized, this is a finding. If telnet is unavailable for testing, check for the existence of the decode and uudecode aliases in the sendmail aliases file. Find the active sendmail aliases file. # grep AliasFile /etc/mail/sendmail.cf (The aliases file is usually at /etc/mail/aliases) Look for decode aliases in the aliases file. # grep decode /etc/mail/aliases If there is an uncommented decode or uudecode alias in the aliases file, this is a finding.

Fix: F-21759r485148_fix

Comment out active decode and uudecode aliases in the aliases file. # vi /usr/mail/aliases Activate updated aliases file. # newaliases

The TFTP daemon must be configured to vendor specifications, including a dedicated TFTP user account, a non-login shell, such as /bin/false, and a home directory owned by the TFTP user.

CM-6 - Medium - CCI-000366 - V-220052 - SV-220052r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005120

Vuln IDs

V-220052
V-849

Rule IDs

SV-220052r505925_rule
SV-39825

If TFTP has a valid shell, it increases the likelihood of someone logging to the TFTP account and compromising the system.

Checks: C-21761r485207_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-21760r485208_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.

The system must not be used as a syslog server (log host) for systems external to the enclave.

CM-6 - Medium - CCI-000366 - V-220053 - SV-220053r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005440

Vuln IDs

V-220053
V-12020

Rule IDs

SV-220053r505925_rule
SV-41515

Syslog messages are typically unencrypted and may contain sensitive information and are, therefore, restricted to the enclave.

Checks: C-21762r485276_chk

Ask the SA if the log host server is collecting data for hosts outside the local enclave. If it is, this is a finding.

Fix: F-21761r485277_fix

Configure the hosts outside of the local enclave to not log to this system.

The syslog daemon must not accept remote messages unless it is a syslog server documented using site-defined procedures.

CM-6 - Medium - CCI-000366 - V-220054 - SV-220054r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005480

Vuln IDs

V-220054
V-12021

Rule IDs

SV-220054r505925_rule
SV-28431

Unintentionally running a syslog server accepting remote messages puts the system at increased risk. Malicious syslog messages sent to the server could exploit vulnerabilities in the server software itself, could introduce misleading information in to the system's logs, or could fill the system's storage leading to a Denial of Service.

Checks: C-21763r485285_chk

# svcprop system-log | grep log_from_remote If the config/log_from_remote value is not false, this is a finding.

Fix: F-21762r485286_fix

# svccfg -s system-log setprop config/log_from_remote=false # svcadm refresh system-log

The SSH daemon must be configured to only use the SSHv2 protocol.

IA-2 - High - CCI-001941 - V-220055 - SV-220055r505925_rule

RMF Control

IA-2

Severity

CCI

CCI-001941

Version

GEN005500

Vuln IDs

V-220055
V-4295

Rule IDs

SV-220055r505925_rule
SV-39817

SSHv1 is not a DoD-approved protocol and has many well-known vulnerability exploits. Exploits of the SSH daemon could provide immediate root access to the system.

Checks: C-21764r485288_chk

Check the SSH daemon configuration for allowed protocol versions. # grep -i protocol /etc/ssh/sshd_config | grep -v '^#' If the variables Protocol 2,1 or Protocol 1 are defined on a line without a leading comment, this is a finding.

Fix: F-21763r485289_fix

Edit the configuration file and modify the Protocol line to look like: Protocol 2 Reload sshd: kill -HUP <PID of sshd>

IP forwarding for IPv4 must not be enabled, unless the system is a router.

CM-6 - Medium - CCI-000366 - V-220056 - SV-220056r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005600

Vuln IDs

V-220056
V-12023

Rule IDs

SV-220056r505925_rule
SV-28581

If the system is configured for IP forwarding and is not a designated router, it could be used to bypass network security by providing a path for communication not filtered by network devices.

Checks: C-21765r485357_chk

Determine if the system is configured for IPv4 forwarding. # svcs | grep svc:/network/ipv4-forwarding If the service is enabled, this is a finding.

Fix: F-21764r485358_fix

Disable IPv4 forwarding on the system. # svcadm disable svc:/network/ipv4-forwarding

The system must not have IP forwarding for IPv6 enabled, unless the system is an IPv6 router.

CM-6 - Medium - CCI-000366 - V-220057 - SV-220057r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005610

Vuln IDs

V-220057
V-22491

Rule IDs

SV-220057r505925_rule
SV-26810

If the system is configured for IP forwarding and is not a designated router, it could be used to bypass network security by providing a path for communication not filtered by network devices.

Checks: C-21766r485360_chk

Check if the system is configured for IPv6 forwarding. # ndd /dev/ip6 ip6_forwarding If the value is not 0, this is a finding.

Fix: F-21765r485361_fix

Disable IPv6 forwarding. # ndd -set /dev/ip6 ip6_forwarding 0 Edit startup scripts as necessary; add this command or remove commands setting the value to 1.

The NFS server must be configured to restrict file system access to local hosts.

CM-6 - Medium - CCI-000366 - V-220058 - SV-220058r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005840

Vuln IDs

V-220058
V-933

Rule IDs

SV-220058r505925_rule
SV-40305

The NFS access option limits user access to the specified level. This assists in protecting exported file systems. If access is not restricted, unauthorized hosts may be able to access the system's NFS exports.

Checks: C-21767r485384_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-21766r485385_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.

The system must not have a public Instant Messaging (IM) client installed.

CM-6 - Medium - CCI-000366 - V-220059 - SV-220059r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006000

Vuln IDs

V-220059
V-12024

Rule IDs

SV-220059r505925_rule
SV-41525

Public Instant Messaging (IM) systems are not approved for use and may result in the unauthorized distribution of information. IM clients provide a way for a user to send a message to one or more other users in real time. Additional capabilities may include file transfer and support for distributed game playing. Communication between clients and associated directory services are managed through messaging servers. Commercial IM clients include AOL Instant Messenger (AIM), MSN Messenger, and Yahoo! Messenger. IM clients present a security issue when the clients route messages through public servers. The obvious implication is potentially sensitive information could be intercepted or altered in the course of transmission. This same issue is associated with the use of public email servers. In order to reduce the potential for disclosure of sensitive Government information and to ensure the validity of official government information, IM clients connecting to public IM services will not be installed. Clients used to access internal or DoD-controlled IM services are permitted.

Checks: C-21768r485396_chk

If an IM client is installed, ask the SA if it has access to any public domain IM servers. If it does have access to public servers, this is a finding.

Fix: F-21767r485397_fix

Uninstall the IM client from the system, or configure the client to only connect to DoD-approved IM services.

The Samba Web Administration Tool (SWAT) must be restricted to the local host or require SSL.

CM-7 - Medium - CCI-000381 - V-220060 - SV-220060r505925_rule

RMF Control

CM-7

Severity

CCI

Version

GEN006080

Vuln IDs

V-220060
V-1026

Rule IDs

SV-220060r505925_rule
SV-42313

SWAT is a tool used to configure Samba. As it modifies Samba configuration, which can impact system security, it must be protected from unauthorized access. SWAT authentication may involve the root password, which must be protected by encryption when traversing the network. Restricting access to the local host allows for the use of SSH TCP forwarding, if configured, or administration by a web browser on the local system.

Checks: C-21769r503792_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-21768r503793_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

The system must have a host-based intrusion detection tool installed.

SI-2 - Medium - CCI-001233 - V-220061 - SV-220061r505925_rule

RMF Control

SI-2

Severity

CCI

CCI-001233

Version

GEN006480

Vuln IDs

V-220061
V-782

Rule IDs

SV-220061r505925_rule
SV-41526

Without a host-based intrusion detection tool, there is no system-level defense when an intruder gains access to a system or network. Additionally, a host-based intrusion detection tool can provide methods to immediately lock out detected intrusion attempts.

Checks: C-21770r485489_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 <daemon name> -print Determine if the application is active on the system. Procedure: # ps -ef | grep <daemon name> If no host-based intrusion detection system is installed on the system, this is a finding.

Fix: F-21769r485490_fix

Install a host-based intrusion detection tool.

The system vulnerability assessment tool, host-based intrusion detection tool, and file integrity tool must notify the SA and the IAO of a security breach or a suspected security breach.

CM-6 - Medium - CCI-000366 - V-220062 - SV-220062r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006560

Vuln IDs

V-220062
V-12028

Rule IDs

SV-220062r505925_rule
SV-41530

Timely notifications of potential security compromises minimize the potential damage. Minimally, the system must log these events and the SA and the IAO will receive the notifications during the daily system log review. If feasible, active alerting (such as email or paging) should be employed consistent with the site's established operations management systems and procedures.

Checks: C-21771r503795_chk

For each security tool on the system, determine if the tool is configured to notify the IAO and SA of any detected security problem. If such notifications are not configured, this is a finding.

Fix: F-21770r503796_fix

Configure the security tools on the system to notify the IAO and SA when any security issues are detected.

The system package management tool must be used to verify system software periodically.

CM-6 - Medium - CCI-000366 - V-220063 - SV-220063r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006565

Vuln IDs

V-220063
V-22506

Rule IDs

SV-220063r505925_rule
SV-26857

Verification using the system package management tool can be used to determine that system software has not been tampered with. This requirement is not applicable to systems not using package management tools.

Checks: C-21772r485495_chk

Check the root crontab (crontab -l) for the presence of a package check command, such as, pkgchk -n. If no such cron job is found, this is a finding.

Fix: F-21771r485496_fix

Add a cron job to run a package verification command, such as, pkgchk -n.

The system must use an access control program.

CM-6 - Medium - CCI-000366 - V-220064 - SV-220064r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006580

Vuln IDs

V-220064
V-940

Rule IDs

SV-220064r505925_rule
SV-28459

Access control programs (such as TCP_WRAPPERS) provide the ability to enhance system security posture.

Checks: C-21773r485507_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-21772r485508_fix

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

The system's access control program must be configured to grant or deny system access to specific hosts.

CM-6 - Medium - CCI-000366 - V-220065 - SV-220065r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006620

Vuln IDs

V-220065
V-12030

Rule IDs

SV-220065r505925_rule
SV-41532

If the system's access control program is not configured with appropriate rules for allowing and denying access to system network resources, services may be accessible to unauthorized hosts.

Checks: C-21774r485513_chk

Check for the existence of the /etc/hosts.allow and /etc/hosts.deny files. Procedure: # ls -la /etc/hosts.allow # ls -la /etc/hosts.deny If either file does not exist, this is a finding. Check for the presence of a default deny entry. Procedure: # grep "ALL: ALL" /etc/hosts.deny If the "ALL: ALL" entry is not present in the /etc/hosts.deny file, any TCP service from a host or network not matching other rules will be allowed access. If the entry is not in /etc/hosts.deny, this is a finding.

Fix: F-21773r485514_fix

Edit the /etc/hosts.allow and /etc/hosts.deny files to configure access restrictions.

Wireless network adapters must be disabled.

AC-18 - Medium - CCI-001443 - V-220066 - SV-220066r509202_rule

RMF Control

AC-18

Severity

CCI

CCI-001443

Version

GEN007841

Vuln IDs

V-220066
V-72771

Rule IDs

SV-220066r509202_rule
SV-87413

The use of wireless networking can introduce many different attack vectors into the organization's network. Common attack vectors such as malicious association and ad hoc networks will allow an attacker to spoof a wireless access point (AP), allowing validated systems to connect to the malicious AP and enabling the attacker to monitor and record network traffic. These malicious APs can also serve to create a man-in-the-middle attack or be used to create a denial of service to valid network resources.

Checks: C-21775r509200_chk

This is N/A for systems that do not have wireless network adapters. Verify that there are no wireless interfaces configured on the system: # ifconfig -a eth0 Link encap:Ethernet HWaddr b8:ac:6f:65:31:e5 inet addr:192.168.2.100 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::baac:6fff:fe65:31e5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2697529 errors:0 dropped:0 overruns:0 frame:0 TX packets:2630541 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2159382827 (2.0 GiB) TX bytes:1389552776 (1.2 GiB) Interrupt:17 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:2849 errors:0 dropped:0 overruns:0 frame:0 TX packets:2849 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2778290 (2.6 MiB) TX bytes:2778290 (2.6 MiB) If a wireless interface is configured, it must be documented and approved by the local Authorizing Official. If a wireless interface is configured and has not been documented and approved, this is a finding.

Fix: F-21774r509201_fix

Configure the system to disable all wireless network interfaces.

The system must use an appropriate reverse-path filter for IPv6 network traffic, if the system uses IPv6.

CM-6 - Medium - CCI-000366 - V-220067 - SV-220067r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN007900

Vuln IDs

V-220067
V-22552

Rule IDs

SV-220067r505925_rule
SV-26227

Reverse-path filtering provides protection against spoofed source addresses by causing the system to discard packets with source addresses for which the system has no route or if the route does not point towards the interface on which the packet arrived. Depending on the role of the system, reverse-path filtering may cause legitimate traffic to be discarded and, therefore, should be used with a more permissive mode or filter, or not at all. Whenever possible, reverse-path filtering should be used.

Checks: C-21776r485543_chk

Determine if the system uses a reverse-path filter for IPv6 network traffic. If it does not, this is a finding.

Fix: F-21775r485544_fix

Configure the system to use a reverse-path filter for IPv6 network traffic.

If the system is using LDAP for authentication or account information, the LDAP TLS certificate authority file and/or directory (as appropriate) must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-220068 - SV-220068r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN008200

Vuln IDs

V-220068
V-22566

Rule IDs

SV-220068r505925_rule
SV-37427

LDAP can be used to provide user authentication and account information, which are vital to system security. The LDAP client configuration must be protected from unauthorized modification.

Checks: C-21777r485576_chk

Check if the system is using NSS LDAP. # grep -v '^#' /etc/nsswitch.conf | grep ldap If no lines are returned, this vulnerability is not applicable. Verify the permissions of the certificate database files. # ls -lL /var/ldap/cert8.db /var/ldap/key3.db /var/ldap/secmod.db If the permissions of any of the files contain a "+", and extended ACL is present, this is a finding.

Fix: F-21776r485577_fix

Remove the extended ACL from the certificate database files. # chmod A- /var/ldap/cert8.db /var/ldap/key3.db /var/ldap/secmod.db

The system must not use removable media as the boot loader.

CM-6 - High - CCI-000366 - V-220069 - SV-220069r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN008640

Vuln IDs

V-220069
V-4247

Rule IDs

SV-220069r505925_rule
SV-41534

Malicious users with removable boot media can gain access to a system configured to use removable media as the boot loader.

Checks: C-21778r485603_chk

Ask the SA if the system uses removable media for the boot loader. If it does, this is a finding.

Fix: F-21777r485604_fix

Configure the system to use a bootloader installed on fixed media.

The nosuid option must be configured in the /etc/rmmount.conf file.

CM-6 - Medium - CCI-000366 - V-226405 - SV-226405r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000000-SOL00020

Vuln IDs

V-226405
V-12031

Rule IDs

SV-226405r505925_rule
SV-12532

The rmmount.conf file controls the mounting of removable media on a Solaris system. Removable media is not to be trusted with privileged access, and therefore the filesystems must be mounted with the nosuid option, which prevents any executables with the setuid bit set on this filesystem from running with owner privileges.

Checks: C-28566r482570_chk

# grep mount /etc/rmmount.conf Confirm the nosuid option is configured. mount * hsfs udfs ufs -o nosuid If the nosuid option is not configured in the /etc/rmmount.conf file, this is a finding.

Fix: F-28554r482571_fix

Edit /etc/rmmount.conf and add the nosuid mount option to the configuration.

The /etc/security/audit_user file must not define a different auditing level for specific users.

AU-12 - Medium - CCI-000172 - V-226406 - SV-226406r505925_rule

RMF Control

AU-12

Severity

CCI

Version

GEN000000-SOL00040

Vuln IDs

V-226406
V-4353

Rule IDs

SV-226406r505925_rule
SV-4353

The audit_user file may be used to selectively audit more, or fewer, auditing features for specific individuals. If used this way it could subject the activity to a lawsuit and could cause the loss of valuable auditing data in the case of a system compromise. If an item is audited for one individual (other than for root and administrative users - who have more auditing features) it must be audited for all.

Checks: C-28567r482573_chk

Perform: # more /etc/security/audit_user If /etc/security/audit_user has entries other than root, ensure the users defined are audited with the same flags as all users as defined in /etc/security/audit_control file.

Fix: F-28555r482574_fix

Edit the audit_user file and remove specific user configurations differing from the global audit settings.

The /etc/security/audit_user file must be owned by root.

CM-6 - Medium - CCI-000366 - V-226407 - SV-226407r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000000-SOL00060

Vuln IDs

V-226407
V-4352

Rule IDs

SV-226407r505925_rule
SV-4352

The /etc/security/audit_user is a sensitive file and must be owned by root to prevent possible system compromise.

Checks: C-28568r482576_chk

Check /etc/security/audit_user ownership. # ls -lL /etc/security/audit_user If /etc/security/audit_user is not owned by root, this is a finding.

Fix: F-28556r482577_fix

Change the owner of the /etc/security/audit_user file to root. # chown root /etc/security/audit_user

The /etc/security/audit_user file must be group-owned by root, sys, or bin.

CM-6 - Medium - CCI-000366 - V-226408 - SV-226408r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000000-SOL00080

Vuln IDs

V-226408
V-4351

Rule IDs

SV-226408r505925_rule
SV-4351

The Solaris audit_user file allows for selective auditing or non-auditing of features for certain users. If it is not protected, it could be compromised and used to mask audit events. This could cause the loss of valuable forensics data in the case of a system compromise.

Checks: C-28569r482579_chk

Check /etc/security/audit_user group ownership. # ls -lL /etc/security/audit_user If /etc/security/audit_user is not group owned by root, sys, or bin, this is a finding.

Fix: F-28557r482580_fix

Change the group owner of the audit_user file to root, bin, or sys. Example: # chgrp root /etc/security/audit_user

The /etc/security/audit_user file must have mode 0640 or less permissive.

AU-9 - Medium - CCI-000162 - V-226409 - SV-226409r505925_rule

RMF Control

AU-9

Severity

CCI

Version

GEN000000-SOL00100

Vuln IDs

V-226409
V-4245

Rule IDs

SV-226409r505925_rule
SV-4245

Audit_user is a sensitive file that, if compromised, would allow a malicious user to select auditing parameters to ignore his sessions. This would allow malicious operations the auditing subsystem would not log for that user.

Checks: C-28570r482582_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-28558r482583_fix

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

The /etc/security/audit_user file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226410 - SV-226410r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000000-SOL00110

Vuln IDs

V-226410
V-22599

Rule IDs

SV-226410r505925_rule
SV-27004

Audit_user is a sensitive file that, if compromised, would allow a malicious user to select auditing parameters to ignore their sessions. This would allow malicious operations the auditing subsystem would not detect for that user. It could also result in long-term system compromise possibly leading to the compromise of other systems and networks.

Checks: C-28571r482585_chk

Check the permissions of the file. # ls -lL /etc/security/audit_user If the permissions of the file contain a "+", an extended ACL is present, this is a finding.

Fix: F-28559r482586_fix

Remove the extended ACL from the file. # chmod A- /etc/security/audit_user

The /usr/aset/masters/uid_aliases must be empty.

AC-4 - Medium - CCI-000032 - V-226411 - SV-226411r505925_rule

RMF Control

AC-4

Severity

CCI

Version

GEN000000-SOL00140

Vuln IDs

V-226411
V-4312

Rule IDs

SV-226411r505925_rule
SV-4312

If uid_aliases has entries, users may not be properly identified in ASET records.

Checks: C-28572r482591_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-28560r482592_fix

Empty or comment out the entries in the uid_aliases file.

If the system is a firewall, ASET must be used on the system, and the firewall parameters must be set in /usr/aset/asetenv.

AC-4 - Medium - CCI-000032 - V-226412 - SV-226412r505925_rule

RMF Control

AC-4

Severity

CCI

Version

GEN000000-SOL00160

Vuln IDs

V-226412
V-4309

Rule IDs

SV-226412r505925_rule
SV-4309

ASET will not perform firewall tasks if it is not listed as a parameter in /usr/aset/asetenv.

Checks: C-28573r482594_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-28561r482595_fix

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

The Solaris system Automated Security Enhancement Tool (ASET) configurable parameters in the asetenv file must be correct.

AC-4 - Medium - CCI-000032 - V-226413 - SV-226413r505925_rule

RMF Control

AC-4

Severity

CCI

Version

GEN000000-SOL00180

Vuln IDs

V-226413
V-953

Rule IDs

SV-226413r505925_rule
SV-953

If settings in the asetenv file have been modified, then system vulnerabilities may not be detected.

Checks: C-28574r482597_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-28562r482598_fix

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

The /usr/aset/userlist file must exist.

AC-4 - Medium - CCI-000032 - V-226414 - SV-226414r505925_rule

RMF Control

AC-4

Severity

CCI

Version

GEN000000-SOL00220

Vuln IDs

V-226414
V-955

Rule IDs

SV-226414r505925_rule
SV-955

If the userlist file does not exist, then an unauthorized user may exist in the /etc/passwd file.

Checks: C-28575r482603_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-28563r482604_fix

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

The /usr/aset/userlist file must be owned by root.

CM-6 - Medium - CCI-000366 - V-226415 - SV-226415r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000000-SOL00240

Vuln IDs

V-226415
V-956

Rule IDs

SV-226415r505925_rule
SV-956

If the userlist file is not owned by root, then an unauthorized user can modify the file and enter an unauthorized user.

Checks: C-28576r482606_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-28564r482607_fix

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

The /usr/aset/userlist file must be group-owned by root.

CM-6 - Medium - CCI-000366 - V-226416 - SV-226416r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000000-SOL00250

Vuln IDs

V-226416
V-22600

Rule IDs

SV-226416r505925_rule
SV-27013

The /usr/aset/userlist file is critical to system security and must be protected from unauthorized access.

Checks: C-28577r482609_chk

Check the group ownership of the file. # ls -lLd /usr/aset/userlist If the group owner of the file is not root, this is a finding.

Fix: F-28565r482610_fix

Change the group ownership of the file. # chgrp root /usr/aset/userlist

The /usr/aset/userlist file must have mode 0600 or less permissive.

CM-6 - Medium - CCI-000366 - V-226417 - SV-226417r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000000-SOL00260

Vuln IDs

V-226417
V-957

Rule IDs

SV-226417r505925_rule
SV-957

A permission mask not set to the required level could allow unauthorized access to sensitive system files and resources.

Checks: C-28578r482612_chk

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

Fix: F-28566r482613_fix

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

The /usr/aset/userlist file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226418 - SV-226418r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000000-SOL00270

Vuln IDs

V-226418
V-22601

Rule IDs

SV-226418r505925_rule
SV-27015

File system ACLs can provide access to files beyond what is allowed by the mode numbers of the files.

Checks: C-28579r482615_chk

Check the permissions of the file. # ls -lLd /usr/aset/userlist If the permissions of the file or directory contains a "+", an extended ACL is present, this is a finding.

Fix: F-28567r482616_fix

Remove the extended ACL from the file. # chmod A- /usr/aset/userlist

The Solaris system EEPROM security-mode parameter must be set to full or command mode.

CM-6 - Medium - CCI-000366 - V-226419 - SV-226419r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000000-SOL00300

Vuln IDs

V-226419
V-958

Rule IDs

SV-226419r505925_rule
SV-958

If the EEPROM security-mode parameter is not set to full or command, then unauthorized access to system EEPROM can take place. In normal situations, when the system is in a controlled access area and it is desirable to have it automatically reboot upon loss of and restoring of power, for instance, then command mode with the autoboot parameter set to true is recommended.

Checks: C-28580r482618_chk

If the system does not have an OBP / EEPROM, this is not applicable. # eeprom | grep security-mode If the EEPROM security-mode parameter is not set to full or command, this is a finding.

Fix: F-28568r482619_fix

Set the system EEPROM security-mode parameter to full or command. # eeprom security-mode=full OR # eeprom security-mode=command The system will prompt the user for a password. This should be securely stored.

The NFS server must have logging implemented.

AU-12 - Medium - CCI-000172 - V-226420 - SV-226420r505925_rule

RMF Control

AU-12

Severity

CCI

Version

GEN000000-SOL00400

Vuln IDs

V-226420
V-4300

Rule IDs

SV-226420r505925_rule
SV-40041

Filesystem logging, especially for NFS exported file systems, can be critical to detecting data misuse and possible hardware/system errors that may, otherwise, go unnoticed.

Checks: C-28581r503798_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-28569r503799_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.

Hidden extended file attributes must not exist on the system.

AC-4 - Medium - CCI-000032 - V-226421 - SV-226421r505925_rule

RMF Control

AC-4

Severity

CCI

Version

GEN000000-SOL00420

Vuln IDs

V-226421
V-12032

Rule IDs

SV-226421r505925_rule
SV-12533

Solaris extended attributes are essentially files themselves that are of an arbitrary size and content. They could be used to hide files from ordinary system file scans.

Checks: C-28582r482624_chk

Search for all files with hidden extended attributes. # find / -xattr -print -exec runat {} ls -al \; If hidden extended file attributes exist, this is a finding.

Fix: F-28570r482625_fix

Remove the hidden extended file attributes. # runat <file name> rm <attribute name>

The root account must be the only account with GID of 0.

CM-6 - High - CCI-000366 - V-226422 - SV-226422r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000000-SOL00440

Vuln IDs

V-226422
V-12033

Rule IDs

SV-226422r505925_rule
SV-12534

Accounts with a GID of 0 have root group privileges.

Checks: C-28583r482627_chk

Check passwd and group files for non-root user ids and group ids with a GID of 0. # more /etc/passwd # more /etc/group OR # awk -F: '$4 == 0' /etc/passwd # awk -F: '$3 == 0' /etc/group Confirm the only account with a group id of 0 is root. If the root account is not the only account with GID of 0, this is a finding.

Fix: F-28571r482628_fix

Change the default GID of non-root accounts to a valid GID other than 0.

The /etc/zones directory, and its contents, must be owned by root.

CM-6 - Medium - CCI-000366 - V-226423 - SV-226423r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000000-SOL00540

Vuln IDs

V-226423
V-22603

Rule IDs

SV-226423r505925_rule
SV-27016

Solaris zones configuration files must be protected against illicit creation, modification, and deletion.

Checks: C-28584r482630_chk

Check the ownership of the files and directories. # ls -lLdR /etc/zones If the owner of the file is not root, this is a finding. If zones are not installed on the system, this is not a finding.

Fix: F-28572r482631_fix

Change the ownership of the files and directories. # chown -R root /etc/zones

The /etc/zones directory, and its contents, must be group-owned by root, sys, or bin.

CM-6 - Medium - CCI-000366 - V-226424 - SV-226424r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000000-SOL00560

Vuln IDs

V-226424
V-22604

Rule IDs

SV-226424r505925_rule
SV-27018

Solaris zones configuration files must be protected against illicit creation, modification, and deletion.

Checks: C-28585r482633_chk

Check the group ownership of the files and directories. # ls -lLRa /etc/zones If the group owner of the directory and all files is not root, sys, or bin, this is a finding. If zones are not installed on the system, this is not a finding.

Fix: F-28573r482634_fix

Change the group ownership of the files and directories. # chgrp -R sys /etc/zones # chgrp root /etc/zones/*.xml # chgrp bin /etc/zones/SUN*.xml

The /etc/zones directory, and its contents, must not be group- or world-writable.

CM-6 - Medium - CCI-000366 - V-226425 - SV-226425r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000000-SOL00580

Vuln IDs

V-226425
V-22605

Rule IDs

SV-226425r505925_rule
SV-27019

Solaris zones configuration files must be protected against illicit creation, modification, and deletion.

Checks: C-28586r482636_chk

Check the permissions of the files and directories. # ls -lLdR /etc/zones If the mode of a directory is more permissive than 0755, or the mode of a file more permissive than 0644, this is a finding. If zones are not installed on the system, this is not a finding.

Fix: F-28574r482637_fix

Change the mode of the file or directory. # chmod 0644 <file> For directories: # chmod 0755 <directory>

The /etc/zones directory, and its contents, must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226426 - SV-226426r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000000-SOL00600

Vuln IDs

V-226426
V-22606

Rule IDs

SV-226426r505925_rule
SV-27020

Solaris zones configuration files must be protected against illicit creation, modification, and deletion.

Checks: C-28587r482639_chk

Check the permissions of the file. # ls -lLd /etc/zones # ls -lLR /etc/zones If the permissions of the file or directory contains a "+", an extended ACL is present, this is a finding. If zones are not installed on the system, this is not a finding.

Fix: F-28575r482640_fix

Remove the extended ACL from the file. # chmod A- <file>

The inherit-pkg-dir zone option must be set to none or the system default list defined for sparse root zones.

CM-6 - Medium - CCI-000366 - V-226427 - SV-226427r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000000-SOL00620

Vuln IDs

V-226427
V-22607

Rule IDs

SV-226427r505925_rule
SV-27022

Solaris zones have the capability to inherit elements of the global zone's filesystem, which reduces the amount storage required for a zone, but also limits the flexibility of the zone. The inherit-pkg-dir option defines which paths are shared between the zones. If set incorrectly, private information from the global zone could be made available to the non-global zone. This option must be set to none (for a whole-root non-global zone), the vendor-specified list of paths for sparse-root non-global zones, or a list specified by the SA for operational reasons which has been justified and documented with the IAO.

Checks: C-28588r482642_chk

If the system is not a global zone, this vulnerability is not applicable. List the non-global zones on the system. # zoneadm list -vi List the configuration for each zone. # zonecfg -z <zone> info Check the inherit-pkg-dir lines. If no such lines exist, this is not a finding. If the lines contain only those defined for sparse root zones (/lib, /platform, /sbin, /usr), this is not a finding. Otherwise, this is a finding.

Fix: F-28576r482643_fix

Remove the inherit-pkg-dir lines or the directories not defined for sparse root zones. # zonecfg -z <zone> remove inherit-pkg-dir=<somedir>

The limitpriv zone option must be set to the vendor default or less permissive.

CM-6 - Medium - CCI-000366 - V-226428 - SV-226428r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000000-SOL00640

Vuln IDs

V-226428
V-22608

Rule IDs

SV-226428r505925_rule
SV-27023

Solaris zones can be assigned privileges generally reserved for the global zone using the limitpriv zone option. Any privilege assignments in excess of the vendor defaults may provide the ability for a non-global zone to compromise the global zone.

Checks: C-28589r482645_chk

If the system is not a global zone, this vulnerability is not applicable. List the non-global zones on the system. # zoneadm list -vi List the configuration for each zone. # zonecfg -z <zone> info Check the limitpriv lines. If a line set other than default, this is a finding. If limitpriv is not set, this is not a finding.

Fix: F-28577r482646_fix

Change the limitpriv setting to default. # zonecfg -z <zone> set limitpriv=default

The physical devices must not be assigned to non-global zones.

CM-6 - Medium - CCI-000366 - V-226429 - SV-226429r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000000-SOL00660

Vuln IDs

V-226429
V-22609

Rule IDs

SV-226429r505925_rule
SV-27024

Solaris non-global zones can be assigned physical hardware devices. This increases the risk of such a non-global zone having the capability to compromise the global zone.

Checks: C-28590r482648_chk

Fix: F-28578r482649_fix

Remove all device assignments from the non-global zone. # zonecfg -z <zone> remove device <device>

The operating system must be a supported release.

CM-6 - High - CCI-000366 - V-226430 - SV-226430r509205_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000100

Vuln IDs

V-226430
V-11940

Rule IDs

SV-226430r509205_rule
SV-27051

An operating system release is considered supported if the vendor continues to provide security patches for the product. With an unsupported release, it will not be possible to resolve security issues discovered in the system software.

Checks: C-28591r509203_chk

# uname -a Oracle has committed to indefinite "sustaining support" for recent Solaris operating system releases. Verify proof of purchase of support from Oracle. If the release is not supported, this is a finding. Severity Override Guidance: If an extended support agreement provides security patches for the unsupported product is procured from the vendor, this finding may be downgraded to a CAT III.

Fix: F-28579r509204_fix

Upgrade to a supported version of the operating system.

System security patches and updates must be installed and up-to-date.

CM-6 - Medium - CCI-000366 - V-226431 - SV-226431r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000120

Vuln IDs

V-226431
V-783

Rule IDs

SV-226431r505925_rule
SV-40813

Timely patching is critical for maintaining the operational availability, confidentiality, and integrity of Information Technology (IT) systems. However, failure to keep operating system and application software patched is a common mistake made by IT professionals. New patches are released daily, and it is often difficult for even experienced system administrators to keep abreast of all the new patches. When new weaknesses in an operating system exist, patches are usually made available by the vendor to resolve the problems. If the most recent security patches and updates are not installed, unauthorized users may take advantage of weaknesses present in the unpatched software. The lack of prompt attention to patching could result in a system compromise.

Checks: C-28592r482657_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-28580r482658_fix

Apply available security updates from Oracle. # smpatch update

A file integrity baseline must be created and maintained.

CM-3 - Medium - CCI-001744 - V-226432 - SV-226432r505925_rule

RMF Control

CM-3

Severity

CCI

Version

GEN000140

Vuln IDs

V-226432
V-11941

Rule IDs

SV-226432r505925_rule
SV-12442

A file integrity baseline is a collection of file metadata which is to evaluate the integrity of the system. A minimal baseline must contain metadata for all device files, setuid files, setgid files, system libraries, system binaries, and system configuration files. The minimal metadata must consist of the mode, owner, group owner, and modification times. For regular files, metadata must also include file size and a cryptographic hash of the file's contents.

Checks: C-28593r503801_chk

Determine if a file integrity baseline, which includes cryptographic hashes, has been created and maintained for the system. If no file integrity baseline exists for the system, this is a finding. If the file integrity baseline contains no cryptographic hashes, this is a finding. If the file integrity baseline is not maintained (has not been updated to be consistent with the latest approved system configuration changes), this is a finding.

Fix: F-28581r503802_fix

Create a file integrity baseline, including cryptographic hashes, for the system.

A file integrity tool must be used at least weekly to check for unauthorized file changes, particularly the addition of unauthorized system libraries or binaries, or for unauthorized modification to authorized system libraries or binaries.

CM-3 - Medium - CCI-001744 - V-226433 - SV-226433r505925_rule

RMF Control

CM-3

Severity

CCI

Version

GEN000220

Vuln IDs

V-226433
V-11945

Rule IDs

SV-226433r505925_rule
SV-28610

Changes in system libraries and binaries can indicate compromise or significant system events, such as patching needing to be checked by automated processes and the results reviewed by the SA. NOTE: The frequency may be increased to daily, if necessary, in accordance with the contingency plan.

Checks: C-28594r503804_chk

Determine if there is a cron job, scheduled to run weekly or more frequently, to run the file integrity tool to check for unauthorized system libraries or binaries, or unauthorized modification to authorized system libraries or binaries. Procedure: # crontab -l If there is no cron job meeting these requirements, this is a finding. NOTE: The frequency may be increased to daily, if necessary, in accordance with the contingency plan.

Fix: F-28582r503805_fix

Create a cron job, scheduled to run weekly or more frequently, to run the file integrity tool to check for unauthorized system libraries or binaries, or unauthorized modification to authorized system libraries or binaries. NOTE: The frequency may be increased to daily, if necessary, in accordance with the contingency plan.

The system clock must be synchronized to an authoritative DoD time source.

AU-8 - Medium - CCI-001891 - V-226434 - SV-226434r505925_rule

RMF Control

AU-8

Severity

CCI

CCI-001891

Version

GEN000240

Vuln IDs

V-226434
V-4301

Rule IDs

SV-226434r505925_rule
SV-40040

To assure the accuracy of the system clock, it must be synchronized with an authoritative time source within DoD. Many system functions, including time-based login and activity restrictions, automated reports, system logs, and audit records depend on an accurate system clock. If there is no confidence in the correctness of the system clock, time-based functions may not operate as intended and records may be of diminished value. Authoritative time sources include authorized time servers within the enclave that synchronize with upstream authoritative sources. Specific requirements for the upstream synchronization of Network Time Protocol (NTP) servers are covered in the Network Other Devices STIG. For systems located on isolated or closed networks, it is not necessary to synchronize with a global authoritative time source. If a global authoritative time source is not available to systems on an isolated network, a local authoritative time source must be established on this network and used by the systems connected to this network. This is necessary to provide the ability to correlate events and allow for the correct operation of time-dependent protocols between systems on the isolated network. If the system is completely isolated (no connections to networks or other systems), time synchronization is not required as no correlation of events between systems will be necessary. If the system is completely isolated, this requirement is not applicable.

Checks: C-28595r482666_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-28583r482667_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.

The system clock must be synchronized continuously.

CM-6 - Medium - CCI-000366 - V-226435 - SV-226435r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000241

Vuln IDs

V-226435
V-22290

Rule IDs

SV-226435r505925_rule
SV-26291

A synchronized system clock is critical for the enforcement of time-based policies and the correlation of logs and audit records with other systems. Internal system clocks tend to drift and require periodic resynchronization to ensure their accuracy. Software, such as NTPD, can be used to continuously synchronize the system clock with authoritative sources. Alternatively, the system may be synchronized periodically, with a maximum of one day between synchronizations. If the system is completely isolated (no connections to networks or other systems), time synchronization is not required as no correlation of events or operation of time-dependent protocols between systems will be necessary. If the system is completely isolated, this requirement is not applicable.

Checks: C-28596r482669_chk

NTP must be used and used only in the global zone. Determine the type of zone that you are currently securing. # zonename If the command output is not "global", then NTP must be disabled. Check the system for a running NTP daemon. # svcs -Ho state ntp If NTP is online, this is a finding. If the output from "zonename" is "global", then NTP must be enabled. Check the system for a running NTP daemon. # svcs -Ho state ntp If NTP is not online, this is a finding.

Fix: F-28584r482670_fix

Determine the type of zone that you are currently securing. # zonename If the command output is not "global", then NTP must be disabled. # svcadm disable ntp If the output from "zonename" is "global", then NTP must be enabled. # svcadm enable ntp

The system must use at least two time sources for clock synchronization.

AU-8 - Medium - CCI-001891 - V-226436 - SV-226436r505925_rule

RMF Control

AU-8

Severity

CCI

CCI-001891

Version

GEN000242

Vuln IDs

V-226436
V-22291

Rule IDs

SV-226436r505925_rule
SV-26303

A synchronized system clock is critical for the enforcement of time-based policies and the correlation of logs and audit records with other systems. For redundancy, two time sources are required so synchronization continues to function if one source fails. If the system is completely isolated (no connections to networks or other systems), time synchronization is not required as no correlation of events or operation of time-dependent protocols between systems will be necessary. If the system is completely isolated, this requirement is not applicable. NOTE: For the Network Time Protocol (NTP), the requirement is two servers, but it is recommended to configure at least four distinct time servers which allow NTP to effectively exclude a time source not consistent with the others. The system's local clock must be excluded from the count of time sources.

Checks: C-28597r482672_chk

Determine the zone that you are currently securing. # zonename If the command output is not "global", this is not applicable. Check the NTP daemon configuration for at least two external servers. # grep '^server' /etc/inet/ntp.conf | egrep -v '(127.127.1.1|127.127.1.0)' If less than two servers or external reference clocks (127.127.x.x other than 127.127.1.0 or 127.127.1.1) are listed, this is a finding.

Fix: F-28585r482673_fix

Add an additional server line to /etc/inet/ntp.conf for each additional NTP server.

The system must use time sources local to the enclave.

AU-8 - Low - CCI-001891 - V-226437 - SV-226437r505925_rule

RMF Control

AU-8

Severity

CCI

CCI-001891

Version

GEN000244

Vuln IDs

V-226437
V-22292

Rule IDs

SV-226437r505925_rule
SV-26305

A synchronized system clock is critical for the enforcement of time-based policies and the correlation of logs and audit records with other systems. The network architecture should provide multiple time servers within an enclave that provide local service to the enclave and synchronize with time sources outside of the enclave. If this server is an enclave time server, this requirement is not applicable. If the system is completely isolated (no connections to networks or other systems), time synchronization is not required as no correlation of events or operation of time-dependent protocols between systems will be necessary. If the system is completely isolated, this requirement is not applicable.

Checks: C-28598r482675_chk

Determine the zone that you are currently securing. # zonename If the command output is not "global", this is not applicable. Check the NTP daemon configuration. # grep '^server' /etc/inet/ntp.conf If an NTP server is listed outside of the enclave, this is a finding.

Fix: F-28586r482676_fix

Remove the server line from /etc/inet/ntp.conf for each NTP server that is external to the enclave.

The time synchronization configuration file (such as /etc/ntp.conf) must be owned by root.

CM-6 - Medium - CCI-000366 - V-226438 - SV-226438r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000250

Vuln IDs

V-226438
V-22294

Rule IDs

SV-226438r505925_rule
SV-26293

A synchronized system clock is critical for the enforcement of time-based policies and the correlation of logs and audit records with other systems. If an illicit time source is used for synchronization, the integrity of system logs and the security of the system could be compromised. If the configuration files controlling time synchronization are not owned by a system account, unauthorized modifications could result in the failure of time synchronization.

Checks: C-28599r482678_chk

Run ls -l /etc/inet/ntp.conf to display the owner of the NTP configuration file. If the owner is not root, this is a finding.

Fix: F-28587r482679_fix

Change the owner of the NTP configuration file to root. # chown root /etc/inet/ntp.conf

The time synchronization configuration file (such as /etc/ntp.conf) must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226439 - SV-226439r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000251

Vuln IDs

V-226439
V-22295

Rule IDs

SV-226439r505925_rule
SV-26296

A synchronized system clock is critical for the enforcement of time-based policies and the correlation of logs and audit records with other systems. If an illicit time source is used for synchronization, the integrity of system logs and the security of the system could be compromised. If the configuration files controlling time synchronization are not owned by a system group, unauthorized modifications could result in the failure of time synchronization.

Checks: C-28600r482681_chk

Check the group ownership of the NTP configuration file. Procedure: # ls -l /etc/inet/ntp.conf If the group owner is not root, bin, or sys, this is a finding.

Fix: F-28588r482682_fix

Change the group owner of the NTP configuration file. Procedure: # chgrp root /etc/inet/ntp.conf

The time synchronization configuration file (such as /etc/ntp.conf) must have mode 0640 or less permissive.

AC-3 - Medium - CCI-002165 - V-226440 - SV-226440r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN000252

Vuln IDs

V-226440
V-22296

Rule IDs

SV-226440r505925_rule
SV-26298

A synchronized system clock is critical for the enforcement of time-based policies and the correlation of logs and audit records with other systems. If an illicit time source is used for synchronization, the integrity of system logs and the security of the system could be compromised. If the configuration files controlling time synchronization are not protected, unauthorized modifications could result in the failure of time synchronization.

Checks: C-28601r482684_chk

Verify the mode for the NTP configuration file is not more permissive than 0640. # ls -l /etc/inet/ntp.conf If the mode is more permissive than 0640, this is a finding.

Fix: F-28589r482685_fix

Change the mode of the NTP configuration file to 0640 or less permissive. # chmod 0640 /etc/inet/ntp.conf

The time synchronization configuration file (such as /etc/ntp.conf) must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226441 - SV-226441r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000253

Vuln IDs

V-226441
V-22297

Rule IDs

SV-226441r505925_rule
SV-26301

A synchronized system clock is critical for the enforcement of time-based policies and the correlation of logs and audit records with other systems. If an illicit time source is used for synchronization, the integrity of system logs and the security of the system could be compromised. If the configuration files controlling time synchronization are not protected, unauthorized modifications could result in the failure of time synchronization.

Checks: C-28602r482687_chk

Check for an extended ACL on the NTP configuration file. # ls -l /etc/inet/ntp.conf If the permissions contain a "+", the file has an extended ACL and this is a finding.

Fix: F-28590r482688_fix

Remove the extended ACL from the file. # chmod A- /etc/inet/ntp.conf

The system must not have unnecessary accounts.

CM-6 - Medium - CCI-000366 - V-226442 - SV-226442r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000290

Vuln IDs

V-226442
V-4269

Rule IDs

SV-226442r505925_rule
SV-4269

Accounts providing no operational purpose provide additional opportunities for system compromise. Unnecessary accounts include user accounts for individuals not requiring access to the system and application accounts for applications not installed on the system.

Checks: C-28603r503807_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-28591r503808_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.

All accounts on the system must have unique user or account names.

IA-2 - Medium - CCI-000764 - V-226443 - SV-226443r505925_rule

RMF Control

IA-2

Severity

CCI

CCI-000764

Version

GEN000300

Vuln IDs

V-226443
V-761

Rule IDs

SV-226443r505925_rule
SV-27061

A unique user name is the first part of the identification and authentication process. If user names are not unique, there can be no accountability on the system for auditing purposes. Multiple accounts sharing the same name could result in the Denial of Service to one or both of the accounts or unauthorized access to files or privileges.

Checks: C-28604r482696_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-28592r482697_fix

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

All accounts must be assigned unique User Identification Numbers (UIDs).

IA-2 - Medium - CCI-000764 - V-226444 - SV-226444r505925_rule

RMF Control

IA-2

Severity

CCI

CCI-000764

Version

GEN000320

Vuln IDs

V-226444
V-762

Rule IDs

SV-226444r505925_rule
SV-27065

Accounts sharing a UID have full access to each others' files. This has the same effect as sharing a login. There is no way to assure identification, authentication, and accountability because the system sees them as the same user. If the duplicate UID is 0, this gives potential intruders another privileged account to attack.

Checks: C-28605r482699_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-28593r482700_fix

Edit user accounts to provide unique UIDs for each account.

UIDs reserved for system accounts must not be assigned to non-system accounts.

CM-6 - Medium - CCI-000366 - V-226445 - SV-226445r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000340

Vuln IDs

V-226445
V-11946

Rule IDs

SV-226445r505925_rule
SV-12447

Reserved UIDs are typically used by system software packages. If non-system accounts have UIDs in this range, they may conflict with system software, possibly leading to the user having permissions to modify system files.

Checks: C-28606r482702_chk

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

Fix: F-28594r482703_fix

Change the UID numbers for non-system accounts with reserved UIDs (those less or equal to 99).

GIDs reserved for system accounts must not be assigned to non-system groups.

CM-6 - Medium - CCI-000366 - V-226446 - SV-226446r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000360

Vuln IDs

V-226446
V-780

Rule IDs

SV-226446r505925_rule
SV-28658

Reserved GIDs are typically used by system software packages. If non-system groups have GIDs in this range, they may conflict with system software, possibly leading to the group having permissions to modify system files.

Checks: C-28607r482705_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-28595r482706_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>

All GIDs referenced in the /etc/passwd file must be defined in the /etc/group file.

CM-6 - Low - CCI-000366 - V-226447 - SV-226447r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000380

Vuln IDs

V-226447
V-781

Rule IDs

SV-226447r505925_rule
SV-27069

If a user is assigned the GID of a group not existing on the system, and a group with the same GID is subsequently created, the user may have unintended rights to the group.

Checks: C-28608r482708_chk

Perform the following to ensure there are no GIDs referenced in /etc/passwd not defined in /etc/group. # logins -o | awk -F: '$3 == ""' If any lines are returned, there are GIDs referenced in /etc/passwd that are not defined in /etc/group, this is a finding.

Fix: F-28596r482709_fix

Add a group to the system for each GID referenced that does not have a corresponding group. #/usr/sbin/groupadd < group >

The Department of Defense (DoD) login banner must be displayed immediately prior to, or as part of, console login prompts.

AC-8 - Medium - CCI-000048 - V-226448 - SV-226448r505925_rule

RMF Control

AC-8

Severity

CCI

Version

GEN000400

Vuln IDs

V-226448
V-763

Rule IDs

SV-226448r505925_rule
SV-28596

Failure to display the login banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources.

Checks: C-28609r503810_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-28597r503811_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."

The Department of Defense (DoD) login banner must be displayed immediately prior to, or as part of, graphical desktop environment login prompts.

AC-8 - Medium - CCI-000048 - V-226449 - SV-226449r509208_rule

RMF Control

AC-8

Severity

CCI

Version

GEN000402

Vuln IDs

V-226449
V-24331

Rule IDs

SV-226449r509208_rule
SV-39880

Failure to display the login banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. This requirement applies to graphical desktop environments provided by the system to locally attached displays and input devices as well as to graphical desktop environments provided to remote systems, including thin clients.

Checks: C-28610r509206_chk

If the system does not use XWindows, this is not applicable. Check the "Dtlogin*greeting.labelString" parameter in /etc/dt/config/C/Xresources 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. If the file does not exist, 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-28598r509207_fix

Create/update /etc/dt/config/C/Xresources with Dtlogin*greeting.labelString: [DoD login banner text]. 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."

The FTPS/FTP service on the system must be configured with the Department of Defense (DoD) login banner.

AC-8 - Medium - CCI-000048 - V-226450 - SV-226450r509211_rule

RMF Control

AC-8

Severity

CCI

Version

GEN000410

Vuln IDs

V-226450
V-23732

Rule IDs

SV-226450r509211_rule
SV-39879

Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. NOTE: SFTP and FTPS are encrypted alternatives to FTP that should be used in place of FTP. SFTP is implemented by the SSH service and uses its banner configuration.

Checks: C-28611r509209_chk

FTP to the system. # ftp localhost 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. If the system does not run the FTP service, this is not applicable. 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."

Fix: F-28599r509210_fix

Edit /etc/ftpd/ftpaccess and add or edit the BANNER parameter ("banner /etc/ftpd/banner.msg"). # vi /etc/ftpd/ftpaccess Add one of the DoD Login Banners (based on the character limitations imposed by the system) to the /etc/ftpd/banner.msg file. # vi /etc/ftpd/banner.msg 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."

Successful and unsuccessful logins and logouts must be logged.

AU-12 - Medium - CCI-000172 - V-226451 - SV-226451r505925_rule

RMF Control

AU-12

Severity

CCI

Version

GEN000440

Vuln IDs

V-226451
V-765

Rule IDs

SV-226451r505925_rule
SV-27080

Monitoring and recording successful and unsuccessful logins assist in tracking unauthorized access to the system. Without this logging, the ability to track unauthorized activity to specific user accounts may be diminished.

Checks: C-28612r503813_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-28600r503814_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.

The system must display the date and time of the last successful account login upon login.

AC-9 - Low - CCI-000052 - V-226452 - SV-226452r505925_rule

RMF Control

AC-9

Severity

CCI

CCI-000052

Version

GEN000452

Vuln IDs

V-226452
V-22299

Rule IDs

SV-226452r505925_rule
SV-26310

Providing users with feedback on when account accesses last occurred facilitates user recognition and reporting of unauthorized account use.

Checks: C-28613r482723_chk

Determine if the system displays the date and time of the last successful login upon logging in. This can be accomplished by logging into the system and verifying whether or not the necessary information is displayed. If the system does not provide this information upon login, this is a finding. Last login information is provided automatically by the login(1) program for telnet and console login sessions. Verify the SSH daemon is configured to display last login information. # grep -i PrintLastLog /etc/ssh/sshd_config If PrintLastLog is present in the configuration and not disabled, this is not a finding. Otherwise, this is a finding.

Fix: F-28601r482724_fix

Configure the system to display the date and time of the last successful login upon logging in. Enable PrintLastLog in the SSH daemon. To enable PrintLastLog in the SSH daemon, remove any lines disabling this option from /etc/ssh/sshd_config.

The system must display a publicly-viewable pattern during a graphical desktop environment session lock.

AC-11 - Low - CCI-000057 - V-226453 - SV-226453r505925_rule

RMF Control

AC-11

Severity

CCI

CCI-000057

Version

GEN000510

Vuln IDs

V-226453
V-22301

Rule IDs

SV-226453r505925_rule
SV-39865

To protect the on-screen content of a session, it must be replaced with a publicly-viewable pattern upon session lock. Examples of publicly viewable patterns include screen saver patterns, photographic images, solid colors, or a blank screen, so long as none of those patterns convey sensitive information. This requirement applies to graphical desktop environments provided by the system to locally attached displays and input devices, as well as, to graphical desktop environments provided to remote systems using remote access protocols.

Checks: C-28614r482735_chk

Determine if a publicly-viewable pattern is displayed during a session lock. If the session lock pattern is not publicly-viewable, this is a finding. Acceptable checks for settings. # grep -i dtsession /etc/dt/config/C/sys.resources | egrep -i "saverList|saverTimeout" The saverTimeout value should be 15 (see GEN000500). The saverList value of StartDtscreenBlank is an acceptable screensaver.

Fix: F-28602r482736_fix

Edit the /etc/dt/config/C/sys.resources file and add/edit the following lines, using 15 for the saverTimeout, and using StartDtscreenBlank for the saverList. dtsession*saverTimeout: 15 dtsession*saverList: StartDtscreenBlank

The root user must not own the logon session for an application requiring a continuous display.

AC-6 - Medium - CCI-002233 - V-226454 - SV-226454r505925_rule

RMF Control

AC-6

Severity

CCI

CCI-002233

Version

GEN000520

Vuln IDs

V-226454
V-769

Rule IDs

SV-226454r505925_rule
SV-769

If an application is providing a continuous display and is running with root privileges, unauthorized users could interrupt the process and gain root access to the system.

Checks: C-28615r503816_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-28603r503817_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.

Users must not be able to change passwords more than once every 24 hours.

IA-5 - Medium - CCI-000198 - V-226455 - SV-226455r505925_rule

RMF Control

IA-5

Severity

CCI

CCI-000198

Version

GEN000540

Vuln IDs

V-226455
V-1032

Rule IDs

SV-226455r505925_rule
SV-39809

The ability to change passwords frequently facilitates users reusing the same password. This can result in users effectively never changing their passwords. This would be accomplished by users changing their passwords when required and then immediately changing it to the original value.

Checks: C-28616r482741_chk

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

Fix: F-28604r482742_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>

The system must not have accounts configured with blank or null passwords.

CM-6 - High - CCI-000366 - V-226456 - SV-226456r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000560

Vuln IDs

V-226456
V-770

Rule IDs

SV-226456r505925_rule
SV-27105

If an account is configured for password authentication but does not have an assigned password, it may be possible to log into the account without authentication. If the root user is configured without a password, the entire system may be compromised. For user accounts not using password authentication, the account must be configured with a password lock value instead of a blank or null value.

Checks: C-28617r482744_chk

Verify no accounts have blank passwords. # logins -p If any account with a blank password is found, this is a finding.

Fix: F-28605r482745_fix

Remove, lock, or configure a password for any account with a blank password.

The system must require passwords contain a minimum of 15 characters.

IA-5 - Medium - CCI-000205 - V-226457 - SV-226457r505925_rule

RMF Control

IA-5

Severity

CCI

CCI-000205

Version

GEN000580

Vuln IDs

V-226457
V-11947

Rule IDs

SV-226457r505925_rule
SV-27110

The use of longer passwords reduces the ability of attackers to successfully obtain valid passwords using guessing or exhaustive search techniques by increasing the password search space.

Checks: C-28618r482747_chk

Check the system password length setting. # grep PASSLENGTH /etc/default/passwd If PASSLENGTH is not set to 15 or more, this is a finding.

Fix: F-28606r482748_fix

Edit /etc/default/passwd and set the PASSLENGTH variable to 15 or greater.

The system must enforce compliance of the entire password during authentication.

IA-5 - Medium - CCI-000205 - V-226458 - SV-226458r505925_rule

RMF Control

IA-5

Severity

CCI

CCI-000205

Version

GEN000585

Vuln IDs

V-226458
V-22302

Rule IDs

SV-226458r505925_rule
SV-26318

Some common password hashing schemes only process the first eight characters of a user's password, which reduces the effective strength of the password.

Checks: C-28619r503819_chk

Verify no password hash in /etc/passwd or /etc/shadow begins with a character other than an underscore (_) or dollar sign ($). # cut -d ':' -f2 /etc/passwd | egrep -v '^[*!$_]' # cut -d ':' -f2 /etc/shadow | egrep -v '^[*!$_]' If any unlocked password hash is present without an initial underscore (_) or dollar sign ($) character, this is a finding.

Fix: F-28607r503820_fix

Edit /etc/security/policy.conf and add or change the CRYPT_DEFAULT setting to something other than __unix__, such as 6. Allowable values for CRYPT_DEFAULT may be found in the /etc/security/crypt.conf file. Change any passwords using non-compliant hashes.

The system must use a FIPS 140-2 approved cryptographic hashing algorithm for generating account password hashes.

IA-7 - Medium - CCI-000803 - V-226459 - SV-226459r505925_rule

RMF Control

IA-7

Severity

CCI

CCI-000803

Version

GEN000590

Vuln IDs

V-226459
V-22303

Rule IDs

SV-226459r505925_rule
SV-40776

Systems must employ cryptographic hashes for passwords using the SHA-2 family of algorithms or FIPS 140-2 approved successors. The use of unapproved algorithms may result in weak password hashes more vulnerable to compromise.

Checks: C-28620r503822_chk

Verify the traditional UNIX crypt algorithm is deprecated. # egrep CRYPT_ALGORITHMS_ALLOW /etc/security/policy.conf If CRYPT_ALGORITHMS_ALLOW is not set, is not set to "6", or is not set to "5,6", this is a finding. Verify new password hashes are generated using either the SHA-256 or SHA-512 cryptographic hashing algorithm. # egrep CRYPT_DEFAULT /etc/security/policy.conf If CRYPT_DEFAULT is not set or is not equal to 5 or 6, this is a finding.

Fix: F-28608r503823_fix

Edit the /etc/security/policy.conf file. # vi /etc/security/policy.conf Uncomment or add the CRYPT_ALGORITHMS_ALLOW line and set it to "5,6". Update the CRYPT_DEFAULT default line to be equal to 5 or 6. The following lines are acceptable. CRYPT_ALGORITHMS_ALLOW=5,6 CRYPT_DEFAULT=6

The password hashes stored on the system must have been generated using a FIPS 140-2 approved cryptographic hashing algorithm.

IA-5 - Medium - CCI-000196 - V-226460 - SV-226460r505925_rule

RMF Control

IA-5

Severity

CCI

CCI-000196

Version

GEN000595

Vuln IDs

V-226460
V-22304

Rule IDs

SV-226460r505925_rule
SV-40790

Checks: C-28621r503825_chk

Determine if any password hashes stored on the system were not generated using a FIPS 140-2 approved cryptographic hashing algorithm. Procedure: # cut -d ':' -f2 /etc/passwd # cut -d ':' -f2 /etc/shadow If any password hashes are present not beginning with $5$ or $6$, this is a finding. Verify that FIPS 140-2 approved cryptographic hashing algorithms are available. # egrep '^[56]' /etc/security/crypt.conf If no lines are returned, this is a finding.

Fix: F-28609r503826_fix

If the /etc/security/crypt.conf file does not support FIPS 140-2 approved cryptographic hashing algorithms, upgrade to at least the Solaris 10 8/07 release. Edit the /etc/security/policy.conf file. # vi /etc/security/policy.conf Uncomment or add the CRYPT_ALGORITHMS_ALLOW line and set it to "5,6". Update the CRYPT_DEFAULT default line to be equal to 5 or 6. The following lines are acceptable. CRYPT_ALGORITHMS_ALLOW=5,6 CRYPT_DEFAULT=6 Update passwords for all accounts with non-compliant password hashes.

The system must require passwords to contain at least one uppercase alphabetic character.

IA-5 - Medium - CCI-000192 - V-226461 - SV-226461r505925_rule

RMF Control

IA-5

Severity

CCI

CCI-000192

Version

GEN000600

Vuln IDs

V-226461
V-11948

Rule IDs

SV-226461r505925_rule
SV-27115

To enforce the use of complex passwords, minimum numbers of characters of different classes are mandated. The use of complex passwords reduces the ability of attackers to successfully obtain valid passwords using guessing or exhaustive search techniques. Complexity requirements increase the password search space by requiring users to construct passwords from a larger character set than they may otherwise use.

Checks: C-28622r482759_chk

Check the MINUPPER setting. # egrep MINUPPER /etc/default/passwd If MINUPPER is not set to 1 or more, this is a finding.

Fix: F-28610r482760_fix

Edit /etc/default/passwd and set the MINUPPER setting to at least 1.

The system must require passwords to contain at least one numeric character.

IA-5 - Medium - CCI-000194 - V-226462 - SV-226462r505925_rule

RMF Control

IA-5

Severity

CCI

CCI-000194

Version

GEN000620

Vuln IDs

V-226462
V-11972

Rule IDs

SV-226462r505925_rule
SV-27119

Checks: C-28623r482762_chk

Check the MINDIGIT setting. # grep MINDIGIT /etc/default/passwd If the MINDIGIT setting is less than 1, this is a finding.

Fix: F-28611r482763_fix

Edit /etc/default/passwd and set the MINDIGIT setting to 1.

The system must require passwords to contain at least one special character.

IA-5 - Medium - CCI-001619 - V-226463 - SV-226463r505925_rule

RMF Control

IA-5

Severity

CCI

CCI-001619

Version

GEN000640

Vuln IDs

V-226463
V-11973

Rule IDs

SV-226463r505925_rule
SV-27123

Checks: C-28624r482765_chk

Check the MINSPECIAL setting. # grep MINSPECIAL /etc/default/passwd If the MINSPECIAL setting is less than 1, this is a finding.

Fix: F-28612r482766_fix

Edit /etc/default/passwd and set MINSPECIAL to 1.

The system must require passwords to contain no more than three consecutive repeating characters.

CM-6 - Medium - CCI-000366 - V-226464 - SV-226464r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000680

Vuln IDs

V-226464
V-11975

Rule IDs

SV-226464r505925_rule
SV-27126

To enforce the use of complex passwords, the number of consecutive repeating characters is limited. Passwords with excessive repeated characters may be more vulnerable to password-guessing attacks.

Checks: C-28625r482768_chk

Check the MAXREPEATS setting. # grep MAXREPEATS /etc/default/passwd If the MAXREPEATS setting is greater than 3, this is a finding.

Fix: F-28613r482769_fix

Edit /etc/default/passwd and set MAXREPEATS to 3.

User passwords must be changed at least every 60 days.

IA-5 - Medium - CCI-000199 - V-226465 - SV-226465r505925_rule

RMF Control

IA-5

Severity

CCI

CCI-000199

Version

GEN000700

Vuln IDs

V-226465
V-11976

Rule IDs

SV-226465r505925_rule
SV-39845

Checks: C-28626r482771_chk

Check the max days field (the 5th field) of /etc/shadow. # awk -F: '{print $1 ":" $5;}' /etc/shadow If the max days field is equal to 0 or greater than 60 for any account that is not password-locked, this is a finding.

Fix: F-28614r482772_fix

Set the max days field to 60 for all user accounts. # passwd -x 60 <user> Set the MAXWEEKS parameter in /etc/default/passwd to a positive, non-zero value of 8 or less.

All non-interactive/automated processing account passwords must be changed at least once per year or be locked.

IA-5 - Medium - CCI-000199 - V-226466 - SV-226466r505925_rule

RMF Control

IA-5

Severity

CCI

CCI-000199

Version

GEN000740

Vuln IDs

V-226466
V-11977

Rule IDs

SV-226466r505925_rule
SV-12478

Limiting the lifespan of authenticators limits the period of time an unauthorized user has access to the system while using compromised credentials and reduces the period of time available for password-guessing attacks to run against a single password. Locking the password for non-interactive and automated processing accounts is preferred as it removes the possibility of accessing the account by a password. On some systems, locking the passwords of these accounts may prevent the account from functioning properly. Passwords for non-interactive/automated processing accounts must not be used for direct logon to the system.

Checks: C-28627r482774_chk

Ask the SA if there are any automated processing accounts on the system. If there are automated processing accounts on the system, ask the SA if the passwords for those automated accounts are changed at least once a year. If SA indicates passwords for automated processing accounts are not changed once per year, this is a finding.

Fix: F-28615r482775_fix

Implement or establish procedures to change the passwords of automated processing accounts at least once per year.

The system must require at least eight characters be changed between the old and new passwords during a password change.

IA-5 - Medium - CCI-000195 - V-226467 - SV-226467r505925_rule

RMF Control

IA-5

Severity

CCI

CCI-000195

Version

GEN000750

Vuln IDs

V-226467
V-22306

Rule IDs

SV-226467r505925_rule
SV-26324

To ensure password changes are effective in their goals, the system must ensure old and new passwords have significant differences. Without significant changes, new passwords may be easily guessed based on the value of a previously compromised password.

Checks: C-28628r482777_chk

Check /etc/default/passwd to verify the MINDIFF setting. # grep MINDIFF /etc/default/passwd If the setting is not present, or is less than 8, this is a finding.

Fix: F-28616r482778_fix

Edit /etc/default/passwd and set or add a MINDIFF setting equal to or greater than 8.

The system must prevent the use of dictionary words for passwords.

CM-6 - Medium - CCI-000366 - V-226468 - SV-226468r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000790

Vuln IDs

V-226468
V-22307

Rule IDs

SV-226468r505925_rule
SV-26345

An easily guessable password provides an open door to any external or internal malicious intruder. Many computer compromises occur as the result of account name and password guessing. This is generally done by someone with an automated script using repeated logon attempts until the correct account and password pair is guessed. Utilities, such as cracklib, can be used to validate passwords are not dictionary words and meet other criteria during password changes.

Checks: C-28629r482783_chk

Check /etc/default/passwd for dictionary check configuration. # grep DICTION /etc/default/passwd If the DICTIONLIST or DICTIONDBDIR settings are not present, or are set to non-existent files or directories, this is a finding.

Fix: F-28617r482784_fix

Edit /etc/default/passwd; add or set DICTIONLIST to the dictionary file and DICTIONDBDIR to a database directory such as /var/passwd. Generate the password dictionary by running the mkpwdict command.

The system must prohibit the reuse of passwords within five iterations.

IA-5 - Medium - CCI-000200 - V-226469 - SV-226469r505925_rule

RMF Control

IA-5

Severity

CCI

CCI-000200

Version

GEN000800

Vuln IDs

V-226469
V-4084

Rule IDs

SV-226469r505925_rule
SV-27132

If a user, or root, used the same password continuously or was allowed to change it back shortly after being forced to change it to something else, it would provide a potential intruder with the opportunity to keep guessing at one user's password until it was guessed correctly.

Checks: C-28630r482786_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-28618r482787_fix

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

The system must restrict the ability to switch to the root user to members of a defined group.

IA-2 - Low - CCI-000770 - V-226470 - SV-226470r505925_rule

RMF Control

IA-2

Severity

CCI

Version

GEN000850

Vuln IDs

V-226470
V-22308

Rule IDs

SV-226470r505925_rule
SV-39876

Configuring a supplemental group for users permitted to switch to the root user prevents unauthorized users from accessing the root account, even with knowledge of the root credentials.

Checks: C-28631r482789_chk

Verify the root user is configured as a role, rather than a normal user. # egrep '^root:' /etc/user_attr If the returned line does not include "type=role", this is a finding. Verify at least one local user has been assigned the root role. # egrep '[:;]roles=[^;]*,?root([,;]|$)' /etc/user_attr If no lines are returned, no users are permitted to assume the root role, this is a finding.

Fix: F-28619r482790_fix

Convert the root user into a role. # usermod -K type=role root Add the root role to authorized users' logins. # usermod -R root <userid>

The root user's home directory must not be the root directory (/).

CM-6 - Low - CCI-000366 - V-226471 - SV-226471r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000900

Vuln IDs

V-226471
V-774

Rule IDs

SV-226471r505925_rule
SV-774

Changing the root home directory to something other than / and assigning it a 0700 protection makes it more difficult for intruders to manipulate the system by reading the files that root places in its default directory. It also gives root the same discretionary access control for root's home directory as for the other plain user home directories.

Checks: C-28632r503828_chk

Determine if root is assigned a home directory other than / by listing its home directory. Procedure: # grep "^root" /etc/passwd | awk -F":" '{print $6}' If the root user home directory is /, this is a finding.

Fix: F-28620r503829_fix

The root home directory should be something other than / (such as /rootdir). Procedure: # mkdir /rootdir # chown root /rootdir # chgrp root /rootdir # chmod 700 /rootdir # cp -r /.??* /rootdir Edit the passwd file and change the root home directory to /rootdir. The cp -r /.??* command copies all files and subdirectories of file names beginning with "." into the new root directory, which preserves the previous root environment. The cp command must be executed from the / directory.

The root account's home directory (other than /) must have mode 0700.

AC-6 - Medium - CCI-002233 - V-226472 - SV-226472r505925_rule

RMF Control

AC-6

Severity

CCI

CCI-002233

Version

GEN000920

Vuln IDs

V-226472
V-775

Rule IDs

SV-226472r505925_rule
SV-775

Permissions greater than 0700 could allow unauthorized users access to the root home directory.

Checks: C-28633r482798_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-28621r482799_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.

The root account's home directory must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226473 - SV-226473r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000930

Vuln IDs

V-226473
V-22309

Rule IDs

SV-226473r505925_rule
SV-26353

File system extended ACLs provide access to files beyond what is allowed by the mode numbers of the files.

Checks: C-28634r482801_chk

Verify the root account's home directory has no extended ACL. # ls -ld ~root If the permissions include a "+", the directory has an extended ACL and this is a finding.

Fix: F-28622r482802_fix

Remove the extended ACL from the directory. # chmod A- ~root

The root accounts executable search path must contain only authorized paths.

CM-6 - Medium - CCI-000366 - V-226474 - SV-226474r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000940

Vuln IDs

V-226474
V-776

Rule IDs

SV-226474r505925_rule
SV-776

The executable search path (typically the PATH environment variable) contains a list of directories for the shell to search to find executables. If this path includes the current working directory or other relative paths, executables in these directories may be executed instead of system commands. This variable is formatted as a colon-separated list of directories. If there is an empty entry, such as a leading or trailing colon, two consecutive colons, or a single period, this is interpreted as the current working directory. Entries starting with a slash (/) are absolute paths.

Checks: C-28635r503831_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-28623r503832_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.

The root account's library search path must be the system default and must contain only absolute paths.

CM-6 - Medium - CCI-000366 - V-226475 - SV-226475r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000945

Vuln IDs

V-226475
V-22310

Rule IDs

SV-226475r505925_rule
SV-26355

The library search path environment variable(s) contain a list of directories for the dynamic linker to search to find libraries. If this path includes the current working directory or other relative paths, libraries in these directories may be loaded instead of system libraries. 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 interpreted as the current working directory. Entries starting with a slash (/) are absolute paths.

Checks: C-28636r482807_chk

Verify the LD_LIBRARY_PATH environment variable is empty or not defined for the root user. # echo $LD_LIBRARY_PATH If a path list is returned, this is a finding.

Fix: F-28624r482808_fix

Edit the root user initialization files and remove any definition of LD_LIBRARY_PATH.

The root account's list of preloaded libraries must be empty.

CM-6 - Medium - CCI-000366 - V-226476 - SV-226476r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN000950

Vuln IDs

V-226476
V-22311

Rule IDs

SV-226476r505925_rule
SV-26357

The library preload list environment variable contains a list of libraries for the dynamic linker to load before loading the libraries required by the binary. If this list contains paths to libraries relative to the current working directory, unintended libraries may be preloaded. This variable is formatted as a space-separated list of libraries. Paths starting with (/) are absolute paths.

Checks: C-28637r482810_chk

Verify the LD_PRELOAD environment variable is empty or not defined for the root user. # echo $LD_PRELOAD If a path list is returned, this is a finding.

Fix: F-28625r482811_fix

Edit the root user initialization files and remove any definition of LD_PRELOAD.

The system must prevent the root account from directly logging in except from the system console.

IA-2 - Medium - CCI-000770 - V-226477 - SV-226477r505925_rule

RMF Control

IA-2

Severity

CCI

Version

GEN000980

Vuln IDs

V-226477
V-778

Rule IDs

SV-226477r505925_rule
SV-27143

Limiting the root account direct logins to only system consoles protects the root account from direct unauthorized access from a non-console device.

Checks: C-28638r482816_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-28626r482817_fix

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

Remote consoles must be disabled or protected from unauthorized access.

AC-17 - Medium - CCI-002314 - V-226478 - SV-226478r505925_rule

RMF Control

AC-17

Severity

CCI

CCI-002314

Version

GEN001000

Vuln IDs

V-226478
V-4298

Rule IDs

SV-226478r505925_rule
SV-27147

The remote console feature provides an additional means of access to the system which could allow unauthorized access if not disabled or properly secured. With virtualization technologies, remote console access is essential as there is no physical console for virtual machines. Remote console access must be protected in the same manner as any other remote privileged access method.

Checks: C-28639r482819_chk

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

Fix: F-28627r482820_fix

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

The root account must not be used for direct logins.

IA-2 - Medium - CCI-000770 - V-226479 - SV-226479r505925_rule

RMF Control

IA-2

Severity

CCI

Version

GEN001020

Vuln IDs

V-226479
V-11979

Rule IDs

SV-226479r505925_rule
SV-39848

Direct login with the root account prevents individual user accountability. Acceptable non-routine uses of the root account for direct login are limited to emergency maintenance, the use of single-user mode for maintenance, and situations where individual administrator accounts are not available.

Checks: C-28640r482822_chk

Check if the root is used for direct logins. Procedure: # last root | grep -v reboot If any direct login records for root exist, this is a finding. Verify the root user is configured as a role, rather than a normal user. Procedure: # egrep '^root:' /etc/user_attr If the returned line does not include "type=role", this is a finding.

Fix: F-28628r482823_fix

Convert the root user into a role. # usermod -K type=role root Add the root role to authorized users' logins. # usermod -R root <userid>

The system must log successful and unsuccessful access to the root account.

AU-12 - Medium - CCI-000169 - V-226480 - SV-226480r505925_rule

RMF Control

AU-12

Severity

CCI

Version

GEN001060

Vuln IDs

V-226480
V-11980

Rule IDs

SV-226480r505925_rule
SV-39850

If successful and unsuccessful logins and logouts are not monitored or recorded, access attempts cannot be tracked. Without this logging, it may be impossible to track unauthorized access to the system.

Checks: C-28641r482825_chk

Check the following log files to determine if access to the root account is being logged. Try to su - and enter an incorrect password. # more /var/adm/sulog If root login accounts are not being logged, this is a finding.

Fix: F-28629r482826_fix

Update /etc/default/su and set SYSLOG=YES. Ensure /etc/syslog.conf is configured to log auth.crit messages to capture all failed su attempts.

The root shell must be located in the / file system.

CM-6 - Low - CCI-000366 - V-226481 - SV-226481r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001080

Vuln IDs

V-226481
V-1062

Rule IDs

SV-226481r505925_rule
SV-27157

To ensure the root shell is available in repair and administrative modes, the root shell must be located in the / file system.

Checks: C-28642r482828_chk

Perform the following to determine if /usr is partitioned. # grep /usr /etc/vfstab If /usr is partitioned, check the location of root's default shell. # awk -F: '$1 == "root" {print $7}' /etc/passwd If the root shell is found to be on a partitioned /usr filesystem or is in a directory symlinked to a partitioned /usr filesystem, even if the actual root shell is a symlink back to the root filesystem, this is a finding.

Fix: F-28630r482829_fix

Change the root account's shell to one present on the / filesystem. Example: # usermod -s /sbin/sh root

Root passwords must never be passed over a network in clear text form.

IA-5 - High - CCI-000197 - V-226482 - SV-226482r505925_rule

RMF Control

IA-5

Severity

CCI

CCI-000197

Version

GEN001100

Vuln IDs

V-226482
V-1046

Rule IDs

SV-226482r505925_rule
SV-1046

If a user accesses the root account (or any account) using an unencrypted connection, the password is passed over the network in clear text form and is subject to interception and misuse. This is true even if recommended procedures are followed by logging on to a named account and using the su command to access root. Satisfies: SRG-OS-000074, SRG-OS-000520

Checks: C-28643r482831_chk

Determine if root has logged in over an unencrypted network connection. First, determine if root has logged in over a network. Procedure: # last | grep "^root " | egrep -v "reboot|console" | more Next, determine if the SSH daemon is running. Procedure: # ps -ef |grep sshd If root has logged in over the network and SSHD is not running, this is a finding.

Fix: F-28631r482832_fix

Enable SSH on the system and use it for all remote connections used to attain root access.

The system must not permit root logins using remote access programs such as SSH.

IA-2 - Medium - CCI-000770 - V-226483 - SV-226483r505925_rule

RMF Control

IA-2

Severity

CCI

Version

GEN001120

Vuln IDs

V-226483
V-1047

Rule IDs

SV-226483r505925_rule
SV-39811

Even though communications are encrypted, an additional layer of security may be gained by extending the policy of not logging directly on as root. In addition, logging in with a user-specific account preserves the audit trail.

Checks: C-28644r482834_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-28632r482835_fix

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

System files and directories must not have uneven access permissions.

AC-3 - Medium - CCI-002165 - V-226484 - SV-226484r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN001140

Vuln IDs

V-226484
V-784

Rule IDs

SV-226484r505925_rule
SV-39833

Discretionary access control is undermined if users, other than a file owner, have greater access permissions to system files and directories than the owner.

Checks: C-28645r482837_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-28633r482838_fix

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

All files and directories must have a valid owner.

CM-6 - Medium - CCI-000366 - V-226485 - SV-226485r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001160

Vuln IDs

V-226485
V-785

Rule IDs

SV-226485r505925_rule
SV-785

Unowned files and directories may be unintentionally inherited if a user is assigned the same UID as the UID of the unowned files.

Checks: C-28646r503834_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-28634r503835_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.

All files and directories must have a valid group-owner.

CM-6 - Medium - CCI-000366 - V-226486 - SV-226486r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001170

Vuln IDs

V-226486
V-22312

Rule IDs

SV-226486r505925_rule
SV-26358

Files without a valid group-owner may be unintentionally inherited if a group is assigned the same GID as the GID of the files without a valid group-owner.

Checks: C-28647r482843_chk

Search the system for files without a valid group-owner. # find / -nogroup -print If any files are found, this is a finding.

Fix: F-28635r482844_fix

Change the group owner for each file without a valid group owner. # chgrp <a-valid-group> /tmp/a-file-without-a-valid-group-owner

All network services daemon files must have mode 0755 or less permissive.

AC-3 - Medium - CCI-002165 - V-226487 - SV-226487r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN001180

Vuln IDs

V-226487
V-786

Rule IDs

SV-226487r505925_rule
SV-27161

Restricting permission on daemons will protect them from unauthorized modification and possible system compromise.

Checks: C-28648r482846_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-28636r482847_fix

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

All network services daemon files must not have extended ACLs.

CM-6 - Medium - CCI-000366 - V-226488 - SV-226488r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001190

Vuln IDs

V-226488
V-22313

Rule IDs

SV-226488r505925_rule
SV-26361

Restricting permission on daemons will protect them from unauthorized modification and possible system compromise.

Checks: C-28649r482849_chk

Verify network services daemon files have no extended ACLs. # ls -la /usr/sbin # ls -la /usr/bin If the permissions include a "+", the file has an extended ACL and 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-28637r482850_fix

Remove the extended ACL from the file. # chmod A- [file with extended ACL]

All system command files must have mode 755 or less permissive.

CM-5 - Medium - CCI-001499 - V-226489 - SV-226489r505925_rule

RMF Control

CM-5

Severity

CCI

Version

GEN001200

Vuln IDs

V-226489
V-794

Rule IDs

SV-226489r505925_rule
SV-794

Restricting permissions will protect system command files from unauthorized modification. System command files include files present in directories used by the operating system for storing default system executables and files present in directories included in the system's default executable search paths.

Checks: C-28650r482852_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-28638r482853_fix

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

All system command files must not have extended ACLs.

CM-5 - Medium - CCI-001499 - V-226490 - SV-226490r505925_rule

RMF Control

CM-5

Severity

CCI

Version

GEN001210

Vuln IDs

V-226490
V-22314

Rule IDs

SV-226490r505925_rule
SV-26365

Checks: C-28651r482855_chk

Verify all system command files have no extended ACLs. # ls -lL /etc /bin /usr/bin /usr/lbin /usr/ucb /sbin /usr/sbin If the permissions include a "+", the file has an extended ACL, this is a finding.

Fix: F-28639r482856_fix

Remove the extended ACL from the file. # chmod A- [file with extended ACL]

All system files, programs, and directories must be owned by a system account.

CM-5 - Medium - CCI-001499 - V-226491 - SV-226491r505925_rule

RMF Control

CM-5

Severity

CCI

Version

GEN001220

Vuln IDs

V-226491
V-795

Rule IDs

SV-226491r505925_rule
SV-795

Restricting permissions will protect the files from unauthorized modification.

Checks: C-28652r482858_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-28640r482859_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.)

System files, programs, and directories must be group-owned by a system group.

CM-5 - Medium - CCI-001499 - V-226492 - SV-226492r505925_rule

RMF Control

CM-5

Severity

CCI

Version

GEN001240

Vuln IDs

V-226492
V-796

Rule IDs

SV-226492r505925_rule
SV-796

Restricting permissions will protect the files from unauthorized modification.

Checks: C-28653r482861_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-28641r482862_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.)

System log files must have mode 0640 or less permissive.

SI-11 - Medium - CCI-001314 - V-226493 - SV-226493r505925_rule

RMF Control

SI-11

Severity

CCI

CCI-001314

Version

GEN001260

Vuln IDs

V-226493
V-787

Rule IDs

SV-226493r505925_rule
SV-39832

If the system log files are not protected, unauthorized users could change the logged data, eliminating its forensic value.

Checks: C-28654r482864_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-28642r482865_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.

System log files must not have extended ACLs, except as needed to support authorized software.

SI-11 - Medium - CCI-001314 - V-226494 - SV-226494r505925_rule

RMF Control

SI-11

Severity

CCI

CCI-001314

Version

GEN001270

Vuln IDs

V-226494
V-22315

Rule IDs

SV-226494r505925_rule
SV-26369

If the system log files are not protected, unauthorized users could change the logged data, eliminating its forensic value. Authorized software may be given log file access through the use of extended ACLs when needed and configured to provide the least privileges required.

Checks: C-28655r482867_chk

Verify all system log files have no extended ACLs. Procedure: # ls -lL /var/adm If the permissions include a "+", the file has an extended ACL. If an extended ACL exists, verify with the SA if the ACL is required to support authorized software and provides the minimum necessary permissions. If an extended ACL exists that provides access beyond the needs of authorized software, this is a finding.

Fix: F-28643r482868_fix

Remove the extended ACL from the file. # chmod A- [file with extended ACL]

Manual page files must have mode 0655 or less permissive.

AC-3 - Low - CCI-002165 - V-226495 - SV-226495r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN001280

Vuln IDs

V-226495
V-792

Rule IDs

SV-226495r505925_rule
SV-39835

If manual pages are compromised, misleading information could be inserted, causing actions that may compromise the system.

Checks: C-28656r482870_chk

Check the mode of the manual page files. Procedure: # ls -lLR /usr/share/man /usr/sfw/share/man /usr/sfw/man If any of the manual page files have a mode more permissive than 0655, this is a finding.

Fix: F-28644r482871_fix

Change the mode of manual page files to 0655 or less permissive. Procedure (example): # chmod 0655 <path>/<manpage>

All manual page files must not have extended ACLs.

CM-6 - Low - CCI-000366 - V-226496 - SV-226496r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001290

Vuln IDs

V-226496
V-22316

Rule IDs

SV-226496r505925_rule
SV-26373

If manual pages are compromised, misleading information could be inserted, causing actions that may compromise the system.

Checks: C-28657r482873_chk

Verify all manual page files have no extended ACLs. Check environment variable $MANPATH for full list of manpage locations. # echo $MANPATH Check for ACLs, note only a partial list is presented below. # ls -lLR /usr/share/man /usr/sfw/man /usr/sfw/share/man If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-28645r482874_fix

Remove the extended ACL from the file. # chmod A- [file with extended ACL]

All library files must not have extended ACLs.

CM-5 - Medium - CCI-001499 - V-226497 - SV-226497r505925_rule

RMF Control

CM-5

Severity

CCI

Version

GEN001310

Vuln IDs

V-226497
V-22317

Rule IDs

SV-226497r505925_rule
SV-26377

Unauthorized access could destroy the integrity of the library files.

Checks: C-28658r482879_chk

Verify system libraries have no extended ACLs. # ls -lL /usr/lib/* /lib/* /usr/sfw/lib If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-28646r482880_fix

Remove the extended ACL from the file. # chmod A- [file with extended ACL]

NIS/NIS+/yp files must be owned by root, sys, or bin.

AC-3 - Medium - CCI-002165 - V-226498 - SV-226498r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN001320

Vuln IDs

V-226498
V-789

Rule IDs

SV-226498r505925_rule
SV-27166

NIS/NIS+/yp files are part of the system's identification and authentication processes and are, therefore, critical to system security. Failure to give ownership of sensitive files or utilities to root or bin provides the designated owner and unauthorized users with the potential to access sensitive information or change the system configuration which could weaken the system's security posture.

Checks: C-28659r482882_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-28647r482883_fix

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

NIS/NIS+/yp files must be group-owned by root, sys, or bin.

AC-3 - Medium - CCI-002165 - V-226499 - SV-226499r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN001340

Vuln IDs

V-226499
V-790

Rule IDs

SV-226499r505925_rule
SV-27171

Checks: C-28660r482885_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-28648r482886_fix

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

The NIS/NIS+/yp command files must have mode 0755 or less permissive.

AC-3 - Medium - CCI-002165 - V-226500 - SV-226500r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN001360

Vuln IDs

V-226500
V-791

Rule IDs

SV-226500r505925_rule
SV-27175

NIS/NIS+/yp files are part of the system's identification and authentication processes and are, therefore, critical to system security. Unauthorized modification of these files could compromise these processes and the system.

Checks: C-28661r482888_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-28649r482889_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

NIS/NIS+/yp command files must not have extended ACLs.

CM-6 - Medium - CCI-000366 - V-226501 - SV-226501r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001361

Vuln IDs

V-226501
V-22318

Rule IDs

SV-226501r505925_rule
SV-26388

NIS/NIS+/yp files are part of the system's identification and authentication processes and are, therefore, critical to system security. ACLs on these files could result in unauthorized modification, which could compromise these processes and the system.

Checks: C-28662r482891_chk

Verify NIS/NIS+/yp files have no extended ACLs. # ls -lLRa /usr/lib/netsvc/yp /var/yp If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-28650r482892_fix

Remove the extended ACL from the directory and files. # chmod -R A- /usr/lib/netsvc/yp /var/yp

The /etc/resolv.conf file must be owned by root.

CM-6 - Medium - CCI-000366 - V-226502 - SV-226502r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001362

Vuln IDs

V-226502
V-22319

Rule IDs

SV-226502r505925_rule
SV-26395

The resolv.conf (or equivalent) file configures the system's DNS resolver. DNS is used to resolve host names to IP addresses. If DNS configuration is modified maliciously, host name resolution may fail or return incorrect information. DNS may be used by a variety of system security functions, such as time synchronization, centralized authentication, and remote system logging.

Checks: C-28663r482894_chk

Verify the /etc/resolv.conf file is owned by root. Procedure: # ls -l /etc/resolv.conf If the file is not owned by root, this is a finding.

Fix: F-28651r482895_fix

Change the owner of the /etc/resolv.conf file to root. # chown root /etc/resolv.conf

The /etc/resolv.conf file must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226503 - SV-226503r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001363

Vuln IDs

V-226503
V-22320

Rule IDs

SV-226503r505925_rule
SV-39894

The resolv.conf (or equivalent) file configures the system's DNS resolver. DNS is used to resolve host names to IP addresses. If DNS configuration is modified maliciously, host name resolution may fail or return incorrect information. DNS may be used by a variety of system security functions such as time synchronization, centralized authentication, and remote system logging.

Checks: C-28664r482897_chk

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

Fix: F-28652r482898_fix

Change the group owner of the /etc/resolv.conf file to root, bin, or sys. Procedure: # chgrp root /etc/resolv.conf

The /etc/resolv.conf file must have mode 0644 or less permissive.

CM-6 - Medium - CCI-000366 - V-226504 - SV-226504r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001364

Vuln IDs

V-226504
V-22321

Rule IDs

SV-226504r505925_rule
SV-26397

Checks: C-28665r482900_chk

Check the mode of the /etc/resolv.conf file. Procedure: # ls -l /etc/resolv.conf If the file mode is more permissive than 0644, this is a finding.

Fix: F-28653r482901_fix

Change the mode of the /etc/resolv.conf file to 0644 or less permissive. # chmod 0644 /etc/resolv.conf

The /etc/resolv.conf file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226505 - SV-226505r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001365

Vuln IDs

V-226505
V-22322

Rule IDs

SV-226505r505925_rule
SV-26402

The resolv.conf (or equivalent) file configures the system's DNS resolver. DNS is used to resolve host names to IP addresses. If DNS configuration is modified maliciously, host name resolution may fail or return incorrect information. DNS may be used by a variety of system security functions such as time synchronization, centralized authentication, and remote system logging.

Checks: C-28666r482903_chk

Verify /etc/resolv.conf has no extended ACL. # ls -l /etc/resolv.conf If the permissions include a "+", the file has an extended ACL, this is a finding.

Fix: F-28654r482904_fix

Remove the extended ACL from the file. # chmod A- /etc/resolv.conf

The /etc/hosts file must be owned by root.

CM-6 - Medium - CCI-000366 - V-226506 - SV-226506r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001366

Vuln IDs

V-226506
V-22323

Rule IDs

SV-226506r505925_rule
SV-26410

The /etc/hosts file (or equivalent) configures local host name to IP address mappings that typically take precedence over DNS resolution. If this file is maliciously modified, it could cause the failure or compromise of security functions requiring name resolution, which may include time synchronization, centralized authentication, and remote system logging.

Checks: C-28667r482906_chk

Verify the /etc/hosts file is owned by root. Procedure: # ls -lL /etc/hosts If the file is not owned by root, this is a finding.

Fix: F-28655r482907_fix

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

The /etc/hosts file must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226507 - SV-226507r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001367

Vuln IDs

V-226507
V-22324

Rule IDs

SV-226507r505925_rule
SV-39896

Checks: C-28668r482909_chk

Check the /etc/hosts file's group ownership. Procedure: # ls -lL /etc/hosts If the file is not group-owned by root, bin, or sys, this is a finding.

Fix: F-28656r482910_fix

Change the group owner of the /etc/hosts file to root, sys, or bin. Procedure: # chgrp root /etc/hosts

The /etc/hosts file must have mode 0644 or less permissive.

CM-6 - Medium - CCI-000366 - V-226508 - SV-226508r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001368

Vuln IDs

V-226508
V-22325

Rule IDs

SV-226508r505925_rule
SV-26412

Checks: C-28669r482912_chk

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

Fix: F-28657r482913_fix

Change the mode of the /etc/hosts file to 0644 or less permissive. # chmod 0644 /etc/hosts

The /etc/hosts file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226509 - SV-226509r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001369

Vuln IDs

V-226509
V-22326

Rule IDs

SV-226509r505925_rule
SV-26415

Checks: C-28670r482915_chk

Verify /etc/hosts has no extended ACL. # ls -lL /etc/hosts If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-28658r482916_fix

Remove the extended ACL from the file. # chmod A- /etc/hosts

The /etc/nsswitch.conf file must be owned by root.

CM-6 - Medium - CCI-000366 - V-226510 - SV-226510r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001371

Vuln IDs

V-226510
V-22327

Rule IDs

SV-226510r505925_rule
SV-26417

The nsswitch.conf file (or equivalent) configures the source of a variety of system security information including account, group, and host lookups. Malicious changes could prevent the system from functioning or compromise system security.

Checks: C-28671r482918_chk

Verify the /etc/nsswitch.conf file is owned by root. Procedure: # ls -l /etc/nsswitch.conf If the file is not owned by root, this is a finding.

Fix: F-28659r482919_fix

Change the owner of the /etc/nsswitch.conf file to root. # chown root /etc/nsswitch.conf

The /etc/nsswitch.conf file must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226511 - SV-226511r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001372

Vuln IDs

V-226511
V-22328

Rule IDs

SV-226511r505925_rule
SV-39897

Checks: C-28672r482921_chk

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

Fix: F-28660r482922_fix

Change the group owner of the /etc/nsswitch.conf file to root, bin, or sys. Procedure: # chgrp root /etc/nsswitch.conf

The /etc/nsswitch.conf file must have mode 0644 or less permissive.

CM-6 - Medium - CCI-000366 - V-226512 - SV-226512r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001373

Vuln IDs

V-226512
V-22329

Rule IDs

SV-226512r505925_rule
SV-26419

Checks: C-28673r482924_chk

Check the mode of the /etc/nsswitch.conf file. Procedure: # ls -l /etc/nsswitch.conf If the file mode is more permissive than 0644, this is a finding.

Fix: F-28661r482925_fix

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

The /etc/nsswitch.conf file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226513 - SV-226513r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001374

Vuln IDs

V-226513
V-22330

Rule IDs

SV-226513r505925_rule
SV-26422

Checks: C-28674r482927_chk

Verify /etc/nsswitch.conf has no extended ACL. Procedure: # ls -l /etc/nsswitch.conf If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-28662r482928_fix

Remove the extended ACL from the file. # chmod A- /etc/nsswitch.conf

The /etc/passwd file must be owned by root.

CM-6 - Medium - CCI-000366 - V-226514 - SV-226514r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001378

Vuln IDs

V-226514
V-22332

Rule IDs

SV-226514r505925_rule
SV-26425

The /etc/passwd file contains the list of local system accounts. It is vital to system security and must be protected from unauthorized modification.

Checks: C-28675r482930_chk

Verify the /etc/passwd file is owned by root. Procedure: # ls -l /etc/passwd If the file is not owned by root, this is a finding.

Fix: F-28663r482931_fix

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

The /etc/passwd file must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226515 - SV-226515r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001379

Vuln IDs

V-226515
V-22333

Rule IDs

SV-226515r505925_rule
SV-39898

The /etc/passwd file contains the list of local system accounts. It is vital to system security and must be protected from unauthorized modification.

Checks: C-28676r482933_chk

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

Fix: F-28664r482934_fix

Change the group owner of the /etc/passwd file to root, bin, or sys. Procedure: # chgrp root /etc/passwd

The /etc/passwd file must have mode 0644 or less permissive.

AC-3 - Medium - CCI-002165 - V-226516 - SV-226516r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN001380

Vuln IDs

V-226516
V-798

Rule IDs

SV-226516r505925_rule
SV-798

If the password file is writable by a group owner or the world, the risk of password file compromise is increased. The password file contains the list of accounts on the system and associated information.

Checks: C-28677r482936_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-28665r482937_fix

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

The /etc/passwd file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226517 - SV-226517r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001390

Vuln IDs

V-226517
V-22334

Rule IDs

SV-226517r505925_rule
SV-26429

File system ACLs can provide access to files beyond what is allowed by the mode numbers of the files. The /etc/passwd file contains the list of local system accounts. It is vital to system security and must be protected from unauthorized modification.

Checks: C-28678r482939_chk

Verify /etc/passwd has no extended ACL. # ls -l /etc/passwd If the permissions include a "+", the file has an extended ACL, this is a finding.

Fix: F-28666r482940_fix

Remove the extended ACL from the file. # chmod A- /etc/passwd

The /etc/group file must be owned by root.

CM-6 - Medium - CCI-000366 - V-226518 - SV-226518r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001391

Vuln IDs

V-226518
V-22335

Rule IDs

SV-226518r505925_rule
SV-26431

The /etc/group file is critical to system security and must be owned by a privileged user. The group file contains a list of system groups and associated information.

Checks: C-28679r482942_chk

Verify the /etc/group file is owned by root. Procedure: # ls -l /etc/group If the file is not owned by root, this is a finding.

Fix: F-28667r482943_fix

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

The /etc/group file must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226519 - SV-226519r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001392

Vuln IDs

V-226519
V-22336

Rule IDs

SV-226519r505925_rule
SV-39899

The /etc/group file is critical to system security and must be protected from unauthorized modification. The group file contains a list of system groups and associated information.

Checks: C-28680r482945_chk

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

Fix: F-28668r482946_fix

Change the group owner of the /etc/group file. Procedure: # chgrp root /etc/group

The /etc/group file must have mode 0644 or less permissive.

CM-6 - Medium - CCI-000366 - V-226520 - SV-226520r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001393

Vuln IDs

V-226520
V-22337

Rule IDs

SV-226520r505925_rule
SV-26433

The /etc/group file is critical to system security and must be protected from unauthorized modification. The group file contains a list of system groups and associated information.

Checks: C-28681r482948_chk

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

Fix: F-28669r482949_fix

Change the mode of the /etc/group file to 0644 or less permissive. # chmod 0644 /etc/group

The /etc/group file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226521 - SV-226521r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001394

Vuln IDs

V-226521
V-22338

Rule IDs

SV-226521r505925_rule
SV-26436

The /etc/group file is critical to system security and must be protected from unauthorized modification. The group file contains a list of system groups and associated information.

Checks: C-28682r482951_chk

Verify /etc/group has no extended ACL. # ls -l /etc/group If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-28670r482952_fix

Remove the extended ACL from the file. # chmod A- /etc/group

The /etc/shadow (or equivalent) file must be owned by root.

AC-3 - Medium - CCI-002165 - V-226522 - SV-226522r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN001400

Vuln IDs

V-226522
V-797

Rule IDs

SV-226522r505925_rule
SV-39826

The /etc/shadow file contains the list of local system accounts. It is vital to system security and must be protected from unauthorized modification. Failure to give ownership of sensitive files or utilities to root provides the designated owner and unauthorized users with the potential to access sensitive information or change the system configuration which could weaken the system's security posture.

Checks: C-28683r482954_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-28671r482955_fix

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

The /etc/shadow file (or equivalent) must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226523 - SV-226523r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001410

Vuln IDs

V-226523
V-22339

Rule IDs

SV-226523r505925_rule
SV-39900

The /etc/shadow file contains the list of local system accounts. It is vital to system security and must be protected from unauthorized modification. The file also contains password hashes which must not be accessible to users other than root.

Checks: C-28684r482957_chk

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

Fix: F-28672r482958_fix

Change the group owner of the /etc/shadow file. Procedure: # chgrp root /etc/shadow

The /etc/shadow (or equivalent) file must have mode 0400.

AC-3 - Medium - CCI-002165 - V-226524 - SV-226524r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN001420

Vuln IDs

V-226524
V-800

Rule IDs

SV-226524r505925_rule
SV-800

Checks: C-28685r482960_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-28673r482961_fix

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

The /etc/shadow file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226525 - SV-226525r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001430

Vuln IDs

V-226525
V-22340

Rule IDs

SV-226525r505925_rule
SV-26440

Checks: C-28686r482963_chk

Verify /etc/shadow has no extended ACL. # ls -lL /etc/shadow If the permissions include a '+', the file has an extended ACL and this is a finding.

Fix: F-28674r482964_fix

Remove the extended ACL from the file. # chmod A- /etc/shadow

All interactive users must be assigned a home directory in the /etc/passwd file.

CM-6 - Low - CCI-000366 - V-226526 - SV-226526r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001440

Vuln IDs

V-226526
V-899

Rule IDs

SV-226526r505925_rule
SV-27184

If users do not have a valid home directory, there is no place for the storage and control of files they own.

Checks: C-28687r482966_chk

Use pwck to verify home directory assignments are present. # pwck If any user is not assigned a home directory, this is a finding.

Fix: F-28675r482967_fix

Assign a home directory to any user without one.

All interactive user home directories defined in the /etc/passwd file must exist.

CM-6 - Low - CCI-000366 - V-226527 - SV-226527r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001460

Vuln IDs

V-226527
V-900

Rule IDs

SV-226527r505925_rule
SV-27192

If a user has a home directory defined that does not exist, the user may be given the / directory, by default, as the current working directory upon logon. This could create a Denial of Service because the user would not be able to perform useful tasks in this location.

Checks: C-28688r503837_chk

Use pwck to verify assigned home directories exist. # pwck If any user's assigned home directory does not exist, this is a finding.

Fix: F-28676r503838_fix

If a user has no home directory, determine why. If possible, delete accounts that have no home directory. If the account is valid, then create the home directory using the appropriate system administration utility or manually. For instance: mkdir directoryname; copy the skeleton files into the directory; chown accountname for the new directory and the skeleton files. Document all changes. Update the sixth field in the /etc/passwd file to reflect the user's home directory. # usermod -d OR # vi /etc/passwd

The /etc/passwd file must not contain password hashes.

IA-5 - Medium - CCI-000196 - V-226528 - SV-226528r505925_rule

RMF Control

IA-5

Severity

CCI

CCI-000196

Version

GEN001470

Vuln IDs

V-226528
V-22347

Rule IDs

SV-226528r505925_rule
SV-26467

If password hashes are readable by non-administrators, the passwords are subject to attack through lookup tables or cryptographic weaknesses in the hashes.

Checks: C-28689r482972_chk

Verify no password hashes are present in /etc/passwd. # cut -d : -f 2 /etc/passwd | grep -v '^x$' If any password hashes are returned, this is a finding.

Fix: F-28677r482973_fix

Migrate /etc/passwd password hashes to /etc/shadow. # pwconv

The /etc/group file must not contain any group password hashes.

CM-6 - Medium - CCI-000366 - V-226529 - SV-226529r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001475

Vuln IDs

V-226529
V-22348

Rule IDs

SV-226529r505925_rule
SV-26447

Group passwords are typically shared and should not be used. Additionally, if password hashes are readable by non-administrators, the passwords are subject to attack through lookup tables or cryptographic weaknesses in the hashes.

Checks: C-28690r482975_chk

Check the /etc/group file for password hashes. Procedure: # cut -d : -f 2 /etc/group | egrep -v '^(x|!)$' If any password hashes are returned, this is a finding. If no password hashes are returned, there is no finding.

Fix: F-28678r482976_fix

Edit /etc/group and change the password field to an exclamation point (!) to lock the group password.

All users' home directories must have mode 0750 or less permissive.

AC-3 - Medium - CCI-002165 - V-226530 - SV-226530r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN001480

Vuln IDs

V-226530
V-901

Rule IDs

SV-226530r505925_rule
SV-901

Excessive permissions on home directories allow unauthorized access to user's files.

Checks: C-28691r482978_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-28679r482979_fix

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

User's home directories must not have extended ACLs.

CM-6 - Low - CCI-000366 - V-226531 - SV-226531r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001490

Vuln IDs

V-226531
V-22350

Rule IDs

SV-226531r505925_rule
SV-26451

Excessive permissions on home directories allow unauthorized access to user's files.

Checks: C-28692r482981_chk

Verify user's home directories have no extended ACLs. # cut -d : -f 6 /etc/passwd | xargs -n1 ls -ld If the permissions include a "+", the file has an extended ACL, this is a finding.

Fix: F-28680r482982_fix

Remove the extended ACL from the file. # chmod A- [user home directory with extended ACL]

All files and directories contained in interactive user's home directories must be owned by the home directory's owner.

CM-6 - Low - CCI-000366 - V-226532 - SV-226532r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001540

Vuln IDs

V-226532
V-914

Rule IDs

SV-226532r505925_rule
SV-39836

If users do not own the files in their directories, unauthorized users may be able to access them. Additionally, if files are not owned by the user, this could be an indication of system compromise.

Checks: C-28693r503840_chk

For each user in the /etc/passwd file, check for the presence of files and directories within the user's home directory not owned by the home directory owner or root. Procedure: # cut -d : -f 6 /etc/passwd | xargs -n1 -IDIR ls -alLR DIR | more OR # find /<usershomedirectory> ! -fstype nfs ! -user <username> -exec ls -ld {} \; | more If user's home directories contain files or directories not owned by the home directory owner or root, this is a finding.

Fix: F-28681r503841_fix

Change the ownership of files and directories in user's home directories to the owner of the home directory. Procedure: # chown accountowner filename OR # find /<usershomedirectory> ! -fstype nfs ! -user <username> ! /( -name .login -o -name .cshrc -o -name .logout -o -name .profile -o -name .bash_profile -o -name .bashrc -o -name .env -o -name .dtprofile -o -name .dispatch -o -name .emacs -o -name .exrc \) -exec chown <username> {} \;

All files and directories contained in user home directories must be group-owned by a group of which the home directory's owner is a member.

CM-6 - Medium - CCI-000366 - V-226533 - SV-226533r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001550

Vuln IDs

V-226533
V-22351

Rule IDs

SV-226533r505925_rule
SV-39877

If a user's files are group-owned by a group of which the user is not a member, unintended users may be able to access them.

Checks: C-28694r482993_chk

Check the contents of user home directories for files group-owned by a group of which the home directory's owner is not a member. 1. List the user accounts. # cut -d : -f 1/etc/passwd 2. For each user account, get a list of GIDs for files in the user's home directory. # find < users home directory > -exec ls -lLd \; 3. Obtain the list of GIDs associated with the user's account. # id < user name > 4. Check the GID lists. If there are GIDs in the file list not present in the user list, this is a finding.

Fix: F-28682r482994_fix

Change the group of a file not group-owned by a group where the home directory's owner is a member. # chgrp < user's primary group > <file with bad group ownership >

All files and directories contained in user's home directories must have mode 0750 or less permissive.

CM-6 - Low - CCI-000366 - V-226534 - SV-226534r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001560

Vuln IDs

V-226534
V-915

Rule IDs

SV-226534r505925_rule
SV-39840

Excessive permissions allow unauthorized access to user's files.

Checks: C-28695r482996_chk

For each user in the /etc/passwd file, check for files and directories with a mode more permissive than 0750. Procedure: # find /<usershomedirectory> ! -fstype nfs $ -perm -0001 -o -perm -0002 -o -perm -0004 -o -perm -0020 -o -perm -2000 -o -perm -4000 $ -exec ls -ld {} \; If user's home directories contain files or directories more permissive than 0750, this is a finding.

Fix: F-28683r482997_fix

Change the mode of files and directories within user's home directories to 0750. Procedure: # chmod 0750 filename Document all changes.

All files and directories contained in user home directories must not have extended ACLs.

CM-6 - Medium - CCI-000366 - V-226535 - SV-226535r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001570

Vuln IDs

V-226535
V-22352

Rule IDs

SV-226535r505925_rule
SV-26456

Excessive permissions allow unauthorized access to user files.

Checks: C-28696r482999_chk

Check the contents of interactive user's home directories (99 < UID < 60000) for files with extended ACLs. # ls -alLR < users home dir > If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-28684r483000_fix

Remove the extended ACL from the file. # chmod A- [user file with extended ACL]

All run control scripts must have mode 0755 or less permissive.

CM-6 - Medium - CCI-000366 - V-226536 - SV-226536r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001580

Vuln IDs

V-226536
V-906

Rule IDs

SV-226536r505925_rule
SV-27199

If the startup files are writable by other users, they could modify the startup files to insert malicious commands into the startup files.

Checks: C-28697r503843_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-28685r503844_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>

All run control scripts must have no extended ACLs.

CM-6 - Medium - CCI-000366 - V-226537 - SV-226537r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001590

Vuln IDs

V-226537
V-22353

Rule IDs

SV-226537r505925_rule
SV-26460

If the startup files are writable by other users, they could modify the startup files to insert malicious commands into the startup files.

Checks: C-28698r483005_chk

Verify run control scripts have no extended ACLs. # ls -lL /etc/rc* /etc/init.d If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-28686r483006_fix

Remove the extended ACL from the file. # chmod A- [run control script with extended ACL]

Run control scripts executable search paths must contain only authorized paths.

CM-6 - Medium - CCI-000366 - V-226538 - SV-226538r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001600

Vuln IDs

V-226538
V-907

Rule IDs

SV-226538r505925_rule
SV-39837

The executable search path (typically the PATH environment variable) contains a list of directories for the shell to search to find executables. If this path includes the current working directory or other relative paths, executables in these directories may be executed instead of system commands. This variable is formatted as a colon-separated list of directories. If there is an empty entry, such as a leading or trailing colon, two consecutive colons, or a single period, this is interpreted as the current working directory. Paths starting with a slash (/) are absolute paths.

Checks: C-28699r483008_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-28687r483009_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.

Run control scripts lists of preloaded libraries must contain only authorized paths.

CM-6 - Medium - CCI-000366 - V-226539 - SV-226539r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001605

Vuln IDs

V-226539
V-22354

Rule IDs

SV-226539r505925_rule
SV-26462

The library preload list environment variable contains a list of libraries for the dynamic linker to load before loading the libraries required by the binary. If this list contains paths to libraries to the current working directory that have not been authorized, unintended libraries may be preloaded. This variable is formatted as a space-separated list of libraries. Paths starting with a slash (/) are absolute paths.

Checks: C-28700r483011_chk

Verify run control scripts' library preload list. Procedure: # find /etc/rc* /etc/init.d -type f -print | xargs grep LD_PRELOAD This variable is formatted as a colon-separated list of paths. 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-28688r483012_fix

Edit the run control script and remove the relative path entry from the library preload variables that are not documented with the ISSO. Edit the run control script and remove any empty entry that is defined.

Run control scripts lists of preloaded libraries must contain only authorized paths.

CM-6 - Medium - CCI-000366 - V-226540 - SV-226540r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001610

Vuln IDs

V-226540
V-22355

Rule IDs

SV-226540r505925_rule
SV-26464

The library preload list environment variable contains a list of libraries for the dynamic linker to load before loading the libraries required by the binary. If this list contains paths to libraries to the current working directory that have not been authorized, unintended libraries may be preloaded. This variable is formatted as a space-separated list of libraries. Paths starting with a slash (/) are absolute paths.

Checks: C-28701r483014_chk

Fix: F-28689r483015_fix

Run control scripts must not execute world-writable programs or scripts.

CM-6 - High - CCI-000366 - V-226541 - SV-226541r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001640

Vuln IDs

V-226541
V-910

Rule IDs

SV-226541r505925_rule
SV-39810

World-writable files could be modified accidentally or maliciously to compromise system integrity.

Checks: C-28702r483017_chk

Check the permissions on the files or scripts executed from system startup scripts to see if they are world-writable. Create a list of all potential run command level scripts. # ls -l /etc/init.d/* | tr '\011' ' ' | tr -s ' ' | cut -f 9,9 -d " " OR # ls -l /sbin/init.d/* | tr '\011' ' ' | tr -s ' ' | cut -f 9,9 -d " " Create a list of world writeable files. # find / -perm -002 -type f >> worldWriteableFileList Determine if any of the world writeable files in worldWriteableFileList are called from the run command level scripts. Note: Depending upon the number of scripts vs world writeable files, it may be easier to inspect the scripts manually. # more `ls -l /etc/init.d/* | tr '\011' ' ' | tr -s ' ' | cut -f 9,9 -d " "` OR # more `ls -l /sbin/init.d/* | tr '\011' ' ' | tr -s ' ' | cut -f 9,9 -d " "` If any system startup script executes any file or script that is world-writable, this is a finding.

Fix: F-28690r483018_fix

Remove the world-writable permission from programs or scripts executed by run control scripts. Procedure: # chmod o-w <program or script executed from run control script>

All system start-up files must be owned by root.

CM-6 - Medium - CCI-000366 - V-226542 - SV-226542r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001660

Vuln IDs

V-226542
V-4089

Rule IDs

SV-226542r505925_rule
SV-27207

System start-up files not owned by root could lead to system compromise by allowing malicious users or applications to modify them for unauthorized purposes. This could lead to system and network compromise.

Checks: C-28703r483020_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-28691r483021_fix

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

All system start-up files must be group-owned by root, sys, or bin.

CM-6 - Medium - CCI-000366 - V-226543 - SV-226543r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001680

Vuln IDs

V-226543
V-4090

Rule IDs

SV-226543r505925_rule
SV-27213

If system start-up files do not have a group owner of root or a system group, the files may be modified by malicious users or intruders.

Checks: C-28704r483023_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-28692r483024_fix

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

System start-up files must only execute programs owned by a privileged UID or an application.

CM-6 - Medium - CCI-000366 - V-226544 - SV-226544r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001700

Vuln IDs

V-226544
V-4091

Rule IDs

SV-226544r505925_rule
SV-27219

System start-up files executing programs owned by other than root (or another privileged user) or an application indicates the system may have been compromised.

Checks: C-28705r483026_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 <executed program> If any executed program is not owned by root, sys, bin, or in rare cases, an application account, this is a finding.

Fix: F-28693r483027_fix

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

All global initialization files must not have extended ACLs.

CM-6 - Medium - CCI-000366 - V-226545 - SV-226545r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001730

Vuln IDs

V-226545
V-22356

Rule IDs

SV-226545r505925_rule
SV-26471

Global initialization files are used to configure the user's shell environment upon login. Malicious modification of these files could compromise accounts upon logon.

Checks: C-28706r483032_chk

Check global initialization files for extended ACLs. # ls -lL /etc/profile /etc/bashrc /etc/csh.login /etc/csh.cshrc /etc/environment /etc/.login /etc/security/environ If the permissions on an existing file include a "+", the file has an extended ACL, this is a finding.

Fix: F-28694r483033_fix

Remove the extended ACL from the file. # chmod A- [global initialization file with extended ACL]

All skeleton files (typically those in /etc/skel) must have mode 0644 or less permissive.

AC-3 - Medium - CCI-002165 - V-226546 - SV-226546r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN001800

Vuln IDs

V-226546
V-788

Rule IDs

SV-226546r505925_rule
SV-788

If the skeleton files are not protected, unauthorized personnel could change user startup parameters and possibly jeopardize user files.

Checks: C-28707r483044_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-28695r483045_fix

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

Skeleton files must not have extended ACLs.

CM-6 - Medium - CCI-000366 - V-226547 - SV-226547r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001810

Vuln IDs

V-226547
V-22357

Rule IDs

SV-226547r505925_rule
SV-26475

If the skeleton files are not protected, unauthorized personnel could change user's startup parameters and possibly jeopardize user's files.

Checks: C-28708r483047_chk

Check skeleton files for extended ACLs. # ls -alL /etc/skel If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-28696r483048_fix

Remove the extended ACL from the file. # chmod A- [skeleton file with extended ACL]

All skeleton files and directories (typically in /etc/skel) must be owned by root.

CM-6 - Medium - CCI-000366 - V-226548 - SV-226548r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001820

Vuln IDs

V-226548
V-11984

Rule IDs

SV-226548r505925_rule
SV-12485

If the skeleton files are not protected, unauthorized personnel could change user startup parameters and possibly jeopardize user files. Failure to give ownership of sensitive files or utilities to root provides the designated owner and unauthorized users with the potential to access sensitive information or change the system configuration which could weaken the system's security posture.

Checks: C-28709r483050_chk

Check skeleton files ownership. # ls -alL /etc/skel If a skeleton file is not owned by root, this is a finding.

Fix: F-28697r483051_fix

Change the ownership of skeleton files with incorrect mode. # chown root <skeleton file>

All skeleton files (typically in /etc/skel) must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226549 - SV-226549r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001830

Vuln IDs

V-226549
V-22358

Rule IDs

SV-226549r505925_rule
SV-39901

If the skeleton files are not protected, unauthorized personnel could change user startup parameters and possibly jeopardize user files.

Checks: C-28710r483053_chk

Verify the skeleton files are group-owned by root, bin, or sys. Procedure: # ls -alL /etc/skel If a skeleton file is not group-owned by root, bin, or sys, this is a finding.

Fix: F-28698r483054_fix

Change the group owner of the skeleton file to root. Procedure: # chgrp <group> /etc/skel/[skeleton file]

All global initialization files executable search paths must contain only authorized paths.

CM-6 - Medium - CCI-000366 - V-226550 - SV-226550r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001840

Vuln IDs

V-226550
V-11985

Rule IDs

SV-226550r505925_rule
SV-12486

The executable search path (typically the PATH environment variable) contains a list of directories for the shell to search to find executables. If this path includes the current working directory or other relative paths, executables in these directories may be executed instead of system commands. This variable is formatted as a colon-separated list of directories. If there is an empty entry, such as a leading or trailing colon, two consecutive colons, or a single period, this is interpreted as the current working directory. Paths starting with a slash (/) are absolute paths.

Checks: C-28711r503846_chk

Check the global initialization files' executable search paths. Procedure: # grep -i PATH /etc/profile /etc/bashrc /etc/csh.login /etc/csh.cshrc /etc/environment /etc/.login /etc/security/environ 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-28699r503847_fix

Edit the global initialization file(s) with PATH variables containing relative paths and remove any relative path form the PATH variables that have not been documented with the ISSO. Edit the global initialization file(s) and remove any empty entry that is defined.

Global initialization files library search paths must contain only authorized paths.

CM-6 - Medium - CCI-000366 - V-226551 - SV-226551r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001845

Vuln IDs

V-226551
V-22359

Rule IDs

SV-226551r505925_rule
SV-26478

The library search path environment variable(s) contain a list of directories for the dynamic linker to search to find libraries. If this path includes the current working directory or other relative paths, libraries in these directories may be loaded instead of system libraries. This variable is formatted as a colon-separated list of directories. If there is an empty entry, such as a leading or trailing colon, two consecutive colons, or a single period, this is interpreted as the current working directory. Paths starting with a slash (/) are absolute paths.

Checks: C-28712r483059_chk

Check the global initialization files' library search paths. # grep LD_LIBRARY_PATH /etc/profile /etc/bashrc /etc/csh.login /etc/csh.cshrc /etc/environment /etc/.login /etc/security/environ 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-28700r483060_fix

Edit the global initialization file and remove the relative path entries from the library search path variables that have not been documented with the ISSO. Edit the global initialization file(s) and remove any empty entry that is defined.

Global initialization files lists of preloaded libraries must contain only authorized paths.

CM-6 - Medium - CCI-000366 - V-226552 - SV-226552r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001850

Vuln IDs

V-226552
V-22360

Rule IDs

SV-226552r505925_rule
SV-39839

The library preload list environment variable contains a list of libraries for the dynamic linker to load before loading the libraries required by the binary. If this list contains paths to libraries to the current working directory that have not been authorized, unintended libraries may be preloaded. This variable is formatted as a space-separated list of libraries. Paths starting with a slash (/) are absolute paths.

Checks: C-28713r483062_chk

Check the global initialization files' library preload list. Procedure: # grep LD_PRELOAD /etc/profile /etc/bashrc /etc/csh.login /etc/csh.cshrc /etc/environment /etc/.login /etc/security/environ This variable is formatted as a colon-separated list of paths. 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-28701r483063_fix

Edit the global initialization file(s) and remove the relative path entry from the library preload list variables that have not been documented with the ISSO. Edit the global initialization file(s) and remove any empty entry that is defined.

All local initialization files must be owned by the user or root.

CM-6 - Medium - CCI-000366 - V-226553 - SV-226553r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001860

Vuln IDs

V-226553
V-904

Rule IDs

SV-226553r505925_rule
SV-904

Local initialization files are used to configure the user's shell environment upon login. Malicious modification of these files could compromise accounts upon logon.

Checks: C-28714r503849_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-28702r503850_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.

All local initialization files must have mode 0740 or less permissive.

CM-6 - Medium - CCI-000366 - V-226554 - SV-226554r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001880

Vuln IDs

V-226554
V-905

Rule IDs

SV-226554r505925_rule
SV-905

Local initialization files are used to configure the user's shell environment upon login. Malicious modification of these files could compromise accounts upon logon.

Checks: C-28715r503852_chk

Check the modes of local initialization files. Procedure: # ls -al /<usershomedirectory>/.login # ls -al /<usershomedirectory>/.cshrc # ls -al /<usershomedirectory>/.logout # ls -al /<usershomedirectory>/.profile # ls -al /<usershomedirectory>/.bash_profile # ls -al /<usershomedirectory>/.bashrc # ls -al /<usershomedirectory>/.bash_logout # ls -al /<usershomedirectory>/.env # ls -al /<usershomedirectory>/.dtprofile (permissions should be 0755) # ls -al /<usershomedirectory>/.dispatch # ls -al /<usershomedirectory>/.emacs # ls -al /<usershomedirectory>/.exrc # find /<usershomedirectory>/.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-28703r503853_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.

Local initialization files must not have extended ACLs.

CM-6 - Medium - CCI-000366 - V-226555 - SV-226555r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001890

Vuln IDs

V-226555
V-22362

Rule IDs

SV-226555r505925_rule
SV-26484

Local initialization files are used to configure the user's shell environment upon login. Malicious modification of these files could compromise accounts upon logon.

Checks: C-28716r483074_chk

Check user home directories for local initialization files with extended ACLs. # cut -d : -f 6 /etc/passwd | xargs -n1 -IDIR ls -alL DIR/.login DIR/.cshrc DIR/.logout DIR/.profile DIR/.bash_profile DIR/.bashrc DIR/.bash_logout DIR/.env DIR/.dtprofile DIR/.dispatch DIR/.emacs DIR/.exrc If the permissions include a "+", the file has an extended ACL, this is a finding.

Fix: F-28704r483075_fix

Remove the extended ACL from the file. # chmod A- [local initialization file with extended ACL]

All local initialization files executable search paths must contain only authorized paths.

CM-6 - Medium - CCI-000366 - V-226556 - SV-226556r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001900

Vuln IDs

V-226556
V-11986

Rule IDs

SV-226556r505925_rule
SV-12487

The executable search path (typically the PATH environment variable) contains a list of directories for the shell to search to find executables. If this path includes the current working directory or other relative paths, executables in these directories may be executed instead of system commands. This variable is formatted as a colon-separated list of directories. If there is an empty entry, such as a leading or trailing colon, two consecutive colons, or a single period, this is interpreted as the current working directory. Paths starting with a slash (/) are absolute paths.

Checks: C-28717r483077_chk

NOTE: The following must be done in the BASH shell. Examine the PATH variable contained in any user's local initialization files using a command shell that supports the use of ~USER as USER's home directory. # cat /etc/passwd | cut -f 1,1 -d ":" | xargs -n1 -IUSER sh -c 'grep -i PATH ~USER/.*' The PATH variable is a colon-delimited directory list. 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-28705r483078_fix

Edit the local initialization file(s) and remove the relative path entries from the PATH variable that have not been documented with the ISSO. Edit the local initialization file(s) and remove any empty entry that is defined.

Local initialization files library search paths must contain only authorized paths.

CM-6 - Medium - CCI-000366 - V-226557 - SV-226557r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001901

Vuln IDs

V-226557
V-22363

Rule IDs

SV-226557r505925_rule
SV-26486

The library search path environment variable(s) contain a list of directories for the dynamic linker to search to find libraries. If this path includes the current working directory or other relative paths, libraries in these directories may be loaded instead of system libraries. This variable is formatted as a colon-separated list of directories. If there is an empty entry, such as a leading or trailing colon, two consecutive colons, or a single period, this is interpreted as the current working directory. Paths starting with a slash (/) are absolute paths.

Checks: C-28718r483080_chk

NOTE: This command should be used in the BASH shell. Verify local initialization files have library search path containing only authorized paths. # cut -d : -f 1 /etc/passwd | xargs -n1 -IUSER sh -c 'grep -l LD_LIBRARY_PATH ~USER/.*' 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-28706r483081_fix

Edit the local initialization file and remove the relative path entries from the library search path variables that have not been documented with the ISSO. Edit the local initialization file and remove any empty entry that is defined.

Local initialization files lists of preloaded libraries must contain only authorized paths.

CM-6 - Medium - CCI-000366 - V-226558 - SV-226558r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001902

Vuln IDs

V-226558
V-22364

Rule IDs

SV-226558r505925_rule
SV-26488

The library preload list environment variable contains a list of libraries for the dynamic linker to load before loading the libraries required by the binary If this list contains paths to libraries to the current working directory that have not been authorized, unintended libraries may be preloaded. This variable is formatted as a space-separated list of libraries. Paths starting with a slash (/) are absolute paths.

Checks: C-28719r483083_chk

NOTE: The following must be done in the BASH shell Verify local initialization files have library preload list containing only authorized paths. # cut -d : -f 1 /etc/passwd | xargs -n1 -IUSER sh -c 'grep -l LD_PRELOAD ~USER/.*' This variable is formatted as a colon-separated list of paths. 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-28707r483084_fix

Edit the local initialization file and remove the relative path entries from the library preload variables that have not been documented with the ISSO. Edit the local initialization file(s) and remove any empty entry that is defined.

User start-up files must not execute world-writable programs.

CM-6 - Medium - CCI-000366 - V-226559 - SV-226559r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001940

Vuln IDs

V-226559
V-4087

Rule IDs

SV-226559r505925_rule
SV-39812

If start-up files execute world-writable programs, especially in unprotected directories, they could be maliciously modified to become Trojans destroying user files or otherwise compromising the system at the user, or higher, level. If the system is compromised at the user level, it is much easier to eventually compromise the system at the root and network level.

Checks: C-28720r483086_chk

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

Fix: F-28708r483087_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.

The .rhosts, .shosts, hosts.equiv, shosts.equiv, /etc/passwd, /etc/shadow, and/or /etc/group files must not contain a plus (+) without defining entries for NIS+ netgroups.

CM-6 - Medium - CCI-000366 - V-226560 - SV-226560r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN001980

Vuln IDs

V-226560
V-11987

Rule IDs

SV-226560r505925_rule
SV-12488

A plus (+) in system accounts' files causes the system to lookup the specified entry using NIS. If the system is not using NIS, no such entries should exist.

Checks: C-28721r483089_chk

Check system configuration files for plus (+) entries. Procedure: # find / -name .rhosts -exec grep + {} \; # find / -name .shosts -exec grep + {} \; # find / -name hosts.equiv -exec grep + {} \; # find / -name shosts.equiv -exec grep + {} \; # grep + /etc/passwd # grep + /etc/shadow # grep + /etc/group If the .rhosts, .shosts, hosts.equiv, shosts.equiv, /etc/passwd, /etc/shadow, and/or /etc/group files contain a plus (+) and do not define entries for NIS+ netgroups, this is a finding.

Fix: F-28709r483090_fix

Edit the .rhosts, .shosts, hosts.equiv, shosts.equiv, /etc/passwd, /etc/shadow, and/or /etc/group files and remove entries containing a plus (+).

There must be no .netrc files on the system.

IA-5 - Medium - CCI-000196 - V-226561 - SV-226561r505925_rule

RMF Control

IA-5

Severity

CCI

CCI-000196

Version

GEN002000

Vuln IDs

V-226561
V-913

Rule IDs

SV-226561r505925_rule
SV-913

Unencrypted passwords for remote FTP servers may be stored in .netrc files. Policy requires passwords be encrypted in storage and not used in access scripts.

Checks: C-28722r483092_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-28710r483093_fix

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

All .rhosts, .shosts, or host.equiv files must only contain trusted host-user pairs.

CM-6 - Medium - CCI-000366 - V-226562 - SV-226562r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002020

Vuln IDs

V-226562
V-4427

Rule IDs

SV-226562r505925_rule
SV-40331

If these files are not properly configured, they could allow malicious access by unknown malicious users from untrusted hosts who could compromise the system.

Checks: C-28723r483095_chk

Locate and examine all .rhosts, .shosts, hosts.equiv, and shosts.equiv files. The .rhosts and .shosts files are stored in home directories. (If a user does not have a home directory assigned in /etc/passwd, the root directory (/) is assigned as a default home directory.) Procedure: # for i in `cut -d: -f6 /etc/passwd | awk '$1 == "" {$1 = "/"} {print $1}'`; do more $i/.rhosts; more $i/.shosts; done # more /etc/hosts.equiv # more /etc/ssh/shosts.equiv If any .rhosts, .shosts, hosts.equiv, or shosts.equiv file contains other than host-user pairs, this is a finding.

Fix: F-28711r483096_fix

If possible, remove the .rhosts, .shosts, hosts.equiv, and shosts.equiv files. If the files are required, remove any content from the files except for necessary host-user pairs.

There must be no .rhosts, .shosts, hosts.equiv, or shosts.equiv files on the system.

CM-6 - High - CCI-000366 - V-226563 - SV-226563r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002040

Vuln IDs

V-226563
V-11988

Rule IDs

SV-226563r505925_rule
SV-40332

The .rhosts, .shosts, hosts.equiv, and shosts.equiv files are used to configure host-based authentication for individual users or the system. Host-based authentication is not sufficient for preventing unauthorized access to the system.

Checks: C-28724r483098_chk

Check for the existence of the files. The .rhosts and .shosts files are stored in home directories. (If a user does not have a home directory assigned in /etc/passwd, the root directory (/) is assigned as a default home directory.) Procedure (the first command is five lines long): # for homedir in `cut -d: -f6 /etc/passwd | awk '$1 == "" {$1 = "/"} {print $1}'`; do ls -l $homedir/.rhosts; ls -l $homedir/.shosts; done # ls -l /etc/hosts.equiv # ls -l /etc/ssh/shosts.equiv If .rhosts, .shosts, hosts.equiv, or shosts.equiv are found, this is a finding.

Fix: F-28712r483099_fix

Remove the .rhosts, .shosts, hosts.equiv, and/or shosts.equiv files.

All .rhosts, .shosts, .netrc, or hosts.equiv files must be accessible by only root or the owner.

CM-6 - Medium - CCI-000366 - V-226564 - SV-226564r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002060

Vuln IDs

V-226564
V-4428

Rule IDs

SV-226564r505925_rule
SV-40341

If these files are accessible by users other than root or the owner, they could be used by a malicious user to set up a system compromise.

Checks: C-28725r503855_chk

# for i in `cut -d: -f6 /etc/passwd | awk '$1 == "" {$1 = "/"} {print $1}'`; do ls -l $i/.rhosts $i/.shosts $i/.netrc; done # ls -l /etc/hosts.equiv # ls -l /etc/ssh/shosts.equiv If the .netrc, .rhosts, .shosts, hosts.equiv, or shosts.equiv files have permissions greater than 600, then this is a finding. (If a password entry has no home directory assigned, the root directory (/) is used as a default.)

Fix: F-28713r503856_fix

Ensure the permission for these files is set at 600 or less and the owner is the owner of the home directory that it is in. These files, outside of home directories (other than hosts.equiv in /etc and shosts.equiv in /etc/ssh; both are owned by root), have no meaning.

The .rhosts file must not be supported in PAM.

CM-6 - Medium - CCI-000366 - V-226565 - SV-226565r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002100

Vuln IDs

V-226565
V-11989

Rule IDs

SV-226565r505925_rule
SV-40334

The .rhosts files are used to specify a list of hosts that are permitted remote access to a particular account without authenticating. The use of such a mechanism defeats strong identification and authentication requirements.

Checks: C-28726r483104_chk

Check the PAM configuration for rhosts_auth. Procedure: # grep rhosts_auth /etc/pam.conf If a rhosts_auth entry is found that is not commented out, this is a finding.

Fix: F-28714r483105_fix

Edit /etc/pam.conf and remove the reference(s) to the rhosts_auth module.

The /etc/shells (or equivalent) file must exist.

CM-6 - Medium - CCI-000366 - V-226566 - SV-226566r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002120

Vuln IDs

V-226566
V-916

Rule IDs

SV-226566r505925_rule
SV-40806

The shells file (or equivalent) lists approved default shells. It helps provide layered defense to the security approach by ensuring users cannot change their default shell to an unauthorized shell that may not be secure.

Checks: C-28727r503858_chk

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

Fix: F-28715r503859_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

All shells referenced in /etc/passwd must be listed in the /etc/shells file, except any shells specified for the purpose of preventing logins.

CM-6 - Medium - CCI-000366 - V-226567 - SV-226567r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002140

Vuln IDs

V-226567
V-917

Rule IDs

SV-226567r505925_rule
SV-917

The shells file lists approved default shells. It helps provide layered defense to the security approach by ensuring users cannot change their default shell to an unauthorized shell that may not be secure.

Checks: C-28728r483110_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-28716r483111_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.

All shell files must be owned by root or bin.

CM-6 - Medium - CCI-000366 - V-226568 - SV-226568r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002200

Vuln IDs

V-226568
V-921

Rule IDs

SV-226568r505925_rule
SV-921

If shell files are owned by users other than root or bin, they could be modified by intruders or malicious users to perform unauthorized actions.

Checks: C-28729r483113_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-28717r483114_fix

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

All shell files must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226569 - SV-226569r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002210

Vuln IDs

V-226569
V-22365

Rule IDs

SV-226569r505925_rule
SV-39902

If shell files are group-owned by users other than root or a system group, they could be modified by intruders or malicious users to perform unauthorized actions.

Checks: C-28730r483116_chk

If /etc/shells exists, check the group ownership of each shell referenced. Procedure: # cat /etc/shells | xargs -n1 ls -lL Otherwise, check any shells found on the system. Procedure: # find / -name "*sh" | xargs -n1 ls -lL If a shell is not group-owned by root, bin, or sys, this is a finding.

Fix: F-28718r483117_fix

Change the group-owner of the shell to root, bin, or sys. Procedure: # chgrp root <shell>

All shell files must have mode 0755 or less permissive.

CM-6 - High - CCI-000366 - V-226570 - SV-226570r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002220

Vuln IDs

V-226570
V-922

Rule IDs

SV-226570r505925_rule
SV-922

Shells with world/group-write permissions give the ability to maliciously modify the shell to obtain unauthorized access.

Checks: C-28731r483119_chk

If /etc/shells exists, check the group ownership of each shell referenced. # cat /etc/shells | xargs -n1 ls -lL Otherwise, check any shells found on the system. # find / -name "*sh" | xargs -n1 ls -lL If a shell has a mode more permissive than 0755, this is a finding.

Fix: F-28719r483120_fix

Change the mode of the shell. # chmod 0755 <shell>

All shell files must not have extended ACLs.

CM-6 - Medium - CCI-000366 - V-226571 - SV-226571r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002230

Vuln IDs

V-226571
V-22366

Rule IDs

SV-226571r505925_rule
SV-26492

Shells with world/group write permissions give the ability to maliciously modify the shell to obtain unauthorized access.

Checks: C-28732r483122_chk

If /etc/shells exists, check the permissions of each shell referenced. # cat /etc/shells | xargs -n1 ls -lL Otherwise, check any shells found on the system. # find / -name "*sh" | xargs -n1 ls -lL If the permissions include a "+", the file has an extended ACL, this is a finding.

Fix: F-28720r483123_fix

Remove the extended ACL from the file. # chmod A- [shell]

The system must be checked for extraneous device files at least weekly.

CM-3 - Low - CCI-001744 - V-226572 - SV-226572r505925_rule

RMF Control

CM-3

Severity

CCI

Version

GEN002260

Vuln IDs

V-226572
V-923

Rule IDs

SV-226572r505925_rule
SV-923

If an unauthorized device is allowed to exist on the system, there is the possibility the system may perform unauthorized operations.

Checks: C-28733r503861_chk

Check the system for an automated job, or check with the SA, to determine if the system is checked for extraneous device files on a weekly basis. If no automated or manual process is in place, this is a finding.

Fix: F-28721r503862_fix

Establish a weekly automated or manual process to create a list of device files on the system and determine if any files have been added, moved, or deleted since the last list was generated. Generate a list of device files. # find / -type b -o -type c > device-file-list

Device files and directories must only be writable by users with a system account or as configured by the vendor.

CM-6 - Medium - CCI-000366 - V-226573 - SV-226573r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002280

Vuln IDs

V-226573
V-924

Rule IDs

SV-226573r505925_rule
SV-924

System device files in writable directories could be modified, removed, or used by an unprivileged user to control system hardware.

Checks: C-28734r483128_chk

Find all device files existing anywhere on the system. Procedure: # find / -type b -print > devicelist # find / -type c -print >> 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-28722r483129_fix

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

Device files used for backup must only be readable and/or writable by root or the backup user.

CM-6 - Medium - CCI-000366 - V-226574 - SV-226574r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002300

Vuln IDs

V-226574
V-925

Rule IDs

SV-226574r505925_rule
SV-925

System backups could be accidentally or maliciously overwritten and destroy the ability to recover the system if a compromise should occur. Unauthorized users could also copy system files.

Checks: C-28735r483131_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-28723r483132_fix

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

Audio devices must have mode 0660 or less permissive.

AC-3 - Medium - CCI-002165 - V-226575 - SV-226575r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN002320

Vuln IDs

V-226575
V-1048

Rule IDs

SV-226575r505925_rule
SV-27241

Globally accessible audio and video devices have proven to be security hazards. There is software that can activate system microphones and video devices connected to user workstations and/or X terminals. Once the microphone has been activated, it is possible to eavesdrop on otherwise private conversations without the victim being aware of it. This action effectively changes the user's microphone to a bugging device.

Checks: C-28736r483134_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-28724r483135_fix

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

Audio devices must not have extended ACLs.

CM-6 - Medium - CCI-000366 - V-226576 - SV-226576r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002330

Vuln IDs

V-226576
V-22367

Rule IDs

SV-226576r505925_rule
SV-26496

File system ACLs can provide access to files beyond what is allowed by the mode numbers of the files.

Checks: C-28737r483137_chk

Check the permissions of audio devices. # ls -lL /dev/audio If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-28725r483138_fix

Remove the extended ACL from the file. # chmod A- /dev/audio

Audio devices must be owned by root.

CM-6 - Medium - CCI-000366 - V-226577 - SV-226577r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002340

Vuln IDs

V-226577
V-1049

Rule IDs

SV-226577r505925_rule
SV-27246

Globally Accessible audio and video devices have proven to be security hazards. There is software that can activate system microphones and video devices connected to user workstations and/or X terminals. Once the microphone has been activated, it is possible to eavesdrop on otherwise private conversations without the victim being aware of it. This action effectively changes the user's microphone to a bugging device.

Checks: C-28738r483140_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-28726r483141_fix

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

Audio devices must be group-owned by root, sys, or bin.

CM-6 - Medium - CCI-000366 - V-226578 - SV-226578r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002360

Vuln IDs

V-226578
V-1061

Rule IDs

SV-226578r505925_rule
SV-27251

Without privileged group owners, audio devices will be vulnerable to being used as eaves-dropping devices by malicious users or intruders to possibly listen to conversations containing sensitive information.

Checks: C-28739r483143_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-28727r483144_fix

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

The owner, group owner, mode, ACL, and location of files with the setuid bit set must be documented using site-defined procedures.

CM-6 - Medium - CCI-000366 - V-226579 - SV-226579r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002380

Vuln IDs

V-226579
V-801

Rule IDs

SV-226579r505925_rule
SV-801

All files with the setuid bit set will allow anyone running these files to be temporarily assigned the UID of the file. While many system files depend on these attributes for proper operation, security problems can result if setuid is assigned to programs that allow reading and writing of files, or shell escapes. Only default vendor-supplied executables should have the setuid bit set.

Checks: C-28740r483146_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-28728r483147_fix

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

The system must be checked weekly for unauthorized setuid files, as well as, unauthorized modification to authorized setuid files.

CM-3 - Medium - CCI-001744 - V-226580 - SV-226580r505925_rule

RMF Control

CM-3

Severity

CCI

Version

GEN002400

Vuln IDs

V-226580
V-803

Rule IDs

SV-226580r505925_rule
SV-803

Files with the setuid bit set will allow anyone running these files to be temporarily assigned the UID of the file. While many system files depend on these attributes for proper operation, security problems can result if setuid is assigned to programs that allow reading and writing of files, or shell escapes.

Checks: C-28741r483149_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-28729r483150_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

The owner, group-owner, mode, ACL, and location of files with the setgid bit set must be documented using site-defined procedures.

CM-6 - Medium - CCI-000366 - V-226581 - SV-226581r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002440

Vuln IDs

V-226581
V-802

Rule IDs

SV-226581r505925_rule
SV-802

All files with the setgid bit set will allow anyone running these files to be temporarily assigned the GID of the file. While many system files depend on these attributes for proper operation, security problems can result if setgid is assigned to programs that allow reading and writing of files, or shell escapes.

Checks: C-28742r503864_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-28730r503865_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.

The system must be checked weekly for unauthorized setgid files, as well as, unauthorized modification to authorized setgid files.

CM-3 - Medium - CCI-001744 - V-226582 - SV-226582r505925_rule

RMF Control

CM-3

Severity

CCI

Version

GEN002460

Vuln IDs

V-226582
V-804

Rule IDs

SV-226582r505925_rule
SV-804

Files with the setgid bit set will allow anyone running these files to be temporarily assigned the group id of the file. While many system files depend on these attributes for proper operation, security problems can result if setgid is assigned to programs that allow reading and writing of files, or shell escapes.

Checks: C-28743r483158_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-28731r483159_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

Public directories must be the only world-writable directories and world-writable files must be located only in public directories.

CM-6 - Medium - CCI-000366 - V-226583 - SV-226583r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002480

Vuln IDs

V-226583
V-1010

Rule IDs

SV-226583r505925_rule
SV-1010

World-writable files and directories make it easy for a malicious user to place potentially compromising files on the system. The only authorized public directories are those temporary directories supplied with the system or those designed to be temporary file repositories. The setting is normally reserved for directories used by the system and by users for temporary file storage (e.g., /tmp) and for directories requiring global read/write access.

Checks: C-28744r483161_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-28732r483162_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.

The sticky bit must be set on all public directories.

CM-6 - Low - CCI-000366 - V-226584 - SV-226584r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002500

Vuln IDs

V-226584
V-806

Rule IDs

SV-226584r505925_rule
SV-806

Failing to set the sticky bit on the public directories allows unauthorized users to delete files in the directory structure. The only authorized public directories are those temporary directories supplied with the system or those designed to be temporary file repositories. The setting is normally reserved for directories used by the system and by users for temporary file storage (e.g., /tmp) and for directories requiring global read/write access.

Checks: C-28745r483164_chk

Verify all world-writable directories have the sticky bit set. Procedure: # find / -type d -perm -002 ! -perm -1000 > wwlist If the sticky bit is not set on a world-writable directory, this is a finding.

Fix: F-28733r483165_fix

Set the sticky bit on all public directories. Procedure: # chmod 1777 /tmp (Replace /tmp with the public directory missing the sticky bit, if necessary.)

All public directories must be owned by root or an application account.

AC-3 - Medium - CCI-002165 - V-226585 - SV-226585r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN002520

Vuln IDs

V-226585
V-807

Rule IDs

SV-226585r505925_rule
SV-807

If a public directory has the sticky bit set and is not owned by a privileged UID, unauthorized users may be able to modify files created by others. The only authorized public directories are those temporary directories supplied with the system or those designed to be temporary file repositories. The setting is normally reserved for directories used by the system and by users for temporary file storage (e.g., /tmp) and for directories requiring global read/write access.

Checks: C-28746r483167_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-28734r483168_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.)

All public directories must be group-owned by root or an application group.

CM-6 - Medium - CCI-000366 - V-226586 - SV-226586r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002540

Vuln IDs

V-226586
V-11990

Rule IDs

SV-226586r505925_rule
SV-12491

If a public directory has the sticky bit set and is not group-owned by a system GID, unauthorized users may be able to modify files created by others. The only authorized public directories are those temporary directories supplied with the system or those designed to be temporary file repositories. The setting is normally reserved for directories used by the system and by users for temporary file storage (e.g., /tmp) and for directories requiring global read/write access.

Checks: C-28747r483170_chk

Check the group ownership of public directories. Procedure: # find / -type d -perm -1002 -exec ls -ld {} \; If any public directory is not group-owned by root, sys, bin, or an application group (such as mail), this is a finding.

Fix: F-28735r483171_fix

Change the group ownership of the public directory. Procedure: # chgrp root /tmp (Replace root with a different system group and/or /tmp with a different public directory as necessary.)

The system and user default umask must be 077.

CM-6 - Medium - CCI-000366 - V-226587 - SV-226587r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002560

Vuln IDs

V-226587
V-808

Rule IDs

SV-226587r505925_rule
SV-28641

The umask controls the default access mode assigned to newly created files. An umask of 077 limits new files to mode 700 or less permissive. Although umask can be represented as a 4-digit number, the first digit representing special access modes is typically ignored or required to be 0. This requirement applies to the globally configured system defaults and the user defaults for each account on the system.

Checks: C-28748r483173_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-28736r483174_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".

Default system accounts must be disabled or removed.

CM-7 - Medium - CCI-000381 - V-226588 - SV-226588r505925_rule

RMF Control

CM-7

Severity

CCI

Version

GEN002640

Vuln IDs

V-226588
V-810

Rule IDs

SV-226588r505925_rule
SV-39834

Vendor accounts and software may contain backdoors allowing unauthorized access to the system. These backdoors are common knowledge and present a threat to system security if the account is not disabled.

Checks: C-28749r483176_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-28737r483177_fix

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

Auditing must be implemented.

AU-12 - Medium - CCI-000169 - V-226589 - SV-226589r505925_rule

RMF Control

AU-12

Severity

CCI

Version

GEN002660

Vuln IDs

V-226589
V-811

Rule IDs

SV-226589r505925_rule
SV-27266

Without auditing, individual system accesses cannot be tracked and malicious activity cannot be detected and traced back to an individual account.

Checks: C-28750r503867_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-28738r503868_fix

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

System audit logs must be owned by root.

AU-9 - Medium - CCI-000162 - V-226590 - SV-226590r505925_rule

RMF Control

AU-9

Severity

CCI

Version

GEN002680

Vuln IDs

V-226590
V-812

Rule IDs

SV-226590r505925_rule
SV-27271

Failure to give ownership of system audit log files to root provides the designated owner and unauthorized users with the potential to access sensitive information.

Checks: C-28751r483182_chk

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

Fix: F-28739r483183_fix

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

System audit logs must be group-owned by root, bin, or sys.

AU-9 - Medium - CCI-000162 - V-226591 - SV-226591r505925_rule

RMF Control

AU-9

Severity

CCI

Version

GEN002690

Vuln IDs

V-226591
V-22702

Rule IDs

SV-226591r505925_rule
SV-27277

Sensitive system and user information could provide a malicious user with enough information to penetrate further into the system.

Checks: C-28752r483185_chk

Determine the location of audit logs and then check the group-ownership. Procedure: # more /etc/security/audit_control # ls -lLd <audit log dir> If any audit log file is not group-owned by root, bin, or sys, this is a finding.

Fix: F-28740r483186_fix

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

System audit logs must have mode 0640 or less permissive.

AU-9 - Medium - CCI-000163 - V-226592 - SV-226592r505925_rule

RMF Control

AU-9

Severity

CCI

CCI-000163

Version

GEN002700

Vuln IDs

V-226592
V-813

Rule IDs

SV-226592r505925_rule
SV-27282

If a user can write to the audit logs, audit trails can be modified or destroyed and system intrusion may not be detected. System audit logs are those files generated from the audit system and do not include activity, error, or other log files created by application software.

Checks: C-28753r483188_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 <audit log dir> 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-28741r483189_fix

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

All system audit files must not have extended ACLs.

AU-9 - Medium - CCI-000163 - V-226593 - SV-226593r505925_rule

RMF Control

AU-9

Severity

CCI

CCI-000163

Version

GEN002710

Vuln IDs

V-226593
V-22369

Rule IDs

SV-226593r505925_rule
SV-26502

If a user can write to the audit logs, then audit trails can be modified or destroyed and system intrusion may not be detected.

Checks: C-28754r483191_chk

Check the audit configuration to determine the location of the system audit log files. # more /etc/security/audit_control Check the system audit log files for extended ACLs. # ls -la [audit log dir] If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-28742r483192_fix

Remove the extended ACL from the file. # chmod A- [audit file]

System audit tool executables must be owned by root.

AU-9 - Low - CCI-001493 - V-226594 - SV-226594r505925_rule

RMF Control

AU-9

Severity

CCI

Version

GEN002715

Vuln IDs

V-226594
V-22370

Rule IDs

SV-226594r505925_rule
SV-26505

To prevent unauthorized access or manipulation of system audit logs, the tools for manipulating those logs must be protected.

Checks: C-28755r483194_chk

Verify the audit tool executables are owned by root. # ls -l /usr/sbin/auditd /usr/sbin/audit /usr/sbin/bsmrecord /usr/sbin/auditreduce /usr/sbin/praudit /usr/sbin/auditconfig If any listed file is not owned by root, this is a finding.

Fix: F-28743r483195_fix

Change the owner of the audit tool executable to root. # chown root [audit tool executable]

System audit tool executables must be group-owned by root, bin, or sys.

AU-9 - Low - CCI-001493 - V-226595 - SV-226595r505925_rule

RMF Control

AU-9

Severity

CCI

Version

GEN002716

Vuln IDs

V-226595
V-22371

Rule IDs

SV-226595r505925_rule
SV-26508

To prevent unauthorized access or manipulation of system audit logs, the tools for manipulating those logs must be protected.

Checks: C-28756r483197_chk

Verify the audit tool executables are group-owned by root, bin, or sys. Procedure: # ls -lL /usr/sbin/auditd /usr/sbin/audit /usr/sbin/bsmrecord /usr/sbin/auditreduce /usr/sbin/praudit /usr/sbin/auditconfig If any listed file is not group-owned by root, bin, or sys, this is a finding.

Fix: F-28744r483198_fix

Change the group-owner of the audit tool executable to root, bin, or sys. Procedure: # chgrp root <audit tool executable>

System audit tool executables must have mode 0750 or less permissive.

AU-9 - Low - CCI-001493 - V-226596 - SV-226596r505925_rule

RMF Control

AU-9

Severity

CCI

Version

GEN002717

Vuln IDs

V-226596
V-22372

Rule IDs

SV-226596r505925_rule
SV-26511

To prevent unauthorized access or manipulation of system audit logs, the tools for manipulating those logs must be protected.

Checks: C-28757r483200_chk

Check the mode of audit tool executables. # ls -l /usr/sbin/auditd /usr/sbin/audit /usr/sbin/bsmrecord /usr/sbin/auditreduce /usr/sbin/praudit /usr/sbin/auditconfig If any listed file has a mode more permissive than 0750, this is a finding.

Fix: F-28745r483201_fix

Change the mode of the audit tool executable to 0750, or less permissive. # chmod 0750 [audit tool executable]

System audit tool executables must not have extended ACLs.

AU-9 - Low - CCI-001493 - V-226597 - SV-226597r505925_rule

RMF Control

AU-9

Severity

CCI

Version

GEN002718

Vuln IDs

V-226597
V-22373

Rule IDs

SV-226597r505925_rule
SV-26515

To prevent unauthorized access or manipulation of system audit logs, the tools for manipulating those logs must be protected.

Checks: C-28758r483203_chk

Check the permissions of audit tool executables. # ls -l /usr/sbin/auditd /usr/sbin/audit /usr/sbin/bsmrecord /usr/sbin/auditreduce /usr/sbin/praudit /usr/sbin/auditconfig If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-28746r483204_fix

Remove the extended ACL from the file. # chmod A- [audit file]

The audit system must alert the SA in the event of an audit processing failure.

AU-5 - Low - CCI-000139 - V-226598 - SV-226598r505925_rule

RMF Control

AU-5

Severity

CCI

CCI-000139

Version

GEN002719

Vuln IDs

V-226598
V-22374

Rule IDs

SV-226598r505925_rule
SV-40562

An accurate and current audit trail is essential for maintaining a record of system activity. If the system fails, the SA must be notified and must take prompt action to correct the problem. Minimally, the system must log this event and the SA will receive this notification during the daily system log review. If feasible, active alerting (such as email or paging) should be employed consistent with the site's established operations management systems and procedures.

Checks: C-28759r503870_chk

Verify the presence of an audit_warn entry in /etc/mail/aliases. # grep audit_warn /etc/mail/aliases If there is no audit_warn entry in /etc/mail/aliases, this is a finding.

Fix: F-28747r503871_fix

Add an audit_warn alias to /etc/mail/aliases that will forward to designated system administrator(s). # vi /etc/mail/aliases Put the updated aliases file into service. # newaliases

The audit system must be configured to audit failed attempts to access files and programs.

AU-12 - Medium - CCI-000172 - V-226599 - SV-226599r505925_rule

RMF Control

AU-12

Severity

CCI

Version

GEN002720

Vuln IDs

V-226599
V-814

Rule IDs

SV-226599r505925_rule
SV-27287

If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises and damages incurred during a system compromise.

Checks: C-28760r483209_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-28748r483210_fix

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

The audit system must alert the SA when the audit storage volume approaches its capacity.

AU-5 - Medium - CCI-001855 - V-226600 - SV-226600r505925_rule

RMF Control

AU-5

Severity

CCI

CCI-001855

Version

GEN002730

Vuln IDs

V-226600
V-22375

Rule IDs

SV-226600r505925_rule
SV-40564

Checks: C-28761r503873_chk

Verify the presence of an audit_warn entry in /etc/mail/aliases. # grep audit_warn /etc/mail/aliases If there is no audit_warn entry in /etc/mail/aliases, this is a finding. Verify the minfree parameter in /etc/security/audit_control. # egrep '^minfree:' /etc/security/audit_control If the minfree parameter is set to zero or not set at all, this is a finding.

Fix: F-28749r503874_fix

If necessary, add an audit_warn alias to /etc/mail/aliases that will forward to designated system administrator(s). # vi /etc/mail/aliases Put the updated aliases file into service. # newaliases If necessary, add or update the minfree: parameter in /etc/security/audit_control. # vi /etc/security/audit_control Ensure the minfree value is greater than zero and less than 100.

The audit system must be configured to audit file deletions.

AU-12 - Medium - CCI-000169 - V-226601 - SV-226601r505925_rule

RMF Control

AU-12

Severity

CCI

Version

GEN002740

Vuln IDs

V-226601
V-815

Rule IDs

SV-226601r505925_rule
SV-27292

Checks: C-28762r483215_chk

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

Fix: F-28750r483216_fix

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

The audit system must be configured to audit account creation.

AC-2 - Low - CCI-000018 - V-226602 - SV-226602r505925_rule

RMF Control

AC-2

Severity

CCI

CCI-000018

Version

GEN002750

Vuln IDs

V-226602
V-22376

Rule IDs

SV-226602r505925_rule
SV-40605

If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromises, and damages incurred during a system compromise.

Checks: C-28763r483218_chk

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

Fix: F-28751r483219_fix

Edit /etc/security/audit_control and add ua to the flags list and naflags list. Refresh auditd. # svcadm refresh auditd

The audit system must be configured to audit account modification.

AC-2 - Low - CCI-001403 - V-226603 - SV-226603r505925_rule

RMF Control

AC-2

Severity

CCI

CCI-001403

Version

GEN002751

Vuln IDs

V-226603
V-22377

Rule IDs

SV-226603r505925_rule
SV-40607

Checks: C-28764r483221_chk

Fix: F-28752r483222_fix

Edit /etc/security/audit_control and add ua to the flags list and naflags list. Refresh auditd. # svcadm refresh auditd

The audit system must be configured to audit account disabling.

AC-2 - Low - CCI-001404 - V-226604 - SV-226604r505925_rule

RMF Control

AC-2

Severity

CCI

CCI-001404

Version

GEN002752

Vuln IDs

V-226604
V-22378

Rule IDs

SV-226604r505925_rule
SV-40610

Checks: C-28765r483224_chk

Fix: F-28753r483225_fix

Edit /etc/security/audit_control and add ua to the flags list and naflags list. Refresh auditd. # svcadm refresh auditd

The audit system must be configured to audit account termination.

AC-2 - Low - CCI-001405 - V-226605 - SV-226605r505925_rule

RMF Control

AC-2

Severity

CCI

CCI-001405

Version

GEN002753

Vuln IDs

V-226605
V-22382

Rule IDs

SV-226605r505925_rule
SV-40611

Checks: C-28766r483227_chk

Fix: F-28754r483228_fix

Edit /etc/security/audit_control and add ua to the flags list and naflags list. Refresh auditd. # svcadm refresh auditd

The audit system must be configured to audit all administrative, privileged, and security actions.

AU-12 - Medium - CCI-000169 - V-226606 - SV-226606r505925_rule

RMF Control

AU-12

Severity

CCI

Version

GEN002760

Vuln IDs

V-226606
V-816

Rule IDs

SV-226606r505925_rule
SV-27298

Checks: C-28767r483230_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-28755r483231_fix

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

The audit system must be configured to audit login, logout, and session initiation.

AU-12 - Medium - CCI-000172 - V-226607 - SV-226607r505925_rule

RMF Control

AU-12

Severity

CCI

Version

GEN002800

Vuln IDs

V-226607
V-818

Rule IDs

SV-226607r505925_rule
SV-27303

Checks: C-28768r483233_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-28756r483234_fix

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

The audit system must be configured to audit all discretionary access control permission modifications.

AU-12 - Medium - CCI-000172 - V-226608 - SV-226608r505925_rule

RMF Control

AU-12

Severity

CCI

Version

GEN002820

Vuln IDs

V-226608
V-819

Rule IDs

SV-226608r505925_rule
SV-27309

Checks: C-28769r483236_chk

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

Fix: F-28757r483237_fix

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

The audit system must be configured to audit the loading and unloading of dynamic kernel modules.

AU-12 - Medium - CCI-000169 - V-226609 - SV-226609r505925_rule

RMF Control

AU-12

Severity

CCI

Version

GEN002825

Vuln IDs

V-226609
V-22383

Rule IDs

SV-226609r505925_rule
SV-26524

Actions concerning dynamic kernel modules must be recorded as they are substantial events. Dynamic kernel modules can increase the attack surface of a system. A malicious kernel module can be used to substantially alter the functioning of a system, often with the purpose of hiding a compromise from the SA.

Checks: C-28770r483239_chk

Check /etc/security/audit_control file. # grep flags /etc/security/audit_control If the as element is missing from the flags line, this is a finding.

Fix: F-28758r483240_fix

Edit /etc/security/audit_control and add the as flag to the flag parameter.

Audit logs must be rotated daily.

CM-6 - Medium - CCI-000366 - V-226610 - SV-226610r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002860

Vuln IDs

V-226610
V-4357

Rule IDs

SV-226610r505925_rule
SV-4357

Rotate audit logs daily to preserve audit file system space and to conform to the DoD/DISA requirement. If it is not rotated daily and moved to another location, then there is more of a chance for the compromise of audit data by malicious users.

Checks: C-28771r483242_chk

Check for any crontab entries that rotate audit logs. Procedure: # crontab -l If such a cron job is found, this is not a finding. Otherwise, query the SA. If there is a process automatically rotating audit logs, this is not a finding. If the SA manually rotates audit logs, this is still a finding, because if the SA is not there, it will not be accomplished. If the audit output is not archived daily, to tape or disk, this is a finding. This can be ascertained by looking at the audit log directory and, if more than one file is there, or if the file does not have today's date, this is a finding.

Fix: F-28759r483243_fix

Configure a cron job or other automated process to rotate the audit logs on a daily basis.

The system must be configured to send audit records to a remote audit server.

AU-9 - Low - CCI-001348 - V-226611 - SV-226611r509214_rule

RMF Control

AU-9

Severity

CCI

CCI-001348

Version

GEN002870

Vuln IDs

V-226611
V-24357

Rule IDs

SV-226611r509214_rule
SV-39881

Audit records contain evidence that can be used in the investigation of compromised systems. To prevent this evidence from compromise, it must be sent to a separate system continuously. Methods for sending audit records include, but are not limited to, system audit tools used to send logs directly to another host or through the system's syslog service to another host.

Checks: C-28772r509212_chk

Audit records may be sent to a remote server in two ways, via an NFS mount of the audit directory, or via the audit_syslog plugin (if available). NFS: Check the "dir" parameter in /etc/security/audit_control. If the directory is on an NFS mount to a remote server, there is no finding. SYSLOG: Check the "plugin" parameter in /etc/security/audit_control. Confirm that the audit_syslog.so* plugin is listed with "p_flags=all". # grep audit_syslog.so /etc/security/audit_control Check that syslogd is sending messages to a remote server (GEN005450): # grep '@' /etc/syslog.conf | grep -v '^#' If both auditd is configured to send audit records to syslog, and syslogd is configured to send messages to a remote server, there is no finding. If auditd is saving audit records on a local directory, and audit records are not being sent to a remote server via syslog, this is a finding.

Fix: F-28760r509213_fix

Update the /etc/security/audit_control file to save audit records to a remote NFS mount. dir:<remote NFS directory> OR If the /usr/lib/security/audit_syslog.so* exists, update the /etc/security/audit_control file to send all audit records to syslog and update /etc/syslog.conf to send all audit messages to a remote server. /etc/security/audit_control: plugin:name=audit_syslog.so.1; p_flags=all /etc/syslog.conf: audit.* @<remote syslog server>

Access to the cron utility must be controlled using the cron.allow and/or cron.deny file(s).

CM-6 - Medium - CCI-000366 - V-226612 - SV-226612r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002960

Vuln IDs

V-226612
V-974

Rule IDs

SV-226612r505925_rule
SV-27317

The cron facility allows users to execute recurring jobs on a regular and unattended basis. The cron.allow file designates accounts allowed to enter and execute jobs using the cron facility. If neither cron.allow nor cron.deny exists, then any account may use the cron facility. This may open the facility up for abuse by system intruders and malicious users.

Checks: C-28773r483248_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-28761r483249_fix

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

The cron.allow file must have mode 0600 or less permissive.

CM-6 - Medium - CCI-000366 - V-226613 - SV-226613r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002980

Vuln IDs

V-226613
V-975

Rule IDs

SV-226613r505925_rule
SV-27323

A cron.allow file that is readable and/or writable by other than root could allow potential intruders and malicious users to use the file contents to help discern information, such as who is allowed to execute cron programs, which could be harmful to overall system and network security.

Checks: C-28774r483251_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-28762r483252_fix

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

The cron.allow file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226614 - SV-226614r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN002990

Vuln IDs

V-226614
V-22384

Rule IDs

SV-226614r505925_rule
SV-26528

Checks: C-28775r483254_chk

Check the permissions of the cron.allow file. # ls -l /etc/cron.allow If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-28763r483255_fix

Remove the extended ACL from the file. # chmod A- /etc/cron.allow

Cron must not execute group-writable or world-writable programs.

CM-6 - Medium - CCI-000366 - V-226615 - SV-226615r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003000

Vuln IDs

V-226615
V-976

Rule IDs

SV-226615r505925_rule
SV-27329

If cron executes group-writable or world-writable programs, there is a possibility that unauthorized users could manipulate the programs with malicious intent. This could compromise system and network security.

Checks: C-28776r483257_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 <cron job file> Determine if the file is group-writable or world-writable. Procedure: # ls -la <cron program file> If cron executes group-writable or world-writable files, this is a finding.

Fix: F-28764r483258_fix

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

Cron must not execute programs in, or subordinate to, world-writable directories.

CM-6 - Medium - CCI-000366 - V-226616 - SV-226616r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003020

Vuln IDs

V-226616
V-977

Rule IDs

SV-226616r505925_rule
SV-27331

If cron programs are located in or subordinate to world-writable directories, they become vulnerable to removal and replacement by malicious users or system intruders.

Checks: C-28777r483260_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 <cron job file> Determine if the directory containing programs executed from cron is world-writable. Procedure: # ls -ld <cron program directory> If cron executes programs in world-writable directories, this is a finding.

Fix: F-28765r483261_fix

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

Crontabs must be owned by root or the crontab creator.

CM-6 - Medium - CCI-000366 - V-226617 - SV-226617r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003040

Vuln IDs

V-226617
V-11994

Rule IDs

SV-226617r505925_rule
SV-27333

To protect the integrity of scheduled system jobs and prevent malicious modification to these jobs, crontab files must be secured.

Checks: C-28778r483263_chk

List all crontabs on the system. # ls -lL /var/spool/cron/crontabs/ If any crontab is not owned by root or the creating user, this is a finding.

Fix: F-28766r483264_fix

Change the crontab owner to root or the crontab creator. # chown root <crontab file>

Crontab files must be group-owned by root, sys, or the crontab creator's primary group.

CM-6 - Medium - CCI-000366 - V-226618 - SV-226618r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003050

Vuln IDs

V-226618
V-22385

Rule IDs

SV-226618r505925_rule
SV-41044

To protect the integrity of scheduled system jobs and prevent malicious modification to these jobs, crontab files must be secured.

Checks: C-28779r483266_chk

Check the group ownership of the crontab files. # ls -lL /var/spool/cron/crontabs/ If the group owner is not root, sys, or the crontab owner's primary group, this is a finding.

Fix: F-28767r483267_fix

Change the group owner of the crontab file to root, sys, or the crontab's primary group. Procedure: # chgrp root [crontab file]

Default system accounts (with the exception of root) must not be listed in the cron.allow file or must be included in the cron.deny file, if cron.allow does not exist.

CM-6 - Medium - CCI-000366 - V-226619 - SV-226619r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003060

Vuln IDs

V-226619
V-11995

Rule IDs

SV-226619r505925_rule
SV-27335

To centralize the management of privileged account crontabs, of the default system accounts, only root may have a crontab.

Checks: C-28780r483269_chk

Check the cron.allow and cron.deny files for the system. # more /etc/cron.d/cron.allow # more /etc/cron.d/cron.deny If a default system account (such as bin, sys, adm, or others) is listed in the cron.allow file, or not listed in the cron.deny file if no cron.allow file exists, this is a finding.

Fix: F-28768r483270_fix

Remove default system accounts (such as bin, sys, adm, or others) from the cron.allow file if it exists, or add those accounts to the cron.deny file.

Crontab files must have mode 0600 or less permissive.

CM-6 - Medium - CCI-000366 - V-226620 - SV-226620r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003080

Vuln IDs

V-226620
V-978

Rule IDs

SV-226620r505925_rule
SV-27340

To protect the integrity of scheduled system jobs and prevent malicious modification to these jobs, crontab files must be secured.

Checks: C-28781r483272_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-28769r483273_fix

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

Crontab files must not have extended ACLs.

CM-6 - Medium - CCI-000366 - V-226621 - SV-226621r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003090

Vuln IDs

V-226621
V-22386

Rule IDs

SV-226621r505925_rule
SV-26534

To protect the integrity of scheduled system jobs and to prevent malicious modification to these jobs, crontab files must be secured. ACLs on crontab files may provide unauthorized access to the files.

Checks: C-28782r483275_chk

Check the permissions of the crontab files. # ls -lL /var/spool/cron/crontabs/ If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-28770r483276_fix

Remove the extended ACL from the file. # chmod A- [crontab file]

Cron and crontab directories must have mode 0755 or less permissive.

CM-6 - Medium - CCI-000366 - V-226622 - SV-226622r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003100

Vuln IDs

V-226622
V-979

Rule IDs

SV-226622r505925_rule
SV-27342

To protect the integrity of scheduled system jobs and to prevent malicious modification to these jobs, crontab files must be secured.

Checks: C-28783r483278_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-28771r483279_fix

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

Cron and crontab directories must not have extended ACLs.

CM-6 - Medium - CCI-000366 - V-226623 - SV-226623r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003110

Vuln IDs

V-226623
V-22387

Rule IDs

SV-226623r505925_rule
SV-26538

To protect the integrity of scheduled system jobs and to prevent malicious modification to these jobs, crontab files must be secured. ACLs on cron and crontab directories may provide unauthorized access to these directories. Unauthorized modifications to these directories or their contents may result in the addition of unauthorized cron jobs or deny service to authorized cron jobs.

Checks: C-28784r483281_chk

Check the permissions of the crontab directories. # ls -ld /var/spool/cron/crontabs/ If the permissions include a "+", the directory has an extended ACL and this is a finding.

Fix: F-28772r483282_fix

Remove the extended ACL from the directory. # chmod A- /var/spool/cron/crontabs/

Cron and crontab directories must be owned by root or bin.

CM-6 - Medium - CCI-000366 - V-226624 - SV-226624r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003120

Vuln IDs

V-226624
V-980

Rule IDs

SV-226624r505925_rule
SV-27345

Incorrect ownership of the cron or crontab directories could permit unauthorized users the ability to alter cron jobs and run automated jobs as privileged users. Failure to give ownership of cron or crontab directories to root or to bin provides the designated owner and unauthorized users with the potential to access sensitive information or change the system configuration which could weaken the system's security posture.

Checks: C-28785r483284_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-28773r483285_fix

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

Cron and crontab directories must be group-owned by root, sys, or bin.

CM-6 - Medium - CCI-000366 - V-226625 - SV-226625r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003140

Vuln IDs

V-226625
V-981

Rule IDs

SV-226625r505925_rule
SV-27347

To protect the integrity of scheduled system jobs and to prevent malicious modification to these jobs, crontab files must be secured. Failure to give group-ownership of cron or crontab directories to a system group provides the designated group and unauthorized users with the potential to access sensitive information or change the system configuration which could weaken the system's security posture.

Checks: C-28786r483287_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-28774r483288_fix

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

Cron logging must be implemented.

AU-12 - Medium - CCI-000172 - V-226626 - SV-226626r505925_rule

RMF Control

AU-12

Severity

CCI

Version

GEN003160

Vuln IDs

V-226626
V-982

Rule IDs

SV-226626r505925_rule
SV-27349

Cron logging can be used to trace the successful or unsuccessful execution of cron jobs. It can also be used to spot intrusions into the use of the cron facility by unauthorized and malicious users.

Checks: C-28787r483290_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-28775r483291_fix

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

The cronlog file must have mode 0600 or less permissive.

AU-9 - Medium - CCI-000162 - V-226627 - SV-226627r505925_rule

RMF Control

AU-9

Severity

CCI

Version

GEN003180

Vuln IDs

V-226627
V-983

Rule IDs

SV-226627r505925_rule
SV-27354

Cron logs contain reports of scheduled system activities and must be protected from unauthorized access or manipulation.

Checks: C-28788r483293_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-28776r483294_fix

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

The cron log files must not have extended ACLs.

CM-6 - Medium - CCI-000366 - V-226628 - SV-226628r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003190

Vuln IDs

V-226628
V-22388

Rule IDs

SV-226628r505925_rule
SV-26542

Cron logs contain reports of scheduled system activities and must be protected from unauthorized access or manipulation.

Checks: C-28789r483296_chk

Check the permissions of the file. # ls -lL /var/cron/log If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-28777r483297_fix

Remove the extended ACL from the file. # chmod A- /var/cron/log

The cron.deny file must have mode 0600 or less permissive.

AC-3 - Medium - CCI-002165 - V-226629 - SV-226629r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN003200

Vuln IDs

V-226629
V-4358

Rule IDs

SV-226629r505925_rule
SV-27359

If file permissions for cron.deny are more permissive than 0600, sensitive information could be viewed or edited by unauthorized users.

Checks: C-28790r483299_chk

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

Fix: F-28778r483300_fix

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

The cron.deny file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226630 - SV-226630r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003210

Vuln IDs

V-226630
V-22389

Rule IDs

SV-226630r505925_rule
SV-26546

If file permissions for cron.deny are more permissive than 0700, sensitive information could be viewed or edited by unauthorized users.

Checks: C-28791r483302_chk

Check the permissions of the file. # ls -lL /etc/cron.d/cron.deny If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-28779r483303_fix

Remove the extended ACL from the file. # chmod A- /etc/cron.d/cron.deny

Cron programs must not set the umask to a value less restrictive than 077.

AC-3 - Low - CCI-002165 - V-226631 - SV-226631r509217_rule

RMF Control

AC-3

Severity

CCI

Version

GEN003220

Vuln IDs

V-226631
V-4360

Rule IDs

SV-226631r509217_rule
SV-27364

The umask controls the default access mode assigned to newly created files. An umask of 077 limits new files to mode 700 or less permissive. Although umask is often represented as a 4-digit octal number, the first digit representing special access modes is typically ignored or required to be 0.

Checks: C-28792r509215_chk

Determine if there are any crontabs by viewing a long listing of the directory. If there are crontabs, examine them to determine what cron jobs exist. Check for any programs specifying an umask. # ls -lL /var/spool/cron/crontabs # cat <crontab file> # grep umask <cron program> If there are no cron jobs present, this vulnerability is not applicable. If any cron job contains an umask value more permissive than 077, this is a finding. Severity Override Guidance: If a cron program sets the umask to 000 or does not restrict the world-writable permission, this becomes a CAT I finding.

Fix: F-28780r509216_fix

Edit cron script files and modify the umask to 077.

The cron.allow file must be owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226632 - SV-226632r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003240

Vuln IDs

V-226632
V-4361

Rule IDs

SV-226632r505925_rule
SV-27366

If the owner of the cron.allow file is not set to root, bin, or sys, the possibility exists for an unauthorized user to view or to edit sensitive information.

Checks: C-28793r483308_chk

# ls -lL /etc/cron.d/cron.allow If the cron.allow file is not owned by root, sys, or bin, this is a finding.

Fix: F-28781r483309_fix

# chown root /etc/cron.d/cron.allow

The at.allow file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226633 - SV-226633r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003245

Vuln IDs

V-226633
V-22390

Rule IDs

SV-226633r505925_rule
SV-26550

File system extended ACLs provide access to files beyond what is allowed by the mode numbers of the files. Unauthorized modification of the at.allow file could result in Denial of Service to authorized at users and the granting of the ability to run at jobs to unauthorized users.

Checks: C-28794r483311_chk

Check the permissions of the file. # ls -lL /etc/cron.d/at.allow If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-28782r483312_fix

Remove the extended ACL from the file. # chmod A- /etc/cron.d/at.allow

The cron.allow file must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226634 - SV-226634r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003250

Vuln IDs

V-226634
V-22391

Rule IDs

SV-226634r505925_rule
SV-26553

If the group of the cron.allow is not set to root, bin, or sys, the possibility exists for an unauthorized user to view or edit the list of users permitted to use cron. Unauthorized modification of this file could cause Denial of Service to authorized cron users or provide unauthorized users with the ability to run cron jobs.

Checks: C-28795r483314_chk

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

Fix: F-28783r483315_fix

Change the group ownership of the file. Procedure: # chgrp root /etc/cron.d/cron.allow

The at.deny file must have mode 0600 or less permissive.

CM-6 - Medium - CCI-000366 - V-226635 - SV-226635r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003252

Vuln IDs

V-226635
V-22392

Rule IDs

SV-226635r505925_rule
SV-26556

The at daemon control files restrict access to scheduled job manipulation and must be protected. Unauthorized modification of the at.deny file could result in Denial of Service to authorized at users or provide unauthorized users with the ability to run at jobs.

Checks: C-28796r483317_chk

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

Fix: F-28784r483318_fix

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

The at.deny file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226857 - SV-226857r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003255

Vuln IDs

V-226857
V-22393

Rule IDs

SV-226857r505925_rule
SV-26560

The "at" daemon control files restrict access to scheduled job manipulation and must be protected. Unauthorized modification of the at.deny file could result in Denial of Service to authorized "at" users or provide unauthorized users with the ability to run "at" jobs.

Checks: C-29019r484855_chk

Check the permissions of the file. # ls -lL /etc/cron.d/at.deny If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-29007r484856_fix

Remove the extended ACL from the file. # chmod A- /etc/cron.d/at.deny

The cron.deny file must be owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226858 - SV-226858r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003260

Vuln IDs

V-226858
V-4430

Rule IDs

SV-226858r505925_rule
SV-27371

Cron daemon control files restrict the scheduling of automated tasks and must be protected.

Checks: C-29020r484858_chk

Check the ownership of the cron.deny file. # ls -lL /etc/cron.d/cron.deny If the cron.deny file is not owned by root, sys, or bin, this is a finding.

Fix: F-29008r484859_fix

Change the ownership of the cron.deny file to root, sys, or bin. # chown root /etc/cron.d/cron.deny

The cron.deny file must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226859 - SV-226859r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003270

Vuln IDs

V-226859
V-22394

Rule IDs

SV-226859r505925_rule
SV-26563

Cron daemon control files restrict the scheduling of automated tasks and must be protected. Unauthorized modification of the cron.deny file could result in Denial of Service to authorized cron users or could provide unauthorized users with the ability to run cron jobs.

Checks: C-29021r484861_chk

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

Fix: F-29009r484862_fix

Change the group ownership of the file to root, sys, or bin. Procedure: # chgrp root /etc/cron.d/cron.deny

Access to the at utility must be controlled via the at.allow and/or at.deny file(s).

AC-3 - Medium - CCI-002165 - V-226860 - SV-226860r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN003280

Vuln IDs

V-226860
V-984

Rule IDs

SV-226860r505925_rule
SV-27376

The at facility selectively allows users to execute jobs at deferred times. It is usually used for one-time jobs. The at.allow file selectively allows access to the at facility. If there is no at.allow file, there is no ready documentation of who is allowed to submit at jobs.

Checks: C-29022r484864_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-29010r484865_fix

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

The at.deny file must not be empty if it exists.

CM-6 - Medium - CCI-000366 - V-226861 - SV-226861r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003300

Vuln IDs

V-226861
V-985

Rule IDs

SV-226861r505925_rule
SV-27380

On some systems, if there is no at.allow file and there is an empty at.deny file, then the system assumes everyone has permission to use the at facility. This could create an insecure setting in the case of malicious users or system intruders.

Checks: C-29023r484867_chk

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

Fix: F-29011r484868_fix

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

Default system accounts (with the exception of root) must not be listed in the at.allow file or must be included in the at.deny file if the at.allow file does not exist.

CM-6 - Medium - CCI-000366 - V-226862 - SV-226862r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003320

Vuln IDs

V-226862
V-986

Rule IDs

SV-226862r505925_rule
SV-27384

Default accounts, such as bin, sys, adm, uucp, daemon, and others, should never have access to the at facility. This would create a possible vulnerability open to intruders or malicious users.

Checks: C-29024r484870_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-29012r484871_fix

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

The at.allow file must have mode 0600 or less permissive.

AC-3 - Medium - CCI-002165 - V-226863 - SV-226863r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN003340

Vuln IDs

V-226863
V-987

Rule IDs

SV-226863r505925_rule
SV-27388

Permissions more permissive than 0600 (read and write for the owner) may allow unauthorized or malicious access to the at.allow and/or at.deny files.

Checks: C-29025r484873_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-29013r484874_fix

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

The "at" daemon must not execute group-writable or world-writable programs.

CM-6 - Medium - CCI-000366 - V-226864 - SV-226864r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003360

Vuln IDs

V-226864
V-988

Rule IDs

SV-226864r505925_rule
SV-40411

If the "at" facility executes world-writable or group-writable programs, it is possible for the programs to be accidentally or maliciously changed or replaced without the owner's intent or knowledge. This would cause a system security breach.

Checks: C-29026r484876_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 <at job file> Check each program executed by "at" for group- or world-writable permissions. Procedure: # ls -la <at program file> If "at" executes group- or world-writable programs, this is a finding.

Fix: F-29014r484877_fix

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

The "at" daemon must not execute programs in, or subordinate to, world-writable directories.

CM-6 - Medium - CCI-000366 - V-226865 - SV-226865r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003380

Vuln IDs

V-226865
V-989

Rule IDs

SV-226865r505925_rule
SV-40412

If "at" programs are located in or subordinate to world-writable directories, they become vulnerable to removal and replacement by malicious users or system intruders.

Checks: C-29027r484879_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 <at job file> Check the directory containing each program executed by "at" for world-writable permissions. Procedure: # ls -la <at program file directory> If "at" executes programs in world-writable directories, this is a finding.

Fix: F-29015r484880_fix

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

The "at" directory must have mode 0755 or less permissive.

AC-3 - Medium - CCI-002165 - V-226866 - SV-226866r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN003400

Vuln IDs

V-226866
V-4364

Rule IDs

SV-226866r505925_rule
SV-40391

If the "at" directory has a mode more permissive than 0755, unauthorized users could be allowed to view or to edit files containing sensitive information within the "at" directory. Unauthorized modifications could result in Denial of Service to authorized "at" jobs.

Checks: C-29028r484882_chk

Check the mode of the "at" directory. Procedure: # ls -ld /var/spool/cron/atjobs If the directory mode is more permissive than 0755, this is a finding.

Fix: F-29016r484883_fix

Change the mode of the "at" directory to 0755. Procedure: # chmod 0755 < at directory >

The "at" directory must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226867 - SV-226867r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003410

Vuln IDs

V-226867
V-22395

Rule IDs

SV-226867r505925_rule
SV-26566

If the "at" directory has an extended ACL, unauthorized users could be allowed to view or to edit files containing sensitive information within the "at" directory. Unauthorized modifications could result in Denial of Service to authorized "at" jobs.

Checks: C-29029r484885_chk

Check the permissions of the directory. # ls -lLd /var/spool/cron/atjobs If the permissions include a "+", the directory has an extended ACL and this is a finding.

Fix: F-29017r484886_fix

Remove the extended ACL from the file. # chmod A- /var/spool/cron/atjobs

The "at" directory must be owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226868 - SV-226868r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003420

Vuln IDs

V-226868
V-4365

Rule IDs

SV-226868r505925_rule
SV-39886

If the owner of the "at" directory is not root, bin, or sys, unauthorized users could be allowed to view or edit files containing sensitive information within the directory.

Checks: C-29030r484888_chk

Check the ownership of the "at" directory. Procedure: # ls -ld /var/spool/cron/atjobs If the directory is not owned by root, sys, or bin, this is a finding.

Fix: F-29018r484889_fix

Change the owner of the "at" directory to root, bin, or sys. Procedure: # chown root /var/spool/cron/atjobs

The "at" directory must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226869 - SV-226869r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003430

Vuln IDs

V-226869
V-22396

Rule IDs

SV-226869r505925_rule
SV-40414

If the "at" directory's group owner is not root, bin, or sys, unauthorized users could be allowed to view or edit files containing sensitive information within the directory.

Checks: C-29031r484891_chk

Check the group ownership of the "at" directory. Procedure: # ls -lLd /var/spool/cron/atjobs If the "at" directory is not group-owned by root, bin, or sys, this is a finding.

Fix: F-29019r484892_fix

Change the group ownership of the "at" directory to root, bin, or sys. Procedure: # chgrp sys /var/spool/cron/atjobs

"At" jobs must not set the umask to a value less restrictive than 077.

AC-3 - Medium - CCI-002165 - V-226870 - SV-226870r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN003440

Vuln IDs

V-226870
V-4366

Rule IDs

SV-226870r505925_rule
SV-40416

The umask controls the default access mode assigned to newly created files. An umask of 077 limits new files to mode 700 or less permissive. Although umask is often represented as a 4-digit number, the first digit representing special access modes is typically ignored or required to be 0.

Checks: C-29032r484894_chk

Determine what "at" jobs exist on the system. Procedure: # ls /var/spool/cron/atjobs If there are no "at" jobs present, this is not applicable. Determine if any of the "at" jobs or any scripts referenced execute the umask command. Check for any umask setting more permissive than 077. # grep umask <at job or referenced script> If any "at" job or referenced script sets umask to a value more permissive than 077, this is a finding.

Fix: F-29020r484895_fix

Edit "at" jobs or referenced scripts to remove umask commands setting umask to a value less restrictive than 077.

The at.allow file must be owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226871 - SV-226871r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003460

Vuln IDs

V-226871
V-4367

Rule IDs

SV-226871r505925_rule
SV-27392

If the owner of the at.allow file is not set to root, bin, or sys, unauthorized users could be allowed to view or edit sensitive information contained within the file.

Checks: C-29033r484897_chk

# ls -lL /etc/cron.d/at.allow If the at.allow file is not owned by root, sys, or bin, this is a finding.

Fix: F-29021r484898_fix

Change the owner of the at.allow file. # chown root /etc/cron.d/at.allow

The at.allow file must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226872 - SV-226872r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003470

Vuln IDs

V-226872
V-22397

Rule IDs

SV-226872r505925_rule
SV-26570

If the group owner of the at.allow file is not set to root, bin, or sys, unauthorized users could be allowed to view or edit the list of users permitted to run at jobs. Unauthorized modification could result in Denial of Service to authorized at users or provide unauthorized users with the ability to run at jobs.

Checks: C-29034r484900_chk

Check the group ownership of the file. Procedure: # ls -lL /etc/cron.d/at.allow If the file is not group-owned by root, bin, or sys, this is a finding.

Fix: F-29022r484901_fix

Change the group ownership of the file. Procedure: # chgrp root /etc/cron.d/at.allow

The at.deny file must be owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226873 - SV-226873r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003480

Vuln IDs

V-226873
V-4368

Rule IDs

SV-226873r505925_rule
SV-27396

If the owner of the at.deny file is not set to root, bin, or sys, unauthorized users could be allowed to view or edit sensitive information contained within the file.

Checks: C-29035r484903_chk

# ls -lL /etc/cron.d/at.deny If the at.deny file is not owned by root, sys, or bin, this is a finding.

Fix: F-29023r484904_fix

Change the owner of the at.deny file. # chown root /etc/cron.d/at.deny

The at.deny file must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226874 - SV-226874r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003490

Vuln IDs

V-226874
V-22398

Rule IDs

SV-226874r505925_rule
SV-26573

If the group owner of the at.deny file is not set to root, bin, or sys, unauthorized users could be allowed to view or edit sensitive information contained within the file. Unauthorized modification could result in Denial of Service to authorized "at" users or provide unauthorized users with the ability to run "at" jobs.

Checks: C-29036r484906_chk

Check the group ownership of the file. Procedure: # ls -lL /etc/cron.d/at.deny If the file is not group-owned by root, bin, or sys, this is a finding.

Fix: F-29024r484907_fix

Change the group ownership of the at.deny file to root, bin, or sys. Procedure: # chgrp root /etc/cron.d/at.deny

Process core dumps must be disabled unless needed.

CM-6 - Low - CCI-000366 - V-226875 - SV-226875r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003500

Vuln IDs

V-226875
V-11996

Rule IDs

SV-226875r505925_rule
SV-27400

Process core dumps contain the memory in use by the process when it crashed. Process core dump files can be of significant size and their use can result in file systems filling to capacity, which may result in Denial of Service. Process core dumps can be useful for software debugging.

Checks: C-29037r484909_chk

Check the process core dump configuration. # coreadm |grep enabled OR # egrep "COREADM_.*_ENABLED" /etc/coreadm.conf. If any lines are returned by coreadm or if any lines are not set to no in /etc/coreadm.conf, this is a finding. # grep coredumpsize /etc/system If the value is 1, this is a finding.

Fix: F-29025r484910_fix

Change the process core dump configuration. # coreadm -d global # coreadm -d process # coreadm -d global-setid # coreadm -d proc-setid # coreadm -d log Edit /etc/system and remove the coredumpsize parameter.

The system must be configured to store any process core dumps in a specific, centralized directory.

CM-6 - Low - CCI-000366 - V-226876 - SV-226876r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003501

Vuln IDs

V-226876
V-22399

Rule IDs

SV-226876r505925_rule
SV-26576

Specifying a centralized location for core file creation allows for the centralized protection of core files. Process core dumps contain the memory in use by the process when it crashed. Any data the process was handling may be contained in the core file, and it must be protected accordingly. If process core dump creation is not configured to use a centralized directory, core dumps may be created in a directory that does not have appropriate ownership or permissions configured, which could result in unauthorized access to the core dumps.

Checks: C-29038r484912_chk

Verify a directory is defined for process core dumps. # grep COREADM_GLOB_PATTERN /etc/coreadm.conf If the parameter is not an absolute path (does not start with a slash [/]), this is a finding.

Fix: F-29026r484913_fix

Change the core file pattern. # coreadm -g /var/core/core.%f.%p Then: # coreadm -u In order to force a reload of the configuration.

The centralized process core dump data directory must be owned by root.

CM-6 - Low - CCI-000366 - V-226877 - SV-226877r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003502

Vuln IDs

V-226877
V-22400

Rule IDs

SV-226877r505925_rule
SV-26579

Process core dumps contain the memory in use by the process when it crashed. Any data the process was handling may be contained in the core file, and it must be protected accordingly. If the centralized process core dump data directory is not owned by root, the core dumps contained in the directory may be subject to unauthorized access.

Checks: C-29039r484915_chk

Check the defined directory for process core dumps. # coreadm | grep "global core file pattern" OR # grep COREADM_GLOB_PATTERN /etc/coreadm.conf Check the ownership of the directory. # ls -lLd [core file directory] If the directory is not owned by root, this is a finding.

Fix: F-29027r484916_fix

Change the owner of the core file directory. # chown root [core file directory]

The centralized process core dump data directory must be group-owned by root, bin, or sys.

CM-6 - Low - CCI-000366 - V-226878 - SV-226878r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003503

Vuln IDs

V-226878
V-22401

Rule IDs

SV-226878r505925_rule
SV-26582

Process core dumps contain the memory in use by the process when it crashed. Any data the process was handling may be contained in the core file, and it must be protected accordingly. If the centralized process core dump data directory is not group-owned by a system group, the core dumps contained in the directory may be subject to unauthorized access.

Checks: C-29040r499357_chk

Check the defined directory for process core dumps. # coreadm | grep "global core file pattern" OR # grep COREADM_GLOB_PATTERN /etc/coreadm.conf Check the group ownership of the directory. # ls -lLd [core file directory] If the directory is not group-owned by root, bin, or sys, this is a finding.

Fix: F-29028r499358_fix

Change the group-owner of the core file directory to root, bin, or sys. Example: # chgrp root [core file directory]

The centralized process core dump data directory must have mode 0700 or less permissive.

CM-6 - Low - CCI-000366 - V-226879 - SV-226879r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003504

Vuln IDs

V-226879
V-22402

Rule IDs

SV-226879r505925_rule
SV-26596

Process core dumps contain the memory in use by the process when it crashed. Any data the process was handling may be contained in the core file, and it must be protected accordingly. If the process core dump data directory has a mode more permissive than 0700, unauthorized users may be able to view or to modify sensitive information contained any process core dumps in the directory.

Checks: C-29041r484921_chk

Check the defined directory for process core dumps. # coreadm | grep "global core file pattern" OR # grep COREADM_GLOB_PATTERN /etc/coreadm.conf Check the permissions of the directory. # ls -lLd [core file directory] If the directory has a mode more permissive than 0700, this is a finding.

Fix: F-29029r484922_fix

Change the mode of the core file directory. # chmod 0700 [core file directory]

The centralized process core dump data directory must not have an extended ACL.

CM-6 - Low - CCI-000366 - V-226880 - SV-226880r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003505

Vuln IDs

V-226880
V-22403

Rule IDs

SV-226880r505925_rule
SV-26602

Process core dumps contain the memory in use by the process when it crashed. Any data the process was handling may be contained in the core file, and it must be protected accordingly. If the process core dump data directory has an extended ACL, unauthorized users may be able to view or to modify sensitive information contained any process core dumps in the directory.

Checks: C-29042r484924_chk

Check the defined directory for process core dumps. # coreadm | grep "global core file pattern" OR # grep COREADM_GLOB_PATTERN /etc/coreadm.conf Check the permissions of the directory. # ls -lLd [core file directory] If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-29030r484925_fix

Remove the extended ACL from the directory. # chmod A- [core file directory]

Kernel core dumps must be disabled unless needed.

CM-6 - Medium - CCI-000366 - V-226881 - SV-226881r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003510

Vuln IDs

V-226881
V-22404

Rule IDs

SV-226881r505925_rule
SV-26605

Kernel core dumps may contain the full contents of system memory at the time of the crash. Kernel core dumps may consume a considerable amount of disk space and may result in Denial of Service by exhausting the available space on the target file system. The kernel core dump process may increase the amount of time a system is unavailable due to a crash. Kernel core dumps can be useful for kernel debugging.

Checks: C-29043r484927_chk

Verify savecore is not used. # dumpadm | grep 'Savecore enabled' If the value is true, this is a finding. OR # grep DUMPADM_ENABLE /etc/dumpadm.conf If the value is yes, this is a finding.

Fix: F-29031r484928_fix

Disable savecore. # dumpadm -n

The kernel core dump data directory must be owned by root.

CM-6 - Low - CCI-000366 - V-226882 - SV-226882r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003520

Vuln IDs

V-226882
V-11997

Rule IDs

SV-226882r505925_rule
SV-27407

Kernel core dumps may contain the full contents of system memory at the time of the crash. As the system memory may contain sensitive information, it must be protected accordingly. If the kernel core dump data directory is not owned by root, the core dumps contained in the directory may be subject to unauthorized access.

Checks: C-29044r484930_chk

Check the ownership of the kernel core dump data directory. # ls -ld /var/crash OR # ls -ld `grep DUMPADM_SAVDIR /etc/dumpadm.conf | cut -d= -f2` If the kernel core dump data directory is not owned by root, this is a finding.

Fix: F-29032r484931_fix

Change the owner of the kernel core dump data directory to root. # chown root /var/crash

The kernel core dump data directory must be group-owned by root.

CM-6 - Low - CCI-000366 - V-226883 - SV-226883r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003521

Vuln IDs

V-226883
V-22405

Rule IDs

SV-226883r505925_rule
SV-26610

Kernel core dumps may contain the full contents of system memory at the time of the crash. As the system memory may contain sensitive information, it must be protected accordingly. If the kernel core dump data directory is not group-owned by a system group, the core dumps contained in the directory may be subject to unauthorized access.

Checks: C-29045r484933_chk

Determine the kernel core dump data directory. # dumpadm | grep "Savecore directory" OR # grep DUMPADM_SAVDIR /etc/dumpadm.conf Check ownership of the core dump data directory. # ls -l [savecore directory] If the directory is not group-owned by root, this is a finding.

Fix: F-29033r484934_fix

Change the group-owner of the kernel core dump data directory. # chgrp root [kernel core dump data directory]

The kernel core dump data directory must have mode 0700 or less permissive.

CM-6 - Low - CCI-000366 - V-226884 - SV-226884r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003522

Vuln IDs

V-226884
V-22406

Rule IDs

SV-226884r505925_rule
SV-26614

Kernel core dumps may contain the full contents of system memory at the time of the crash. As the system memory may contain sensitive information, it must be protected accordingly. If the mode of the kernel core dump data directory is more permissive than 0700, unauthorized users may be able to view or to modify kernel core dump data files.

Checks: C-29046r484936_chk

Determine the kernel core dump data directory. # dumpadm | grep "Savecore directory" OR # grep DUMPADM_SAVDIR /etc/dumpadm.conf Check the permissions of the kernel core dump data directory. # ls -l [savecore directory] If the directory has a mode more permissive than 0700, this is a finding.

Fix: F-29034r484937_fix

Change the group-owner of the kernel core dump data directory. # chmod 0700 [kernel core dump data directory]

The kernel core dump data directory must not have an extended ACL.

CM-6 - Low - CCI-000366 - V-226885 - SV-226885r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003523

Vuln IDs

V-226885
V-22407

Rule IDs

SV-226885r505925_rule
SV-26618

Kernel core dumps may contain the full contents of system memory at the time of the crash. As the system memory may contain sensitive information, it must be protected accordingly. If there is an extended ACL for the kernel core dump data directory, unauthorized users may be able to view or to modify kernel core dump data files.

Checks: C-29047r484939_chk

Determine the kernel core dump data directory. # dumpadm | grep "Savecore directory" OR # grep DUMPADM_SAVDIR /etc/dumpadm.conf Check the kernel core dump data directory permissions. # ls -ld [savecore directory] If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-29035r484940_fix

Remove the extended ACL from the file. # chmod A- [kernel core dump directory]

The system must implement non-executable program stacks.

CM-6 - Medium - CCI-000366 - V-226886 - SV-226886r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003540

Vuln IDs

V-226886
V-11999

Rule IDs

SV-226886r505925_rule
SV-27412

A common type of exploit is the stack buffer overflow. An application receives, from an attacker, more data than it is prepared for and stores this information on its stack, writing beyond the space reserved for it. This can be designed to cause execution of the data written on the stack. One mechanism to mitigate this vulnerability is for the system to not allow the execution of instructions in sections of memory identified as part of the stack.

Checks: C-29048r503876_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. Determine if the system implements non-executable program stacks. # grep noexec_user_stack /etc/system If the noexec_user_stack is not set to 1, this is a finding.

Fix: F-29036r503877_fix

This action applies to the global zone only. Determine the type of zone that you are currently securing. # zonename If the command output is "global", this action applies. Edit /etc/system and set the noexec_user_stack parameter to 1. Restart the system for the setting to take effect.

The system must use initial TCP sequence numbers most resistant to sequence number guessing attacks.

CM-6 - Medium - CCI-000366 - V-226887 - SV-226887r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003580

Vuln IDs

V-226887
V-12001

Rule IDs

SV-226887r505925_rule
SV-27416

One use of initial TCP sequence numbers is to verify bidirectional communication between two hosts, which provides some protection against spoofed source addresses being used by the connection originator. If the initial TCP sequence numbers for a host can be determined by an attacker, it may be possible to establish a TCP connection from a spoofed source address without bidirectional communication.

Checks: C-29049r484945_chk

# grep "TCP_STRONG_ISS=2" /etc/default/inetinit If this variable is not set, this is a finding.

Fix: F-29037r484946_fix

Edit /etc/default/inetinit and set the TCP_STRONG_ISS parameter to 2.

The system must not forward IPv4 source-routed packets.

CM-6 - Medium - CCI-000366 - V-226888 - SV-226888r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003600

Vuln IDs

V-226888
V-12002

Rule IDs

SV-226888r505925_rule
SV-27420

Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when IPv4 forwarding is enabled and the system is functioning as a router.

Checks: C-29050r484948_chk

Determine the type of zone that you are currently securing. # zonename If the zone is not the global zone, determine if any interfaces are exclusive to the zone: # dladm show-link If the output indicates "insufficient privileges" then this requirement is not applicable. If the zone is the global zone or the non-global zone has exclusive interfaces verify the network settings: # ndd /dev/ip ip_forward_src_routed If the returned value is not 0, this is a finding.

Fix: F-29038r484949_fix

Configure the system to not forward IPv4 source-routed packets. Procedure: # ndd /dev/ip ip_forward_src_routed 0 This command must also be added to a system startup script.

TCP backlog queue sizes must be set appropriately.

CM-6 - Medium - CCI-000366 - V-226889 - SV-226889r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003601

Vuln IDs

V-226889
V-23741

Rule IDs

SV-226889r505925_rule
SV-28639

To provide some mitigation to TCP DoS attacks, the TCP backlog queue sizes must be set to at least 1280 or in accordance with product-specific guidelines.

Checks: C-29051r484951_chk

Determine the type of zone that you are currently securing. # zonename If the zone is not the global zone, determine if any interfaces are exclusive to the zone: # dladm show-link If the output indicates "insufficient privileges" then this requirement is not applicable. If the zone is the global zone or the non-global zone has exclusive interfaces determine the network settings. Procedure: # ndd /dev/tcp tcp_conn_req_max_q0 If the returned value is not 1280 or greater, this is a finding. Procedure: # ndd /dev/tcp tcp_conn_req_max_q If the returned value is not 1024, this is a finding.

Fix: F-29039r484952_fix

Procedure: # ndd -set /dev/tcp tcp_conn_req_max_q0 1280 # ndd -set /dev/tcp tcp_conn_req_max_q 1024 Ensure these commands are also present in system startup scripts.

The system must not process ICMP timestamp requests.

CM-6 - Low - CCI-000366 - V-226890 - SV-226890r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003602

Vuln IDs

V-226890
V-22409

Rule IDs

SV-226890r505925_rule
SV-26621

The processing of Internet Control Message Protocol (ICMP) timestamp requests increases the attack surface of the system.

Checks: C-29052r484954_chk

Determine the type of zone that you are currently securing. # zonename If the zone is not the global zone, determine if any interfaces are exclusive to the zone: # dladm show-link If the output indicates "insufficient privileges" then this requirement is not applicable. If the zone is the global zone or the non-global zone has exclusive interfaces verify the system does not respond to ICMP timestamp requests. # ndd /dev/ip ip_respond_to_timestamp If the result is not 0, this is a finding.

Fix: F-29040r484955_fix

Disable ICMP timestamp responses on the system. # ndd -set /dev/ip ip_respond_to_timestamp 0 Also add this command to a system startup script.

The system must not respond to ICMPv4 echoes sent to a broadcast address.

CM-6 - Medium - CCI-000366 - V-226891 - SV-226891r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003603

Vuln IDs

V-226891
V-22410

Rule IDs

SV-226891r505925_rule
SV-26622

Responding to broadcast Internet Control Message Protocol (ICMP) echoes facilitates network mapping and provides a vector for amplification attacks.

Checks: C-29053r484957_chk

Determine the type of zone that you are currently securing. # zonename If the zone is not the global zone, determine if any interfaces are exclusive to the zone: # dladm show-link If the output indicates "insufficient privileges" then this requirement is not applicable. If the zone is the global zone or the non-global zone has exclusive interfaces verify the system does not respond to ICMP ECHO_REQUESTs set to broadcast addresses. # ndd /dev/ip ip_respond_to_echo_broadcast If the result is not 0, this is a finding.

Fix: F-29041r484958_fix

Configure the system to not respond to ICMP ECHO_REQUESTs sent to broadcast addresses. # ndd -set /dev/ip ip_respond_to_echo_broadcast 0 Also add this command to a system startup script.

The system must not respond to ICMP timestamp requests sent to a broadcast address.

CM-6 - Medium - CCI-000366 - V-226892 - SV-226892r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003604

Vuln IDs

V-226892
V-22411

Rule IDs

SV-226892r505925_rule
SV-26624

The processing of Internet Control Message Protocol (ICMP) timestamp requests increases the attack surface of the system. Responding to broadcast ICMP timestamp requests facilitates network mapping and provides a vector for amplification attacks.

Checks: C-29054r484960_chk

Determine the type of zone that you are currently securing. # zonename If the zone is not the global zone, determine if any interfaces are exclusive to the zone: # dladm show-link If the output indicates "insufficient privileges" then this requirement is not applicable. If the zone is the global zone or the non-global zone has exclusive interfaces verify the system does not respond to ICMP timestamp requests set to broadcast addresses. # ndd /dev/ip ip_respond_to_echo_broadcast If the result is not 0, this is a finding.

Fix: F-29042r484961_fix

Configure the system to not respond to ICMP timestamp requests sent to broadcast addresses. # ndd -set /dev/ip ip_respond_to_echo_broadcast 0 Also add this command to a system startup script.

The system must not apply reversed source routing to TCP responses.

CM-6 - Medium - CCI-000366 - V-226893 - SV-226893r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003605

Vuln IDs

V-226893
V-22412

Rule IDs

SV-226893r505925_rule
SV-26626

Checks: C-29055r484963_chk

Determine the type of zone that you are currently securing. # zonename If the zone is not the global zone, determine if any interfaces are exclusive to the zone: # dladm show-link If the output indicates "insufficient privileges" then this requirement is not applicable. If the zone is the global zone or the non-global zone has exclusive interfaces verify the system does not apply reversed source routing to TCP responses. # ndd /dev/tcp tcp_rev_src_routes If the result is not 0, this is a finding.

Fix: F-29043r484964_fix

Configure the system to not apply reversed source routing to TCP responses. # ndd -set /dev/tcp tcp_rev_src_routes 0 Also add this command to a system startup script.

The system must prevent local applications from generating source-routed packets.

CM-6 - Medium - CCI-000366 - V-226894 - SV-226894r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003606

Vuln IDs

V-226894
V-22413

Rule IDs

SV-226894r505925_rule
SV-29709

Checks: C-29056r484966_chk

Check the system for an IPF rule blocking outgoing source-routed packets. Procedure: # ipfstat -o Examine the list for rules such as: block out log quick all with opt lsrr block out log quick all with opt ssrr If the listed rules do not block both lsrr and ssrr options, this is a finding.

Fix: F-29044r484967_fix

Edit /etc/ipf/ipf.conf and add rules to block outgoing source-routed packets, such as: block out log quick all with opt lsrr block out log quick all with opt ssrr Reload the IPF rules. Procedure: # ipf -Fa -A -f /etc/ipf/ipf.conf

The system must not accept source-routed IPv4 packets.

CM-6 - Medium - CCI-000366 - V-226895 - SV-226895r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003607

Vuln IDs

V-226895
V-22414

Rule IDs

SV-226895r505925_rule
SV-29711

Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the handling of source-routed traffic destined to the system itself, not to traffic forwarded by the system to another, such as when IPv4 forwarding is enabled and the system is functioning as a router.

Checks: C-29057r484969_chk

Determine the type of zone that you are currently securing. # zonename If the zone is not the global zone, determine if any interfaces are exclusive to the zone: # dladm show-link If the output indicates "insufficient privileges" then this requirement is not applicable. If the zone is the global zone or the non-global zone has exclusive interfaces check the system for an IPF rule blocking incoming source-routed packets. Procedure: # ipfstat -i Examine the list for rules such as: block in log quick all with opt lsrr block in log quick all with opt ssrr If the listed rules do not block incoming traffic with both lsrr and ssrr options, this is a finding.

Fix: F-29045r484970_fix

Edit /etc/ipf/ipf.conf and add rules to block incoming source-routed packets, such as: block in log quick all with opt lsrr block in log quick all with opt ssrr Reload the IPF rules. Procedure: # ipf -Fa -A -f /etc/ipf/ipf.conf

Proxy ARP must not be enabled on the system.

CM-6 - Medium - CCI-000366 - V-226896 - SV-226896r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003608

Vuln IDs

V-226896
V-22415

Rule IDs

SV-226896r505925_rule
SV-29603

Proxy ARP allows a system to respond to ARP requests on one interface on behalf of hosts connected to another interface. If this function is enabled when not required, addressing information may be leaked between the attached network segments.

Checks: C-29058r484972_chk

Determine if the system has non-local published ARP entries. Procedure: # arp -a If any entries have the flag P and no flag L, they are non-local published entries, and this is a finding.

Fix: F-29046r484973_fix

Remove non-local published ARP entries from the system. Procedure: # arp -d <host> Check system initialization files for any commands creating published ARP entries (such as "arp -s <host> <ether> pub" or "arp -f") and removing them.

The system must ignore IPv4 ICMP redirect messages.

CM-6 - Medium - CCI-000366 - V-226897 - SV-226897r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003609

Vuln IDs

V-226897
V-22416

Rule IDs

SV-226897r505925_rule
SV-26630

ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the host's route table and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle attack.

Checks: C-29059r484975_chk

Determine the type of zone that you are currently securing. # zonename If the zone is not the global zone, determine if any interfaces are exclusive to the zone: # dladm show-link If the output indicates "insufficient privileges" then this requirement is not applicable. If the zone is the global zone or the non-global zone has exclusive interfaces verify the system does not accept IPv4 ICMP redirect messages. Procedure: # ndd -get /dev/ip ip_ignore_redirect If the result is not 1, this is a finding.

Fix: F-29047r484976_fix

Configure the system to not accept IPv4 ICMP redirect messages. Procedure: # ndd -set /dev/ip ip_ignore_redirect 1 This command must also be added to a system startup script.

The system must not send IPv4 ICMP redirects.

CM-6 - Medium - CCI-000366 - V-226898 - SV-226898r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003610

Vuln IDs

V-226898
V-22417

Rule IDs

SV-226898r505925_rule
SV-26632

ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain information from the system's route table that could reveal portions of the network topology.

Checks: C-29060r484978_chk

Determine the type of zone that you are currently securing. # zonename If the zone is not the global zone, determine if any interfaces are exclusive to the zone: # dladm show-link If the output indicates "insufficient privileges" then this requirement is not applicable. If the zone is the global zone or the non-global zone has exclusive interfaces verify the system does not send IPv4 ICMP redirect messages. Procedure: # ndd /dev/ip ip_send_redirects If the result is not 0, this is a finding.

Fix: F-29048r484979_fix

Configure the system to not send IPv4 ICMP redirect messages. Procedure: # ndd -set /dev/ip ip_send_redirects 0 Also add this command to a system startup script.

The system must log martian packets.

AU-12 - Low - CCI-000169 - V-226899 - SV-226899r505925_rule

RMF Control

AU-12

Severity

CCI

Version

GEN003611

Vuln IDs

V-226899
V-22418

Rule IDs

SV-226899r505925_rule
SV-29773

Martian packets are packets containing addresses known by the system to be invalid. Logging these messages allows the SA to identify misconfigurations or attacks in progress.

Checks: C-29061r503879_chk

If the system is not a global zone, this vulnerability is not applicable. Determine if the system is configured to log martian packets. Examine the IPF rules on the system. Procedure: # ipfstat -i There must be rules logging inbound traffic containing invalid source addresses, which minimally include the system's own addresses and broadcast addresses for attached subnets. If such rules do not exist, this is a finding.

Fix: F-29049r503880_fix

Configure the system to log martian packets using IPF. Add rules logging inbound traffic containing invalid source addresses, which minimally include the system's own addresses and broadcast addresses for attached subnets. For example, consider a system with a single network connection having IP address 192.168.1.10 with a local subnet broadcast address of 192.168.1.255. Packets with source addresses of 192.168.1.10 and 192.168.1.255 must be logged if received by the system from the network connection. Edit /etc/ipf/ipf.conf and add the following rules, substituting local addresses and interface names: block in log quick on ce0 from 192.168.1.10 to any block in log quick on ce0 from 192.168.1.255 to any Reload the IPF rules. Procedure: # ipf -Fa -A -f /etc/ipf/ipf.conf

A separate file system must be used for user home directories (such as /home or equivalent).

CM-6 - Low - CCI-000366 - V-226900 - SV-226900r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003620

Vuln IDs

V-226900
V-12003

Rule IDs

SV-226900r505925_rule
SV-28618

The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.

Checks: C-29062r484987_chk

Determine if the /export/home path is a separate file system. # grep /export/home /etc/vfstab If no result is returned, /export/home is not on a separate file system and this is a finding. If ZFS is used for home directories, this is not applicable.

Fix: F-29050r484988_fix

Migrate the /export/home path onto a separate file system.

The system must use a separate file system for the system audit data path.

CM-6 - Low - CCI-000366 - V-226901 - SV-226901r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003623

Vuln IDs

V-226901
V-23738

Rule IDs

SV-226901r505925_rule
SV-28628

The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.

Checks: C-29063r484990_chk

Determine the audit log data path. # grep "^dir:" /etc/security/audit_control Determine if the audit log data path is a separate filesystem. # df -h <audit data path> If the returned mount point is "/" this is a finding.

Fix: F-29051r484991_fix

Migrate the system audit data path onto a separate file system.

The system must use a separate filesystem for /tmp (or equivalent).

CM-6 - Low - CCI-000366 - V-226902 - SV-226902r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003624

Vuln IDs

V-226902
V-23739

Rule IDs

SV-226902r505925_rule
SV-28632

The use of separate filesystems for different paths can protect the system from failures resulting from a filesystem becoming full or failing.

Checks: C-29064r484993_chk

Determine if the /tmp path is a separate file system. # grep /tmp /etc/vfstab If no result is returned, /tmp is not on a separate file system, this is a finding. If the returned result indicates that /tmp is mounted on a memory or swap based file system, this is not a finding

Fix: F-29052r484994_fix

Migrate the /tmp path onto a separate file system.

The root file system must employ journaling or another mechanism ensuring file system consistency.

CM-6 - Medium - CCI-000366 - V-226903 - SV-226903r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003640

Vuln IDs

V-226903
V-4304

Rule IDs

SV-226903r505925_rule
SV-40021

File system journaling, or logging, can allow reconstruction of file system data after a system crash, thus, preserving the integrity of data that may have otherwise been lost. Journaling file systems typically do not require consistent checks upon booting after a crash, which can improve system availability. Some file systems employ other mechanisms to ensure consistency which also satisfy this requirement.

Checks: C-29065r503882_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-29053r503883_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.

All local file systems must employ journaling or another mechanism ensuring file system consistency.

CM-6 - Low - CCI-000366 - V-226904 - SV-226904r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003650

Vuln IDs

V-226904
V-22422

Rule IDs

SV-226904r505925_rule
SV-26638

File system journaling, or logging, can allow reconstruction of file system data after a system crash, thus preserving the integrity of data that may have otherwise been lost. Journaling file systems typically do not require consistent checks upon booting after a crash, which can improve system availability. Some file systems employ other mechanisms to ensure consistency which also satisfy this requirement.

Checks: C-29066r484999_chk

Fix: F-29054r485000_fix

Convert local file systems to use journaling or another mechanism ensuring file system consistency.

The system must log authentication informational data.

AU-12 - Medium - CCI-000169 - V-226905 - SV-226905r505925_rule

RMF Control

AU-12

Severity

CCI

Version

GEN003660

Vuln IDs

V-226905
V-12004

Rule IDs

SV-226905r505925_rule
SV-12505

Monitoring and recording successful and unsuccessful logins assists in tracking unauthorized access to the system.

Checks: C-29067r485002_chk

Check /etc/syslog.conf and verify the auth facility is logging both the notice and info level messages by using one of the procedures below. # grep "auth.notice" /etc/syslog.conf # grep "auth.info" /etc/syslog.conf OR # grep 'auth.*' /etc/syslog.conf If auth.* is not found, and either auth.notice or auth.info is not found, this is a finding.

Fix: F-29055r485003_fix

Edit /etc/syslog.conf and add local log destinations for auth.* or both auth.notice and auth.info.

Inetd and xinetd must be disabled or removed if no network services utilizing them are enabled.

CM-7 - Medium - CCI-000381 - V-226906 - SV-226906r505925_rule

RMF Control

CM-7

Severity

CCI

Version

GEN003700

Vuln IDs

V-226906
V-12005

Rule IDs

SV-226906r505925_rule
SV-27426

Unnecessary services should be disabled to decrease the attack surface of the system.

Checks: C-29068r485005_chk

Determine if inetd is running, # svcs -a | grep inetd If inetd is not running, this check is not a finding. # inetadm | grep -v disabled If no enabled/online services are found, yet the inetd daemon is running, this is a finding.

Fix: F-29056r485006_fix

Disable the inetd service. Procedure: # svcadm disable inetd

The inetd.conf file must be owned by root or bin.

AC-3 - Medium - CCI-002165 - V-226907 - SV-226907r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN003720

Vuln IDs

V-226907
V-821

Rule IDs

SV-226907r505925_rule
SV-39883

Failure to give ownership of sensitive files or utilities to root provides the designated owner and unauthorized users with the potential to access sensitive information or change the system configuration which could weaken the system's security posture.

Checks: C-29069r485008_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-29057r485009_fix

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

The inetd.conf file must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226908 - SV-226908r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003730

Vuln IDs

V-226908
V-22423

Rule IDs

SV-226908r505925_rule
SV-39884

Failure to give ownership of sensitive files or utilities to system groups may provide unauthorized users with the potential to access sensitive information or change the system configuration which could weaken the system's security posture.

Checks: C-29070r485011_chk

Check the group ownership of the inetd.conf file. Procedure: # ls -alL /etc/inet/inetd.conf If the file is not group-owned by root, bin, or sys, this is a finding.

Fix: F-29058r485012_fix

Change the group ownership of the inetd.conf file. Procedure: # chgrp sys /etc/inet/inetd.conf

The inetd.conf file must have mode 0440 or less permissive.

AC-3 - Medium - CCI-002165 - V-226909 - SV-226909r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN003740

Vuln IDs

V-226909
V-822

Rule IDs

SV-226909r505925_rule
SV-39885

The Internet service daemon configuration files must be protected as malicious modification could cause Denial of Service or increase the attack surface of the system.

Checks: C-29071r485014_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-29059r485015_fix

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

The inetd.conf file must not have extended ACLs.

CM-6 - Medium - CCI-000366 - V-226910 - SV-226910r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003745

Vuln IDs

V-226910
V-22424

Rule IDs

SV-226910r505925_rule
SV-26653

The Internet service daemon configuration files must be protected as malicious modification could cause Denial of Service or increase the attack surface of the system.

Checks: C-29072r485017_chk

Check the permissions of the inetd configuration file. # ls -lL /etc/inet/inetd.conf If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-29060r485018_fix

Remove the extended ACL from the file. # chmod A- /etc/inet/inetd.conf

The services file must be owned by root or bin.

AC-3 - Medium - CCI-002165 - V-226911 - SV-226911r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN003760

Vuln IDs

V-226911
V-823

Rule IDs

SV-226911r505925_rule
SV-823

Failure to give ownership of sensitive files or utilities to root or bin provides the designated owner and unauthorized users with the potential to access sensitive information or change the system configuration which could weaken the system's security posture.

Checks: C-29073r485020_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-29061r485021_fix

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

The services file must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226912 - SV-226912r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003770

Vuln IDs

V-226912
V-22427

Rule IDs

SV-226912r505925_rule
SV-39903

Failure to give ownership of system configuration files to root or a system group provides the designated owner and unauthorized users with the potential to change the system configuration which could weaken the system's security posture.

Checks: C-29074r485023_chk

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

Fix: F-29062r485024_fix

Change the group-owner of the services file. Procedure: # chgrp root /etc/services

The services file must have mode 0444 or less permissive.

AC-3 - Medium - CCI-002165 - V-226913 - SV-226913r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN003780

Vuln IDs

V-226913
V-824

Rule IDs

SV-226913r505925_rule
SV-824

The services file is critical to the proper operation of network services and must be protected from unauthorized modification. Unauthorized modification could result in the failure of network services.

Checks: C-29075r485026_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-29063r485027_fix

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

The services file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226914 - SV-226914r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003790

Vuln IDs

V-226914
V-22428

Rule IDs

SV-226914r505925_rule
SV-26660

The services file is critical to the proper operation of network services and must be protected from unauthorized modification. If the services file has an extended ACL, it may be possible for unauthorized users to modify the file. Unauthorized modification could result in the failure of network services.

Checks: C-29076r485029_chk

Check the permissions of the /etc/services file. # ls -lL /etc/services If the permissions include a "+", the file has an extended ACL, this is a finding.

Fix: F-29064r485030_fix

Remove the extended ACL from the file. # chmod A- /etc/services

Inetd or xinetd logging/tracing must be enabled.

AU-3 - Low - CCI-000134 - V-226915 - SV-226915r505925_rule

RMF Control

AU-3

Severity

CCI

CCI-000134

Version

GEN003800

Vuln IDs

V-226915
V-1011

Rule IDs

SV-226915r505925_rule
SV-27430

Inetd or xinetd logging and tracing allows the system administrators to observe the IP addresses connecting to their machines and to observe what network services are being sought. This provides valuable information when trying to find the source of malicious users and potential malicious users.

Checks: C-29077r503885_chk

Verify the default value of the inet service property tcp_trace. # inetadm -p |grep tcp_trace If the tcp_trace inet service property is not set or is set to FALSE, this is a finding. Verify that all enabled inetd-managed processes have the tcp_trace inet service property set to the default value or TRUE. # inetadm | grep enabled | awk '{print $NF}' | xargs inetadm -l | more If any enabled inetd-managed processes have the tcp_trace inet service property set to FALSE, this is a finding.

Fix: F-29065r503886_fix

Enable logging or tracing for inetd. Procedure: # inetadm -M tcp_trace=TRUE Set the tcp_trace inet service property to the default for all enabled inetd-managed services. # inetadm | grep enabled | awk '{print $NF}' | xargs -I X inetadm -m X tcp_trace= (Note: The trailing '=' instructs inetd to use the default value for tcp_trace.)

The portmap or rpcbind service must not be installed unless needed.

CM-7 - Medium - CCI-000381 - V-226916 - SV-226916r505925_rule

RMF Control

CM-7

Severity

CCI

Version

GEN003815

Vuln IDs

V-226916
V-22430

Rule IDs

SV-226916r505925_rule
SV-40810

Checks: C-29078r485038_chk

If the system needs the portmap service to operate, this is not applicable. The rpcbind program is part of a core Solaris package and cannot be removed. Verify the permissions on the rpcbind file. # ls -lL /usr/sbin/rpcbind If the rpcbind service is not required and the rpcbind file has non-zero permissions, this is a finding.

Fix: F-29066r485039_fix

Remove all permissions from the rpcbind file. Procedure: # chmod 0000 /usr/sbin/rpcbind

The rshd service must not be installed.

CM-7 - Medium - CCI-000381 - V-226917 - SV-226917r505925_rule

RMF Control

CM-7

Severity

CCI

Version

GEN003825

Vuln IDs

V-226917
V-22431

Rule IDs

SV-226917r505925_rule
SV-26668

The rshd process provides a typically unencrypted, host-authenticated remote access service. SSH should be used in place of this service.

Checks: C-29079r485044_chk

Check if the SUNWrcmdr package is installed. Procedure: # pkginfo SUNWrcmdr If the package is installed, this is a finding.

Fix: F-29067r485045_fix

Remove the SUNWrcmdr package. Procedure: # pkgrm SUNWrcmdr

The rlogind service must not be installed.

CM-7 - Medium - CCI-000381 - V-226918 - SV-226918r505925_rule

RMF Control

CM-7

Severity

CCI

Version

GEN003835

Vuln IDs

V-226918
V-22433

Rule IDs

SV-226918r505925_rule
SV-26670

The rlogind process provides a typically unencrypted, host-authenticated remote access service. SSH should be used in place of this service.

Checks: C-29080r485050_chk

Check if the SUNWrcmdr package is installed. Procedure: # pkginfo SUNWrcmdr If the package is installed, this is a finding.

Fix: F-29068r485051_fix

Remove the SUNWrcmdr package. Procedure: # pkgrm SUNWrcmdr

The rexec daemon must not be running.

CM-7 - High - CCI-000381 - V-226919 - SV-226919r505925_rule

RMF Control

CM-7

Severity

CCI

Version

GEN003840

Vuln IDs

V-226919
V-4688

Rule IDs

SV-226919r505925_rule
SV-27438

The rexecd process provides a typically unencrypted, host-authenticated remote access service. SSH should be used in place of this service.

Checks: C-29081r485053_chk

# svcs rexec If the service is enabled, this is a finding.

Fix: F-29069r485054_fix

# svcadm disable rexec # svcadm refresh inetd

The rexecd service must not be installed.

CM-7 - Medium - CCI-000381 - V-226920 - SV-226920r505925_rule

RMF Control

CM-7

Severity

CCI

Version

GEN003845

Vuln IDs

V-226920
V-22434

Rule IDs

SV-226920r505925_rule
SV-26674

The rexecd process provides a typically unencrypted, host-authenticated remote access service. SSH should be used in place of this service.

Checks: C-29082r485056_chk

Check if the SUNWrcmdr package is installed. Procedure: # pkginfo SUNWrcmdr If the package is installed, this is a finding.

Fix: F-29070r485057_fix

Remove the SUNWrcmdr package. Procedure: # pkgrm SUNWrcmdr

The telnet daemon must not be running.

IA-5 - High - CCI-000197 - V-226921 - SV-226921r505925_rule

RMF Control

IA-5

Severity

CCI

CCI-000197

Version

GEN003850

Vuln IDs

V-226921
V-24386

Rule IDs

SV-226921r505925_rule
SV-39864

The telnet daemon provides a typically unencrypted remote access service which does not provide for the confidentiality and integrity of user passwords or the remote session. If a privileged user were to log on using this service, the privileged user password could be compromised. Satisfies: SRG-OS-000074, SRG-OS-000520

Checks: C-29083r485059_chk

Determine if the telnet daemon is running. # svcs telnet If the telnet service is enabled, this is a finding.

Fix: F-29071r485060_fix

Disable the telnet daemon. # svcadm disable telnet # svcadm refresh inetd

The system must not have the finger service active.

CM-6 - Low - CCI-000366 - V-226922 - SV-226922r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003860

Vuln IDs

V-226922
V-4701

Rule IDs

SV-226922r505925_rule
SV-27441

The finger service provides information about the system's users to network clients. This information could expose information that could be used in subsequent attacks.

Checks: C-29084r485062_chk

If the "SUNWrcmds" package, containing the finger service executable, is not installed, this is not applicable. # svcs finger If the finger service is not disabled, this is a finding.

Fix: F-29072r485063_fix

Disable the finger service and restart inetd. Procedure: # svcadm disable finger # svcadm refresh inetd

The hosts.lpd file (or equivalent) must not contain a "+" character.

CM-6 - Medium - CCI-000366 - V-226923 - SV-226923r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003900

Vuln IDs

V-226923
V-827

Rule IDs

SV-226923r505925_rule
SV-40457

Having the "+" character in the hosts.lpd (or equivalent) file allows all hosts to use local system print resources.

Checks: C-29085r503888_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 *:<port> 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 "<Location />" 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-29073r503889_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

The hosts.lpd (or equivalent) file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226924 - SV-226924r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003950

Vuln IDs

V-226924
V-22436

Rule IDs

SV-226924r505925_rule
SV-26678

Excessive permissions on the hosts.lpd (or equivalent) file may permit unauthorized modification. Unauthorized modifications could disrupt access to local printers from authorized remote hosts or permit unauthorized remote access to local printers.

Checks: C-29086r485078_chk

Check the permissions 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 permissions on any file include a '+', the file has an extended ACL and this is a finding.

Fix: F-29074r485079_fix

Remove the extended ACLs from the files. # chmod A- /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

The traceroute command owner must be root.

CM-6 - Medium - CCI-000366 - V-226925 - SV-226925r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003960

Vuln IDs

V-226925
V-4369

Rule IDs

SV-226925r505925_rule
SV-28392

If the traceroute command owner has not been set to root, an unauthorized user could use this command to obtain knowledge of the network topology inside the firewall. This information may allow an attacker to determine trusted routers and other network information possibly leading to system and network compromise.

Checks: C-29087r485081_chk

# ls -lL /usr/sbin/traceroute If the traceroute command is not owned by root, this is a finding.

Fix: F-29075r485082_fix

Change the owner of the traceroute command to root. Example procedure: # chown root /usr/sbin/traceroute

The traceroute command must be group-owned by sys, bin, or root.

CM-6 - Medium - CCI-000366 - V-226926 - SV-226926r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN003980

Vuln IDs

V-226926
V-4370

Rule IDs

SV-226926r505925_rule
SV-28395

If the group owner of the traceroute command has not been set to a system group, unauthorized users could have access to the command and use it to gain information regarding a network's topology inside of the firewall. This information may allow an attacker to determine trusted routers and other network information possibly leading to system and network compromise.

Checks: C-29088r485084_chk

Check the group ownership of the traceroute file. Procedure: # ls -lL /usr/sbin/traceroute If the traceroute command is not group-owned by root, sys, or bin, this is a finding.

Fix: F-29076r485085_fix

Change the group-owner of the traceroute command to root. Procedure: # chgrp root /usr/sbin/traceroute

The traceroute file must have mode 0700 or less permissive.

AC-3 - Medium - CCI-002165 - V-226927 - SV-226927r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN004000

Vuln IDs

V-226927
V-4371

Rule IDs

SV-226927r505925_rule
SV-28399

If the mode of the traceroute executable is more permissive than 0700, malicious code could be inserted by an attacker and triggered whenever the traceroute command is executed by authorized users. Additionally, if an unauthorized user is granted executable permissions to the traceroute command, it could be used to gain information about the network topology behind the firewall. This information may allow an attacker to determine trusted routers and other network information that may lead to system and network compromise.

Checks: C-29089r485087_chk

# ls -lL /usr/sbin/traceroute If the traceroute command has a mode more permissive than 0700, this is a finding.

Fix: F-29077r485088_fix

Change the mode of the traceroute command. # chmod 0700 /usr/sbin/traceroute

The traceroute file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226928 - SV-226928r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004010

Vuln IDs

V-226928
V-22437

Rule IDs

SV-226928r505925_rule
SV-26682

If an extended ACL exists on the traceroute executable file, it may provide unauthorized users with access to the file. Malicious code could be inserted by an attacker and triggered whenever the traceroute command is executed by authorized users. Additionally, if an unauthorized user is granted executable permissions to the traceroute command, it could be used to gain information about the network topology behind the firewall. This information may allow an attacker to determine trusted routers and other network information possibly leading to system and network compromise.

Checks: C-29090r485090_chk

Check the permissions of the /usr/sbin/traceroute file. # ls -lL /usr/contrib/bin/traceroute If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-29078r485091_fix

Remove the extended ACL from the file. # chmod A- /usr/sbin/traceroute

Administrative accounts must not run a web browser, except as needed for local service administration.

CM-6 - High - CCI-000366 - V-226929 - SV-226929r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004220

Vuln IDs

V-226929
V-4382

Rule IDs

SV-226929r505925_rule
SV-4382

If a web browser flaw is exploited while running as a privileged user, the entire system could be compromised. Specific exceptions for local service administration should be documented in site-defined policy. These exceptions may include HTTP(S)-based tools used for the administration of the local system, services, or attached devices. Examples of possible exceptions are HP's System Management Homepage (SMH), the CUPS administrative interface, and Sun's StorageTek Common Array Manager (CAM) when these services are running on the local system.

Checks: C-29091r503891_chk

Look in the root account home directory for a .netscape or a .mozilla directory. If none exists, this is not a finding. If there is one, verify with the root users and the IAO what the intent of the browsing is. Some evidence may be obtained by using the browser to view cached pages under the .netscape directory.

Fix: F-29079r503892_fix

Enforce policy requiring administrative accounts use web browsers only for local service administration.

The alias file must be owned by root.

AC-3 - Medium - CCI-002165 - V-226930 - SV-226930r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN004360

Vuln IDs

V-226930
V-831

Rule IDs

SV-226930r505925_rule
SV-40493

If the alias file is not owned by root, an unauthorized user may modify the file to add aliases to run malicious code or redirect email.

Checks: C-29092r485096_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 <alias file> If the alias file is not owned by root, this is a finding.

Fix: F-29080r485097_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

The alias file must have mode 0644 or less permissive.

AC-3 - Medium - CCI-002165 - V-226931 - SV-226931r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN004380

Vuln IDs

V-226931
V-832

Rule IDs

SV-226931r505925_rule
SV-40651

Excessive permissions on the aliases file may permit unauthorized modification. If the alias file is modified by an unauthorized user, they may modify the file to run malicious code or redirect email.

Checks: C-29093r485102_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-29081r485103_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

The alias file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226932 - SV-226932r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004390

Vuln IDs

V-226932
V-22439

Rule IDs

SV-226932r505925_rule
SV-26687

Checks: C-29094r485105_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 permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-29082r485106_fix

Remove the extended ACL from the files. # chmod A- /etc/mail/aliases /etc/mail/aliases.db

Files executed through a mail aliases file must be owned by root and must reside within a directory owned and writable only by root.

AC-3 - High - CCI-002165 - V-226933 - SV-226933r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN004400

Vuln IDs

V-226933
V-833

Rule IDs

SV-226933r505925_rule
SV-833

If a file executed through a mail aliases file is not owned and writable only by root, it may be subject to unauthorized modification. Unauthorized modification of files executed through aliases may allow unauthorized users to attain root privileges.

Checks: C-29095r503894_chk

Find the aliases file on the system. Procedure: # find / -name aliases -depth -print # more < aliases file location > Examine the aliases file for any directories or paths that may be utilized. Procedure: # ls -lL < path > Check if the file or parent directory is owned by root. If not, this is a finding.

Fix: F-29083r503895_fix

Edit the /etc/mail/aliases file (alternatively, /usr/lib/sendmail.cf). Locate the entries executing a program. They will appear similar to the following line. Aliasname: : /usr/local/bin/ls (or some other program name) Ensure root owns the programs and the directory(ies) they reside in by using the chown command to change owner to root. Procedure: # chown root filename

Files executed through a mail aliases file must be group-owned by root, bin, or sys, and must reside within a directory group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226934 - SV-226934r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004410

Vuln IDs

V-226934
V-22440

Rule IDs

SV-226934r505925_rule
SV-39904

If a file executed through a mail aliases file is not group-owned by root or a system group, it may be subject to unauthorized modification. Unauthorized modification of files executed through aliases may allow unauthorized users to attain root privileges.

Checks: C-29096r485111_chk

Examine the contents of the /etc/mail/aliases file. For each file referenced, check the group ownership of the file. Procedure: # ls -lL <file referenced from aliases> If the group owner of any file is not root, bin, or sys, this is a finding.

Fix: F-29084r485112_fix

Change the group ownership of the file referenced from /etc/mail/aliases. Procedure: # chgrp root <file referenced from aliases>

Files executed through a mail aliases file must not have extended ACLs.

CM-6 - Medium - CCI-000366 - V-226935 - SV-226935r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004430

Vuln IDs

V-226935
V-22441

Rule IDs

SV-226935r505925_rule
SV-26696

Excessive permissions on files executed through a mail alias file could result in modification by an unauthorized user, execution of malicious code, and/or system compromise.

Checks: C-29097r485114_chk

Examine the contents of the /etc/mail/aliases file. For each file referenced, check the permissions of the file. # ls -lL [file referenced from aliases] If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-29085r485115_fix

Remove the extended ACL from the file. # chmod A- [file referenced from aliases]

Sendmail logging must not be set to less than nine in the sendmail.cf file.

CM-6 - Low - CCI-000366 - V-226936 - SV-226936r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004440

Vuln IDs

V-226936
V-835

Rule IDs

SV-226936r505925_rule
SV-835

If Sendmail is not configured to log at level 9, system logs may not contain the information necessary for tracking unauthorized use of the Sendmail service.

Checks: C-29098r485117_chk

Check if Sendmail logging is set to level 9. Procedure: # grep "O L" /etc/mail/sendmail.cf OR # grep LogLevel /etc/mail/sendmail.cf If logging is set to less than 9, this is a finding.

Fix: F-29086r485118_fix

Edit the sendmail.conf file, locate the "O L" or LogLevel entry and change it to 9.

The system syslog service must log informational and more severe SMTP service messages.

AU-12 - Medium - CCI-000169 - V-226937 - SV-226937r505925_rule

RMF Control

AU-12

Severity

CCI

Version

GEN004460

Vuln IDs

V-226937
V-836

Rule IDs

SV-226937r505925_rule
SV-41546

If informational and more severe SMTP service messages are not logged, malicious activity on the system may go unnoticed.

Checks: C-29099r485120_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-29087r485121_fix

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

The SMTP service log file must be owned by root.

AC-3 - Medium - CCI-002165 - V-226938 - SV-226938r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN004480

Vuln IDs

V-226938
V-837

Rule IDs

SV-226938r505925_rule
SV-837

If the SMTP service log file is not owned by root, then unauthorized personnel may modify or delete the file to hide a system compromise.

Checks: C-29100r485123_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 <file location> If any mail log file is not owned by root, this is a finding.

Fix: F-29088r485124_fix

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

The SMTP service log file must have mode 0644 or less permissive.

AC-3 - Medium - CCI-002165 - V-226939 - SV-226939r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN004500

Vuln IDs

V-226939
V-838

Rule IDs

SV-226939r505925_rule
SV-838

If the SMTP service log file is more permissive than 0644, unauthorized users may be allowed to change the log file.

Checks: C-29101r485126_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 <file location> If the log file permissions are greater than 0644, this is a finding.

Fix: F-29089r485127_fix

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

The SMTP service log file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226940 - SV-226940r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004510

Vuln IDs

V-226940
V-22442

Rule IDs

SV-226940r505925_rule
SV-26700

If the SMTP service log file has an extended ACL, unauthorized users may be allowed to access or to modify the log file.

Checks: C-29102r485129_chk

Examine /etc/syslog.conf and determine the log file(s) receiving logs for mail.crit, mail.debug, mail.*, or *.crit. Check the permissions on these log files. # ls -lL [log file] If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-29090r485130_fix

Remove the extended ACL from the file. # chmod A- [log file]

The SMTP service must not have the EXPN feature active.

CM-6 - Low - CCI-000366 - V-226941 - SV-226941r509220_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004660

Vuln IDs

V-226941
V-4692

Rule IDs

SV-226941r509220_rule
SV-4692

The SMTP EXPN function allows an attacker to determine if an account exists on a system, providing significant assistance to a brute-force attack on user accounts. EXPN may also provide additional information concerning users on the system, such as the full names of account owners. False Positives: False positives may occur with the SMTP EXPN check. According to RFC821, it is acceptable for a server to respond with a 250 (success) or 550 (failure) when the server supports the EXPN command. For example, some servers return "550 EXPN command not available", meaning the command is not supported and the machine is not vulnerable. However, a result of "550 That is a mailing list, not a user" would be a failure code, but not an indication of an error, and the machine would be vulnerable. If false positive is suspected, check the log file for the response from the server.

Checks: C-29103r509218_chk

Determine if EXPN is disabled. Procedure: # telnet localhost 25 expn root If the command does not return a 500 error code of command unrecognized, this is a finding. OR Locate the sendmail.cf configuration file. Procedure: # find / -name sendmail.cf -print # grep -v "^#" <sendmail.cf location> | egrep -i "(goaway|noexpn)" Verify the EXPN command is disabled with an entry in the sendmail.cf file that reads as one of the following: Opnoexpn O PrivacyOptions=noexpn Opgoaway O PrivacyOptions=goaway (Other privacy options, such as novrfy or noetrn, may be included in the same line, separated by commas. The goaway option encompasses a number of privacy options, including noexpn.) If the EXPN command is not disabled, this is a finding.

Fix: F-29091r509219_fix

Edit the sendmail.cf file and add Opnoexpn option. Restart the Sendmail service.

The SMTP service must not have the VRFY feature active.

CM-6 - Low - CCI-000366 - V-226942 - SV-226942r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004680

Vuln IDs

V-226942
V-4693

Rule IDs

SV-226942r505925_rule
SV-4693

The VRFY (Verify) command allows an attacker to determine if an account exists on a system, providing significant assistance to a brute-force attack on user accounts. VRFY may provide additional information about users on the system, such as the full names of account owners.

Checks: C-29104r503897_chk

Determine if VRFY is disabled. Procedure: # telnet localhost 25 vrfy root If the command does not return a 500 error code of command unrecognized, this is a finding. OR Locate the sendmail.cf configuration file. Procedure: # find / -name sendmail.cf -print # grep -v "^#" <sendmail.cf location> |grep -i "(goaway|vrfy)" Verify the VRFY command is disabled with an entry in the sendmail.cf file that reads as one of the following: Opnovrfy O PrivacyOptions=novrfy Opgoaway O PrivacyOptions=goaway (Other privacy options, such as noexpn or noetrn, may be included in the same line, separated by commas. The goaway option encompasses a number of privacy options, including novrfy.) If the VRFY command is not disabled, this is a finding.

Fix: F-29092r503898_fix

If Sendmail is running, add the line Opnovrfy to the Sendmail configuration file, usually located in /etc/sendmail.cf. For other mail servers, contact the vendor for information on how to disable the verify command. Newer versions of Sendmail are available at http://www.sendmail.org or from ftp://ftp.cs.berkeley.edu/ucb/sendmail

The Sendmail service must not have the wizard backdoor active.

CM-6 - Low - CCI-000366 - V-226943 - SV-226943r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004700

Vuln IDs

V-226943
V-4694

Rule IDs

SV-226943r505925_rule
SV-4694

Very old installations of the Sendmail mailing system contained a feature whereby a remote user connecting to the SMTP port can enter the WIZ command and be given an interactive shell with root privileges.

Checks: C-29105r503900_chk

Locate the sendmail.cf configuration file and check for wiz configuration. Procedure: # find / -name sendmail.cf -print # grep -v "^#" <sendmail.cf location> |grep -i wiz If an entry is found for wiz, this is a finding.

Fix: F-29093r503901_fix

If the WIZ command is enabled on Sendmail, it should be disabled by adding this line to the sendmail.cf configuration file (it must be typed in uppercase). OW* For the change to take effect, kill the Sendmail process, refreeze the sendmail.cf file, and restart the Sendmail process.

Mail relaying must be restricted.

CM-6 - Medium - CCI-000366 - V-226944 - SV-226944r509223_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004710

Vuln IDs

V-226944
V-23952

Rule IDs

SV-226944r509223_rule
SV-28908

If unrestricted mail relaying is permitted, unauthorized senders could use this host as a mail relay for the purpose of sending SPAM or other unauthorized activity.

Checks: C-29106r509221_chk

If the system uses Sendmail, locate the sendmail.cf file. Procedure: # find / -name sendmail.cf Determine if Sendmail only binds to loopback addresses by examining the DaemonPortOptions configuration options. Procedure: # grep -i "O DaemonPortOptions" </path/to/sendmail.cf> If there are uncommented DaemonPortOptions lines, and all such lines specify system loopback addresses, this is not a finding. Otherwise, determine if Sendmail is configured to allow open relay operation. Procedure: # find / -name sendmail.mc # grep -i promiscuous_relay </path/to/sendmail.mc> If the promiscuous relay feature is enabled, this is a finding. If the system uses Postfix, locate the main.cf file. Procedure: # find / -name main.cf Determine if Postfix only binds to loopback addresses by examining the inet_interfaces line. Procedure: # grep inet_interfaces </path/to/main.cf> If inet_interfaces is set to loopback-only or contains only loopback addresses, such as 127.0.0.1 and [::1], Postfix is not listening on external network interfaces, this is not a finding. Otherwise, determine if Postfix is configured to restrict clients permitted to relay mail by examining the smtpd_client_restrictions line. Procedure: # grep smtpd_client_restrictions </path/to/main.cf> If the smtpd_client_restrictions line is missing, or does not contain reject, this is a finding. If the line contains permit before reject, this is a finding. If the system is using other SMTP software, consult the software's documentation for procedures to verify mail relaying is restricted.

Fix: F-29094r509222_fix

If the system uses Sendmail, edit the sendmail.mc file and remove the promiscuous_relay configuration. Rebuild the sendmail.cf file from the modified sendmail.mc and restart the service. If the system does not need to receive mail from external hosts, add one or more DaemonPortOptions lines referencing system loopback addresses (such as "O DaemonPortOptions=Addr=127.0.0.1,Port=smtp,Name=MTA") and remove lines containing non-loopback addresses. Restart the service. If the system uses Postfix, edit the main.cf file and add or edit the smtpd_client_restrictions line to have contents permit mynetworks, reject or a similarly restrictive rule. If the system does not need to receive mail from external hosts, add or edit the inet_interfaces line to have contents loopback-only or a set of loopback addresses for the system. Restart the service. If the system is using other SMTP software, consult the software's documentation for procedures to restrict mail relaying.

Unencrypted FTP must not be used on the system.

CM-6 - Medium - CCI-000366 - V-226945 - SV-226945r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004800

Vuln IDs

V-226945
V-12010

Rule IDs

SV-226945r505925_rule
SV-28635

FTP is typically unencrypted and, therefore, presents confidentiality and integrity risks. FTP may be protected by encryption in certain cases, such as when used in a Kerberos environment. SFTP and FTPS are encrypted alternatives to FTP.

Checks: C-29107r485162_chk

Perform the following to determine if unencrypted FTP is enabled. # svcs ftp If FTP is enabled, ask the SA if it is encrypted. If it is not, this is a finding.

Fix: F-29095r485163_fix

# svcadm disable ftp

Anonymous FTP must not be active on the system unless authorized.

CM-6 - Medium - CCI-000366 - V-226946 - SV-226946r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004820

Vuln IDs

V-226946
V-846

Rule IDs

SV-226946r505925_rule
SV-846

Due to the numerous vulnerabilities inherent in anonymous FTP, it is recommended that it not be used. If anonymous FTP must be used on a system, the requirement must be authorized and approved in the system accreditation package.

Checks: C-29108r485165_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-29096r485166_fix

Configure the FTP service to not permit anonymous logins.

If the system is an anonymous FTP server, it must be isolated to the DMZ network.

CM-6 - Medium - CCI-000366 - V-226947 - SV-226947r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004840

Vuln IDs

V-226947
V-4702

Rule IDs

SV-226947r505925_rule
SV-4702

Anonymous FTP is a public data service which is only permitted in a server capacity when located on the DMZ network.

Checks: C-29109r485168_chk

Use the command ftp to connect the system's FTP service. 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 not successful, this check is not applicable. Ask the SA if the system is located on a DMZ network. If the system is not located on a DMZ network, this is a finding.

Fix: F-29097r485169_fix

Move the system to a DMZ network.

The ftpusers file must exist.

AC-3 - Medium - CCI-002165 - V-226948 - SV-226948r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN004880

Vuln IDs

V-226948
V-840

Rule IDs

SV-226948r505925_rule
SV-28404

The ftpusers file contains a list of accounts not allowed to use FTP to transfer files. If this file does not exist, then unauthorized accounts can utilize FTP.

Checks: C-29110r485171_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-29098r485172_fix

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

The ftpusers file must contain account names not allowed to use FTP.

AC-3 - Medium - CCI-002165 - V-226949 - SV-226949r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN004900

Vuln IDs

V-226949
V-841

Rule IDs

SV-226949r505925_rule
SV-28407

The ftpusers file contains a list of accounts that are not allowed to use FTP to transfer files. If the file does not contain the names of all accounts not authorized to use FTP, then unauthorized use of FTP may take place.

Checks: C-29111r485174_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-29099r485175_fix

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

The ftpusers file must be owned by root.

AC-3 - Medium - CCI-002165 - V-226950 - SV-226950r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN004920

Vuln IDs

V-226950
V-842

Rule IDs

SV-226950r505925_rule
SV-28410

If the file ftpusers is not owned by root, an unauthorized user may modify the file to allow unauthorized accounts to use FTP.

Checks: C-29112r485177_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-29100r485178_fix

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

The ftpusers file must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226951 - SV-226951r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004930

Vuln IDs

V-226951
V-22444

Rule IDs

SV-226951r505925_rule
SV-39905

If the ftpusers file is not group-owned by root or a system group, an unauthorized user may modify the file to allow unauthorized accounts to use FTP.

Checks: C-29113r485180_chk

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

Fix: F-29101r485181_fix

Change the group owner of the ftpusers file. Procedure: # chgrp root /etc/ftpusers

The ftpusers file must have mode 0640 or less permissive.

AC-3 - Medium - CCI-002165 - V-226952 - SV-226952r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN004940

Vuln IDs

V-226952
V-843

Rule IDs

SV-226952r505925_rule
SV-28413

Excessive permissions on the ftpusers file could permit unauthorized modification. Unauthorized modification could result in Denial of Service to authorized FTP users or permit unauthorized users to access the FTP service.

Checks: C-29114r485183_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-29102r485184_fix

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

The ftpusers file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226953 - SV-226953r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN004950

Vuln IDs

V-226953
V-22445

Rule IDs

SV-226953r505925_rule
SV-26707

Checks: C-29115r485186_chk

Check the permissions of the /etc/ftpd/ftpusers file. # ls -lL /etc/ftpd/ftpusers If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-29103r485187_fix

Remove the extended ACL from the file. # chmod A- /etc/ftpd/ftpusers

The FTP daemon must be configured for logging or verbose mode.

AU-3 - Low - CCI-000130 - V-226954 - SV-226954r505925_rule

RMF Control

AU-3

Severity

CCI

CCI-000130

Version

GEN004980

Vuln IDs

V-226954
V-845

Rule IDs

SV-226954r505925_rule
SV-40816

The -l option allows basic logging of connections. The verbose (on HP) and the debug (on Solaris) allow logging of what files the FTP session transferred. This extra logging makes it possible to easily track which files are being transferred onto or from a system. If they are not configured, the only option for tracking is the audit files. The audit files are much harder to read. If auditing is not properly configured, then there would be no record at all of the file transfer transactions.

Checks: C-29116r485189_chk

Verify the FTP daemon is invoked with the -l option by SMF. # inetadm -l ftp | grep in.ftpd If the exec name-value pair does not include the -l option for in.ftpd, this is a finding.

Fix: F-29104r485190_fix

Add the -l option to the exec name-value pair used by SMF to invoke the FTP daemon. # inetadm -m ftp exec="/usr/sbin/in.ftpd [other options] -l" Refresh inetd. # svcadm refresh inetd

Anonymous FTP accounts must not have a functional shell.

CM-6 - High - CCI-000366 - V-226955 - SV-226955r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005000

Vuln IDs

V-226955
V-4387

Rule IDs

SV-226955r505925_rule
SV-4387

If an anonymous FTP account has been configured to use a functional shell, attackers could gain access to the shell if the account is compromised.

Checks: C-29117r485192_chk

Check the shell for the anonymous FTP account. Procedure: # grep "^ftp" /etc/passwd This is a finding if the seventh field is empty (the entry ends with a ':') or if the seventh field does not contain one of the following. /bin/false /dev/null /usr/bin/false /bin/true /sbin/nologin

Fix: F-29105r485193_fix

Configure anonymous FTP accounts to use a non-functional shell. If necessary, edit the /etc/passwd file to remove any functioning shells associated with the FTP account and replace them with non-functioning shells, such as, /dev/null.

The anonymous FTP account must be configured to use chroot or a similarly isolated environment.

CM-6 - Medium - CCI-000366 - V-226956 - SV-226956r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005020

Vuln IDs

V-226956
V-4388

Rule IDs

SV-226956r505925_rule
SV-39838

If an anonymous FTP account does not use a chroot or similarly isolated environment, the system may be more vulnerable to exploits against the FTP service. Such exploits could allow an attacker to gain shell access to the system and view, edit, or remove sensitive files.

Checks: C-29118r485195_chk

The default Solaris FTP daemon, in.ftpd, uses the ftp user's home directory as the chroot base for anonymous FTP. If any files and directories within the ftp user's home directory are owned by any user other than root, or if any subdirectory other than pub has permissions more permissive than 0111, this is a finding.

Fix: F-29106r485196_fix

Run the ftpconfig(1M) command to set up a chroot-ed environment for anonymous FTP with appropriate constraints. # ftpconfig < anonymous FTP home directory>

All FTP users must have a default umask of 077.

CM-6 - Medium - CCI-000366 - V-226957 - SV-226957r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005040

Vuln IDs

V-226957
V-12011

Rule IDs

SV-226957r505925_rule
SV-12512

The umask controls the default access mode assigned to newly created files. An umask of 077 limits new files to mode 700 or less permissive. Although umask is stored as a 4-digit number, the first digit representing special access modes is typically ignored or required to be 0.

Checks: C-29119r485198_chk

Check the umask setting for the FTP user. Procedure: # su - ftp $ umask If the umask value does not return 077, this is a finding.

Fix: F-29107r485199_fix

Edit the initialization files for the FTP user and set the umask to 077.

The TFTP daemon must operate in secure mode which provides access only to a single directory on the host file system.

CM-6 - High - CCI-000366 - V-226958 - SV-226958r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005080

Vuln IDs

V-226958
V-847

Rule IDs

SV-226958r505925_rule
SV-28419

Secure mode limits TFTP requests to a specific directory. If TFTP is not running in secure mode, it may be able to write to any file or directory and may seriously impair system integrity, confidentiality, and availability.

Checks: C-29120r485201_chk

Determine if TFTPD is running in secure mode. # grep tftp /etc/inet/inetd.conf OR # svccfg -s tftp/udp6 listprop |grep in.tftpd |grep exec If any returned service line does not use the -s parameter to TFTPD, this is a finding. If TFTP is not installed this check is not applicable.

Fix: F-29108r485202_fix

Edit /etc/inet/inetd.conf and add the -s parameter to TFTPD. # inetconv OR Update the SMF entry for the TFTP daemon. # svccfg -s tftp/udp6 setprop inetd_start/exec = "astring:\"/usr/sbin/in.tftpd -s <other TFTPD options>\""

The TFTP daemon must have mode 0755 or less permissive.

AC-3 - High - CCI-002165 - V-226959 - SV-226959r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN005100

Vuln IDs

V-226959
V-848

Rule IDs

SV-226959r505925_rule
SV-40392

If TFTP runs with the setuid or setgid bit set, it may be able to write to any file or directory and may seriously impair system integrity, confidentiality, and availability.

Checks: C-29121r485204_chk

Check the mode of the TFTP daemon. Procedure: # ls -lL /usr/sbin/in.tftpd If the mode of the file is more permissive than 0755, this is a finding.

Fix: F-29109r485205_fix

Change the mode of the TFTP daemon. Procedure: # chmod 0755 /usr/sbin/in.tftpd

Any active TFTP daemon must be authorized and approved in the system accreditation package.

CM-6 - High - CCI-000366 - V-226960 - SV-226960r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005140

Vuln IDs

V-226960
V-4695

Rule IDs

SV-226960r505925_rule
SV-28423

TFTP is a file transfer protocol often used by embedded systems to obtain configuration data or software. The service is unencrypted and does not require authentication of requests. Data available using this service may be subject to unauthorized access or interception.

Checks: C-29122r485210_chk

Determine if the TFTP daemon is active. # svcs svc:/network/tftp/* If TFTP is found enabled, it is a finding if it is not documented using site-defined procedures.

Fix: F-29110r485211_fix

Disable the TFTP daemon. # svcadm disable svc:/network/tftp/* # svcadm refresh inetd If TFTP is found enabled, it is a finding if it is not documented.

Any X Windows host must write .Xauthority files.

CM-6 - Medium - CCI-000366 - V-226961 - SV-226961r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005160

Vuln IDs

V-226961
V-850

Rule IDs

SV-226961r505925_rule
SV-850

.Xauthority files ensure the user is authorized to access the specific X Windows host. If .Xauthority files are not used, it may be possible to obtain unauthorized access to the X Windows host.

Checks: C-29123r485213_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-29111r485214_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.

All .Xauthority files must have mode 0600 or less permissive.

CM-6 - Medium - CCI-000366 - V-226962 - SV-226962r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005180

Vuln IDs

V-226962
V-12014

Rule IDs

SV-226962r505925_rule
SV-12515

.Xauthority files ensure the user is authorized to access the specific X Windows host. Excessive permissions may permit unauthorized modification of these files, which could lead to Denial of Service to authorized access or allow unauthorized access to be obtained.

Checks: C-29124r485216_chk

Check the file permissions for the .Xauthority files in the home directories of users of X. Procedure: # cd ~<X user> # ls -lL .Xauthority If the file mode is more permissive than 0600, this is finding.

Fix: F-29112r485217_fix

Change the mode of the .Xauthority files. Procedure: # chmod 0600 .Xauthority

The .Xauthority files must not have extended ACLs.

CM-6 - Medium - CCI-000366 - V-226963 - SV-226963r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005190

Vuln IDs

V-226963
V-22446

Rule IDs

SV-226963r505925_rule
SV-26711

.Xauthority files ensure the user is authorized to access the specific X Windows host. Extended ACLs may permit unauthorized modification of these files, which could lead to Denial of Service to authorized access or allow unauthorized access to be obtained.

Checks: C-29125r485219_chk

Check the file permissions for the .Xauthority files. # ls -lL .Xauthority If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-29113r485220_fix

Remove the extended ACL from the file. # chmod A- .Xauthority

X displays must not be exported to the world.

CM-6 - High - CCI-000366 - V-226964 - SV-226964r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005200

Vuln IDs

V-226964
V-4697

Rule IDs

SV-226964r505925_rule
SV-4697

Open X displays allow an attacker to capture keystrokes and to execute commands remotely. Many users have their X Server set to xhost +, permitting access to the X Server by anyone, from anywhere.

Checks: C-29126r503903_chk

If X Windows is not used on the system, this is not applicable. Check the output of the xhost command from an X terminal. Procedure: $ xhost If the output reports access control is enabled (and possibly lists the hosts that can receive X Window logins), this is not a finding. If the xhost command returns a line indicating access control is disabled, this is a finding. NOTE: It may be necessary to define the display if the command reports it cannot open the display. Procedure: $ DISPLAY=MachineName:0.0; export DISPLAY MachineName may be replaced with an Internet Protocol Address. Repeat the check procedure after setting the display.

Fix: F-29114r503904_fix

If using an xhost-type authentication the xhost - command can be used to remove current trusted hosts and then selectively allow only trusted hosts to connect with xhost + commands. A cryptographically secure authentication, such as provided by the xauth program, is always preferred. Refer to your X11 server's documentation for further security information.

.Xauthority or X*.hosts (or equivalent) file(s) must be used to restrict access to the X server.

CM-6 - Medium - CCI-000366 - V-226965 - SV-226965r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005220

Vuln IDs

V-226965
V-12016

Rule IDs

SV-226965r505925_rule
SV-12517

If access to the X server is not restricted, a user's X session may be compromised.

Checks: C-29127r485225_chk

Determine if the X server is running. Procedure: # ps -ef |grep X Determine if xauth is being used. Procedure: # xauth xauth> list If the above command sequence does not show any host other than the localhost, then xauth is not being used. Search the system for an X*.hosts files, where * is a display number that may be used to limit X window connections. If no files are found, X*.hosts files are not being used. If the X*.hosts files contain any unauthorized hosts, this is a finding. If both xauth and X*.hosts files are not being used, this is a finding.

Fix: F-29115r485226_fix

Create an X*.hosts file, where * is a display number that may be used to limit X window connections. Add the list of authorized X clients to the file.

The .Xauthority utility must only permit access to authorized hosts.

CM-6 - Medium - CCI-000366 - V-226966 - SV-226966r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005240

Vuln IDs

V-226966
V-12017

Rule IDs

SV-226966r505925_rule
SV-12518

If unauthorized clients are permitted access to the X server, a user's X session may be compromised.

Checks: C-29128r485228_chk

Check the X Window system access is limited to authorized clients. Procedure: # xauth xauth> list Ask the SA if the clients listed are authorized. If any are not, this is a finding.

Fix: F-29116r485229_fix

Remove unauthorized clients from the xauth configuration. # xauth remove <display name>

X Window System connections that are not required must be disabled.

CM-7 - Medium - CCI-000381 - V-226967 - SV-226967r505925_rule

RMF Control

CM-7

Severity

CCI

Version

GEN005260

Vuln IDs

V-226967
V-12018

Rule IDs

SV-226967r505925_rule
SV-12519

If unauthorized clients are permitted access to the X server, a user's X session may be compromised.

Checks: C-29129r485231_chk

Determine if the X Window system is running. Procedure: # ps -ef |grep X Ask the SA if the X Window system is an operational requirement. If it is not, this is a finding.

Fix: F-29117r485232_fix

Disable the X Windows server on the system.

The system must not have the UUCP service active.

CM-7 - Medium - CCI-000381 - V-226968 - SV-226968r505925_rule

RMF Control

CM-7

Severity

CCI

Version

GEN005280

Vuln IDs

V-226968
V-4696

Rule IDs

SV-226968r505925_rule
SV-28428

The UUCP utility is designed to assist in transferring files, executing remote commands, and sending email between UNIX systems over phone lines and direct connections between systems. The UUCP utility is a primitive and arcane system with many security issues. There are alternate data transfer utilities/products that can be configured to more securely transfer data by providing for authentication, as well as encryption.

Checks: C-29130r485234_chk

# svcs uucp If UUCP is found enabled and its use is not justified and documented with the ISSO, this is a finding.

Fix: F-29118r485235_fix

# svcadm disable uucp # svcadm refresh inetd

SNMP communities, users, and passphrases must be changed from the default.

CM-6 - High - CCI-000366 - V-226969 - SV-226969r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005300

Vuln IDs

V-226969
V-993

Rule IDs

SV-226969r505925_rule
SV-40281

Whether active or not, default SNMP passwords, users, and passphrases must be changed to maintain security. If the service is running with the default authenticators, then anyone can gather data about the system and the network and use the information to potentially compromise the integrity of the system or network(s).

Checks: C-29131r503906_chk

Check the SNMP configuration for default passwords. Locate and examine the SNMP configuration. Procedure: # more /etc/sma/snmp/snmpd.conf /var/sma_snmp/snmpd.conf /etc/snmp/conf/snmpd.conf /usr/sfw/lib/sma_snmp/snmpd.conf Identify any community names or user password configuration. If any community name or password is set to a default value, such as public, private, snmp-trap, or password, this is a finding.

Fix: F-29119r503907_fix

Change the default passwords. To change them, locate the snmpd.conf file and edit it. Locate the line system-group-read-community which has a default password of public and make the password something more random (less guessable). Make the same changes for the lines that read system-group-write-community, read-community, write-community, trap, and trap-community. Read the information in the file carefully. The trap is defining who to send traps to, for instance, by default. It is not a password, but the name of a host.

The SNMP service must use only SNMPv3 or its successors.

CM-7 - Medium - CCI-000381 - V-226970 - SV-226970r505925_rule

RMF Control

CM-7

Severity

CCI

Version

GEN005305

Vuln IDs

V-226970
V-22447

Rule IDs

SV-226970r505925_rule
SV-26715

SNMP Versions 1 and 2 are not considered secure. Without the strong authentication and privacy provided by the SNMP Version 3 User-based Security Model (USM), an attacker or other unauthorized users may gain access to detailed system management information and use the information to launch attacks against the system.

Checks: C-29132r485240_chk

Verify the SNMP daemon is not configured to use the v1 or v2c security models. # egrep '(v1|v2c|community|com2sec)' /etc/sma/snmp/snmpd.conf /var/sma_snmp/snmpd.conf /etc/snmp/conf/snmpd.conf /usr/sfw/lib/sma_snmp/snmpd.conf | grep -v '^#' If any configuration is found, this is a finding.

Fix: F-29120r485241_fix

Edit non-compliant snmpd.conf files and remove references to the v1, v2c, community, or com2sec. Restart the SNMP service. # svcadm restart svc:/application/management/sma:default

The snmpd.conf file must have mode 0600 or less permissive.

AC-3 - Medium - CCI-002165 - V-226971 - SV-226971r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN005320

Vuln IDs

V-226971
V-994

Rule IDs

SV-226971r505925_rule
SV-40262

The snmpd.conf file contains authenticators and must be protected from unauthorized access and modification.

Checks: C-29133r485243_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-29121r485244_fix

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

Management Information Base (MIB) files must have mode 0640 or less permissive.

AC-3 - Medium - CCI-002165 - V-226972 - SV-226972r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN005340

Vuln IDs

V-226972
V-995

Rule IDs

SV-226972r505925_rule
SV-40817

The ability to read the MIB file could impart special knowledge to an intruder or malicious user about the ability to extract compromising information about the system or network.

Checks: C-29134r485246_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-29122r485247_fix

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

Management Information Base (MIB) files must not have extended ACLs.

CM-6 - Medium - CCI-000366 - V-226973 - SV-226973r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005350

Vuln IDs

V-226973
V-22450

Rule IDs

SV-226973r505925_rule
SV-26727

The ability to read the MIB file could impart special knowledge to an intruder or malicious user about the ability to extract compromising information about the system or network.

Checks: C-29135r485249_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 the permissions include a "+", the file has an extended ACL, this is a finding.

Fix: F-29123r485250_fix

Remove the extended ACL from the file. # chmod A- [mib file]

The snmpd.conf files must be owned by root.

CM-6 - Medium - CCI-000366 - V-226974 - SV-226974r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005360

Vuln IDs

V-226974
V-12019

Rule IDs

SV-226974r505925_rule
SV-40274

The snmpd.conf files contain authenticators and must be protected from unauthorized access and modification. If the files are not owned by root, they may be subject to access and modification from unauthorized users.

Checks: C-29136r485252_chk

Determine the owner of the SNMP 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 the snmpd.conf files are not owned by root, this is a finding.

Fix: F-29124r485253_fix

Change the owner of the snmpd.conf file to root. Procedure: # chown root <snmpd.conf file>

The snmpd.conf file must be group-owned by root, sys, or bin.

CM-6 - Medium - CCI-000366 - V-226975 - SV-226975r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005365

Vuln IDs

V-226975
V-22451

Rule IDs

SV-226975r505925_rule
SV-26733

The snmpd.conf file contains authenticators and must be protected from unauthorized access and modification. If the file is not group-owned by a system group, it may be subject to access and modification from unauthorized users.

Checks: C-29137r485255_chk

Check the group ownership of the SNMP configuration files. Procedure: # ls -lL /etc/sma/snmp/snmpd.conf /var/sma_snmp/snmpd.conf /etc/snmp/conf/snmpd.conf /usr/sfw/lib/sma_snmp/snmpd.conf If the files are not group-owned by root, sys, or bin, this is a finding.

Fix: F-29125r485256_fix

Change the group ownership of the SNMP configuration file. Procedure: # chgrp root /etc/sma/snmp/snmpd.conf /var/sma_snmp/snmpd.conf /etc/snmp/conf/snmpd.conf /usr/sfw/lib/sma_snmp/snmpd.conf

The snmpd.conf file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226976 - SV-226976r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005375

Vuln IDs

V-226976
V-22452

Rule IDs

SV-226976r505925_rule
SV-26737

The snmpd.conf file contains authenticators and must be protected from unauthorized access and modification.

Checks: C-29138r485258_chk

Check the permissions of the SNMP configuration files. # ls -lL/etc/sma/snmp/snmpd.conf /var/sma_snmp/snmpd.conf /etc/snmp/conf/snmpd.conf /usr/sfw/lib/sma_snmp/snmpd.conf If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-29126r485259_fix

Remove the extended ACL from the files. # chmod A- /etc/sma/snmp/snmpd.conf /var/sma_snmp/snmpd.conf /etc/snmp/conf/snmpd.conf /usr/sfw/lib/sma_snmp/snmpd.conf

If the system is a Network Management System (NMS) server, it must only run the NMS and any software required by the NMS.

CM-7 - Medium - CCI-000381 - V-226977 - SV-226977r505925_rule

RMF Control

CM-7

Severity

CCI

Version

GEN005380

Vuln IDs

V-226977
V-4392

Rule IDs

SV-226977r505925_rule
SV-4392

Installing extraneous software on a system designated as a dedicated Network Management System (NMS) server poses a security threat to the system and the network. Should an attacker gain access to the NMS through unauthorized software, the entire network may be susceptible to malicious activity.

Checks: C-29139r485261_chk

Ask the SA if this is an NMS server. If it is an NMS server, then ask what other applications run on it. If there is anything other than network management software and DBMS software used only for the storage and inquiry of NMS data, this is a finding.

Fix: F-29127r485262_fix

Ensure only authorized software is loaded on a designated NMS server. Authorized software is limited to the NMS software itself, a database management system for the NMS server if necessary, and network management software.

The /etc/syslog.conf file must have mode 0640 or less permissive.

CM-6 - Medium - CCI-000366 - V-226978 - SV-226978r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005390

Vuln IDs

V-226978
V-22453

Rule IDs

SV-226978r505925_rule
SV-26740

Unauthorized users must not be allowed to access or modify the /etc/syslog.conf file.

Checks: C-29140r485264_chk

Check the permissions of the syslog configuration file. # ls -lL /etc/syslog.conf If the mode of the file is more permissive than 0640, this is a finding.

Fix: F-29128r485265_fix

Change the permissions of the syslog configuration file. # chmod 0640 /etc/syslog.conf

The /etc/syslog.conf file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-226979 - SV-226979r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005395

Vuln IDs

V-226979
V-22454

Rule IDs

SV-226979r505925_rule
SV-26743

Unauthorized users must not be allowed to access or modify the /etc/syslog.conf file.

Checks: C-29141r485267_chk

Check the permissions of the syslog configuration file. # ls -lL /etc/syslog.conf If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-29129r485268_fix

Remove the extended ACL from the file. # chmod A- /etc/syslog.conf

The /etc/syslog.conf file must be owned by root.

CM-6 - Medium - CCI-000366 - V-226980 - SV-226980r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005400

Vuln IDs

V-226980
V-4393

Rule IDs

SV-226980r505925_rule
SV-4393

If the /etc/syslog.conf file is not owned by root, unauthorized users could be allowed to view, edit, or delete important system messages handled by the syslog facility.

Checks: C-29142r485270_chk

Check /etc/syslog.conf ownership. # ls -lL /etc/syslog.conf If /etc/syslog.conf is not owned by root, this is a finding.

Fix: F-29130r485271_fix

Use the chown command to set the owner to root. # chown root /etc/syslog.conf

The /etc/syslog.conf file must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-226981 - SV-226981r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005420

Vuln IDs

V-226981
V-4394

Rule IDs

SV-226981r505925_rule
SV-39892

If the group owner of /etc/syslog.conf is not root, bin, or sys, unauthorized users could be permitted to view, edit, or delete important system messages handled by the syslog facility.

Checks: C-29143r485273_chk

Check /etc/syslog.conf group ownership. Procedure: # ls -lL /etc/syslog.conf If /etc/syslog.conf is not group-owned by root, sys, or bin, this is a finding.

Fix: F-29131r485274_fix

Change the group owner of the /etc/syslog.conf file to root, bin, or sys. Procedure: # chgrp root /etc/syslog.conf

The system must use a remote syslog server (log host).

AU-9 - Medium - CCI-001348 - V-226982 - SV-226982r505925_rule

RMF Control

AU-9

Severity

CCI

CCI-001348

Version

GEN005450

Vuln IDs

V-226982
V-22455

Rule IDs

SV-226982r505925_rule
SV-26745

A syslog server (log host) receives syslog messages from one or more systems. This data can be used as an authoritative log source in the event a system is compromised and its local logs are suspect.

Checks: C-29144r485279_chk

Check the syslog configuration file for remote syslog servers. # grep '@' /etc/syslog.conf | grep -v '^#' If no line is returned, this is a finding.

Fix: F-29132r485280_fix

Edit the syslog configuration file and add an appropriate remote syslog server.

The system must only use remote syslog servers (log hosts) justified and documented using site-defined procedures.

CM-6 - Medium - CCI-000366 - V-226983 - SV-226983r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005460

Vuln IDs

V-226983
V-4395

Rule IDs

SV-226983r505925_rule
SV-4395

If a remote log host is in use and it has not been justified and documented with the IAO, sensitive information could be obtained by unauthorized users without the SA's knowledge. A remote log host is any host to which the system is sending syslog messages over a network.

Checks: C-29145r485282_chk

Examine the syslog.conf file for any references to remote log hosts. # grep -v "^#" /etc/syslog.conf | grep '@' Destination locations beginning with an @ represent log hosts. If the log host name is a local alias, such as log host, consult the /etc/hosts or other name databases as necessary to obtain the canonical name or address for the log host. Determine if the host referenced is a log host documented using site-defined procedures. If an undocumented log host is referenced, this is a finding.

Fix: F-29133r485283_fix

Remove, replace, or document the referenced undocumented log host.

The SSH client must be configured to only use the SSHv2 protocol.

IA-5 - Medium - CCI-000197 - V-226984 - SV-226984r505925_rule

RMF Control

IA-5

Severity

CCI

CCI-000197

Version

GEN005501

Vuln IDs

V-226984
V-22456

Rule IDs

SV-226984r505925_rule
SV-26749

SSHv1 is not a DoD-approved protocol and has many well-known vulnerability exploits. Exploits of the SSH client could provide access to the system with the privileges of the user running the client.

Checks: C-29146r485291_chk

Check the SSH client configuration for allowed protocol versions. # grep -i protocol /etc/ssh/ssh_config | grep -v '^#' If the returned protocol configuration allows versions less than 2, this is a finding.

Fix: F-29134r485292_fix

Edit the /etc/ssh/ssh_config file and add or edit a Protocol configuration line that does not allow versions less than 2.

The SSH daemon must only listen on management network addresses unless authorized for uses other than management.

CM-6 - Medium - CCI-000366 - V-226985 - SV-226985r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005504

Vuln IDs

V-226985
V-22457

Rule IDs

SV-226985r505925_rule
SV-26750

The SSH daemon should only listen on network addresses designated for management traffic. If the system has multiple network interfaces and SSH listens on addresses not designated for management traffic, the SSH service could be subject to unauthorized access. If SSH is used for purposes other than management, such as providing an SFTP service, the list of approved listening addresses may be documented.

Checks: C-29147r485294_chk

Check the SSH daemon configuration for listening network addresses. # grep -i Listen /etc/ssh/sshd_config | grep -v '^#' If no configuration is returned, or if a returned Listen configuration contains addresses not designated for management traffic, this is a finding.

Fix: F-29135r485295_fix

Edit the SSH daemon configuration to specify listening network addresses designated for management traffic.

The SSH daemon must be configured to only use FIPS 140-2 approved ciphers.

AC-17 - Medium - CCI-000068 - V-226986 - SV-226986r505925_rule

RMF Control

AC-17

Severity

CCI

Version

GEN005505

Vuln IDs

V-226986
V-22458

Rule IDs

SV-226986r505925_rule
SV-41035

DoD information systems are required to use FIPS 140-2 approved ciphers. SSHv2 ciphers meeting this requirement are 3DES and AES. Satisfies: SRG-OS-000033, SRG-OS-000505, SRG-OS-000555

Checks: C-29148r485297_chk

Check the SSH daemon configuration for allowed ciphers. # grep -i ciphers /etc/ssh/sshd_config | grep -v '^#' If no lines are returned, or the returned ciphers list contains any cipher not starting with 3des or aes, this is a finding.

Fix: F-29136r485298_fix

Edit /etc/ssh/sshd_config and change or set the Ciphers line to the following. Ciphers aes128-ctr, aes192-ctr, aes256-ctr

The SSH daemon must be configured to not use Cipher-Block Chaining (CBC) ciphers.

CM-6 - Medium - CCI-000366 - V-226987 - SV-226987r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005506

Vuln IDs

V-226987
V-22459

Rule IDs

SV-226987r505925_rule
SV-26752

The Cipher-Block Chaining (CBC) mode of encryption as implemented in the SSHv2 protocol is vulnerable to chosen plain text attacks and must not be used.

Checks: C-29149r503909_chk

Fix: F-29137r503910_fix

Edit /etc/ssh/sshd_config and add or edit the "Ciphers" line. Only include ciphers that start with "3des" or "aes" and do not contain "cbc". For the list of available ciphers for the particular version of your software, consult the sshd_config manpage. Restart the SSH daemon.

The SSH daemon must be configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms.

AC-17 - Medium - CCI-001453 - V-226988 - SV-226988r505925_rule

RMF Control

AC-17

Severity

CCI

CCI-001453

Version

GEN005507

Vuln IDs

V-226988
V-22460

Rule IDs

SV-226988r505925_rule
SV-26753

DoD information systems are required to use FIPS 140-2 approved cryptographic hash functions. Satisfies: SRG-OS-000250, SRG-OS-000495, SRG-OS-000500

Checks: C-29150r485303_chk

Check the SSH daemon configuration for allowed MACs. Procedure: # grep -i macs /etc/ssh/sshd_config | grep -v '^#' If no lines are returned, or the returned MACs list contains any MAC that is not hmac-sha1 or a better hmac algorithm that is on the FIPS 140-2 approved list, this is a finding.

Fix: F-29138r485304_fix

Edit the SSH daemon configuration and remove any MACs that are not hmac-sha1 or a better hmac algorithm that is on the FIPS 140-2 approved list. If necessary, add a MACs line.

The SSH client must be configured to only use FIPS 140-2 approved ciphers.

AC-17 - Medium - CCI-000068 - V-226989 - SV-226989r505925_rule

RMF Control

AC-17

Severity

CCI

Version

GEN005510

Vuln IDs

V-226989
V-22461

Rule IDs

SV-226989r505925_rule
SV-26754

DoD information systems are required to use FIPS 140-2 approved ciphers. SSHv2 ciphers meeting this requirement are 3DES and AES. Satisfies: SRG-OS-000033, SRG-OS-000505, SRG-OS-000555

Checks: C-29151r485306_chk

Check the SSH client configuration for allowed ciphers. # grep -i ciphers /etc/ssh/ssh_config | grep -v '^#' If no lines are returned, the returned ciphers list contains any cipher not starting with 3des or aes, this is a finding.

Fix: F-29139r485307_fix

Edit /etc/ssh/ssh_config and add or edit the "Ciphers" line. Only include ciphers that start with "3des" or "aes" and do not contain "cbc". For the list of available ciphers for the particular version of your software, consult the ssh_config manpage.

The SSH client must be configured to not use CBC-based ciphers.

CM-6 - Medium - CCI-000366 - V-226990 - SV-226990r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005511

Vuln IDs

V-226990
V-22462

Rule IDs

SV-226990r505925_rule
SV-26755

The Cipher-Block Chaining (CBC) mode of encryption as implemented in the SSHv2 protocol is vulnerable to chosen plain text attacks and must not be used.

Checks: C-29152r485309_chk

Check the SSH client configuration for allowed ciphers. # grep -i ciphers /etc/ssh/ssh_config | grep -v '^#' If no lines are returned, or the returned ciphers list contains any cipher ending with cbc, this is a finding.

Fix: F-29140r485310_fix

The SSH client must be configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms.

AC-17 - Medium - CCI-001453 - V-226991 - SV-226991r505925_rule

RMF Control

AC-17

Severity

CCI

CCI-001453

Version

GEN005512

Vuln IDs

V-226991
V-22463

Rule IDs

SV-226991r505925_rule
SV-26756

DoD information systems are required to use FIPS 140-2 approved cryptographic hash functions. Satisfies: SRG-OS-000250, SRG-OS-000495, SRG-OS-000500

Checks: C-29153r485312_chk

Check the SSH client configuration for allowed MACs. Procedure: # grep -i macs /etc/ssh/ssh_config | grep -v '^#' If no lines are returned, or the returned MACs list contains any MAC that is not hmac-sha1 or a better hmac algorithm that is on the FIPS 140-2 approved list, this is a finding.

Fix: F-29141r485313_fix

Edit the SSH client configuration and remove any MACs that are not hmac-sha1 or a better hmac algorithm that is on the FIPS 140-2 approved list. If necessary, add a MACs line.

The SSH daemon must restrict login ability to specific users and/or groups.

CM-6 - Medium - CCI-000366 - V-226992 - SV-226992r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005521

Vuln IDs

V-226992
V-22470

Rule IDs

SV-226992r505925_rule
SV-26763

Restricting SSH logins to a limited group of users, such as system administrators, prevents password-guessing and other SSH attacks from reaching system accounts and other accounts not authorized for SSH access.

Checks: C-29154r485315_chk

Check the SSH daemon configuration for the AllowGroups setting. # grep -i AllowGroups /etc/ssh/sshd_config | grep -v '^#' If no lines are returned, this is a finding.

Fix: F-29142r485316_fix

Edit the SSH daemon configuration and add an AllowGroups directive.

The SSH public host key files must have mode 0644 or less permissive.

CM-6 - Medium - CCI-000366 - V-226993 - SV-226993r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005522

Vuln IDs

V-226993
V-22471

Rule IDs

SV-226993r505925_rule
SV-26764

If a public host key file is modified by an unauthorized user, the SSH service may be compromised.

Checks: C-29155r485318_chk

Check the permissions for SSH public host key files. # ls -lL /etc/ssh/*key.pub If any file has a mode more permissive than 0644, this is a finding.

Fix: F-29143r485319_fix

Change the permissions for the SSH public host key files. # chmod 0644 /etc/ssh/*key.pub

The SSH private host key files must have mode 0600 or less permissive.

CM-6 - Medium - CCI-000366 - V-226994 - SV-226994r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005523

Vuln IDs

V-226994
V-22472

Rule IDs

SV-226994r505925_rule
SV-26765

If an unauthorized user obtains the private SSH host key file, the host could be impersonated.

Checks: C-29156r485321_chk

Check the permissions for SSH private host key files. # ls -lL /etc/ssh/*key If any file has a mode more permissive than 0600, this is a finding.

Fix: F-29144r485322_fix

Change the permissions for the SSH private host key files. # chmod 0600 /etc/ssh/*key

The SSH daemon must not permit GSSAPI authentication unless needed.

CM-6 - Low - CCI-000366 - V-226995 - SV-226995r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005524

Vuln IDs

V-226995
V-22473

Rule IDs

SV-226995r505925_rule
SV-26766

GSSAPI authentication is used to provide additional authentication mechanisms to applications. Allowing GSSAPI authentication through SSH exposes the system's GSSAPI to remote hosts, increasing the attack surface of the system. GSSAPI authentication must be disabled unless needed.

Checks: C-29157r503912_chk

Ask the SA if GSSAPI authentication is used for SSH authentication to the system. If so, this is not applicable. Check the SSH daemon configuration for the GSSAPI authentication setting. # grep -i GSSAPIAuthentication /etc/ssh/sshd_config | grep -v '^#' If no lines are returned, or the setting is set to yes, this is a finding.

Fix: F-29145r503913_fix

Edit the SSH daemon configuration and set (add if necessary) a GSSAPIAuthentication directive set to no.

The SSH client must not permit GSSAPI authentication unless needed.

CM-6 - Low - CCI-000366 - V-226996 - SV-226996r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005525

Vuln IDs

V-226996
V-22474

Rule IDs

SV-226996r505925_rule
SV-26767

Checks: C-29158r503915_chk

Check the SSH clients configuration for the GSSAPI authentication setting. # grep -i GSSAPIAuthentication /etc/ssh/ssh_config | grep -v '^#' If no lines are returned, or the setting is set to yes, this is a finding.

Fix: F-29146r503916_fix

Edit the SSH client configuration and set (add if necessary) a GSSAPIAuthentication directive set to no.

The SSH daemon must perform strict mode checking of home directory configuration files.

CM-6 - Medium - CCI-000366 - V-226997 - SV-226997r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005536

Vuln IDs

V-226997
V-22485

Rule IDs

SV-226997r505925_rule
SV-40400

If other users have access to modify user-specific SSH configuration files, they may be able to log into the system as another user.

Checks: C-29159r485330_chk

Check the SSH daemon configuration for the StrictModes setting. # grep -i StrictModes /etc/ssh/sshd_config | grep -v '^#' If the setting is present and not set to yes, this is a finding.

Fix: F-29147r485331_fix

Edit the SSH daemon configuration and change the StrictModes setting value to yes or remove it entirely.

The SSH daemon must not allow rhosts RSA authentication.

CM-6 - Medium - CCI-000366 - V-226998 - SV-226998r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005538

Vuln IDs

V-226998
V-22487

Rule IDs

SV-226998r505925_rule
SV-40396

If SSH permits rhosts RSA authentication, a user may be able to log in based on the keys of the host originating the request and not any user-specific authentication.

Checks: C-29160r485333_chk

Check the SSH daemon configuration for the RhostsRSAAuthentication setting. # grep -i RhostsRSAAuthentication /etc/ssh/sshd_config | grep -v '^#' If the setting is set to yes, this is a finding.

Fix: F-29148r485334_fix

Edit the SSH daemon configuration and change the RhostsRSAAuthentication setting value to no or remove it entirely.

The SSH daemon must not allow compression or must only allow compression after successful authentication.

CM-6 - Medium - CCI-000366 - V-226999 - SV-226999r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005539

Vuln IDs

V-226999
V-22488

Rule IDs

SV-226999r505925_rule
SV-26787

If compression is allowed in an SSH connection prior to authentication, vulnerabilities in the compression software could result in compromise of the system from an unauthenticated connection, potentially with root privileges.

Checks: C-29161r485336_chk

Check the SSH daemon configuration for the Compression setting. # grep -i Compression /etc/ssh/sshd_config | grep -v '^#' If the setting is not present, or set to yes, this is a finding.

Fix: F-29149r485337_fix

Edit the SSH daemon configuration and add or edit the Compression setting value to no or delayed.

The SSH daemon must be configured for IP filtering.

CM-6 - Medium - CCI-000366 - V-227000 - SV-227000r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005540

Vuln IDs

V-227000
V-12022

Rule IDs

SV-227000r505925_rule
SV-40279

The SSH daemon must be configured for IP filtering to provide a layered defense against connection attempts from unauthorized addresses.

Checks: C-29162r485339_chk

Check the TCP wrappers configuration files to determine if SSHD is configured to use TCP wrappers. Procedure: # egrep '^[^#:]*(ALL|sshd)' /etc/hosts.deny # egrep '^[^#:]*(ALL|sshd)' /etc/hosts.allow If neither of the hosts.deny or hosts.allow files exist, this is a finding. If no entries are returned, the TCP wrappers are not configured for SSHD, this is a finding.

Fix: F-29150r485340_fix

Add appropriate IP restrictions for SSH to the /etc/hosts.deny and/or /etc/hosts.allow files.

The SSH daemon must be configured with the Department of Defense (DoD) login banner.

AC-8 - Medium - CCI-000048 - V-227001 - SV-227001r505925_rule

RMF Control

AC-8

Severity

CCI

Version

GEN005550

Vuln IDs

V-227001
V-22489

Rule IDs

SV-227001r505925_rule
SV-40280

Failure to display the DoD logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. The SSH service must be configured to display the DoD logon warning banner through the SSH daemon configuration. The SSH daemon may also be used to provide SFTP service. The warning banner configuration for SSH will apply to SFTP.

Checks: C-29163r503918_chk

Verify the SSH daemon is configured for logon warning banners. # grep -i banner /etc/ssh/sshd_config | grep -v '^#' # cat [banner file] Verify the Banner configuration line is present and the file it references contains a login warning banner. If the SSH daemon is not configured to display a logon warning banner, this is a finding.

Fix: F-29151r503919_fix

Edit the SSH daemon configuration and add (or edit) a banner setting referencing a file containing a logon warning banner. 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."

The system must be configured with a default gateway for IPv4 if the system uses IPv4, unless the system is a router.

CM-6 - Medium - CCI-000366 - V-227002 - SV-227002r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005560

Vuln IDs

V-227002
V-4397

Rule IDs

SV-227002r505925_rule
SV-30079

If a system has no default gateway defined, the system is at increased risk of man-in-the-middle, monitoring, and Denial of Service attacks.

Checks: C-29164r485345_chk

Check the system for an IPv4 default route. Procedure: # netstat -r |grep default If a default route is not defined, this is a finding.

Fix: F-29152r485346_fix

Create or edit /etc/defaultrouter to contain the default gateway address. Procedure (for a default gateway of 192.168.3.1): # echo "192.168.3.1" > /etc/defaultrouter Restart the system for the setting to take effect.

The system must be configured with a default gateway for IPv6 if the system uses IPv6, unless the system is a router.

CM-6 - Medium - CCI-000366 - V-227003 - SV-227003r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005570

Vuln IDs

V-227003
V-22490

Rule IDs

SV-227003r505925_rule
SV-26804

If a system has no default gateway defined, the system is at increased risk of man-in-the-middle, monitoring, and Denial of Service attacks.

Checks: C-29165r485348_chk

Check for a default route for IPv6. # netstat -f inet6 -r | grep default If the system uses IPv6, and no results are returned, this is a finding.

Fix: F-29153r485349_fix

Add a default route for IPv6. # route add -inet6 default <gateway> Add this command to an init script.

A system used for routing must not run other network services or applications.

CM-6 - Medium - CCI-000366 - V-227004 - SV-227004r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005580

Vuln IDs

V-227004
V-4398

Rule IDs

SV-227004r505925_rule
SV-4398

Installing extraneous software on a system designated as a dedicated router poses a security threat to the system and the network. Should an attacker gain access to the router through the unauthorized software, the entire network is susceptible to malicious activity.

Checks: C-29166r485351_chk

Ask the SA if the system is a designated router. If it is not, this is not applicable. Check the system for non-routing network services. Procedure: # netstat -a | grep -i listen # ps -ef If non-routing services, including Web servers, file servers, DNS servers, or applications servers, but excluding management services, such as SSH and SNMP, are running on the system, this is a finding.

Fix: F-29154r485352_fix

Ensure only authorized software is loaded on a designated router. Authorized software will be limited to the most current version of routing protocols and SSH for system administration purposes.

The system must not be running any routing protocol daemons, unless the system is a router.

CM-6 - Medium - CCI-000366 - V-227005 - SV-227005r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005590

Vuln IDs

V-227005
V-22665

Rule IDs

SV-227005r505925_rule
SV-39878

Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not required, system network information may be unnecessarily transmitted across the network.

Checks: C-29167r485354_chk

Fix: F-29155r485355_fix

Disable any routing protocol daemons. # svcadm disable <routing protocol daemon>

The NFS export configuration file must be owned by root.

CM-6 - Medium - CCI-000366 - V-227006 - SV-227006r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005740

Vuln IDs

V-227006
V-928

Rule IDs

SV-227006r505925_rule
SV-28444

Failure to give ownership of the NFS export configuration file to root provides the designated owner and possible unauthorized users with the potential to change system configuration which could weaken the system's security posture.

Checks: C-29168r485363_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-29156r485364_fix

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

The NFS export configuration file must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-227007 - SV-227007r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005750

Vuln IDs

V-227007
V-22492

Rule IDs

SV-227007r505925_rule
SV-26813

Failure to give group ownership of the NFS export configuration file to root or system groups provides the designated group owner and possible unauthorized users with the potential to change system configuration which could weaken the system's security posture.

Checks: C-29169r485366_chk

Check the group ownership of the NFS export configuration file. Procedure: # ls -lL /etc/dfs/dfstab If the file is not group-owned by root, bin, or sys, this is a finding.

Fix: F-29157r485367_fix

Change the group ownership of the NFS export configuration file. Procedure: # chgrp root /etc/dfs/dfstab

The NFS export configuration file must have mode 0644 or less permissive.

CM-6 - Low - CCI-000366 - V-227008 - SV-227008r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005760

Vuln IDs

V-227008
V-929

Rule IDs

SV-227008r505925_rule
SV-28446

Excessive permissions on the NFS export configuration file could allow unauthorized modification of the file, which could result in Denial of Service to authorized NFS exports and the creation of additional unauthorized exports.

Checks: C-29170r485369_chk

# ls -lL /etc/dfs/dfstab If the file has a mode more permissive than 0644, this is a finding.

Fix: F-29158r485370_fix

Change the permissions of the dfstab file to 664 or less permissive. # chmod 0644 /etc/dfs/dfstab

The NFS exports configuration file must not have an extended ACL.

CM-6 - Low - CCI-000366 - V-227009 - SV-227009r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005770

Vuln IDs

V-227009
V-22493

Rule IDs

SV-227009r505925_rule
SV-26816

File system extended ACLs provide access to files beyond what is allowed by the mode numbers of the files. Excessive permissions on the NFS export configuration file could allow unauthorized modification of the file, which could result in Denial of Service to authorized NFS exports and the creation of additional unauthorized exports.

Checks: C-29171r485372_chk

Check the group ownership of the NFS export configuration file. # ls -lL /etc/dfs/dfstab If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-29159r485373_fix

Remove the extended ACL from the file. # chmod A- /etc/dfs/dfstab

All NFS-exported system files and system directories must be owned by root.

CM-6 - Medium - CCI-000366 - V-227010 - SV-227010r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005800

Vuln IDs

V-227010
V-931

Rule IDs

SV-227010r505925_rule
SV-40303

Failure to give ownership of sensitive files or directories to root provides the designated owner and possible unauthorized users with the potential to access sensitive information or change system configuration which could weaken the system's security posture.

Checks: C-29172r485375_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 <exported file system path> If the files and directories are not owned by root, this is a finding.

Fix: F-29160r485376_fix

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

All NFS exported system files and system directories must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-227011 - SV-227011r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005810

Vuln IDs

V-227011
V-22496

Rule IDs

SV-227011r505925_rule
SV-26821

Failure to give group ownership of sensitive files or directories to root provides the members of the owning group with the potential to access sensitive information or change system configuration which could weaken the system's security posture.

Checks: C-29173r485378_chk

List the exports. # cat /etc/dfs/dfstab OR # more /etc/dfs/sharetab For each export, check the ownership information. # ls -ldL <export> If the directory is not group-owned by root, sys, or bin this is a finding.

Fix: F-29161r485379_fix

Change the group owner of the export directory. # chgrp root <export>

The NFS anonymous UID and GID must be configured to values that have no permissions.

IA-2 - Medium - CCI-000764 - V-227012 - SV-227012r505925_rule

RMF Control

IA-2

Severity

CCI

CCI-000764

Version

GEN005820

Vuln IDs

V-227012
V-932

Rule IDs

SV-227012r505925_rule
SV-40304

When an NFS server is configured to deny remote root access, a selected UID and GID are used to handle requests from the remote root user. The UID and GID should be chosen from the system to provide the appropriate level of non-privileged access.

Checks: C-29174r485381_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-29162r485382_fix

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

The system's NFS export configuration must not have the sec option set to none (or equivalent); additionally, the default authentication must not to be set to none.

CM-6 - Medium - CCI-000366 - V-227013 - SV-227013r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005860

Vuln IDs

V-227013
V-934

Rule IDs

SV-227013r505925_rule
SV-40306

If sec=none on Solaris, all NFS requests are mapped to an unknown/common user instead of being processed according to the provided UID.

Checks: C-29175r485387_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-29163r485388_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.

The NFS server must not allow remote root access.

CM-6 - Medium - CCI-000366 - V-227014 - SV-227014r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005880

Vuln IDs

V-227014
V-935

Rule IDs

SV-227014r505925_rule
SV-40307

If the NFS server allows root access to local file systems from remote hosts, this access could be used to compromise the system.

Checks: C-29176r485390_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-29164r485391_fix

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

The nosuid option must be enabled on all NFS client mounts.

CM-6 - Medium - CCI-000366 - V-227015 - SV-227015r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN005900

Vuln IDs

V-227015
V-936

Rule IDs

SV-227015r505925_rule
SV-28452

Enabling the nosuid mount option prevents the system from granting owner or group-owner privileges to programs with the setuid or setgid bit set. If the system does not restrict this access, users with unprivileged access to the local system may be able to acquire privileged access by executing setuid or setgid files located on the mounted NFS file system.

Checks: C-29177r485393_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-29165r485394_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.

The system must not have any peer-to-peer file-sharing application installed.

CM-7 - Medium - CCI-000381 - V-227016 - SV-227016r505925_rule

RMF Control

CM-7

Severity

CCI

Version

GEN006040

Vuln IDs

V-227016
V-12025

Rule IDs

SV-227016r505925_rule
SV-12526

Peer-to-peer file-sharing software can result in the unintentional exfiltration of information. There are also many legal issues associated with these types of utilities including copyright infringement or other intellectual property issues. The ASD Memo "Use of Peer-to-Peer (P2P) File-Sharing Applications across the DoD" states the following: "P2P file-sharing applications are authorized for use on DoD networks with approval by the appropriate Designated Approval Authority (DAA). Documented requirements, security architecture, configuration management process, and a training program for users are all requirements within the approval process. The unauthorized use of application or services, including P2P applications, is prohibited, and such applications or services must be eliminated." P2P applications include, but are not limited to, the following: -Napster, -Kazaa, -ARES, -Limewire, -IRC Chat Relay, and -BitTorrent.

Checks: C-29178r503921_chk

Ask the SA if any peer-to-peer file-sharing applications are installed. Some examples of these applications include: - Napster, - Kazaa, - ARES, - Limewire, - IRC Chat Relay, and - BitTorrent. If any of these applications are installed, this is a finding.

Fix: F-29166r503922_fix

Uninstall the peer-to-peer file sharing application(s) from the system.

The system must not run Samba unless needed.

CM-7 - Medium - CCI-000381 - V-227017 - SV-227017r505925_rule

RMF Control

CM-7

Severity

CCI

Version

GEN006060

Vuln IDs

V-227017
V-4321

Rule IDs

SV-227017r505925_rule
SV-4321

Samba is a tool used for the sharing of files and printers between Windows and UNIX operating systems. It provides access to sensitive files and, therefore, poses a security risk if compromised.

Checks: C-29179r485402_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-29167r485403_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.

The smb.conf file must be owned by root.

CM-6 - Medium - CCI-000366 - V-227018 - SV-227018r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006100

Vuln IDs

V-227018
V-1027

Rule IDs

SV-227018r505925_rule
SV-40291

The smb.conf file allows access to other machines on the network and grants permissions to certain users. If it is owned by another user, the file may be maliciously modified and the Samba configuration could be compromised.

Checks: C-29180r485408_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-29168r485409_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

The smb.conf file must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-227019 - SV-227019r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006120

Vuln IDs

V-227019
V-1056

Rule IDs

SV-227019r505925_rule
SV-39890

If the group owner of the smb.conf file is not root or a system group, the file may be maliciously modified and the Samba configuration could be compromised.

Checks: C-29181r485411_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-29169r485412_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

The smb.conf file must have mode 0644 or less permissive.

AC-3 - Medium - CCI-002165 - V-227020 - SV-227020r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN006140

Vuln IDs

V-227020
V-1028

Rule IDs

SV-227020r505925_rule
SV-40294

If the smb.conf file has excessive permissions, the file may be maliciously modified and the Samba configuration could be compromised.

Checks: C-29182r485414_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-29170r485415_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

The smb.conf file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-227021 - SV-227021r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006150

Vuln IDs

V-227021
V-22497

Rule IDs

SV-227021r505925_rule
SV-26824

Excessive permissions could endanger the security of the Samba configuration file and, ultimately, the system and network.

Checks: C-29183r485417_chk

Check the group ownership of the Samba configuration 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 permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-29171r485418_fix

Remove the extended ACL from the file. # chmod A- /etc/smb.conf /etc/sfw/smb.conf /etc/samba/smb.conf /etc/sfw/samba/smb.conf

The smbpasswd file must be owned by root.

CM-6 - Medium - CCI-000366 - V-227022 - SV-227022r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006160

Vuln IDs

V-227022
V-1029

Rule IDs

SV-227022r505925_rule
SV-40284

If the smbpasswd file is not owned by root, the smbpasswd file may be maliciously accessed or modified, potentially resulting in the compromise of Samba accounts.

Checks: C-29184r485420_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-29172r485421_fix

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

The smbpasswd file must be group-owned by root.

CM-6 - Medium - CCI-000366 - V-227023 - SV-227023r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006180

Vuln IDs

V-227023
V-1058

Rule IDs

SV-227023r505925_rule
SV-40287

If the smbpasswd file is not group-owned by root, the smbpasswd file may be maliciously accessed or modified, potentially resulting in the compromise of Samba accounts.

Checks: C-29185r485423_chk

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

Fix: F-29173r485424_fix

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

The smbpasswd file must have mode 0600 or less permissive.

AC-3 - Medium - CCI-002165 - V-227024 - SV-227024r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN006200

Vuln IDs

V-227024
V-1059

Rule IDs

SV-227024r505925_rule
SV-40289

If the smbpasswd file has a mode more permissive than 0600, the smbpasswd file may be maliciously accessed or modified, potentially resulting in the compromise of Samba accounts.

Checks: C-29186r485426_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-29174r485427_fix

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

The smbpasswd file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-227025 - SV-227025r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006210

Vuln IDs

V-227025
V-22498

Rule IDs

SV-227025r505925_rule
SV-26828

If the permissions of the smbpasswd file are too permissive, the smbpasswd file may be maliciously accessed or modified, potentially resulting in the compromise of Samba accounts.

Checks: C-29187r485429_chk

Check the group ownership of the Samba configuration file. # ls -lL /etc/sfw/private/smbpasswd If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-29175r485430_fix

Remove the extended ACL from the file. # chmod A- /etc/sfw/private/smbpasswd

The smb.conf file must use the hosts option to restrict access to Samba.

CM-6 - Medium - CCI-000366 - V-227026 - SV-227026r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006220

Vuln IDs

V-227026
V-1030

Rule IDs

SV-227026r505925_rule
SV-40298

Samba increases the attack surface of the system and must be restricted to communicate only with systems requiring access.

Checks: C-29188r485432_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-29176r485433_fix

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

Samba must be configured to use an authentication mechanism other than "share."

CM-6 - Medium - CCI-000366 - V-227027 - SV-227027r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006225

Vuln IDs

V-227027
V-22499

Rule IDs

SV-227027r505925_rule
SV-40295

Samba share authentication does not provide for individual user identification and must not be used.

Checks: C-29189r485435_chk

Check the security mode of the Samba configuration. 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: # grep -i security /etc/smb.conf /etc/sfw/smb.conf /etc/samba/smb.conf /etc/sfw/samba/smb.conf If the security mode is share, this is a finding.

Fix: F-29177r485436_fix

Edit the smb.conf file and change the security setting to user or another valid setting other than share.

Samba must be configured to use encrypted passwords.

CM-6 - Medium - CCI-000366 - V-227028 - SV-227028r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006230

Vuln IDs

V-227028
V-22500

Rule IDs

SV-227028r505925_rule
SV-40296

Samba must be configured to protect authenticators. If Samba passwords are not encrypted for storage, plain-text user passwords may be read by those with access to the Samba password file.

Checks: C-29190r485438_chk

Check the encryption setting of the Samba configuration. Procedure: # grep -i 'encrypt passwords' /etc/smb.conf /etc/sfw/smb.conf /etc/samba/smb.conf /etc/sfw/samba/smb.conf If the setting is not present, or not set to yes, this is a finding.

Fix: F-29178r485439_fix

Edit the smb.conf file and change the encrypt passwords setting to yes.

Samba must be configured to not allow guest access to shares.

CM-6 - Medium - CCI-000366 - V-227029 - SV-227029r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006235

Vuln IDs

V-227029
V-22501

Rule IDs

SV-227029r505925_rule
SV-40297

Guest access to shares permits anonymous access and is not permitted.

Checks: C-29191r485441_chk

Check the encryption setting for the Samba configuration. 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: # grep -i 'guest ok' /etc/smb.conf /etc/sfw/smb.conf /etc/samba/smb.conf /etc/sfw/samba/smb.conf If the setting exists and is set to yes, this is a finding.

Fix: F-29179r485442_fix

Edit the smb.conf file and change the guest ok setting to no.

The system must not run an Internet Network News (INN) server.

CM-7 - Medium - CCI-000381 - V-227030 - SV-227030r505925_rule

RMF Control

CM-7

Severity

CCI

Version

GEN006240

Vuln IDs

V-227030
V-1023

Rule IDs

SV-227030r505925_rule
SV-1023

Internet Network News (INN) servers access Usenet newsfeeds and store newsgroup articles. INN servers use the Network News Transfer Protocol (NNTP) to transfer information from the Usenet to the server and from the server to authorized remote hosts. If this function is necessary to support a valid mission requirement, its use must be authorized and approved in the system accreditation package.

Checks: C-29192r485444_chk

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

Fix: F-29180r485445_fix

Disable the INN server.

The /etc/news/hosts.nntp (or equivalent) must have mode 0600 or less permissive.

AC-3 - Medium - CCI-002165 - V-227031 - SV-227031r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN006260

Vuln IDs

V-227031
V-4273

Rule IDs

SV-227031r505925_rule
SV-4273

Excessive permissions on the hosts.nntp file may allow unauthorized modification which could lead to Denial-of-Service to authorized users or provide access to unauthorized users.

Checks: C-29193r485447_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-29181r485448_fix

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

The /etc/news/hosts.nntp file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-227032 - SV-227032r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006270

Vuln IDs

V-227032
V-22502

Rule IDs

SV-227032r505925_rule
SV-26835

File system extended ACLs provide access to files beyond what is allowed by the mode numbers of the files. Excessive permissions on the hosts.nntp file may allow unauthorized modification which could lead to Denial of Service to authorized users or provide access to unauthorized users.

Checks: C-29194r485450_chk

Check the permissions of the file. # ls -lL /etc/news/hosts.nntp If the permissions include a "+", the file has an extended ACL, this is a finding.

Fix: F-29182r485451_fix

Remove the extended ACL from the file. # chmod A- /etc/news/hosts.nntp

The /etc/news/hosts.nntp.nolimit (or equivalent) must have mode 0600 or less permissive.

AC-3 - Medium - CCI-002165 - V-227033 - SV-227033r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN006280

Vuln IDs

V-227033
V-4274

Rule IDs

SV-227033r505925_rule
SV-4274

Excessive permissions on the hosts.nntp.nolimit file may allow unauthorized modification which could lead to Denial-of-Service to authorized users or provide access to unauthorized users.

Checks: C-29195r485453_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-29183r485454_fix

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

The /etc/news/hosts.nntp.nolimit file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-227034 - SV-227034r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006290

Vuln IDs

V-227034
V-22503

Rule IDs

SV-227034r505925_rule
SV-26842

File system extended ACLs provide access to files beyond what is allowed by the mode numbers of the files. Excessive permissions on the hosts.nntp.nolimit file may allow unauthorized modification which could lead to Denial of Service to authorized users or provide access to unauthorized users.

Checks: C-29196r485456_chk

Check the permissions of the file. # ls -lL /etc/news/hosts.nntp.nolimit If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-29184r485457_fix

Remove the extended ACL from the file. # chmod A- /etc/news/hosts.nntp.nolimit

The /etc/news/nnrp.access (or equivalent) must have mode 0600 or less permissive.

AC-3 - Medium - CCI-002165 - V-227035 - SV-227035r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN006300

Vuln IDs

V-227035
V-4275

Rule IDs

SV-227035r505925_rule
SV-4275

Excessive permissions on the nnrp.access file may allow unauthorized modification which could lead to Denial-of-Service to authorized users or provide access to unauthorized users.

Checks: C-29197r485459_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-29185r485460_fix

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

The /etc/news/nnrp.access file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-227036 - SV-227036r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006310

Vuln IDs

V-227036
V-22504

Rule IDs

SV-227036r505925_rule
SV-26846

File system extended ACLs provide access to files beyond what is allowed by the mode numbers of the files. Excessive permissions on the nnrp.access file may allow unauthorized modification which could lead to Denial of Service to authorized users or provide access to unauthorized users.

Checks: C-29198r485462_chk

Check the permissions of the file. # ls -lL /etc/news/nnrp.access If the permissions include a "+", the file has an extended ACL and this is a finding.

Fix: F-29186r485463_fix

Remove the extended ACL from the file. # chmod A- /etc/news/nnrp.access

The /etc/news/passwd.nntp file (or equivalent) must have mode 0600 or less permissive.

AC-3 - Medium - CCI-002165 - V-227037 - SV-227037r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN006320

Vuln IDs

V-227037
V-4276

Rule IDs

SV-227037r505925_rule
SV-4276

File permissions more permissive than 0600 for /etc/news/passwd.nntp may allow access to privileged information by system intruders or malicious users.

Checks: C-29199r485465_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-29187r485466_fix

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

The /etc/news/passwd.nntp file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-227038 - SV-227038r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006330

Vuln IDs

V-227038
V-22505

Rule IDs

SV-227038r505925_rule
SV-26850

Extended ACLs may provide excessive permissions on the /etc/news/passwd.nntp file, which may permit unauthorized access or modification to the NNTP configuration.

Checks: C-29200r485468_chk

Check the permissions of the file. # ls -lL /etc/news/passwd.nntp If the permissions include a "+", the file has an extended ACL, this is a finding.

Fix: F-29188r485469_fix

Remove the extended ACL from the file. # chmod A- /etc/news/passwd.nntp

Files in /etc/news must be owned by root.

CM-6 - Medium - CCI-000366 - V-227039 - SV-227039r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006340

Vuln IDs

V-227039
V-4277

Rule IDs

SV-227039r505925_rule
SV-40487

If critical system files are not owned by a privileged user, system integrity could be compromised.

Checks: C-29201r485471_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-29189r485472_fix

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

The files in /etc/news must be group-owned by root.

CM-6 - Medium - CCI-000366 - V-227040 - SV-227040r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006360

Vuln IDs

V-227040
V-4278

Rule IDs

SV-227040r505925_rule
SV-40489

If critical system files do not have a privileged group owner, system integrity could be compromised.

Checks: C-29202r485474_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-29190r485475_fix

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

The system must not use UDP for NIS/NIS+.

CM-7 - High - CCI-000381 - V-227041 - SV-227041r505925_rule

RMF Control

CM-7

Severity

CCI

Version

GEN006380

Vuln IDs

V-227041
V-4399

Rule IDs

SV-227041r505925_rule
SV-4399

Implementing NIS or NIS+ under UDP may make the system more susceptible to a Denial of Service attack and does not provide the same quality of service as TCP.

Checks: C-29203r485477_chk

If the system does not use NIS or NIS+, this is not applicable. Check if NIS or NIS+ is implemented using UDP. Procedure: # rpcinfo -p | grep yp | grep udp If NIS or NIS+ is implemented using UDP, this is a finding.

Fix: F-29191r485478_fix

Configure the system to not use UDP for NIS and NIS+. Consult vendor documentation for the required procedure.

The Network Information System (NIS) protocol must not be used.

CM-7 - Medium - CCI-000381 - V-227042 - SV-227042r505925_rule

RMF Control

CM-7

Severity

CCI

Version

GEN006400

Vuln IDs

V-227042
V-867

Rule IDs

SV-227042r505925_rule
SV-867

Due to numerous security vulnerabilities existing within NIS, it must not be used. Possible alternative directory services are NIS+ and LDAP.

Checks: C-29204r485480_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-29192r485481_fix

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

NIS maps must be protected through hard-to-guess domain names.

CM-6 - Medium - CCI-000366 - V-227043 - SV-227043r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006420

Vuln IDs

V-227043
V-12026

Rule IDs

SV-227043r505925_rule
SV-12527

The use of hard-to-guess NIS domain names provides additional protection from unauthorized access to the NIS directory information.

Checks: C-29205r485483_chk

Check the domain name for NIS maps. Procedure: # domainname If the name returned is simple to guess, such as the organization name, building, or room name, etc., this is a finding.

Fix: F-29193r485484_fix

Change the NIS domain name to a value difficult to guess. Consult vendor documentation for the required procedure.

Any NIS+ server must be operating at security level 2.

CM-7 - Medium - CCI-000382 - V-227044 - SV-227044r505925_rule

RMF Control

CM-7

Severity

CCI

CCI-000382

Version

GEN006460

Vuln IDs

V-227044
V-926

Rule IDs

SV-227044r505925_rule
SV-28453

If the NIS+ server is not operating in, at least, security level 2, there is no encryption and the system could be penetrated by intruders and/or malicious users.

Checks: C-29206r503924_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-29194r503925_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.

The file integrity tool must be configured to verify ACLs.

SI-6 - Low - CCI-002696 - V-227045 - SV-227045r505925_rule

RMF Control

SI-6

Severity

CCI

CCI-002696

Version

GEN006570

Vuln IDs

V-227045
V-22507

Rule IDs

SV-227045r505925_rule
SV-26858

ACLs can provide permissions beyond those permitted through the file mode and must be verified by file integrity tools.

Checks: C-29207r485498_chk

If using AIDE, verify the configuration contains the acl option for all monitored files and directories. Here is an example AIDE configuration fragment. SampleRule = p+i+l+n+u+g+s+m+c+acl+xattrs+sha256 /bin SampleRule If the acl option is not present, this is a finding. If using a different file integrity tool, check the configuration per tool documentation.

Fix: F-29195r485499_fix

If using AIDE, edit the configuration and add the acl option for all monitored files and directories. If using a different file integrity tool, configure ACL checking per the tool's documentation.

The file integrity tool must be configured to verify extended attributes.

SI-6 - Low - CCI-002696 - V-227046 - SV-227046r505925_rule

RMF Control

SI-6

Severity

CCI

CCI-002696

Version

GEN006571

Vuln IDs

V-227046
V-22508

Rule IDs

SV-227046r505925_rule
SV-26860

Extended attributes in file systems are used to contain arbitrary data and file metadata with security implications.

Checks: C-29208r485501_chk

If using AIDE, verify the configuration contains the xattrs option for all monitored files and directories. Here is an example AIDE configuration fragment. SampleRule = p+i+l+n+u+g+s+m+c+acl+xattrs+sha256 /bin SampleRule If the xattrs option is not present, this is a finding. If using a different file integrity tool, check the configuration per tool documentation.

Fix: F-29196r485502_fix

If using AIDE, edit the configuration and add the xattrs option for all monitored files and directories. If using a different file integrity tool, configure extended attributes checking per the tool's documentation.

The file integrity tool must use FIPS 140-2 approved cryptographic hashes for validating file contents.

AU-9 - Low - CCI-001496 - V-227047 - SV-227047r505925_rule

RMF Control

AU-9

Severity

CCI

CCI-001496

Version

GEN006575

Vuln IDs

V-227047
V-22509

Rule IDs

SV-227047r505925_rule
SV-26861

File integrity tools often use cryptographic hashes for verifying that file contents have not been altered. These hashes must be FIPS 140-2 approved.

Checks: C-29209r485504_chk

If using AIDE, verify the configuration contains the sha256 or sha512 options for all monitored files and directories. Here is an example AIDE configuration fragment. SampleRule = p+i+l+n+u+g+s+m+c+acl+xattrs+sha256 /bin SampleRule If either the sha256 or sha512 option is not present, this is a finding. If using a different file integrity tool, check the configuration per tool documentation.

Fix: F-29197r485505_fix

If using AIDE, edit the configuration and add the sha256 or sha512 option for all monitored files and directories. If using a different file integrity tool, configure FIPS 140-2 approved cryptographic hashes per the tool's documentation.

The system's access control program must log each system access attempt.

AU-12 - Medium - CCI-000172 - V-227048 - SV-227048r505925_rule

RMF Control

AU-12

Severity

CCI

Version

GEN006600

Vuln IDs

V-227048
V-941

Rule IDs

SV-227048r505925_rule
SV-941

If access attempts are not logged, then multiple attempts to log on to the system by an unauthorized user may go undetected.

Checks: C-29210r503927_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-29198r503928_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.

The system must use a virus scan program.

CM-6 - Medium - CCI-000366 - V-227049 - SV-227049r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN006640

Vuln IDs

V-227049
V-12765

Rule IDs

SV-227049r505925_rule
SV-28461

Virus scanning software can be used to protect a system from penetration by computer viruses and to limit their spread through intermediate systems.

Checks: C-29211r485516_chk

The operator will ensure that anti-virus software is installed and operating. If the operator is unable to provide a documented configuration for an installed anti-virus software system or if not properly used, this is a finding.

Fix: F-29199r485517_fix

The operator will ensure that anti-virus software is installed and operating.

The Reliable Datagram Sockets (RDS) protocol must be disabled or not installed unless required.

CM-7 - Medium - CCI-000382 - V-227050 - SV-227050r505925_rule

RMF Control

CM-7

Severity

CCI

CCI-000382

Version

GEN007480

Vuln IDs

V-227050
V-22530

Rule IDs

SV-227050r505925_rule
SV-26894

The Reliable Datagram Sockets (RDS) protocol is a relatively new protocol developed by Oracle for communication between the nodes of a cluster. Binding this protocol to the network stack increases the attack surface of the host. Unprivileged local processes may be able to cause the system to dynamically load a protocol handler by opening a socket using the protocol. Satisfies: SRG-OS-000096, SRG-OS-000510

Checks: C-29212r485519_chk

Ask the SA if RDS is required by application software running on the system. If so, this is not applicable. Verify the RDS protocol handler is not installed. # pkginfo | grep SUNWrds If no results are returned, this is not a finding. Verify the RDS protocol handler is prevented from dynamic loading. # grep "exclude: rds" /etc/system If no result is returned, this is a finding.

Fix: F-29200r485520_fix

Remove the RDS protocol handler package. # pkgrm SUNWrds OR Prevent the RDS protocol handler from dynamic loading. # echo "exclude: rds" >> /etc/system

The Transparent Inter-Process Communication (TIPC) protocol must be disabled or not installed.

CM-7 - Medium - CCI-000382 - V-227051 - SV-227051r505925_rule

RMF Control

CM-7

Severity

CCI

CCI-000382

Version

GEN007540

Vuln IDs

V-227051
V-22533

Rule IDs

SV-227051r505925_rule
SV-26902

The Transparent Inter-Process Communication (TIPC) protocol is a relatively new cluster communications protocol developed by Ericsson. Binding this protocol to the network stack increases the attack surface of the host. Unprivileged local processes may be able to cause the kernel to dynamically load a protocol handler by opening a socket using the protocol. Satisfies: SRG-OS-000096, SRG-OS-000510

Checks: C-29213r485522_chk

Verify the TIPC protocol handler package is not installed. # pkginfo | grep SUNWtipc If the TIPC protocol handler package is not installed, this is not a finding Verify the TIPC protocol handler is prevented from dynamic loading. # grep "exclude: tipc" /etc/system If no result is returned, this is a finding.

Fix: F-29201r485523_fix

Remove the TIPC protocol handler package. # pkgrm SUNWtipc OR Prevent the TIPC protocol handler from dynamic loading. # echo "exclude: tipc" >> /etc/system

The system must not have 6to4 enabled.

CM-6 - Medium - CCI-000366 - V-227052 - SV-227052r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN007780

Vuln IDs

V-227052
V-22545

Rule IDs

SV-227052r505925_rule
SV-26921

6to4 is an IPv6 transition mechanism that involves tunneling IPv6 packets encapsulated in IPv4 packets on an ad-hoc basis. This is not a preferred transition strategy and increases the attack surface of the system.

Checks: C-29214r485525_chk

# ifconfig -a If a tunnel interface is displayed with an IPv4 tunnel source address, an IPv6 interface address, and no tunnel destination address, this is a finding.

Fix: F-29202r485526_fix

Disable the active 6to4 tunnel. # ifconfig <tunnel> down Check the /etc/hostname* files for startup configuration for the tunnel, and edit or delete as appropriate to prevent the tunnel creation on startup.

The system must not have IP tunnels configured.

CM-6 - Medium - CCI-000366 - V-227053 - SV-227053r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN007820

Vuln IDs

V-227053
V-22547

Rule IDs

SV-227053r505925_rule
SV-26927

IP tunneling mechanisms can be used to bypass network filtering.

Checks: C-29215r485528_chk

Check for any IP tunnels. # ifconfig -a | grep 'ip.*tun' If any results are returned, this is a finding.

Fix: F-29203r485529_fix

Disable the tunnels. # ifconfig <tunnel> down Remove the startup configuration for the tunnels. # rm /etc/hostname.<tunnel>

The DHCP client must be disabled if not needed.

CM-6 - Medium - CCI-000366 - V-227054 - SV-227054r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN007840

Vuln IDs

V-227054
V-22548

Rule IDs

SV-227054r505925_rule
SV-26931

DHCP allows for the unauthenticated configuration of network parameters on the system by exchanging information with a DHCP server.

Checks: C-29216r485531_chk

Verify no interface is configured to use DHCP. # ls /etc/dhcp.* If any file is found, this is a finding.

Fix: F-29204r485532_fix

Delete the DHCP client configuration. # rm /etc/dhcp.*

The system must ignore IPv6 ICMP redirect messages.

CM-6 - Medium - CCI-000366 - V-227055 - SV-227055r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN007860

Vuln IDs

V-227055
V-22550

Rule IDs

SV-227055r505925_rule
SV-26937

Checks: C-29217r485537_chk

Determine the type of zone that you are currently securing. # zonename If the zone is not the global zone, determine if any interfaces are exclusive to the zone: # dladm show-link If the output indicates "insufficient privileges" then this requirement is not applicable. If the zone is the global zone or the non-global zone has exclusive interfaces verify the system is configured to ignore IPv6 ICMP redirect messages. # ndd /dev/ip6 ip6_ignore_redirect If the returned value is not 1, this is a finding.

Fix: F-29205r485538_fix

Configure the system to ignore IPv6 ICMP redirect messages. # ndd -set /dev/ip6 ip6_ignore_redirect 1 Also add this command to a system startup script.

The system must not send IPv6 ICMP redirects.

CM-6 - Medium - CCI-000366 - V-227056 - SV-227056r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN007880

Vuln IDs

V-227056
V-22551

Rule IDs

SV-227056r505925_rule
SV-26938

Checks: C-29218r485540_chk

Determine the type of zone that you are currently securing. # zonename If the zone is not the global zone, determine if any interfaces are exclusive to the zone: # dladm show-link If the output indicates "insufficient privileges" then this requirement is not applicable. If the zone is the global zone or the non-global zone has exclusive interfaces verify the system is configured to not send IPv6 ICMP redirect messages. # ndd /dev/ip6 ip6_send_redirects If the returned value is not 0, this is a finding.

Fix: F-29206r485541_fix

Configure the system to not send IPv6 ICMP redirect messages. # ndd -set /dev/ip6 ip6_send_redirects 0 Also, add this command to a system startup script.

The system must not forward IPv6 source-routed packets.

CM-6 - Medium - CCI-000366 - V-227057 - SV-227057r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN007920

Vuln IDs

V-227057
V-22553

Rule IDs

SV-227057r505925_rule
SV-26940

Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when IPv6 forwarding is enabled and the system is functioning as a router.

Checks: C-29219r485546_chk

Determine the type of zone that you are currently securing. # zonename If the zone is not the global zone, determine if any interfaces are exclusive to the zone: # dladm show-link If the output indicates "insufficient privileges" then this requirement is not applicable. If the zone is the global zone or the non-global zone has exclusive interfaces verify the system is configured to not forward IPv6 source-routed packets. # ndd /dev/ip6 ip6_forward_src_routed If the returned value is not 0, this is a finding.

Fix: F-29207r485547_fix

Configure the system to not forward IPv6 source-routed packets. # ndd -set /dev/ip6 ip6_forward_src_routed 0 Also, add this command to a system startup script.

The system must not respond to ICMPv6 echo requests sent to a broadcast address.

CM-6 - Medium - CCI-000366 - V-227058 - SV-227058r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN007950

Vuln IDs

V-227058
V-23972

Rule IDs

SV-227058r505925_rule
SV-29785

Responding to broadcast ICMP echo requests facilitates network mapping and provides a vector for amplification attacks.

Checks: C-29220r485549_chk

Determine the type of zone that you are currently securing. # zonename If the zone is not the global zone, determine if any interfaces are exclusive to the zone: # dladm show-link If the output indicates "insufficient privileges" then this requirement is not applicable. If the zone is the global zone or the non-global zone has exclusive interfaces determine if the system is configured to ignore IPv6 multicast ICMP echo-requests. Procedure: # ndd -get /dev/ip ip6_respond_to_echo_multicast If the result is not 0, this is a finding.

Fix: F-29208r485550_fix

Configure the system to not respond to IPv6 multicast ICMP echo-requests. Procedure: # ndd -set /dev/ip ip6_respond_to_echo_multicast 0 This command must also be added to a system startup script.

If the system is using LDAP for authentication or account information, the system must use a TLS connection using FIPS 140-2 approved cryptographic algorithms.

AC-17 - Medium - CCI-001453 - V-227059 - SV-227059r505925_rule

RMF Control

AC-17

Severity

CCI

CCI-001453

Version

GEN007980

Vuln IDs

V-227059
V-22555

Rule IDs

SV-227059r505925_rule
SV-41038

LDAP can be used to provide user authentication and account information, which are vital to system security. Communication between an LDAP server and a host using LDAP requires protection. Satisfies: SRG-OS-000250, SRG-OS-000495, SRG-OS-000500

Checks: C-29221r485552_chk

Check if the system is using NSS LDAP. # grep -v '^#' /etc/nsswitch.conf | grep ldap If no lines are returned, this vulnerability is not applicable. Verify TLS is used for client authentications to the server # grep "NS_LDAP_AUTH=" /var/ldap/ldap_client_file If any of the authentication methods used do not begin with "tls:", this is a finding. Retrieve the list of LDAP servers. # grep "NS_LDAP_SERVERS=" /var/ldap/client_file Use the certutil to verify the cipher(s) used for every server. # certutil -L -n < host nickname > -d /var/ldap If any of the TLS connections do not use FIPS 140-2 approved cryptographic algorithms, this is a finding.

Fix: F-29209r485553_fix

Configure all LDAP authentications and connections to be encrypted using TLS and FIPS 140-2 approved cryptographic algorithms.

If the system is using LDAP for authentication or account information the LDAP client configuration file must have mode 0600 or less permissive.

CM-6 - Medium - CCI-000366 - V-227060 - SV-227060r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN008060

Vuln IDs

V-227060
V-22559

Rule IDs

SV-227060r505925_rule
SV-40726

LDAP can be used to provide user authentication and account information, which are vital to system security. The LDAP client configuration must be protected from unauthorized modification.

Checks: C-29222r485555_chk

Verify the permissions of the files. # ls -lL /var/ldap/ldap_client_file /var/ldap/ldap_client_cred If the mode of either file is more permissive than 0600, this is a finding.

Fix: F-29210r485556_fix

Change the permissions of the files. # chmod 0600 /var/ldap/ldap_client_file /var/ldap/ldap_client_cred

If the system is using LDAP for authentication or account information, the LDAP configuration file must be owned by root.

CM-6 - Medium - CCI-000366 - V-227061 - SV-227061r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN008080

Vuln IDs

V-227061
V-22560

Rule IDs

SV-227061r505925_rule
SV-40727

LDAP can be used to provide user authentication and account information, which are vital to system security. The LDAP client configuration must be protected from unauthorized modification.

Checks: C-29223r485558_chk

Verify the ownership of the files. # ls -lL /var/ldap/ldap_client_file /var/ldap/ldap_client_cred If the files are not owned by root, this is a finding.

Fix: F-29211r485559_fix

Change the owner of the files. # chown root /var/ldap/ldap_client_file /var/ldap/ldap_client_cred

If the system is using LDAP for authentication or account information, the LDAP configuration file must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-227062 - SV-227062r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN008100

Vuln IDs

V-227062
V-22561

Rule IDs

SV-227062r505925_rule
SV-39906

LDAP can be used to provide user authentication and account information, which are vital to system security. The LDAP client configuration must be protected from unauthorized modification.

Checks: C-29224r485561_chk

Check the group ownership of the files. Procedure: # ls -lL /var/ldap/ldap_client_file /var/ldap/ldap_client_cred If the files are not group-owned by root, bin, or sys, this is a finding.

Fix: F-29212r485562_fix

Change the group-owner of the files to root, bin, or sys. Procedure: # chgrp root /var/ldap/ldap_client_file /var/ldap/ldap_client_cred

If the system is using LDAP for authentication or account information, the /etc/ldap.conf (or equivalent) file must not have an extended ACL.

CM-6 - Medium - CCI-000366 - V-227063 - SV-227063r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN008120

Vuln IDs

V-227063
V-22562

Rule IDs

SV-227063r505925_rule
SV-40728

LDAP can be used to provide user authentication and account information, which are vital to system security. The LDAP client configuration must be protected from unauthorized modification.

Checks: C-29225r485564_chk

Verify the permissions of the files. # ls -lL /var/ldap/ldap_client_file /var/ldap/ldap_client_cred If the permissions include a "+", the files have an extended ACL, this is a finding.

Fix: F-29213r485565_fix

Remove the extended ACL from the files. # chmod A- /var/ldap/ldap_client_file /var/ldap/ldap_client_cred

If the system is using LDAP for authentication or account information, the TLS certificate authority file and/or directory (as appropriate) must be owned by root.

CM-6 - Medium - CCI-000366 - V-227064 - SV-227064r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN008140

Vuln IDs

V-227064
V-22563

Rule IDs

SV-227064r505925_rule
SV-40755

LDAP can be used to provide user authentication and account information, which are vital to system security. The LDAP client configuration must be protected from unauthorized modification.

Checks: C-29226r485567_chk

Check if the system is using NSS LDAP. # grep -v '^#' /etc/nsswitch.conf | grep ldap If no lines are returned, this vulnerability is not applicable. Verify the ownership of the certificate database files. # ls -lL /var/ldap/cert8.db /var/ldap/key3.db /var/ldap/secmod.db If the owner of any of the files is not root, this is a finding.

Fix: F-29214r485568_fix

Change the ownership of the certificate database files. # chown root /var/ldap/cert8.db /var/ldap/key3.db /var/ldap/secmod.db

If the system is using LDAP for authentication or account information, the TLS certificate authority file and/or directory (as appropriate) must be group-owned by root, bin, or sys.

CM-6 - Medium - CCI-000366 - V-227065 - SV-227065r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN008160

Vuln IDs

V-227065
V-22564

Rule IDs

SV-227065r505925_rule
SV-39907

LDAP can be used to provide user authentication and account information, which are vital to system security. The LDAP client configuration must be protected from unauthorized modification

Checks: C-29227r485570_chk

Check if the system is using NSS LDAP. # grep -v '^#' /etc/nsswitch.conf | grep ldap If no lines are returned, this vulnerability is not applicable. Verify the group ownership of the certificate database files. # ls -lL /var/ldap/cert8.db /var/ldap/key3.db /var/ldap/secmod.db If the group owner of any of the files is not root, bin, or sys, this is a finding.

Fix: F-29215r485571_fix

Change the group ownership of the certificate database files. # chgrp root /var/ldap/cert8.db /var/ldap/key3.db /var/ldap/secmod.db

If the system is using LDAP for authentication or account information, the TLS certificate authority file and/or directory (as appropriate) must have mode 0644 (0755 for directories) or less permissive.

CM-6 - Medium - CCI-000366 - V-227066 - SV-227066r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN008180

Vuln IDs

V-227066
V-22565

Rule IDs

SV-227066r505925_rule
SV-40760

LDAP can be used to provide user authentication and account information, which are vital to system security. The LDAP client configuration must be protected from unauthorized modification.

Checks: C-29228r485573_chk

Check if the system is using NSS LDAP. # grep -v '^#' /etc/nsswitch.conf | grep ldap If no lines are returned, this vulnerability is not applicable. Verify the mode of the certificate database files. # ls -lL /var/ldap/cert8.db /var/ldap/key3.db /var/ldap/secmod.db If the mode of any of the files is more permissive than 0644, this is a finding.

Fix: F-29216r485574_fix

Change the mode of the certificate database files. # chmod 0644 /var/ldap/cert8.db /var/ldap/key3.db /var/ldap/secmod.db NOTE: Some SAs may prefer to set the permissions to 0600. This is acceptable.

Automated file system mounting tools must not be enabled unless needed.

CM-6 - Low - CCI-000366 - V-227067 - SV-227067r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN008440

Vuln IDs

V-227067
V-22577

Rule IDs

SV-227067r505925_rule
SV-26965

Automated file system mounting tools may provide unprivileged users with the ability to access local media and network shares. If this access is not necessary for the system's operation, it must be disabled to reduce the risk of unauthorized access to these resources.

Checks: C-29229r503930_chk

If the autofs service is needed, this vulnerability is not applicable. Check if the autofs service is running. # svcs svc:/system/filesystem/autofs If the autofs service is online this is a finding.

Fix: F-29217r503931_fix

Stop and disable the autofs service. # svcadm disable autofs

The system must have USB disabled unless needed.

CM-6 - Low - CCI-000366 - V-227068 - SV-227068r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN008460

Vuln IDs

V-227068
V-22578

Rule IDs

SV-227068r505925_rule
SV-26968

USB is a common computer peripheral interface. USB devices may include storage devices that could be used to install malicious software on a system or exfiltrate data.

Checks: C-29230r485582_chk

If the system needs USB, this vulnerability is not applicable. Verify the SUNWusb package is installed. # pkginfo SUNWusb If the package is installed, this is a finding.

Fix: F-29218r485583_fix

Remove the SUNWusb package. # pkgrm SUNWusb

The system must have USB Mass Storage disabled unless needed.

CM-6 - Low - CCI-000366 - V-227069 - SV-227069r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN008480

Vuln IDs

V-227069
V-22579

Rule IDs

SV-227069r505925_rule
SV-26970

USB is a common computer peripheral interface. USB devices may include storage devices that could be used to install malicious software on a system or exfiltrate data.

Checks: C-29231r503933_chk

If the system needs a particular USB driver for storage, this vulnerability is not applicable. Check the current loaded kernel modules: # modinfo | grep usb_ac # modinfo | grep usb_as # modinfo | grep hid # modinfo | grep scsa2usb # modinfo | grep usbprn # modinfo | grep usbser_edge If any command produces output, this is a finding. Check the configuration of the /etc/system file: # grep 'exclude: usb_ac' /etc/system # grep 'exclude: usb_as' /etc/system # grep 'exclude: hid' /etc/system # grep 'exclude: scsa2usb' /etc/system # grep 'exclude: usbprn' /etc/system # grep 'exclude: usbser_edge' /etc/system If no results are returned from any particular command, this is a finding.

Fix: F-29219r503934_fix

Prevent the USB drivers from loading: # echo "exclude: usb_ac" >> /etc/system # echo "exclude: usb_as" >> /etc/system # echo "exclude: hid" >> /etc/system # echo "exclude: scsa2usb" >> /etc/system # echo "exclude: usbprn" >> /etc/system # echo "exclude: usbser_edge" >> /etc/system The system must be restarted for these changes to take effect.

The system must have IEEE 1394 (Firewire) disabled unless needed.

CM-6 - Low - CCI-000366 - V-227070 - SV-227070r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN008500

Vuln IDs

V-227070
V-22580

Rule IDs

SV-227070r505925_rule
SV-26972

Firewire is a common computer peripheral interface. Firewire devices may include storage devices that could be used to install malicious software on a system or exfiltrate data.

Checks: C-29232r485588_chk

If the system needs IEEE 1394 (Firewire), this is not applicable. Check if the firewire module is not disabled. # grep 'exclude: s1394' /etc/system If no results are returned, this is a finding.

Fix: F-29220r485589_fix

Disable the firewire module. # echo "exclude: s1394" >> /etc/system Reboot for the changes to take effect.

The system must employ a local firewall.

CM-6 - Medium - CCI-000366 - V-227071 - SV-227071r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN008520

Vuln IDs

V-227071
V-22582

Rule IDs

SV-227071r505925_rule
SV-26974

A local firewall protects the system from exposing unnecessary or undocumented network services to the local enclave. If a system within the enclave is compromised, firewall protection on an individual system continues to protect it from attack.

Checks: C-29233r485591_chk

Determine the zone that you are currently securing. # zonename If the command output is "global", only the "phys" and "SR-IOV" interfaces assigned to the global zone require inspection. If using a non-Global zone, all "phys" and "SR-IOV" interfaces assigned to the zone require inspection. Determine if the system is using a local firewall. # svcs network/ipfilter If the service is not online, this is a finding.

Fix: F-29221r485592_fix

Enable the system's local firewall. # svcadm enable network/ipfilter

The system's local firewall must implement a deny-all, allow-by-exception policy.

AC-17 - Medium - CCI-002314 - V-227072 - SV-227072r505925_rule

RMF Control

AC-17

Severity

CCI

CCI-002314

Version

GEN008540

Vuln IDs

V-227072
V-22583

Rule IDs

SV-227072r505925_rule
SV-26976

Checks: C-29234r485594_chk

If the system is not a global zone, this vulnerability is not applicable. Check the firewall rules for a default deny rule. # ipfstat -i An example of a default deny rule is: block in log quick on ne3 from any to any. If there is no default deny rule, this is a finding.

Fix: F-29222r485595_fix

Edit /etc/ipf/ipf.conf and add a default deny rule. Restart the ipfilter service. # svcadm restart network/ipfilter

The system must be configured to only boot from the system boot device.

CM-6 - High - CCI-000366 - V-227073 - SV-227073r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN008600

Vuln IDs

V-227073
V-1013

Rule IDs

SV-227073r505925_rule
SV-1013

The ability to boot from removable media is the same as being able to boot into single user or maintenance mode without a password. This ability could allow a malicious user to boot the system and perform changes possibly compromising or damaging the system. It could also allow the system to be used for malicious purposes by a malicious anonymous user.

Checks: C-29235r485597_chk

Determine if the system is configured to boot from devices other than the system startup media. If so, this is a finding. In most cases, this will require access to the BIOS or system controller. 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-29223r485598_fix

Configure the system to only boot from system startup media.

System BIOS or system controllers supporting password protection must have administrator accounts/passwords configured, and no others.

AC-3 - Medium - CCI-000213 - V-227074 - SV-227074r505925_rule

RMF Control

AC-3

Severity

CCI

CCI-000213

Version

GEN008620

Vuln IDs

V-227074
V-4246

Rule IDs

SV-227074r505925_rule
SV-4246

A system's BIOS or system controller handles the initial startup of a system and its configuration must be protected from unauthorized modification. When the BIOS or system controller supports the creation of user accounts or passwords, such protections must be used and accounts/passwords only assigned to system administrators. Failure to protect BIOS or system controller settings could result in Denial-of-Service or compromise of the system resulting from unauthorized configuration changes.

Checks: C-29236r485600_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-29224r485601_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.

If the system boots from removable media, it must be stored in a safe or similarly secured container.

CM-6 - High - CCI-000366 - V-227075 - SV-227075r505925_rule

RMF Control

CM-6

Severity

CCI

Version

GEN008680

Vuln IDs

V-227075
V-4255

Rule IDs

SV-227075r505925_rule
SV-4255

Storing the boot loader on removable media in an insecure location could allow a malicious user to modify the systems boot instructions or boot to an insecure operating system.

Checks: C-29237r485606_chk

Ask the SA if the system boots from removable media. If so, ask if the boot media is stored in a secure container when not in use. If it is not, this is a finding.

Fix: F-29225r485607_fix

Store the system boot media in a secure container when not in use.

The system package management tool must cryptographically verify the authenticity of software packages during installation.

CM-5 - Low - CCI-001749 - V-227076 - SV-227076r505925_rule

RMF Control

CM-5

Severity

CCI

CCI-001749

Version

GEN008800

Vuln IDs

V-227076
V-22588

Rule IDs

SV-227076r505925_rule
SV-26991

To prevent the installation of software from unauthorized sources, the system package management tool must use cryptographic algorithms to verify the packages are authentic.

Checks: C-29238r485609_chk

Verify package signature validation is not disabled. # grep "authentication=quit" /var/sadm/install/admin/default If no configuration is returned, this is a finding.

Fix: F-29226r485610_fix

Edit /var/sadm/install/admin/default and set the authentication setting to quit.

The system package management tool must not automatically obtain updates.

SI-2 - Low - CCI-001233 - V-227077 - SV-227077r505925_rule

RMF Control

SI-2

Severity

CCI

CCI-001233

Version

GEN008820

Vuln IDs

V-227077
V-22589

Rule IDs

SV-227077r505925_rule
SV-40814

System package management tools can obtain a list of updates and patches from a package repository and make this information available to the SA for review and action. Using a package repository outside of the organization's control, presents a risk that malicious packages could be introduced.

Checks: C-29239r485612_chk

Determine if the system package management tool is configured to automatically obtain updated packages using the cron or at utilities. # grep smpatch /var/spool/cron/crontabs/* /var/spool/cron/atjobs/* If smpatch is called with the add, update, or remove subcommands, this is a finding.

Fix: F-29227r485613_fix

Disable any cron or at jobs running smpatch. # crontab -e < user running smpatch > # atrm < id of at job running smpatch >

The system, if capable, must be configured to require the use of a CAC, PIV compliant hardware token, or Alternate Logon Token (ALT) for authentication.

IA-2 - Medium - CCI-000768 - V-227078 - SV-227078r505925_rule

RMF Control

IA-2

Severity

CCI

CCI-000768

Version

GEN009120

Vuln IDs

V-227078
V-24347

Rule IDs

SV-227078r505925_rule
SV-30004

In accordance with CTO 07-015 PKI authentication is required. This provides stronger, two-factor authentication than using a username/password. NOTE: The following are exempt from this, however, they must meet all password requirements and must be documented with the IAO: - Stand-alone systems. - Application Accounts. - Students or unpaid employees (such as, interns) who are not eligible to receive or not in receipt of a CAC, PIV, or ALT. - Warfighters and support personnel located at operational tactical locations conducting wartime operations that are not collocated with RAPIDS workstations to issue CAC; are not eligible for CAC or do not have the capability to use ALT. - Test systems that have an Interim Approval to Test (IATT) and provide protection via separate VPN, firewall, or security measures preventing access to network and system components from outside the protection boundary documented in the IATT.

Checks: C-29240r485615_chk

Consult vendor documentation to determine if the system is capable of CAC authentication. If it is not, this is not applicable. Interview the SA to determine if all accounts not exempted by policy are using CAC authentication. If non-exempt accounts are not using CAC authentication, this is a finding.

Fix: F-29228r485616_fix

Consult vendor documentation to determine the procedures necessary for configuring CAC authentication. Configure all accounts required by policy to use CAC authentication.

The hosts.lpd (or equivalent) file must be owned by root.

AC-3 - Medium - CCI-002165 - V-227079 - SV-227079r505925_rule

RMF Control

AC-3

Severity

CCI

Version

GEN003920

Vuln IDs

V-227079
V-828

Rule IDs

SV-227079r505925_rule
SV-37455

Failure to give ownership of the hosts.lpd file to root provides the designated owner, and possible unauthorized users, with the potential to modify the hosts.lpd file. Unauthorized modifications could disrupt access to local printers from authorized remote hosts or permit unauthorized remote access to local printers.

Checks: C-29241r485624_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-29229r485625_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

The hosts.lpd (or equivalent) must have mode 0644 or less permissive.

AC-3 - Medium - CCI-002165 - V-227080 - SV-227080r505925_rule

RMF Control

AC-3

Severity

CCI