AIX 5.3 SECURITY TECHNICAL IMPLEMENTATION GUIDE

  • Version/Release: V1R3
  • Published: 2014-10-03
  • Expand All:
  • Severity:
  • Sort:
Compare

Select any two versions of this STIG to compare the individual requirements

View

Select any old version/release of this STIG to view the previous requirements

The AIX Security Technical Implementation Guide (STIG) is published as a tool to improve the security of Department of Defense (DoD) information systems. Comments or proposed revisions to this document should be sent via email to the following address: disa.letterkenny.FSO.mbx.stig-customer-support-mailbox@mail.mil.
b
The system must require authentication upon booting into single-user and maintenance modes.
AC-3 - Medium - CCI-000213 - V-756 - SV-27039r1_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
GEN000020
Vuln IDs
  • V-756
Rule IDs
  • SV-27039r1_rule
If the system does not require a valid root password 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.System AdministratorIAIA-2, IAIA-1
Checks: C-27960r1_chk

Ensure the root account for any bootable partitions has a password assigned in the /etc/security/passwd file.

Fix: F-24305r1_fix

Assign a root account password for any bootable partition.

b
Direct logins must not be permitted to shared, default, application, or utility accounts.
IA-2 - Medium - CCI-000770 - V-760 - SV-38668r1_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000770
Version
GEN000280
Vuln IDs
  • V-760
Rule IDs
  • SV-38668r1_rule
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.System AdministratorECSC-1, IAIA-1
Checks: C-36649r1_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. # last <unix account> Shared or Application accounts can have direct login disabled by setting the rlogin parameter to false in the users stanza of the /etc/security/user file. #lsuser -a rlogin < user_id > If users log directly on to shared accounts, this is a finding.

Fix: F-31623r1_fix

Use the switch user (su) command from a named account login to access shared accounts. Maintain audit trails to identify the actual user of that account name. Document requirements and procedures for users/administrators to log into their own accounts first and then switch user (su) to the account that must be shared. Direct login to shared or application accounts can be prevented by setting the rlogin = false in the accounts stanza of the /etc/security/user file. Additional hardening of the shared/application accounts can be done with the sugroups = in the accounts stanza of the /etc/security/user file. #chuser rlogin=false < user id >

b
All accounts on the system must have unique user or account names.
IA-2 - Medium - CCI-000764 - V-761 - SV-27064r1_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000764
Version
GEN000300
Vuln IDs
  • V-761
Rule IDs
  • SV-27064r1_rule
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.System AdministratorIAIA-2, IAIA-1
Checks: C-27980r1_chk

Perform the following to ensure there are no duplicate account names: # usrck -n ALL If any duplicate account names are found, this is a finding.

Fix: F-24342r1_fix

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

b
All accounts must be assigned unique User Identification Numbers (UIDs).
IA-2 - Medium - CCI-000764 - V-762 - SV-27067r1_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000764
Version
GEN000320
Vuln IDs
  • V-762
Rule IDs
  • SV-27067r1_rule
Accounts that share 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.System AdministratorIAIA-2, IAIA-1
Checks: C-27984r1_chk

Perform the following to ensure there are no duplicate UIDs: # usrck -n ALL If any duplicate UIDs are found, this is a finding.

Fix: F-24344r1_fix

Edit user accounts to provide unique UIDs for each account.

b
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-763 - SV-38932r1_rule
RMF Control
AC-8
Severity
Medium
CCI
CCI-000048
Version
GEN000400
Vuln IDs
  • V-763
Rule IDs
  • SV-38932r1_rule
Failure to display the login banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources.System AdministratorECWM-1
Checks: C-28845r1_chk

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

Fix: F-31626r1_fix

Edit /etc/security/login.cfg and assign the herald value for the default and /dev/console stanzas to one of the DoD login banners (based on the character limitations imposed by the system). # chsec -f /etc/security/login.cfg -s default -a herald="<DoD Login Banner>" OR # vi /etc/security/login.cfg and add a herald = <DoD Login Banner> statement to the default stanza 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."

b
Successful and unsuccessful logins and logouts must be logged.
AU-2 - Medium - CCI-000126 - V-765 - SV-38935r1_rule
RMF Control
AU-2
Severity
Medium
CCI
CCI-000126
Version
GEN000440
Vuln IDs
  • V-765
Rule IDs
  • SV-38935r1_rule
Monitoring and recording successful and unsuccessful logins assists in tracking unauthorized access to the system. Without this logging, the ability to track unauthorized activity to specific user accounts may be diminished.System AdministratorECAR-1, ECAR-2, ECAR-3
Checks: C-27996r1_chk

Determine if successful logons are being logged. # last | more Determine if unsuccessful logons are being logged. # last -f /etc/security/failedlogin | more If the commands do not return successful and unsuccessful logins, this is a finding.

Fix: F-31630r1_fix

Edit /etc/syslog.conf and add local log destinations for auth.* or both auth.notice and auth.info. "auth.info /var/log/authlog" Verify service startup scripts for syslog and utmp (if present) are enabled. # vi /etc/rc.tcpip Check the syslogd service is not commented out. Refresh syslogd. #refresh -s syslogd

b
The system must disable accounts after three consecutive unsuccessful login attempts.
AC-7 - Medium - CCI-000044 - V-766 - SV-38671r1_rule
RMF Control
AC-7
Severity
Medium
CCI
CCI-000044
Version
GEN000460
Vuln IDs
  • V-766
Rule IDs
  • SV-38671r1_rule
Disabling accounts after a limited number of unsuccessful login attempts improves protection against password guessing attacks.System AdministratorECLO-1, ECLO-2
Checks: C-36678r1_chk

# /usr/sbin/lsuser -a loginretries ALL | more Check all active accounts on the system for the maximum number of tries before the system will lock the account. If a user has values set to 0 or greater then 3, this is a finding.

Fix: F-31633r1_fix

Use the chsec command to configure the number of unsuccessful logins resulting in account lockout. # chsec -f /etc/security/user -s default -a loginretries=3 # chsec -f /etc/security/user -s <user id> -a loginretries=3

b
The delay between login prompts following a failed login attempt must be at least 4 seconds.
AC-7 - Medium - CCI-000043 - V-768 - SV-38839r1_rule
RMF Control
AC-7
Severity
Medium
CCI
CCI-000043
Version
GEN000480
Vuln IDs
  • V-768
Rule IDs
  • SV-38839r1_rule
Enforcing a delay between successive failed login attempts increases protection against automated password guessing attacks.System AdministratorECLO-1, ECLO-2
Checks: C-37832r1_chk

Check the logindelay parameter. # more /etc/security/login.cfg OR #grep logindelay /etc/security/login.cfg | grep -v \* Verify the value of the logindelay variable is 4 or more in each stanza. If the value of logindelay is not 4 or more, this is a finding.

Fix: F-33091r1_fix

Use vi or the chsec command to change the login delay time period. #chsec -f /etc/security/login.cfg -s default -a logindelay=4 OR # vi /etc/security/login.cfg Add logindelay = 4 to the default stanza.

b
The root user must not own the logon session for an application requiring a continuous display.
AC-6 - Medium - CCI-000225 - V-769 - SV-769r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN000520
Vuln IDs
  • V-769
Rule IDs
  • SV-769r2_rule
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.System AdministratorPESL-1
Checks: C-229r2_chk

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

Fix: F-923r2_fix

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

c
The system must not have accounts configured with blank or null passwords.
CM-6 - High - CCI-000366 - V-770 - SV-27107r1_rule
RMF Control
CM-6
Severity
High
CCI
CCI-000366
Version
GEN000560
Vuln IDs
  • V-770
Rule IDs
  • SV-27107r1_rule
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. System AdministratorIAIA-2, IAIA-1
Checks: C-28022r1_chk

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

Fix: F-33344r1_fix

Remove or configure a password for any account with a blank password. # passwd <user id> # smitty passwd To remove an account with a blank password. # smitty rmuser

b
The root account must be the only account having an UID of 0.
CM-6 - Medium - CCI-000366 - V-773 - SV-773r2_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN000880
Vuln IDs
  • V-773
Rule IDs
  • SV-773r2_rule
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.System AdministratorIAIA-1, IAIA-2, ECLP-1
Checks: C-28053r1_chk

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

Fix: F-24403r1_fix

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

a
The root user's home directory must not be the root directory (/).
CM-6 - Low - CCI-000366 - V-774 - SV-38940r1_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GEN000900
Vuln IDs
  • V-774
Rule IDs
  • SV-38940r1_rule
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.System AdministratorECCD-2, ECCD-1
Checks: C-28062r1_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-32113r1_fix

The root home directory should be something other than / (such as /root). Procedure: # mkdir /root # chown root /root # chgrp sys /root # chmod 700 /root # cp -r /.??* /root/. Then, edit the passwd file and change the root home directory to /root. The cp -r /.??* command copies all files and subdirectories of file names that begin with "." into the new root directory, which preserves the previous root environment. Must be in the "/" directory when executing the "cp" command.

b
The root account's home directory (other than /) must have mode 0700.
AC-6 - Medium - CCI-000225 - V-775 - SV-38941r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN000920
Vuln IDs
  • V-775
Rule IDs
  • SV-38941r1_rule
Permissions greater than 0700 could allow unauthorized users access to the root home directory.System AdministratorECCD-1, ECCD-2
Checks: C-28063r1_chk

Check the mode of the root home directory. Procedure: # grep "^root" /etc/passwd | awk -F":" '{print $6}' # ls -ld &lt;root home directory&gt; 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-32119r1_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 /root.

b
The root account's executable search path must be the vendor default and must contain only absolute paths.
CM-6 - Medium - CCI-000366 - V-776 - SV-40085r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN000940
Vuln IDs
  • V-776
Rule IDs
  • SV-40085r1_rule
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 or two consecutive colons, this is interpreted as the current working directory. Entries starting with a slash (/) are absolute paths.System AdministratorECSC-1, ECCD-1, ECCD-2
Checks: C-236r2_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 starts with a character other than a slash (/), this is a finding. If directories beyond those in the vendor's default root path are present, this is a finding.

Fix: F-34156r1_fix

Edit the root user's local initialization files. Change any found PATH variable settings to the vendor's default path for the root user. Remove any empty path entries or references to relative paths. # cd <root's home directory> # vi .profile .cshrc If the bash shell is installed, edit these additional files. # vi .bashrc .bash_profile

b
The root account must not have world-writable directories in its executable search path.
CM-6 - Medium - CCI-000366 - V-777 - SV-777r2_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN000960
Vuln IDs
  • V-777
Rule IDs
  • SV-777r2_rule
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. System AdministratorECCD-2, ECCD-1
Checks: C-28064r1_chk

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

Fix: F-24415r1_fix

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

b
The system must prevent the root account from directly logging in except from the system console.
IA-2 - Medium - CCI-000770 - V-778 - SV-38683r1_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000770
Version
GEN000980
Vuln IDs
  • V-778
Rule IDs
  • SV-38683r1_rule
Limiting the root account direct logins to only system consoles protects the root account from direct unauthorized access from a non-console device.System AdministratorECSD-2, ECPA-1
Checks: C-36930r1_chk

Check the remote login ability of the root account. Procedure: # lsuser -a rlogin root If the rlogin value is not false, this is a finding.

Fix: F-32196r1_fix

The root account can be protected from non-console device logins by setting rlogin = false in the root: stanza of the /etc/security/user file. #chsec -f /etc/security/user -s root -a rlogin=false

b
Group Identifiers (GIDs) reserved for system accounts must not be assigned to non-system groups.
CM-6 - Medium - CCI-000366 - V-780 - SV-39094r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN000360
Vuln IDs
  • V-780
Rule IDs
  • SV-39094r1_rule
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.System AdministratorECSC-1
Checks: C-280r2_chk

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

Fix: F-33336r1_fix

Change the primary group GID numbers for non-system accounts with reserved primary group GIDs (those less or equal to 99 in general, or 499 for Linux). # smitty chuser

a
All Group Identifiers (GIDs) referenced in the /etc/passwd file must be defined in the /etc/group file.
CM-6 - Low - CCI-000366 - V-781 - SV-27071r1_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GEN000380
Vuln IDs
  • V-781
Rule IDs
  • SV-27071r1_rule
If a user is assigned the GID of a group that does not exist on the system, and a group with that GID is subsequently created, the user may have unintended rights to the group. System AdministratorECSC-1
Checks: C-27988r1_chk

Perform the following to ensure there are no GIDs referenced in /etc/passwd not defined in /etc/group: # usrck -n ALL If GIDs referenced in /etc/passwd are not defined in /etc/group are returned, this is a finding.

Fix: F-33340r1_fix

Add a group to the system for each GID referenced without a corresponding group. # smitty mkgroup

b
The system must have a host-based intrusion detection tool installed.
SI-4 - Medium - CCI-001259 - V-782 - SV-41526r2_rule
RMF Control
SI-4
Severity
Medium
CCI
CCI-001259
Version
GEN006480
Vuln IDs
  • V-782
Rule IDs
  • SV-41526r2_rule
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.System AdministratorECID-1
Checks: C-285r3_chk

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

Fix: F-936r3_fix

Install a host-based intrusion detection tool.

b
System security patches and updates must be installed and up-to-date.
SI-2 - Medium - CCI-001227 - V-783 - SV-27060r2_rule
RMF Control
SI-2
Severity
Medium
CCI
CCI-001227
Version
GEN000120
Vuln IDs
  • V-783
Rule IDs
  • SV-27060r2_rule
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.System AdministratorVIVM-1
Checks: C-36595r2_chk

Obtain the list of available security patches from IBM. Verify the available patches and service packs have been installed on the system. Check the currently running TL (Technology Levels and Service Packs). #oslevel -s Perform the following to obtain a list of installed patches. # /usr/sbin/instfix -i If there are security patches available and applicable for the system that have not been installed, this is a finding.

Fix: F-31604r1_fix

Use a web browser to access the vendor's support web site. Download the service packs and patches. Use SMIT to apply the updates. #smitty update_all

b
System files and directories must not have uneven access permissions.
AC-6 - Medium - CCI-000225 - V-784 - SV-784r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001140
Vuln IDs
  • V-784
Rule IDs
  • SV-784r2_rule
Discretionary access control is undermined if users, other than a file owner, have greater access permissions to system files and directories than the owner.System AdministratorECCD-2, ECCD-1
Checks: C-289r2_chk

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

Fix: F-24427r1_fix

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

b
All files and directories must have a valid owner.
CM-6 - Medium - CCI-000366 - V-785 - SV-38942r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN001160
Vuln IDs
  • V-785
Rule IDs
  • SV-38942r1_rule
Unowned files and directories may be unintentionally inherited if a user is assigned the same UID as the UID of the unowned files.System AdministratorECCD-1, ECCD-2
Checks: C-290r2_chk

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

Fix: F-32206r1_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. #chown <a-valid-user> <directory>/<file>

b
All network services daemon files must have mode 0755 or less permissive.
AC-6 - Medium - CCI-000225 - V-786 - SV-38774r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001180
Vuln IDs
  • V-786
Rule IDs
  • SV-38774r1_rule
Restricting permission on daemons will protect them from unauthorized modification and possible system compromise.System AdministratorECLP-1
Checks: C-36945r1_chk

Check the mode of network services daemons. # ls -la /usr/sbin /usr/bin If the mode of a network services daemon is more permissive than 0755, this is a finding. NOTE: Network daemons that may not reside in these directories (such as httpd or sshd) must also be checked for the correct permissions.

Fix: F-940r2_fix

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

b
System log files must have mode 0640 or less permissive.
SI-11 - Medium - CCI-001314 - V-787 - SV-787r2_rule
RMF Control
SI-11
Severity
Medium
CCI
CCI-001314
Version
GEN001260
Vuln IDs
  • V-787
Rule IDs
  • SV-787r2_rule
If the system log files are not protected, unauthorized users could change the logged data, eliminating its forensic value.System AdministratorECTP-1
Checks: C-292r2_chk

Check the mode of log files. Procedure: # ls -lL /var/log /var/log/syslog /var/adm If any of the log files have modes more permissive than 0640, this is a finding.

Fix: F-941r2_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.

b
All skeleton files (typically those in /etc/skel) must have mode 0644 or less permissive.
AC-6 - Medium - CCI-000225 - V-788 - SV-38735r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001800
Vuln IDs
  • V-788
Rule IDs
  • SV-38735r1_rule
If the skeleton files are not protected, unauthorized personnel could change user startup parameters and possibly jeopardize user files. System AdministratorECLP-1
Checks: C-37165r1_chk

Check skeleton files permissions. Procedure: # ls -l /etc/security/.profile If a skeleton file has a mode more permissive than 0644, this is a finding. Check the mkuser.sys file. The /etc/security/mkuser.sys is a script containing items used in creation of users' ~/.profile files. This script needs to be both protected from unauthorized modification, but also needs to be executable, therefore the permissions need to be at the mode of 755. #ls -l /etc/security/mkuser.sys If the mkuser.sys file has a mode more permissive than 0755, this is a finding.

Fix: F-32450r1_fix

Change the mode of skeleton files with incorrect mode. # chmod 0644 /etc/security/.profile #chmod 0755 /etc/security/mkuser.sys

b
NIS/NIS+/yp files must be owned by root, sys, or bin.
AC-6 - Medium - CCI-000225 - V-789 - SV-38775r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001320
Vuln IDs
  • V-789
Rule IDs
  • SV-38775r1_rule
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.System AdministratorECLP-1
Checks: C-36963r1_chk

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

Fix: F-35060r1_fix

Change the owner of the NIS files to root, sys, or bin. Procedure (example): # chown root < directory>/< file >

b
NIS/NIS+/yp files must be group-owned by sys, bin, other, or system.
AC-6 - Medium - CCI-000225 - V-790 - SV-38776r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001340
Vuln IDs
  • V-790
Rule IDs
  • SV-38776r1_rule
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.System AdministratorECLP-1
Checks: C-36964r1_chk

Check the group ownership of the NIS files. Procedure: # ls -lRa /var/nis /var/yp /usr/lib/nis /usr/lib/netsvc/yp If the file group owner is not sys, bin, or system, this is a finding.

Fix: F-33349r1_fix

Change the group owner of the NIS files to sys, bin, system, or other. Procedure: # chgrp system < directory>/< file >

b
The NIS/NIS+/yp files must have mode 0755 or less permissive.
AC-6 - Medium - CCI-000225 - V-791 - SV-38781r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001360
Vuln IDs
  • V-791
Rule IDs
  • SV-38781r1_rule
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.System AdministratorECLP-1
Checks: C-37004r1_chk

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

Fix: F-945r2_fix

Change the mode of NIS/NIS+/yp files to 0755 or less permissive. Procedure (example): # chmod 0755 <filename>

a
Manual page files must have mode 0644 or less permissive.
AC-6 - Low - CCI-000225 - V-792 - SV-792r2_rule
RMF Control
AC-6
Severity
Low
CCI
CCI-000225
Version
GEN001280
Vuln IDs
  • V-792
Rule IDs
  • SV-792r2_rule
If manual pages are compromised, misleading information could be inserted, causing actions that may compromise the system.System AdministratorECCD-1, ECCD-2
Checks: C-295r2_chk

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

Fix: F-946r2_fix

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

b
Library files must have mode 0755 or less permissive.
CM-5 - Medium - CCI-001499 - V-793 - SV-38943r1_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
GEN001300
Vuln IDs
  • V-793
Rule IDs
  • SV-38943r1_rule
Unauthorized access could destroy the integrity of the library files.System AdministratorDCSL-1
Checks: C-296r2_chk

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

Fix: F-32227r1_fix

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

b
All system command files must have mode 0755 or less permissive.
CM-5 - Medium - CCI-001499 - V-794 - SV-794r3_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
GEN001200
Vuln IDs
  • V-794
Rule IDs
  • SV-794r3_rule
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.Elevate to Severity Code I if any file listed is world-writable.System AdministratorECLP-1
Checks: C-298r4_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 0755, this is a finding. NOTE: Elevate to Severity Code I if any command file listed is world-writable.

Fix: F-948r2_fix

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

b
All system files, programs, and directories must be owned by a system account.
CM-5 - Medium - CCI-001499 - V-795 - SV-40783r1_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
GEN001220
Vuln IDs
  • V-795
Rule IDs
  • SV-40783r1_rule
Restricting permissions will protect the files from unauthorized modification.System AdministratorECLP-1
Checks: C-39522r1_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. For this check, the system-provided "ipsec" user is considered to be a system account.

Fix: F-949r2_fix

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

b
System files, programs, and directories must be group-owned by a system group.
CM-5 - Medium - CCI-001499 - V-796 - SV-39098r1_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
GEN001240
Vuln IDs
  • V-796
Rule IDs
  • SV-39098r1_rule
Restricting permissions will protect the files from unauthorized modification.System AdministratorECLP-1
Checks: C-39523r1_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. For this check, the system-provided "ipsec" group is also acceptable.

Fix: F-33348r1_fix

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

b
The /etc/security/passwd file must be owned by root.
AC-6 - Medium - CCI-000225 - V-797 - SV-38944r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001400
Vuln IDs
  • V-797
Rule IDs
  • SV-38944r1_rule
The /etc/security/passwd 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 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.System AdministratorECLP-1
Checks: C-28148r1_chk

Check the ownership of the /etc/security/passwd file. Procedure: # ls -lL /etc/security/passwd If the owner of this file is not root, this is a finding.

Fix: F-32285r1_fix

Change the ownership of the /etc/security/passwd file. # chown root /etc/security/passwd

b
The /etc/passwd file must have mode 0644 or less permissive.
AC-6 - Medium - CCI-000225 - V-798 - SV-798r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001380
Vuln IDs
  • V-798
Rule IDs
  • SV-798r2_rule
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.System AdministratorECLP-1
Checks: C-8016r2_chk

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

Fix: F-952r2_fix

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

b
The /etc/security/passwd file must have mode 0400.
AC-6 - Medium - CCI-000225 - V-800 - SV-38728r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001420
Vuln IDs
  • V-800
Rule IDs
  • SV-38728r1_rule
The /etc/security/passwd 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.System AdministratorECLP-1
Checks: C-37036r1_chk

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

Fix: F-32304r2_fix

Change the mode of the /etc/security/passwd file. # chmod 0400 /etc/security/passwd

b
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-000368 - V-801 - SV-801r2_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000368
Version
GEN002380
Vuln IDs
  • V-801
Rule IDs
  • SV-801r2_rule
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.trueSystem AdministratorInformation Assurance OfficerECPA-1
Checks: C-527r2_chk

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

Fix: F-955r2_fix

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

b
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-000368 - V-802 - SV-38945r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000368
Version
GEN002440
Vuln IDs
  • V-802
Rule IDs
  • SV-38945r1_rule
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.trueInformation Assurance OfficerSystem AdministratorECPA-1
Checks: C-8026r2_chk

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

Fix: F-32464r1_fix

All files with the sgid bit set will be documented in the system baseline and authorized by the Information Systems Security Officer. Locate all sgid files with the following command: #find / -perm -2000 -exec ls -lL {} \; # find / -perm -2000 -exec aclget {} \; Ensure sgid 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.

b
The system must be checked weekly for unauthorized setuid files, as well as, unauthorized modification to authorized setuid files.
CM-3 - Medium - CCI-000318 - V-803 - SV-803r2_rule
RMF Control
CM-3
Severity
Medium
CCI
CCI-000318
Version
GEN002400
Vuln IDs
  • V-803
Rule IDs
  • SV-803r2_rule
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.System AdministratorDCSL-1
Checks: C-528r2_chk

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

Fix: F-957r2_fix

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

b
The system must be checked weekly for unauthorized setgid files, as well as, unauthorized modification to authorized setgid files.
CM-3 - Medium - CCI-000318 - V-804 - SV-804r2_rule
RMF Control
CM-3
Severity
Medium
CCI
CCI-000318
Version
GEN002460
Vuln IDs
  • V-804
Rule IDs
  • SV-804r2_rule
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.System AdministratorDCSL-1
Checks: C-8027r2_chk

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

Fix: F-958r2_fix

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

b
Removable media, remote file systems, and any file system not containing approved setuid files must be mounted with the nosuid option.
AC-6 - Medium - CCI-000225 - V-805 - SV-38746r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002420
Vuln IDs
  • V-805
Rule IDs
  • SV-38746r1_rule
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 not containing approved setuid files. Executing setuid files from untrusted file systems, or file systems not containing approved setuid files, increases the opportunity for unprivileged users to attain unauthorized administrative access.System AdministratorECLP-1
Checks: C-37185r1_chk

Check /etc/filesystems and verify the nosuid mount option is used on file systems mounted from removable media, network shares, or any other file system not containing approved setuid or setgid files. Each file system stanza must contain a device special file and may additionally contain all of the following fields type = , options = , and check = . # more /etc/filesystems # lsfs If any of these files systems do not mount with the nosuid option, it is a finding.

Fix: F-32462r1_fix

Edit /etc/filesystems and add the options = nosuid to the stanza of file system mounted from removable media or network shares, and any file system not containing approved setuid or setgid files. OR Add the nosuid option with the chfs command. # chfs -a options=nosuid <filesystem>

a
The sticky bit must be set on all public directories.
CM-6 - Low - CCI-000366 - V-806 - SV-806r2_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GEN002500
Vuln IDs
  • V-806
Rule IDs
  • SV-806r2_rule
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.System AdministratorECCD-1, ECCD-2
Checks: C-30901r1_chk

Verify all world-writable directories have the sticky bit set. Procedure: # find / -type d -perm -002 ! -perm -1000 &gt; wwlist If the sticky bit is not set on a world-writable directory, this is a finding.

Fix: F-960r2_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.)

b
All public directories must be owned by root or an application account.
AC-6 - Medium - CCI-000225 - V-807 - SV-807r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002520
Vuln IDs
  • V-807
Rule IDs
  • SV-807r2_rule
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.System AdministratorECLP-1
Checks: C-8028r2_chk

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

Fix: F-961r2_fix

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

b
The system and user default umask must be 077.
CM-6 - Medium - CCI-000366 - V-808 - SV-39501r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN002560
Vuln IDs
  • V-808
Rule IDs
  • SV-39501r1_rule
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.trueIf the default umask is 000 or does not restrict the world-writable permission, this becomes a CAT I finding.System AdministratorECCD-1, ECCD-2
Checks: C-550r2_chk

Check global initialization files for the configured umask value. Procedure: # grep umask /etc/* Check local initialization files for the configured umask value. Procedure: # grep umask /userhomedirectory/.* If the system and user default umask is not 077, this is a finding. NOTE: If the default umask is 000 or allows for the creation of world-writable files, this becomes a Severity Code I (CAT I) finding.

Fix: F-962r2_fix

Edit local and global initialization files that contain "umask" and change them to use 077 instead of the current value.

b
Default system accounts must be disabled or removed.
IA-5 - Medium - CCI-000178 - V-810 - SV-38897r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000178
Version
GEN002640
Vuln IDs
  • V-810
Rule IDs
  • SV-38897r1_rule
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.System AdministratorIAAC-1
Checks: C-37188r1_chk

Determine if default system accounts (such as those for guest, sys, bin, uucp, nuucp, daemon, smtp, and lpd) have been disabled. Procedure: # lsuser -a account_locked ALL If there are any unlocked default system accounts, this is a finding.

Fix: F-24500r1_fix

Lock the default system account(s). # chuser account_locked=true <user>

b
Auditing must be implemented.
AU-12 - Medium - CCI-000169 - V-811 - SV-38946r1_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000169
Version
GEN002660
Vuln IDs
  • V-811
Rule IDs
  • SV-38946r1_rule
Without auditing, individual system accesses cannot be tracked and malicious activity cannot be detected and traced back to an individual account.System AdministratorECAR-1, ECAR-3, ECAR-2
Checks: C-28347r1_chk

Determine if auditing is enabled. # /usr/sbin/audit query | head -1 If the response Auditing On is not returned, this is a finding.

Fix: F-32465r1_fix

Use SMIT or command line to enable auditing on the system. #audit start Additionally, make sure auditing subsystem starts on system startup. #mkitab -i cron "audit:2:once:/usr/sbin/audit start 2>&1 > /dev/console"

b
System audit logs must be owned by root.
AU-9 - Medium - CCI-000162 - V-812 - SV-38900r1_rule
RMF Control
AU-9
Severity
Medium
CCI
CCI-000162
Version
GEN002680
Vuln IDs
  • V-812
Rule IDs
  • SV-38900r1_rule
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.System AdministratorECTP-1
Checks: C-37189r1_chk

Perform the following to determine the location of audit logs and then check the ownership. Procedure: # grep -p bin: /etc/security/audit/config Directories to search will be listed under the bin stanza. # ls -la &lt;audit directories&gt; If any audit log file is not owned by root, this is a finding.

Fix: F-966r2_fix

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

b
System audit logs must have mode 0640 or less permissive.
AU-9 - Medium - CCI-000163 - V-813 - SV-38904r1_rule
RMF Control
AU-9
Severity
Medium
CCI
CCI-000163
Version
GEN002700
Vuln IDs
  • V-813
Rule IDs
  • SV-38904r1_rule
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.System AdministratorECTP-1
Checks: C-37247r1_chk

Perform the following to determine the location of audit logs and then check the mode of the files. Procedure: # grep -p bin: /etc/security/audit/config Directories to search will be listed under the bin stanza. # ls -la &lt;audit directories&gt; If any audit log file has a mode more permissive than 0640, this is a finding.

Fix: F-967r2_fix

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

b
The audit system must be configured to audit failed attempts to access files and programs.
AU-2 - Medium - CCI-000126 - V-814 - SV-38850r1_rule
RMF Control
AU-2
Severity
Medium
CCI
CCI-000126
Version
GEN002720
Vuln IDs
  • V-814
Rule IDs
  • SV-38850r1_rule
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.System AdministratorECAR-3, ECAR-1, ECAR-2
Checks: C-37842r1_chk

Check the system audit configuration to determine if failed attempts to access files and programs are audited. Check system activities (events) to audit are listed in the /etc/security/audit/events file. Procedure: # more /etc/security/audit/events If the FILE_Open event is not configured, this is a finding. Check the FILE_Open audit event is defined in the audit classes' stanza classes: of the /etc/security/audit/config file. Procedure: #more /etc/security/audit/config Make note of the audit class(es) that the FILE_Open event is associated with. If the FILE_Open event is not associated with any audit classes in the classes: stanza, this is a finding. Verify the audit class is associated with the default user and all other user ids listed in the users: stanza of the /etc/security/audit/config file. Procedure: #more /etc/security/audit/config If the class(es) the FILE_Open event is(/are) not associated with the default user and all the system users in the users: stanza, this is a finding. Supplementary Information: Successful setup of AIX auditing requires several files and stanza's to be correctly configured. 1. The /etc/security/audit/events must have the system call defined. 2. The /etc/security/audit/config has 2 stanzas that need to be configured a. "classes:" stanza. Each entry in this stanza defines two things. The first is the name of a class to group the events to be audited on. The class is linked to users of the system for auditing. The second is the event(s) to be audited in this class: stanza. Example: classes: DISA_CLASS = FILE_Open, File_Unlink, FS_Rmdir b. "users:" stanza. There are two options of specifying what users audit on. The first is to explicitly spell out user names. EXAMPLE: users: root = DISA_CLASS The second is to specify a default catching all users not listed elsewhere in the users: stanza EXAMPLE users: root = DISA_CLASS default = DISA_CLASS 3. An approach to setup auditing to meet STIG requirements would be to create class stanza with all audit events that are required. The users: stanza would then be populated with the root user, any other user ids with special requirements and finally a default user. 4. The /usr/lib/security/mkuser.default file can have under the users: stanza an entry auditclasses = class(es) of events to be audited for each new user added to the system.

Fix: F-33105r1_fix

Edit /etc/security/audit/events and add the FILE_Open event to the list of audited events. Edit /etc/security/audit/config and add the FILE_Open audit event to an audit class in the classes: stanza. Edit the /etc/security/audit/config and assign the audit classes that have the FILE_Open event to the users listed in the users: stanza.

b
The audit system must be configured to audit file deletions.
AU-2 - Medium - CCI-000126 - V-815 - SV-27294r1_rule
RMF Control
AU-2
Severity
Medium
CCI
CCI-000126
Version
GEN002740
Vuln IDs
  • V-815
Rule IDs
  • SV-27294r1_rule
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. System AdministratorECAR-1, ECAR-2, ECAR-3
Checks: C-37843r1_chk

Check the system audit configuration to determine if failed attempts to access files and programs are audited. # more /etc/security/audit/events If auditing of the FILE_Unlink or FS_Rmdir events is not configured, this is a finding. If no results are returned, this is a finding. Check the FILE_Unlink and FS_Rmdir audit event(s) are defined in the audit classes' stanza classes: of the /etc/security/audit/config file. #more /etc/security/audit/config Make note of the audit class(es) that the File_Unlink and FS_Rmdir events are associated with. If the FILE_Unlink and FS_Rmdir events are not associated with any audit classes in the classes: stanza this is a finding. Verify the audit class is associated with the default user and all other user ids listed in the users: stanza of the /etc/security/audit/config file. #more /etc/security/audit/config If the class(es) that the FILE_Unlink and FS_Rmdir events are not associated with the default user and all the system users in the users: stanza, this is a finding.

Fix: F-33106r1_fix

Edit /etc/security/audit/events and add the FILE_Unlink or FS_Rmdir events to the list of audited events. Edit /etc/security/audit/config and add the FILE_Unlink and FS_Rmdir audit events to an audit class in the classes: stanza. Edit the /etc/security/audit/config and assign the audit classes containing the FILE_Unlink and FS_Rmdir events to the all users listed in the users: stanza.

b
The audit system must be configured to audit all administrative, privileged, and security actions.
CM-5 - Medium - CCI-000347 - V-816 - SV-40138r1_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-000347
Version
GEN002760
Vuln IDs
  • V-816
Rule IDs
  • SV-40138r1_rule
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.System AdministratorECAR-3, ECAR-1, ECAR-2
Checks: C-28415r1_chk

Check the auditing configuration of the system. # more /etc/security/audit/events Verify the following events are configured. ACCT_Disable, ACCT_Enable, AUD_it, BACKUP_Export, DEV_Change, DEV_Configure, DEV_Create, FILE_Chpriv, FILE_Fchpriv, FILE_Mknod, FILE_Owner, FS_Chroot, FS_Mount, FS_Umount, PASSWORD_Check, PROC_Adjtime, PROC_Kill, PROC_Privilege, PROC_Setpgid, PROC_SetUserIDs, RESTORE_Import, TCBCK_Delete, USER_Change, USER_Create, USER_Reboot, USER_Remove, and USER_SetEnv If any of these events are missing from the configuration, this is a finding. Check the ACCT_Disable, ACCT_Enable, AUD_it, BACKUP_Export, DEV_Change, DEV_Configure, DEV_Create, FILE_Chpriv, FILE_Fchpriv, FILE_Mknod, FILE_Owner, FS_Chroot, FS_Mount, FS_Umount, PASSWORD_Check, PROC_Adjtime, PROC_Kill, PROC_Privilege, PROC_Setpgid, PROC_SetUserIDs, RESTORE_Import, TCBCK_Delete, USER_Change, USER_Create, USER_Reboot, USER_Remove, and USER_SetEnv audit events are defined in the audit classes' stanza 'classes:' of the /etc/security/audit/config file. #more /etc/security/audit/config Make note of the audit class(es) that the ACCT_Disable, ACCT_Enable, AUD_it, BACKUP_Export, DEV_Change, DEV_Configure, DEV_Create, FILE_Chpriv, FILE_Fchpriv, FILE_Mknod, FILE_Owner, FS_Chroot, FS_Mount, FS_Umount, PASSWORD_Check, PROC_Adjtime, PROC_Kill, PROC_Privilege, PROC_Setpgid, PROC_SetUserIDs, RESTORE_Import, TCBCK_Delete, USER_Change, USER_Create, USER_Reboot, USER_Remove, and USER_SetEnv events are associated with. If the ACCT_Disable, ACCT_Enable, AUD_it, BACKUP_Export, DEV_Change, DEV_Configure, DEV_Create, FILE_Chpriv, FILE_Fchpriv, FILE_Mknod, FILE_Owner, FS_Chroot, FS_Mount, FS_Umount, PASSWORD_Check, PROC_Adjtime, PROC_Kill, PROC_Privilege, PROC_Setpgid, PROC_SetUserIDs, RESTORE_Import, TCBCK_Delete, USER_Change, USER_Create, USER_Reboot, USER_Remove, and USER_SetEnv events are not associated with any audit classes in the classes: stanza, this is a finding. Verify the audit class is associated with the default user and all other user ids listed in the users: stanza of the /etc/security/audit/config file. #more /etc/security/audit/config If the class(es) that the ACCT_Disable, ACCT_Enable, AUD_it, BACKUP_Export, DEV_Change, DEV_Configure, DEV_Create, FILE_Chpriv, FILE_Fchpriv, FILE_Mknod, FILE_Owner, FS_Chroot, FS_Mount, FS_Umount, PASSWORD_Check, PROC_Adjtime,PROC_Kill, PROC_Privilege, PROC_Setpgid, PROC_SetUserIds, RESTORE_Import, TCBCK_Delete, USER_Change, USER_Create, USER_Reboot, USER_Remove, and USER_SetEnv events are not associated with the default user and all the system users in the 'users:' stanza, this is a finding.

Fix: F-24542r1_fix

Edit /etc/security/audit/events and add the following events to the list of audited events: ACCT_Disable, ACCT_Enable, AUD_it, BACKUP_Export, DEV_Change, DEV_Configure, DEV_Create, FILE_Chpriv, FILE_Fchpriv, FILE_Mknod, FILE_Owner, FS_Chroot, FS_Mount, FS_Umount, PASSWORD_Check, PROC_Adjtime, PROC_Kill, PROC_Privilege, PROC_Setpgid, PROC_SetUserIDs, RESTORE_Import, TCBCK_Delete, USER_Change, USER_Create, USER_Reboot, USER_Remove, and USER_SetEnv. Edit /etc/security/audit/config and add the ACCT_Disable, ACCT_Enable, AUD_it, BACKUP_Export, DEV_Change, DEV_Configure, DEV_Create, FILE_Chpriv, FILE_Fchpriv, FILE_Mknod, FILE_Owner, FS_Chroot, FS_Mount, FS_Umount, PASSWORD_Check, PROC_Adjtime, PROC_Kill, PROC_Privilege, PROC_Setpgid, PROC_SetUserIDs, RESTORE_Import, TCBCK_Delete, USER_Change, USER_Create, USER_Reboot, USER_Remove, and USER_SetEnv audit events to an audit class in the classes: stanza. Edit the /etc/security/audit/config and assign the audit classes with the ACCT_Disable, ACCT_Enable, AUD_it, BACKUP_Export, DEV_Change, DEV_Configure, DEV_Create, FILE_Chpriv, FILE_Fchpriv, FILE_Mknod, FILE_Owner, FS_Chroot, FS_Mount, FS_Umount, PASSWORD_Check, PROC_Adjtime, PROC_Kill, PROC_Privilege, PROC_Setpgid, PROC_SetUserIDs, RESTORE_Import, TCBCK_Delete, USER_Change, USER_Create, USER_Reboot, USER_Remove, and USER_SetEnv events to the all users listed in the users: stanza.

b
The audit system must be configured to audit login, logout, and session initiation.
AU-2 - Medium - CCI-000126 - V-818 - SV-38856r1_rule
RMF Control
AU-2
Severity
Medium
CCI
CCI-000126
Version
GEN002800
Vuln IDs
  • V-818
Rule IDs
  • SV-38856r1_rule
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.System AdministratorECAR-2, ECAR-3, ECAR-1
Checks: C-37848r1_chk

Check the system's audit configuration. # more /etc/security/audit/events Confirm the following events are configured: USER_Login, USER_Logout, INIT_Start, INIT_End and USER_SU. If any of these events are not present, this is a finding. Check the USER_Login, USER_Logout, INIT_Start, INIT_End, and USER_SU audit events are defined in the audit classes' stanza 'classes:' of the /etc/security/audit/config file. #more /etc/security/audit/config Make note of the audit class(es) the USER_Login, USER_Logout, INIT_Start, INIT_End, and USER_SU events are associated with. If the USER_Login, USER_Logout, INIT_Start, INIT_End, and USER_SU events are not associated with any audit classes in the classes: stanza, this is a finding. Verify the audit class is associated with the default user and all other user ids listed in the users: stanza of the /etc/security/audit/config file. #more /etc/security/audit/config If the class(es) the USER_Login, USER_Logout, INIT_Start, INIT_End, and USER_SU events are not associated with the default user and all the system users in the users: stanza, this is a finding.

Fix: F-33111r1_fix

Edit /etc/security/audit/events and add the USER_Login, USER_Logout, INIT_Start, INIT_End, and USER_SU events to the list of audited events. Edit /etc/security/audit/config and add the USER_Login, USER_Logout, INIT_Start, INIT_End, and USER_SU audit events to an audit class in the classes: stanza. Edit the /etc/security/audit/config and assign the audit classes with the USER_Login, USER_Logout, INIT_Start, INIT_End, and USER_SU events to the all users listed in the users: stanza.

b
The audit system must be configured to audit all discretionary access control permission modifications.
AU-2 - Medium - CCI-000126 - V-819 - SV-38857r1_rule
RMF Control
AU-2
Severity
Medium
CCI
CCI-000126
Version
GEN002820
Vuln IDs
  • V-819
Rule IDs
  • SV-38857r1_rule
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.System AdministratorECAR-1, ECAR-3, ECAR-2
Checks: C-37849r1_chk

Check the system's audit configuration. # more /etc/security/audit/events Confirm the following events are configured: FILE_Acl, FILE_Fchmod, FILE_Fchown, FILE_Mode, and FILE_Owner. If any of these events are not configured, this is a finding. Check the FILE_Acl, FILE_Fchmod, FILE_Fchown, FILE_Mode, and FILE_Owner audit events are defined in the audit classes' stanza classes: of the /etc/security/audit/config file. #more /etc/security/audit/config Make note of the audit class(es) the FILE_Acl, FILE_Fchmod, FILE_Fchown, FILE_Mode, and FILE_Owner events are associated with. If the FILE_Acl, FILE_Fchmod, FILE_Fchown, FILE_Mode, and FILE_Owner events are not associated with any audit classes in the classes: stanza, this is a finding. Verify the audit class is associated with the default user and all other user ids listed in the users: stanza of the /etc/security/audit/config file. If the class(es) the FILE_Acl, FILE_Fchmod, FILE_Fchown, FILE_Mode, and FILE_Owner events are not associated with the default user and all the system users in the users: stanza, this is a finding.

Fix: F-33112r1_fix

Edit /etc/security/audit/events and add the FILE_Acl, FILE_Fchmod, FILE_Fchown, FILE_Mode, and FILE_Owner events to the list of audited events. Edit /etc/security/audit/config and add the FILE_Acl, FILE_Fchmod, FILE_Fchown, FILE_Mode, and FILE_Owner audit events to an audit class in the classes: stanza. Edit the /etc/security/audit/config and assign the audit classes with the FILE_Acl, FILE_Fchmod, FILE_Fchown, FILE_Mode, and FILE_Owner events to the all users listed in the users: stanza.

b
The inetd.conf file, xinetd.conf file, and the xinetd.d directory must be owned by root or bin.
AC-6 - Medium - CCI-000225 - V-821 - SV-821r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003720
Vuln IDs
  • V-821
Rule IDs
  • SV-821r2_rule
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.System AdministratorECLP-1
Checks: C-567r2_chk

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

Fix: F-975r2_fix

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

b
The inetd.conf and xinetd.conf files must have mode 0440 or less permissive.
AC-6 - Medium - CCI-000225 - V-822 - SV-822r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003740
Vuln IDs
  • V-822
Rule IDs
  • SV-822r2_rule
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.System AdministratorECLP-1
Checks: C-8029r2_chk

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

Fix: F-976r2_fix

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

b
The services file must be owned by root or bin.
AC-6 - Medium - CCI-000225 - V-823 - SV-823r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003760
Vuln IDs
  • V-823
Rule IDs
  • SV-823r2_rule
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.System AdministratorECLP-1
Checks: C-28612r1_chk

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

Fix: F-977r2_fix

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

b
The services file must have mode 0444 or less permissive.
AC-6 - Medium - CCI-000225 - V-824 - SV-824r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003780
Vuln IDs
  • V-824
Rule IDs
  • SV-824r2_rule
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.System AdministratorECLP-1
Checks: C-8030r2_chk

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

Fix: F-978r2_fix

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

a
Global initialization files must contain the mesg -n or mesg n commands.
CM-6 - Low - CCI-000366 - V-825 - SV-38893r1_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GEN001780
Vuln IDs
  • V-825
Rule IDs
  • SV-38893r1_rule
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.System AdministratorECSC-1
Checks: C-37164r1_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/security/.profile /etc/csh.login /etc/csh.cshrc If no global initialization files contain mesg -n or mesg n, this is a finding.

Fix: F-979r2_fix

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

b
The hosts.lpd file (or equivalent) must not contain a "+" character.
CM-6 - Medium - CCI-000366 - V-827 - SV-38883r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN003900
Vuln IDs
  • V-827
Rule IDs
  • SV-38883r1_rule
Having the "+" character in the hosts.lpd (or equivalent) file allows all hosts to use local system print resources.System AdministratorECCD-2, ECCD-1
Checks: C-37885r1_chk

Look for the presence of a print service configuration file. Procedure: # find /etc -name hosts.lpd -print # find /etc -name Systems -print # find /etc -name printers.conf If none of the files are found, this check should be marked not applicable. Otherwise, examine the configuration file. Procedure: # more &lt;print service file&gt; Check for entries containing a "+" character by itself on any line. If any are found, this is a finding.

Fix: F-33132r1_fix

Remove the "+" entries from the hosts.lpd (or equivalent) file.

b
The hosts.lpd (or equivalent) file must be owned by root, bin, sys, or lp.
AC-6 - Medium - CCI-000225 - V-828 - SV-828r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003920
Vuln IDs
  • V-828
Rule IDs
  • SV-828r2_rule
Failure to give ownership of the hosts.lpd file to root, bin, sys, or lp 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.System AdministratorECLP-1
Checks: C-612r2_chk

Locate any print service configuration file on the system. Consult vendor documentation to verify the names and locations of print service configuration files on the system. Procedure: # find /etc -name hosts.lpd -print # find /etc -name Systems -print If no print service configuration file is found, this is not applicable. Check the ownership of the print service configuration file(s). Procedure: # ls -lL &lt;print service file&gt; If the owner of the file is not root, sys, bin, or lp, this is a finding.

Fix: F-982r2_fix

Change the owner of the /etc/hosts.lpd file (or equivalent, such as /etc/lp/Systems) to root, lp, or another privileged UID. Consult vendor documentation to determine the name and location of print service configuration files. Procedure: # chown root /etc/hosts.lpd

b
The hosts.lpd (or equivalent) must have mode 0644 or less permissive.
AC-6 - Medium - CCI-000225 - V-829 - SV-829r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003940
Vuln IDs
  • V-829
Rule IDs
  • SV-829r2_rule
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.System AdministratorECLP-1
Checks: C-8031r2_chk

Locate any print service configuration file on the system. Consult vendor documentation for the name and location of print service configuration files. Procedure: # find /etc -name hosts.lpd -print # find /etc -name Systems -print If no print service configuration file is found, this is not applicable. Check the mode of the print service configuration file. Procedure: # ls -lL &lt;print service file&gt; If the mode of the print service configuration file is more permissive than 0644, this is a finding.

Fix: F-983r2_fix

Change the mode of the /etc/hosts.lpd file (or equivalent, such as /etc/lp/Systems) to 0644 or less permissive. Consult vendor documentation for the name and location of print service configuration files. Procedure: # chmod 0644 /etc/hosts.lpd

b
The alias file must be owned by root.
AC-6 - Medium - CCI-000225 - V-831 - SV-40836r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN004360
Vuln IDs
  • V-831
Rule IDs
  • SV-40836r1_rule
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.System AdministratorECLP-1
Checks: C-39548r1_chk

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

Fix: F-985r2_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

b
The alias file must have mode 0644 or less permissive.
AC-6 - Medium - CCI-000225 - V-832 - SV-40684r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN004380
Vuln IDs
  • V-832
Rule IDs
  • SV-40684r1_rule
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.System AdministratorECLP-1
Checks: C-39414r1_chk

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

Fix: F-34539r1_fix

Change the mode of the /etc/mail/aliases file. Procedure: # chmod 0644 /etc/mail/aliases

c
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-6 - High - CCI-000225 - V-833 - SV-39506r1_rule
RMF Control
AC-6
Severity
High
CCI
CCI-000225
Version
GEN004400
Vuln IDs
  • V-833
Rule IDs
  • SV-39506r1_rule
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.System AdministratorECLP-1
Checks: C-615r2_chk

Find the aliases file on the system. Procedure: # find / -name aliases -depth -print # more &lt; aliases file location &gt; Examine the aliases file for any directories or paths that may be utilized. Procedure: # ls -lL &lt; path &gt; Check if the file or parent directory is owned by root. If not, this is a finding.

Fix: F-987r2_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

b
Files executed through a mail aliases file must have mode 0755 or less permissive.
AC-6 - Medium - CCI-000225 - V-834 - SV-834r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN004420
Vuln IDs
  • V-834
Rule IDs
  • SV-834r2_rule
If a file executed through a mail alias file has permissions greater than 0755, it can be modified by an unauthorized user and may contain malicious code or instructions possibly compromising the system.System AdministratorECLP-1
Checks: C-8033r2_chk

Find the aliases file on the system. Procedure: # find / -name aliases -depth -print Examine the aliases file for any directories or paths that may be utilized. Procedure: # more &lt;aliases file location&gt; Check the permissions for any paths referenced. Procedure: # ls -lL &lt;path&gt; If any file referenced from the aliases file has a mode more permissive than 0755, this is a finding.

Fix: F-988r2_fix

Use the chmod command to change the access permissions for files executed from the alias file. For example: # chmod 0755 < filename >

a
Sendmail logging must not be set to less than nine in the sendmail.cf file.
CM-6 - Low - CCI-000366 - V-835 - SV-38916r1_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GEN004440
Vuln IDs
  • V-835
Rule IDs
  • SV-38916r1_rule
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.System AdministratorECAR-2, ECAR-3, ECAR-1
Checks: C-616r2_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-989r2_fix

Edit the sendmail.conf file, locate the "O L" or LogLevel entry and change it to 9.

b
The system syslog service must log informational and more severe SMTP service messages.
AU-2 - Medium - CCI-000126 - V-836 - SV-39155r1_rule
RMF Control
AU-2
Severity
Medium
CCI
CCI-000126
Version
GEN004460
Vuln IDs
  • V-836
Rule IDs
  • SV-39155r1_rule
If informational and more severe SMTP service messages are not logged, malicious activity on the system may go unnoticed.System AdministratorECSC-1, ECAR-1, ECAR-2, ECAR-3
Checks: C-38139r1_chk

Check the syslog configuration file for mail.crit logging configuration. The syslog.conf file critical mail logging option line will typically appear as one of the following examples: mail.crit /var/log/syslog *.crit /var/log/syslog mail.* /var/log/syslog Procedure: # more /etc/syslog.conf If syslog is not configured to log critical Sendmail messages, this is a finding.

Fix: F-33411r1_fix

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

b
The SMTP service log file must be owned by root.
AC-6 - Medium - CCI-000225 - V-837 - SV-837r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN004480
Vuln IDs
  • V-837
Rule IDs
  • SV-837r2_rule
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.System AdministratorECLP-1
Checks: C-8034r2_chk

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

Fix: F-991r2_fix

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

b
The SMTP service log file must have mode 0644 or less permissive.
AC-6 - Medium - CCI-000225 - V-838 - SV-838r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN004500
Vuln IDs
  • V-838
Rule IDs
  • SV-838r2_rule
If the SMTP service log file is more permissive than 0644, unauthorized users may be allowed to change the log file.System AdministratorECLP-1
Checks: C-8035r2_chk

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

Fix: F-992r2_fix

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

b
The ftpusers file must exist.
AC-6 - Medium - CCI-000225 - V-840 - SV-28403r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN004880
Vuln IDs
  • V-840
Rule IDs
  • SV-28403r1_rule
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. System AdministratorECCD-2, ECCD-1
Checks: C-28645r1_chk

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

Fix: F-25674r1_fix

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

b
The ftpusers file must contain account names not allowed to use FTP.
AC-6 - Medium - CCI-000225 - V-841 - SV-28406r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN004900
Vuln IDs
  • V-841
Rule IDs
  • SV-28406r1_rule
The ftpusers file contains a list of accounts 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.System AdministratorECCD-1, ECCD-2
Checks: C-28656r1_chk

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

Fix: F-25682r1_fix

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

b
The ftpusers file must be owned by root.
AC-6 - Medium - CCI-000225 - V-842 - SV-28409r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN004920
Vuln IDs
  • V-842
Rule IDs
  • SV-28409r1_rule
If the file ftpusers is not owned by root, an unauthorized user may modify the file to allow unauthorized accounts to use FTP. System AdministratorECLP-1
Checks: C-28664r1_chk

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

Fix: F-25694r1_fix

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

b
The ftpusers file must have mode 0640 or less permissive.
AC-6 - Medium - CCI-000225 - V-843 - SV-28412r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN004940
Vuln IDs
  • V-843
Rule IDs
  • SV-28412r1_rule
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.System AdministratorECLP-1
Checks: C-28668r1_chk

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

Fix: F-25697r1_fix

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

a
The FTP daemon must be configured for logging or verbose mode.
AU-3 - Low - CCI-000130 - V-845 - SV-38991r1_rule
RMF Control
AU-3
Severity
Low
CCI
CCI-000130
Version
GEN004980
Vuln IDs
  • V-845
Rule IDs
  • SV-38991r1_rule
The -l option allows logging of connections. 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.System AdministratorECAR-2, ECAR-3, ECAR-1
Checks: C-37953r1_chk

Perform: # grep ftpd /etc/inetd.conf, Check the line for ftpd to check if the -l argument. If the ftpd is invoked without the -l argument, this is a finding. Check the /etc/syslog.conf file for daemon.info or *.info. # more /etc/syslog.conf If daemon.info or *.info is not being logged, this is a finding.

Fix: F-33206r1_fix

Edit the /etc/inetd.conf file and add the -l argument to the ftpd service line. # vi /etc/inetd.conf Restart inetd.conf # refresh -s inetd Add daemon.info or *.info to the /etc/syslog.conf file. #vi /etc/syslog.conf *.info /var/log/syslog Restart the syslog daemon. # refresh -s syslogd

b
Anonymous FTP must not be active on the system unless authorized.
AC-22 - Medium - CCI-001475 - V-846 - SV-40086r1_rule
RMF Control
AC-22
Severity
Medium
CCI
CCI-001475
Version
GEN004820
Vuln IDs
  • V-846
Rule IDs
  • SV-40086r1_rule
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.trueInformation Assurance OfficerSystem AdministratorECSC-1
Checks: C-711r2_chk

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

Fix: F-34157r1_fix

Remove user "anonymous" from /etc/passwd.

c
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-847 - SV-28420r1_rule
RMF Control
CM-6
Severity
High
CCI
CCI-000366
Version
GEN005080
Vuln IDs
  • V-847
Rule IDs
  • SV-28420r1_rule
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. System AdministratorECSC-1
Checks: C-28685r2_chk

If the system is not running tftp, this is not applicable. Determine if tftpd is running in secure mode. # more /etc/tftpaccess.ctl If the file does not exist, this is a finding. If the file does not contain an entry restricting access to the tftp user home directory, this is a finding. If other configuration is in the file, this is a finding.

Fix: F-25711r1_fix

Edit /etc/tftpaccess.ctl to only contain an entry restricting access to the tftp user home directory.

c
The TFTP daemon must have mode 0755 or less permissive.
AC-6 - High - CCI-000225 - V-848 - SV-848r2_rule
RMF Control
AC-6
Severity
High
CCI
CCI-000225
Version
GEN005100
Vuln IDs
  • V-848
Rule IDs
  • SV-848r2_rule
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.System AdministratorECPA-1
Checks: C-714r2_chk

Check the mode of the TFTP daemon. Procedure: # find / -name "*tftpd" -print # ls -lL &lt;file location&gt; If the mode of the file is more permissive than 0755, this is a finding.

Fix: F-1002r2_fix

Change the mode of the TFTP daemon. Procedure: # chmod 0755 <tftp server>

b
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.
AC-6 - Medium - CCI-000225 - V-849 - SV-849r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN005120
Vuln IDs
  • V-849
Rule IDs
  • SV-849r2_rule
If TFTP has a valid shell, it increases the likelihood of someone logging to the TFTP account and compromising the system.System AdministratorECSC-1
Checks: C-715r2_chk

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

Fix: F-1003r2_fix

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

b
Any X Windows host must write .Xauthority files.
CM-2 - Medium - CCI-000297 - V-850 - SV-850r2_rule
RMF Control
CM-2
Severity
Medium
CCI
CCI-000297
Version
GEN005160
Vuln IDs
  • V-850
Rule IDs
  • SV-850r2_rule
.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.System AdministratorECCD-1, ECCD-2
Checks: C-718r2_chk

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

Fix: F-1004r2_fix

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

b
The Network Information System (NIS) protocol must not be used.
AC-17 - Medium - CCI-001435 - V-867 - SV-867r2_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-001435
Version
GEN006400
Vuln IDs
  • V-867
Rule IDs
  • SV-867r2_rule
Due to numerous security vulnerabilities existing within NIS, it must not be used. Possible alternative directory services are NIS+ and LDAP.System AdministratorInformation Assurance OfficerECSC-1
Checks: C-851r2_chk

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

Fix: F-1021r2_fix

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

a
All interactive users must be assigned a home directory in the /etc/passwd file.
AC-6 - Low - CCI-000225 - V-899 - SV-27186r1_rule
RMF Control
AC-6
Severity
Low
CCI
CCI-000225
Version
GEN001440
Vuln IDs
  • V-899
Rule IDs
  • SV-27186r1_rule
If users do not have a valid home directory, there is no place for the storage and control of files they own.System AdministratorECSC-1
Checks: C-28161r1_chk

Use usrck to verify home directory assignments are present. Procedure: # usrck -n ALL If any user is not assigned a home directory, this is a finding.

Fix: F-1053r3_fix

Assign a home directory to any user without one.

a
All interactive user home directories defined in the /etc/passwd file must exist.
AC-6 - Low - CCI-000225 - V-900 - SV-27194r1_rule
RMF Control
AC-6
Severity
Low
CCI
CCI-000225
Version
GEN001460
Vuln IDs
  • V-900
Rule IDs
  • SV-27194r1_rule
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.System AdministratorECSC-1
Checks: C-28170r1_chk

Use pwck to check that assigned home directories exist. Procedure: # usrck -n ALL If any user's assigned home directory does not exist, this is a finding.

Fix: F-1054r2_fix

If a user has no home directory, determine why. If possible, delete accounts with no home directory. If the account is valid, then create the home directory using the appropriate system administration utility or manually create, i.e., mkdir <directory name>; copy the skeleton files into the directory; chown <user name> <directory name> for the new directory and the skeleton files. Document all changes.

b
All users' home directories must have mode 0750 or less permissive.
AC-6 - Medium - CCI-000225 - V-901 - SV-901r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001480
Vuln IDs
  • V-901
Rule IDs
  • SV-901r2_rule
Excessive permissions on home directories allow unauthorized access to user's files.System AdministratorECLP-1
Checks: C-8017r3_chk

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

Fix: F-1055r2_fix

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

b
All interactive users' home directories must be owned by their respective users.
AC-6 - Medium - CCI-000225 - V-902 - SV-902r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001500
Vuln IDs
  • V-902
Rule IDs
  • SV-902r2_rule
If users do not own their home directories, unauthorized users could access user files.System AdministratorECLP-1
Checks: C-8018r2_chk

Check the ownership of each user's home directory listed in the /etc/passwd file. Procedure: # ls -lLd &lt;user home directory&gt; If any user's home directory is not owned by the assigned user, this is a finding.

Fix: F-1056r2_fix

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

b
All interactive users' home directories must be group-owned by the home directory owner's primary group.
AC-6 - Medium - CCI-000225 - V-903 - SV-903r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001520
Vuln IDs
  • V-903
Rule IDs
  • SV-903r2_rule
If the GID of the home directory is not the same as the GID of the user, this would allow unauthorized access to files.System AdministratorECLP-1
Checks: C-8019r3_chk

Check the group ownership for each user in the /etc/passwd file. Procedure: # ls -lLd &lt;user home directory&gt; If any user's home directory is not group-owned by the assigned user's primary group, this is a finding. Home directories for application accounts requiring different group ownership must be documented using site-defined procedures.

Fix: F-1057r3_fix

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

b
All local initialization files must be owned by the user or root.
AC-6 - Medium - CCI-000225 - V-904 - SV-904r3_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001860
Vuln IDs
  • V-904
Rule IDs
  • SV-904r3_rule
Local initialization files are used to configure the user's shell environment upon login. Malicious modification of these files could compromise accounts upon logon.System AdministratorECLP-1
Checks: C-395r4_chk

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

Fix: F-1058r3_fix

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

b
All local initialization files must have mode 0740 or less permissive.
AC-6 - Medium - CCI-000225 - V-905 - SV-905r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001880
Vuln IDs
  • V-905
Rule IDs
  • SV-905r2_rule
Local initialization files are used to configure the user's shell environment upon login. Malicious modification of these files could compromise accounts upon logon.System AdministratorECLP-1
Checks: C-8020r2_chk

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

Fix: F-1059r3_fix

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

b
All run control scripts must have mode 0755 or less permissive.
AC-6 - Medium - CCI-000225 - V-906 - SV-38732r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001580
Vuln IDs
  • V-906
Rule IDs
  • SV-38732r1_rule
If the startup files are writable by other users, they could modify the startup files to insert malicious commands into the startup files.System AdministratorECLP-1
Checks: C-37149r1_chk

Check run control script modes. # cd /etc # find rc* -ls If any run control script has a mode more permissive than 0755, this is a finding.

Fix: F-32414r1_fix

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

b
Run control scripts' executable search paths must contain only absolute paths.
CM-6 - Medium - CCI-000366 - V-907 - SV-41074r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN001600
Vuln IDs
  • V-907
Rule IDs
  • SV-41074r1_rule
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, or two consecutive colons, this is interpreted as the current working directory. Paths starting with a slash (/) are absolute paths.System AdministratorECCD-1, ECCD-2
Checks: C-39526r1_chk

Verify run control scripts' library search paths. Procedure: # grep -r PATH /etc/rc* 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 (/), this is a relative path, and this is a finding.

Fix: F-1061r2_fix

Edit the run control script and remove the relative path entry from the executable search path variable.

c
Run control scripts must not execute world-writable programs or scripts.
AC-6 - High - CCI-000225 - V-910 - SV-910r2_rule
RMF Control
AC-6
Severity
High
CCI
CCI-000225
Version
GEN001640
Vuln IDs
  • V-910
Rule IDs
  • SV-910r2_rule
World-writable files could be modified accidentally or maliciously to compromise system integrity.System AdministratorECCD-2, ECCD-1
Checks: C-402r8_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 " " Create a list of world writeable files. # find / -perm -002 -type f &gt;&gt; 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 "` If any system startup script executes any file or script that is world-writable, this is a finding.

Fix: F-1064r2_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>

b
There must be no .netrc files on the system.
IA-5 - Medium - CCI-000196 - V-913 - SV-913r2_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000196
Version
GEN002000
Vuln IDs
  • V-913
Rule IDs
  • SV-913r2_rule
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.System AdministratorECCD-1, IAIA-1, IAIA-2, ECCD-2
Checks: C-404r2_chk

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

Fix: F-1067r3_fix

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

a
All files and directories contained in interactive user's home directories must be owned by the home directory's owner.
AC-6 - Low - CCI-000225 - V-914 - SV-914r2_rule
RMF Control
AC-6
Severity
Low
CCI
CCI-000225
Version
GEN001540
Vuln IDs
  • V-914
Rule IDs
  • SV-914r2_rule
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.trueSystem AdministratorInformation Assurance OfficerECCD-2, ECCD-1
Checks: C-405r3_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. Procedure: # find /&lt;usershomedirectory&gt; ! -fstype nfs ! -user &lt;username&gt; ! \( -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 ls -ld {} \; If user's home directories contain files or directories not owned by the home directory owner, this is a finding.

Fix: F-1068r2_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> {} \;

a
All files and directories contained in user's home directories must have mode 0750 or less permissive.
AC-6 - Low - CCI-000225 - V-915 - SV-915r2_rule
RMF Control
AC-6
Severity
Low
CCI
CCI-000225
Version
GEN001560
Vuln IDs
  • V-915
Rule IDs
  • SV-915r2_rule
Excessive permissions allow unauthorized access to user's files. trueSystem AdministratorInformation Assurance OfficerECLP-1
Checks: C-431r3_chk

For each user in the /etc/passwd file, check for files and directories with a mode more permissive than 0750. Procedure: # find /&lt;usershomedirectory&gt; ! -fstype nfs ! \( -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 \) \( -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-1069r2_fix

Change the mode of files and directories within user's home directories to 0750. Procedure: # chmod 0750 filename Document all changes.

b
The /etc/shells (or equivalent) file must exist.
CM-6 - Medium - CCI-000366 - V-916 - SV-38741r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN002120
Vuln IDs
  • V-916
Rule IDs
  • SV-38741r1_rule
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.System AdministratorECSC-1
Checks: C-37242r1_chk

Check /etc/security/login.cfg for a shells stanza. Procedure: # grep -p usw: /etc/security/login.cfg | grep "shells =" If no such stanza exists, this is a finding. Check the /etc/shells file. Procedure: # more /etc/shells If the /etc/shells file does not exist, this is a finding.

Fix: F-32456r1_fix

Edit the /etc/security/login.cfg file and add a shells stanza containing a list of valid shells. #chsec -f /etc/security/login.cfg -s usw -a shells=<list of approved shells> Create the /etc/shells file. #vi /etc/shells

b
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-917 - SV-38742r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN002140
Vuln IDs
  • V-917
Rule IDs
  • SV-38742r1_rule
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.System AdministratorECSC-1
Checks: C-37177r1_chk

Confirm the login shells referenced in the /etc/passwd file are listed in the /etc/security/login.cfg file's shells =variable in the usw stanza. # more /etc/security/login.cfg # 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 shells stanza. If a shell referenced in /etc/passwd is not listed in the shells stanza, excluding the above mentioned shells, then this is a finding.

Fix: F-32457r1_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. Alternatively, use the SMIT to change the /etc/passwd shell entry.

b
Accounts must be locked upon 35 days of inactivity.
AC-2 - Medium - CCI-000017 - V-918 - SV-38840r1_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-000017
Version
GEN000760
Vuln IDs
  • V-918
Rule IDs
  • SV-38840r1_rule
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. trueSystem AdministratorIAAC-1
Checks: C-37833r1_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. If an inactive account is not disabled via an invalid login shell /bin/false entry in the shell field of the /etc/passwd file or account_locked = true in /etc/security/user file, this is a finding.

Fix: F-33093r1_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 SMIT or the chsec command. Change the accounts login shell. #chsh <account> /bin/false Lock the account in /etc/security/user file. #chuser account_locked=true < user id > OR # smitty chuser

b
All shell files must be owned by root or bin.
AC-6 - Medium - CCI-000225 - V-921 - SV-38847r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002200
Vuln IDs
  • V-921
Rule IDs
  • SV-38847r1_rule
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.System AdministratorECLP-1
Checks: C-37840r1_chk

Obtain a list of system shells from /etc/security/login.cfg and check the ownership of these shells. Procedure: #grep shells /etc/security/login.cfg | grep -v \* | cut -f 2 -d = | sed s/,/\ /g | xargs -n1 ls -l If any shell is not owned by root or bin, this is a finding. Obtain a list of system shells from /etc/shells and check the ownership of these shells. Procedure: #cat /etc/shells | xargs -n1 ls -l If any shell is not owned by root or bin, this is a finding.

Fix: F-33103r1_fix

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

c
All shell files must have mode 0755 or less permissive.
AC-6 - High - CCI-000225 - V-922 - SV-38846r1_rule
RMF Control
AC-6
Severity
High
CCI
CCI-000225
Version
GEN002220
Vuln IDs
  • V-922
Rule IDs
  • SV-38846r1_rule
Shells with world/group write permissions give the ability to maliciously modify the shell to obtain unauthorized access.System AdministratorECLP-1
Checks: C-37839r1_chk

Obtain a list of system shells from /etc/security/login.cfg and check the permissions of these shells. Procedure: #grep shells /etc/security/login.cfg | grep -v \* | cut -f 2 -d = | sed s/,/\ /g | xargs -n1 ls -l If any shell has a mode more permissive than 0755, this is a finding. Obtain a list of system shells from /etc/shells and check the ownership of these shells. Procedure: #cat /etc/shells | xargs -n1 ls -l If any shell has a mode more permissive than 0755, this is a finding.

Fix: F-33102r1_fix

Change the mode of the shell. # chmod 0755 < shell >

a
The system must be checked for extraneous device files at least weekly.
CM-3 - Low - CCI-000318 - V-923 - SV-923r2_rule
RMF Control
CM-3
Severity
Low
CCI
CCI-000318
Version
GEN002260
Vuln IDs
  • V-923
Rule IDs
  • SV-923r2_rule
If an unauthorized device is allowed to exist on the system, there is the possibility the system may perform unauthorized operations.System AdministratorInformation Assurance OfficerDCSW-1, ECSC-1
Checks: C-464r2_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-1077r2_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

b
Device files and directories must only be writable by users with a system account or as configured by the vendor.
AC-6 - Medium - CCI-000225 - V-924 - SV-924r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002280
Vuln IDs
  • V-924
Rule IDs
  • SV-924r2_rule
System device files in writable directories could be modified, removed, or used by an unprivileged user to control system hardware.System AdministratorECCD-1, ECLP-1, ECCD-2
Checks: C-465r2_chk

Find all device files existing anywhere on the system. Procedure: # find / -type b -print &gt; devicelist # find / -type c -print &gt;&gt; devicelist Check the permissions on the directories above subdirectories containing device files. If any of the device files or their parent directories is world-writable, excepting device files specifically intended to be world-writable, such as /dev/null, this is a finding.

Fix: F-1078r3_fix

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

b
Device files used for backup must only be readable and/or writable by root or the backup user.
AC-6 - Medium - CCI-000225 - V-925 - SV-38745r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002300
Vuln IDs
  • V-925
Rule IDs
  • SV-38745r1_rule
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.trueInformation Assurance OfficerSystem AdministratorECCD-1, ECCD-2
Checks: C-37183r1_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 (Typical backup devices for tape are/dev/rmt* and cd/dvd writers are /dev/cd*).

Fix: F-32459r1_fix

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

b
Any NIS+ server must be operating at security level 2.
AC-17 - Medium - CCI-001435 - V-926 - SV-926r2_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-001435
Version
GEN006460
Vuln IDs
  • V-926
Rule IDs
  • SV-926r2_rule
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.System AdministratorECSC-1
Checks: C-852r2_chk

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

Fix: F-25778r1_fix

Configure the NIS+ server to use security level 2.

b
The NFS export configuration file must be owned by root.
AC-6 - Medium - CCI-000225 - V-928 - SV-28445r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN005740
Vuln IDs
  • V-928
Rule IDs
  • SV-28445r1_rule
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.System AdministratorECLP-1
Checks: C-28739r1_chk

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

Fix: F-25756r1_fix

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

a
The NFS export configuration file must have mode 0644 or less permissive.
AC-6 - Low - CCI-000225 - V-929 - SV-28447r1_rule
RMF Control
AC-6
Severity
Low
CCI
CCI-000225
Version
GEN005760
Vuln IDs
  • V-929
Rule IDs
  • SV-28447r1_rule
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.System AdministratorECLP-1, ECCD-2, ECCD-1
Checks: C-28742r1_chk

# ls -lL /etc/exports If the file has a mode more permissive than 0644, this is a finding.

Fix: F-25760r1_fix

# chmod 0644 /etc/exports

b
All NFS-exported system files and system directories must be owned by root.
AC-6 - Medium - CCI-000225 - V-931 - SV-931r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN005800
Vuln IDs
  • V-931
Rule IDs
  • SV-931r2_rule
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.System AdministratorECSC-1
Checks: C-862r2_chk

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

Fix: F-1085r2_fix

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

b
The NFS anonymous UID and GID must be configured to values without permissions.
AC-14 - Medium - CCI-000062 - V-932 - SV-38956r1_rule
RMF Control
AC-14
Severity
Medium
CCI
CCI-000062
Version
GEN005820
Vuln IDs
  • V-932
Rule IDs
  • SV-38956r1_rule
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.System AdministratorIAIA-1, ECSC-1, IAIA-2
Checks: C-863r2_chk

Check if the anon option is set correctly for exported file systems. List exported file systems. # exportfs -v 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-32338r1_fix

Edit /etc/exports and set the anon=-1 option for exported file systems without it. Re-export the file systems. # exportfs -a

b
The NFS server must be configured to restrict file system access to local hosts.
CM-6 - Medium - CCI-000366 - V-933 - SV-41524r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN005840
Vuln IDs
  • V-933
Rule IDs
  • SV-41524r1_rule
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.System AdministratorECSC-1
Checks: C-864r2_chk

Check the permissions on exported NFS file systems. Procedure: # exportfs -v 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-1087r2_fix

Edit /etc/exports 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.

b
The NFS server must not allow remote root access.
AC-6 - Medium - CCI-000225 - V-935 - SV-935r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN005880
Vuln IDs
  • V-935
Rule IDs
  • SV-935r2_rule
If the NFS server allows root access to local file systems from remote hosts, this access could be used to compromise the system.System AdministratorInformation Assurance OfficerInformation Assurance ManagerEBRP-1
Checks: C-867r2_chk

Determine if the NFS server is exporting with the root access option. Procedure: # exportfs -v | grep "root=" If an export with the root option is found, this is a finding.

Fix: F-1089r2_fix

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

b
The nosuid option must be enabled on all NFS client mounts.
AC-6 - Medium - CCI-000225 - V-936 - SV-38957r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN005900
Vuln IDs
  • V-936
Rule IDs
  • SV-38957r1_rule
Enabling the nosuid mount option prevents the system from granting owner or group-owner privileges to programs with the suid or sgid 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 suid or sgid files located on the mounted NFS file system.Information Assurance OfficerSystem AdministratorInformation Assurance ManagerECPA-1
Checks: C-38202r1_chk

Check the system for NFS mounts not using the nosuid option. Procedure: # lsfs -v nfs If the mounted file systems do not have the nosuid option, this is a finding.

Fix: F-32339r1_fix

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

b
The system must use an access control program.
CM-6 - Medium - CCI-000366 - V-940 - SV-38959r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN006580
Vuln IDs
  • V-940
Rule IDs
  • SV-38959r1_rule
Access control programs (such as TCP_WRAPPERS) provide the ability to enhance system security posture.System AdministratorEBRU-1
Checks: C-28781r1_chk

Determine if TCP_WRAPPERS is being used. # grep tcpd /etc/inetd.conf If no services are listed, this is a finding.

Fix: F-32344r1_fix

Edit /etc/inetd.conf and use tcpd to wrap services. Use SMIT to install TCP Wrappers from the AIX Expansion pack media as fileset netsec.options.tcpwrappers.

b
The system's access control program must log each system access attempt.
AU-2 - Medium - CCI-000126 - V-941 - SV-941r2_rule
RMF Control
AU-2
Severity
Medium
CCI
CCI-000126
Version
GEN006600
Vuln IDs
  • V-941
Rule IDs
  • SV-941r2_rule
If access attempts are not logged, then multiple attempts to log on to the system by an unauthorized user may go undetected.System AdministratorECAR-1, ECAR-3, ECAR-2
Checks: C-888r2_chk

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

Fix: F-1095r2_fix

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

b
AIX Trusted Computing Base (TCB) software must be implemented.
AC-4 - Medium - CCI-000032 - V-969 - SV-969r2_rule
RMF Control
AC-4
Severity
Medium
CCI
CCI-000032
Version
GEN000000-AIX00020
Vuln IDs
  • V-969
Rule IDs
  • SV-969r2_rule
The AIX Trusted Computing Base (TCB) software provides protection from the unauthorized modification of core system files.System AdministratorECSC-1
Checks: C-2321r2_chk

Perform: # /bin/tcbck If TCB is not installed, the output will show an error code of 3001-101 and/or a text message indicating TCB is not installed, this is a finding.

Fix: F-31368r1_fix

Ensure the Trusted Computing Base (TCB) software is implemented. TCB can only be installed at OS installation time.

b
Access to the cron utility must be controlled using the cron.allow and/or cron.deny file(s).
AC-6 - Medium - CCI-000225 - V-974 - SV-27318r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002960
Vuln IDs
  • V-974
Rule IDs
  • SV-27318r1_rule
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.System AdministratorECLP-1
Checks: C-28455r1_chk

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

Fix: F-24558r1_fix

Create /var/adm/cron/cron.allow and/or /var/adm/cron/cron.deny with appropriate content.

b
The cron.allow file must have mode 0640 or less permissive.
AC-6 - Medium - CCI-000225 - V-975 - SV-39872r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002980
Vuln IDs
  • V-975
Rule IDs
  • SV-39872r1_rule
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.System AdministratorECLP-1
Checks: C-38875r1_chk

Check mode of the cron.allow file. Procedure: # ls -lL /var/adm/cron/cron.allow If the file has a mode more permissive than 0640, this is a finding.

Fix: F-34019r1_fix

Change the mode of the cron.allow file to 0640. Procedure: # chmod 0640 /var/adm/cron/cron.allow

b
Cron must not execute group-writable or world-writable programs.
AC-6 - Medium - CCI-000225 - V-976 - SV-27329r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003000
Vuln IDs
  • V-976
Rule IDs
  • SV-27329r1_rule
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. System AdministratorDCSL-1
Checks: C-28464r1_chk

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

Fix: F-1130r2_fix

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

b
Cron must not execute programs in, or subordinate to, world-writable directories.
AC-6 - Medium - CCI-000225 - V-977 - SV-38947r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003020
Vuln IDs
  • V-977
Rule IDs
  • SV-38947r1_rule
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.System AdministratorDCSL-1
Checks: C-28466r1_chk

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

Fix: F-32473r1_fix

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

b
Crontab files must have mode 0600 or less permissive, and files in cron script directories must have mode 0700 or less permissive.
AC-6 - Medium - CCI-000225 - V-978 - SV-39873r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003080
Vuln IDs
  • V-978
Rule IDs
  • SV-39873r1_rule
To protect the integrity of scheduled system jobs and prevent malicious modification to these jobs, crontab files must be secured.System AdministratorECLP-1
Checks: C-790r2_chk

Check the modes of the crontab and cron job script files. If the mode is more permissive than 0600 for crontab files or 0700 for cron job script files, this is a finding.

Fix: F-1132r2_fix

Change the modes of crontab files to 0600 and cron job script files to 0700.

b
Cron and crontab directories must have mode 0755 or less permissive.
AC-6 - Medium - CCI-000225 - V-979 - SV-27342r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003100
Vuln IDs
  • V-979
Rule IDs
  • SV-27342r1_rule
To protect the integrity of scheduled system jobs and to prevent malicious modification to these jobs, crontab files must be secured. System AdministratorECLP-1
Checks: C-28478r1_chk

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

Fix: F-24581r1_fix

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

b
Cron and crontab directories must be owned by root or bin.
AC-6 - Medium - CCI-000225 - V-980 - SV-27345r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003120
Vuln IDs
  • V-980
Rule IDs
  • SV-27345r1_rule
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.System AdministratorECLP-1
Checks: C-28480r1_chk

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

Fix: F-24583r1_fix

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

b
Cron and crontab directories must be group-owned by system, sys, bin, or cron.
AC-6 - Medium - CCI-000225 - V-981 - SV-39104r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003140
Vuln IDs
  • V-981
Rule IDs
  • SV-39104r1_rule
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.System AdministratorECLP-1
Checks: C-38095r1_chk

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

Fix: F-33357r1_fix

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

b
Cron logging must be implemented.
AU-2 - Medium - CCI-000126 - V-982 - SV-27350r1_rule
RMF Control
AU-2
Severity
Medium
CCI
CCI-000126
Version
GEN003160
Vuln IDs
  • V-982
Rule IDs
  • SV-27350r1_rule
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. System AdministratorECAR-2, ECAR-1, ECAR-3
Checks: C-28491r1_chk

# ls -lL /var/adm/cron/log If this file does not exist or is older than the last cron job, this is a finding.

Fix: F-1136r2_fix

Enable cron logging on the system.

b
The cronlog file must have mode 0600 or less permissive.
AC-6 - Medium - CCI-000225 - V-983 - SV-27355r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003180
Vuln IDs
  • V-983
Rule IDs
  • SV-27355r1_rule
Cron logs contain reports of scheduled system activities and must be protected from unauthorized access or manipulation. System AdministratorECTP-1, ECLP-1
Checks: C-28498r1_chk

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

Fix: F-24600r1_fix

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

b
Access to the at utility must be controlled via the at.allow and/or at.deny file(s).
AC-6 - Medium - CCI-000225 - V-984 - SV-27377r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003280
Vuln IDs
  • V-984
Rule IDs
  • SV-27377r1_rule
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.System AdministratorECLP-1
Checks: C-28531r1_chk

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

Fix: F-11346r2_fix

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

b
The at.deny file must not be empty if it exists.
AC-6 - Medium - CCI-000225 - V-985 - SV-27381r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003300
Vuln IDs
  • V-985
Rule IDs
  • SV-27381r1_rule
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.trueInformation Assurance OfficerSystem AdministratorECLP-1
Checks: C-28535r1_chk

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

Fix: F-1139r2_fix

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

b
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.
AC-6 - Medium - CCI-000225 - V-986 - SV-27385r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003320
Vuln IDs
  • V-986
Rule IDs
  • SV-27385r1_rule
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.System AdministratorECPA-1
Checks: C-28541r1_chk

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

Fix: F-1140r2_fix

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

b
The at.allow file must have mode 0640 or less permissive.
AC-6 - Medium - CCI-000225 - V-987 - SV-39871r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003340
Vuln IDs
  • V-987
Rule IDs
  • SV-39871r1_rule
Permissions more permissive than 0640 may allow unauthorized or malicious access to the at.allow and/or at.deny files.System AdministratorECLP-1
Checks: C-38874r1_chk

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

Fix: F-34018r1_fix

Change the mode of the at.allow file. # chmod 0640 /var/adm/cron/at.allow

b
The at daemon must not execute group-writable or world-writable programs.
AC-6 - Medium - CCI-000225 - V-988 - SV-988r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003360
Vuln IDs
  • V-988
Rule IDs
  • SV-988r2_rule
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.System AdministratorDCSL-1
Checks: C-801r2_chk

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

Fix: F-1142r2_fix

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

b
The "at" daemon must not execute programs in, or subordinate to, world-writable directories.
AC-6 - Medium - CCI-000225 - V-989 - SV-989r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003380
Vuln IDs
  • V-989
Rule IDs
  • SV-989r2_rule
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.System AdministratorDCSL-1
Checks: C-802r2_chk

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

Fix: F-1143r2_fix

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

c
SNMP communities, users, and passphrases must be changed from the default.
IA-5 - High - CCI-000178 - V-993 - SV-38889r1_rule
RMF Control
IA-5
Severity
High
CCI
CCI-000178
Version
GEN005300
Vuln IDs
  • V-993
Rule IDs
  • SV-38889r1_rule
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).System AdministratorIAAC-1
Checks: C-37055r1_chk

Check the SNMP configuration for default passwords. Locate and examine the SNMP configuration. Procedure: # find / -name "snmp*.conf" -print # more &lt;snmpd.conf&gt; 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, or any value which does not meet DISA password requirements, this is a finding.

Fix: F-33134r1_fix

Change the default passwords. To change them, locate the file /etc/snmpd.conf or the file /etc/snmpd3.conf. Edit the file. Locate the line system-group-read-community which has a default password of public and make the password something more random (less guessable). Do the same 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.

b
The snmpd.conf file must have mode 0600 or less permissive.
AC-6 - Medium - CCI-000225 - V-994 - SV-38817r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN005320
Vuln IDs
  • V-994
Rule IDs
  • SV-38817r1_rule
The snmpd.conf file contains authenticators and must be protected from unauthorized access and modification.System AdministratorECLP-1
Checks: C-37058r1_chk

Check the mode of the SNMP daemon configuration file. Locate the SNMP daemon configuration file. Consult vendor documentation to verify the name and location of the file. Procedure: # find / -name "snmpd*.conf" Check the mode of the SNMP daemon configuration file. Procedure: # ls -lL &lt;snmpd conf&gt;

Fix: F-32326r1_fix

Change the mode of the SNMP daemon configuration file to 0600. Procedure: # chmod 0600 /etc/snmpd.conf # chmod 0600 /etc/snmpdv3.conf

b
Management Information Base (MIB) files must have mode 0640 or less permissive.
AC-6 - Medium - CCI-000225 - V-995 - SV-995r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN005340
Vuln IDs
  • V-995
Rule IDs
  • SV-995r2_rule
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.System AdministratorECLP-1
Checks: C-818r2_chk

Check the modes for all Management Information Base (MIB) files on the system. Procedure: # find / -name *.mib -print # ls -lL &lt;mib file&gt; If any file is returned that does not have mode 0640 or less permissive, this is a finding.

Fix: F-1149r2_fix

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

b
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-1010 - SV-1010r3_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN002480
Vuln IDs
  • V-1010
Rule IDs
  • SV-1010r3_rule
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.System AdministratorECSC-1
Checks: C-467r3_chk

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

Fix: F-1164r2_fix

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

a
Inetd or xinetd logging/tracing must be enabled.
AU-3 - Low - CCI-000134 - V-1011 - SV-38951r1_rule
RMF Control
AU-3
Severity
Low
CCI
CCI-000134
Version
GEN003800
Vuln IDs
  • V-1011
Rule IDs
  • SV-38951r1_rule
Inetd or xinetd logging and tracing allows the system administrators to observe the IP addresses that are 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.System AdministratorECAR-3, ECSC-1, ECAR-2, ECAR-1
Checks: C-38287r2_chk

Determine if inetd or xinetd has logging or tracing enabled. # ps -ef |grep inetd |grep -e "-d" If no results are returned, this is a finding.

Fix: F-31831r1_fix

Edit the inetd startup script to contain the "-d" parameter for the inetd process. #vi /etc/rc.tcpip # chssys -s inetd -a '-d'

c
The system must be configured to only boot from the system boot device.
CM-6 - High - CCI-000366 - V-1013 - SV-38835r1_rule
RMF Control
CM-6
Severity
High
CCI
CCI-000366
Version
GEN008600
Vuln IDs
  • V-1013
Rule IDs
  • SV-38835r1_rule
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 that could compromise or damage the system. It could also allow the system to be used for malicious purposes by a malicious anonymous user.System AdministratorECSC-1
Checks: C-37096r1_chk

Determine if the system is configured to boot from devices other than the system startup media. # bootlist -m normal -o The returned values should be hdisk{x}. If the system is setup to boot from a non-hard disk device, this is a finding. Additionally, ask the SA if the machine is setup for multi-boot in the SMS application. If multi-boot is enabled, the firmware will stop at boot time and request which image to boot from the user. If multi-boot is enabled, this is a finding.

Fix: F-32367r1_fix

Configure the system to only boot from system startup media. # bootlist -m normal hdisk< x > Set multi-boot to off in the SMS application.

b
The system must not run an Internet Network News (INN) server.
CM-7 - Medium - CCI-000381 - V-1023 - SV-1023r2_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
GEN006240
Vuln IDs
  • V-1023
Rule IDs
  • SV-1023r2_rule
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.System AdministratorInformation Assurance OfficerECSC-1
Checks: C-2043r2_chk

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

Fix: F-1177r2_fix

Disable the INN server.

b
The Samba Web Administration Tool (SWAT) must be restricted to the local host or require SSL.
AC-17 - Medium - CCI-001436 - V-1026 - SV-1026r2_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-001436
Version
GEN006080
Vuln IDs
  • V-1026
Rule IDs
  • SV-1026r2_rule
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.System AdministratorEBRP-1, ECCT-1, ECCT-2
Checks: C-2047r3_chk

Check the system for an enabled SWAT service. # grep -i swat /etc/inetd.conf If SWAT is found enabled, it must be utilized with SSL to ensure a secure connection between the client and the server. Ask the SA to identify the method used to provide SSL protection for the SWAT service. Verify (or ask the SA to demonstrate) this configuration is effective by accessing SWAT using an HTTPS connection from a web browser. If SWAT is found enabled and has no SSL protection, this is a finding.

Fix: F-1180r3_fix

Disable SWAT (e.g., remove the "swat" line from inetd.conf or equivalent, and restart the service) or configure SSL protection for the SWAT service.

b
The /usr/lib/smb.conf file must be owned by root.
AC-6 - Medium - CCI-000225 - V-1027 - SV-40724r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN006100
Vuln IDs
  • V-1027
Rule IDs
  • SV-40724r1_rule
The /usr/lib/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.System AdministratorECLP-1
Checks: C-39455r1_chk

Check the ownership of the /usr/lib/smb.conf file. Procedure: # ls -l /usr/lib/smb.conf If an smb.conf file is not owned by root, this is a finding.

Fix: F-34583r1_fix

Change the ownership of the smb.conf file. Procedure: # chown root /usr/lib/smb.conf

b
The /usr/lib/smb.conf file must have mode 0644 or less permissive.
AC-6 - Medium - CCI-000225 - V-1028 - SV-39229r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN006140
Vuln IDs
  • V-1028
Rule IDs
  • SV-39229r1_rule
If the smb.conf file has excessive permissions, the file may be maliciously modified and the Samba configuration could be compromised.System AdministratorECLP-1
Checks: C-39456r1_chk

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

Fix: F-34584r1_fix

Change the mode of the smb.conf file to 0644 or less permissive. Procedure: # chmod 0644 /usr/lib/smb.conf

b
The /var/private/smbpasswd file must be owned by root.
AC-6 - Medium - CCI-000225 - V-1029 - SV-40379r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN006160
Vuln IDs
  • V-1029
Rule IDs
  • SV-40379r1_rule
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.System AdministratorECLP-1
Checks: C-39245r1_chk

Check the ownership of the smbpasswd file. # ls -l /var/private/smbpasswd If an smbpasswd file is not owned by root, this is a finding.

Fix: F-34347r1_fix

Change the owner of the smbpasswd file to root. # chown root /var/private/smbpasswd

b
The smb.conf file must use the hosts option to restrict access to Samba.
AC-6 - Medium - CCI-000225 - V-1030 - SV-39237r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN006220
Vuln IDs
  • V-1030
Rule IDs
  • SV-39237r1_rule
Samba increases the attack surface of the system and must be restricted to communicate only with systems requiring access.System AdministratorECSC-1
Checks: C-38211r1_chk

Examine the smb.conf file. # more /usr/lib/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-1184r2_fix

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

b
Users must not be able to change passwords more than once every 24 hours.
IA-5 - Medium - CCI-000198 - V-1032 - SV-38768r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000198
Version
GEN000540
Vuln IDs
  • V-1032
Rule IDs
  • SV-38768r1_rule
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.System AdministratorECSC-1
Checks: C-36689r1_chk

Check the minage field for each user. # /usr/sbin/lsuser -a minage ALL If the minage field is less than 1 for any user, this is a finding.

Fix: F-33201r1_fix

Use SMIT or the chsec command to set the minimum password age to 1 week. # chsec -f /etc/security/user -s default -a minage=1 # chsec -f /etc/security/user -s <user id> -a minage=1 OR # smitty chuser

c
Root passwords must never be passed over a network in clear text form.
IA-5 - High - CCI-000197 - V-1046 - SV-39097r1_rule
RMF Control
IA-5
Severity
High
CCI
CCI-000197
Version
GEN001100
Vuln IDs
  • V-1046
Rule IDs
  • SV-39097r1_rule
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.System AdministratorECNK-1, ECNK-2, IAIA-1, IAIA-2
Checks: C-891r2_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-33347r1_fix

Install OpenSSH from AIX installation media or AIX Expansion Pack. #smitty installp Enable SSH on the system and use it for all remote connections used to attain root access. Disable direct root login. # chsec -f /etc/security/user -s root -a rlogin=false

b
The system must not permit root logins using remote access programs, such as ssh.
IA-2 - Medium - CCI-000770 - V-1047 - SV-38684r1_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000770
Version
GEN001120
Vuln IDs
  • V-1047
Rule IDs
  • SV-38684r1_rule
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.System AdministratorECPA-1
Checks: C-36938r1_chk

Determine if the SSH daemon is configured to permit root logins. Procedure: # find / -name sshd_config -ls # grep -v "^#" &lt;sshd_config path and file&gt; | grep -i permitrootlogin If the PermitRootLogin entry is not found or is not set to no, this is a finding.

Fix: F-32204r1_fix

Edit the /etc/ssh/sshd_config file and set the PermitRootLogin option to no and refresh sshd. #kill -1 <pid of sshd>

b
Audio devices must have mode 0660 or less permissive.
AC-6 - Medium - CCI-000225 - V-1048 - SV-27243r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002320
Vuln IDs
  • V-1048
Rule IDs
  • SV-27243r1_rule
Audio and video devices that are globally accessible have proven to be another security hazard. 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. System AdministratorECLP-1
Checks: C-28267r1_chk

Check the mode of audio devices. # /usr/sbin/lsdev -C | grep -i audio # ls -lL /dev/*aud0 If the mode of audio devices are more permissive than 0660, this is a finding.

Fix: F-24491r1_fix

Change the mode of audio devices. # chmod o-w <audio device>

b
Audio devices must be owned by root.
AC-6 - Medium - CCI-000225 - V-1049 - SV-27248r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002340
Vuln IDs
  • V-1049
Rule IDs
  • SV-27248r1_rule
Audio and video devices that are globally accessible have proven to be another security hazard. 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. System AdministratorECLP-1
Checks: C-28273r1_chk

Check the owner of audio devices. Procedure: # /usr/sbin/lsdev -C | grep -i audio # ls -lL /dev/*aud0 If the owner of any audio device file is not root, this is a finding.

Fix: F-1203r2_fix

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

b
The /usr/lib/smb.conf file must be group-owned by bin, sys, or system.
AC-6 - Medium - CCI-000225 - V-1056 - SV-39231r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN006120
Vuln IDs
  • V-1056
Rule IDs
  • SV-39231r1_rule
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.System AdministratorECLP-1
Checks: C-39457r1_chk

Check the group ownership of the smb.conf file. Procedure: # ls -l /usr/lib/smb.conf If an smb.conf file is not group-owned by bin, sys, or system, this is a finding.

Fix: F-33481r1_fix

Change the group owner of the smb.conf file. Procedure: # chgrp system /usr/lib/smb.conf

b
The /var/private/smbpasswd file must be group-owned by sys or system.
AC-6 - Medium - CCI-000225 - V-1058 - SV-39235r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN006180
Vuln IDs
  • V-1058
Rule IDs
  • SV-39235r1_rule
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.System AdministratorECLP-1
Checks: C-38209r1_chk

Check smbpasswd ownership. # ls -lL /var/private/smbpasswd If smbpasswd is not group-owned by sys, or system, this is a finding.

Fix: F-33485r1_fix

Use the chgrp command to change the group owner of the smbpasswd file to system. # chgrp system /var/private/smbpasswd

b
The /var/private/smbpasswd file must have mode 0600 or less permissive.
AC-6 - Medium - CCI-000225 - V-1059 - SV-40725r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN006200
Vuln IDs
  • V-1059
Rule IDs
  • SV-40725r1_rule
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.System AdministratorECLP-1
Checks: C-39458r1_chk

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

Fix: F-34585r1_fix

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

b
Audio devices must be group-owned by root, sys, bin, or system.
AC-6 - Medium - CCI-000225 - V-1061 - SV-27253r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002360
Vuln IDs
  • V-1061
Rule IDs
  • SV-27253r1_rule
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. System AdministratorECLP-1
Checks: C-28285r1_chk

Check the group owner of audio devices. Procedure: # /usr/sbin/lsdev -C | grep -i audio # ls -lL /dev/*aud0 If the group owner of an audio device is not root, sys, bin, or system, this is a finding.

Fix: F-1215r2_fix

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

b
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-4083 - SV-39096r1_rule
RMF Control
AC-11
Severity
Medium
CCI
CCI-000057
Version
GEN000500
Vuln IDs
  • V-4083
Rule IDs
  • SV-39096r1_rule
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.System AdministratorPESL-1
Checks: C-8205r2_chk

Log into a graphical desktop environment provided by the system. Allow the session to remain idle for 15 minutes. If the desktop session is not automatically locked after 15 minutes, or does not require re-authentication to resume operations, this is a finding.

Fix: F-4016r2_fix

Consult vendor documentation to determine the settings required for the system to lock graphical desktop environments. Configure the system to lock graphical desktop environments after 15 minutes of inactivity and require re-authentication to resume operations.

b
The system must prohibit the reuse of passwords within five iterations.
IA-5 - Medium - CCI-000200 - V-4084 - SV-38679r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000200
Version
GEN000800
Vuln IDs
  • V-4084
Rule IDs
  • SV-38679r1_rule
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.System AdministratorIAIA-2, IAIA-1
Checks: C-36911r1_chk

Procedure: #lsuser -a histsize ALL If the returned histsize for any user is less than 5, this is a finding.

Fix: F-32090r1_fix

Use the chsec command to configure the system to prohibit the reuse of passwords within five iterations. # chsec -f /etc/security/user -s default -a histsize=5 # chuser histsize=5 < user id >

b
User start-up files must not execute world-writable programs.
AC-6 - Medium - CCI-000225 - V-4087 - SV-4087r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001940
Vuln IDs
  • V-4087
Rule IDs
  • SV-4087r2_rule
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.System AdministratorDCSW-1
Checks: C-8206r2_chk

Check local initialization files for any executed world-writable programs or scripts. Procedure: # more /&lt;usershomedirectory&gt;/.* # ls -al &lt;program or script&gt; If any local initialization file executes a world-writable program or script, this is a finding.

Fix: F-4020r2_fix

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

b
All system start-up files must be owned by root.
AC-6 - Medium - CCI-000225 - V-4089 - SV-27209r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001660
Vuln IDs
  • V-4089
Rule IDs
  • SV-27209r1_rule
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. System AdministratorECLP-1
Checks: C-28187r1_chk

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

Fix: F-4022r2_fix

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

b
All system start-up files must be group-owned by sys, bin, other, or system.
AC-6 - Medium - CCI-000225 - V-4090 - SV-27216r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001680
Vuln IDs
  • V-4090
Rule IDs
  • SV-27216r1_rule
If system start-up files do not have a group owner of a system group, the files may be modified by malicious users or intruders.System AdministratorECLP-1
Checks: C-28193r1_chk

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

Fix: F-34013r1_fix

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

b
System start-up files must only execute programs owned by a privileged UID or an application.
AC-6 - Medium - CCI-000225 - V-4091 - SV-27221r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001700
Vuln IDs
  • V-4091
Rule IDs
  • SV-27221r1_rule
System start-up files executing programs owned by other than root (or another privileged user) or an application indicate the system may have been compromised. System AdministratorDCSL-1
Checks: C-28190r1_chk

Check the ownership of any files executed from system startup scripts. If any of these files are not owned by root, bin, sys, or other, this is a finding.

Fix: F-24458r1_fix

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

b
System BIOS or system controllers supporting password protection must have administrator accounts/passwords configured, and no others.
AC-3 - Medium - CCI-000213 - V-4246 - SV-38836r1_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
GEN008620
Vuln IDs
  • V-4246
Rule IDs
  • SV-38836r1_rule
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.System AdministratorECSC-1
Checks: C-37097r1_chk

Ask the SA if a password has been given to the Service processors ADMIN account. If a password has not been assigned to the service processor, this is a finding.

Fix: F-33090r1_fix

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

c
The system must not use removable media as the boot loader.
CM-6 - High - CCI-000366 - V-4247 - SV-38837r1_rule
RMF Control
CM-6
Severity
High
CCI
CCI-000366
Version
GEN008640
Vuln IDs
  • V-4247
Rule IDs
  • SV-38837r1_rule
Malicious users with removable boot media can gain access to a system configured to use removable media as the boot loader.System AdministratorECSC-1
Checks: C-37099r1_chk

Check the servers boot lists for the normal, service, both, or prevboot modes. # bootlist -m &lt;mode&gt; -o Ensure hdisk{x} is the only devices listed. If boot devices, such as cd{x}, fd{x}. rmt{x}, ent{x} are used, this is a finding.

Fix: F-32369r1_fix

Configure the system to use a bootloader installed on fixed media. # bootlist -m normal hdisk0 # bootlist -m service hdisk0

c
If the system boots from removable media, it must be stored in a safe or similarly secured container.
SC-32 - High - CCI-001208 - V-4255 - SV-4255r2_rule
RMF Control
SC-32
Severity
High
CCI
CCI-001208
Version
GEN008680
Vuln IDs
  • V-4255
Rule IDs
  • SV-4255r2_rule
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.System AdministratorInformation Assurance OfficerPESS-1
Checks: C-2079r2_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-4166r2_fix

Store the system boot media in a secure container when not in use.

b
The system must not have unnecessary accounts.
AC-2 - Medium - CCI-000012 - V-4269 - SV-38767r1_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-000012
Version
GEN000290
Vuln IDs
  • V-4269
Rule IDs
  • SV-38767r1_rule
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.System AdministratorIAAC-1
Checks: C-36656r1_chk

Check the system for unnecessary user accounts. Procedure: # more /etc/passwd Some examples of unnecessary accounts includes guest, uucp, games, news, gopher, ftp, and lp. If any unnecessary accounts are found, this is a finding.

Fix: F-34155r1_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, that are associated with a service not in use should also be removed. # rmuser -p <username>

b
The /etc/news/hosts.nntp (or equivalent) must have mode 0600 or less permissive.
AC-6 - Medium - CCI-000225 - V-4273 - SV-39250r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN006260
Vuln IDs
  • V-4273
Rule IDs
  • SV-39250r1_rule
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.System AdministratorECLP-1
Checks: C-38224r1_chk

Check /etc/news/hosts.nntp permissions. # find / -name hosts.nntp # ls -lL &lt; hosts.nntp file &gt; If /etc/news/hosts.nntp has a mode more permissive than 0600, this is a finding.

Fix: F-33499r1_fix

Change the mode of the hosts.nntp file to 0600. # chmod 0600 < hosts.nntp file>

b
The /etc/news/hosts.nntp.nolimit (or equivalent) must have mode 0600 or less permissive.
AC-6 - Medium - CCI-000225 - V-4274 - SV-39252r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN006280
Vuln IDs
  • V-4274
Rule IDs
  • SV-39252r1_rule
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.System AdministratorECLP-1
Checks: C-38226r1_chk

Check /etc/news/hosts.nntp.nolimit permissions. # find / -name hosts.nntp.nolimit # ls -lL &lt; hosts.nntp.nolimit file &gt; If hosts.nntp.nolimit has a mode more permissive than 0600, this is a finding.

Fix: F-33501r1_fix

Change the mode of hosts.nntp.nolimit to 0600. # chmod 0600 < hosts.nntp.nolimit file>

b
The /etc/news/nnrp.access (or equivalent) must have mode 0600 or less permissive.
AC-6 - Medium - CCI-000225 - V-4275 - SV-39255r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN006300
Vuln IDs
  • V-4275
Rule IDs
  • SV-39255r1_rule
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.System AdministratorECLP-1
Checks: C-38229r1_chk

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

Fix: F-33504r1_fix

Change the mode of the nnrp.access file to 0600. # chmod 0600 < nnrp.access >

b
The /etc/news/passwd.nntp file (or equivalent) must have mode 0600 or less permissive.
AC-6 - Medium - CCI-000225 - V-4276 - SV-39260r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN006320
Vuln IDs
  • V-4276
Rule IDs
  • SV-39260r1_rule
File permissions more permissive than 0600 for /etc/news/passwd.nntp may allow access to privileged information by system intruders or malicious users.System AdministratorECLP-1
Checks: C-38235r1_chk

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

Fix: F-33509r1_fix

Change the mode of the passwd.nntp file. # chmod 0600 < passwd.nntp >

b
Files in /etc/news must be owned by root or news.
AC-6 - Medium - CCI-000225 - V-4277 - SV-4277r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN006340
Vuln IDs
  • V-4277
Rule IDs
  • SV-4277r2_rule
If critical system files are not owned by a privileged user, system integrity could be compromised.System AdministratorECLP-1
Checks: C-28776r1_chk

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

Fix: F-4188r2_fix

Change the ownership of the files in /etc/news to root or news. Procedure: # chown root /etc/news/*

b
The files in /etc/news must be group-owned by system or news.
AC-6 - Medium - CCI-000225 - V-4278 - SV-40837r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN006360
Vuln IDs
  • V-4278
Rule IDs
  • SV-40837r1_rule
If critical system files do not have a privileged group owner, system integrity could be compromised.System AdministratorECLP-1
Checks: C-39549r1_chk

Check /etc/news files group ownership. Procedure: # ls -al /etc/news If /etc/news files are not group-owned by system or news, this is a finding.

Fix: F-34681r1_fix

Change the group owner of the files in /etc/news to system or news. Procedure: # chgrp news /etc/news/*

b
The securetcpip command must be used.
AC-4 - Medium - CCI-000032 - V-4284 - SV-4284r2_rule
RMF Control
AC-4
Severity
Medium
CCI
CCI-000032
Version
GEN000000-AIX00040
Vuln IDs
  • V-4284
Rule IDs
  • SV-4284r2_rule
The AIX securetcpip command disables insecure network utilities, such as rcp, rlogin, rlogind, rsh, rshd, tftp, tftpd, and trpt/d. These services increase the attack surface of the system.System AdministratorECSC-1
Checks: C-2446r2_chk

The securetcpip command is in /etc. If it is not there, this is a finding. Perform: more /etc/security/config If the stanza below is not there, this is a finding. tcpip: netrc = ftp, rexec The stanza indicates the securetcpip command, which disables all the unsafe tcpip commands, (e.g., rsh, rlogin, tftp) has been executed.

Fix: F-33317r1_fix

Ensure secure tcp/ip has been invoked before allowing operations on the system.

b
A baseline of AIX files with the TCB bit set must be checked weekly.
SI-7 - Medium - CCI-001298 - V-4287 - SV-4287r2_rule
RMF Control
SI-7
Severity
Medium
CCI
CCI-001298
Version
GEN000000-AIX00060
Vuln IDs
  • V-4287
Rule IDs
  • SV-4287r2_rule
If a baseline of files with the TCB bit set is not kept and checked weekly, the system could be compromised without the knowledge of any authority.System AdministratorDCSL-1
Checks: C-2449r3_chk

Perform the following command with no parameters to ensure the system is in trusted mode. # /bin/tcbck If TCB is not installed, the output will show an error code of 3001-101 and/or a text message indicating TCB is not installed. If the output from the command indicates it is not in trusted mode, this is not reviewed. Otherwise, check the root crontab to verify tcbck is executed weekly. If it is not in the crontab, ask the SA if the check is run manually and to see the results of the check.

Fix: F-4198r2_fix

Add tcbck command as a weekly cronjob with the output sent to the SA.

c
The SSH daemon must be configured to only use the SSHv2 protocol.
AC-17 - High - CCI-001436 - V-4295 - SV-40862r1_rule
RMF Control
AC-17
Severity
High
CCI
CCI-001436
Version
GEN005500
Vuln IDs
  • V-4295
Rule IDs
  • SV-40862r1_rule
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.System AdministratorECSC-1, DCPP-1
Checks: C-39554r2_chk

Examine the sshd configuration file. # grep -i Protocol /etc/ssh/sshd_config If Protocol 2,1 or Protocol 1 are defined on a line without a leading comment, this is a finding.

Fix: F-4206r2_fix

Edit the configuration file and modify the Protocol line. Protocol 2 Restart sshd: /sbin/init.d/secsh stop /sbin/init.d/secsh start

b
Remote consoles must be disabled or protected from unauthorized access.
AC-17 - Medium - CCI-000070 - V-4298 - SV-27149r1_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-000070
Version
GEN001000
Vuln IDs
  • V-4298
Rule IDs
  • SV-27149r1_rule
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.System AdministratorECSC-1
Checks: C-28076r1_chk

Check /etc/security/login.cfg # more /etc/security/login.cfg If an alternate console is defined, this is a finding.

Fix: F-24423r1_fix

Edit /etc/security/login.cfg and remove the alternate console definition.

b
The system clock must be synchronized to an authoritative DoD time source.
AU-8 - Medium - CCI-001492 - V-4301 - SV-38666r1_rule
RMF Control
AU-8
Severity
Medium
CCI
CCI-001492
Version
GEN000240
Vuln IDs
  • V-4301
Rule IDs
  • SV-38666r1_rule
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 synchronizing 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. System AdministratorECSC-1
Checks: C-36610r2_chk

Verify if NTP running. # lssrc -s xntpd or # ps -ef | egrep "xntpd|ntpd" or # ntpq -p Verify xntpd is started at boot time and scheduled to run. #grep xntpd /etc/rc.tcpip | grep -v \# If NTP is running use the following command. # more /etc/ntp.conf and # ntpq -p Confirm the servers and peers or multicastclient (as applicable) are local or an authoritative U.S. DoD source. If a non-local/non-authoritative (U.S. DoD source) time-server is used, this is a finding.

Fix: F-31621r1_fix

Use a local authoritative time server that synchronizes to an authorized DoD time source. Ensure all systems in the facility feed from one or more local time servers feeding from the authoritative time server. View the (x)ntp/(x)ntpd man page(s). # man xntpd Create/edit the /etc/ntp.conf file, delete any non-local and/or non-US/DoD sources and insert the local or an authoritative US/DoD source. Start or restart the NTP service. # refresh -s xntpd OR # stopsrc -s xntpd # startsrc -s xntpd

b
The root file system must employ journaling or another mechanism ensuring file system consistency.
CP-10 - Medium - CCI-000553 - V-4304 - SV-38909r1_rule
RMF Control
CP-10
Severity
Medium
CCI
CCI-000553
Version
GEN003640
Vuln IDs
  • V-4304
Rule IDs
  • SV-38909r1_rule
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 consistency 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.System AdministratorECAR-2, ECAR-1, ECAR-3
Checks: C-36860r1_chk

Logging should be enabled for those types of files systems that do not turn on logging by default. Procedure: # mount #lsfs JFS, JFS2, 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 system types, if the root file system does not have the logging option, this is a finding. If the nolog option or the log=NULL option is set on the root file system, this is a finding.

Fix: F-4215r2_fix

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

b
The system must not run Samba unless needed.
AC-17 - Medium - CCI-001436 - V-4321 - SV-4321r2_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-001436
Version
GEN006060
Vuln IDs
  • V-4321
Rule IDs
  • SV-4321r2_rule
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.System AdministratorECSC-1, DCPD-1
Checks: C-2132r2_chk

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

Fix: F-4232r2_fix

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

b
Audit logs must be rotated daily.
CM-6 - Medium - CCI-000366 - V-4357 - SV-4357r2_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN002860
Vuln IDs
  • V-4357
Rule IDs
  • SV-4357r2_rule
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.System AdministratorECSC-1
Checks: C-8278r2_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-4268r2_fix

Configure a cron job or other automated process to rotate the audit logs on a daily basis.

b
The cron.deny file must have mode 0640 or less permissive.
AC-6 - Medium - CCI-000225 - V-4358 - SV-39874r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003200
Vuln IDs
  • V-4358
Rule IDs
  • SV-39874r1_rule
If file permissions for cron.deny are more permissive than 0640, sensitive information could be viewed or edited by unauthorized users.System AdministratorECLP-1
Checks: C-38876r1_chk

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

Fix: F-34020r1_fix

Change the mode of the cron.deny file. # chmod 0640 /var/adm/cron/cron.deny

a
Cron programs must not set the umask to a value less restrictive than 077.
AC-6 - Low - CCI-000225 - V-4360 - SV-27364r1_rule
RMF Control
AC-6
Severity
Low
CCI
CCI-000225
Version
GEN003220
Vuln IDs
  • V-4360
Rule IDs
  • SV-27364r1_rule
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.trueIf a cron program sets the umask to 000 or does not restrict the world-writable permission, this becomes a CAT I finding.System AdministratorECCD-2, ECCD-1
Checks: C-28508r1_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 &lt;crontab file&gt; # grep umask &lt;cron program&gt; 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.

Fix: F-4271r2_fix

Edit cron script files and modify the umask to 077.

b
The cron.allow file must be owned by root, bin, or sys.
AC-6 - Medium - CCI-000225 - V-4361 - SV-27367r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003240
Vuln IDs
  • V-4361
Rule IDs
  • SV-27367r1_rule
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.System AdministratorECLP-1
Checks: C-28511r1_chk

# ls -lL /var/adm/cron/cron.allow If the cron.allow file is not owned by root, sys, or bin, this is a finding.

Fix: F-24612r1_fix

# chown root /var/adm/cron/cron.allow

b
The at directory must have mode 0755 or less permissive.
AC-6 - Medium - CCI-000225 - V-4364 - SV-38907r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003400
Vuln IDs
  • V-4364
Rule IDs
  • SV-38907r1_rule
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.System AdministratorECLP-1
Checks: C-37215r1_chk

Check the mode of the at directory. # ls -lLd /var/spool/cron/atjobs If the directory mode is more permissive than 0755, this is a finding.

Fix: F-4275r2_fix

Change the mode of the "at" directory to 0755. Procedure: # chmod 0755 < at directory >

b
The at directory must be owned by root, bin, sys, daemon, or cron.
AC-6 - Medium - CCI-000225 - V-4365 - SV-39350r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003420
Vuln IDs
  • V-4365
Rule IDs
  • SV-39350r1_rule
If the owner of the at directory is not root, bin, sys, daemon, or cron unauthorized users could be allowed to view or edit files containing sensitive information within the directory.System AdministratorECLP-1
Checks: C-38296r1_chk

Check the ownership of the at directory. Procedure: # ls -ld /var/spool/cron/atjobs If the directory is not owned by root, bin, sys, daemon, or cron, this is a finding.

Fix: F-33584r1_fix

Change the owner of the at directory to root, bin, sys, daemon, or cron. Procedure: # chown bin /var/spool/cron/atjobs

b
"At" jobs must not set the umask to a value less restrictive than 077.
AC-6 - Medium - CCI-000225 - V-4366 - SV-4366r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003440
Vuln IDs
  • V-4366
Rule IDs
  • SV-4366r2_rule
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.trueSystem AdministratorInformation Assurance OfficerECCD-1, ECCD-2
Checks: C-8247r2_chk

Determine what "at" jobs exist on the system. Procedure: # ls /var/spool/cron/atjobs /var/spool/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 &lt;at job or referenced script&gt; If any "at" job or referenced script sets umask to a value more permissive than 077, this is a finding.

Fix: F-4277r2_fix

Edit "at" jobs or referenced scripts to remove umask commands setting umask to a value less restrictive than 077.

b
The at.allow file must be owned by root, bin, or sys.
AC-6 - Medium - CCI-000225 - V-4367 - SV-27393r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003460
Vuln IDs
  • V-4367
Rule IDs
  • SV-27393r1_rule
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.System AdministratorECLP-1
Checks: C-28556r1_chk

# ls -lL /var/adm/cron/at.allow If the at.allow file is not owned by root, sys, or bin, this is a finding.

Fix: F-24641r1_fix

Change the owner of the at.allow file. # chown root /var/adm/cron/at.allow

b
The at.deny file must be owned by root, bin, or sys.
AC-6 - Medium - CCI-000225 - V-4368 - SV-27397r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003480
Vuln IDs
  • V-4368
Rule IDs
  • SV-27397r1_rule
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.System AdministratorECLP-1
Checks: C-28560r1_chk

# ls -lL /var/adm/cron/at.deny If the at.deny file is not owned by root, sys, or bin, this is a finding.

Fix: F-24645r1_fix

Change the owner of the at.deny file. # chown root /var/adm/cron/at.deny

b
The traceroute command owner must be root.
AC-6 - Medium - CCI-000225 - V-4369 - SV-28393r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003960
Vuln IDs
  • V-4369
Rule IDs
  • SV-28393r1_rule
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.System AdministratorECLP-1
Checks: C-28630r1_chk

# ls -lL /usr/bin/traceroute If the traceroute command is not owned by root, this is a finding.

Fix: F-25665r1_fix

Change the owner of the traceroute command to root. Example: # chown root /usr/bin/traceroute

b
The traceroute command must be group-owned by sys, bin, or system.
AC-6 - Medium - CCI-000225 - V-4370 - SV-28397r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003980
Vuln IDs
  • V-4370
Rule IDs
  • SV-28397r1_rule
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.System AdministratorECLP-1
Checks: C-28633r1_chk

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

Fix: F-25668r1_fix

Change the group owner of the traceroute command to sys, bin, or system. Procedure: # chgrp system /usr/bin/traceroute

b
The traceroute file must have mode 0700 or less permissive.
AC-6 - Medium - CCI-000225 - V-4371 - SV-28400r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN004000
Vuln IDs
  • V-4371
Rule IDs
  • SV-28400r1_rule
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 possibly leading to system and network compromise.System AdministratorECLP-1
Checks: C-28636r1_chk

# ls -lL /usr/bin/traceroute If the traceroute command has a mode more permissive than 0700, this is a finding.

Fix: F-25671r1_fix

Change the mode of the traceroute command. # chmod 0700 /usr/bin/traceroute

c
Administrative accounts must not run a web browser, except as needed for local service administration.
AC-6 - High - CCI-000225 - V-4382 - SV-4382r2_rule
RMF Control
AC-6
Severity
High
CCI
CCI-000225
Version
GEN004220
Vuln IDs
  • V-4382
Rule IDs
  • SV-4382r2_rule
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.System AdministratorECLP-1
Checks: C-8266r2_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-4293r2_fix

Enforce policy requiring administrative accounts use web browsers only for local service administration.

a
The SMTP service's SMTP greeting must not provide version information.
CM-6 - Low - CCI-000366 - V-4384 - SV-39164r1_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GEN004560
Vuln IDs
  • V-4384
Rule IDs
  • SV-39164r1_rule
The version of the SMTP service can be used by attackers to plan an attack based on vulnerabilities present in the specific version.System AdministratorECSC-1
Checks: C-38146r1_chk

Check for the Sendmail version being displayed in the greeting. # telnet localhost 25 If a version number is displayed, this is a finding.

Fix: F-33419r1_fix

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

b
The system must not use .forward files.
CM-6 - Medium - CCI-000366 - V-4385 - SV-4385r2_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN004580
Vuln IDs
  • V-4385
Rule IDs
  • SV-4385r2_rule
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.System AdministratorECSC-1
Checks: C-8268r2_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-4296r2_fix

Remove .forward files from the system.

c
Anonymous FTP accounts must not have a functional shell.
AC-6 - High - CCI-000225 - V-4387 - SV-4387r2_rule
RMF Control
AC-6
Severity
High
CCI
CCI-000225
Version
GEN005000
Vuln IDs
  • V-4387
Rule IDs
  • SV-4387r2_rule
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.System AdministratorECCD-1, ECCD-2
Checks: C-8269r2_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-4298r2_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.

b
If the system is a Network Management System (NMS) server, it must only run the NMS and any software required by the NMS.
SC-32 - Medium - CCI-001208 - V-4392 - SV-4392r2_rule
RMF Control
SC-32
Severity
Medium
CCI
CCI-001208
Version
GEN005380
Vuln IDs
  • V-4392
Rule IDs
  • SV-4392r2_rule
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.System AdministratorDCPA-1
Checks: C-8271r2_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-4303r2_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.

b
The /etc/syslog.conf file must be owned by root.
AC-6 - Medium - CCI-000225 - V-4393 - SV-4393r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN005400
Vuln IDs
  • V-4393
Rule IDs
  • SV-4393r2_rule
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.System AdministratorECLP-1
Checks: C-8272r2_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-4304r2_fix

Use the chown command to set the owner to root. # chown root /etc/syslog.conf

b
The /etc/syslog.conf file must be group-owned by bin, sys, or system.
AC-6 - Medium - CCI-000225 - V-4394 - SV-40364r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN005420
Vuln IDs
  • V-4394
Rule IDs
  • SV-40364r1_rule
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.System AdministratorECLP-1
Checks: C-39246r1_chk

Check /etc/syslog.conf group ownership. Procedure: # ls -lL /etc/syslog.conf If /etc/syslog.conf is not group-owned by sys, bin, or system, this is a finding.

Fix: F-34348r1_fix

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

b
The system must only use remote syslog servers (log hosts) justified and documented using site-defined procedures.
CM-6 - Medium - CCI-000366 - V-4395 - SV-4395r2_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN005460
Vuln IDs
  • V-4395
Rule IDs
  • SV-4395r2_rule
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.trueSystem AdministratorInformation Assurance OfficerECSC-1
Checks: C-8274r2_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-4306r3_fix

Remove, replace, or document the referenced undocumented log host.

b
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-4397 - SV-39217r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN005560
Vuln IDs
  • V-4397
Rule IDs
  • SV-39217r1_rule
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.System AdministratorECSC-1
Checks: C-8275r2_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-33468r1_fix

Set a default gateway for IPv4. # smitty route OR # route add 0 < ip address of gateway >

b
A system used for routing must not run other network services or applications.
SC-32 - Medium - CCI-001208 - V-4398 - SV-4398r2_rule
RMF Control
SC-32
Severity
Medium
CCI
CCI-001208
Version
GEN005580
Vuln IDs
  • V-4398
Rule IDs
  • SV-4398r2_rule
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.System AdministratorDCSP-1
Checks: C-8276r2_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-4309r2_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.

c
The system must not use UDP for NIS/NIS+.
AC-17 - High - CCI-001436 - V-4399 - SV-4399r2_rule
RMF Control
AC-17
Severity
High
CCI
CCI-001436
Version
GEN006380
Vuln IDs
  • V-4399
Rule IDs
  • SV-4399r2_rule
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.System AdministratorECSC-1
Checks: C-8277r2_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-4310r2_fix

Configure the system to not use UDP for NIS and NIS+. Consult vendor documentation for the required procedure.

b
All .rhosts, .shosts, or host.equiv files must only contain trusted host-user pairs.
CM-6 - Medium - CCI-000366 - V-4427 - SV-4427r2_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN002020
Vuln IDs
  • V-4427
Rule IDs
  • SV-4427r2_rule
If these files are not properly configured, they could allow malicious access by unknown malicious users from untrusted hosts who could compromise the system.G614. The only allowable use of a’ +’ character in a hosts.equiv and .rhosts files is to allow NIS+ netgroups access to the system.System AdministratorECCD-2, ECCD-1
Checks: C-8219r2_chk

Locate and examine all .rhosts, .shosts, hosts.equiv, and shosts.equiv files. Procedure: # find / -name .rhosts # more /&lt;directorylocation&gt;/.rhosts # find / -name .shosts # more /&lt;directorylocation&gt;/.shosts # find / -name hosts.equiv # more /&lt;directorylocation&gt;/hosts.equiv # find / -name shosts.equiv # more /&lt;directorylocation&gt;/shosts.equiv If any .rhosts, .shosts, hosts.equiv, or shosts.equiv file contains other than host-user pairs, this is a finding.

Fix: F-4326r2_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.

b
All .rhosts, .shosts, .netrc, or hosts.equiv files must be accessible by only root or the owner.
AC-6 - Medium - CCI-000225 - V-4428 - SV-39502r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002060
Vuln IDs
  • V-4428
Rule IDs
  • SV-39502r1_rule
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.System AdministratorECLP-1
Checks: C-8220r2_chk

# find / -type f -name .rhosts # ls -alL /&lt;directorylocation&gt;/.rhosts # find / -type f -name .shosts # ls -alL /&lt;directorylocation&gt;/.shosts # find / -type f -name hosts.equiv # ls -lL /&lt;directorylocation&gt;/hosts.equiv # find / -type f -name shosts.equiv # ls -lL /&lt;directorylocation&gt;/shosts.equiv If the .rhosts, .shosts, hosts.equiv, or shosts.equiv files have permissions greater than 700, this is a finding.

Fix: F-4327r2_fix

Ensure the permission for these files is set at 700 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 which is in /etc and owned by root), have no meaning.

b
The cron.deny file must be owned by root, bin, or sys.
AC-6 - Medium - CCI-000225 - V-4430 - SV-27372r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003260
Vuln IDs
  • V-4430
Rule IDs
  • SV-27372r1_rule
Cron daemon control files restrict the scheduling of automated tasks and must be protected. System AdministratorECLP-1
Checks: C-28524r1_chk

# ls -lL /var/adm/cron/cron.deny If the cron.deny file is not owned by root, sys, or bin, this is a finding.

Fix: F-24618r1_fix

# chown root /var/adm/cron/cron.deny

c
The rsh daemon must not be running.
AC-17 - High - CCI-000068 - V-4687 - SV-27434r1_rule
RMF Control
AC-17
Severity
High
CCI
CCI-000068
Version
GEN003820
Vuln IDs
  • V-4687
Rule IDs
  • SV-27434r1_rule
The rshd process provides a typically unencrypted, host-authenticated remote access service. SSH should be used in place of this service. System AdministratorInformation Assurance OfficerEBRU-1
Checks: C-28620r1_chk

# grep -v "^#" /etc/inetd.conf |grep rshd If rshd is found to be enabled, this is a finding.

Fix: F-24706r1_fix

Edit /etc/inetd.conf and comment out the rshd service. Restart the inetd service.

c
The rexec daemon must not be running.
AC-17 - High - CCI-001435 - V-4688 - SV-38878r1_rule
RMF Control
AC-17
Severity
High
CCI
CCI-001435
Version
GEN003840
Vuln IDs
  • V-4688
Rule IDs
  • SV-38878r1_rule
The rexecd process provides a typically unencrypted, host-authenticated remote access service. SSH should be used in place of this service.trueInformation Assurance OfficerSystem AdministratorECSC-1, EBRP-1
Checks: C-37883r1_chk

# grep -v "^#" /etc/inetd.conf |grep rexec If any results are returned, this is a finding.

Fix: F-33130r1_fix

Edit /etc/inetd.conf and comment out the line for the rexec service. Refresh the inetd daemon. # refresh -s inetd

c
The SMTP service must be an up-to-date version.
SI-2 - High - CCI-001230 - V-4689 - SV-38917r1_rule
RMF Control
SI-2
Severity
High
CCI
CCI-001230
Version
GEN004600
Vuln IDs
  • V-4689
Rule IDs
  • SV-38917r1_rule
The SMTP service version on the system must be current to avoid exposing vulnerabilities present in unpatched versions.System AdministratorVIVM-1
Checks: C-36887r2_chk

Determine the version of the SMTP service software. Locate the sendmail daemon. Procedure: # find / -name sendmail Obtain version information for the Sendmail daemon. Procedure: # what &lt; file location &gt; OR # strings &lt; file location &gt; | grep version OR # echo \$Z | sendmail -d0 Version 8.14.5 is the latest released version. If the Sendmail version is not at least 8.14.5 or the vendor's latest version, this is a finding.

Fix: F-33422r1_fix

Obtain and install a newer version of Sendmail from the operating system vendor or from http://www.sendmail.org or ftp://ftp.cs.berkeley.edu/ucb/sendmail.

c
The Sendmail server must have the debug feature disabled.
CM-6 - High - CCI-000366 - V-4690 - SV-4690r2_rule
RMF Control
CM-6
Severity
High
CCI
CCI-000366
Version
GEN004620
Vuln IDs
  • V-4690
Rule IDs
  • SV-4690r2_rule
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.System AdministratorECSC-1
Checks: C-652r3_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 installed on the system. # echo \$Z | /usr/sbin/sendmail -bt -d0 If the sendmail reported version is less than 8.6, this is a finding.

Fix: F-4618r2_fix

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

c
The SMTP service must not have a uudecode alias active.
SI-2 - High - CCI-001230 - V-4691 - SV-4691r2_rule
RMF Control
SI-2
Severity
High
CCI
CCI-001230
Version
GEN004640
Vuln IDs
  • V-4691
Rule IDs
  • SV-4691r2_rule
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.System AdministratorECSC-1
Checks: C-653r2_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.

Fix: F-4619r2_fix

Disable mail aliases for decode and uudecode. If the /etc/aliases or /usr/lib/aliases (mail alias) file contains entries for these programs, remove them or disable them by placing # at the beginning of the line, and then executing the "newaliases" command. For more information on mail aliases, refer to the man page for aliases. Disabled aliases would be similar to the examples below: # decode: |/usr/bin/uudecode # uudecode: |/usr/bin/uuencode -d

a
The SMTP service must not have the EXPN feature active.
CM-6 - Low - CCI-000366 - V-4692 - SV-28402r1_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GEN004660
Vuln IDs
  • V-4692
Rule IDs
  • SV-28402r1_rule
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 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 a false positive is suspected, check the log file for the response from the server.System AdministratorECSC-1
Checks: C-655r2_chk

Perform the following to determine if EXPN is disabled: # 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 by: # find / -name sendmail.cf -print # grep -v "^#" &lt;sendmail.cf location&gt; |grep -i privacyoptions The O PrivacyOptions should have the noexpn or the goaway option (covering both noexpn and novrfy). If the EXPN command is not disabled, this is a finding.

Fix: F-25673r1_fix

Edit the sendmail.cf file and add or edit the following line: O PrivacyOptions=goaway Restart the Sendmail service.

a
The SMTP service must not have the VRFY feature active.
CM-6 - Low - CCI-000366 - V-4693 - SV-39171r1_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GEN004680
Vuln IDs
  • V-4693
Rule IDs
  • SV-39171r1_rule
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.System AdministratorECSC-1
Checks: C-38150r1_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 "^#" |grep -i vrfy Ensure the VRFY command is disabled with an entry in the sendmail.cf file. The entry could be any one of Opnovrfy, novrfy, or goaway, which could also have other options included, such as noexpn. The goaway argument encompasses many things, such as novrfy and noexpn. If no setting to disable VRFY is found, this is a finding.

Fix: F-33425r1_fix

If you are running Sendmail, add the line Opnovrfy to your 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.

a
The Sendmail service must not have the wizard backdoor active.
CM-6 - Low - CCI-000366 - V-4694 - SV-4694r2_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GEN004700
Vuln IDs
  • V-4694
Rule IDs
  • SV-4694r2_rule
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.System AdministratorECSC-1
Checks: C-706r2_chk

Locate the sendmail.cf configuration file and check for wiz configuration. Procedure: # find / -name sendmail.cf -print # grep -v "^#" &lt;sendmail.cf location&gt; |grep -i wiz If an entry is found for wiz, this is a finding.

Fix: F-4622r2_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.

c
Any active TFTP daemon must be authorized and approved in the system accreditation package.
AC-6 - High - CCI-000225 - V-4695 - SV-39193r1_rule
RMF Control
AC-6
Severity
High
CCI
CCI-000225
Version
GEN005140
Vuln IDs
  • V-4695
Rule IDs
  • SV-39193r1_rule
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.System AdministratorInformation Assurance OfficerDCSW-1
Checks: C-38171r1_chk

Determine if the TFTP daemon is active. # grep -v "^#" /etc/inetd.conf |grep tftp If TFTP is found enabled, it is a finding if it is not documented using site-defined procedures.

Fix: F-33446r1_fix

Disable the TFTP daemon. Edit /etc/inetd.conf and comment out the tftp line. Restart the inetd service. # refresh -s inetd

b
The system must not have the UUCP service active.
AC-17 - Medium - CCI-001436 - V-4696 - SV-28427r1_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-001436
Version
GEN005280
Vuln IDs
  • V-4696
Rule IDs
  • SV-28427r1_rule
The UUCP utility is designed to assist in transferring files, executing remote commands, and sending e-mail 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.System AdministratorECSC-1
Checks: C-28692r1_chk

# grep uucp /etc/inetd.conf If uucp is found enabled, this is a finding.

Fix: F-25720r1_fix

Edit /etc/inetd.conf and comment out the uucp service. Restart the inetd service.

c
X displays must not be exported to the world.
AC-6 - High - CCI-000225 - V-4697 - SV-4697r2_rule
RMF Control
AC-6
Severity
High
CCI
CCI-000225
Version
GEN005200
Vuln IDs
  • V-4697
Rule IDs
  • SV-4697r2_rule
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.System AdministratorECSC-1
Checks: C-719r2_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-4625r2_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.

a
The system must not have the finger service active.
AC-4 - Low - CCI-001551 - V-4701 - SV-27440r1_rule
RMF Control
AC-4
Severity
Low
CCI
CCI-001551
Version
GEN003860
Vuln IDs
  • V-4701
Rule IDs
  • SV-27440r1_rule
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. System AdministratorDCPP-1, EBRU-1
Checks: C-28626r1_chk

# grep -v "^#" /etc/inetd.conf |grep finger If the finger service is not disabled, this is a finding.

Fix: F-24712r1_fix

Edit /etc/inetd.conf and comment out the finger service line. Restart the inetd service.

b
If the system is an anonymous FTP server, it must be isolated to the DMZ network.
IA-4 - Medium - CCI-000787 - V-4702 - SV-4702r2_rule
RMF Control
IA-4
Severity
Medium
CCI
CCI-000787
Version
GEN004840
Vuln IDs
  • V-4702
Rule IDs
  • SV-4702r2_rule
Anonymous FTP is a public data service which is only permitted in a server capacity when located on the DMZ network.System AdministratorInformation Assurance OfficerEBBD-2, EBBD-1, ECSC-1, EBBD-3
Checks: C-712r2_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-4630r2_fix

Move the system to a DMZ network.

c
The operating system must be a supported release.
SI-2 - High - CCI-001230 - V-11940 - SV-27052r1_rule
RMF Control
SI-2
Severity
High
CCI
CCI-001230
Version
GEN000100
Vuln IDs
  • V-11940
Rule IDs
  • SV-27052r1_rule
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.If an extended support agreement providing security patches for the unsupported product is procured from the vendor, this finding may be downgraded to a CAT III.System AdministratorVIVM-1
Checks: C-36589r1_chk

# oslevel Vendor supported versions are 5.3 and later at the time of writing. AIX 5.3 End of support 30 April 2012 AIX 5.2 End of support 30 April 2009 AIX 5.1 End of support 1 April 2006 If the release is not supported, this is a finding.

Fix: F-11211r2_fix

Upgrade to a supported version of the operating system.

b
A file integrity baseline must be created and maintained.
CM-2 - Medium - CCI-000293 - V-11941 - SV-38784r1_rule
RMF Control
CM-2
Severity
Medium
CCI
CCI-000293
Version
GEN000140
Vuln IDs
  • V-11941
Rule IDs
  • SV-38784r1_rule
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.System AdministratorDCSW-1
Checks: C-7918r2_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-31619r1_fix

Create a file integrity baseline, including cryptographic hashes, for the system. # find / -depth -print | tee Baseline Open the above file and either manually execute md5sum, csum, or the chksum command on each file. Alternatively, write a script to perform the above. NOTE: For security purposes, "md5sum" is preferred over "chksum". The md5sum command can be loaded from the Linux Tool Kit for AIX. Alternatively, OpenSSL can be used to create hashes. #openssl dgst -md5 < file >

b
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.
RA-5 - Medium - CCI-001069 - V-11945 - SV-28610r1_rule
RMF Control
RA-5
Severity
Medium
CCI
CCI-001069
Version
GEN000220
Vuln IDs
  • V-11945
Rule IDs
  • SV-28610r1_rule
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: For MAC I systems, increase the frequency to daily.System AdministratorDCSL-1
Checks: C-28849r2_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: For MAC I systems, increase the frequency to daily.

Fix: F-25883r2_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: For MAC I systems, increase the frequency to daily.

b
UIDs reserved for system accounts must not be assigned to non-system accounts.
CM-6 - Medium - CCI-000366 - V-11946 - SV-38669r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN000340
Vuln IDs
  • V-11946
Rule IDs
  • SV-38669r1_rule
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. System AdministratorECSC-1
Checks: C-36661r1_chk

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

Fix: F-31625r1_fix

Using the usermod command, change the UID numbers for non-system accounts with reserved UIDs (those less or equal to 128). # usermod -u <uid> login Alternatively, smit can be used for this same purpose. #smitty users

b
The system must require passwords to contain a minimum of 14 characters.
IA-5 - Medium - CCI-000205 - V-11947 - SV-38936r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000205
Version
GEN000580
Vuln IDs
  • V-11947
Rule IDs
  • SV-38936r1_rule
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.System AdministratorIAIA-2, IAIA-1
Checks: C-28028r1_chk

Check the system password length setting. # /usr/sbin/lsuser -a minlen ALL If minlen is not set to 14 or more, this is a finding.

Fix: F-31635r1_fix

Change the minimum password length to 14 or more. # chsec -f /etc/security/user -s default -a minlen=14 # chuser minlen=14 <user id>

b
The system must require that passwords contain at least one special character.
IA-5 - Medium - CCI-001619 - V-11973 - SV-39503r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-001619
Version
GEN000640
Vuln IDs
  • V-11973
Rule IDs
  • SV-39503r1_rule
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.System AdministratorIAIA-2, IAIA-1
Checks: C-38421r1_chk

Check the minother setting. Procedure: # grep minother /etc/security/user OR # lsuser -a minother ALL If the minother setting is less than 1, this is a finding.

Fix: F-33711r1_fix

Use the chsec command to set the minother setting to 1. # chsec -f /etc/security/user -s default -a minother=1 # chuser minother=1 < user id >

b
The system must require passwords to contain no more than three consecutive repeating characters.
CM-6 - Medium - CCI-000366 - V-11975 - SV-38675r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN000680
Vuln IDs
  • V-11975
Rule IDs
  • SV-38675r1_rule
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.System AdministratorIAIA-1, IAIA-2
Checks: C-36902r1_chk

Check the maxrepeats setting. Procedure: # grep -i maxrepeats /etc/security/user OR # lsuser -a maxrepeats ALL If the maxrepeats setting is greater than 3, this is a finding.

Fix: F-32056r1_fix

Use the chsec command to set maxrepeats to 3. # chsec -f /etc/security/user -s default -a maxrepeats=3 # chuser maxrepeats=3 < user id >

b
User passwords must be changed at least every 60 days.
IA-5 - Medium - CCI-000180 - V-11976 - SV-38939r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000180
Version
GEN000700
Vuln IDs
  • V-11976
Rule IDs
  • SV-38939r1_rule
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.System AdministratorIAIA-2, IAIA-1
Checks: C-28049r1_chk

Check the maxage field for each user. The field represents the number of weeks a password is valid. Procedure: # /usr/sbin/lsuser -a maxage ALL If the maxage field is 0 or greater than 8 for any user, this is a finding.

Fix: F-32059r1_fix

Use the chsec command to set the maxage field to 8 for each user. # chsec -f /etc/security/user -s default -a maxage=8 # chuser maxage=8 < user id >

b
All non-interactive/automated processing account passwords must be changed at least once per year or be locked.
IA-5 - Medium - CCI-000199 - V-11977 - SV-38676r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000199
Version
GEN000740
Vuln IDs
  • V-11977
Rule IDs
  • SV-38676r1_rule
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.System AdministratorIAIA-2, IAIA-1
Checks: C-36905r1_chk

NOTE: This will always require a manual review. This is a local policy issue/question. 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 the SA indicates passwords for automated processing accounts are not changed once per year, this is a finding. Procedure: Go to last password change date for the system account. # grep -p &lt;account_name&gt; /etc/security/passwd | grep lastupdate To examine the time a password was last changed, the following perl script has been provided. Put the lastupdate value in the &lt;lastupdate&gt;. #perl -e 'use POSIX; print strftime("%c\n" , localtime(&lt;lastupdate&gt;));'

Fix: F-32066r1_fix

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

b
The root account must not be used for direct logins.
IA-2 - Medium - CCI-000770 - V-11979 - SV-40787r1_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000770
Version
GEN001020
Vuln IDs
  • V-11979
Rule IDs
  • SV-40787r1_rule
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.System AdministratorECPA-1
Checks: C-39527r1_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.

Fix: F-11240r3_fix

Enforce policy requiring all root account access is attained by first logging into a user account and then becoming root (using su, for example).

b
The system must log successful and unsuccessful access to the root account.
AU-2 - Medium - CCI-000126 - V-11980 - SV-27154r1_rule
RMF Control
AU-2
Severity
Medium
CCI
CCI-000126
Version
GEN001060
Vuln IDs
  • V-11980
Rule IDs
  • SV-27154r1_rule
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.System AdministratorECAR-2, ECAR-1, ECAR-3
Checks: C-28084r1_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-11241r2_fix

Troubleshoot the system logging configuration to provide for logging of root account login attempts.

b
All global initialization files must have mode 0644 or less permissive.
AC-6 - Medium - CCI-000225 - V-11981 - SV-38882r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001720
Vuln IDs
  • V-11981
Rule IDs
  • SV-38882r1_rule
Global initialization files are used to configure the user's shell environment upon login. Malicious modification of these files could compromise accounts upon logon.System AdministratorECLP-1
Checks: C-37157r1_chk

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

Fix: F-11242r2_fix

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

b
All global initialization files must be owned by root.
AC-6 - Medium - CCI-000225 - V-11982 - SV-38884r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001740
Vuln IDs
  • V-11982
Rule IDs
  • SV-38884r1_rule
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.System AdministratorECLP-1
Checks: C-37161r1_chk

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

Fix: F-11243r2_fix

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

b
All global initialization files must be group-owned by sys, bin, system, or security.
AC-6 - Medium - CCI-000225 - V-11983 - SV-38892r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001760
Vuln IDs
  • V-11983
Rule IDs
  • SV-38892r1_rule
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.System AdministratorECLP-1
Checks: C-37162r1_chk

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

Fix: F-33353r1_fix

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

b
All skeleton files and directories (typically in /etc/skel) must be owned by root or bin.
AC-6 - Medium - CCI-000225 - V-11984 - SV-38737r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001820
Vuln IDs
  • V-11984
Rule IDs
  • SV-38737r1_rule
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 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.System AdministratorECLP-1
Checks: C-37238r1_chk

Check skeleton files ownership. Procedure: # ls -l /etc/security/.profile /etc/security/mkuser.sys If a skeleton file is not owned by root or bin, this is a finding.

Fix: F-32452r1_fix

Change the ownership of skeleton files with incorrect mode. # chown root /etc/security/.profile /etc/security/mkuser.sys

b