HP-UX 11.23 Security Technical Implementation Guide

  • Version/Release: V1R8
  • Published: 2015-12-02
  • 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 HP-UX 11.23 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 e-mail to the following address: disa.stig_spt@mail.mil.
b
The system must require authentication upon booting into single-user and maintenance modes.
AC-3 - Medium - CCI-000213 - V-756 - SV-38318r2_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
GEN000020
Vuln IDs
  • V-756
Rule IDs
  • SV-38318r2_rule
Single user mode access must be strictly limited to privileged users. The ability to boot to single user mode allows a malicious user the opportunity to modify, compromise, or otherwise damage the system.System AdministratorIAIA-2, IAIA-1
Checks: C-36228r2_chk

Check the /tcb/files/auth/system/default entry. # grep “:d_boot_authenticate” /tcb/files/auth/system/default If the returned entry looks like “:d_boot_authenticate@:”, single user boot authentication is disabled, and this is a finding. For SMSE: Check the setting for BOOT_AUTH is set to N=1. # grep BOOT_AUTH /etc/default/security /var/adm/userdb/* If BOOT_AUTH=0, then single user boot authentication is disabled, and this is a finding.

Fix: F-31487r2_fix

For Trusted Mode: If single user boot authentication is disabled, use the System Administration Manager (SAM) or the System Management Homepage (SMH) to enable single user boot (for root only) authentication. For SMSE: Note: There may be additional package/bundle updates that must be installed to support attributes in the /etc/default/security file. Use the SAM/SMH interface (/etc/default/security file) and/or the userdbset command (/var/adm/userdb/* files) to update the attribute. See the below example: BOOT_AUTH=1 Note: Never use a text editor to modify any /var/adm/userdb database file. The database contains checksums and other binary data, and editors (vi included) do not follow the file locking conventions that are used to control access to the database. If manually editing the /etc/default/security file, save any change(s) before exiting the editor."

b
Direct logins must not be permitted to share, default, application, or utility accounts.
IA-2 - Medium - CCI-000770 - V-760 - SV-38441r1_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000770
Version
GEN000280
Vuln IDs
  • V-760
Rule IDs
  • SV-38441r1_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-36244r1_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>

Fix: F-31501r1_fix

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

b
All accounts on the system must have unique user or account names.
IA-2 - Medium - CCI-000764 - V-761 - SV-38442r2_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000764
Version
GEN000300
Vuln IDs
  • V-761
Rule IDs
  • SV-38442r2_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-36245r4_chk

Verify the consistency of the assigned home directories in the authentication database. For Trusted Mode: # authck -av For SMSE: # pwck If any duplicate account names are found, this is a finding.

Fix: F-31502r2_fix

Determine if the duplicate accounts have the same or different UIDs. # cat /etc/passwd | cut -f 1,1 -d “:” | sort | uniq -d If the UIDs are different, the account name must be changed. If the UIDs are the same, disable/remove one of the two (or more) password file entries via the SAM/SMH interface.

b
All accounts must be assigned unique User Identification Numbers (UIDs).
IA-2 - Medium - CCI-000764 - V-762 - SV-38443r2_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000764
Version
GEN000320
Vuln IDs
  • V-762
Rule IDs
  • SV-38443r2_rule
Accounts sharing a UID have full access to each others' files. This has the same effect as sharing a login. There is no way to assure identification, authentication, and accountability because the system sees them as the same user. If the duplicate UID is 0, this gives potential intruders another privileged account to attack.System AdministratorIAIA-1, IAIA-2
Checks: C-36246r2_chk

Verify the consistency of the assigned home directories in the authentication database. For Trusted Mode: # authck -av For SMSE: # pwck If a non-unique UID is found in the password file, this is a finding.

Fix: F-31503r2_fix

Determine if the duplicate UIDs are associated with the same or a different account name. # cat /etc/passwd | grep <non-uniqueUID> or, for multiple non-unique UIDs: # cat /etc/passwd | egrep “<non-uniqueUID1>|<non-uniqueUID2>|,non-uniqueUIDn>“ If the account names are unique, the UIDs must also be modified to be unique. If the account names are the same, disable/remove one of the two (or more) password file entries via the SAM/SMH interface. .

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

NOTE: This will virtually always require a manual review. Access the system console and make a login 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-31504r1_fix

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

b
Successful and unsuccessful logins and logouts must be logged.
AU-2 - Medium - CCI-000126 - V-765 - SV-27082r1_rule
RMF Control
AU-2
Severity
Medium
CCI
CCI-000126
Version
GEN000440
Vuln IDs
  • V-765
Rule IDs
  • SV-27082r1_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-2, ECAR-3, ECAR-1
Checks: C-27995r1_chk

List the logged successful logons to determine if successful logons are being logged. # last -R | more List the logged unsuccessful logons to determine if unsuccessful logons are being logged. # lastb -R | more If logs do not contain successful and unsuccessful logins, this is a finding.

Fix: F-31505r1_fix

Verify that login logs are handled correctly in the /etc/syslog.conf file. Verify that service startup scripts for syslog and (w/b)tmp (if present) are enabled. NOTE: Also examine the syslog.conf file for any references to remote log hosts if last/lastb produce no results. # cat /etc/syslog.conf | tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' | grep -v '^#' | grep "\@"

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

For Trusted Mode: The u_maxtries attribute in the /tcb/files/auth/system/default file controls whether an account is locked after too many consecutive authentication failures. An account is locked after “N” consecutive authentication failures. Check the global setting for u_maxtries is set to N=3. # grep u_maxtries /tcb/files/auth/system/default If the u_maxtries attribute is not set to 3, this is a finding. For SMSE: The AUTH_MAXTRIES attribute in the /etc/default/security configuration file controls whether an account is locked after too many consecutive authentication failures. An account is locked after N+1 consecutive authentication failures. Check the setting for AUTH_MAXTRIES is set to N=2. # grep AUTH_MAXTRIES /etc/default/security /var/adm/userdb/* If the attribute AUTH_MAXTRIES is not set to 2, this is a finding.

Fix: F-31506r2_fix

For Trusted Mode: Use the SAM/SMH interface or edit the /tcb/files/auth/system/default file and update the u_maxtries attribute. See the below example: :u_maxtries#3: If manually editing the file, save any change(s) before exiting the editor. For SMSE: Note: There may be additional package/bundle updates that must be installed to support attributes in the /etc/default/security file. Use the SAM/SMH interface (/etc/default/security file) and/or the userdbset command (/var/adm/userdb/* files) to update the attribute. See the below example: AUTH_MAXTRIES=2 Note: Never use a text editor to modify any /var/adm/userdb database file. The database contains checksums and other binary data, and editors (vi included) do not follow the file locking conventions that are used to control access to the database. If manually editing the /etc/default/security file, save any change(s) before exiting the editor.

b
The delay between login prompts following a failed login attempt must be at least 4 seconds.
AC-7 - Medium - CCI-002238 - V-768 - SV-38446r3_rule
RMF Control
AC-7
Severity
Medium
CCI
CCI-002238
Version
GEN000480
Vuln IDs
  • V-768
Rule IDs
  • SV-38446r3_rule
Enforcing a delay between consecutive failed login attempts increases protection against automated password guessing attacks.GEN000480Attack mitigations to minimize risk: 1. Ensure that the “nodelay” parameter is not found in the /etc/pam.conf file. 2. In the file /opt/ssh/etc/sshd_config, the “MaxAuthTries” attribute must be explicitly set to “1”. This attribute controls the maximum number of authentication attempts permitted per SSH daemon connection. 3. In the file /opt/ssh/etc/sshd_config, the “MaxStartups” attribute must be explicitly set to an organization defined value of “10” (the default) or less. This attribute controls the maximum number of unauthenticated connections to the SSH daemon. 4. IPFilter DCA mode is disabled by default, and must be explicitly enabled. Set the following attribute in the /etc/rc.config.d/ipfconf file: DCA_START=1 The below /etc/opt/ipf/ipf.conf file rule specifies a connection limit of ““ for all hosts when attempting to connect to port ““. The ““ and ““ must be set to organization defined values. Per vendor documentation, this rule must be the next-to-last rule in /etc/opt/ipf/ipf.conf. The final rule in the file must define the default connection limit. See the below example for the last 2 line entries in /etc/opt/ipf/ipf.conf (note that the double quotes are for emphasis only): “pass in proto tcp from any to any port = keep limit “ “block in from any to any” Save the file before exiting the editor. The system should not require restarting for the new rule(s) to take effect. System AdministratorECLO-1, ECLO-2
Checks: C-36250r2_chk

For Trusted Mode: Check the t_logdelay setting. # more /tcb/files/auth/system/default Verify the value of the t_logdelay variable. If the value is less than 4, this is a finding. For SMSE: By default, PAM executes a built-in, 3 second standard delay if user authentication fails. This delay cannot be extended. The “nodelay” parameter disables the built-in delay. Ensure that the “nodelay” parameter is not found in the /etc/pam.conf file. The HP-SMSE environment does not meet the failed authentication 4 second minimum delay requirement. This check will always result in a finding.

Fix: F-31507r2_fix

For Trusted Mode: Use the SAM/SMH interface to ensure that the t_logdelay setting is 4. For SMSE: There is no fix, however, there are attack mitigations to minimize risk (see mitigations).

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-38447r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN000520
Vuln IDs
  • V-769
Rule IDs
  • SV-38447r1_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-36251r1_chk

NOTE: This will virtually always require a manual review. If there is an application running on the system that is continuously in use (such as a network monitoring application), ask the SA what the name of the application is. Execute ps -ef | more to determine which user owns the process(es) associated with the application. If the owner is root, this is a finding.

Fix: F-31508r1_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 and 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-38448r2_rule
RMF Control
CM-6
Severity
High
CCI
CCI-000366
Version
GEN000560
Vuln IDs
  • V-770
Rule IDs
  • SV-38448r2_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-1, IAIA-2
Checks: C-36252r2_chk

For Trusted Mode: Verify that user accounts do not have blank passwords. # cd /tcb/files/auth &amp;&amp; grep “u_pwd=::” */* If any user account with a blank password is found, this is a finding. For SMSE: Inspect the password (2nd) field in the /etc/shadow file. # cat /etc/shadow If any user account in the /etc/shadow file contains a null password field, this is a finding.

Fix: F-31509r2_fix

For Trusted Mode: Use the System Administration Manager (SAM) or the System Management Homepage (SMH) to disable null passwords and immediately expire the password for any account with a null password, forcing the user to create a password on the very next login. Alternatively, the account may also be disabled. Protected password database files are maintained in the /tcb/files/auth hierarchy. This directory contains other directories each named with a single letter from the alphabet. User authentication profiles are stored in these directories based on the first letter of the user account name. Verify that SAM/SMH has now disabled null passwords for all accounts. # grep “:u_nullpw@:” /tcb/files/auth/[a-z,A-Z] For SMSE: Use the SAM/SMH interface (/etc/default/security file) and/or the userdbset command (/var/adm/userdb/* files) to update the attribute(s). See the below example: LOGIN_POLICY_STRICT=1 ALLOW_NULL_PASSWORD=0 Note: Never use a text editor to modify any /var/adm/userdb database file. The database contains checksums and other binary data, and editors (vi included) do not follow the file locking conventions that are used to control access to the database. If manually editing the /etc/default/security file, save any change(s) before exiting the editor. Use the System Administration Manager (SAM) or the System Management Homepage (SMH) to immediately expire the password for any account with a null password, forcing the user to create a password on the very next login. Alternatively, the account may also be disabled.

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

Check the system for duplicate UID 0 assignments by listing all accounts assigned UID 0. # cat /etc/passwd | cut -f 1,3 -d ":" | grep ":0" If any accounts other than root are assigned UID 0, this is a finding.

Fix: F-31528r1_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-34829r1_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GEN000900
Vuln IDs
  • V-774
Rule IDs
  • SV-34829r1_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 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-1, ECCD-2
Checks: C-36272r1_chk

Determine if root is assigned a home directory other than / by listing its home directory. # cat /etc/passwd | grep "^root" | cut -f 6,6 -d ":" If the root user home directory is /, this is a finding.

Fix: F-31529r1_fix

The root home directory should be something other than / (such as /roothome). # mkdir /rootdir # chown root /rootdir # chgrp root /rootdir # chmod 700 /rootdir # cp -r /.??* /rootdir/. Edit the passwd file and change the root home directory to /rootdir. The cp -r /.??* command copies all files and subdirectories of file names that begin with "." into the new root directory, which preserves the previous root environment. Ensure you are 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-38450r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN000920
Vuln IDs
  • V-775
Rule IDs
  • SV-38450r1_rule
Permissions greater than 0700 could allow unauthorized users access to the root home directory.System AdministratorECCD-2, ECCD-1
Checks: C-36273r1_chk

Check the mode of the root home directory. Procedure: # cat /etc/passwd | grep "^root" | cut -f 6,6 -d ":" # ls -lLd &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 check will be marked Not Applicable.

Fix: F-31530r1_fix

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

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-38451r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN000940
Vuln IDs
  • V-776
Rule IDs
  • SV-38451r1_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-2, ECCD-1
Checks: C-36274r1_chk

To view the root user's PATH, log in as the root user, and execute: # 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-31531r1_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.

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

For each world-writable path in root's executable search path, do 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-38453r2_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000770
Version
GEN000980
Vuln IDs
  • V-778
Rule IDs
  • SV-38453r2_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-36276r2_chk

Check the /etc/securetty file contents. # more /etc/securetty If /etc/securetty does not exist, or has contents other than console or /dev/null, this is a finding.

Fix: F-31533r3_fix

If the /etc/securetty file does not exist, create the file containing only the word console and ensure correct file properties. # echo “console” > /etc/securetty

b
GIDs reserved for system accounts must not be assigned to non-system groups.
CM-6 - Medium - CCI-000366 - V-780 - SV-38454r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN000360
Vuln IDs
  • V-780
Rule IDs
  • SV-38454r1_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-36253r3_chk

Confirm all accounts with a GID of 99 and below are used by a system account. If a GID reserved for system accounts (0 - 99) is used by a non-system account, this is a finding. The vendor-supplied system default group "users" (gid=20) is considered an exception to this check. # cat /etc/passwd | cut -f 1,4 -d ":"

Fix: F-31510r1_fix

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

a
All GIDs referenced in the /etc/passwd file must be defined in the /etc/group file.
CM-6 - Low - CCI-000366 - V-781 - SV-38455r1_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GEN000380
Vuln IDs
  • V-781
Rule IDs
  • SV-38455r1_rule
If a user is assigned the GID of a group not existing 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-36254r1_chk

Determine if any GIDs referenced in /etc/passwd are not defined in /etc/group. Procedure: # cat /etc/passwd | cut -f 4,4 -d ":" | sort | uniq With the above GIDs, manually execute the following command for every GID from above. Note that this command is expected to return line entry information from /etc/group. # grep -n &lt;GID&gt; /etc/group If any GIDs referenced in /etc/passwd and not defined in /etc/group are returned, this is a finding.

Fix: F-31511r2_fix

Add a group to the system (edit /etc/group) for each GID referenced without a corresponding group.

b
The system must have a host-based intrusion detection tool installed.
SI-4 - Medium - CCI-001259 - V-782 - SV-35141r1_rule
RMF Control
SI-4
Severity
Medium
CCI
CCI-001259
Version
GEN006480
Vuln IDs
  • V-782
Rule IDs
  • SV-35141r1_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-34998r1_chk

A few applications providing host-based network intrusion protection are: - Dragon Squire by Enterasys Networks - ITA by Symantec - Hostsentry by Psionic Software - Logcheck by Psionic Software - RealSecure agent by ISS - Swatch by Stanford University Ask the SA or IAO if a host-based intrusion detection application is loaded on the system (where &lt;daemon name&gt; is the name of the primary application daemon) to determine if the application is loaded on the system. # find / -name &lt;daemon&gt; | xargs -n1 ls -lL Determine if the application is active on the system. # 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-32105r1_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-35242r2_rule
RMF Control
SI-2
Severity
Medium
CCI
CCI-001227
Version
GEN000120
Vuln IDs
  • V-783
Rule IDs
  • SV-35242r2_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-288r3_chk

Obtain the list of available security patches from HP. Ensure the available patches have been installed on the system. To list patches installed on the system, use the swlist utility. Example: # swlist -l fileset If there are security patches available and applicable for the system that have not been installed, this is a finding.

Fix: F-937r5_fix

Use a web browser to access the vendor's support website. Follow the instructions to set up an account with a login and a password. Once this is done it is possible to download the needed patches. # swinstall

b
System files and directories must not have uneven access permissions.
AC-6 - Medium - CCI-000225 - V-784 - SV-38457r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001140
Vuln IDs
  • V-784
Rule IDs
  • SV-38457r1_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-1, ECCD-2
Checks: C-36277r1_chk

Check system directories for uneven file permissions. Procedure: # ls -lL /etc /bin /usr/bin /usr/lbin /usr/usb /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-31534r1_fix

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

b
All files and directories must have a valid owner.
CM-6 - Medium - CCI-000366 - V-785 - SV-34833r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN001160
Vuln IDs
  • V-785
Rule IDs
  • SV-34833r1_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-2, ECCD-1
Checks: C-290r2_chk

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

Fix: F-939r2_fix

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

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

Check the mode of network services daemons. # ls -lLa /usr/lbin 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-31556r1_fix

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

b
System log files must have mode 0640 or less permissive.
SI-11 - Medium - CCI-001314 - V-787 - SV-35275r1_rule
RMF Control
SI-11
Severity
Medium
CCI
CCI-001314
Version
GEN001260
Vuln IDs
  • V-787
Rule IDs
  • SV-35275r1_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-36302r1_chk

Check the mode of log files. # ls -lLR /var/log /var/log/syslog /var/adm /var/opt Note that some of the above directories will contain more than just system log files. For example: /var/adm/sa, /var/adm/sw, etc. Any non-system log files contained within the above directories should be excluded from this requirement. If any of the system log files have modes more permissive than 0640, this is a finding.

Fix: F-31557r1_fix

Change the mode of the system log files to 0640 or less permissive. # chmod 0640 <path>/<system-log-file> NOTE: Do not confuse system log files with audit logs.

b
All skeleton files (typically those in /etc/skel) must have mode 0444 or less permissive.
AC-6 - Medium - CCI-000225 - V-788 - SV-38459r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001800
Vuln IDs
  • V-788
Rule IDs
  • SV-38459r1_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-36364r1_chk

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

Fix: F-31701r1_fix

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

b
NIS/NIS+/yp files must be owned by root, sys, or bin.
AC-6 - Medium - CCI-000225 - V-789 - SV-38460r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001320
Vuln IDs
  • V-789
Rule IDs
  • SV-38460r1_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-36303r1_chk

Check NIS file ownership. Procedure: # ls -lLa /var/yp/&lt;nis domainname&gt; If the file ownership is not root, sys, or bin, this is a finding.

Fix: F-31558r1_fix

Change the ownership of NIS/NIS+/yp files to root, sys, or bin. Consult vendor documentation to determine the location of the files. Procedure (example): # chown root <filename>

b
NIS/NIS+/yp files must be group-owned by root, sys, bin, or other.
AC-6 - Medium - CCI-000225 - V-790 - SV-38461r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001340
Vuln IDs
  • V-790
Rule IDs
  • SV-38461r1_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-36304r3_chk

Check NIS file ownership. # ls -alLR /var/yp/`domainname` If the file group owner is not root, sys, bin (the default), or other, this is a finding.

Fix: F-31559r2_fix

Change the group owner of the NIS files to root, sys, bin, or other. # chgrp root <filename>

b
The NIS/NIS+/yp command files must have mode 0755 or less permissive.
AC-6 - Medium - CCI-000225 - V-791 - SV-38462r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001360
Vuln IDs
  • V-791
Rule IDs
  • SV-38462r1_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-36305r1_chk

Check NIS file mode. Procedure: # grep -i NIS_DOMAIN /etc/rc.config.d/namesvrs # ls -lLa /var/yp/&lt;NIS_DOMAIN&gt; If the file's mode is more permissive than 0755, this is a finding.

Fix: F-31560r1_fix

Change the mode of NIS/NIS+/yp command 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-38463r2_rule
RMF Control
AC-6
Severity
Low
CCI
CCI-000225
Version
GEN001280
Vuln IDs
  • V-792
Rule IDs
  • SV-38463r2_rule
If manual pages are compromised, misleading information could be inserted, causing actions possibly compromising the system.ECCD-1, ECCD-2
Checks: C-39552r3_chk

Check the mode of the manual page files. # find `env | grep MANPATH | cut -f 2,2 -d "=" | tr ':' ' ' ` -type f \( -perm -100 -o -perm -030 -o -perm -003 \) -exec ls -al {} + If any manual page file mode is more permissive than 0644, this is a finding.

Fix: F-31561r1_fix

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

b
Library files must have mode 0755 or less permissive.
CM-5 - Medium - CCI-001499 - V-793 - SV-38464r1_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
GEN001300
Vuln IDs
  • V-793
Rule IDs
  • SV-38464r1_rule
Unauthorized access could destroy the integrity of the library files.System AdministratorDCSL-1
Checks: C-36307r2_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 755, this is a finding.

Fix: F-31562r1_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 number.

b
All system command files must have mode 755 or less permissive.
CM-5 - Medium - CCI-001499 - V-794 - SV-38465r1_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
GEN001200
Vuln IDs
  • V-794
Rule IDs
  • SV-38465r1_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 world-writable.System AdministratorECLP-1
Checks: C-36308r1_chk

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

Fix: F-31563r1_fix

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

b
All system files, programs, and directories must be owned by a system account.
CM-5 - Medium - CCI-001499 - V-795 - SV-38466r1_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
GEN001220
Vuln IDs
  • V-795
Rule IDs
  • SV-38466r1_rule
Restricting permissions will protect the files from unauthorized modification.System AdministratorECLP-1
Checks: C-36309r1_chk

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

Fix: F-31564r1_fix

Change the owner of system files, programs, and directories to a system account. Procedure: # chown root <path>/<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-38467r1_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-001499
Version
GEN001240
Vuln IDs
  • V-796
Rule IDs
  • SV-38467r1_rule
Restricting permissions will protect the files from unauthorized modification.System AdministratorECLP-1
Checks: C-36310r1_chk

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

Fix: F-31565r1_fix

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

b
The /etc/shadow (or equivalent) file must be owned by root.
AC-6 - Medium - CCI-000225 - V-797 - SV-38468r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001400
Vuln IDs
  • V-797
Rule IDs
  • SV-38468r2_rule
The /etc/shadow file contains the list of local system accounts. It is vital to system security and must be protected from unauthorized modification. Failure to give ownership of sensitive files or utilities to root 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-36330r4_chk

For Trusted Mode: Check the ownership of the /etc/shadow file. # ls -lL /etc/shadow If the /etc/shadow file exists and is not owned by root, this is a finding. NOTE: /etc/shadow should not exist if the system is in Trusted Mode. Check the ownership of the TCB auth files and directories. # ls -lLd /tcb /tcb/files /tcb/files/auth # ls -lL /tcb/files/auth/[a-z,A-Z]/* If the owner of any of the /tcb files and directories is not root, this is a finding. For SMSE: Check the /etc/shadow file. # ls -lL /etc/shadow If the /etc/shadow file exists and is not owned by root, this is a finding.

Fix: F-31585r2_fix

For Trusted Mode: # chown root /tcb # chown root /tcb/files /tcb/files/auth # chown root /tcb/files/auth/[a-z]/* For SMSE: # chown root /etc/shadow

b
The /etc/passwd file must have mode 0444 or less permissive.
AC-6 - Medium - CCI-000225 - V-798 - SV-38469r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001380
Vuln IDs
  • V-798
Rule IDs
  • SV-38469r1_rule
If the passwd file is writable by a group owner or the world, the risk of passwd file compromise is increased. The passwd file contains the list of accounts on the system and associated information.System AdministratorECLP-1
Checks: C-36331r1_chk

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

Fix: F-31586r1_fix

Change the mode of the passwd file to 0444. # chmod 0444 /etc/passwd Document all changes.

b
The /etc/shadow (or equivalent) file must have mode 0400.
AC-6 - Medium - CCI-000225 - V-800 - SV-38470r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001420
Vuln IDs
  • V-800
Rule IDs
  • SV-38470r2_rule
The /etc/shadow file contains the list of local system accounts. It is vital to system security and must be protected from unauthorized modification. The file also contains password hashes which must not be accessible to users other than root. The Trusted Mode /tcb tree requires modes more permissive than the shadow file.System AdministratorECLP-1
Checks: C-36332r2_chk

For Trusted Mode: Check the TCB auth files and directories. # ls -lLd /tcb /tcb/files /tcp/files/auth # ls -lL /tcb/files/auth/[a-z,A-Z]/* If the mode of /tcb directory is more permissive than 0555, this is a finding. If the mode of /tcb/files or /tcb/files/auth directories is more permissive than 0771, this is a finding. If the mode of any of the /tcb/files/auth/[a-z]/* is more permissive than 0664, this is a finding. For SMSE: Check the /etc/shadow file. # ls -lL /etc/shadow If the /etc/shadow file has a mode more permissive than 0400, this is a finding. NOTE: The /etc/shadow file will not exist if the system is in Trusted Mode.

Fix: F-31587r3_fix

For Trusted Mode: # chmod 0555 /tcb # chmod 0771 /tcb/files /tcb/files/auth # chmod 0664 /tcb/files/auth/[a-z]/* For SMSE: # chmod 0400 /etc/shadow

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-38471r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000368
Version
GEN002380
Vuln IDs
  • V-801
Rule IDs
  • SV-38471r1_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-36399r1_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 suid bit set have been documented. If any undocumented file has its suid bit set, this is a finding.

Fix: F-31738r1_fix

Document the files with the suid bit set or unset the suid 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-34943r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000368
Version
GEN002440
Vuln IDs
  • V-802
Rule IDs
  • SV-34943r1_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.trueSystem AdministratorInformation Assurance OfficerECPA-1
Checks: C-36401r1_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-31740r1_fix

All files with the sgid bit set will be documented in the system baseline and authorized by the Information Systems Security Officer (ISSO). Locate all sgid files with the following command: find / -perm -2000 -exec ls -lL {} \; 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-38472r1_rule
RMF Control
CM-3
Severity
Medium
CCI
CCI-000318
Version
GEN002400
Vuln IDs
  • V-803
Rule IDs
  • SV-38472r1_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-36400r1_chk

NOTE: This will virtually always require a manual review. Determine if a weekly automated or manual process is used to generate a list of suid files on the system and compare it with the prior list. If no such process is in place, this is a finding.

Fix: F-31739r1_fix

Establish a weekly automated or manual process to generate a list of suid files on the system and compare it with the prior list. To create a list of suid files: # find / -perm -4000 > suid-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-38473r1_rule
RMF Control
CM-3
Severity
Medium
CCI
CCI-000318
Version
GEN002460
Vuln IDs
  • V-804
Rule IDs
  • SV-38473r1_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-36402r1_chk

NOTE: This will virtually always require a manual review. Determine if a weekly automated or manual process is used to generate a list of sgid files on the system and compare it with the prior list. If no such process is in place, this is a finding.

Fix: F-31741r1_fix

Establish a weekly automated or manual process to generate a list of sgid files on the system and compare it with the prior list. To create a list of sgid files: # find / -type f -perm -2000 -exec ls -lL {} \; >> sgid-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-34946r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002420
Vuln IDs
  • V-805
Rule IDs
  • SV-34946r1_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 that do not contain approved setuid files, increases the opportunity for unprivileged users to attain unauthorized administrative access.System AdministratorECLP-1
Checks: C-36403r1_chk

Check /etc/fstab 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 line entry must contain a device specific file and may additionally contain all of the following fields, in the following order: mount directory, type, options, backup frequency, pass number (on parallel fsck) and comment. # cat /etc/fstab | grep -v "^#" If the "nosuid" mount option is not used on file systems mounted from removable media, network shares, or any other file system that does not contain approved setuid or setgid files, this is a finding.

Fix: F-31742r1_fix

Edit /etc/fstab and add the nosuid mount option to all file systems mounted from removable media or network shares, and any file system not containing approved setuid or setgid files.

a
The sticky bit must be set on all public directories.
CM-6 - Low - CCI-000366 - V-806 - SV-38474r1_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GEN002500
Vuln IDs
  • V-806
Rule IDs
  • SV-38474r1_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-36405r1_chk

Verify all world-writable directories have the sticky bit set. Procedure: # find / -type d -perm -002 ! -perm -1000 -exec ls -lLd {} \; | tee wwlist If the sticky bit is not set on a world-writable directory, this is a finding.

Fix: F-31743r1_fix

Set the sticky bit on all public directories. Procedure: # chmod 1777 <world writeable directory>

b
All public directories must be owned by root or an application account.
AC-6 - Medium - CCI-000225 - V-807 - SV-34950r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002520
Vuln IDs
  • V-807
Rule IDs
  • SV-34950r1_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-36406r1_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-31744r1_fix

Change the owner of public directories to root or an application account. Procedure: # chown root <public directory>

b
The system and user default umask must be 077.
CM-6 - Medium - CCI-000366 - V-808 - SV-38475r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN002560
Vuln IDs
  • V-808
Rule IDs
  • SV-38475r1_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-36407r1_chk

Check global initialization files for the configured umask value. # grep umask /etc/* | grep -v ":#" | grep "umask [0-9]" 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-31745r1_fix

Edit local and global initialization files containing 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-27264r2_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000178
Version
GEN002640
Vuln IDs
  • V-810
Rule IDs
  • SV-27264r2_rule
Vendor accounts and software may contain backdoors that will allow 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-36408r2_chk

Account/password locking is typically accomplished with the asterisk (*). System logins that never had a password use a double exclamation mark (!!) and accounts that have been locked have the valid password entry invalidated by a single exclamation mark (!) prefix. For Trusted Mode: Protected password database files are maintained in the /tcb/files/auth hierarchy. This directory contains other directories each named with a single letter from the alphabet. User authentication profiles are stored in these directories based on the first letter of the user account name. Next check if default system accounts (such as those for sys, bin, uucp, nuucp, daemon, smtp) have been disabled. # grep “u_pwd=“ /tcb/files/auth/[a-z,A-Z]/* If any default system accounts (such as those for sys, bin, uucp, nuucp, daemon, smtp) have not been disabled, this is a finding. For SMSE: Check if default system accounts (such as those for sys, bin, uucp, nuucp, daemon, smtp) have been disabled. # cat /etc/shadow If any default system accounts (such as those for sys, bin, uucp, nuucp, daemon, smtp) have not been disabled, this is a finding.

Fix: F-31746r2_fix

For Trusted Mode and SMSE: Use the System Administration Manager (SAM) or the System Management Homepage (SMH) to lock/disable or remove any enabled default system accounts.

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

Determine if auditing is enabled. # audsys If the audit service is not running, this is a finding.

Fix: F-30370r1_fix

In order to turn auditing on, the system must first be in Trusted Mode. Next, turn on the auditing system. The system will use existing current and next audit trails (if configured). # sam Then: Auditing and Security -> Audited Events -> Actions -> Turn Auditing On.

b
System audit logs must be owned by root.
AU-9 - Medium - CCI-000162 - V-812 - SV-38477r2_rule
RMF Control
AU-9
Severity
Medium
CCI
CCI-000162
Version
GEN002680
Vuln IDs
  • V-812
Rule IDs
  • SV-38477r2_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-36424r2_chk

Inspect the auditing configuration file, /etc/rc.config.d/auditing, to determine the filename and path of the audit logs. The entries should appear similar to the following: PRI_AUDFILE=/var/.audit/file1 SEC_AUDFILE=/var/.audit/file2 # egrep “PRI_AUDFILE|SEC_AUDFILE” /etc/rc.config.d/auditing For each audit log directory/file, check the ownership. # ls -lLd &lt;audit directory&gt; # ls -lLa &lt;audit file&gt; If any audit log directory/file is not owned by root, this is a finding.

Fix: F-31763r2_fix

As root, change the ownership. # chown root <audit directory> # chown root <audit file>

b
System audit logs must have mode 0640 or less permissive.
AU-9 - Medium - CCI-000163 - V-813 - SV-38478r2_rule
RMF Control
AU-9
Severity
Medium
CCI
CCI-000163
Version
GEN002700
Vuln IDs
  • V-813
Rule IDs
  • SV-38478r2_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-36425r2_chk

Inspect the auditing configuration file, /etc/rc.config.d/auditing, to determine the filename and path of the audit logs. The entries should appear similar to the following: PRI_AUDFILE=/var/.audit/file1 SEC_AUDFILE=/var/.audit/file2 # egrep “PRI_AUDFILE|SEC_AUDFILE” /etc/rc.config.d/auditing For each audit log directory/file, check the permissions. # ls -lLd &lt;audit directory&gt; # ls -lLa &lt;audit file&gt; If any audit log file has permissions greater than 0640 (0750 for directories), this is a finding.

Fix: F-31764r2_fix

As root, change the permissions. # 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-38479r1_rule
RMF Control
AU-2
Severity
Medium
CCI
CCI-000126
Version
GEN002720
Vuln IDs
  • V-814
Rule IDs
  • SV-38479r1_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-1, ECAR-3
Checks: C-36426r1_chk

Check the system audit configuration to determine if failed attempts to access files and programs are audited. # grep -i audevent_args1 /etc/rc.config.d/auditing | grep open If no results are returned, this is a finding.

Fix: F-31765r1_fix

Edit /etc/rc.config.d/auditing and add -e open to the end of the AUDEVENT_ARGS1 parameter.

b
The audit system must be configured to audit file deletions.
AU-2 - Medium - CCI-000126 - V-815 - SV-38480r1_rule
RMF Control
AU-2
Severity
Medium
CCI
CCI-000126
Version
GEN002740
Vuln IDs
  • V-815
Rule IDs
  • SV-38480r1_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-36427r1_chk

Check the system audit configuration to determine if failed attempts to access files and programs are audited. # grep -i audevent_args1 /etc/rc.config.d/auditing | grep delete If no results are returned, this is a finding.

Fix: F-31766r1_fix

Edit /etc/rc.config.d/auditing and add -e delete to the end of the AUDEVENT_ARGS1 parameter.

b
The audit system must be configured to audit all administrative, privileged, and security actions.
CM-5 - Medium - CCI-000347 - V-816 - SV-38481r1_rule
RMF Control
CM-5
Severity
Medium
CCI
CCI-000347
Version
GEN002760
Vuln IDs
  • V-816
Rule IDs
  • SV-38481r1_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-36428r1_chk

Check the auditing configuration of the system. # grep -i audevent_args1 /etc/rc.config.d/auditing | grep admin # grep -i audevent_args1 /etc/rc.config.d/auditing | grep removable If no results are returned for either of these commands, this is a finding.

Fix: F-31767r1_fix

Edit /etc/rc.config.d/auditing and add -e admin and -e removable to the end of the AUDEVENT_ARGS1 parameter.

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

Check the system's audit configuration. # grep -i audevent_args1 /etc/rc.config.d/auditing | grep login If no results are returned, this is a finding.

Fix: F-31768r1_fix

Edit /etc/rc.config.d/auditing and add -e login to the end of the AUDEVENT_ARGS1 parameter.

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

Check the system's audit configuration. The term moddac is code for MODify Dicscretionary Access Control (i.e., chown, chmod, etc.). # grep -i audevent_args1 /etc/rc.config.d/auditing | grep moddac If no results are returned, this is a finding.

Fix: F-31769r1_fix

Edit /etc/rc.config.d/auditing and add -e moddac to the end of the AUDEVENT_ARGS1 parameter.

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-35067r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003720
Vuln IDs
  • V-821
Rule IDs
  • SV-35067r1_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-34933r1_chk

Check the ownership of the xinetd.d directory, the (x)inetd.conf file and any files identified by the configuration file includedir stanza. # find / -type d -name xinetd.d | xargs -n1 ls -lLd # find / -type f -name inetd.conf -o -name xinetd.conf | xargs -n1 ls -lL # grep includedir &lt;PATH&gt;/xinetd.conf If any of the above named files, included files or directories are not owned by root or bin, this is a finding.

Fix: F-30239r1_fix

Change the ownership of the inetd.conf file to root or bin. # chown root <file or directory>

b
The inetd.conf and xinetd.conf files must have mode 0440 or less permissive.
AC-6 - Medium - CCI-000225 - V-822 - SV-35072r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003740
Vuln IDs
  • V-822
Rule IDs
  • SV-35072r1_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-34936r1_chk

Check the mode of the (x)inetd.conf file and any files identified by the configuration file includedir stanza: # find / -type f -name inetd.conf -o -name xinetd.conf | xargs -n1 ls -lL # grep includedir &lt;PATH&gt;/xinetd.conf # ls -lL &lt;includedir files from previous command&gt; If any of the above file mode are more permissive than 0440, this is a finding.

Fix: F-30242r1_fix

Change the mode of the (x)inetd.conf file. # chmod 0440 <file>

b
The services file must be owned by root or bin.
AC-6 - Medium - CCI-000225 - V-823 - SV-35077r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003760
Vuln IDs
  • V-823
Rule IDs
  • SV-35077r1_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-34941r1_chk

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

Fix: F-30246r1_fix

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

b
The services file must have mode 0444 or less permissive.
AC-6 - Medium - CCI-000225 - V-824 - SV-35078r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003780
Vuln IDs
  • V-824
Rule IDs
  • SV-35078r1_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-34942r1_chk

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

Fix: F-30247r1_fix

Change the mode of the services file to 0444 or less permissive. # 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-38484r1_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GEN001780
Vuln IDs
  • V-825
Rule IDs
  • SV-38484r1_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-36365r1_chk

Check global initialization files for the presence of mesg -n or mesg n. Procedure: # grep "mesg" /etc/.login /etc/profile /etc/bashrc /etc/csh.login /etc/csh.cshrc If global initialization files exist and do not contain mesg -n or mesg n, this is a finding.

Fix: F-31702r1_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-35140r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN003900
Vuln IDs
  • V-827
Rule IDs
  • SV-35140r1_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-34997r1_chk

Look for the presence of a print service configuration file. The hosts.lpd file is not used on HP, only inetd.sec, hosts.equiv, and/or the system (lp) .rhosts will apply. When rlpdaemon is started via inetd, access control is provided via the fileinetd.sec to allow or prevent a host from making print requests. When rlpdaemon is started at boot via a run command file, all requests must come from one of the machines listed in the file /etc/hosts.equiv or /var/spool/lp/.rhosts. Procedure: First, determine the rlpdaemon startup method: 1) Print services started via inetd? # cat /etc/inetd.conf | grep -v "^#" | grep -c rlpdaemon If the above command return value is 1, check the services file. # cat /etc/services | grep -v "^#" | grep printer | grep -c spooler If the above command return value is 1, check the inetd.sec file. # cat /var/adm/inetd.sec | grep -v "^#" | tr '\011' ' ' | tr -s ' ' | grep printer | grep allow | grep -c "\+" If the above command return value is 1, this is a finding. 2) The rlpdaemon is started as a service, and not via inetd. Verify neither the /etc/hosts.equiv nor /var/spool/lp/.rhosts contains a "+": # cat /etc/hosts.equiv | grep -v "^#" | grep -c "\+" # cat /var/spool/lp/.rhosts | grep -v "^#" | grep -c "\+" If the return value of either of the above two command(s) is 1, this is a finding. If none of the files are found, this check should be marked not a finding. Otherwise, examine the configuration file. # more &lt;print service file&gt; Check for entries containing a "+" or "_" character. If any are found, this is a finding.

Fix: F-30292r1_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-35143r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003920
Vuln IDs
  • V-828
Rule IDs
  • SV-35143r1_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-35001r1_chk

Locate any print service configuration file(s) on the system. HP vendor documentation identifies the following names and locations of print service configuration files on the system that can be checked via the following commands: # ls -lL /var/spool/lp/.rhosts # ls -lL /var/adm/inetd.sec # ls -lL /etc/hosts.equiv If no print service configuration file is found, this is not a finding. Check the ownership of the print service configuration file(s). # ls -lL &lt;print service configuration file&gt; If the owner of the file is not root, sys, bin, or lp, this is a finding.

Fix: F-30294r1_fix

Change the owner of the /etc/hosts.lpd file (or equivalent) to root, lp, or another privileged UID. # chown root <print service configuration file>

b
The hosts.lpd (or equivalent) must have mode 0644 or less permissive.
AC-6 - Medium - CCI-000225 - V-829 - SV-35148r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003940
Vuln IDs
  • V-829
Rule IDs
  • SV-35148r1_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-35005r1_chk

Locate any print service configuration file(s) on the system. HP vendor documentation identifies the following names and locations of print service configuration files on the system that can be checked via the following commands: # ls -lL /var/spool/lp/.rhosts # ls -lL /var/adm/inetd.sec # ls -lL /etc/hosts.equiv If no print service configuration file is found, this is not a finding. Check the mode of the print service configuration file. # ls -lL &lt;print service configuration file&gt; If the mode of the print service configuration file is more permissive than 0644, this is a finding.

Fix: F-30299r1_fix

Change the mode of the /etc/hosts.lpd file (or equivalent) to 0644 or less permissive. Procedure: # chmod 0644 <print service configuration file>

b
The alias file must be owned by root.
AC-6 - Medium - CCI-000225 - V-831 - SV-35161r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN004360
Vuln IDs
  • V-831
Rule IDs
  • SV-35161r1_rule
If the aliases file is not owned by root, an unauthorized user may modify the file to add aliases to run malicious code or redirect e-mail.System AdministratorECLP-1
Checks: C-35014r1_chk

Find the aliases file on the system and check the ownership. # ls -lL /etc/mail/aliases If the file is not owned by root, this is a finding.

Fix: F-30308r1_fix

Change the owner of the /etc/mail/aliases file (or equivalent) to root. # chown root /etc/mail/aliases

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

Find the aliases file on the system. Procedure: # ls -lL /etc/mail/aliases If the aliases file exists with a mode more permissive than 0644, this is a finding.

Fix: F-30311r1_fix

Change the mode of the aliases file (or equivalent) to 0644. # 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-35169r1_rule
RMF Control
AC-6
Severity
High
CCI
CCI-000225
Version
GEN004400
Vuln IDs
  • V-833
Rule IDs
  • SV-35169r1_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-35019r1_chk

Examine the aliases file for any utilized directories or paths. # cat/etc/mail/aliases | cut -f 2,2 -d ":" | grep "|" For example, the alias file entry will look like: msgs: "|/usr/bin/msgs -s" The entry must be an absolute path name: # ls -lLd `dirname &lt;entry&gt;` # ls -lL &lt;entry&gt; If the file or parent directory is not owned by root, this a finding.

Fix: F-30312r1_fix

Edit the /etc/mail/aliases file Locate the entries executing a program. They will appear similar to the following line: alias: "|/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. For a directory entry: # chown root <entry> For a file entry (change BOTH the directory and file, where/as necessary: # chown root <entry> # chown root `dirname <entry>`

b
Files executed through a mail aliases file must have mode 0755 or less permissive.
AC-6 - Medium - CCI-000225 - V-834 - SV-35043r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN004420
Vuln IDs
  • V-834
Rule IDs
  • SV-35043r1_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-36562r1_chk

Examine the aliases file on the system for any utilized directories or paths. # cat /etc/mail/aliases | cut -f 2,2 -d ":" | grep "|" Check the permissions for any file paths referenced. # ls -lL &lt;path/file&gt; If any file referenced from the aliases file has a mode more permissive than 0755, this is a finding.

Fix: F-31930r1_fix

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

a
Sendmail logging must not be set to less than 9 in the sendmail.cf file.
CM-6 - Low - CCI-000366 - V-835 - SV-35047r1_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GEN004440
Vuln IDs
  • V-835
Rule IDs
  • SV-35047r1_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-3, ECAR-2, ECAR-1
Checks: C-36564r1_chk

The sendmail.cf log level option line will typically appear as follows: O LogLevel=N Check if Sendmail logging is set to level 9 via the following command: # cat /etc/mail/sendmail.cf | tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' | grep -v "^#" | \ grep -i loglevel | tr '\011' ' ' | tr -d ' ' | cut -f 2,2 -d "=" If logging is not set, i.e., line is missing or commented, this is a finding. If logging is set to less than 9, this is a finding.

Fix: F-31932r1_fix

Edit the sendmail.cf file, locate the entry (and where necessary uncomment it and/or create it) and modify/set 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-35051r1_rule
RMF Control
AU-2
Severity
Medium
CCI
CCI-000126
Version
GEN004460
Vuln IDs
  • V-836
Rule IDs
  • SV-35051r1_rule
If informational and more severe SMTP service messages are not logged, malicious activity on the system may go unnoticed.System AdministratorECSC-1, ECAR-3, ECAR-1, ECAR-2
Checks: C-36565r1_chk

The syslog.conf file critical mail logging option line will typically appear as one of the following examples: mail.crit /var/adm/messages mail.* /var/adm/messages *.* /var/adm/messages *.crit /var/adm/messages Check the syslog configuration file for mail.crit logging configuration. # cat /etc/syslog.conf | tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' | grep -v "^#" | egrep -i "mail.crit|mail.\*|\*.crit|\*.\*" If syslog is not configured to log critical sendmail messages, this is a finding.

Fix: F-31933r1_fix

Edit the syslog.conf file and add a configuration line specifying an appropriate destination for critical "mail" syslogs, for example: mail.crit /var/adm/messages mail.* /var/adm/messages *.* /var/adm/messages *.crit /var/adm/messages

b
The SMTP service log file must be owned by root.
AC-6 - Medium - CCI-000225 - V-837 - SV-35053r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN004480
Vuln IDs
  • V-837
Rule IDs
  • SV-35053r1_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-36566r1_chk

Locate any Sendmail log files by checking the syslog configuration file. # cat /etc/syslog.conf | tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' | grep -v "^#" | \ egrep -i "mail.info|mail.debug|mail.\*|\*.info|\*.debug|\*.\*" | cut -f 2,2 -d " " | uniq | xargs -n1 ls -lL 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. If any mail log file is not owned by root, this is a finding.

Fix: F-31934r1_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-35058r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN004500
Vuln IDs
  • V-838
Rule IDs
  • SV-35058r1_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-36567r1_chk

Check the mode of the SMTP service log file. # cat /etc/syslog.conf | tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' | grep -v "^#" | egrep -i "mail.info|mail.debug|mail.\*|\*.info|\*.debug|\*.\*" | cut -f 2,2 -d " " | uniq | xargs -n1 ls -lL Check the configuration to determine which log files contain logs for mail. # ls -lL &lt;sendmail log file&gt; If any Sendmail log file permissions are greater than 0644, this is a finding.

Fix: F-31935r1_fix

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

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

Check for the existence of the ftpusers file. This file is normally located in the /etc/ftpd directory. # ls -lL /etc/ftpd/ftpusers OR alternatively # find / -type f -name ftpusers -exec ls -lL {} \; If the ftpusers file does not exist, this is a finding.

Fix: F-31950r1_fix

Create a /etc/ftpd/ftpusers (or equivalent) file containing a list of /etc/passwd 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-35103r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN004900
Vuln IDs
  • V-841
Rule IDs
  • SV-35103r1_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-36583r1_chk

Check the contents of the ftpusers file. # more /etc/ftpd/ftpusers OR alternatively # find / -type f -name ftpusers -exec ls -lL {} \; If the system has accounts not allowed to use FTP and not listed in the ftpusers file, this is a finding.

Fix: F-31951r1_fix

Add accounts not allowed to use FTP to the /etc/ftpd/ftpusers (or equivalent) file.

b
The ftpusers file must be owned by root.
AC-6 - Medium - CCI-000225 - V-842 - SV-38485r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN004920
Vuln IDs
  • V-842
Rule IDs
  • SV-38485r1_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-36584r1_chk

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

Fix: F-31952r1_fix

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

b
The ftpusers file must have mode 0640 or less permissive.
AC-6 - Medium - CCI-000225 - V-843 - SV-38486r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN004940
Vuln IDs
  • V-843
Rule IDs
  • SV-38486r1_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-36586r1_chk

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

Fix: F-31954r1_fix

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

a
The FTP daemon must be configured for logging or verbose mode.
AU-3 - Low - CCI-000130 - V-845 - SV-38995r1_rule
RMF Control
AU-3
Severity
Low
CCI
CCI-000130
Version
GEN004980
Vuln IDs
  • V-845
Rule IDs
  • SV-38995r1_rule
The -l option allows basic logging of connections. The verbose (on HP) and the debug (on Solaris) allow logging of what files the ftp session transferred. This extra logging makes it possible to easily track which files are being transferred onto or from a system. If they are not configured, the only option for tracking is the audit files. The audit files are much harder to read. If auditing is not properly configured, then there would be no record at all of the file transfer transactions.System AdministratorECAR-3, ECAR-2, ECAR-1
Checks: C-37978r2_chk

Perform: # grep ftpd /etc/inetd.conf Check the line for ftpd to see if the -v options are invoked. If not, this is a finding.

Fix: F-33221r1_fix

The v option enables more verbose logging, shows the accessed file names, and the logout timestamp. The syslog.conf file must be configured to log daemon.info and daemon.debug to a proper log file in which to capture the data. The output goes into the system log file. The log file is /var/adm/syslog. Edit the inetd.conf file. Locate the line that defines ftpd by typing /ftpd/cr. Add the v option where ftpd appears to the right of the pathname for ftpd. For instance: ftp stream tcp nowait root /usr/sbin/in.ftpd in.ftpd -v This is a requirement even when the system is using TCP_WRAPPERS and/or secure shell. The only time it is not a requirement is if the ftp daemon is not configured to run.

b
Anonymous FTP must not be active on the system unless authorized.
AC-22 - Medium - CCI-001475 - V-846 - SV-35100r1_rule
RMF Control
AC-22
Severity
Medium
CCI
CCI-001475
Version
GEN004820
Vuln IDs
  • V-846
Rule IDs
  • SV-35100r1_rule
Due to the numerous vulnerabilities inherent in anonymous FTP, it is not recommended for use. 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-36580r2_chk

Attempt to log in with anonymous or ftp. The user can type any string of characters as a password. (By convention, the password is the host name of the user's host or the user's email address.) The anonymous user is then given access only to user ftp's home directory, usually called /home/ftp. If the login is successful, this is a finding.

Fix: F-31948r2_fix

Configure the FTP service to not permit anonymous logins. Remove the user(s) ftp and/or anonymous from the /etc/passwd file.

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-35110r1_rule
RMF Control
CM-6
Severity
High
CCI
CCI-000366
Version
GEN005080
Vuln IDs
  • V-847
Rule IDs
  • SV-35110r1_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-36593r1_chk

Determine if the TFTP daemon is installed, started, and running in secure mode. # cat /etc/inetd.conf | tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' | grep -v "^#" | cut -f 6,7 -d " " | grep -i tftp If the tftpd process is not configured with exactly one path argument (example: "/usr/lbin/tftpd tftpd"), this is a finding.

Fix: F-31960r1_fix

Edit /etc/inetd.conf and add one path argument, representing the TFTP root directory, to the tftpd command.

c
The TFTP daemon must have mode 0755 or less permissive.
AC-6 - High - CCI-000225 - V-848 - SV-35155r1_rule
RMF Control
AC-6
Severity
High
CCI
CCI-000225
Version
GEN005100
Vuln IDs
  • V-848
Rule IDs
  • SV-35155r1_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-36594r1_chk

Check the mode of the TFTP daemon. # ls -lL /usr/lbin/tftpd If the mode of the file is more permissive than 0755, this is a finding.

Fix: F-31961r1_fix

Change the mode of the TFTP daemon. # chmod 0755 /usr/lbin/tftpd

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-35157r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN005120
Vuln IDs
  • V-849
Rule IDs
  • SV-35157r1_rule
If TFTP has a valid shell, it increases the likelihood that someone could logon to the TFTP account and compromise 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-31962r1_fix

Create a tftp user account if none exists. Assign a non-login shell to the tftp user account, such as /usr/bin/false. Assign/create the tftp user account home directory where/as necessary. Ensure the home directory is owned by the tftp user.

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

Check for .Xauthority files being utilized by looking for such files in the home directory of a user using X. Get a list of (non-system account) users and the associated home directories. # cat /etc/passwd | cut -f 1,6 -d ":" Inspect individual user home directories for the .Xauthority file. # find &lt;f6 from the above command&gt; -type f -name "\.Xauthority" -exec ls -lLa {} \; 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-31964r1_fix

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

b
The Network Information System (NIS) protocol must not be used.
AC-17 - Medium - CCI-001435 - V-867 - SV-38487r1_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-001435
Version
GEN006400
Vuln IDs
  • V-867
Rule IDs
  • SV-38487r1_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-36720r1_chk

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

Fix: F-32102r1_fix

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

a
All interactive users must be assigned a home directory in the /etc/passwd file.
AC-6 - Low - CCI-000225 - V-899 - SV-38488r2_rule
RMF Control
AC-6
Severity
Low
CCI
CCI-000225
Version
GEN001440
Vuln IDs
  • V-899
Rule IDs
  • SV-38488r2_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-36333r3_chk

Verify the consistency of the assigned home directories in the authentication database. For Trusted Mode: # authck -av If any user is not assigned a home directory, this is a finding. For SMSE: # pwck If any user is not assigned a home directory, this is a finding.

Fix: F-31588r2_fix

For Trusted Mode: Determine why the user is not assigned a home directory. Possible actions include: account deletion or disablement. If the account is determined to be valid, manually create the home directory if required (mkdir directoryname, copy the skeleton files into the directory, chown account name for the new directory and the skeleton files) and assign to the user in the /etc/passwd file or take corrective action via the HP SMH/SAM utility. For SMSE: Note: There may be additional package/bundle updates that must be installed to support attributes in the /etc/default/security file. Determine why the user is not assigned a home directory. Possible actions include: account deletion or disablement. If the account is determined to be valid, manually create the home directory if required (mkdir directoryname, copy the skeleton files into the directory, chown account name for the new directory and the skeleton files) and assign to the user in the /etc/passwd file or take corrective action via the HP SMH/SAM utility. Additionally, use the SAM/SMH interface (/etc/default/security file) and/or the userdbset command (/var/adm/userdb/* files) to update the ABORT_LOGIN_ON_MISSING_HOMEDIR attribute. See the below example: ABORT_LOGIN_ON_MISSING_HOMEDIR=1 Note: Never use a text editor to modify any /var/adm/userdb database file. The database contains checksums and other binary data, and editors (vi included) do not follow the file locking conventions that are used to control access to the database. If manually editing the /etc/default/security file, save any change(s) before exiting the editor.

a
All interactive user home directories defined in the /etc/passwd file must exist.
AC-6 - Low - CCI-000225 - V-900 - SV-38489r2_rule
RMF Control
AC-6
Severity
Low
CCI
CCI-000225
Version
GEN001460
Vuln IDs
  • V-900
Rule IDs
  • SV-38489r2_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-36334r3_chk

Verify the consistency of the assigned home directories in the authentication database. For Trusted Mode: # authck -av If any assigned home directory does not exist, this is a finding. For SMSE: # pwck If any assigned home directory does not exist, this is a finding.

Fix: F-31589r2_fix

Determine why the user home directory does not exist. Possible actions include: account deletion or disablement. If the account is determined to be valid, create the home directory either manually (mkdir directoryname, copy the skeleton files into the directory, chown account name for the new directory and the skeleton files) or via the HP SMH/SAM utility.

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

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

Fix: F-31590r1_fix

Change the mode of user's home directory to 0750 or less permissive. Procedure (example): # chmod 0750 <home directory> NOTE: Application directories are allowed to and may need 0755 permissions (or greater) for correct operation.

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

Check the ownership of each user home directory listed in the /etc/passwd file. Procedure: # ls -lLd &lt;user home directory&gt; OR # ls -lLd `cat /etc/passwd | cut -f 6,6 -d ":"` | more If any user home directory is not owned by the assigned user, this is a finding.

Fix: F-31591r1_fix

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

b
All interactive user home directories must be group-owned by the home directory owner's primary group.
AC-6 - Medium - CCI-000225 - V-903 - SV-38491r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001520
Vuln IDs
  • V-903
Rule IDs
  • SV-38491r1_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-36337r1_chk

Check the group ownership for each user in the /etc/passwd file. Procedure: # ls -lLd &lt;user home directory&gt; OR # ls -lLd `cat /etc/passwd | cut -f 6,6 -d ":"` | more If any user 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-31592r1_fix

Change the group-owner for user 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-38492r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001860
Vuln IDs
  • V-904
Rule IDs
  • SV-38492r1_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-36366r2_chk

Check the ownership of local initialization files. Procedure: # ls -alL /&lt;usershomedirectory&gt;/.login # ls -alL /&lt;usershomedirectory&gt;/.cshrc # ls -alL /&lt;usershomedirectory&gt;/.logout # ls -alL /&lt;usershomedirectory&gt;/.profile # ls -alL /&lt;usershomedirectory&gt;/.bash_profile # ls -alL /&lt;usershomedirectory&gt;/.bashrc # ls -alL /&lt;usershomedirectory&gt;/.bash_logout # ls -alL /&lt;usershomedirectory&gt;/.env # ls -alL /&lt;usershomedirectory&gt;/.dtprofile # ls -alL /&lt;usershomedirectory&gt;/.dispatch # ls -alL /&lt;usershomedirectory&gt;/.emacs # ls -alL /&lt;usershomedirectory&gt;/.exrc # find /&lt;usershomedirectory&gt;/.dt ! -fstype nfs ! -user &lt;username&gt; -exec ls -ld {} \; If local initialization files are not owned by the home directory's user or root, this is a finding.

Fix: F-31703r1_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 filenames 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.

b
All local initialization files must have mode 0740 or less permissive.
AC-6 - Medium - CCI-000225 - V-905 - SV-38493r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001880
Vuln IDs
  • V-905
Rule IDs
  • SV-38493r1_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-36367r1_chk

Check the modes of local initialization files. Procedure: # ls -alL /&lt;usershomedirectory&gt;/.login # ls -alL /&lt;usershomedirectory&gt;/.cschrc # ls -alL /&lt;usershomedirectory&gt;/.logout # ls -alL /&lt;usershomedirectory&gt;/.profile # ls -alL /&lt;usershomedirectory&gt;/.bash_profile # ls -alL /&lt;usershomedirectory&gt;/.bashrc # ls -alL /&lt;usershomedirectory&gt;/.bash_logout # ls -alL /&lt;usershomedirectory&gt;/.env # ls -alL /&lt;usershomedirectory&gt;/.dtprofile (permissions should be 0755) # ls -alL /&lt;usershomedirectory&gt;/.dispatch # ls -alL /&lt;usershomedirectory&gt;/.emacs # ls -alL /&lt;usershomedirectory&gt;/.exrc # find /&lt;usershomedirecotory&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 is more permissive than 0755, or the .dtprofile file is more permissive than 0755, this is a finding.

Fix: F-31704r1_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-38494r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001580
Vuln IDs
  • V-906
Rule IDs
  • SV-38494r1_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-36338r1_chk

Verify run control scripts have no extended ACLs. # ls -lLa /sbin/init.d/[a-z,A-Z,0-9]* If the permissions include a "+" the file has an extended ACL, this is a finding.

Fix: F-31593r1_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 they are world-writable, use the chmod command to correct the vulnerability, and research why they are world-writable. # chmod 755 startupfile

b
Run control scripts executable search paths must contain only absolute paths.
CM-6 - Medium - CCI-000366 - V-907 - SV-38495r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN001600
Vuln IDs
  • V-907
Rule IDs
  • SV-38495r1_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. 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-2, ECCD-1
Checks: C-36339r1_chk

Verify the run control scripts search paths do not contain references to the current working directory or other relative paths in any script where the "PATH" variable occurs. # grep "PATH" /sbin/init.d/[a-z,A-Z,0-9]* | grep -v "_PATH" This variable is formatted as a colon-separated list of directories. If there is an empty entry, such as a leading or trailing colon, or two consecutive colons, this is a finding. If an entry begins with a character other than a slash (/), this is a relative path, and this is a finding.

Fix: F-31594r1_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-38496r2_rule
RMF Control
AC-6
Severity
High
CCI
CCI-000225
Version
GEN001640
Vuln IDs
  • V-910
Rule IDs
  • SV-38496r2_rule
World-writable files could be modified accidentally or maliciously to compromise system integrity.System AdministratorECCD-2, ECCD-1
Checks: C-402r9_chk

Check the permissions on the files or scripts executed from system startup scripts to see if they are world-writable. Create a list of all potential run command level scripts. # ls -l /etc/init.d/* | tr '\011' ' ' | tr -s ' ' | cut -f 9,9 -d " " OR # ls -l /sbin/init.d/* | tr '\011' ' ' | tr -s ' ' | cut -f 9,9 -d " " Create a list of world writeable files. # find / -perm -002 -type f &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 " "` OR # more `ls -l /sbin/init.d/* | tr '\011' ' ' | tr -s ' ' | cut -f 9,9 -d " "` If any system startup script executes any file or script that is world-writable, this is a finding.

Fix: F-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-38499r1_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000196
Version
GEN002000
Vuln IDs
  • V-913
Rule IDs
  • SV-38499r1_rule
Unencrypted passwords for remote FTP servers may be stored in .netrc files. Policy requires passwords to be encrypted in storage and not used in access scripts.System AdministratorIAIA-2, ECCD-2, IAIA-1, ECCD-1
Checks: C-36369r1_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-31706r1_fix

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

a
All files and directories contained in interactive user home directories must be owned by the home directory's owner.
AC-6 - Low - CCI-000225 - V-914 - SV-38497r1_rule
RMF Control
AC-6
Severity
Low
CCI
CCI-000225
Version
GEN001540
Vuln IDs
  • V-914
Rule IDs
  • SV-38497r1_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-36340r5_chk

For each user in the /etc/passwd file, check for the presence of files and directories within the user's home directory that are not owned by the home directory owner. # 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 {} \; Or # ls -lLR `cat /etc/passwd | cut -f 6,6 -d ":"` | more If user home directories contain files or directories not owned by the home directory owner, this is a finding.

Fix: F-31595r1_fix

Change the ownership of files and directories in user home directories to the owner of the home directory. Procedure: # chown <account-owner> <filename>

a
All files and directories contained in user home directories must have mode 0750 or less permissive.
AC-6 - Low - CCI-000225 - V-915 - SV-38498r1_rule
RMF Control
AC-6
Severity
Low
CCI
CCI-000225
Version
GEN001560
Vuln IDs
  • V-915
Rule IDs
  • SV-38498r1_rule
Excessive permissions allow unauthorized access to user files. trueInformation Assurance OfficerSystem AdministratorECLP-1
Checks: C-36341r5_chk

For each user in the /etc/passwd file, check for files and directories with a mode more permissive than 0750. NOTE the following exclusions/exemptions: HP installed users "hpsmh" and "cimsrvr". Note that some home directories "may" restrict access to their files. # find /&lt;usershomedirectory&gt; ! -fstype nfs ! \( -name .login -o -name .cshrc -o -name .logout -o -name .profile -o -name .bash_profile -o -name .bbashrc -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 {} \; Or # ls -lLR `cat /etc/passwd | cut -f 6,6 -d ":"` | more If user home directories contain files or directories more permissive than 0750, this is a finding.

Fix: F-31596r1_fix

Change the mode of files and directories within user 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-34952r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN002120
Vuln IDs
  • V-916
Rule IDs
  • SV-34952r1_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, unsecure shell.System AdministratorECSC-1
Checks: C-36410r1_chk

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

Fix: F-31748r1_fix

Create /etc/shells file containing a list of valid system shells. Consult vendor documentation for an appropriate list of system shells. Procedure: Typical installed shells include: /sbin/sh /usr/bin/sh /usr/bin/rsh /usr/bin/ksh /usr/bin/rksh /usr/bin/csh /usr/bin/keysh # echo "/sbin/sh" >> /etc/shells (Repeat as necessary for all existing shell programs.)

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-35266r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN002140
Vuln IDs
  • V-917
Rule IDs
  • SV-35266r1_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-35098r1_chk

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

Fix: F-30367r1_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.

b
Accounts must be locked upon 35 days of inactivity.
AC-2 - Medium - CCI-000017 - V-918 - SV-38500r2_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-000017
Version
GEN000760
Vuln IDs
  • V-918
Rule IDs
  • SV-38500r2_rule
Inactive user accounts pose a risk to systems and applications. Owners of Inactive accounts will not notice if unauthorized access to their account has been obtained. There is a risk that inactive accounts can potentially be exploited to obtain and maintain undetected access to a system and/or application. The operating system must track periods of user account inactivity and disable all inactive accounts. Non-interactive accounts on the system, such as application accounts, may be documented exceptions. Non-interactive accounts on the system, such as application accounts, may be documented exceptions. Non-interactive accounts on the system, such as application accounts, may be documented exceptions. trueSystem AdministratorIAAC-1
Checks: C-36270r3_chk

For Trusted Mode: Verify that user accounts are locked after 35 days of inactivity. Note: The “u_llogin” attribute is stored in seconds: 86400 seconds/day * 35 days = 3024000 seconds. # cd /tcb/files/auth &amp;&amp; cat */* | egrep “:u_name=|:u_llogin=“ If user account is not set to lock after 35 days of inactivity, this is a finding. For SMSE: Check the INACTIVITY_MAXDAYS setting. # grep INACTIVITY_MAXDAYS /etc/default/security /var/adm/userdb/* If INACTIVITY_MAXDAYS is set to 0 or greater than 35 for any user, this is a finding.

Fix: F-31527r3_fix

For Trusted Mode: Use the SAM/SMH interface to update the “u_llogin” (user last login) /tcb database attribute. See the /tcb database entry example below: :u_llogin#3024000: For SMSE: Note: There may be additional package/bundle updates that must be installed to support attributes in the /etc/default/security file. Use the SAM/SMH interface (/etc/default/security file) and/or the userdbset command (/var/adm/userdb/* files) to update the INACTIVITY_MAXDAYS attribute. See the below example: INACTIVITY_MAXDAYS=35 Note: Never use a text editor to modify any /var/adm/userdb database file. The database contains checksums and other binary data, and editors (vi included) do not follow the file locking conventions that are used to control access to the database. If manually editing the /etc/default/security file, save any change(s) before exiting the editor.

b
All shell files must be owned by root or bin.
AC-6 - Medium - CCI-000225 - V-921 - SV-38501r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002200
Vuln IDs
  • V-921
Rule IDs
  • SV-38501r1_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-36412r1_chk

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

Fix: F-31750r1_fix

Change the ownership of any system shell not owned by root or bin: # chown root <path/shell>

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

If /etc/shells exists, check the group ownership of each shell referenced. # cat /etc/shells | xargs -n1 ls -lL Otherwise, check any shells found on the system. # find / -name "*sh" | xargs -n1 ls -lL If a shell has a mode more permissive than 0755, this is a finding.

Fix: F-31751r1_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-38504r1_rule
RMF Control
CM-3
Severity
Low
CCI
CCI-000318
Version
GEN002260
Vuln IDs
  • V-923
Rule IDs
  • SV-38504r1_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 OfficerECSC-1, DCSW-1
Checks: C-36414r1_chk

NOTE: This will virtually always be a manual review. 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-31752r1_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. A list of device files can be generated with this command: # find / -type b -o -type c -o -type n > 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-38505r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002280
Vuln IDs
  • V-924
Rule IDs
  • SV-38505r1_rule
System device files in writable directories could be modified, removed, or used by an unprivileged user to control system hardware.System AdministratorECLP-1, ECCD-2, ECCD-1
Checks: C-36415r1_chk

Find all device special files existing anywhere on the system. Types include: b=block, c=character, p=fifo. Example: # find / -type b -print &gt;&gt; devicelist # find / -type c -print &gt;&gt; devicelist # find / -type p -print &gt;&gt; devicelist Check the permissions on the directories above subdirectories that contain device files. If any device file, or directory containing device files, is world-writable, except device files specifically intended to be world-writable such as /dev/null, this is a finding. Note the following exception/exclusion list: /dev/pts/*, /dev/pty/*, /dev/ptym/*, the following in dev: full, zero, null, tty, ptmx, pty*, tcp, udp, ip, arp, udp6, tcp6, rawip6, ip6, rawip, rtsock, ipsecpol, ipseckey, sad, dlpi*, sasd*, ttyp*, ttyq*, ttyr*, strlog, telnetm, tlclts, asyncdsk, async, tlcots, tlcotsod, echo, beep, gvid0, gvid, poll, log, log.um, stcpmap, nuls, usctp6, sctp6, usctp and sctp.

Fix: F-31753r1_fix

Remove the world-writable permission from the device file(s). # 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-38506r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002300
Vuln IDs
  • V-925
Rule IDs
  • SV-38506r1_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-36416r1_chk

Check the system for device files read/write enabled for users other than root or the backup user. Example: # find / \( -perm -0020 -o -perm -0040 -o -perm -0002 -o -perm -0004 \) -a \( -type b -o -type c -o -type n \) -exec ls -ld {} \; If any device files used for backup are read/write enabled for users other than root, this is a finding.

Fix: F-31754r1_fix

Use the chmod command to remove the read/write bit(s) from the backup device files. # chmod o-r <b/u device file name> # chmod o-w <b/u device file name> # chmod g-r <b/u device file name> # chmod g-w <b/u device file name> Document all changes.

b
Any Network Information System (NIS+) server must be operating at security level 2.
AC-17 - Medium - CCI-001435 - V-926 - SV-38537r1_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-001435
Version
GEN006460
Vuln IDs
  • V-926
Rule IDs
  • SV-38537r1_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-36723r1_chk

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

Fix: F-32104r1_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-38998r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN005740
Vuln IDs
  • V-928
Rule IDs
  • SV-38998r1_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-35023r1_chk

# echo `ls -lL /etc/exports` | tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' | cut -f 3,3 -d " " If the export configuration file is not owned by root, this is a finding.

Fix: F-30316r1_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-39000r1_rule
RMF Control
AC-6
Severity
Low
CCI
CCI-000225
Version
GEN005760
Vuln IDs
  • V-929
Rule IDs
  • SV-39000r1_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 AdministratorECCD-1, ECLP-1, ECCD-2
Checks: C-35028r1_chk

# echo `ls -lL /etc/exports` | tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' | cut -f 1,1 -d " " If the file has a mode more permissive than 0644, this is a finding.

Fix: F-30320r1_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-39003r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN005800
Vuln IDs
  • V-931
Rule IDs
  • SV-39003r1_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-35036r1_chk

Check for NFS exported file systems. # cat /etc/exports This will display all of the exported file systems. For each file system displayed, check the ownership. Check the owner of the NFS export configuration file. # echo ` ls -lLad &lt;export file system path&gt;` | tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' If the files and directories are not owned by root, this is a finding.

Fix: F-30327r1_fix

Change the ownership of exported file systems not owned by root. # 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-39006r1_rule
RMF Control
AC-14
Severity
Medium
CCI
CCI-000062
Version
GEN005820
Vuln IDs
  • V-932
Rule IDs
  • SV-39006r1_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-2, IAIA-1, ECSC-1
Checks: C-35042r1_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, 65534, or 65535). If an appropriate anon= setting is not present for an exported file system, this is a finding.

Fix: F-1086r2_fix

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

b
The NFS server must be configured to restrict file system access to local hosts.
CM-6 - Medium - CCI-000366 - V-933 - SV-39008r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN005840
Vuln IDs
  • V-933
Rule IDs
  • SV-39008r1_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-36686r1_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-32060r1_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 via the following commands: # exportfs -u <the file system entry that was modified> # exportfs -v <the file system entry that was modified>

b
The NFS server must not allow remote root access.
AC-6 - Medium - CCI-000225 - V-935 - SV-39011r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN005880
Vuln IDs
  • V-935
Rule IDs
  • SV-39011r1_rule
If the NFS server allows root access to local file systems from remote hosts, this access could be used to compromise the system.Information Assurance ManagerInformation Assurance OfficerSystem AdministratorEBRP-1
Checks: C-36687r1_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-32062r1_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-35204r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN005900
Vuln IDs
  • V-936
Rule IDs
  • SV-35204r1_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.System AdministratorInformation Assurance ManagerInformation Assurance OfficerECPA-1
Checks: C-35048r1_chk

Check the system for NFS mounts that do not use the nosuid option. # mount -v | grep " type nfs " | grep -v "nosuid" If the mounted file systems do not have the nosuid option, this is a finding.

Fix: F-30338r1_fix

Edit /etc/fstab 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-35198r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN006580
Vuln IDs
  • V-940
Rule IDs
  • SV-35198r1_rule
Access control programs (such as TCP_WRAPPERS) provide the ability to enhance system security posture.System AdministratorEBRU-1
Checks: C-35044r1_chk

Locate the inetd.conf file (normally located within the /etc directory). # find /etc -type f -name inetd.conf Determine if TCP_WRAPPERS is used. The following example demonstrates one possible single inetd.conf line first without and then with the service tcp wrapped. telnet stream tcp6 nowait root /usr/sbin/telnetd telnetd telnet stream tcp6 nowait root /usr/sbin/tcpd telnetd # cat &lt;path&gt;/inetd.conf | tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' |grep -v "^#" | grep tcpd If there are unwrapped active services listed, this is a finding.

Fix: F-30334r1_fix

Edit /etc/inetd.conf and use tcpd to wrap active services.

b
The system's access control program must log each system’s access attempt.
AU-2 - Medium - CCI-000126 - V-941 - SV-35206r2_rule
RMF Control
AU-2
Severity
Medium
CCI
CCI-000126
Version
GEN006600
Vuln IDs
  • V-941
Rule IDs
  • SV-35206r2_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-2, ECAR-1, ECAR-3
Checks: C-35049r2_chk

Normally, tcpd logs to the mail facility in the syslog.conf file (normally located within the /etc directory). Determine if syslog is configured to log events by tcpd. # find /etc -type f -name syslog.conf # cat &lt;path&gt;/syslog.conf | tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' |grep -v “^#” | egrep “mail.debug|mail.info|mail.\*” Look for an entry similar to the following, indicating that mail alerts are being logged: mail.* /var/log/maillog If no entries for mail exist, then tcpd is not logging and this is a finding.

Fix: F-32112r1_fix

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

b
The system must be configured to operate in a security mode.
CM-2 - Medium - CCI-000293 - V-960 - SV-38681r2_rule
RMF Control
CM-2
Severity
Medium
CCI
CCI-000293
Version
GEN000000-HPUX0020
Vuln IDs
  • V-960
Rule IDs
  • SV-38681r2_rule
When operating in standard mode, account passwords are stored in the /etc/passwd file, which is world readable. By operating in either Trusted Mode or Standard Mode with Security Extensions, the system security posture is enhanced thru the addition of a secure, non-world readable password container other than /etc/passwd.System AdministratorDCSW-1
Checks: C-2278r4_chk

For Trusted Mode: Determine if the /tcb directory tree exists. # ls -lLd /tcb If the /tcb directory tree does not exist, this is a finding. For SMSE: Determine if the userdb directory tree and the /etc/shadow file exists. # ls -lL /var/adm/userdb # ls -lL /etc/shadow If both the /var/adm/userdb directory tree and the /etc/shadow file do not exist, this is a finding.

Fix: F-33047r2_fix

SAM/SMH must be used to convert standard mode HP-UX to Trusted Mode (optional for SMSE). For Trusted Mode only: The following command may be used to “manually” convert from Standard Mode to Trusted Mode (note that its use is not vendor supported): # tsconvert -c For SMSE only: The following command may be used to “manually” create the /etc/shadow file with information from the /etc/passwd file (use of this commend is vendor supported). # pwconv Note that additional software bundles and/or patches may be required in order to completely convert a standard mode system to SMSE.

b
The HP-UX /etc/securetty must be group-owned by root, sys, or bin.
AC-6 - Medium - CCI-000225 - V-965 - SV-965r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN000000-HPUX0080
Vuln IDs
  • V-965
Rule IDs
  • SV-965r2_rule
Root, sys, and bin are the most privileged group accounts, by default, for most UNIX systems. If a file as sensitive as /etc/securetty is not group-owned by a privileged group, it could lead to system compromise.System AdministratorECLP-1
Checks: C-2289r2_chk

ls -lL /etc/securetty

Fix: F-1119r2_fix

Change the group-owner of the /etc/securetty to root, bin, or sys. Example: # chgrp root /etc/securetty

b
The /etc/securetty file must be owned by root.
AC-6 - Medium - CCI-000225 - V-966 - SV-38682r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN000000-HPUX0060
Vuln IDs
  • V-966
Rule IDs
  • SV-38682r1_rule
Failure to make root the owner of sensitive files and utilities may provide unauthorized owners the potential to access and/or change sensitive information or system configurations, thus weakening the overall security posture of a site.System AdministratorECLP-1
Checks: C-37789r1_chk

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

Fix: F-1120r2_fix

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

b
The /etc/securetty file must have mode 0640 or less permissive.
AC-6 - Medium - CCI-000225 - V-967 - SV-967r2_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN000000-HPUX0100
Vuln IDs
  • V-967
Rule IDs
  • SV-967r2_rule
Excessive permissions on the /etc/securetty file could result in unauthorized modification of the file. Changes to the file could reduce the system's security by specifying additional terminals permitted to accept root logins, or deny service by preventing root logins on authorized terminals.System AdministratorECCD-2, ECLP-1, ECCD-1
Checks: C-2290r2_chk

Check the mode of the securetty file. Example: # ls -lL /etc/securetty If /etc/securetty has a mode more permissive than 0640, this is a finding.

Fix: F-1121r2_fix

Change the mode of the /etc/securetty file to 0640. Example: # chmod 0640 /etc/securetty

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-38541r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002960
Vuln IDs
  • V-974
Rule IDs
  • SV-38541r1_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-36431r1_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-31770r1_fix

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

b
The cron.allow file must have mode 0600 or less permissive.
AC-6 - Medium - CCI-000225 - V-975 - SV-38542r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002980
Vuln IDs
  • V-975
Rule IDs
  • SV-38542r1_rule
A cron.allow file, 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-36432r1_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 0600, this is a finding.

Fix: F-31771r1_fix

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

b
Cron must not execute group-writable or world-writable programs.
AC-6 - Medium - CCI-000225 - V-976 - SV-38543r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003000
Vuln IDs
  • V-976
Rule IDs
  • SV-38543r1_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-36434r1_chk

List all cronjobs on the system. Procedure: # ls -lL /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 -lLa &lt;cron program file&gt; If cron executes group-writable or world-writable files, this is a finding.

Fix: F-31773r1_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-38544r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003020
Vuln IDs
  • V-977
Rule IDs
  • SV-38544r1_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-36433r1_chk

List all cronjobs on the system. Procedure: # ls -lL /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 -lLd &lt;cron program directory&gt; If cron executes programs in world-writable directories, this is a finding.

Fix: F-31772r1_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-38545r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003080
Vuln IDs
  • V-978
Rule IDs
  • SV-38545r1_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-36451r1_chk

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

Fix: F-31790r1_fix

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

b
Cron and crontab directories must have mode 0755 or less permissive.
AC-6 - Medium - CCI-000225 - V-979 - SV-38546r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003100
Vuln IDs
  • V-979
Rule IDs
  • SV-38546r1_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-36452r1_chk

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

Fix: F-1133r2_fix

Change the mode of crontab directories to 0755.

b
Cron and crontab directories must be owned by root or bin.
AC-6 - Medium - CCI-000225 - V-980 - SV-38547r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003120
Vuln IDs
  • V-980
Rule IDs
  • SV-38547r1_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-36453r1_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-31792r1_fix

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

b
Cron and crontab directories must be group-owned by root, sys, bin or other.
AC-6 - Medium - CCI-000225 - V-981 - SV-38548r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003140
Vuln IDs
  • V-981
Rule IDs
  • SV-38548r1_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-36454r1_chk

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

Fix: F-31793r1_fix

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

b
Cron logging must be implemented.
AU-2 - Medium - CCI-000126 - V-982 - SV-38549r1_rule
RMF Control
AU-2
Severity
Medium
CCI
CCI-000126
Version
GEN003160
Vuln IDs
  • V-982
Rule IDs
  • SV-38549r1_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-36455r1_chk

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

Fix: F-31794r1_fix

Enable cron/logging on the system via: # /sbin/init.d/cron stop # mv <current cron log> <to a new location and new name> # /sbin/init.d/cron start # more /var/adm/cron/log Cron automatically handles its own logging function and (at least) the Start Time should be visible at the beginning of the new log file /var/adm/cron/log.

b
The cronlog file must have mode 0600 or less permissive.
AC-6 - Medium - CCI-000225 - V-983 - SV-38550r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003180
Vuln IDs
  • V-983
Rule IDs
  • SV-38550r1_rule
Cron logs contain reports of scheduled system activities and must be protected from unauthorized access or manipulation.System AdministratorECLP-1, ECTP-1
Checks: C-36456r1_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-31795r1_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-35033r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003280
Vuln IDs
  • V-984
Rule IDs
  • SV-35033r1_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-36457r1_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-31796r1_fix

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

b
The at.deny file must not be empty if it exists.
AC-6 - Medium - CCI-000225 - V-985 - SV-38551r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003300
Vuln IDs
  • V-985
Rule IDs
  • SV-38551r1_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-36458r1_chk

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

Fix: F-31797r1_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-38552r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003320
Vuln IDs
  • V-986
Rule IDs
  • SV-38552r1_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-36459r1_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-31799r1_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 0600 or less permissive.
AC-6 - Medium - CCI-000225 - V-987 - SV-38553r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003340
Vuln IDs
  • V-987
Rule IDs
  • SV-38553r1_rule
Permissions more permissive than 0600 (i.e. read, write and execute for the owner) may allow unauthorized or malicious access to the at.allow and/or at.deny files.System AdministratorECLP-1
Checks: C-36460r1_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 0600, this is a finding.

Fix: F-31800r1_fix

Change the mode of the at.allow file. # chmod 0600 /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-38554r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003360
Vuln IDs
  • V-988
Rule IDs
  • SV-38554r1_rule
If the at facility executes group- or world-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-36461r1_chk

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

Fix: F-31801r1_fix

Remove group-write and world-write permissions from files executed by at jobs. # 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-38555r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003380
Vuln IDs
  • V-989
Rule IDs
  • SV-38555r1_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-36462r1_chk

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

Fix: F-31802r1_fix

Remove the world-writable permission from directories containing programs executed by at. # 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-35172r1_rule
RMF Control
IA-5
Severity
High
CCI
CCI-000178
Version
GEN005300
Vuln IDs
  • V-993
Rule IDs
  • SV-35172r1_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 using the information to potentially compromise the integrity of the system or network(s).System AdministratorIAAC-1
Checks: C-36606r1_chk

Check the SNMP configuration for default passwords. Locate and examine the SNMP configuration. # more /etc/SnmpAgent.d/snmpd.conf Alternatively: # cat /etc/SnmpAgent.d/snmpd.conf | grep -i community 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-31974r1_fix

Change the default passwords. To change them, edit the /etc/SnmpAgent.d/snmpd.conf 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 reading 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 will not be 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-35176r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN005320
Vuln IDs
  • V-994
Rule IDs
  • SV-35176r1_rule
The snmpd.conf file contains authenticators and must be protected from unauthorized access and modification.System AdministratorECLP-1
Checks: C-36612r1_chk

Check the mode of the SNMP daemon configuration file. # ls -lL /etc/SnmpAgent.d/snmpd.conf If the /etc/SnmpAgent.d/snmpd.conf file has a mode more permissive than 0600, this is a finding.

Fix: F-31978r1_fix

Change the mode of the SNMP daemon configuration file to 0600. # chmod 0600 /etc/SnmpAgent.d/snmpd.conf

b
Management Information Base (MIB) files must have mode 0640 or less permissive.
AC-6 - Medium - CCI-000225 - V-995 - SV-35178r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN005340
Vuln IDs
  • V-995
Rule IDs
  • SV-35178r1_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-36613r1_chk

Check the modes for all MIB files on the system. # find / -type f -name *.mib -exec ls -lL {} \; If any file is returned without a mode 0640 or less permissive, this is a finding.

Fix: F-31979r1_fix

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

a
Inetd or xinetd logging/tracing must be enabled.
AU-3 - Low - CCI-000134 - V-1011 - SV-35085r1_rule
RMF Control
AU-3
Severity
Low
CCI
CCI-000134
Version
GEN003800
Vuln IDs
  • V-1011
Rule IDs
  • SV-35085r1_rule
Inetd or xinetd logging and tracing allows the system administrators to observe the IP addresses connecting to their machines and to observe what network services are being sought. This provides valuable information when trying to find the source of malicious users and potential malicious users.System AdministratorECAR-1, ECSC-1, ECAR-2, ECAR-3
Checks: C-36533r1_chk

# ps -ef | grep -v grep | egrep -i "inetd|xinetd" If the -l logging parameter is not used, this is a finding. If the (x)inetd process is not running, this is not a finding.

Fix: F-31897r1_fix

Edit the (x)inetd startup script to include the -l parameter for the internet daemon process.

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

HP-UX 11-v2 may be booted from the following system startup media (must have been previously configured by root): • Hard drives • CD/DVD drives (for installation) • Tape drives (for installation) • USB device (configured with the Ignite boot content) Determine if the system is configured to boot from devices other than the system startup media. Verification should (optimally) be performed during IPL/ISL boot. In lieu of rebooting the system, ask the SA if the system is configured to boot from devices other than system startup media. If so, this is a finding.

Fix: F-1167r2_fix

Configure the system to only boot from system startup media.

b
The system must not run an Internet Network News (INN) server.
CM-7 - Medium - CCI-000381 - V-1023 - SV-38236r1_rule
RMF Control
CM-7
Severity
Medium
CCI
CCI-000381
Version
GEN006240
Vuln IDs
  • V-1023
Rule IDs
  • SV-38236r1_rule
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-36722r2_chk

Check the domain name for NIS maps. Procedure: # domainname If the name returned is simple to guess, such as the organization name, building, or room name, etc., this is a finding.

Fix: F-32085r1_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-35211r1_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-001436
Version
GEN006080
Vuln IDs
  • V-1026
Rule IDs
  • SV-35211r1_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-36693r3_chk

Determine if the CIFS (HP SAMBA) bundle is installed (SWAT is included). # swlist -l bundle | egrep -i "CIFS-CLIENT|CIFS-SERVER" If the HP bundle is not installed, this is not applicable. If the HP bundle is installed, ask the SA if the Samba Web Administration Tool (SWAT) has been configured to use SSL. If SWAT is not configured to use SSL, this is a finding.

Fix: F-32068r2_fix

Disable SWAT. # chmod 0000 <path>/swat OR # rm -i <path>/swat

b
The /etc/smb.conf file must be owned by root.
AC-6 - Medium - CCI-000225 - V-1027 - SV-35213r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN006100
Vuln IDs
  • V-1027
Rule IDs
  • SV-35213r1_rule
The /etc/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-36694r1_chk

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

Fix: F-32069r1_fix

Change the ownership of the smb.conf file. # chown root /etc/opt/samba/smb.conf

b
The /etc/opt/samba/smb.conf file must have mode 0644 or less permissive.
AC-6 - Medium - CCI-000225 - V-1028 - SV-35221r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN006140
Vuln IDs
  • V-1028
Rule IDs
  • SV-35221r1_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-36697r1_chk

Check the mode of the smb.conf file. # ls -lL /etc/opt/samba/smb.conf If the smb.conf has a mode more permissive than 0644, this is a finding.

Fix: F-32071r1_fix

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

b
The smbpasswd file must be owned by root.
AC-6 - Medium - CCI-000225 - V-1029 - SV-35225r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN006160
Vuln IDs
  • V-1029
Rule IDs
  • SV-35225r1_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-36700r1_chk

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

Fix: F-32074r1_fix

Use the chown command to configure the smb passwd file. # chown root <path>/smbpasswd

b
The smb.conf file must use the hosts option to restrict access to Samba.
AC-6 - Medium - CCI-000225 - V-1030 - SV-35107r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN006220
Vuln IDs
  • V-1030
Rule IDs
  • SV-35107r1_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-36704r1_chk

Examine the smb.conf file. # cat /etc/opt/samba/smb.conf | tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' | grep -v "^#" | egrep "^hosts|^ hosts allow|^hosts deny" If the hosts option is not present to restrict access to a list of authorized hosts and networks, this is a finding.

Fix: F-32079r1_fix

Edit the smb.conf file and set the hosts option to permit only authorized hosts access Samba. An example might be: hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24 hosts deny = 0.0.0.0/0 The above will only allow SMB connections from the localhost and from the two private networks 192.168.2 and 192.168.3. All other connections will be refused as soon as the client sends its first packet.

b
Users must not be able to change passwords more than once every 24 hours.
IA-5 - Medium - CCI-000198 - V-1032 - SV-38199r2_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000198
Version
GEN000540
Vuln IDs
  • V-1032
Rule IDs
  • SV-38199r2_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-36255r3_chk

For Trusted Mode: Check the “u_minchg” attribute in the users TS database entry. Individual user: # export PATH=$PATH:/usr/lbin # getprpw -r -m mintm &lt;USER&gt; All users: # logins -o -x | awk -F: '{print $1” “$10}' If the value is less than 1 for any user, this is a finding. For SMSE: Check the PASSWORD_MINDAYS attribute. # grep PASSWORD_MINDAYS /etc/default/security /var/adm/userdb/* If the attribute PASSWORD_MINDAYS is less than 1, this is a finding.

Fix: F-31512r2_fix

For both Trusted Mode and SMSE: Use the SAM/SMH interface to ensure that password changes are restricted to no less than once every 24 hours. Use the SAM/SMH interface (/etc/default/security file) and/or the userdbset command (/var/adm/userdb/* files) to ensure that password changes are restricted to no less than once every 24 hours. See the below example: PASSWORD_MINDAYS=1 Note: Never use a text editor to modify any /var/adm/userdb database file. The database contains checksums and other binary data, and editors (vi included) do not follow the file locking conventions that are used to control access to the database. If manually editing the /etc/default/security file, save any change(s) before exiting the editor.

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

Perform the following to determine if root has logged in over an unencrypted network connection. The first command determines if root has logged in over a network. The second will check to see if the SSH daemon is running. Procedure: # last -R | grep "^root " | egrep -v "reboot|console" | more # ps -ef |grep sshd If the output from the last command shows root has logged in over the network and sshd is not running, this is a finding.

Fix: F-31537r1_fix

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

b
The system must not permit root logins using remote access programs such as SSH.
IA-2 - Medium - CCI-000770 - V-1047 - SV-38207r1_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-000770
Version
GEN001120
Vuln IDs
  • V-1047
Rule IDs
  • SV-38207r1_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-36279r1_chk

Check the SSH daemon configuration. Note that keywords are case-insensitive and arguments (args) are case-sensitive. keyword=PermitRootLogin Required arg(s)=no Default arg values include: "yes" Note: When the default "arg" value exactly matches the required "arg" value (see above), the &lt;keyword=arg&gt; are not required to exist (commented or uncommented) in the ssh (client) or sshd (server) configuration file. While not required, it is recommended that the configuration file(s) be populated with all keywords and assigned arg values as a means to explicitly document the ssh(d) binary's expected behavior. Examine the file. # cat /opt/ssh/etc/sshd_config | tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' | grep -v '^#' | grep -i "PermitRootLogin" If the return value is yes, without-password or forced-commands-only, this is a finding.

Fix: F-24426r1_fix

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

b
Audio devices must have mode 0660 or less permissive.
AC-6 - Medium - CCI-000225 - V-1048 - SV-38241r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002320
Vuln IDs
  • V-1048
Rule IDs
  • SV-38241r1_rule
Globally accessible audio and video devices have proven to be another security hazard. There is software capable of activating 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 into a bugging device.System AdministratorECLP-1
Checks: C-36418r1_chk

Check the mode of audio device files. Determine audio devices and class identifiers, i.e., audio should be listed as audio. # ioscan Determine audio device special files. # ioscan -fn -C &lt;audio class ID from the above command output&gt; Determine the device file mode. # ls -lL &lt;device special file&gt; If the mode of any audio device file is more permissive than 0660, this is a finding.

Fix: F-31756r1_fix

Change the mode of audio devices. # chmod 0660 <audio device>

b
Audio devices must be owned by root.
AC-6 - Medium - CCI-000225 - V-1049 - SV-38242r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002340
Vuln IDs
  • V-1049
Rule IDs
  • SV-38242r1_rule
Globally accessible audio and video devices have proven to be another security hazard. There is software capable of activating 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 into a bugging device.System AdministratorECLP-1
Checks: C-36419r1_chk

Check the owner of audio devices. Determine audio devices and class identifiers, i.e., audio should be listed as audio. # ioscan Determine audio device special files. # ioscan -fn -C &lt;audio class ID from the above command output&gt; Determine the device file mode. # ls -lL &lt;device special file&gt; If the owner of any audio device file is not root, this is a finding.

Fix: F-31757r1_fix

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

b
The /etc/smb.conf file must be group-owned by root, bin, sys, or system.
AC-6 - Medium - CCI-000225 - V-1056 - SV-35219r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN006120
Vuln IDs
  • V-1056
Rule IDs
  • SV-35219r1_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-35063r1_chk

Check the group ownership of the smb.conf file. # find / -type f -name smb.conf | xargs -n1 ls -lL If the smb.conf file is not group-owned by root, bin, sys or other, this is a finding.

Fix: F-30350r1_fix

Change the group owner of the "smb.conf" file. # chgrp root /etc/samba/smb.conf

b
The smbpasswd file must be group-owned by root.
AC-6 - Medium - CCI-000225 - V-1058 - SV-37880r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN006180
Vuln IDs
  • V-1058
Rule IDs
  • SV-37880r1_rule
If the smbpasswd file is not group-owned by root, it may be maliciously accessed or modified, potentially resulting in the compromise of Samba accounts.System AdministratorECLP-1
Checks: C-37107r1_chk

Check smbpasswd ownership: # ls -lL /var/opt/samba/private/smbpasswd If the smbpasswd file is not group-owned by root, this is a finding.

Fix: F-32374r1_fix

Use the chgrp command to ensure that the group owner of the smbpasswd file is root. # chgrp root <path>/smbpasswd

b
The smbpasswd file must have mode 0600 or less permissive.
AC-6 - Medium - CCI-000225 - V-1059 - SV-37883r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN006200
Vuln IDs
  • V-1059
Rule IDs
  • SV-37883r1_rule
If the smbpasswd file has a mode more permissive than 0600, it may be maliciously accessed or modified, potentially resulting in the compromise of Samba accounts.System AdministratorECLP-1
Checks: C-37108r1_chk

Check the mode of files maintained using smbpasswd. # ls -lL /var/opt/samba/private/smbpasswd If the smbpasswd file is more permissive than 0600, this is a finding.

Fix: F-32376r1_fix

Change the mode of the smbpasswd file to 0600. # chmod 0600 <path>/smbpasswd

b
Audio devices must be group-owned by root, sys, bin, or system.
AC-6 - Medium - CCI-000225 - V-1061 - SV-27252r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002360
Vuln IDs
  • V-1061
Rule IDs
  • SV-27252r1_rule
Without privileged group owners, audio devices will be vulnerable to being used as eaves-dropping devices by malicious users or intruders possibly listening to conversations containing sensitive information. System AdministratorECLP-1
Checks: C-28284r1_chk

Check the group-owner of audio devices. Procedure: # /usr/sbin/ioscan -f # ls -lL &lt;audio device file&gt; 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>

a
The root shell must be located in the / file system.
CM-6 - Low - CCI-000366 - V-1062 - SV-38208r1_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GEN001080
Vuln IDs
  • V-1062
Rule IDs
  • SV-38208r1_rule
To ensure the root shell is available in repair and administrative modes, the root shell must be located in the / file system.System AdministratorECSC-1
Checks: C-36281r1_chk

Determine if the root shell is located on / (IE: a non-mounted file system). # cat /etc/passwd | grep "^root:" | awk -F ":" '{print $NF}' # grep &lt;shell location from above&gt; /etc/fstab If the root shell is located on a mountable file system listed in /etc/fstab, this is a finding.

Fix: F-31538r1_fix

Change the root account's shell to one present on the / file system.

b
Graphical desktop environments provided by the system must automatically lock after 15 minutes of inactivity and must require users to re-authenticate to unlock the environment.
AC-11 - Medium - CCI-000057 - V-4083 - SV-38416r1_rule
RMF Control
AC-11
Severity
Medium
CCI
CCI-000057
Version
GEN000500
Vuln IDs
  • V-4083
Rule IDs
  • SV-38416r1_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-36256r1_chk

Examine the dtsession timeout variable setting. # cat /etc/dt/config/C/sys.resources | grep -i dtsession | grep -i lockTimeout If the dtsession timeout is higher than 15, commented or does not exist, this is a finding.

Fix: F-31513r1_fix

Configure the CDE lock manager to lock your screen after a certain amount of inactive time. To configure the CDE lock manager to lock the screen after 15 minutes of inactive time, enter the following commands (ensure to NOT overwrite an existing file): # cp /usr/dt/config/C/sys.resources /etc/dt/config/C/sys.resources # vi /etc/dt/config/C/sys.resources Locate and add/uncomment/change the line to N=15 dtsession*lockTimeout: <N> dtsession*lockTimeout: 15 Log out of CDE and log back in to verify the timeout is in effect.

b
The system must prohibit the reuse of passwords within five iterations.
IA-5 - Medium - CCI-000200 - V-4084 - SV-38417r2_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000200
Version
GEN000800
Vuln IDs
  • V-4084
Rule IDs
  • SV-38417r2_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, this 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-36283r2_chk

For Trusted Mode: Check the PASSWORD_HISTORY_DEPTH setting. # cat /etc/default/security | grep PASSWORD_HISTORY_DEPTH If PASSWORD_HISTORY_DEPTH is not set to 5 or greater, this is a finding. For SMSE: Check the PASSWORD_HISTORY_DEPTH setting. # grep PASSWORD_HISTORY_DEPTH /etc/default/security /var/adm/userdb/* If PASSWORD_HISTORY_DEPTH is not set to 5 or greater, this is a finding.

Fix: F-31540r2_fix

For Trusted Mode: Use the SAM/SMH interface or edit the /etc/default/security file and update the PASSWORD_HISTORY_DEPTH attribute. See the below example: PASSWORD_HISTORY_DEPTH=5 If manually editing the file, save any change(s) before exiting the editor. For SMSE: Note: There may be additional package/bundle updates that must be installed to support attributes in the /etc/default/security file. Use the SAM/SMH interface (/etc/default/security file) and/or the userdbset command (/var/adm/userdb/* files) to update the PASSWORD_HISTORY_DEPTH attribute. See the below example: PASSWORD_HISTORY_DEPTH=5 Note: Never use a text editor to modify any /var/adm/userdb database file. The database contains checksums and other binary data, and editors (vi included) do not follow the file locking conventions that are used to control access to the database. If manually editing the /etc/default/security file, save any change(s) before exiting the editor.

b
User start-up files must not execute world-writable programs.
AC-6 - Medium - CCI-000225 - V-4087 - SV-38418r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001940
Vuln IDs
  • V-4087
Rule IDs
  • SV-38418r1_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 compromise the system at the user level or higher. 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-36370r1_chk

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

Fix: F-31707r1_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-38420r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001660
Vuln IDs
  • V-4089
Rule IDs
  • SV-38420r1_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-36372r2_chk

System start-up files are identified as follows: Run control scripts reside in the /sbin/init.d directory. Links to the run control scripts exist in the /sbin/rc*.d directories. Run control configuration files exist in the /etc/rc.config.d directory. Check all system start-up script file ownership. # ls -lL /sbin/init.d/* /sbin/rc*.d/* /etc/rc.config.d/* If any system start-up script file is not owned by root or bin, this is a finding.

Fix: F-31709r1_fix

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

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

System start-up files are identified as follows: Run control scripts reside in the /sbin/init.d directory. Links to the run control scripts exist in the /sbin/rc*.d directories. Run control script configuration files exist in the /etc/rc.config.d directory. Check system start-up script file group ownership. # ls -lL /sbin/init.d/* /etc/rc.config.d/* /etc/rc.config.d/* If any system start-up script file is not group-owned by root, sys, bin or other, this is a finding.

Fix: F-31711r1_fix

Change the group ownership of the run control script(s) with incorrect group ownership. Procedure: # chgrp root <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-38422r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN001700
Vuln IDs
  • V-4091
Rule IDs
  • SV-38422r1_rule
System start-up files that execute programs owned by other than root (or another privileged user) or an application indicate that the system may have been compromised.System AdministratorDCSL-1
Checks: C-36374r2_chk

Determine the ownership of programs executed by system start-up files. # more `ls -alL /sbin/init.d/* | tr '\011' ' ' | tr -s ' ' | cut -f 9,9 -d " "` If any executed program is not owned by root, sys, bin, or in rare cases, an application account, this is a finding.

Fix: F-31712r2_fix

Change the ownership of the file executed from system startup scripts to root, bin, sys, or the application account, where required. # 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-38423r1_rule
RMF Control
AC-3
Severity
Medium
CCI
CCI-000213
Version
GEN008620
Vuln IDs
  • V-4246
Rule IDs
  • SV-38423r1_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-36797r1_chk

On systems with a BIOS or system controller, verify a supervisor or administrator password is set. If a password is not set, this is a finding. Attempt to log into the system controller first using the user/pwd format of Admin/Admin, then as Oper/Oper. Also, depending upon the MP/SP/GSP, it may also allow for simple carriage return entry &lt;CR&gt;/&lt;CR&gt; if account(s)/password(s) are uninitialized. If the BIOS or system controller supports user-level access in addition to supervisor/administrator access, determine if this access is enabled. If so, this is a finding.

Fix: F-32174r1_fix

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

c
The system must not use removable media as the boot loader.
CM-6 - High - CCI-000366 - V-4247 - SV-38424r1_rule
RMF Control
CM-6
Severity
High
CCI
CCI-000366
Version
GEN008640
Vuln IDs
  • V-4247
Rule IDs
  • SV-38424r1_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-40611r1_chk

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

Fix: F-32175r1_fix

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

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-38425r1_rule
RMF Control
SC-32
Severity
High
CCI
CCI-001208
Version
GEN008680
Vuln IDs
  • V-4255
Rule IDs
  • SV-38425r1_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.Information Assurance OfficerSystem AdministratorPESS-1
Checks: C-36799r1_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-32176r1_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-38426r1_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-000012
Version
GEN000290
Vuln IDs
  • V-4269
Rule IDs
  • SV-38426r1_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-36257r1_chk

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

Fix: F-31514r1_fix

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

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

Locate/check the hosts.nntp permissions. # find / -type f -name hosts.nntp | xargs -n1 ls -lL If hosts.nntp has a mode more permissive than 0600, this is a finding.

Fix: F-30262r1_fix

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

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

Check hosts.nntp.nolimit permissions. # find / -type f -name hosts.nntp.nolimit | xargs -n1 ls -lL If hosts.nntp.nolimit has a mode more permissive than 0600, this is a finding.

Fix: F-30264r1_fix

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

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

Check nnrp.access permissions. # find / -type f -name nnrp.access | xargs -n1 ls -lL If nnrp.access has a mode more permissive than 0600, this is a finding.

Fix: F-30266r1_fix

Change the mode of the nnrp.access file to 0600. # chmod 0600 <path>/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-35120r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN006320
Vuln IDs
  • V-4276
Rule IDs
  • SV-35120r1_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-34978r1_chk

Check passwd.nntp permissions. # find / -type f -name passwd.nntp | xargs -n1 ls -lL If passwd.nntp has a mode more permissive than 0600, this is a finding.

Fix: F-30272r1_fix

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

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

Check the ownership of the files in news. # find /var/news -type f | xargs -n1 ls -lL If any files are not owned by root or news, this is a finding.

Fix: F-30274r1_fix

Change the ownership of the files in <path>/news to root or news. # chown root <path>/news/*

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

Check news files group ownership. # find /var/news -type f | xargs -n1 ls -lL If news files are not group-owned by root or news, this is a finding.

Fix: F-30278r1_fix

Change the group owner of the files in news to root or news. # chgrp root <path>/news/*

b
The HP-UX AUDOMON_ARGS attribute must be explicitly initialized.
AU-2 - Medium - CCI-000126 - V-4290 - SV-38429r2_rule
RMF Control
AU-2
Severity
Medium
CCI
CCI-000126
Version
GEN000000-HPUX0040
Vuln IDs
  • V-4290
Rule IDs
  • SV-38429r2_rule
The minimal set of auditing requirements necessary to collect useful forensics data and provide user help when violations are detected must be configured.System AdministratorECAR-2, ECAR-1, ECAR-3
Checks: C-36226r2_chk

Check the /etc/rc.config.d/auditing file AUDOMON_ARGS settings: # cat /etc/rc.config.d/auditing | tr “\011” “ “ | tr -s “ “ | sed -e 's/^[ \t]*//' grep -v “#” The above command should return a single line with the following information: AUDOMON_ARGS=“-p 20, -t 1, -w 90” If “p”, “t”, or “w” flags are not set to “20”, “1”, and “90”, respectively, this is a finding.

Fix: F-31485r2_fix

Edit the /etc/rc.config.d/auditing file and insert the following line: AUDOMON_ARGS=“-p 20, -t 1, -w 90” Restart auditing: # /sbin/init.d/auditing stop # /sbin/init.d/auditing start

c
The SSH daemon must be configured to only use the SSHv2 protocol.
AC-17 - High - CCI-001436 - V-4295 - SV-35209r1_rule
RMF Control
AC-17
Severity
High
CCI
CCI-001436
Version
GEN005500
Vuln IDs
  • V-4295
Rule IDs
  • SV-35209r1_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-35053r1_chk

Check the SSH daemon configuration. Note that keywords are case-insensitive and arguments (args) are case-sensitive. keyword=Protocol Required arg(s)=2 Default arg values include: "2,1" Note: When the default "arg" value exactly matches the required "arg" value (see above), the &lt;keyword=arg&gt; are not required to exist (commented or uncommented) in the ssh (client) or sshd (server) configuration file. While not required, it is recommended that the configuration file(s) be populated with all keywords and assigned arg values as a means to explicitly document the ssh(d) binary's expected behavior. Examine the file. # cat /opt/ssh/etc/sshd_config | tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' | grep -v '^#' | grep -i "Protocol" | cut -f 2,2 -d " " If the return value is "1" or "2,1" (double quotes are for emphasis only) , this is a finding.

Fix: F-30340r1_fix

Edit the configuration file and modify the Protocol line entry to appear as follows: Protocol 2

b
Remote consoles must be disabled or protected from unauthorized access.
AC-17 - Medium - CCI-000070 - V-4298 - SV-27148r2_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-000070
Version
GEN001000
Vuln IDs
  • V-4298
Rule IDs
  • SV-27148r2_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-28074r3_chk

Check /etc/securetty # more /etc/securetty If the /etc/securetty file does not exist, or contains other than "console" or "/dev/null" this is a finding.

Fix: F-24422r4_fix

If the /etc/securetty file does not exist, create the file containing only the word console and ensure correct file properties. # echo “console” > /etc/securetty

b
The system clock must be synchronized to an authoritative DoD time source.
AU-8 - Medium - CCI-001492 - V-4301 - SV-38428r1_rule
RMF Control
AU-8
Severity
Medium
CCI
CCI-001492
Version
GEN000240
Vuln IDs
  • V-4301
Rule IDs
  • SV-38428r1_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 synchronized 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-36233r4_chk

Check Content: Check the root crontab for ntpdate jobs running at least daily. If cron is used, this command must return a line with the following required format: columns 3, 4, and 5 must be an asterisk (*) for the job to be run daily. # crontab -l | grep ntpdate OR Check that ntpd is used for system clock synchronization. If ntpd is used, this command must return a line starting with an asterisk followed by the name of the remote host that the local system is synchronized with. # ntpq -p | grep "^*" If the system clock is not being synchronized continuously (via ntpd) or at least daily (via cron), this is a finding.

Fix: F-31492r2_fix

Use a local authoritative time server synchronizing to an authorized DoD time source. Ensure all systems in the facility feed from one or more local time servers feeding from the authoritative time server. View the current system (x)ntpd man page for a detailed discussion of configuration option details: # man xntpd Create/edit the ntp.conf file, delete any non-local and/or non-U.S. DoD sources and insert the local or an authoritative U.S. DoD source. Example /etc/ntp.conf file: # # server : ntp server used (poll) to obtain time server <IP or hostname for 1st server> server <IP or hostname for 2nd server> # # peer : a peer relationship with another ntp server peer <IP or hostname for ntp peer> # # driftfile : track local clock time (drift of the local clock) driftfile <drift file name, default is /etc/ntp.drift> Stop/restart (x)ntpd. The default system script to start ntp should be found in the system startup directory /sbin/init.d : # /sbin/init.d/xntpd start

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

Logging should be enabled for those types of files systems that do not turn on logging by default. # mount Alternatively: # cat /etc/fstab | tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' | grep -v "^#" | \ cut -f 2,3 -d " " | grep "/ " | grep -c -i "vxfs" If the above command return value is 1, vxfs journaling is in use, this is not a finding. JFS, VXFS, HFS, XFS, reiserfs, EXT3 and EXT4 all turn logging on by default and will not be a finding. The ZFS file system uses other mechanisms to provide for file system consistency, and will not be a finding. For other file systems types, if the root file system does not have the logging option, this is a finding. If the nolog option is set on the root file system, this is a finding.

Fix: F-30232r1_fix

Implement file system journaling for the root file system, or use a file system that uses other mechanisms to ensure file system consistency. If the root file system supports journaling, enable it. If the file system does not support journaling or another mechanism to ensure file system 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-35208r1_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-001436
Version
GEN006060
Vuln IDs
  • V-4321
Rule IDs
  • SV-35208r1_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 AdministratorDCPD-1, ECSC-1
Checks: C-36692r1_chk

Check the system for a running Samba server. # ps -ef |grep -v grep | 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-32067r1_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-38427r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN002860
Vuln IDs
  • V-4357
Rule IDs
  • SV-38427r1_rule
Rotate audit logs daily to preserve audit file system space and to conform to the DoD 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-36435r1_chk

Check for a crontab entry that rotates audit logs. # crontab -l If any cron job to rotate audit logs is found, this is not a finding. Otherwise, query the SA. If there is a process that automatically rotates 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-31774r1_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 0600 or less permissive.
AC-6 - Medium - CCI-000225 - V-4358 - SV-38430r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003200
Vuln IDs
  • V-4358
Rule IDs
  • SV-38430r1_rule
If file permissions for cron.deny are more permissive than 0600, sensitive information could be viewed or edited by unauthorized users.System AdministratorECLP-1
Checks: C-36463r1_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 0600, this is a finding.

Fix: F-31803r1_fix

Change the mode of the cron.deny file. # chmod 0600 /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-38431r1_rule
RMF Control
AC-6
Severity
Low
CCI
CCI-000225
Version
GEN003220
Vuln IDs
  • V-4360
Rule IDs
  • SV-38431r1_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-36464r1_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-31804r1_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-38432r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003240
Vuln IDs
  • V-4361
Rule IDs
  • SV-38432r1_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-36465r1_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-31807r1_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-38433r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003400
Vuln IDs
  • V-4364
Rule IDs
  • SV-38433r1_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-36466r1_chk

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

Fix: F-31808r1_fix

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

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

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

Fix: F-31809r1_fix

Change the owner of the existing at directory to root, bin, or sys. # chown root <at directory> (Replace root with another system group and/or <at directory> with a different at directory as necessary.)

b
"At" jobs must not set the umask to a value less restrictive than 077.
AC-6 - Medium - CCI-000225 - V-4366 - SV-34996r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003440
Vuln IDs
  • V-4366
Rule IDs
  • SV-34996r1_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 AdministratorECCD-2, ECCD-1
Checks: C-34871r1_chk

Determine what at jobs exist on the system. Procedure: # ls /var/spool/cron/atjobs If there are no at jobs present, this is not applicable. Determine if any of the at jobs or any scripts referenced execute the umask command. Check for any umask setting more permissive than 077. # grep -n 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. NOTE: The at facility will set the execution environment umask to 022. A grep of the at file will normally yield a line in the file that may look like umask 2. When examining any at job command file, this should not be mistaken for a user defined umask (re-)setting.

Fix: F-30201r1_fix

Edit at jobs or referenced scripts to remove umask commands setting the umask value more permissive than 077.

b
The at.allow file must be owned by root, bin, or sys.
AC-6 - Medium - CCI-000225 - V-4367 - SV-34997r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003460
Vuln IDs
  • V-4367
Rule IDs
  • SV-34997r1_rule
If the owner of the at.allow file is not set to root, sys, or bin, unauthorized users could be allowed to view or edit sensitive information contained within the file.System AdministratorECLP-1
Checks: C-34872r1_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-30202r1_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-34998r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003480
Vuln IDs
  • V-4368
Rule IDs
  • SV-34998r1_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-34873r1_chk

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

Fix: F-30203r1_fix

Change the owner of the at.deny file. # chown root /usr/lib/cron/at.deny

b
The traceroute command owner must be root.
AC-6 - Medium - CCI-000225 - V-4369 - SV-35151r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003960
Vuln IDs
  • V-4369
Rule IDs
  • SV-35151r1_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-35008r2_chk

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

Fix: F-30302r2_fix

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

b
The traceroute command must be group-owned by sys, bin, root, or other.
AC-6 - Medium - CCI-000225 - V-4370 - SV-35154r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003980
Vuln IDs
  • V-4370
Rule IDs
  • SV-35154r1_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-35010r1_chk

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

Fix: F-30305r1_fix

Change the group-owner of the traceroute command to root. See the following example: # chgrp root /usr/contrib/bin/traceroute

b
The traceroute file must have mode 0700 or less permissive.
AC-6 - Medium - CCI-000225 - V-4371 - SV-38435r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN004000
Vuln IDs
  • V-4371
Rule IDs
  • SV-38435r1_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-36553r1_chk

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

Fix: F-31919r1_fix

Change the mode of the traceroute command. # chmod 0700 /usr/contrib/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-35272r1_rule
RMF Control
AC-6
Severity
High
CCI
CCI-000225
Version
GEN004220
Vuln IDs
  • V-4382
Rule IDs
  • SV-35272r1_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-35103r2_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. # find `cat /etc/passwd | grep "^root" | cut -f 6,6 -d ":"` -type d -name \.mozilla -o -name .netscape If the find command returns any output for either browser directories, this is a finding. After the fact, it should be verified with the root users and the IAO what official business function(s) the browsers support and correct documentation.

Fix: F-30372r1_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-38436r1_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GEN004560
Vuln IDs
  • V-4384
Rule IDs
  • SV-38436r1_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-36570r1_chk

To 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-31938r1_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 as noted below: O SmtpGreetingMessage=$j Sendmail $v/$Z; $b change it to: O SmtpGreetingMessage= Mail Server Ready ; $b Then restart the Sendmail service.

b
The system must not use .forward files.
CM-6 - Medium - CCI-000366 - V-4385 - SV-35061r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN004580
Vuln IDs
  • V-4385
Rule IDs
  • SV-35061r1_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-36571r1_chk

Search for any .forward files (typically found in a user's home directory) on the system by: # find / -type f -name .forward This is considered a finding if any .forward files are found on the system.

Fix: F-31939r1_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-35106r1_rule
RMF Control
AC-6
Severity
High
CCI
CCI-000225
Version
GEN005000
Vuln IDs
  • V-4387
Rule IDs
  • SV-35106r1_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-36588r1_chk

Check the shell for the anonymous FTP account. # cat /etc/passwd | grep "^ftp" | cut -f 7,7 -d ":" | \ egrep -c -i "\/bin\/false|\/dev\/null|\/usr\/bin\/false|\/bin\/true|\/sbin\/nologin" This is a finding if the seventh field is empty (the entry ends with a colon[:]) 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-31956r1_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
The anonymous FTP account must be configured to use chroot or a similarly isolated environment.
CM-6 - Medium - CCI-000366 - V-4388 - SV-35108r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN005020
Vuln IDs
  • V-4388
Rule IDs
  • SV-35108r1_rule
If an anonymous FTP account does not use a chroot or similarly isolated environment, the system may be more vulnerable to exploits against the FTP service. Such exploits could allow an attacker to gain shell access to the system and view, edit, or remove sensitive files.System AdministratorECSC-1
Checks: C-36590r2_chk

Is FTP installed? # ls -lL /usr/lbin/ftpd If ftpd is not installed, this is not a finding. If ftpd is installed, determine if there is an anonymous ftp user configured in /etc/passwd. # cat /etc/passwd | egrep -c "^ftp|^anonymous" The /etc/passwd file, home directory entry for the anonymous FTP user should appear as the following example: ftp:4rL2xXxDatENY:509:159::/home/ftp/./:/usr/bin/false If there is an anonymous ftp user configured in /etc/passwd, determine if the ftp/anonymous user's home directory entry in the /etc/passwd file configured for chroot? # cat /etc/passwd | egrep "^ftp|^anonymous" | cut -f 6,6 -d ":" A dot (.) in field 6 of the FTP /etc/passwd file determines where the chroot will be performed. In the above example, the new root directory is /home/ftp. If an anonymous ftp user is found and the above command does not return an absolute path with a home directory of "dot" (see the above example), this is a finding.

Fix: F-31957r2_fix

Using the HP-SMH, configure the anonymous FTP service to operate in a chroot environment.

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-35181r1_rule
RMF Control
SC-32
Severity
Medium
CCI
CCI-001208
Version
GEN005380
Vuln IDs
  • V-4392
Rule IDs
  • SV-35181r1_rule
Installing extraneous software on a system designated as a dedicated 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-35026r1_chk

NOTE: This will virtually always require a manual review. 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-30318r1_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 bin.
AC-6 - Medium - CCI-000225 - V-4393 - SV-38437r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN005400
Vuln IDs
  • V-4393
Rule IDs
  • SV-38437r1_rule
If the /etc/syslog.conf file is not owned by bin, unauthorized users could be allowed to view, edit, or delete important system messages handled by the syslog facility.System AdministratorECLP-1
Checks: C-36621r1_chk

Check /etc/syslog.conf ownership. # ls -lL /etc/syslog.conf If either /etc/syslog.conf is not owned by bin, this is a finding.

Fix: F-31988r1_fix

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

b
The /etc/syslog.conf file must be group-owned by root, bin, sys, or system.
AC-6 - Medium - CCI-000225 - V-4394 - SV-35186r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN005420
Vuln IDs
  • V-4394
Rule IDs
  • SV-35186r1_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-35030r1_chk

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

Fix: F-30322r1_fix

Change the group owner of the /etc/syslog.conf file to root, bin, sys, or other. # chgrp root /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-35192r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN005460
Vuln IDs
  • V-4395
Rule IDs
  • SV-35192r1_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-35037r1_chk

Examine the syslog.conf file for any references to remote log hosts. # cat /etc/syslog.conf | tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' | grep -v '^#' | grep "\@" Destinations beginning with the @ symbol represent log hosts. If the log host name is a local alias such as loghost, 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-30328r1_fix

Remove 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-30080r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN005560
Vuln IDs
  • V-4397
Rule IDs
  • SV-30080r1_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-36669r1_chk

Check the system for an IPv4 default route. # netstat -r |grep default If a default route is not defined, this is a finding.

Fix: F-32042r1_fix

Edit /etc/rc.config.d/netconf and add configuration for a default route. For a default gateway of 192.168.3.1: ROUTE_DESTINATION[0]=default ROUTE_MASK[0]="" ROUTE_GATEWAY[0]=192.168.3.1 ROUTE_COUNT[0]=1 ROUTE_ARGS[0]="" Restart the system for the setting to take effect.

b
A system used for routing must not run other network services or applications.
SC-32 - Medium - CCI-001208 - V-4398 - SV-35156r1_rule
RMF Control
SC-32
Severity
Medium
CCI
CCI-001208
Version
GEN005580
Vuln IDs
  • V-4398
Rule IDs
  • SV-35156r1_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-35011r1_chk

Ask the SA if the system is a designated router. If it is not, this is not applicable. If this system is a designated router, check the system for non-routing network services. # 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-30306r1_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 Network Information System (NIS/NIS+).
AC-17 - High - CCI-001436 - V-4399 - SV-35147r1_rule
RMF Control
AC-17
Severity
High
CCI
CCI-001436
Version
GEN006380
Vuln IDs
  • V-4399
Rule IDs
  • SV-35147r1_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-36719r1_chk

If the system does not use NIS or NIS+, this is not applicable. Check if NIS or NIS+ is implemented using UDP. # rpcinfo -p | grep yp | grep udp If NIS or NIS+ is implemented using UDP, this is a finding.

Fix: F-30298r1_fix

Configure the system to not use UDP for NIS and NIS+. HP-UX specific documentation (note the major version of NIS+ currently running) should be consulted 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-38438r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN002020
Vuln IDs
  • V-4427
Rule IDs
  • SV-38438r1_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.System AdministratorECCD-1, ECCD-2
Checks: C-36375r1_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 anything other than host-user pairs, this is a finding.

Fix: F-32971r1_fix

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

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-34960r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN002060
Vuln IDs
  • V-4428
Rule IDs
  • SV-34960r1_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-38439r1_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-000225
Version
GEN003260
Vuln IDs
  • V-4430
Rule IDs
  • SV-38439r1_rule
Cron daemon control files restrict the scheduling of automated tasks and must be protected.System AdministratorECLP-1
Checks: C-36468r1_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-31810r1_fix

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

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

# cat /etc/inetd.conf | grep -v "^#" | grep -c remshd If the above command return value is greater than 0, this is a finding.

Fix: F-30282r1_fix

Edit /etc/inetd.conf and comment out the remshd service. Refresh the inetd service. # inetd -c

c
The rexec daemon must not be running.
AC-17 - High - CCI-001435 - V-4688 - SV-35132r2_rule
RMF Control
AC-17
Severity
High
CCI
CCI-001435
Version
GEN003840
Vuln IDs
  • V-4688
Rule IDs
  • SV-35132r2_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 AdministratorEBRP-1, ECSC-1
Checks: C-34990r3_chk

# cat /etc/inetd.conf | tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' |grep -v "^#" | \ cut -f 6,7 -d " " | grep -c -i rexecd If any results are returned, this is a finding.

Fix: F-30284r1_fix

Edit /etc/inetd.conf and comment out the line for the rexec daemon service. Restart the inetd service via the following command: # inetd -c

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

Determine the version of the SMTP service software. To obtain version information for the Sendmail daemon: # what /usr/sbin/sendmail OR # strings /usr/sbin/sendmail | grep -i version If the Sendmail version is not at least 8.14.4, or if it is not the vendor's latest version, this is a finding.

Fix: F-31940r1_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-35070r1_rule
RMF Control
CM-6
Severity
High
CCI
CCI-000366
Version
GEN004620
Vuln IDs
  • V-4690
Rule IDs
  • SV-35070r1_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-36573r1_chk

Check for an enabled debug command provided by the SMTP service. # telnet localhost 25 debug If the command does not return a 500 error code of command unrecognized, 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-35071r1_rule
RMF Control
SI-2
Severity
High
CCI
CCI-001230
Version
GEN004640
Vuln IDs
  • V-4691
Rule IDs
  • SV-35071r1_rule
A common configuration for older mail transfer agents (MTAs) is to include 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 the decode or the 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-36574r1_chk

Check the SMTP service for an active decode command. # telnet localhost 25 decode If the command does not return a 500 error code of command unrecognized, this is a finding.

Fix: F-31942r1_fix

Disable mail aliases for decode and uudecode. If the /etc/mail/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 these (commented) file entry examples: # 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-35076r1_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GEN004660
Vuln IDs
  • V-4692
Rule IDs
  • SV-35076r1_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 your log file for the response from the server.System AdministratorECSC-1
Checks: C-36575r1_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 (command unrecognized), this is a finding. OR Check the sendmail.cf configuration file by: # cat /etc/mail/sendmail.cf | tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' | grep -v "^#" |\ grep -i privacyoptions | egrep -c -i "noexpn|goaway" 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-31943r1_fix

Edit the /etc/mail/sendmail.cf file and add or edit the following line: O PrivacyOptions=goaway Then restart the Sendmail service.

a
The SMTP service must not have the VRFY feature active.
CM-6 - Low - CCI-000366 - V-4693 - SV-35083r1_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GEN004680
Vuln IDs
  • V-4693
Rule IDs
  • SV-35083r1_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-36576r1_chk

Determine if VRFY is disabled. # telnet localhost 25 vrfy root If the command does not return a 500 error code of command unrecognized, this is a finding. OR Check the sendmail.cf configuration file by: # cat /etc/mail/sendmail.cf | tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' | grep -v "^#" | \ grep -i privacyoptions | egrep -c -i "goaway|novrfy" 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-31944r1_fix

If running Sendmail, add the line Opnovrfy to the Sendmail configuration file, usually located in /etc/mail/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. Edit the /etc/mail/sendmail.cf file and add or edit (one of) the following line(s): O PrivacyOptions=novrfy O PrivacyOptions=goaway Then restart the Sendmail service.

a
The Sendmail service must not have the wizard backdoor active.
CM-6 - Low - CCI-000366 - V-4694 - SV-35093r1_rule
RMF Control
CM-6
Severity
Low
CCI
CCI-000366
Version
GEN004700
Vuln IDs
  • V-4694
Rule IDs
  • SV-35093r1_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-36577r1_chk

Check the /etc/mail/sendmail.cf configuration file for "wiz" configuration. # cat /etc/mail/sendmail.cf |tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' | grep -v "^#" |\ grep -i wiz If an entry is found for wiz, this is a finding.

Fix: F-31945r1_fix

If the WIZ command is enabled on Sendmail, it should be disabled by adding this line to the sendmail.cf configuration file (note that 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-38440r1_rule
RMF Control
AC-6
Severity
High
CCI
CCI-000225
Version
GEN005140
Vuln IDs
  • V-4695
Rule IDs
  • SV-38440r1_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-36597r1_chk

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

Fix: F-31963r1_fix

Disable the TFTP daemon. Edit /etc/inetd.conf and comment out the tftp line. Restart the inetd service via the command: # inetd -c

b
The system must not have the UUCP service active.
AC-17 - Medium - CCI-001436 - V-4696 - SV-35171r1_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-001436
Version
GEN005280
Vuln IDs
  • V-4696
Rule IDs
  • SV-35171r1_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-36605r1_chk

# cat /etc/inetd.conf | tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' | grep -v "^#" | grep -i uucp If uucp is found enabled, this is a finding.

Fix: F-31973r1_fix

Edit /etc/inetd.conf and comment the uucp service entry. Restart the inetd service. # inetd -c

c
X displays must not be exported to the world.
AC-6 - High - CCI-000225 - V-4697 - SV-35168r1_rule
RMF Control
AC-6
Severity
High
CCI
CCI-000225
Version
GEN005200
Vuln IDs
  • V-4697
Rule IDs
  • SV-35168r1_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-36601r1_chk

Windows is not used on the system, this is not applicable. Check the output of the "xhost" command from an X terminal. First, verify the DISPLAY variable is correctly set. $ echo $DISPLAY NOTE: It may be necessary to define the display if the command reports it cannot open the display. MachineName may be replaced with an Internet Protocol Address. Repeat the check procedure after setting the display. $ DISPLAY=MachineName:0.0; export DISPLAY $ 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.

Fix: F-31968r1_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.

a
The system must not have the finger service active.
AC-4 - Low - CCI-001551 - V-4701 - SV-35136r1_rule
RMF Control
AC-4
Severity
Low
CCI
CCI-001551
Version
GEN003860
Vuln IDs
  • V-4701
Rule IDs
  • SV-35136r1_rule
The finger service provides information about the system's users to network clients. This could expose information that could be used in subsequent attacks.System AdministratorEBRU-1, DCPP-1
Checks: C-34994r1_chk

# cat /etc/inetd.conf | tr '\011' ' ' | tr -s ' ' | sed -e 's/^[ \t]*//' |grep -v "^#" | \ cut -f 6,7 -d " " | grep -c -i fingerd If the fingerd service is not disabled, this is a finding.

Fix: F-30288r1_fix

Edit /etc/inetd.conf and comment out the fingerd line. Restart the inetd service via the following command: # inetd -c

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-35101r1_rule
RMF Control
IA-4
Severity
Medium
CCI
CCI-000787
Version
GEN004840
Vuln IDs
  • V-4702
Rule IDs
  • SV-35101r1_rule
Anonymous FTP is a public data service which is only permitted in a server capacity when located on the DMZ network.Information Assurance OfficerSystem AdministratorEBBD-1, EBBD-3, ECSC-1, EBBD-2
Checks: C-36581r1_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. # ftp localhost OR # ftp `hostname` 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-31949r1_fix

Move the system to a DMZ network.

b
A file integrity baseline including cryptographic hashes must be created and maintained.
CM-2 - Medium - CCI-000293 - V-11941 - SV-38271r1_rule
RMF Control
CM-2
Severity
Medium
CCI
CCI-000293
Version
GEN000140
Vuln IDs
  • V-11941
Rule IDs
  • SV-38271r1_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-36231r2_chk

This will always be a manual review. Determine if a file integrity baseline, which includes cryptographic hashes, has been created and maintained for the system. While HPUX-HIDS has the ability to detect file system changes, it does not currently support the creation of a system baseline. A number of third-party vendors (TripWire, for example) may be used for this purpose. Additionally, local scripts may also be used to create and maintain the system baseline, though this would not be the preferred method. Ask the SA if a file system baseline has been created and is being maintained on an ongoing basis. 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 (i.e., the baseline has not been updated to be consistent with the latest approved system configuration changes), this is a finding.

Fix: F-31490r1_fix

Create a file integrity baseline, including cryptographic hashes, for the system. # find / -depth -print | tee HP11-v3_Baseline Open the above file and either manually execute md5sum or the chksum command on each file. Alternatively, write a script to perform the above. NOTE: For security purposes, md5sum is preferred over chksum.

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-28610r2_rule
RMF Control
RA-5
Severity
Medium
CCI
CCI-001069
Version
GEN000220
Vuln IDs
  • V-11945
Rule IDs
  • SV-28610r2_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: The frequency may be increased to daily, if necessary, in accordance with the contingency plan.System AdministratorDCSL-1
Checks: C-28849r3_chk

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

Fix: F-25883r3_fix

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

b
UIDs reserved for system accounts must not be assigned to non-system accounts.
CM-6 - Medium - CCI-000366 - V-11946 - SV-35265r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN000340
Vuln IDs
  • V-11946
Rule IDs
  • SV-35265r1_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-29002r1_chk

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

Fix: F-26001r1_fix

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

b
The system must require that passwords contain a minimum of 15 characters.
IA-5 - Medium - CCI-000205 - V-11947 - SV-27111r4_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000205
Version
GEN000580
Vuln IDs
  • V-11947
Rule IDs
  • SV-27111r4_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-28027r5_chk

For Trusted Mode: Check the system password length setting. For Trusted systems, the range of supported values for N is 6 to 80. # grep MIN_PASSWORD_LENGTH /etc/default/security If the MIN_PASSWORD_LENGTH attribute (N) is not set to 15 or greater, this is a finding. For SMSE: Check the system password length setting. For Standard (non-SMSE enabled) systems, the maximum supported length is N=8. Once the /etc/shadow file is created and long passwords are enabled (may require additional software product installations), check the system password length setting. The LONG_PASSWORD attribute is valid only when the LongPassword11i3 product is installed and the password hash algorithm is different from the traditional DES-based hash algorithm. # egrep "CRYPT_ALGORITHMS_DEPRECATE|CRYPT_DEFAULT|LONG_PASSWORD|MIN_PASSWORD_LENGTH" /etc/default/security /var/adm/userdb/* The following is an example output from the above command: CRYPT_ALGORITHMS_DEPRECATE=__unix__ CRYPT_DEFAULT=6 LONG_PASSWORD=1 MIN_PASSWORD_LENGTH=15 Note: The MIN_PASSWORD_LENGTH attribute may exceed 15 characters. If the attributes CRYPT_ALGORITHMS_DEPRECATE, CRYPT_DEFAULT, LONG_PASSWORD, and MIN_PASSWORD_LENGTH are not set per the above example output, this is a finding.

Fix: F-24374r5_fix

For Trusted Mode: Use the SAM/SMH interface to set the system password length attribute “MIN_PASSWORD_LENGTH” to 15 or greater. For SMSE: Note: There may be additional package/bundle updates that must be installed to support attributes in the /etc/default/security file. Install the additional LongPassword11i3 and PHI11i3 product bundles where/as required. Use the SAM/SMH interface (/etc/default/security file) and/or the userdbset command (/var/adm/userdb/* files) to update the attribute(s). See the below example(s): CRYPT_ALGORITHMS_DEPRECATE=__unix__ CRYPT_DEFAULT=6 LONG_PASSWORD=1 MIN_PASSWORD_LENGTH=15 Note: The MIN_PASSWORD_LENGTH attribute must be set equal to or greater than 15. If the "vi" editor was used to update the /etc/default/security file, save the file before exiting the editor.

b
The system must require passwords contain at least one uppercase alphabetic character.
IA-5 - Medium - CCI-000192 - V-11948 - SV-38244r2_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000192
Version
GEN000600
Vuln IDs
  • V-11948
Rule IDs
  • SV-38244r2_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-36284r2_chk

For Trusted Mode: Check the PASSWORD_MIN_UPPER_CASE_CHARS setting. # cat /etc/default/security | grep PASSWORD_MIN_UPPER_CASE_CHARS If PASSWORD_MIN_UPPER_CASE_CHARS is not set to 1 or greater, this is a finding. For SMSE: Check the PASSWORD_MIN_UPPER_CASE_CHARS setting. # grep PASSWORD_MIN_UPPER_CASE_CHARS /etc/default/security /var/adm/userdb/* If PASSWORD_MIN_UPPER_CASE_CHARS is not set to 1 or more, this is a finding.

Fix: F-31541r2_fix

For Trusted Mode: Use the SAM/SMH interface or edit the /etc/default/security file and update the PASSWORD_MIN_UPPER_CASE_CHARS attribute. See the below example: PASSWORD_MIN_UPPER_CASE_CHARS=1 If manually editing the file, save any change(s) before exiting the editor. For SMSE: Note: There may be additional package/bundle updates that must be installed to support attributes in the /etc/default/security file. Use the SAM/SMH interface (/etc/default/security file) and/or the userdbset command (/var/adm/userdb/* files) to update the PASSWORD_MIN_UPPER_CASE_CHARS attribute. See the below example: PASSWORD_MIN_UPPER_CASE_CHARS=1 Note: Never use a text editor to modify any /var/adm/userdb database file. The database contains checksums and other binary data, and editors (vi included) do not follow the file locking conventions that are used to control access to the database. If manually editing the /etc/default/security file, save any change(s) before exiting the editor.

b
The system must require passwords contain at least one numeric character.
IA-5 - Medium - CCI-000194 - V-11972 - SV-38245r2_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000194
Version
GEN000620
Vuln IDs
  • V-11972
Rule IDs
  • SV-38245r2_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-36285r2_chk

For Trusted Mode: Check the PASSWORD_MIN_DIGIT_CHARS setting. # cat /etc/default/security | grep PASSWORD_MIN_DIGIT_CHARS If PASSWORD_MIN_DIGIT_CHARS is not set to 1 or greater this is a finding. For SMSE: Check the PASSWORD_MIN_DIGIT_CHARS setting. # grep PASSWORD_MIN_DIGIT_CHARS /etc/default/security /var/adm/userdb/* If PASSWORD_MIN_DIGIT_CHARS is not set to 1 or greater, this is a finding.

Fix: F-31542r2_fix

For Trusted Mode: Use the SAM/SMH interface or edit the /etc/default/security file and update the PASSWORD_MIN_DIGIT_CHARS attribute. See the below example: PASSWORD_MIN_DIGIT_CHARS=1 If manually editing the file, save any change(s) before exiting the editor. For SMSE: Note: There may be additional package/bundle updates that must be installed to support attributes in the /etc/default/security file. Use the SAM/SMH interface (/etc/default/security file) and/or the userdbset command (/var/adm/userdb/* files) to update the PASSWORD_MIN_DIGIT_CHARS attribute. See the below example: PASSWORD_MIN_DIGIT_CHARS=1 Note: Never use a text editor to modify any /var/adm/userdb database file. The database contains checksums and other binary data, and editors (vi included) do not follow the file locking conventions that are used to control access to the database. If manually editing the /etc/default/security file, save any change(s) before exiting the editor.

b
The system must require passwords contain at least one special character.
IA-5 - Medium - CCI-001619 - V-11973 - SV-38246r2_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-001619
Version
GEN000640
Vuln IDs
  • V-11973
Rule IDs
  • SV-38246r2_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-36286r2_chk

For Trusted Mode: Check the PASSWORD_MIN_SPECIAL_CHARS setting. # cat /etc/default/security | grep PASSWORD_MIN_SPECIAL_CHARS If PASSWORD_MIN_SPECIAL_CHARS is not set to 1 or greater this is a finding. For SMSE: Check the PASSWORD_MIN_SPECIAL_CHARS setting. # grep PASSWORD_MIN_SPECIAL_CHARS /etc/default/security /var/adm/userdb/* If PASSWORD_MIN_SPECIAL_CHARS is not set to 1 or greater, this is a finding.

Fix: F-31543r2_fix

For Trusted Mode: Use the SAM/SMH interface or edit the /etc/default/security file and update the PASSWORD_MIN_SPECIAL_CHARS attribute. See the below example: PASSWORD_MIN_SPECIAL_CHARS=1 If manually editing the file, save any change(s) before exiting the editor. For SMSE: Note: There may be additional package/bundle updates that must be installed to support attributes in the /etc/default/security file. Use the SAM/SMH interface (/etc/default/security file) and/or the userdbset command (/var/adm/userdb/* files) to update the PASSWORD_MIN_SPECIAL_CHARS attribute. See the below example: PASSWORD_MIN_SPECIAL_CHARS=1 Note: Never use a text editor to modify any /var/adm/userdb database file. The database contains checksums and other binary data, and editors (vi included) do not follow the file locking conventions that are used to control access to the database. If manually editing the /etc/default/security file, save any change(s) before exiting the editor.

b
The system must require passwords contain no more than three consecutive repeating characters.
CM-6 - Medium - CCI-000366 - V-11975 - SV-38210r1_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
GEN000680
Vuln IDs
  • V-11975
Rule IDs
  • SV-38210r1_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-36287r1_chk

HP-UX does not currently support enforcement of non-repeating characters; this is always considered a finding.

Fix: F-31544r1_fix

Configure/modify the system policy to require passwords not