| V-226929 | High | Administrative accounts must not run a web browser, except as needed for local service administration. | 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... |
| V-226456 | High | The system must not have accounts configured with blank or null passwords. | 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... |
| V-226563 | High | There must be no .rhosts, .shosts, hosts.equiv, or shosts.equiv files on the system. | The .rhosts, .shosts, hosts.equiv, and shosts.equiv files are used to configure host-based authentication for individual users or the system. Host-based authentication is not sufficient for... |
| V-220039 | High | The rsh daemon must not be running. | The rshd process provides a typically unencrypted, host-authenticated remote access service. SSH should be used in place of this service.
Satisfies: SRG-OS-000033, SRG-OS-000505, SRG-OS-000555 |
| V-226482 | High | Root passwords must never be passed over a network in clear text form. | 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... |
| V-226960 | High | Any active TFTP daemon must be authorized and approved in the system accreditation package. | 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... |
| V-226964 | High | X displays must not be exported to the world. | 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. |
| V-227041 | High | The system must not use UDP for NIS/NIS+. | 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. |
| V-220069 | High | The system must not use removable media as the boot loader. | Malicious users with removable boot media can gain access to a system configured to use removable media as the boot loader. |
| V-226933 | High | Files executed through a mail aliases file must be owned by root and must reside within a directory owned and writable only by root. | 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... |
| V-226921 | High | The telnet daemon must not be running. | The telnet daemon provides a typically unencrypted remote access service which does not provide for the confidentiality and integrity of user passwords or the remote session. If a privileged user... |
| V-220050 | High | The Sendmail server must have the debug feature disabled. | 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. |
| V-220051 | High | The SMTP service must not have a uudecode alias active. | A common configuration for older Mail Transfer Agents (MTAs) includes an alias for the decode user. All mail sent to this user is sent to the uudecode program, which automatically converts and... |
| V-220055 | High | The SSH daemon must be configured to only use the SSHv2 protocol. | 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. |
| V-226430 | High | The operating system must be a supported release. | An operating system release is considered supported if the vendor continues to provide security patches for the product. With an unsupported release, it will not be possible to resolve security... |
| V-226570 | High | All shell files must have mode 0755 or less permissive. | Shells with world/group-write permissions give the ability to maliciously modify the shell to obtain unauthorized access. |
| V-226541 | High | Run control scripts must not execute world-writable programs or scripts.
| World-writable files could be modified accidentally or maliciously to compromise system integrity. |
| V-220049 | High | The SMTP service must be an up-to-date version. | The SMTP service version on the system must be current to avoid exposing vulnerabilities present in unpatched versions. |
| V-226919 | High | The rexec daemon must not be running. | The rexecd process provides a typically unencrypted, host-authenticated remote access service. SSH should be used in place of this service. |
| V-226969 | High | SNMP communities, users, and passphrases must be changed from the default. | 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... |
| V-226959 | High | The TFTP daemon must have mode 0755 or less permissive. | 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. |
| V-226958 | High | The TFTP daemon must operate in secure mode which provides access only to a single directory on the host file system. | 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,... |
| V-226955 | High | Anonymous FTP accounts must not have a functional shell. | 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. |
| V-226422 | High | The root account must be the only account with GID of 0. | Accounts with a GID of 0 have root group privileges. |
| V-227075 | High | If the system boots from removable media, it must be stored in a safe or similarly secured container. | 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. |
| V-227073 | High | The system must be configured to only boot from the system boot device. | 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... |
| V-226926 | Medium | The traceroute command must be group-owned by sys, bin, or root. | 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... |
| V-226927 | Medium | The traceroute file must have mode 0700 or less permissive. | 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... |
| V-226924 | Medium | The hosts.lpd (or equivalent) file must not have an extended ACL. | 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... |
| V-226925 | Medium | The traceroute command owner must be root. | 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... |
| V-226923 | Medium | The hosts.lpd file (or equivalent) must not contain a "+" character. | Having the "+" character in the hosts.lpd (or equivalent) file allows all hosts to use local system print resources. |
| V-226519 | Medium | The /etc/group file must be group-owned by root, bin, or sys. | The /etc/group file is critical to system security and must be protected from unauthorized modification. The group file contains a list of system groups and associated information. |
| V-226518 | Medium | The /etc/group file must be owned by root. | The /etc/group file is critical to system security and must be owned by a privileged user. The group file contains a list of system groups and associated information. |
| V-226517 | Medium | The /etc/passwd file must not have an extended ACL. | File system ACLs can provide access to files beyond what is allowed by the mode numbers of the files. The /etc/passwd file contains the list of local system accounts. It is vital to system... |
| V-226516 | Medium | The /etc/passwd file must have mode 0644 or less permissive. | If the password file is writable by a group owner or the world, the risk of password file compromise is increased. The password file contains the list of accounts on the system and associated information. |
| V-226515 | Medium | The /etc/passwd file must be group-owned by root, bin, or sys. | The /etc/passwd file contains the list of local system accounts. It is vital to system security and must be protected from unauthorized modification. |
| V-226514 | Medium | The /etc/passwd file must be owned by root. | The /etc/passwd file contains the list of local system accounts. It is vital to system security and must be protected from unauthorized modification. |
| V-226513 | Medium | The /etc/nsswitch.conf file must not have an extended ACL. | The nsswitch.conf file (or equivalent) configures the source of a variety of system security information including account, group, and host lookups. Malicious changes could prevent the system... |
| V-226512 | Medium | The /etc/nsswitch.conf file must have mode 0644 or less permissive. | The nsswitch.conf file (or equivalent) configures the source of a variety of system security information including account, group, and host lookups. Malicious changes could prevent the system... |
| V-226511 | Medium | The /etc/nsswitch.conf file must be group-owned by root, bin, or sys. | The nsswitch.conf file (or equivalent) configures the source of a variety of system security information including account, group, and host lookups. Malicious changes could prevent the system... |
| V-226457 | Medium | The system must require passwords contain a minimum of 15 characters. | 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. |
| V-226454 | Medium | The root user must not own the logon session for an application requiring a continuous display. | 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. |
| V-226455 | Medium | Users must not be able to change passwords more than once every 24 hours. | 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... |
| V-226450 | Medium | The FTPS/FTP service on the system must be configured with the Department of Defense (DoD) login banner. | Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources.
NOTE: SFTP and FTPS are encrypted alternatives... |
| V-226451 | Medium | Successful and unsuccessful logins and logouts must be logged. | Monitoring and recording successful and unsuccessful logins assist in tracking unauthorized access to the system. Without this logging, the ability to track unauthorized activity to specific user... |
| V-226458 | Medium | The system must enforce compliance of the entire password during authentication. | Some common password hashing schemes only process the first eight characters of a user's password, which reduces the effective strength of the password. |
| V-226459 | Medium | The system must use a FIPS 140-2 approved cryptographic hashing algorithm for generating account password hashes. | Systems must employ cryptographic hashes for passwords using the SHA-2 family of algorithms or FIPS 140-2 approved successors. The use of unapproved algorithms may result in weak password hashes... |
| V-226632 | Medium | The cron.allow file must be owned by root, bin, or sys. | 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. |
| V-226633 | Medium | The at.allow file must not have an extended ACL. | File system extended ACLs provide access to files beyond what is allowed by the mode numbers of the files. Unauthorized modification of the at.allow file could result in Denial of Service to... |
| V-226630 | Medium | The cron.deny file must not have an extended ACL. | If file permissions for cron.deny are more permissive than 0700, sensitive information could be viewed or edited by unauthorized users. |
| V-226634 | Medium | The cron.allow file must be group-owned by root, bin, or sys. | If the group of the cron.allow is not set to root, bin, or sys, the possibility exists for an unauthorized user to view or edit the list of users permitted to use cron. Unauthorized modification... |
| V-226635 | Medium | The at.deny file must have mode 0600 or less permissive. | The at daemon control files restrict access to scheduled job manipulation and must be protected. Unauthorized modification of the at.deny file could result in Denial of Service to authorized at... |
| V-226562 | Medium | All .rhosts, .shosts, or host.equiv files must only contain trusted host-user pairs. | If these files are not properly configured, they could allow malicious access by unknown malicious users from untrusted hosts who could compromise the system. |
| V-220038 | Medium | The portmap or rpcbind service must not be running unless needed. | The portmap and rpcbind services increase the attack surface of the system and should only be used when needed. The portmap or rpcbind services are used by a variety of services using remote... |
| V-226920 | Medium | The rexecd service must not be installed. | The rexecd process provides a typically unencrypted, host-authenticated remote access service. SSH should be used in place of this service. |
| V-226579 | Medium | The owner, group owner, mode, ACL, and location of files with the setuid bit set must be documented using site-defined procedures. | 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,... |
| V-220032 | Medium | All global initialization files must be owned by root. | Global initialization files are used to configure the user's shell environment upon login. Malicious modification of these files could compromise accounts upon logon. Failure to give ownership... |
| V-220033 | Medium | All global initialization files must be group-owned by root, sys, or bin. | Global initialization files are used to configure the user's shell environment upon login. Malicious modification of these files could compromise accounts upon logon. Failure to give ownership... |
| V-220030 | Medium | All interactive user's home directories must be group-owned by the home directory owner's primary group. | If the GID of the home directory is not the same as the GID of the user, this would allow unauthorized access to files. |
| V-220031 | Medium | All global initialization files must have mode 0644 or less permissive. | Global initialization files are used to configure the user's shell environment upon login. Malicious modification of these files could compromise accounts upon logon. |
| V-220036 | Medium | Removable media, remote file systems, and any file system that does not contain approved setuid files must be mounted with the "nosuid" option. | The "nosuid" mount option causes the system to not execute setuid files with owner privileges. This option must be used for mounting any file system that does not contain approved setuid files. ... |
| V-220037 | Medium | The system must not be configured for network bridging. | Some systems have the ability to bridge or switch frames (link-layer forwarding) between multiple interfaces. This can be useful in a variety of situations but, if enabled when not needed, has the... |
| V-220035 | Medium | Local initialization files must be group-owned by the user's primary group or root. | Local initialization files are used to configure the user's shell environment upon login. Malicious modification of these files could compromise accounts upon logon. |
| V-226483 | Medium | The system must not permit root logins using remote access programs such as SSH.
| 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... |
| V-226962 | Medium | All .Xauthority files must have mode 0600 or less permissive. | .Xauthority files ensure the user is authorized to access the specific X Windows host. Excessive permissions may permit unauthorized modification of these files, which could lead to Denial of... |
| V-226963 | Medium | The .Xauthority files must not have extended ACLs. | .Xauthority files ensure the user is authorized to access the specific X Windows host. Extended ACLs may permit unauthorized modification of these files, which could lead to Denial of Service to... |
| V-226961 | Medium | Any X Windows host must write .Xauthority files. | .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. |
| V-226966 | Medium | The .Xauthority utility must only permit access to authorized hosts. | If unauthorized clients are permitted access to the X server, a user's X session may be compromised. |
| V-226928 | Medium | The traceroute file must not have an extended ACL. | If an extended ACL exists on the traceroute executable file, it may provide unauthorized users with access to the file. Malicious code could be inserted by an attacker and triggered whenever the... |
| V-226965 | Medium | .Xauthority or X*.hosts (or equivalent) file(s) must be used to restrict access to the X server. | If access to the X server is not restricted, a user's X session may be compromised. |
| V-226968 | Medium | The system must not have the UUCP service active. | The UUCP utility is designed to assist in transferring files, executing remote commands, and sending email between UNIX systems over phone lines and direct connections between systems. The UUCP... |
| V-226510 | Medium | The /etc/nsswitch.conf file must be owned by root. | The nsswitch.conf file (or equivalent) configures the source of a variety of system security information including account, group, and host lookups. Malicious changes could prevent the system... |
| V-226412 | Medium | If the system is a firewall, ASET must be used on the system, and the firewall parameters must be set in /usr/aset/asetenv. | ASET will not perform firewall tasks if it is not listed as a parameter in /usr/aset/asetenv. |
| V-226413 | Medium | The Solaris system Automated Security Enhancement Tool (ASET) configurable parameters in the asetenv file must be correct. | If settings in the asetenv file have been modified, then system vulnerabilities may not be detected. |
| V-226410 | Medium | The /etc/security/audit_user file must not have an extended ACL. | Audit_user is a sensitive file that, if compromised, would allow a malicious user to select auditing parameters to ignore their sessions. This would allow malicious operations the auditing... |
| V-226411 | Medium | The /usr/aset/masters/uid_aliases must be empty. | If uid_aliases has entries, users may not be properly identified in ASET records. |
| V-226416 | Medium | The /usr/aset/userlist file must be group-owned by root. | The /usr/aset/userlist file is critical to system security and must be protected from unauthorized access. |
| V-226417 | Medium | The /usr/aset/userlist file must have mode 0600 or less permissive. | A permission mask not set to the required level could allow unauthorized access to sensitive system files and resources. |
| V-226414 | Medium | The /usr/aset/userlist file must exist. | If the userlist file does not exist, then an unauthorized user may exist in the /etc/passwd file. |
| V-226415 | Medium | The /usr/aset/userlist file must be owned by root. | If the userlist file is not owned by root, then an unauthorized user can modify the file and enter an unauthorized user. |
| V-226425 | Medium | The /etc/zones directory, and its contents, must not be group- or world-writable. | Solaris zones configuration files must be protected against illicit creation, modification, and deletion. |
| V-226418 | Medium | The /usr/aset/userlist file must not have an extended ACL. | File system ACLs can provide access to files beyond what is allowed by the mode numbers of the files. |
| V-226419 | Medium | The Solaris system EEPROM security-mode parameter must be set to full or command mode. | If the EEPROM security-mode parameter is not set to full or command, then unauthorized access to system EEPROM can take place. In normal situations, when the system is in a controlled access area... |
| V-226950 | Medium | The ftpusers file must be owned by root. | If the file ftpusers is not owned by root, an unauthorized user may modify the file to allow unauthorized accounts to use FTP. |
| V-226429 | Medium | The physical devices must not be assigned to non-global zones. | Solaris non-global zones can be assigned physical hardware devices. This increases the risk of such a non-global zone having the capability to compromise the global zone. |
| V-226428 | Medium | The limitpriv zone option must be set to the vendor default or less permissive. | Solaris zones can be assigned privileges generally reserved for the global zone using the limitpriv zone option. Any privilege assignments in excess of the vendor defaults may provide the ability... |
| V-226566 | Medium | The /etc/shells (or equivalent) file must exist. | 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... |
| V-226567 | Medium | All shells referenced in /etc/passwd must be listed in the /etc/shells file, except any shells specified for the purpose of preventing logins. | 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... |
| V-226564 | Medium | All .rhosts, .shosts, .netrc, or hosts.equiv files must be accessible by only root or the owner. | 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. |
| V-226565 | Medium | The .rhosts file must not be supported in PAM. | The .rhosts files are used to specify a list of hosts that are permitted remote access to a particular account without authenticating. The use of such a mechanism defeats strong identification... |
| V-226489 | Medium | All system command files must have mode 755 or less permissive. | 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... |
| V-226488 | Medium | All network services daemon files must not have extended ACLs. | Restricting permission on daemons will protect them from unauthorized modification and possible system compromise. |
| V-226560 | Medium | The .rhosts, .shosts, hosts.equiv, shosts.equiv, /etc/passwd, /etc/shadow, and/or /etc/group files must not contain a plus (+) without defining entries for NIS+ netgroups. | A plus (+) in system accounts' files causes the system to lookup the specified entry using NIS. If the system is not using NIS, no such entries should exist. |
| V-226561 | Medium | There must be no .netrc files on the system.
| Unencrypted passwords for remote FTP servers may be stored in .netrc files. Policy requires passwords be encrypted in storage and not used in access scripts. |
| V-226485 | Medium | All files and directories must have a valid owner. | Unowned files and directories may be unintentionally inherited if a user is assigned the same UID as the UID of the unowned files. |
| V-226484 | Medium | System files and directories must not have uneven access permissions. | Discretionary access control is undermined if users, other than a file owner, have greater access permissions to system files and directories than the owner. |
| V-226487 | Medium | All network services daemon files must have mode 0755 or less permissive. | Restricting permission on daemons will protect them from unauthorized modification and possible system compromise. |
| V-226486 | Medium | All files and directories must have a valid group-owner. | Files without a valid group-owner may be unintentionally inherited if a group is assigned the same GID as the GID of the files without a valid group-owner. |
| V-226480 | Medium | The system must log successful and unsuccessful access to the root account. | If successful and unsuccessful logins and logouts are not monitored or recorded, access attempts cannot be tracked. Without this logging, it may be impossible to track unauthorized access to the system. |
| V-226568 | Medium | All shell files must be owned by root or bin. | 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. |
| V-226569 | Medium | All shell files must be group-owned by root, bin, or sys. | If shell files are group-owned by users other than root or a system group, they could be modified by intruders or malicious users to perform unauthorized actions. |
| V-226424 | Medium | The /etc/zones directory, and its contents, must be group-owned by root, sys, or bin. | Solaris zones configuration files must be protected against illicit creation, modification, and deletion. |
| V-226867 | Medium | The "at" directory must not have an extended ACL. | If the "at" directory has an extended ACL, unauthorized users could be allowed to view or to edit files containing sensitive information within the "at" directory. Unauthorized modifications... |
| V-226866 | Medium | The "at" directory must have mode 0755 or less permissive. | 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... |
| V-226865 | Medium | The "at" daemon must not execute programs in, or subordinate to, world-writable directories. | 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. |
| V-226864 | Medium | The "at" daemon must not execute group-writable or world-writable programs. | If the "at" facility executes world-writable or group-writable programs, it is possible for the programs to be accidentally or maliciously changed or replaced without the owner's intent or... |
| V-226863 | Medium | The at.allow file must have mode 0600 or less permissive. | Permissions more permissive than 0600 (read and write for the owner) may allow unauthorized or malicious access to the at.allow and/or at.deny files. |
| V-226862 | Medium | 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. | 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. |
| V-226988 | Medium | The SSH daemon must be configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms. | DoD information systems are required to use FIPS 140-2 approved cryptographic hash functions.
Satisfies: SRG-OS-000250, SRG-OS-000495, SRG-OS-000500 |
| V-226989 | Medium | The SSH client must be configured to only use FIPS 140-2 approved ciphers. | DoD information systems are required to use FIPS 140-2 approved ciphers. SSHv2 ciphers meeting this requirement are 3DES and AES.
Satisfies: SRG-OS-000033, SRG-OS-000505, SRG-OS-000555 |
| V-226861 | Medium | The at.deny file must not be empty if it exists. | 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... |
| V-226980 | Medium | The /etc/syslog.conf file must be owned by root. | If the /etc/syslog.conf file is not owned by root, unauthorized users could be allowed to view, edit, or delete important system messages handled by the syslog facility. |
| V-226981 | Medium | The /etc/syslog.conf file must be group-owned by root, bin, or sys. | 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. |
| V-226982 | Medium | The system must use a remote syslog server (log host). | A syslog server (log host) receives syslog messages from one or more systems. This data can be used as an authoritative log source in the event a system is compromised and its local logs are suspect. |
| V-226983 | Medium | The system must only use remote syslog servers (log hosts) justified and documented using site-defined procedures. | 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... |
| V-226984 | Medium | The SSH client must be configured to only use the SSHv2 protocol. | SSHv1 is not a DoD-approved protocol and has many well-known vulnerability exploits. Exploits of the SSH client could provide access to the system with the privileges of the user running the client. |
| V-226985 | Medium | The SSH daemon must only listen on management network addresses unless authorized for uses other than management. | The SSH daemon should only listen on network addresses designated for management traffic. If the system has multiple network interfaces and SSH listens on addresses not designated for management... |
| V-226986 | Medium | The SSH daemon must be configured to only use FIPS 140-2 approved ciphers. | DoD information systems are required to use FIPS 140-2 approved ciphers. SSHv2 ciphers meeting this requirement are 3DES and AES.
Satisfies: SRG-OS-000033, SRG-OS-000505, SRG-OS-000555 |
| V-226987 | Medium | The SSH daemon must be configured to not use Cipher-Block Chaining (CBC) ciphers. | The Cipher-Block Chaining (CBC) mode of encryption as implemented in the SSHv2 protocol is vulnerable to chosen plain text attacks and must not be used. |
| V-227042 | Medium | The Network Information System (NIS) protocol must not be used. | Due to numerous security vulnerabilities existing within NIS, it must not be used. Possible alternative directory services are NIS+ and LDAP. |
| V-227043 | Medium | NIS maps must be protected through hard-to-guess domain names. | The use of hard-to-guess NIS domain names provides additional protection from unauthorized access to the NIS directory information. |
| V-227040 | Medium | The files in /etc/news must be group-owned by root. | If critical system files do not have a privileged group owner, system integrity could be compromised. |
| V-227044 | Medium | Any NIS+ server must be operating at security level 2. | 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. |
| V-227048 | Medium | The system's access control program must log each system access attempt. | If access attempts are not logged, then multiple attempts to log on to the system by an unauthorized user may go undetected. |
| V-227049 | Medium | The system must use a virus scan program. | Virus scanning software can be used to protect a system from penetration by computer viruses and to limit their spread through intermediate systems. |
| V-226956 | Medium | The anonymous FTP account must be configured to use chroot or a similarly isolated environment. | 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... |
| V-220061 | Medium | The system must have a host-based intrusion detection tool installed. | 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... |
| V-220060 | Medium | The Samba Web Administration Tool (SWAT) must be restricted to the local host or require SSL. | 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... |
| V-220063 | Medium | The system package management tool must be used to verify system software periodically. | Verification using the system package management tool can be used to determine that system software has not been tampered with.
This requirement is not applicable to systems not using package... |
| V-220062 | Medium | The system vulnerability assessment tool, host-based intrusion detection tool, and file integrity tool must notify the SA and the IAO of a security breach or a suspected security breach. | Timely notifications of potential security compromises minimize the potential damage.
Minimally, the system must log these events and the SA and the IAO will receive the notifications during the... |
| V-220065 | Medium | The system's access control program must be configured to grant or deny system access to specific hosts. | If the system's access control program is not configured with appropriate rules for allowing and denying access to system network resources, services may be accessible to unauthorized hosts. |
| V-220064 | Medium | The system must use an access control program. | Access control programs (such as TCP_WRAPPERS) provide the ability to enhance system security posture. |
| V-220067 | Medium | The system must use an appropriate reverse-path filter for IPv6 network traffic, if the system uses IPv6. | Reverse-path filtering provides protection against spoofed source addresses by causing the system to discard packets with source addresses for which the system has no route or if the route does... |
| V-220066 | Medium | Wireless network adapters must be disabled. | The use of wireless networking can introduce many different attack vectors into the organization's network. Common attack vectors such as malicious association and ad hoc networks will allow an... |
| V-220068 | Medium | If the system is using LDAP for authentication or account information, the LDAP TLS certificate authority file and/or directory (as appropriate) must not have an extended ACL. | LDAP can be used to provide user authentication and account information, which are vital to system security. The LDAP client configuration must be protected from unauthorized modification. |
| V-226939 | Medium | The SMTP service log file must have mode 0644 or less permissive. | If the SMTP service log file is more permissive than 0644, unauthorized users may be allowed to change the log file. |
| V-226938 | Medium | The SMTP service log file must be owned by root. | 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. |
| V-226931 | Medium | The alias file must have mode 0644 or less permissive. | Excessive permissions on the aliases file may permit unauthorized modification. If the alias file is modified by an unauthorized user, they may modify the file to run malicious code or redirect email. |
| V-226930 | Medium | The alias file must be owned by root. | If the alias file is not owned by root, an unauthorized user may modify the file to add aliases to run malicious code or redirect email. |
| V-226932 | Medium | The alias file must not have an extended ACL. | Excessive permissions on the aliases file may permit unauthorized modification. If the alias file is modified by an unauthorized user, they may modify the file to run malicious code or redirect email. |
| V-226935 | Medium | Files executed through a mail aliases file must not have extended ACLs. | Excessive permissions on files executed through a mail alias file could result in modification by an unauthorized user, execution of malicious code, and/or system compromise. |
| V-226934 | Medium | Files executed through a mail aliases file must be group-owned by root, bin, or sys, and must reside within a directory group-owned by root, bin, or sys. | If a file executed through a mail aliases file is not group-owned by root or a system group, it may be subject to unauthorized modification. Unauthorized modification of files executed through... |
| V-226937 | Medium | The system syslog service must log informational and more severe SMTP service messages. | If informational and more severe SMTP service messages are not logged, malicious activity on the system may go unnoticed. |
| V-226522 | Medium | The /etc/shadow (or equivalent) file must be owned by root. | 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... |
| V-226523 | Medium | The /etc/shadow file (or equivalent) must be group-owned by root, bin, or sys. | 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... |
| V-226520 | Medium | The /etc/group file must have mode 0644 or less permissive. | The /etc/group file is critical to system security and must be protected from unauthorized modification. The group file contains a list of system groups and associated information. |
| V-226521 | Medium | The /etc/group file must not have an extended ACL. | The /etc/group file is critical to system security and must be protected from unauthorized modification. The group file contains a list of system groups and associated information. |
| V-226524 | Medium | The /etc/shadow (or equivalent) file must have mode 0400. | 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... |
| V-226525 | Medium | The /etc/shadow file must not have an extended ACL.
| 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... |
| V-226441 | Medium | The time synchronization configuration file (such as /etc/ntp.conf) must not have an extended ACL. | A synchronized system clock is critical for the enforcement of time-based policies and the correlation of logs and audit records with other systems. If an illicit time source is used for... |
| V-226440 | Medium | The time synchronization configuration file (such as /etc/ntp.conf) must have mode 0640 or less permissive. | A synchronized system clock is critical for the enforcement of time-based policies and the correlation of logs and audit records with other systems. If an illicit time source is used for... |
| V-226443 | Medium | All accounts on the system must have unique user or account names. | 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... |
| V-226442 | Medium | The system must not have unnecessary accounts. | 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... |
| V-226445 | Medium | UIDs reserved for system accounts must not be assigned to non-system accounts. | 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... |
| V-226444 | Medium | All accounts must be assigned unique User Identification Numbers (UIDs). | 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... |
| V-226446 | Medium | GIDs reserved for system accounts must not be assigned to non-system groups. | 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... |
| V-226551 | Medium | Global initialization files library search paths must contain only authorized paths. | The library search path environment variable(s) contain a list of directories for the dynamic linker to search to find libraries. If this path includes the current working directory or other... |
| V-226592 | Medium | System audit logs must have mode 0640 or less permissive. | 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... |
| V-226629 | Medium | The cron.deny file must have mode 0600 or less permissive. | If file permissions for cron.deny are more permissive than 0600, sensitive information could be viewed or edited by unauthorized users. |
| V-226628 | Medium | The cron log files must not have extended ACLs. | Cron logs contain reports of scheduled system activities and must be protected from unauthorized access or manipulation. |
| V-226625 | Medium | Cron and crontab directories must be group-owned by root, sys, or bin. | 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... |
| V-226624 | Medium | Cron and crontab directories must be owned by root or bin. | 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... |
| V-226627 | Medium | The cronlog file must have mode 0600 or less permissive. | Cron logs contain reports of scheduled system activities and must be protected from unauthorized access or manipulation. |
| V-226626 | Medium | Cron logging must be implemented. | 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. |
| V-226621 | Medium | Crontab files must not have extended ACLs. | To protect the integrity of scheduled system jobs and to prevent malicious modification to these jobs, crontab files must be secured. ACLs on crontab files may provide unauthorized access to the files. |
| V-226620 | Medium | Crontab files must have mode 0600 or less permissive. | To protect the integrity of scheduled system jobs and prevent malicious modification to these jobs, crontab files must be secured. |
| V-226623 | Medium | Cron and crontab directories must not have extended ACLs. | To protect the integrity of scheduled system jobs and to prevent malicious modification to these jobs, crontab files must be secured. ACLs on cron and crontab directories may provide unauthorized... |
| V-226622 | Medium | Cron and crontab directories must have mode 0755 or less permissive. | To protect the integrity of scheduled system jobs and to prevent malicious modification to these jobs, crontab files must be secured. |
| V-226439 | Medium | The time synchronization configuration file (such as /etc/ntp.conf) must be group-owned by root, bin, or sys. | A synchronized system clock is critical for the enforcement of time-based policies and the correlation of logs and audit records with other systems. If an illicit time source is used for... |
| V-226992 | Medium | The SSH daemon must restrict login ability to specific users and/or groups. | Restricting SSH logins to a limited group of users, such as system administrators, prevents password-guessing and other SSH attacks from reaching system accounts and other accounts not authorized... |
| V-227000 | Medium | The SSH daemon must be configured for IP filtering. | The SSH daemon must be configured for IP filtering to provide a layered defense against connection attempts from unauthorized addresses. |
| V-226498 | Medium | NIS/NIS+/yp files must be owned by root, sys, or bin. | 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... |
| V-226881 | Medium | Kernel core dumps must be disabled unless needed. | Kernel core dumps may contain the full contents of system memory at the time of the crash. Kernel core dumps may consume a considerable amount of disk space and may result in Denial of Service by... |
| V-220029 | Medium | All interactive user's home directories must be owned by their respective users. | If users do not own their home directories, unauthorized users could access user files. |
| V-220028 | Medium | Library files must have mode 0755 or less permissive. | Unauthorized access could destroy the integrity of the library files. |
| V-226552 | Medium | Global initialization files lists of preloaded libraries must contain only authorized paths. | The library preload list environment variable contains a list of libraries for the dynamic linker to load before loading the libraries required by the binary. If this list contains paths to... |
| V-220025 | Medium | The root account must be the only account having an UID of 0. | If an account has an UID of 0, it has root authority. Multiple accounts with an UID of 0 afford more opportunity for potential intruders to guess a password for a privileged account. |
| V-220024 | Medium | Accounts must be locked upon 35 days of inactivity. | On some systems, accounts with disabled passwords still allow access using rcp, remsh, or rlogin through equivalent remote hosts. All that is required is the remote host name and the user name... |
| V-220026 | Medium | The root account must not have world-writable directories in its executable search path. | 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. |
| V-220021 | Medium | The system must disable accounts after three consecutive unsuccessful login attempts. | Disabling accounts after a limited number of unsuccessful login attempts improves protection against password guessing attacks. |
| V-220020 | Medium | Direct logins must not be permitted to shared, default, application, or utility accounts. | 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... |
| V-220023 | Medium | Graphical desktop environments provided by the system must automatically lock after 15 minutes of inactivity and the system must require users to re-authenticate to unlock the environment. | 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... |
| V-220022 | Medium | The delay between login prompts following a failed login attempt must be at least 4 seconds. | Enforcing a delay between successive failed login attempts increases protection against automated password guessing attacks. |
| V-226499 | Medium | NIS/NIS+/yp files must be group-owned by root, sys, or bin. | 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... |
| V-226557 | Medium | Local initialization files library search paths must contain only authorized paths. | The library search path environment variable(s) contain a list of directories for the dynamic linker to search to find libraries. If this path includes the current working directory or other... |
| V-226556 | Medium | All local initialization files executable search paths must contain only authorized 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... |
| V-226887 | Medium | The system must use initial TCP sequence numbers most resistant to sequence number guessing attacks. | One use of initial TCP sequence numbers is to verify bidirectional communication between two hosts, which provides some protection against spoofed source addresses being used by the connection... |
| V-226886 | Medium | The system must implement non-executable program stacks. | A common type of exploit is the stack buffer overflow. An application receives, from an attacker, more data than it is prepared for and stores this information on its stack, writing beyond the... |
| V-226975 | Medium | The snmpd.conf file must be group-owned by root, sys, or bin. | The snmpd.conf file contains authenticators and must be protected from unauthorized access and modification. If the file is not group-owned by a system group, it may be subject to access and... |
| V-226974 | Medium | The snmpd.conf files must be owned by root. | The snmpd.conf files contain authenticators and must be protected from unauthorized access and modification. If the files are not owned by root, they may be subject to access and modification... |
| V-226977 | Medium | If the system is a Network Management System (NMS) server, it must only run the NMS and any software required by the NMS. | Installing extraneous software on a system designated as a dedicated Network Management System (NMS) server poses a security threat to the system and the network. Should an attacker gain access to... |
| V-226976 | Medium | The snmpd.conf file must not have an extended ACL. | The snmpd.conf file contains authenticators and must be protected from unauthorized access and modification. |
| V-226973 | Medium | Management Information Base (MIB) files must not have extended ACLs. | 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. |
| V-226972 | Medium | Management Information Base (MIB) files must have mode 0640 or less permissive. | 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. |
| V-227011 | Medium | All NFS exported system files and system directories must be group-owned by root, bin, or sys. | Failure to give group ownership of sensitive files or directories to root provides the members of the owning group with the potential to access sensitive information or change system configuration... |
| V-227013 | Medium | The system's NFS export configuration must not have the sec option set to none (or equivalent); additionally, the default authentication must not to be set to none. | If sec=none on Solaris, all NFS requests are mapped to an unknown/common user instead of being processed according to the provided UID. |
| V-226979 | Medium | The /etc/syslog.conf file must not have an extended ACL. | Unauthorized users must not be allowed to access or modify the /etc/syslog.conf file. |
| V-226871 | Medium | The at.allow file must be owned by root, bin, or sys. | If the owner of the at.allow file is not set to root, bin, or sys, unauthorized users could be allowed to view or edit sensitive information contained within the file. |
| V-227017 | Medium | The system must not run Samba unless needed. | 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. |
| V-227016 | Medium | The system must not have any peer-to-peer file-sharing application installed. | Peer-to-peer file-sharing software can result in the unintentional exfiltration of information. There are also many legal issues associated with these types of utilities including copyright... |
| V-226405 | Medium | The nosuid option must be configured in the /etc/rmmount.conf file. | The rmmount.conf file controls the mounting of removable media on a Solaris system. Removable media is not to be trusted with privileged access, and therefore the filesystems must be mounted with... |
| V-226407 | Medium | The /etc/security/audit_user file must be owned by root. | The /etc/security/audit_user is a sensitive file and must be owned by root to prevent possible system compromise. |
| V-226406 | Medium | The /etc/security/audit_user file must not define a different auditing level for specific users. | The audit_user file may be used to selectively audit more, or fewer, auditing features for specific individuals. If used this way it could subject the activity to a lawsuit and could cause the... |
| V-226409 | Medium | The /etc/security/audit_user file must have mode 0640 or less permissive. | Audit_user is a sensitive file that, if compromised, would allow a malicious user to select auditing parameters to ignore his sessions. This would allow malicious operations the auditing... |
| V-226408 | Medium | The /etc/security/audit_user file must be group-owned by root, sys, or bin. | The Solaris audit_user file allows for selective auditing or non-auditing of features for certain users. If it is not protected, it could be compromised and used to mask audit events. This could... |
| V-220058 | Medium | The NFS server must be configured to restrict file system access to local hosts. | 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... |
| V-220059 | Medium | The system must not have a public Instant Messaging (IM) client installed. | Public Instant Messaging (IM) systems are not approved for use and may result in the unauthorized distribution of information. IM clients provide a way for a user to send a message to one or more... |
| V-226494 | Medium | System log files must not have extended ACLs, except as needed to support authorized software. | If the system log files are not protected, unauthorized users could change the logged data, eliminating its forensic value. Authorized software may be given log file access through the use of... |
| V-220052 | Medium | 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. | If TFTP has a valid shell, it increases the likelihood of someone logging to the TFTP account and compromising the system. |
| V-220053 | Medium | The system must not be used as a syslog server (log host) for systems external to the enclave. | Syslog messages are typically unencrypted and may contain sensitive information and are, therefore, restricted to the enclave. |
| V-220054 | Medium | The syslog daemon must not accept remote messages unless it is a syslog server documented using site-defined procedures. | Unintentionally running a syslog server accepting remote messages puts the system at increased risk. Malicious syslog messages sent to the server could exploit vulnerabilities in the server... |
| V-220056 | Medium | IP forwarding for IPv4 must not be enabled, unless the system is a router. | If the system is configured for IP forwarding and is not a designated router, it could be used to bypass network security by providing a path for communication not filtered by network devices. |
| V-220057 | Medium | The system must not have IP forwarding for IPv6 enabled, unless the system is an IPv6 router. | If the system is configured for IP forwarding and is not a designated router, it could be used to bypass network security by providing a path for communication not filtered by network devices. |
| V-226585 | Medium | All public directories must be owned by root or an application account. | 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... |
| V-226586 | Medium | All public directories must be group-owned by root or an application group. | If a public directory has the sticky bit set and is not group-owned by a system GID, unauthorized users may be able to modify files created by others.
The only authorized public directories are... |
| V-226587 | Medium | The system and user default umask must be 077. | 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... |
| V-226580 | Medium | The system must be checked weekly for unauthorized setuid files, as well as, unauthorized modification to authorized setuid files. | 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,... |
| V-226581 | Medium | The owner, group-owner, mode, ACL, and location of files with the setgid bit set must be documented using site-defined procedures. | 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,... |
| V-226582 | Medium | The system must be checked weekly for unauthorized setgid files, as well as, unauthorized modification to authorized setgid files. | 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,... |
| V-226583 | Medium | Public directories must be the only world-writable directories and world-writable files must be located only in public directories. | World-writable files and directories make it easy for a malicious user to place potentially compromising files on the system.
The only authorized public directories are those temporary... |
| V-226588 | Medium | Default system accounts must be disabled or removed. | Vendor accounts and software may contain backdoors allowing unauthorized access to the system. These backdoors are common knowledge and present a threat to system security if the account is not disabled. |
| V-226589 | Medium | Auditing must be implemented. | Without auditing, individual system accesses cannot be tracked and malicious activity cannot be detected and traced back to an individual account. |
| V-227001 | Medium | The SSH daemon must be configured with the Department of Defense (DoD) login banner. | Failure to display the DoD logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources.
The SSH service must be configured to... |
| V-226903 | Medium | The root file system must employ journaling or another mechanism ensuring file system consistency. | 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... |
| V-226905 | Medium | The system must log authentication informational data. | Monitoring and recording successful and unsuccessful logins assists in tracking unauthorized access to the system. |
| V-226906 | Medium | Inetd and xinetd must be disabled or removed if no network services utilizing them are enabled. | Unnecessary services should be disabled to decrease the attack surface of the system. |
| V-226907 | Medium | The inetd.conf file must be owned by root or bin. | 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... |
| V-226908 | Medium | The inetd.conf file must be group-owned by root, bin, or sys. | Failure to give ownership of sensitive files or utilities to system groups may provide unauthorized users with the potential to access sensitive information or change the system configuration... |
| V-226909 | Medium | The inetd.conf file must have mode 0440 or less permissive. | 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. |
| V-226573 | Medium | Device files and directories must only be writable by users with a system account or as configured by the vendor. | System device files in writable directories could be modified, removed, or used by an unprivileged user to control system hardware. |
| V-226575 | Medium | Audio devices must have mode 0660 or less permissive. | Globally accessible audio and video devices have proven to be security hazards. There is software that can activate system microphones and video devices connected to user workstations and/or X... |
| V-226574 | Medium | Device files used for backup must only be readable and/or writable by root or the backup user. | 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. |
| V-226577 | Medium | Audio devices must be owned by root. | Globally Accessible audio and video devices have proven to be security hazards. There is software that can activate system microphones and video devices connected to user workstations and/or X... |
| V-226576 | Medium | Audio devices must not have extended ACLs. | File system ACLs can provide access to files beyond what is allowed by the mode numbers of the files. |
| V-226472 | Medium | The root account's home directory (other than /) must have mode 0700. | Permissions greater than 0700 could allow unauthorized users access to the root home directory. |
| V-226473 | Medium | The root account's home directory must not have an extended ACL. | File system extended ACLs provide access to files beyond what is allowed by the mode numbers of the files. |
| V-226474 | Medium | The root accounts executable search path must contain only authorized 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... |
| V-226475 | Medium | The root account's library search path must be the system default and must contain only absolute paths. | The library search path environment variable(s) contain a list of directories for the dynamic linker to search to find libraries. If this path includes the current working directory or other... |
| V-226476 | Medium | The root account's list of preloaded libraries must be empty. | The library preload list environment variable contains a list of libraries for the dynamic linker to load before loading the libraries required by the binary. If this list contains paths to... |
| V-226477 | Medium | The system must prevent the root account from directly logging in except from the system console. | Limiting the root account direct logins to only system consoles protects the root account from direct unauthorized access from a non-console device. |
| V-226478 | Medium | Remote consoles must be disabled or protected from unauthorized access. | 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... |
| V-226479 | Medium | The root account must not be used for direct logins. | Direct login with the root account prevents individual user accountability. Acceptable non-routine uses of the root account for direct login are limited to emergency maintenance, the use of... |
| V-226535 | Medium | All files and directories contained in user home directories must not have extended ACLs. | Excessive permissions allow unauthorized access to user files. |
| V-227021 | Medium | The smb.conf file must not have an extended ACL. | Excessive permissions could endanger the security of the Samba configuration file and, ultimately, the system and network. |
| V-226537 | Medium | All run control scripts must have no extended ACLs. | If the startup files are writable by other users, they could modify the startup files to insert malicious commands into the startup files. |
| V-226492 | Medium | System files, programs, and directories must be group-owned by a system group. | Restricting permissions will protect the files from unauthorized modification. |
| V-226536 | Medium | All run control scripts must have mode 0755 or less permissive. | If the startup files are writable by other users, they could modify the startup files to insert malicious commands into the startup files. |
| V-226438 | Medium | The time synchronization configuration file (such as /etc/ntp.conf) must be owned by root. | A synchronized system clock is critical for the enforcement of time-based policies and the correlation of logs and audit records with other systems. If an illicit time source is used for... |
| V-227025 | Medium | The smbpasswd file must not have an extended ACL. | If the permissions of the smbpasswd file are too permissive, the smbpasswd file may be maliciously accessed or modified, potentially resulting in the compromise of Samba accounts. |
| V-227019 | Medium | The smb.conf file must be group-owned by root, bin, or sys. | 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. |
| V-227026 | Medium | The smb.conf file must use the hosts option to restrict access to Samba. | Samba increases the attack surface of the system and must be restricted to communicate only with systems requiring access. |
| V-227018 | Medium | The smb.conf file must be owned by root. | The smb.conf file allows access to other machines on the network and grants permissions to certain users. If it is owned by another user, the file may be maliciously modified and the Samba... |
| V-227027 | Medium | Samba must be configured to use an authentication mechanism other than "share." | Samba share authentication does not provide for individual user identification and must not be used. |
| V-226614 | Medium | The cron.allow file must not have an extended ACL. | A cron.allow file that is readable and/or writable by other than root could allow potential intruders and malicious users to use the file contents to help discern information, such as who is... |
| V-227028 | Medium | Samba must be configured to use encrypted passwords. | Samba must be configured to protect authenticators. If Samba passwords are not encrypted for storage, plain-text user passwords may be read by those with access to the Samba password file. |
| V-226616 | Medium | Cron must not execute programs in, or subordinate to, world-writable directories. | 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. |
| V-226617 | Medium | Crontabs must be owned by root or the crontab creator. | To protect the integrity of scheduled system jobs and prevent malicious modification to these jobs, crontab files must be secured. |
| V-226610 | Medium | Audit logs must be rotated daily. | Rotate audit logs daily to preserve audit file system space and to conform to the DoD/DISA requirement. If it is not rotated daily and moved to another location, then there is more of a chance... |
| V-226612 | Medium | Access to the cron utility must be controlled using the cron.allow and/or cron.deny file(s). | 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... |
| V-226613 | Medium | The cron.allow file must have mode 0600 or less permissive. | A cron.allow file that is readable and/or writable by other than root could allow potential intruders and malicious users to use the file contents to help discern information, such as who is... |
| V-226993 | Medium | The SSH public host key files must have mode 0644 or less permissive. | If a public host key file is modified by an unauthorized user, the SSH service may be compromised. |
| V-226971 | Medium | The snmpd.conf file must have mode 0600 or less permissive. | The snmpd.conf file contains authenticators and must be protected from unauthorized access and modification. |
| V-226991 | Medium | The SSH client must be configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms. | DoD information systems are required to use FIPS 140-2 approved cryptographic hash functions.
Satisfies: SRG-OS-000250, SRG-OS-000495, SRG-OS-000500 |
| V-226990 | Medium | The SSH client must be configured to not use CBC-based ciphers. | The Cipher-Block Chaining (CBC) mode of encryption as implemented in the SSHv2 protocol is vulnerable to chosen plain text attacks and must not be used. |
| V-226618 | Medium | Crontab files must be group-owned by root, sys, or the crontab creator's primary group. | To protect the integrity of scheduled system jobs and prevent malicious modification to these jobs, crontab files must be secured. |
| V-226619 | Medium | Default system accounts (with the exception of root) must not be listed in the cron.allow file or must be included in the cron.deny file, if cron.allow does not exist. | To centralize the management of privileged account crontabs, of the default system accounts, only root may have a crontab. |
| V-226970 | Medium | The SNMP service must use only SNMPv3 or its successors. | SNMP Versions 1 and 2 are not considered secure. Without the strong authentication and privacy provided by the SNMP Version 3 User-based Security Model (USM), an attacker or other unauthorized... |
| V-226539 | Medium | Run control scripts lists of preloaded libraries must contain only authorized paths. | The library preload list environment variable contains a list of libraries for the dynamic linker to load before loading the libraries required by the binary. If this list contains paths to... |
| V-226490 | Medium | All system command files must not have extended ACLs. | 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... |
| V-226538 | Medium | Run control scripts executable search paths must contain only authorized 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... |
| V-226874 | Medium | The at.deny file must be group-owned by root, bin, or sys. | If the group owner of the at.deny file is not set to root, bin, or sys, unauthorized users could be allowed to view or edit sensitive information contained within the file. Unauthorized... |
| V-227010 | Medium | All NFS-exported system files and system directories must be owned by root. | 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... |
| V-227012 | Medium | The NFS anonymous UID and GID must be configured to values that have no permissions. | 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... |
| V-226870 | Medium | "At" jobs must not set the umask to a value less restrictive than 077. | 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... |
| V-227014 | Medium | The NFS server must not allow remote root access. | If the NFS server allows root access to local file systems from remote hosts, this access could be used to compromise the system. |
| V-226872 | Medium | The at.allow file must be group-owned by root, bin, or sys. | If the group owner of the at.allow file is not set to root, bin, or sys, unauthorized users could be allowed to view or edit the list of users permitted to run at jobs. Unauthorized modification... |
| V-226873 | Medium | The at.deny file must be owned by root, bin, or sys. | 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. |
| V-227055 | Medium | The system must ignore IPv6 ICMP redirect messages. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the host's route table and are unauthenticated. An... |
| V-227054 | Medium | The DHCP client must be disabled if not needed. | DHCP allows for the unauthenticated configuration of network parameters on the system by exchanging information with a DHCP server. |
| V-227057 | Medium | The system must not forward IPv6 source-routed packets. | Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security... |
| V-227056 | Medium | The system must not send IPv6 ICMP redirects. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain information from the system's route table revealing ... |
| V-227051 | Medium | The Transparent Inter-Process Communication (TIPC) protocol must be disabled or not installed. | The Transparent Inter-Process Communication (TIPC) protocol is a relatively new cluster communications protocol developed by Ericsson. Binding this protocol to the network stack increases the... |
| V-227050 | Medium | The Reliable Datagram Sockets (RDS) protocol must be disabled or not installed unless required. | The Reliable Datagram Sockets (RDS) protocol is a relatively new protocol developed by Oracle for communication between the nodes of a cluster. Binding this protocol to the network stack... |
| V-227053 | Medium | The system must not have IP tunnels configured. | IP tunneling mechanisms can be used to bypass network filtering. |
| V-227052 | Medium | The system must not have 6to4 enabled. | 6to4 is an IPv6 transition mechanism that involves tunneling IPv6 packets encapsulated in IPv4 packets on an ad-hoc basis. This is not a preferred transition strategy and increases the attack... |
| V-227059 | Medium | If the system is using LDAP for authentication or account information, the system must use a TLS connection using FIPS 140-2 approved cryptographic algorithms. | LDAP can be used to provide user authentication and account information, which are vital to system security. Communication between an LDAP server and a host using LDAP requires... |
| V-227058 | Medium | The system must not respond to ICMPv6 echo requests sent to a broadcast address. | Responding to broadcast ICMP echo requests facilitates network mapping and provides a vector for amplification attacks. |
| V-220017 | Medium | The ASET master files must be located in the /usr/aset/masters directory. | If ASET is used and the master files (tune.high, tune.med, tune.low, and uid_aliases) are not located in the proper place, ASET cannot operate correctly and valuable security findings could be lost. |
| V-220018 | Medium | The asetenv file YPCHECK variable must be set to true when NIS+ is configured. | If YPCHECK is not set to true in asetenv, then ypfiles may not be checked. |
| V-220019 | Medium | The system must require authentication upon booting into single-user and maintenance modes. | If the system does not require valid root authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged access to... |
| V-226948 | Medium | The ftpusers file must exist. | 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. |
| V-226949 | Medium | The ftpusers file must contain account names not allowed to use FTP. | The ftpusers file contains a list of accounts that are not allowed to use FTP to transfer files. If the file does not contain the names of all accounts not authorized to use FTP, then unauthorized... |
| V-226944 | Medium | Mail relaying must be restricted. | If unrestricted mail relaying is permitted, unauthorized senders could use this host as a mail relay for the purpose of sending SPAM or other unauthorized activity. |
| V-226945 | Medium | Unencrypted FTP must not be used on the system. | FTP is typically unencrypted and, therefore, presents confidentiality and integrity risks. FTP may be protected by encryption in certain cases, such as when used in a Kerberos environment. SFTP... |
| V-226946 | Medium | Anonymous FTP must not be active on the system unless authorized. | Due to the numerous vulnerabilities inherent in anonymous FTP, it is recommended that it not be used. If anonymous FTP must be used on a system, the requirement must be authorized and approved in... |
| V-226947 | Medium | If the system is an anonymous FTP server, it must be isolated to the DMZ network. | Anonymous FTP is a public data service which is only permitted in a server capacity when located on the DMZ network. |
| V-226940 | Medium | The SMTP service log file must not have an extended ACL. | If the SMTP service log file has an extended ACL, unauthorized users may be allowed to access or to modify the log file. |
| V-227020 | Medium | The smb.conf file must have mode 0644 or less permissive. | If the smb.conf file has excessive permissions, the file may be maliciously modified and the Samba configuration could be compromised. |
| V-227022 | Medium | The smbpasswd file must be owned by root. | 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. |
| V-227023 | Medium | The smbpasswd file must be group-owned by root. | If the smbpasswd file is not group-owned by root, the smbpasswd file may be maliciously accessed or modified, potentially resulting in the compromise of Samba accounts. |
| V-227024 | Medium | The smbpasswd file must have mode 0600 or less permissive. | If the smbpasswd file has a mode more permissive than 0600, the smbpasswd file may be maliciously accessed or modified, potentially resulting in the compromise of Samba accounts. |
| V-226530 | Medium | All users' home directories must have mode 0750 or less permissive. | Excessive permissions on home directories allow unauthorized access to user's files. |
| V-226533 | Medium | All files and directories contained in user home directories must be group-owned by a group of which the home directory's owner is a member. | If a user's files are group-owned by a group of which the user is not a member, unintended users may be able to access them. |
| V-226434 | Medium | The system clock must be synchronized to an authoritative DoD time source. | 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,... |
| V-226435 | Medium | The system clock must be synchronized continuously. | A synchronized system clock is critical for the enforcement of time-based policies and the correlation of logs and audit records with other systems. Internal system clocks tend to drift and... |
| V-226436 | Medium | The system must use at least two time sources for clock synchronization. | A synchronized system clock is critical for the enforcement of time-based policies and the correlation of logs and audit records with other systems. For redundancy, two time sources are required... |
| V-226431 | Medium | System security patches and updates must be installed and up-to-date. | Timely patching is critical for maintaining the operational availability, confidentiality, and integrity of Information Technology (IT) systems. However, failure to keep operating system and... |
| V-226432 | Medium | A file integrity baseline must be created and maintained. | 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... |
| V-226433 | Medium | 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. | 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... |
| V-226540 | Medium | Run control scripts lists of preloaded libraries must contain only authorized paths. | The library preload list environment variable contains a list of libraries for the dynamic linker to load before loading the libraries required by the binary. If this list contains paths to... |
| V-226542 | Medium | All system start-up files must be owned by root. | 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... |
| V-226543 | Medium | All system start-up files must be group-owned by root, sys, or bin. | If system start-up files do not have a group owner of root or a system group, the files may be modified by malicious users or intruders. |
| V-226544 | Medium | System start-up files must only execute programs owned by a privileged UID or an application. | System start-up files executing programs owned by other than root (or another privileged user) or an application indicates the system may have been compromised. |
| V-226545 | Medium | All global initialization files must not have extended ACLs. | Global initialization files are used to configure the user's shell environment upon login. Malicious modification of these files could compromise accounts upon logon. |
| V-226898 | Medium | The system must not send IPv4 ICMP redirects. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain information from the system's route table that... |
| V-226547 | Medium | Skeleton files must not have extended ACLs. | If the skeleton files are not protected, unauthorized personnel could change user's startup parameters and possibly jeopardize user's files. |
| V-226548 | Medium | All skeleton files and directories (typically in /etc/skel) must be owned by root. | If the skeleton files are not protected, unauthorized personnel could change user startup parameters and possibly jeopardize user files. Failure to give ownership of sensitive files or utilities... |
| V-226897 | Medium | The system must ignore IPv4 ICMP redirect messages. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the host's route table and are unauthenticated. An... |
| V-226894 | Medium | The system must prevent local applications from generating source-routed packets. | Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. |
| V-226895 | Medium | The system must not accept source-routed IPv4 packets. | Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security... |
| V-226892 | Medium | The system must not respond to ICMP timestamp requests sent to a broadcast address. | The processing of Internet Control Message Protocol (ICMP) timestamp requests increases the attack surface of the system. Responding to broadcast ICMP timestamp requests facilitates network... |
| V-226893 | Medium | The system must not apply reversed source routing to TCP responses. | Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. |
| V-226891 | Medium | The system must not respond to ICMPv4 echoes sent to a broadcast address. | Responding to broadcast Internet Control Message Protocol (ICMP) echoes facilitates network mapping and provides a vector for amplification attacks. |
| V-226491 | Medium | All system files, programs, and directories must be owned by a system account. | Restricting permissions will protect the files from unauthorized modification. |
| V-226917 | Medium | The rshd service must not be installed. | The rshd process provides a typically unencrypted, host-authenticated remote access service. SSH should be used in place of this service. |
| V-226916 | Medium | The portmap or rpcbind service must not be installed unless needed. | The portmap and rpcbind services increase the attack surface of the system and should only be used when needed. The portmap or rpcbind services are used by a variety of services using Remote... |
| V-227029 | Medium | Samba must be configured to not allow guest access to shares. | Guest access to shares permits anonymous access and is not permitted. |
| V-226869 | Medium | The "at" directory must be group-owned by root, bin, or sys. | If the "at" directory's group owner is not root, bin, or sys, unauthorized users could be allowed to view or edit files containing sensitive information within the directory. |
| V-226868 | Medium | The "at" directory must be owned by root, bin, or sys. | 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. |
| V-227064 | Medium | If the system is using LDAP for authentication or account information, the TLS certificate authority file and/or directory (as appropriate) must be owned by root. | LDAP can be used to provide user authentication and account information, which are vital to system security. The LDAP client configuration must be protected from unauthorized modification. |
| V-227065 | Medium | If the system is using LDAP for authentication or account information, the TLS certificate authority file and/or directory (as appropriate) must be group-owned by root, bin, or sys. | LDAP can be used to provide user authentication and account information, which are vital to system security. The LDAP client configuration must be protected from unauthorized modification |
| V-227066 | Medium | If the system is using LDAP for authentication or account information, the TLS certificate authority file and/or directory (as appropriate) must have mode 0644 (0755 for directories) or less permissive. | LDAP can be used to provide user authentication and account information, which are vital to system security. The LDAP client configuration must be protected from unauthorized modification. |
| V-227060 | Medium | If the system is using LDAP for authentication or account information the LDAP client configuration file must have mode 0600 or less permissive. | LDAP can be used to provide user authentication and account information, which are vital to system security. The LDAP client configuration must be protected from unauthorized modification. |
| V-227061 | Medium | If the system is using LDAP for authentication or account information, the LDAP configuration file must be owned by root. | LDAP can be used to provide user authentication and account information, which are vital to system security. The LDAP client configuration must be protected from unauthorized modification. |
| V-227062 | Medium | If the system is using LDAP for authentication or account information, the LDAP configuration file must be group-owned by root, bin, or sys. | LDAP can be used to provide user authentication and account information, which are vital to system security. The LDAP client configuration must be protected from unauthorized modification. |
| V-226860 | Medium | Access to the at utility must be controlled via the at.allow and/or at.deny file(s). | 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... |
| V-220048 | Medium | The system must not use .forward files. | 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... |
| V-220043 | Medium | The hosts.lpd (or equivalent) file must be group-owned by root, bin, or sys. | Failure to give group ownership of the hosts.lpd (or equivalent) file to root, bin, sys, or system provides the members of the owning group and possible unauthorized users, with the potential to... |
| V-220041 | Medium | Network analysis tools must not be installed. | Network analysis tools allow for the capture of network traffic visible to the system. |
| V-220040 | Medium | The rlogind service must not be running. | The rlogind process provides a typically unencrypted, host-authenticated remote access service. SSH should be used in place of this service.
Satisfies: SRG-OS-000033, SRG-OS-000505, SRG-OS-000555 |
| V-220046 | Medium | The SMTP service HELP command must not be enabled. | The HELP command should be disabled to mask version information. The version of the SMTP service software could be used by attackers to target vulnerabilities present in specific software versions. |
| V-220045 | Medium | The aliases file must be group-owned by root, sys, smmsp, or bin. | If the alias file is not group-owned by root or a system group, an unauthorized user may modify the file to add aliases to run malicious code or redirect email. |
| V-226593 | Medium | All system audit files must not have extended ACLs. | If a user can write to the audit logs, then audit trails can be modified or destroyed and system intrusion may not be detected. |
| V-226546 | Medium | All skeleton files (typically those in /etc/skel) must have mode 0644 or less permissive. | If the skeleton files are not protected, unauthorized personnel could change user startup parameters and possibly jeopardize user files. |
| V-226978 | Medium | The /etc/syslog.conf file must have mode 0640 or less permissive. | Unauthorized users must not be allowed to access or modify the /etc/syslog.conf file. |
| V-226599 | Medium | The audit system must be configured to audit failed attempts to access files and programs. | 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. |
| V-226896 | Medium | Proxy ARP must not be enabled on the system. | Proxy ARP allows a system to respond to ARP requests on one interface on behalf of hosts connected to another interface. If this function is enabled when not required, addressing information may... |
| V-227063 | Medium | If the system is using LDAP for authentication or account information, the /etc/ldap.conf (or equivalent) file must not have an extended ACL. | LDAP can be used to provide user authentication and account information, which are vital to system security. The LDAP client configuration must be protected from unauthorized modification. |
| V-226549 | Medium | All skeleton files (typically in /etc/skel) must be group-owned by root, bin, or sys. | If the skeleton files are not protected, unauthorized personnel could change user startup parameters and possibly jeopardize user files. |
| V-226913 | Medium | The services file must have mode 0444 or less permissive. | 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. |
| V-226912 | Medium | The services file must be group-owned by root, bin, or sys. | Failure to give ownership of system configuration files to root or a system group provides the designated owner and unauthorized users with the potential to change the system configuration which... |
| V-226911 | Medium | The services file must be owned by root or bin. | 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... |
| V-226910 | Medium | The inetd.conf file must not have extended ACLs. | 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. |
| V-226508 | Medium | The /etc/hosts file must have mode 0644 or less permissive. | The /etc/hosts file (or equivalent) configures local host name to IP address mappings that typically take precedence over DNS resolution. If this file is maliciously modified, it could cause the... |
| V-226509 | Medium | The /etc/hosts file must not have an extended ACL. | The /etc/hosts file (or equivalent) configures local host name to IP address mappings that typically take precedence over DNS resolution. If this file is maliciously modified, it could cause the... |
| V-226914 | Medium | The services file must not have an extended ACL. | The services file is critical to the proper operation of network services and must be protected from unauthorized modification. If the services file has an extended ACL, it may be possible for... |
| V-226504 | Medium | The /etc/resolv.conf file must have mode 0644 or less permissive.
| The resolv.conf (or equivalent) file configures the system's DNS resolver. DNS is used to resolve host names to IP addresses. If DNS configuration is modified maliciously, host name resolution... |
| V-226505 | Medium | The /etc/resolv.conf file must not have an extended ACL. | The resolv.conf (or equivalent) file configures the system's DNS resolver. DNS is used to resolve host names to IP addresses. If DNS configuration is modified maliciously, host name resolution... |
| V-226507 | Medium | The /etc/hosts file must be group-owned by root, bin, or sys. | The /etc/hosts file (or equivalent) configures local host name to IP address mappings that typically take precedence over DNS resolution. If this file is maliciously modified, it could cause the... |
| V-226500 | Medium | The NIS/NIS+/yp command files must have mode 0755 or less permissive. | 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... |
| V-226501 | Medium | NIS/NIS+/yp command files must not have extended ACLs. | NIS/NIS+/yp files are part of the system's identification and authentication processes and are, therefore, critical to system security. ACLs on these files could result in unauthorized... |
| V-226502 | Medium | The /etc/resolv.conf file must be owned by root. | The resolv.conf (or equivalent) file configures the system's DNS resolver. DNS is used to resolve host names to IP addresses. If DNS configuration is modified maliciously, host name resolution... |
| V-226503 | Medium | The /etc/resolv.conf file must be group-owned by root, bin, or sys. | The resolv.conf (or equivalent) file configures the system's DNS resolver. DNS is used to resolve host names to IP addresses. If DNS configuration is modified maliciously, host name resolution... |
| V-226463 | Medium | The system must require passwords to contain at least one special character. | 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... |
| V-226571 | Medium | All shell files must not have extended ACLs. | Shells with world/group write permissions give the ability to maliciously modify the shell to obtain unauthorized access. |
| V-226461 | Medium | The system must require passwords to contain at least one uppercase alphabetic character. | 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... |
| V-226460 | Medium | The password hashes stored on the system must have been generated using a FIPS 140-2 approved cryptographic hashing algorithm. | Systems must employ cryptographic hashes for passwords using the SHA-2 family of algorithms or FIPS 140-2 approved successors. The use of unapproved algorithms may result in weak password hashes... |
| V-226467 | Medium | The system must require at least eight characters be changed between the old and new passwords during a password change. | To ensure password changes are effective in their goals, the system must ensure old and new passwords have significant differences. Without significant changes, new passwords may be easily... |
| V-226466 | Medium | All non-interactive/automated processing account passwords must be changed at least once per year or be locked. | Limiting the lifespan of authenticators limits the period of time an unauthorized user has access to the system while using compromised credentials and reduces the period of time available for... |
| V-226465 | Medium | User passwords must be changed at least every 60 days. | Limiting the lifespan of authenticators limits the period of time an unauthorized user has access to the system while using compromised credentials and reduces the period of time available for... |
| V-226464 | Medium | The system must require passwords to contain no more than three consecutive repeating characters. | 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. |
| V-226469 | Medium | The system must prohibit the reuse of passwords within five iterations. | If a user, or root, used the same password continuously or was allowed to change it back shortly after being forced to change it to something else, it would provide a potential intruder with the... |
| V-226468 | Medium | The system must prevent the use of dictionary words for passwords. | An easily guessable password provides an open door to any external or internal malicious intruder. Many computer compromises occur as the result of account name and password guessing. This is... |
| V-226918 | Medium | The rlogind service must not be installed. | The rlogind process provides a typically unencrypted, host-authenticated remote access service. SSH should be used in place of this service. |
| V-226578 | Medium | Audio devices must be group-owned by root, sys, or bin. | Without privileged group owners, audio devices will be vulnerable to being used as eaves-dropping devices by malicious users or intruders to possibly listen to conversations containing sensitive... |
| V-226607 | Medium | The audit system must be configured to audit login, logout, and session initiation. | 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. |
| V-226606 | Medium | The audit system must be configured to audit all administrative, privileged, and security actions. | 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. |
| V-226601 | Medium | The audit system must be configured to audit file deletions. | 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. |
| V-226600 | Medium | The audit system must alert the SA when the audit storage volume approaches its capacity. | An accurate and current audit trail is essential for maintaining a record of system activity. If the system fails, the SA must be notified and must take prompt action to correct the... |
| V-226609 | Medium | The audit system must be configured to audit the loading and unloading of dynamic kernel modules. | Actions concerning dynamic kernel modules must be recorded as they are substantial events. Dynamic kernel modules can increase the attack surface of a system. A malicious kernel module can be... |
| V-226608 | Medium | The audit system must be configured to audit all discretionary access control permission modifications. | 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. |
| V-226449 | Medium | The Department of Defense (DoD) login banner must be displayed immediately prior to, or as part of, graphical desktop environment login prompts. | Failure to display the login banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources.
This requirement applies to graphical desktop... |
| V-226448 | Medium | The Department of Defense (DoD) login banner must be displayed immediately prior to, or as part of, console login prompts. | Failure to display the login banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources. |
| V-226462 | Medium | The system must require passwords to contain at least one numeric character. | 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... |
| V-226506 | Medium | The /etc/hosts file must be owned by root. | The /etc/hosts file (or equivalent) configures local host name to IP address mappings that typically take precedence over DNS resolution. If this file is maliciously modified, it could cause the... |
| V-226528 | Medium | The /etc/passwd file must not contain password hashes. | If password hashes are readable by non-administrators, the passwords are subject to attack through lookup tables or cryptographic weaknesses in the hashes. |
| V-226967 | Medium | X Window System connections that are not required must be disabled. | If unauthorized clients are permitted access to the X server, a user's X session may be compromised. |
| V-226529 | Medium | The /etc/group file must not contain any group password hashes. | Group passwords are typically shared and should not be used. Additionally, if password hashes are readable by non-administrators, the passwords are subject to attack through lookup tables or... |
| V-227006 | Medium | The NFS export configuration file must be owned by root. | 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... |
| V-227007 | Medium | The NFS export configuration file must be group-owned by root, bin, or sys. | Failure to give group ownership of the NFS export configuration file to root or system groups provides the designated group owner and possible unauthorized users with the potential to change... |
| V-227004 | Medium | A system used for routing must not run other network services or applications. | 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... |
| V-227005 | Medium | The system must not be running any routing protocol daemons, unless the system is a router. | Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not required, system network information may be... |
| V-226957 | Medium | All FTP users must have a default umask of 077. | The umask controls the default access mode assigned to newly created files. An umask of 077 limits new files to mode 700 or less permissive. Although umask is stored as a 4-digit number, the... |
| V-227002 | Medium | The system must be configured with a default gateway for IPv4 if the system uses IPv4, unless the system is a router. | 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. |
| V-226953 | Medium | The ftpusers file must not have an extended ACL. | 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... |
| V-226952 | Medium | The ftpusers file must have mode 0640 or less permissive. | 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... |
| V-226951 | Medium | The ftpusers file must be group-owned by root, bin, or sys. | If the ftpusers file is not group-owned by root or a system group, an unauthorized user may modify the file to allow unauthorized accounts to use FTP. |
| V-227003 | Medium | The system must be configured with a default gateway for IPv6 if the system uses IPv6, unless the system is a router. | 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. |
| V-227033 | Medium | The /etc/news/hosts.nntp.nolimit (or equivalent) must have mode 0600 or less permissive. | 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. |
| V-227032 | Medium | The /etc/news/hosts.nntp file must not have an extended ACL. | File system extended ACLs provide access to files beyond what is allowed by the mode numbers of the files. Excessive permissions on the hosts.nntp file may allow unauthorized modification which... |
| V-227031 | Medium | The /etc/news/hosts.nntp (or equivalent) must have mode 0600 or less permissive. | 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. |
| V-227030 | Medium | The system must not run an Internet Network News (INN) server. | Internet Network News (INN) servers access Usenet newsfeeds and store newsgroup articles. INN servers use the Network News Transfer Protocol (NNTP) to transfer information from the Usenet to the... |
| V-227037 | Medium | The /etc/news/passwd.nntp file (or equivalent) must have mode 0600 or less permissive. | File permissions more permissive than 0600 for /etc/news/passwd.nntp may allow access to privileged information by system intruders or malicious users. |
| V-227036 | Medium | The /etc/news/nnrp.access file must not have an extended ACL. | File system extended ACLs provide access to files beyond what is allowed by the mode numbers of the files. Excessive permissions on the nnrp.access file may allow unauthorized modification which... |
| V-227035 | Medium | The /etc/news/nnrp.access (or equivalent) must have mode 0600 or less permissive. | 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. |
| V-227034 | Medium | The /etc/news/hosts.nntp.nolimit file must not have an extended ACL. | File system extended ACLs provide access to files beyond what is allowed by the mode numbers of the files. Excessive permissions on the hosts.nntp.nolimit file may allow unauthorized modification... |
| V-226427 | Medium | The inherit-pkg-dir zone option must be set to none or the system default list defined for sparse root zones. | Solaris zones have the capability to inherit elements of the global zone's filesystem, which reduces the amount storage required for a zone, but also limits the flexibility of the zone. The... |
| V-226426 | Medium | The /etc/zones directory, and its contents, must not have an extended ACL. | Solaris zones configuration files must be protected against illicit creation, modification, and deletion. |
| V-227039 | Medium | Files in /etc/news must be owned by root. | If critical system files are not owned by a privileged user, system integrity could be compromised. |
| V-227038 | Medium | The /etc/news/passwd.nntp file must not have an extended ACL. | Extended ACLs may provide excessive permissions on the /etc/news/passwd.nntp file, which may permit unauthorized access or modification to the NNTP configuration. |
| V-226423 | Medium | The /etc/zones directory, and its contents, must be owned by root. | Solaris zones configuration files must be protected against illicit creation, modification, and deletion. |
| V-226421 | Medium | Hidden extended file attributes must not exist on the system. | Solaris extended attributes are essentially files themselves that are of an arbitrary size and content. They could be used to hide files from ordinary system file scans. |
| V-226420 | Medium | The NFS server must have logging implemented. | Filesystem logging, especially for NFS exported file systems, can be critical to detecting data misuse and possible hardware/system errors that may, otherwise, go unnoticed. |
| V-226858 | Medium | The cron.deny file must be owned by root, bin, or sys. | Cron daemon control files restrict the scheduling of automated tasks and must be protected. |
| V-226859 | Medium | The cron.deny file must be group-owned by root, bin, or sys. | Cron daemon control files restrict the scheduling of automated tasks and must be protected. Unauthorized modification of the cron.deny file could result in Denial of Service to authorized cron... |
| V-226553 | Medium | All local initialization files must be owned by the user or root. | Local initialization files are used to configure the user's shell environment upon login. Malicious modification of these files could compromise accounts upon logon. |
| V-226550 | Medium | All global initialization files executable search paths must contain only authorized 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... |
| V-226555 | Medium | Local initialization files must not have extended ACLs. | Local initialization files are used to configure the user's shell environment upon login. Malicious modification of these files could compromise accounts upon logon. |
| V-226554 | Medium | All local initialization files must have mode 0740 or less permissive. | Local initialization files are used to configure the user's shell environment upon login. Malicious modification of these files could compromise accounts upon logon. |
| V-226889 | Medium | TCP backlog queue sizes must be set appropriately. | To provide some mitigation to TCP DoS attacks, the TCP backlog queue sizes must be set to at least 1280 or in accordance with product-specific guidelines. |
| V-226493 | Medium | System log files must have mode 0640 or less permissive. | If the system log files are not protected, unauthorized users could change the logged data, eliminating its forensic value. |
| V-226559 | Medium | User start-up files must not execute world-writable programs. | If start-up files execute world-writable programs, especially in unprotected directories, they could be maliciously modified to become Trojans destroying user files or otherwise compromising the... |
| V-226558 | Medium | Local initialization files lists of preloaded libraries must contain only authorized paths. | The library preload list environment variable contains a list of libraries for the dynamic linker to load before loading the libraries required by the binary If this list contains paths to... |
| V-226497 | Medium | All library files must not have extended ACLs. | Unauthorized access could destroy the integrity of the library files. |
| V-227080 | Medium | The hosts.lpd (or equivalent) must have mode 0644 or less permissive. | 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... |
| V-226888 | Medium | The system must not forward IPv4 source-routed packets. | Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security... |
| V-226615 | Medium | Cron must not execute group-writable or world-writable programs. | 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... |
| V-226591 | Medium | System audit logs must be group-owned by root, bin, or sys. | Sensitive system and user information could provide a malicious user with enough information to penetrate further into the system. |
| V-226999 | Medium | The SSH daemon must not allow compression or must only allow compression after successful authentication. | If compression is allowed in an SSH connection prior to authentication, vulnerabilities in the compression software could result in compromise of the system from an unauthenticated connection,... |
| V-226998 | Medium | The SSH daemon must not allow rhosts RSA authentication.
| If SSH permits rhosts RSA authentication, a user may be able to log in based on the keys of the host originating the request and not any user-specific authentication. |
| V-226590 | Medium | System audit logs must be owned by root. | 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. |
| V-226857 | Medium | The at.deny file must not have an extended ACL. | The "at" daemon control files restrict access to scheduled job manipulation and must be protected. Unauthorized modification of the at.deny file could result in Denial of Service to authorized... |
| V-227079 | Medium | The hosts.lpd (or equivalent) file must be owned by root. | Failure to give ownership of the hosts.lpd file to root provides the designated owner, and possible unauthorized users, with the potential to modify the hosts.lpd file. Unauthorized modifications... |
| V-227078 | Medium | The system, if capable, must be configured to require the use of a CAC, PIV compliant hardware token, or Alternate Logon Token (ALT) for authentication. | In accordance with CTO 07-015 PKI authentication is required. This provides stronger, two-factor authentication than using a username/password.
NOTE: The following are exempt from this, however,... |
| V-227074 | Medium | System BIOS or system controllers supporting password protection must have administrator accounts/passwords configured, and no others. | 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... |
| V-227072 | Medium | The system's local firewall must implement a deny-all, allow-by-exception policy. | A local firewall protects the system from exposing unnecessary or undocumented network services to the local enclave. If a system within the enclave is compromised, firewall protection on an... |
| V-227071 | Medium | The system must employ a local firewall. | A local firewall protects the system from exposing unnecessary or undocumented network services to the local enclave. If a system within the enclave is compromised, firewall protection on an... |
| V-227015 | Medium | The nosuid option must be enabled on all NFS client mounts. | Enabling the nosuid mount option prevents the system from granting owner or group-owner privileges to programs with the setuid or setgid bit set. If the system does not restrict this access,... |
| V-226997 | Medium | The SSH daemon must perform strict mode checking of home directory configuration files. | If other users have access to modify user-specific SSH configuration files, they may be able to log into the system as another user. |
| V-226994 | Medium | The SSH private host key files must have mode 0600 or less permissive. | If an unauthorized user obtains the private SSH host key file, the host could be impersonated. |
| V-226922 | Low | The system must not have the finger service active. | The finger service provides information about the system's users to network clients. This information could expose information that could be used in subsequent attacks. |
| V-226452 | Low | The system must display the date and time of the last successful account login upon login. | Providing users with feedback on when account accesses last occurred facilitates user recognition and reporting of unauthorized account use. |
| V-226453 | Low | The system must display a publicly-viewable pattern during a graphical desktop environment session lock. | To protect the on-screen content of a session, it must be replaced with a publicly-viewable pattern upon session lock. Examples of publicly viewable patterns include screen saver patterns,... |
| V-226631 | Low | Cron programs must not set the umask to a value less restrictive than 077. | 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... |
| V-220034 | Low | Global initialization files must contain the mesg -n or mesg n commands. | 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. |
| V-227008 | Low | The NFS export configuration file must have mode 0644 or less permissive. | 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... |
| V-227009 | Low | The NFS exports configuration file must not have an extended ACL. | File system extended ACLs provide access to files beyond what is allowed by the mode numbers of the files. Excessive permissions on the NFS export configuration file could allow unauthorized... |
| V-226481 | Low | The root shell must be located in the / file system. | To ensure the root shell is available in repair and administrative modes, the root shell must be located in the / file system. |
| V-226531 | Low | User's home directories must not have extended ACLs. | Excessive permissions on home directories allow unauthorized access to user's files. |
| V-227046 | Low | The file integrity tool must be configured to verify extended attributes. | Extended attributes in file systems are used to contain arbitrary data and file metadata with security implications. |
| V-227047 | Low | The file integrity tool must use FIPS 140-2 approved cryptographic hashes for validating file contents. | File integrity tools often use cryptographic hashes for verifying that file contents have not been altered. These hashes must be FIPS 140-2 approved. |
| V-227045 | Low | The file integrity tool must be configured to verify ACLs. | ACLs can provide permissions beyond those permitted through the file mode and must be verified by file integrity tools. |
| V-226936 | Low | Sendmail logging must not be set to less than nine in the sendmail.cf file. | 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. |
| V-226526 | Low | All interactive users must be assigned a home directory in the /etc/passwd file. | If users do not have a valid home directory, there is no place for the storage and control of files they own. |
| V-226527 | Low | All interactive user home directories defined in the /etc/passwd file must exist. | 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... |
| V-226447 | Low | All GIDs referenced in the /etc/passwd file must be defined in the /etc/group file. | If a user is assigned the GID of a group not existing on the system, and a group with the same GID is subsequently created, the user may have unintended rights to the group. |
| V-226878 | Low | The centralized process core dump data directory must be group-owned by root, bin, or sys. | Process core dumps contain the memory in use by the process when it crashed. Any data the process was handling may be contained in the core file, and it must be protected accordingly. If the... |
| V-226879 | Low | The centralized process core dump data directory must have mode 0700 or less permissive. | Process core dumps contain the memory in use by the process when it crashed. Any data the process was handling may be contained in the core file, and it must be protected accordingly. If the... |
| V-226875 | Low | Process core dumps must be disabled unless needed. | Process core dumps contain the memory in use by the process when it crashed. Process core dump files can be of significant size and their use can result in file systems filling to capacity, which... |
| V-226877 | Low | The centralized process core dump data directory must be owned by root. | Process core dumps contain the memory in use by the process when it crashed. Any data the process was handling may be contained in the core file, and it must be protected accordingly. If the... |
| V-226584 | Low | The sticky bit must be set on all public directories. | 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... |
| V-226900 | Low | A separate file system must be used for user home directories (such as /home or equivalent). | The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing. |
| V-226902 | Low | The system must use a separate filesystem for /tmp (or equivalent). | The use of separate filesystems for different paths can protect the system from failures resulting from a filesystem becoming full or failing. |
| V-226904 | Low | All local file systems must employ journaling or another mechanism ensuring file system consistency. | 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... |
| V-226572 | Low | The system must be checked for extraneous device files at least weekly. | If an unauthorized device is allowed to exist on the system, there is the possibility the system may perform unauthorized operations. |
| V-226470 | Low | The system must restrict the ability to switch to the root user to members of a defined group. | Configuring a supplemental group for users permitted to switch to the root user prevents unauthorized users from accessing the root account, even with knowledge of the root credentials. |
| V-226471 | Low | The root user's home directory must not be the root directory (/). | Changing the root home directory to something other than / and assigning it a 0700 protection makes it more difficult for intruders to manipulate the system by reading the files that root places... |
| V-226611 | Low | The system must be configured to send audit records to a remote audit server. | Audit records contain evidence that can be used in the investigation of compromised systems. To prevent this evidence from compromise, it must be sent to a separate system continuously. Methods... |
| V-226995 | Low | The SSH daemon must not permit GSSAPI authentication unless needed. | GSSAPI authentication is used to provide additional authentication mechanisms to applications. Allowing GSSAPI authentication through SSH exposes the system's GSSAPI to remote hosts, increasing... |
| V-226876 | Low | The system must be configured to store any process core dumps in a specific, centralized directory. | Specifying a centralized location for core file creation allows for the centralized protection of core files. Process core dumps contain the memory in use by the process when it crashed. Any... |
| V-226941 | Low | The SMTP service must not have the EXPN feature active. | 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... |
| V-226942 | Low | The SMTP service must not have the VRFY feature active. | 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... |
| V-226943 | Low | The Sendmail service must not have the wizard backdoor active. | 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. |
| V-226534 | Low | All files and directories contained in user's home directories must have mode 0750 or less permissive. | Excessive permissions allow unauthorized access to user's files. |
| V-226532 | Low | All files and directories contained in interactive user's home directories must be owned by the home directory's owner. | 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. |
| V-226437 | Low | The system must use time sources local to the enclave. | A synchronized system clock is critical for the enforcement of time-based policies and the correlation of logs and audit records with other systems. The network architecture should provide... |
| V-226890 | Low | The system must not process ICMP timestamp requests. | The processing of Internet Control Message Protocol (ICMP) timestamp requests increases the attack surface of the system. |
| V-227068 | Low | The system must have USB disabled unless needed. | USB is a common computer peripheral interface. USB devices may include storage devices that could be used to install malicious software on a system or exfiltrate data. |
| V-227069 | Low | The system must have USB Mass Storage disabled unless needed. | USB is a common computer peripheral interface. USB devices may include storage devices that could be used to install malicious software on a system or exfiltrate data. |
| V-227067 | Low | Automated file system mounting tools must not be enabled unless needed. | Automated file system mounting tools may provide unprivileged users with the ability to access local media and network shares. If this access is not necessary for the system's operation, it must... |
| V-220047 | Low | The SMTP services SMTP greeting must not provide version information. | The version of the SMTP service can be used by attackers to plan an attack based on vulnerabilities present in the specific version. |
| V-226597 | Low | System audit tool executables must not have extended ACLs. | To prevent unauthorized access or manipulation of system audit logs, the tools for manipulating those logs must be protected. |
| V-226596 | Low | System audit tool executables must have mode 0750 or less permissive. | To prevent unauthorized access or manipulation of system audit logs, the tools for manipulating those logs must be protected. |
| V-226595 | Low | System audit tool executables must be group-owned by root, bin, or sys. | To prevent unauthorized access or manipulation of system audit logs, the tools for manipulating those logs must be protected. |
| V-226594 | Low | System audit tool executables must be owned by root. | To prevent unauthorized access or manipulation of system audit logs, the tools for manipulating those logs must be protected. |
| V-226901 | Low | The system must use a separate file system for the system audit data path. | The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing. |
| V-226899 | Low | The system must log martian packets. | Martian packets are packets containing addresses known by the system to be invalid. Logging these messages allows the SA to identify misconfigurations or attacks in progress. |
| V-226598 | Low | The audit system must alert the SA in the event of an audit processing failure. | An accurate and current audit trail is essential for maintaining
a record of system activity. If the system fails, the SA must be notified and must take prompt
action to correct the... |
| V-226915 | Low | Inetd or xinetd logging/tracing must be enabled. | 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... |
| V-226605 | Low | The audit system must be configured to audit account termination. | 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. |
| V-226604 | Low | The audit system must be configured to audit account disabling. | 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. |
| V-226603 | Low | The audit system must be configured to audit account modification. | 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. |
| V-226602 | Low | The audit system must be configured to audit account creation. | 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. |
| V-226882 | Low | The kernel core dump data directory must be owned by root. | Kernel core dumps may contain the full contents of system memory at the time of the crash. As the system memory may contain sensitive information, it must be protected accordingly. If the kernel... |
| V-226954 | Low | The FTP daemon must be configured for logging or verbose mode. | 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... |
| V-226880 | Low | The centralized process core dump data directory must not have an extended ACL. | Process core dumps contain the memory in use by the process when it crashed. Any data the process was handling may be contained in the core file, and it must be protected accordingly. If the... |
| V-226883 | Low | The kernel core dump data directory must be group-owned by root. | Kernel core dumps may contain the full contents of system memory at the time of the crash. As the system memory may contain sensitive information, it must be protected accordingly. If the kernel... |
| V-226885 | Low | The kernel core dump data directory must not have an extended ACL. | Kernel core dumps may contain the full contents of system memory at the time of the crash. As the system memory may contain sensitive information, it must be protected accordingly. If there is... |
| V-226884 | Low | The kernel core dump data directory must have mode 0700 or less permissive. | Kernel core dumps may contain the full contents of system memory at the time of the crash. As the system memory may contain sensitive information, it must be protected accordingly. If the mode... |
| V-226496 | Low | All manual page files must not have extended ACLs. | If manual pages are compromised, misleading information could be inserted, causing actions that may compromise the system. |
| V-226495 | Low | Manual page files must have mode 0655 or less permissive. | If manual pages are compromised, misleading information could be inserted, causing actions that may compromise the system. |
| V-227077 | Low | The system package management tool must not automatically obtain updates. | System package management tools can obtain a list of updates and patches from a package repository and make this information available to the SA for review and action. Using a package repository... |
| V-227076 | Low | The system package management tool must cryptographically verify the authenticity of software packages during installation. | To prevent the installation of software from unauthorized sources, the system package management tool must use cryptographic algorithms to verify the packages are authentic. |
| V-227070 | Low | The system must have IEEE 1394 (Firewire) disabled unless needed. | Firewire is a common computer peripheral interface. Firewire devices may include storage devices that could be used to install malicious software on a system or exfiltrate data. |
| V-226996 | Low | The SSH client must not permit GSSAPI authentication unless needed. | GSSAPI authentication is used to provide additional authentication mechanisms to applications. Allowing GSSAPI authentication through SSH exposes the system's GSSAPI to remote hosts, increasing... |
