| V-252930 | | TOSS must prevent the installation of patches, service packs, device drivers, or operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization. | Changes to any software components can have significant effects on the overall security of the operating system. This requirement ensures the software... |
| V-252937 | | The root account must be the only account having unrestricted access to the TOSS 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 op... |
| V-252938 | | The systemd Ctrl-Alt-Delete burst key sequence in TOSS must be disabled. | 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 o... |
| V-252940 | | TOSS must not allow blank or null passwords in the system-auth file. | 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... |
| V-252945 | | TOSS must not allow an unattended or automatic logon to the system. | Failure to restrict system access to authenticated users negatively impacts operating system security.... |
| V-252963 | | The x86 Ctrl-Alt-Delete key sequence in TOSS must be disabled if a graphical user interface is installed. | 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-252966 | | TOSS must not allow 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... |
| V-253059 | | TOSS must implement NIST FIPS-validated cryptography for the following: to provision digital signatures; to generate cryptographic hashes; and to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. | Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The operating system must implement cry... |
| V-253098 | | A File Transfer Protocol (FTP) server package must not be installed unless mission essential on TOSS. | The FTP service provides an unencrypted remote access that does not provide for the confidentiality and integrity of user passwords or the remote sess... |
| V-253109 | | The x86 Ctrl-Alt-Delete key sequence must be disabled on TOSS. | 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-253110 | | TOSS must be a vendor-supported release. | An operating system release is considered "supported" if the vendor continues to provide security patches for the product. With an unsupported release... |
| V-253122 | | TOSS must not allow blank or null passwords in the password-auth file. | 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... |
| V-252911 | | TOSS must display the Standard Mandatory DoD Notice and Consent Banner or equivalent US Government Agency Notice and Consent Banner before granting local or remote access to the system. | Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbi... |
| V-252912 | | TOSS, 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-252913 | | TOSS, for PKI-based authentication, must enforce authorized access to the corresponding private key. | If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure.
Th... |
| V-252914 | | TOSS must require authentication upon booting into emergency or rescue 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-252915 | | TOSS must not permit direct logons to the root account using remote access from outside of the system via SSH. | Even though the communications channel may be encrypted, an additional layer of security is gained by extending the policy of not logging on directly ... |
| V-252916 | | The TOSS file system automounter must be disabled unless required. | Automatically mounting file systems permits easy introduction of unknown devices, thereby facilitating malicious activity.... |
| V-252917 | | The TOSS pam_unix.so module must be configured in the password-auth file to use a FIPS 140-2-approved cryptographic hashing algorithm for system authentication. | Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide con... |
| V-252918 | | The TOSS pam_unix.so module must be configured in the system-auth file to use a FIPS 140-2-approved cryptographic hashing algorithm for system authentication. | Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide con... |
| V-252919 | | The TOSS operating system must implement DoD-approved encryption in the OpenSSL package. | Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Remote access (e.g., RDP) is access ... |
| V-252920 | | TOSS must use a Linux Security Module configured to enforce limits on system services. | An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions.
Sec... |
| V-252921 | | TOSS must prevent unauthorized and unintended information transfer via shared system resources. | Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the a... |
| V-252922 | | The TOSS operating system must be configured to use TCP syncookies. | Denial of Service (DoS) is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accompl... |
| V-252924 | | The TOSS operating system must implement DoD-approved encryption to protect the confidentiality of SSH connections. | Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Remote access (e.g., RDP) is access ... |
| V-252925 | | The TOSS operating system must implement DoD-approved TLS encryption in the GnuTLS package. | Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Transport Layer Security (TLS) encry... |
| V-252926 | | The TOSS SSH daemon must be configured to use only Message Authentication Codes (MACs) employing FIPS 140-2 validated cryptographic hash algorithms. | Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Remote access (e.g., RDP) is access ... |
| V-252927 | | The TOSS operating system must be configured to preserve log records from failure events. | Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure s... |
| V-252928 | | TOSS must, for networked systems, compare internal information system clocks at least every 24 hours with a server which is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DOD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS). | Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time that a particul... |
| V-252929 | | The TOSS file integrity tool must notify the system administrator when changes to the baseline configuration or anomalies in the operation of any security functions are discovered within an organizationally defined frequency. | Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the operating s... |
| V-252931 | | TOSS 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-252932 | | TOSS must have the packages required for multifactor authentication installed. | Using an authentication device, such as a DOD Common Access Card (CAC) or token that is separate from the information system, ensures that even if the... |
| V-252933 | | TOSS 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.
TOSS includes multiple optio... |
| V-252934 | | All TOSS networked 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-252935 | | For TOSS systems using Domain Name Servers (DNS) resolution, at least two name servers must be configured. | To provide availability for name resolution services, multiple redundant name servers are mandated. A failure in name resolution could lead to the fai... |
| V-252936 | | The debug-shell systemd service must be disabled on TOSS. | The debug-shell requires no authentication and provides root privileges to anyone who has physical access to the machine. While this feature is disabl... |
| V-252939 | | There must be no ".shosts" files on The TOSS 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 suffi... |
| V-252941 | | TOSS must not be performing 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-252942 | | The TOSS SSH daemon must not allow authentication using known host's 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-252943 | | The TOSS 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 ... |
| V-252944 | | The TOSS SSH daemon must not allow Kerberos authentication, except to fulfill documented and validated mission requirements. | Configuring these settings for the SSH daemon provides additional assurance that remote logon via SSH will not use unused methods of authentication, e... |
| V-252946 | | TOSS must enforce the limit of five consecutive invalid logon attempts by a user during a 15-minute time period. | By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force att... |
| V-252948 | | TOSS must retain a user's session lock until that user reestablishes access using established identification and authentication procedures. | 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-252949 | | TOSS must automatically lock graphical user sessions after 15 minutes 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-252950 | | TOSS must map the authenticated identity to the user or group account for PKI-based authentication. | Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the individual user or group will n... |
| V-252951 | | TOSS duplicate User IDs (UIDs) must not exist for interactive users. | To ensure accountability and prevent unauthenticated access, interactive users must be identified and authenticated to prevent potential misuse and co... |
| V-252952 | | TOSS must use multifactor authentication for network and local access to privileged and nonprivileged accounts. | Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased.
Multifactor authentication requires u... |
| V-252953 | | TOSS must disable account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity. | Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected ac... |
| V-252954 | | TOSS must automatically remove or disable emergency accounts after the crisis is resolved or 72 hours. | Emergency accounts are privileged accounts that are established in response to crisis situations where the need for rapid account activation is requir... |
| V-252955 | | TOSS must reveal error messages only to authorized users. | 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-252956 | | TOSS must protect wireless access to the system using authentication of users and/or devices. | Allowing devices and users to connect to the system without first authenticating them allows untrusted access and can lead to a compromise or attack.
... |
| V-252957 | | TOSS must automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes occur. | By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, ... |
| V-252958 | | TOSS must require users to reauthenticate for privilege escalation. | Without reauthentication, users may access resources or perform tasks for which they do not have authorization.
When operating systems provide the c... |
| V-252959 | | TOSS must require users to provide a password 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 c... |
| V-252960 | | All TOSS local interactive user accounts must be assigned a home directory upon creation. | 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-252961 | | All TOSS 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-252962 | | All TOSS 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-252964 | | TOSS must disable the user list at logon for graphical user interfaces. | Leaving the user list enabled is a security risk since it allows anyone with physical access to the system to enumerate known user accounts without au... |
| V-252965 | | TOSS 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-252967 | | TOSS must not have unnecessary accounts. | Accounts providing no operational purpose provide additional opportunities for system compromise. Unnecessary accounts include user accounts for indiv... |
| V-252968 | | TOSS must define default permissions for all authenticated users in such a way that the user 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-252969 | | All TOSS local interactive user home directories must have mode 0770 or less permissive. | Users' home directories/folders may contain information of a sensitive nature. Non-privileged users should coordinate any sharing of information with ... |
| V-252970 | | All TOSS local interactive user home directories must be owned by root. | Users' home directories/folders may contain information of a sensitive nature. Non-privileged users should coordinate any sharing of information with ... |
| V-252971 | | All TOSS local interactive user home directories must be owned by the user's primary group. | Users' home directories/folders may contain information of a sensitive nature. Non-privileged users should coordinate any sharing of information with ... |
| V-252972 | | TOSS must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow. | Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomp... |
| V-252973 | | TOSS audit records must contain information to establish what type of events occurred, when the events occurred, the source of events, where events occurred, and the outcome of events. | Without establishing what type of events occurred, when events occurred, the source of events, where events occurred, and the outcome of events, it wo... |
| V-252974 | | TOSS must generate audit records containing the full-text recording of privileged commands. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-252975 | | TOSS must alert the ISSO and SA (at a minimum) in the event of an 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-252976 | | TOSS must take appropriate action when an audit processing failure occurs. | It is critical that when the operating system is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit ... |
| V-252977 | | TOSS audit logs must have a mode of 0600 or less permissive to prevent unauthorized read access. | Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
Audit informat... |
| V-252978 | | TOSS audit log directory must have a mode of 0700 or less permissive to prevent unauthorized read access. | Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
Audit informat... |
| V-252979 | | TOSS audit logs must be owned by user root to prevent unauthorized read access. | Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
Audit informat... |
| V-252980 | | TOSS audit logs must be owned by group root to prevent unauthorized read access. | Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
Audit informat... |
| V-252981 | | TOSS audit log directory must be owned by user root to prevent unauthorized read access. | Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
Audit informat... |
| V-252982 | | TOSS audit log directory must be owned by group root to prevent unauthorized read access. | Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
Audit informat... |
| V-252983 | | The TOSS audit system must protect auditing rules from unauthorized change. | Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
Audit informat... |
| V-252984 | | The TOSS audit system must protect logon UIDs from unauthorized change. | Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.
Audit informat... |
| V-252985 | | Successful/unsuccessful uses of the "chage" command in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-252986 | | Successful/unsuccessful uses of the "chcon" command in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-252987 | | Successful/unsuccessful uses of the ssh-agent in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-252988 | | Successful/unsuccessful uses of the "passwd" command in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-252989 | | Successful/unsuccessful uses of postdrop in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-252990 | | Successful/unsuccessful uses of postqueue in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-252991 | | Successful/unsuccessful uses of setsebool in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-252992 | | Successful/unsuccessful uses of the ssh-keysign in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-252993 | | Successful/unsuccessful uses of the "setfacl" command in RTOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-252994 | | Successful/unsuccessful uses of the "pam_timestamp_check" command in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-252995 | | Successful/unsuccessful uses of the "newgrp" command in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-252996 | | Successful/unsuccessful uses of the "init_module" command in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-252997 | | Successful/unsuccessful uses of the "rename" command in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-252998 | | Successful/unsuccessful uses of the "renameat" command in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-252999 | | Successful/unsuccessful uses of the "rmdir" command in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253000 | | Successful/unsuccessful uses of the "unlink" command in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253001 | | Successful/unsuccessful uses of the "unlinkat" command in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253002 | | Successful/unsuccessful uses of the "finit_module" command in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253003 | | Successful/unsuccessful uses of the "delete_module" command in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253004 | | Successful/unsuccessful uses of the "crontab" command in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253005 | | Successful/unsuccessful uses of the "chsh" command in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253006 | | Successful/unsuccessful uses of setfiles in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253007 | | Successful/unsuccessful uses of the "chacl" command in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253008 | | TOSS must allow only the Information System Security Manager (ISSM) (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited. | Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the ... |
| V-253009 | | Successful/unsuccessful uses of the chmod system call in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253010 | | Successful/unsuccessful uses of the chown system call in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253011 | | Successful/unsuccessful uses of the creat system call in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253012 | | Successful/unsuccessful uses of the fchmod system call in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253013 | | Successful/unsuccessful uses of the fchmodat system call in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253014 | | Successful/unsuccessful uses of the fchown system call in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253015 | | Successful/unsuccessful uses of the fchownat system call in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253016 | | Successful/unsuccessful uses of the ftruncate system call system call in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253017 | | Successful/unsuccessful uses of the lchown system call in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253018 | | Successful/unsuccessful uses of the open system call in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253019 | | Successful/unsuccessful uses of the open_by_handle_at system call system call in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253020 | | Successful/unsuccessful uses of the openat system call in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253021 | | Successful/unsuccessful uses of the truncate system call in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253022 | | TOSS audit tools must be owned by "root". | Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tool... |
| V-253023 | | TOSS must use cryptographic mechanisms to protect the integrity of 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-253024 | | TOSS must generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group". | Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomp... |
| V-253025 | | TOSS must generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow". | Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomp... |
| V-253026 | | TOSS must generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd". | Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomp... |
| V-253027 | | TOSS must generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd". | Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomp... |
| V-253028 | | TOSS must generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers". | Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomp... |
| V-253029 | | TOSS must generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/". | Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomp... |
| V-253030 | | The TOSS audit system must prevent all software from executing at higher privilege levels than users executing the software and the audit system must be configured to audit the execution of privileged functions. | In certain situations, software applications/programs need to execute with elevated privileges to perform required functions. However, if the privileg... |
| V-253031 | | TOSS must allocate audit record storage capacity to store at least one week's worth of audit records, when audit records are not immediately sent to a central audit record storage facility. | In order to ensure TOSS systems have a sufficient storage capacity in which to write the audit logs, TOSS needs to be able to allocate audit record st... |
| V-253032 | | The TOSS audit records must be offloaded onto a different system or storage media from the system being audited. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Offloading is a common process in information sy... |
| V-253033 | | TOSS must label all off-loaded audit logs before sending them to the central log server. | 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-253034 | | The TOSS audit system must be configured to audit any usage of the "fsetxattr" system call. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253035 | | The TOSS audit system must be configured to audit any usage of the "lsetxattr" system call. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253036 | | Successful/unsuccessful uses of the fremovexattr system call in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253037 | | Successful/unsuccessful uses of the "lremovexattr" system call in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253038 | | Successful/unsuccessful uses of the "removexattr" system call in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253039 | | Successful/unsuccessful modifications to the "lastlog" file in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253040 | | Successful/unsuccessful uses of "semanage" in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253041 | | Successful/unsuccessful uses of the "gpasswd" command in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253042 | | Successful/unsuccessful uses of the "mount" command in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253043 | | Successful/unsuccessful uses of the "mount" syscall in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253044 | | Successful/unsuccessful uses of the "su" command in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253045 | | Successful/unsuccessful uses of the "umount" command in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253046 | | Successful/unsuccessful uses of the "unix_update" in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253047 | | Successful/unsuccessful uses of the "usermod" command in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253048 | | Successful/unsuccessful uses of "unix_chkpwd" in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253049 | | Successful/unsuccessful uses of "userhelper" in TOSS must generate an audit record. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-253050 | | Successful/unsuccessful uses of the "kmod" command in TOSS must generate an audit record. | "Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correla... |
| V-253051 | | The auditd service must be running in TOSS. | Configuring TOSS to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and e... |
| V-253052 | | The TOSS audit system must audit local 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-253054 | | TOSS must have the packages required for offloading audit logs installed. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Offloading is a common process in information sy... |
| V-253055 | | TOSS must have the packages required for encrypting offloaded audit logs installed. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Offloading is a common process in information sy... |
| V-253056 | | TOSS must monitor remote access methods. | Remote access services, such as those providing remote access to network devices and information systems, which lack automated monitoring capabilities... |
| V-253057 | | TOSS must force a frequent session key renegotiation for SSH connections by the client. | Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercep... |
| V-253058 | | TOSS must force a frequent session key renegotiation for SSH connections to the server. | Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercep... |
| V-253060 | | TOSS must enforce password complexity by requiring that at least one uppercase character be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-253061 | | TOSS must enforce password complexity by requiring that at least one lowercase character be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-253062 | | TOSS must enforce password complexity by requiring that at least one numeric character be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-253063 | | TOSS must require the change of at least eight characters when passwords are changed. | If the operating system allows the user to consecutively reuse extensive portions of passwords, this increases the chances of password compromise by i... |
| V-253064 | | TOSS must store only 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-253065 | | TOSS must not have the rsh-server package installed. | 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-253066 | | TOSS must enforce 24 hours/one day as the minimum password lifetime. | Enforcing a minimum password lifetime helps to prevent repeated password changes to defeat the password reuse or history enforcement requirement. If u... |
| V-253067 | | TOSS must enforce a 60-day maximum password lifetime restriction. | Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If the operating system does not... |
| V-253069 | | TOSS must enforce a minimum 15-character password length. | The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised.
Password complexit... |
| V-253070 | | TOSS must cover or disable the built-in or attached camera when not in use. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-253071 | | TOSS must disable IEEE 1394 (FireWire) Support. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-253072 | | TOSS must disable mounting of cramfs. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-253073 | | TOSS must disable network management of the chrony daemon. | Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time when a particul... |
| V-253074 | | TOSS must disable the asynchronous transfer mode (ATM) protocol. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-253075 | | TOSS must disable the controller area network (CAN) protocol. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-253076 | | TOSS must disable the stream control transmission (SCTP) protocol. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-253077 | | TOSS must disable the transparent inter-process communication (TIPC) protocol. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-253078 | | TOSS must not have any automated bug reporting tools installed. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-253079 | | TOSS must not have the sendmail package installed. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-253080 | | TOSS must not have the telnet-server package installed. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-253081 | | TOSS must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. | In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types... |
| V-253082 | | TOSS must be configured to disable USB mass storage. | USB mass storage permits easy introduction of unknown devices, thereby facilitating malicious activity.
Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-0... |
| V-253083 | | TOSS must be configured so that all network connections associated with SSH traffic are terminated at the end of the session or after 10 minutes of inactivity, except to fulfill documented and validated mission requirements. | Terminating an idle SSH session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a managemen... |
| V-253085 | | All TOSS local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at rest protection. | TOSS systems handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modificati... |
| V-253086 | | TOSS must limit privileges to change software resident within software libraries. | If the operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the a... |
| V-253087 | | TOSS must enforce password complexity by requiring that at least one special character be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity or strength is a measure o... |
| V-253088 | | A firewall must be installed on TOSS. | "Firewalld" provides an easy and effective way to block/limit remote access to the system via ports, services, and protocols.
Remote access services,... |
| V-253089 | | TOSS must take appropriate action when the internal event queue is full. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Offloading is a common process in information sy... |
| V-253090 | | TOSS must accept Personal Identity Verification (PIV) credentials. | The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access.
The DoD has mandated the use of the Common Access... |
| V-253091 | | TOSS must implement DoD-approved encryption in the OpenSSL package. | Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Remote access (e.g., RDP) is access ... |
| V-253092 | | A firewall must be able to protect against or limit the effects of Denial of Service (DoS) attacks by ensuring TOSS can implement rate-limiting measures on impacted network interfaces. | DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or m... |
| V-253093 | | TOSS must implement non-executable data to protect its memory from unauthorized code execution. | Some adversaries launch attacks with the intent of executing code in non-executable regions of memory or in memory locations that are prohibited. Secu... |
| V-253095 | | TOSS must enable the "SELinux" targeted policy. | Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. Security function is de... |
| V-253096 | | TOSS must prevent the use of dictionary words for passwords. | If TOSS allows the user to select passwords based on dictionary words, then this increases the chances of password compromise by increasing the opport... |
| V-253097 | | TOSS 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-253099 | | All TOSS local 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-253100 | | All TOSS local 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 un-owned files.... |
| V-253101 | | Cron logging must be implemented in TOSS. | 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 cr... |
| V-253102 | | If the Trivial File Transfer Protocol (TFTP) server is required, the TOSS TFTP daemon must be configured to operate in secure mode. | Restricting TFTP to a specific directory prevents remote users from copying, transferring, or overwriting system files.... |
| V-253103 | | The graphical display manager must not be installed on TOSS unless approved. | Internet services that are not required for system or application processes must not be active to decrease the attack surface of the system. Graphical... |
| V-253106 | | The TOSS 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-253107 | | The TOSS 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-253108 | | The TOSS 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-253111 | | TOSS must be configured to prevent unrestricted mail relaying. | If unrestricted mail relaying is permitted, unauthorized senders could use this host as a mail relay for the purpose of sending spam or other unauthor... |
| V-253112 | | TOSS must define default permissions for logon and non-logon shells. | The umask controls the default access mode assigned to newly created files. A umask of 077 limits new files to mode 600 or less permissive. Although u... |
| V-253113 | | TOSS must disable access to network bpf syscall from unprivileged processes. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-253114 | | TOSS must enable hardening for the Berkeley Packet Filter Just-in-time compiler. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-253115 | | TOSS must enable the hardware random number generator entropy gatherer service. | The most important characteristic of a random number generator is its randomness, namely its ability to deliver random numbers that are impossible to ... |
| V-253118 | | TOSS must ignore IPv4 Internet Control Message Protocol (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 hos... |
| V-253119 | | TOSS must ignore IPv6 Internet Control Message Protocol (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 hos... |
| V-253120 | | TOSS must not accept router advertisements on all IPv6 interfaces by default. | Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not ... |
| V-253121 | | TOSS must not accept router advertisements on all IPv6 interfaces. | Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not ... |
| V-253123 | | TOSS must not allow interfaces to perform Internet Control Message Protocol (ICMP) redirects 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-253124 | | TOSS must not forward 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-253125 | | TOSS 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, ... |
| V-253126 | | TOSS must not forward 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-253127 | | TOSS 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, ... |
| V-253128 | | TOSS must not respond to Internet Control Message Protocol (ICMP) echoes sent to a broadcast address. | Responding to broadcast ICMP echoes facilitates network mapping and provides a vector for amplification attacks.
There are notable differences betwee... |
| V-253129 | | TOSS must not send 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-253130 | | TOSS must prevent 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-253131 | | TOSS must prevent 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-253132 | | TOSS must restrict exposed kernel pointer addresses access. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-253133 | | TOSS 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 the r... |
| V-253134 | | TOSS must use reverse path filtering on all IPv4 interfaces. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-253135 | | TOSS network interfaces must not be in promiscuous mode. | Network interfaces in promiscuous mode allow for the capture of all network traffic visible to the system. If unauthorized individuals can access thes... |
| V-253136 | | TOSS must enable kernel parameters to enforce discretionary access control on symlinks. | Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should ... |
| V-253137 | | TOSS must enable kernel parameters to enforce discretionary access control on hardlinks. | Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should ... |
| V-252923 | | TOSS must display the Standard Mandatory DoD Notice and Consent Banner or equivalent US Government Agency Notice and Consent Banner before granting local or remote access to the system via a ssh logon. | Display of a standardized and approved use notification before granting access to TOSS ensures privacy and security notification verbiage used is cons... |
| V-252947 | | TOSS must limit the number of concurrent sessions to 256 for all accounts and/or account types. | Operating system management includes the ability to control the number of users and user sessions that utilize an operating system. Limiting the numbe... |
| V-253053 | | TOSS must resolve audit information before writing to disk. | 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-253084 | | TOSS must have policycoreutils package installed. | Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. Security function is de... |
| V-253094 | | YUM must remove all software components after updated versions have been installed on TOSS. | Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by advers... |
| V-253104 | | The TOSS 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.
TOSS installation media come ... |
| V-253105 | | The TOSS 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.
TOSS installation media come wit... |
| V-253116 | | TOSS must ensure the SSH server uses strong entropy. | The most important characteristic of a random number generator is its randomness, namely its ability to deliver random numbers that are impossible to ... |
| V-253117 | | TOSS must have the packages required to use the hardware random number generator entropy gatherer service. | The most important characteristic of a random number generator is its randomness, namely its ability to deliver random numbers that are impossible to ... |
