| V-234802 | | Vendor-packaged SUSE operating 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. Howev... |
| V-234803 | | The SUSE operating system must display the Standard Mandatory DOD Notice and Consent Banner before granting access via local console. | Display of a standardized and approved use notification before granting access to the SUSE operating system ensures privacy and security notification ... |
| V-234805 | | The SUSE operating system must display the Standard Mandatory DOD Notice and Consent Banner before granting access via SSH. | Display of a standardized and approved use notification before granting access to the SUSE operating system ensures privacy and security notification ... |
| V-234806 | | The SUSE operating system must display the Standard Mandatory DoD Notice and Consent Banner until users acknowledge the usage conditions and take explicit actions to log on for further access to the local graphical user interface (GUI). | The SUSE operating system must display the Standard Mandatory DoD Notice and Consent Banner until users acknowledge the usage conditions and take expl... |
| V-234807 | | The SUSE operating system file /etc/gdm/banner must contain the Standard Mandatory DoD Notice and Consent banner text. | The banner must be acknowledged by the user prior to allowing the user access to the SUSE operating system. This provides assurance that the user has ... |
| V-234808 | | The SUSE operating system must display a banner before granting local or remote access to the system via a graphical user logon. | Display of a standardized and approved use notification before granting access to the SUSE operating system ensures privacy and security notification ... |
| V-234809 | | The SUSE operating system must display the approved Standard Mandatory DoD Notice before granting local or remote access to the system via a graphical user logon. | Display of a standardized and approved use notification before granting access to the SUSE operating system ensures privacy and security notification ... |
| V-234810 | | The SUSE operating system must be able to lock the graphical user interface (GUI). | A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but do... |
| V-234812 | | The SUSE operating system must initiate a session lock after a 15-minute period of inactivity for the graphical user interface (GUI). | A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information syst... |
| V-234813 | | The SUSE operating system must initiate a session lock after a 10-minute period of inactivity. | A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information syst... |
| V-234815 | | The SUSE operating system must log SSH connection attempts and failures to the server. | Remote access services, such as those providing remote access to network devices and information systems, which lack automated monitoring capabilities... |
| V-234816 | | The SUSE operating system must implement DOD-approved encryption to protect the confidentiality of SSH remote connections. | Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session.
Remote ... |
| V-234817 | | The SUSE operating system, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. | Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly tru... |
| V-234821 | | The SUSE operating system must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services as defined in the Ports, Protocols, and Services Management (PPSM) Category Assignments List (CAL) and vulnerability assessments. | To prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within d... |
| V-234822 | | The SUSE operating system must not have duplicate User IDs (UIDs) for interactive users. | To ensure accountability and prevent unauthenticated access, interactive users must be identified and authenticated to prevent potential misuse and co... |
| V-234823 | | The SUSE operating system must disable the file system automounter unless required. | Automatically mounting file systems permits easy introduction of unknown devices, thereby facilitating malicious activity.
Satisfies: SRG-OS-000114-G... |
| V-234825 | | The SUSE operating system must employ FIPS 140-2 approved cryptographic hashing algorithm for system authentication (login.defs). | Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied on to provide confi... |
| V-234826 | | The SUSE operating system SSH daemon must be configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms. | Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Remote access (e.g., RDP) is access ... |
| V-234827 | | The SUSE operating system SSH daemon must be configured with a timeout interval. | Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management se... |
| V-234828 | | The sticky bit must be set on all SUSE operating system world-writable directories. | Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the a... |
| V-234829 | | The SUSE operating system must be configured to use TCP syncookies. | Denial of Service (DoS) is a condition in which a resource is not available for legitimate users. When this occurs, the organization either cannot acc... |
| V-234830 | | The SUSE operating system, for all network connections associated with SSH traffic, must immediately terminate at the end of the session or after 10 minutes of inactivity. | Automatic session termination addresses the termination of user-initiated logical sessions in contrast to the termination of network connections assoc... |
| V-234832 | | The SUSE operating system must generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries. | Any operating system providing too much information in error messages risks compromising the data and security of the structure, and content of error ... |
| V-234833 | | The SUSE operating system must prevent unauthorized users from accessing system error messages. | Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational st... |
| V-234834 | | The SUSE operating system library files must have mode 0755 or less permissive. | If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing ... |
| V-234835 | | The SUSE operating system library directories must have mode 0755 or less permissive. | If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing ... |
| V-234836 | | The SUSE operating system library files must be owned by root. | If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing ... |
| V-234837 | | The SUSE operating system library directories must be owned by root. | If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing ... |
| V-234838 | | The SUSE operating system library files must be group-owned by root. | If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing ... |
| V-234839 | | The SUSE operating system library directories must be group-owned by root. | If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing ... |
| V-234840 | | The SUSE operating system must have system commands set to a mode of 0755 or less permissive. | If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing ... |
| V-234841 | | The SUSE operating system must have directories that contain system commands set to a mode of 0755 or less permissive. | If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing ... |
| V-234842 | | The SUSE operating system must have system commands owned by root. | If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing ... |
| V-234843 | | The SUSE operating system must have directories that contain system commands owned by root. | If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing ... |
| V-234844 | | The SUSE operating system must have system commands group-owned by root or a system account. | If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing ... |
| V-234845 | | The SUSE operating system must have directories that contain system commands group-owned by root. | If the SUSE operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing ... |
| V-234846 | | The SUSE operating system must have a firewall system installed to immediately disconnect or disable remote access to the whole operating system. | Operating system remote access functionality must have the capability to immediately disconnect current users remotely accessing the information syste... |
| V-234847 | | The SUSE operating system wireless network adapters must be disabled unless approved and documented. | Without protection of communications with wireless peripherals, confidentiality and integrity may be compromised because unprotected communications ca... |
| V-234848 | | SUSE operating system AppArmor tool must be configured to control whitelisted applications and user home directory access control. | Using a whitelist provides a configuration management method for allowing the execution of only authorized software. Using only authorized software de... |
| V-234849 | | The SUSE operating system clock must, for networked systems, be synchronized to an authoritative DOD time source at least every 24 hours. | Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular ev... |
| V-234851 | | Advanced Intrusion Detection Environment (AIDE) must verify the baseline SUSE operating system configuration at least weekly. | Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the SUSE operat... |
| V-234854 | | The SUSE operating system must have the packages required for multifactor authentication to be installed. | Using an authentication device, such as a Common Access Card (CAC) or token separate from the information system, ensures that even if the information... |
| V-234855 | | The SUSE operating system must implement certificate status checking for multifactor authentication. | Using an authentication device, such as a Common Access Card (CAC) or token separate from the information system, ensures credentials stored on the au... |
| V-234856 | | The SUSE operating system must disable the USB mass storage kernel module. | Without identifying devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity.
Peripherals include but are ... |
| V-234857 | | If Network Security Services (NSS) is being used by the SUSE operating system it must prohibit the use of cached authentications after one day. | If cached authentication information is out of date, the validity of the authentication information may be questionable.... |
| V-234858 | | The SUSE operating system must configure the Linux Pluggable Authentication Modules (PAM) to prohibit the use of cached offline authentications after one day. | If cached authentication information is out of date, the validity of the authentication information may be questionable.... |
| V-234861 | | The SUSE operating system must implement kptr-restrict to prevent the leaking of internal kernel addresses. | Some adversaries launch attacks with the intent of executing code in nonexecutable regions of memory or in memory locations that are prohibited. Secur... |
| V-234862 | | Address space layout randomization (ASLR) must be implemented by the SUSE operating system to protect memory from unauthorized code execution. | Some adversaries launch attacks with the intent of executing code in nonexecutable regions of memory or in memory locations that are prohibited. Secur... |
| V-234863 | | The SUSE operating system must remove all outdated software components after updated versions have been installed. | Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by advers... |
| V-234864 | | The SUSE operating system must notify the System Administrator (SA) when Advanced Intrusion Detection Environment (AIDE) discovers anomalies in the operation of any security functions. | If anomalies are not acted on, security functions may fail to secure the system.
Security function is defined as the hardware, software, and/or firm... |
| V-234865 | | The SUSE operating system must off-load rsyslog messages for networked systems in real time and off-load standalone systems at least weekly. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information s... |
| V-234866 | | The SUSE operating system must provision temporary accounts with an expiration date for 72 hours. | If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To ... |
| V-234867 | | The SUSE operating system must lock an account after three consecutive invalid access attempts. | By limiting the number of failed access attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing,... |
| V-234869 | | The SUSE operating system must implement multifactor authentication for access to privileged accounts via pluggable authentication modules (PAM). | Using an authentication device, such as a Common Access Card (CAC) or token that is separate from the information system, ensures that even if the inf... |
| V-234870 | | The SUSE operating system must deny direct logons to the root account using remote access via SSH. | To ensure individual accountability and prevent unauthorized access, organizational users must be individually identified and authenticated.
A group ... |
| V-234871 | | The SUSE operating system must disable account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity after password expiration. | Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected ac... |
| V-234872 | | The SUSE operating system must never automatically remove or disable emergency administrator accounts. | Emergency accounts are privileged accounts that are established in response to crisis situations where the need for rapid account activation is requir... |
| V-234874 | | The SUSE operating system must not have unnecessary accounts. | Accounts providing no operational purpose provide additional opportunities for system compromise. Unnecessary accounts include user accounts for indiv... |
| V-234875 | | The SUSE operating system must not have unnecessary account capabilities. | Accounts providing no operational purpose provide additional opportunities for system compromise. Therefore all necessary non interactive accounts sho... |
| V-234877 | | The SUSE operating system must restrict privilege elevation to authorized personnel. | The sudo command allows a user to execute programs with elevated (administrator) privileges. It prompts the user for their password and confirms your ... |
| V-234878 | | The SUSE operating system must require reauthentication when using the "sudo" command. | Without reauthentication, users may access resources or perform tasks for which they do not have authorization.
When operating systems provide the c... |
| V-234879 | | The SUSE operating system must use the invoking user's password for privilege escalation when using "sudo". | The sudoers security policy requires that users authenticate themselves before they can use sudo. When sudoers requires authentication, it validates t... |
| V-234880 | | All SUSE operating system local interactive user accounts, upon creation, must be assigned a home directory. | If local interactive users are not assigned a valid home directory, there is no place for the storage and control of files they should own.... |
| V-234881 | | The SUSE operating system must display the date and time of the last successful account logon upon an SSH logon. | Providing users with feedback on when account accesses via SSH last occurred facilitates user recognition and reporting of unauthorized account use.... |
| V-234882 | | The SUSE operating system must enforce passwords that contain at least one uppercase character. | Use of a complex password helps increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of... |
| V-234883 | | The SUSE operating system must enforce passwords that contain at least one lowercase character. | Use of a complex password helps increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of... |
| V-234884 | | The SUSE operating system must enforce passwords that contain at least one numeric character. | Use of a complex password helps increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of... |
| V-234885 | | The SUSE operating system must require the change of at least eight of the total number of characters when passwords are changed. | If the SUSE operating system allows the user to consecutively reuse extensive portions of passwords, this increases the chances of password compromise... |
| V-234886 | | The SUSE operating system must configure the Linux Pluggable Authentication Modules (PAM) to only store encrypted representations of passwords. | Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can ... |
| V-234887 | | The SUSE operating system must employ FIPS 140-2-approved cryptographic hashing algorithms for all stored passwords. | The system must use a strong hashing algorithm to store the password. The system must use a sufficient number of hashing rounds to ensure the required... |
| V-234888 | | The SUSE operating system must employ FIPS 140-3 approved cryptographic hashing algorithms for all stored passwords. | The system must use a strong hashing algorithm to store the password. The system must use a sufficient number of hashing rounds to ensure the required... |
| V-234889 | | The SUSE operating system must be configured to create or update passwords with a minimum lifetime of 24 hours (one day). | Enforcing a minimum password lifetime helps prevent repeated password changes to defeat the password reuse or history enforcement requirement. If user... |
| V-234890 | | The SUSE operating system must employ user passwords with a minimum lifetime of 24 hours (one day). | Enforcing a minimum password lifetime helps prevent repeated password changes to defeat the password reuse or history enforcement requirement. If user... |
| V-234891 | | The SUSE operating system must be configured to create or update passwords with a maximum lifetime of 60 days. | Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If the SUSE operating system doe... |
| V-234892 | | The SUSE operating system must employ user passwords with a maximum lifetime of 60 days. | Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If the SUSE operating system doe... |
| V-234895 | | The SUSE operating system must employ passwords with a minimum of 15 characters. | The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised.
Password complexit... |
| V-234896 | | The SUSE operating system must enforce passwords that contain at least one special character. | Use of a complex password helps increase the time and resources required to compromise the password. Password complexity or strength is a measure of t... |
| V-234897 | | The SUSE operating system must prevent the use of dictionary words for passwords. | If the SUSE operating system allows the user to select passwords based on dictionary words, this increases the chances of password compromise by incre... |
| V-234899 | | The SUSE operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/passwd. | Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way t... |
| V-234900 | | The SUSE operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/group. | Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way t... |
| V-234901 | | The SUSE operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow. | Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way t... |
| V-234902 | | The SUSE operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/security/opasswd. | Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way t... |
| V-234903 | | The SUSE operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/gshadow. | Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way t... |
| V-234904 | | SUSE operating system audit records must contain information to establish what type of events occurred, the source of events, where events occurred, and the outcome of events. | Without establishing what type of events occurred, the source of events, where events occurred, and the outcome of events, it would be difficult to es... |
| V-234906 | | The SUSE operating system must generate audit records for all uses of the passwd command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-234910 | | The SUSE operating system must generate audit records for all uses of the unix_chkpwd or unix2_chkpwd commands. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234911 | | The SUSE operating system must generate audit records for all uses of the chage command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234912 | | The SUSE operating system must generate audit records for all uses of the crontab command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234913 | | The SUSE operating system must audit all uses of the sudoers file and all files in the /etc/sudoers.d/ directory. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-234914 | | The SUSE operating system must generate audit records for all uses of the creat, open, openat, open_by_handle_at, truncate, and ftruncate system calls. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234918 | | The SUSE operating system must generate audit records for all uses of the setxattr, fsetxattr, lsetxattr, removexattr, fremovexattr, and lremovexattr system calls. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234924 | | The SUSE operating system must generate audit records for all uses of the chown, fchown, fchownat, and lchown system calls. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234928 | | The SUSE operating system must generate audit records for all uses of the chmod, fchmod, and fchmodat system calls. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234932 | | The SUSE operating system must generate audit records for all uses of the sudoedit command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234937 | | The SUSE operating system must generate audit records for all uses of the insmod command. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or... |
| V-234938 | | The SUSE operating system must generate audit records for all uses of the rmmod command. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or... |
| V-234939 | | The SUSE operating system must generate audit records for all uses of the modprobe command. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or... |
| V-234940 | | The SUSE operating system must generate audit records for all uses of the kmod command. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or... |
| V-234941 | | The SUSE operating system must generate audit records for all uses of the chmod command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234942 | | The SUSE operating system must generate audit records for all uses of the setfacl command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234943 | | The SUSE operating system must generate audit records for all uses of the chacl command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234944 | | The SUSE operating system must generate audit records for all uses of the chcon command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234945 | | The SUSE operating system must generate audit records for all uses of the rm command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234946 | | The SUSE operating system must generate audit records for all modifications to the tallylog file must generate an audit record. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234947 | | The SUSE operating system must generate audit records for all modifications to the lastlog file. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234948 | | The SUSE operating system must generate audit records for all uses of the passmass command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234949 | | The SUSE operating system must generate audit records for all uses of the usermod command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234950 | | The SUSE operating system must generate audit records for all uses of the pam_timestamp_check command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234951 | | The SUSE operating system must generate audit records for all uses of the delete_module system call. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234952 | | The SUSE operating system must generate audit records for all uses of the init_module and finit_module system calls. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234954 | | The SUSE operating system must generate audit records for all uses of the su command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234956 | | The Information System Security Officer (ISSO) and System Administrator (SA), at a minimum, must be alerted of a SUSE operating system audit processing failure event. | It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notificatio... |
| V-234957 | | The Information System Security Officer (ISSO) and System Administrator (SA), at a minimum, must have mail aliases to be notified of a SUSE operating system audit processing failure. | It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notificatio... |
| V-234958 | | The SUSE operating system audit system must take appropriate action when the audit storage volume is full. | It is critical that when the SUSE operating system is at risk of failing to process audit logs as required, it takes action to mitigate the failure. A... |
| V-234959 | | The SUSE operating system must protect audit rules from unauthorized modification. | Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the ... |
| V-234961 | | The SUSE operating system audit tools must have the proper permissions configured to protect against unauthorized access. | Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tool... |
| V-234962 | | The SUSE operating system file integrity tool must be configured to protect the integrity of the audit tools. | Protecting the integrity of the tools used for auditing purposes is a critical step toward ensuring the integrity of audit information. Audit informat... |
| V-234964 | | The SUSE operating system must have the auditing package installed. | Without establishing what type of events occurred, the source of events, where events occurred, and the outcome of events, it would be difficult to es... |
| V-234965 | | The SUSE operating system must allocate audit record storage capacity to store at least one week of audit records when audit records are not immediately sent to a central audit record storage facility. | To ensure SUSE operating systems have a sufficient storage capacity in which to write the audit logs, SUSE operating systems need to be able to alloca... |
| V-234966 | | The audit-audispd-plugins must be installed on the SUSE operating system. | The audit-audispd-plugins must be installed on the SUSE operating system.... |
| V-234969 | | The SUSE operating system auditd service must notify the System Administrator (SA) and Information System Security Officer (ISSO) immediately when audit storage capacity is 75 percent full. | If security personnel are not notified immediately when storage volume reaches 75 percent utilization, they are unable to plan for audit record storag... |
| V-234973 | | The SUSE operating system must generate audit records for all uses of the unlink, unlinkat, rename, renameat, and rmdir system calls. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234975 | | The SUSE operating system must generate audit records for the /run/utmp file. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234976 | | The SUSE operating system must generate audit records for the /var/log/wtmp file. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234977 | | The SUSE operating system must generate audit records for the /var/log/btmp file. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-234978 | | The SUSE operating system must off-load audit records onto a different system or media from the system being audited. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information s... |
| V-234979 | | Audispd must take appropriate action when the SUSE operating system audit storage is full. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information s... |
| V-234981 | | The SUSE operating system must not disable syscall auditing. | By default, the SUSE operating system includes the "-a task,never" audit rule as a default. This rule suppresses syscall auditing for all tasks starte... |
| V-234982 | | The SUSE operating system must enforce a delay of at least four seconds between logon prompts following a failed logon attempt. | Limiting the number of logon attempts over a certain time interval reduces the chances that an unauthorized user may gain access to an account.... |
| V-234983 | | The SUSE operating system must enforce a delay of at least four seconds between logon prompts following a failed logon attempt. | The SUSE operating system must enforce a delay of at least four seconds between logon prompts following a failed logon attempt.... |
| V-234991 | | All SUSE operating system local interactive users must have a home directory assigned in the /etc/passwd file. | If local interactive users are not assigned a valid home directory, there is no place for the storage and control of files they should own.... |
| V-234992 | | All SUSE operating system local interactive user home directories defined in the /etc/passwd file must exist. | If a local interactive user has a home directory defined that does not exist, the user may be given access to the / directory as the current working d... |
| V-234993 | | All SUSE operating system local interactive user home directories must have mode 0750 or less permissive. | Excessive permissions on local interactive user home directories may allow unauthorized access to user files by other users.... |
| V-234994 | | All SUSE operating system local interactive user home directories must be group-owned by the home directory owner's primary group. | If the Group Identifier (GID) of a local interactive user’s home directory is not the same as the primary GID of the user, this would allow unauthoriz... |
| V-234995 | | All SUSE operating system local initialization files must have mode 0740 or less permissive. | Local initialization files are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accou... |
| V-234996 | | All SUSE operating system local interactive user initialization files executable search paths must contain only paths that resolve to the users home directory. | The executable search path (typically the PATH environment variable) contains a list of directories for the shell to search to find executables. If th... |
| V-234997 | | All SUSE operating system local initialization files must not execute world-writable programs. | If user start-up files execute world-writable programs, especially in unprotected directories, they could be maliciously modified to destroy user file... |
| V-234998 | | SUSE operating system file systems that contain user home directories must be mounted to prevent files with the setuid and setgid bit set from being executed. | The "nosuid" mount option causes the system to not execute setuid and setgid files with owner privileges. This option must be used for mounting any fi... |
| V-234999 | | SUSE operating system file systems that are used with removable media must be mounted to prevent files with the setuid and setgid bit set from being executed. | The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting an... |
| V-235000 | | SUSE operating system file systems that are being imported via Network File System (NFS) must be mounted to prevent files with the setuid and setgid bit set from being executed. | The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting an... |
| V-235001 | | SUSE operating system file systems that are being imported via Network File System (NFS) must be mounted to prevent binary files from being executed. | The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved... |
| V-235002 | | All SUSE operating system world-writable directories must be group-owned by root, sys, bin, or an application group. | If a world-writable directory has the sticky bit set and is not group-owned by a privileged Group Identifier (GID), unauthorized users may be able to ... |
| V-235003 | | SUSE operating system 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... |
| V-235006 | | The SUSE operating system must be configured to not overwrite Pluggable Authentication Modules (PAM) configuration on package changes. | The "pam-config" command line utility automatically generates a system PAM configuration as packages are installed, updated, or removed from the syste... |
| V-235007 | | The SUSE operating system SSH daemon must be configured to not allow authentication using known hosts authentication. | Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misc... |
| V-235008 | | The SUSE operating system SSH daemon 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-235009 | | The SUSE operating system SSH daemon private host key files must have mode 0640 or less permissive. | If an unauthorized user obtains the private SSH host key file, the host could be impersonated.... |
| V-235010 | | The SUSE operating system 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 on to the system as another user.... |
| V-235013 | | The SUSE operating system SSH daemon must disable forwarded remote X connections for interactive users, unless to fulfill documented and validated mission requirements. | The security risk of using X11 forwarding is that the client's X11 display server may be exposed to attack when the SSH client requests forwarding. A ... |
| V-235014 | | The SUSE operating system must not forward Internet Protocol version 4 (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, ... |
| V-235015 | | The SUSE operating system must not forward Internet Protocol version 6 (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, ... |
| V-235016 | | The SUSE operating system must not forward Internet Protocol version 4 (IPv4) source-routed packets by default. | 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, ... |
| V-235017 | | The SUSE operating system must not forward Internet Protocol version 6 (IPv6) source-routed packets by default. | 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, ... |
| V-235018 | | The SUSE operating system must prevent Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages from being accepted. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the hos... |
| V-235019 | | The SUSE operating system must not allow interfaces to accept Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages by default. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the hos... |
| V-235020 | | The SUSE operating system must prevent Internet Protocol version 6 (IPv6) Internet Control Message Protocol (ICMP) redirect messages from being accepted. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the hos... |
| V-235021 | | The SUSE operating system must not allow interfaces to accept Internet Protocol version 6 (IPv6) Internet Control Message Protocol (ICMP) redirect messages by default. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the hos... |
| V-235022 | | The SUSE operating system must not allow interfaces to send Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages by default. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain inform... |
| V-235023 | | The SUSE operating system must not send Internet Protocol version 4 (IPv4) Internet Control Message Protocol (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 inform... |
| V-235024 | | The SUSE operating system must not be performing Internet Protocol version 4 (IPv4) packet forwarding 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 ... |
| V-235025 | | The SUSE operating system must not be performing Internet Protocol version 6 (IPv6) packet forwarding 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 ... |
| V-235026 | | The SUSE operating system must not be performing Internet Protocol version 6 (IPv6) packet forwarding by default 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 ... |
| V-235027 | | The SUSE operating system must not have network interfaces in promiscuous mode unless approved and documented. | Network interfaces in promiscuous mode allow for the capture of all network traffic visible to the system. If unauthorized individuals can access thes... |
| V-235028 | | All SUSE operating system files and directories must have a valid owner. | Unowned files and directories may be unintentionally inherited if a user is assigned the same User Identifier (UID) as the UID of the unowned files.... |
| V-235029 | | All SUSE operating system 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 Group Identifier (GID) as the GID of the files with... |
| V-235030 | | The SUSE operating system default permissions must be defined in such a way that all authenticated users can only read and modify their own files. | Setting the most restrictive default permissions ensures that when new accounts are created, they do not have unnecessary access.... |
| V-251723 | | The SUSE operating system must specify the default "include" directory for the /etc/sudoers file. | The "sudo" command allows authorized users to run programs (including shells) as other users, system users, and root. The "/etc/sudoers" file is used ... |
| V-251724 | | The SUSE operating system must not be configured to bypass password requirements for privilege escalation. | Without re-authentication, users may access resources or perform tasks for which they do not have authorization.
When operating systems provide the ... |
| V-255920 | | The SUSE operating system SSH server must be configured to use only FIPS-validated key exchange algorithms. | Without cryptographic integrity protections provided by FIPS-validated cryptographic algorithms, information can be viewed and altered by unauthorized... |
| V-255922 | | The SUSE operating system must use a file integrity tool to verify correct operation of all security functions. | Without verification of the security functions, security functions may not operate correctly, and the failure may go unnoticed. Security function is d... |
| V-256982 | | The SUSE operating system must automatically expire temporary accounts within 72 hours. | Temporary accounts are privileged or nonprivileged accounts that are established during pressing circumstances, such as new software or hardware confi... |
| V-256983 | | The SUSE operating system must be configured to allow sending email notifications of unauthorized configuration changes to designated personnel. | Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the operating s... |
| V-274879 | | The SUSE operating system must audit any script or executable called by cron as root or by any privileged user. | Any script or executable called by cron as root or by any privileged user must be owned by that user, must have the permissions 755 or more restrictiv... |
| V-234811 | | The SUSE operating system must utilize vlock to allow for session locking. | A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but do... |
| V-234814 | | The SUSE operating system must conceal, via the session lock, information previously visible on the display with a publicly viewable image in the graphical user interface (GUI). | A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but do... |
| V-234850 | | The SUSE operating system must be configured to use Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). | If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis.
Time stamps generate... |
| V-234868 | | The SUSE operating system must limit the number of concurrent sessions to 10 for all accounts and/or account types. | SUSE operating system management includes the ability to control the number of users and user sessions that utilize a SUSE operating system. Limiting ... |
| V-234873 | | The SUSE operating system must display the date and time of the last successful account logon upon logon. | Providing users with feedback on when account accesses last occurred facilitates user recognition and reporting of unauthorized account use.... |
| V-234905 | | The SUSE operating system must generate audit records for all uses of the ssh-keysign command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-234907 | | The SUSE operating system must generate audit records for all uses of the gpasswd command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-234908 | | The SUSE operating system must generate audit records for all uses of the newgrp command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-234909 | | The SUSE operating system must generate audit records for a uses of the chsh command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-234933 | | The SUSE operating system must generate audit records for all uses of the chfn command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-234934 | | The SUSE operating system must generate audit records for all uses of the mount system call. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-234935 | | The SUSE operating system must generate audit records for all uses of the umount system call. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-234936 | | The SUSE operating system must generate audit records for all uses of the ssh-agent command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-234955 | | The SUSE operating system must generate audit records for all uses of the sudo command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-234963 | | The SUSE operating system must generate audit records for all uses of the privileged functions. | Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromise... |
| V-234967 | | The SUSE operating system audit event multiplexor must be configured to use Kerberos. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Allowing devices and users to connect to or from... |
| V-234968 | | Audispd must off-load audit records onto a different system or media from the SUSE operating system being audited. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information s... |
| V-234980 | | The SUSE operating 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-234986 | | The SUSE operating system file integrity tool must be configured to verify Access Control Lists (ACLs). | ACLs can provide permissions beyond those permitted through the file mode and must be verified by file integrity tools.... |
| V-234987 | | The SUSE operating system 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-235004 | | A separate file system must be used for SUSE operating system user home directories (such as /home or an 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-235005 | | The SUSE operating system must use a separate file system for /var. | 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-255921 | | The SUSE operating system must restrict access to the kernel message buffer. | Restricting access to the kernel message buffer limits access only to root. This prevents attackers from gaining additional system information as a no... |
| V-234800 | | The SUSE operating system must be a vendor-supported release. | A SUSE operating system release is considered "supported" if the vendor continues to provide security patches for the product. With an unsupported rel... |
| V-234804 | | The SUSE operating system must not have the vsftpd package installed if not required for operational support. | It is detrimental for SUSE operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unne... |
| V-234818 | | The SUSE operating system must not have the telnet-server package installed. | It is detrimental for SUSE operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unne... |
| V-234819 | | SUSE operating systems with a basic input/output system (BIOS) must require authentication upon booting into single-user and maintenance modes. | To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD syst... |
| V-234820 | | SUSE operating systems with Unified Extensible Firmware Interface (UEFI) implemented must require authentication upon booting into single-user mode and maintenance. | If the system allows a user to boot into single-user or maintenance mode without authentication, any user that invokes single-user or maintenance mode... |
| V-234831 | | All SUSE operating system persistent disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at-rest protection. | SUSE operating systems handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and mo... |
| V-234852 | | The SUSE operating system tool zypper must have gpgcheck enabled. | Changes to any software components can have significant effects on the overall security of the SUSE operating system. This requirement ensures the sof... |
| V-234853 | | The SUSE operating system must reauthenticate users when changing authenticators, roles, or escalating privileges. | Without reauthentication, users may access resources or perform tasks for which they do not have authorization.
When the SUSE operating system provi... |
| V-234859 | | FIPS 140-2 mode must be enabled on the SUSE operating system. | Use of weak or untested encryption algorithms undermines the purposes of using encryption to protect data. The SUSE operating system must implement cr... |
| V-234860 | | All networked SUSE operating systems must have and implement SSH to protect the confidentiality and integrity of transmitted and received information, as well as information during preparation for transmission. | Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercep... |
| V-234876 | | The SUSE operating system root account must be the only account with unrestricted access to the system. | If an account other than root also has a User Identifier (UID) of "0", it has root authority, giving that account unrestricted access to the entire SU... |
| V-234898 | | The SUSE operating system must not be configured to allow blank or null passwords. | Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can ... |
| V-234984 | | There must be no .shosts files on the SUSE operating system. | The .shosts files are used to configure host-based authentication for individual users or the system via SSH. Host-based authentication is not suffici... |
| V-234985 | | There must be no shosts.equiv files on the SUSE operating system. | The shosts.equiv files are used to configure host-based authentication for the system via SSH. Host-based authentication is not sufficient for prevent... |
| V-234988 | | The SUSE operating system must disable the x86 Ctrl-Alt-Delete key sequence. | A locally logged-on user, who presses Ctrl-Alt-Delete when at the console, can reboot the system. If accidentally pressed, as could happen in the case... |
| V-234989 | | The SUSE operating system must disable the x86 Ctrl-Alt-Delete key sequence for Graphical User Interfaces. | A locally logged-on user, who presses Ctrl-Alt-Delete when at the console, can reboot the system. If accidentally pressed, as could happen in the case... |
| V-234990 | | The SUSE operating system must disable the systemd Ctrl-Alt-Delete burst key sequence. | A locally logged-on user, who presses Ctrl-Alt-Delete when at the console, can reboot the system. If accidentally pressed, as could happen in the case... |
| V-235031 | | The SUSE operating system must not allow unattended or automatic logon via the graphical user interface (GUI). | Failure to restrict system access to authenticated users negatively impacts SUSE operating system security.... |
| V-235032 | | The SUSE operating system must not allow unattended or automatic logon via SSH. | Failure to restrict system access via SSH to authenticated users negatively impacts SUSE operating system security.... |
| V-251725 | | The SUSE operating system must not have accounts configured with blank or null passwords. | If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords should ne... |
