| Finding ID |
Severity |
Title |
Description |
|
V-253122
|
High |
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 never be used in operational environments. |
|
V-253110
|
High |
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, it will not be possible to resolve security issues discovered in the system software. |
|
V-253109
|
High |
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 of a mixed OS environment, this can create the risk of short-term loss of availability of systems due to unintentional reboot. In a graphical user environment,... |
|
V-253098
|
High |
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 session. If a privileged user were to log on using this service, the privileged user password could be compromised. SSH or other encrypted file transfer methods must... |
|
V-253059
|
High |
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 cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated.
TOSS utilizes GRUB 2 as the default... |
|
V-252966
|
High |
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 never be used in operational environments. |
|
V-252963
|
High |
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 of a mixed OS environment, this can create the risk of short-term loss of availability of systems due to unintentional reboot. In a graphical user environment,... |
|
V-252945
|
High |
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-252940
|
High |
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 never be used in operational environments. |
|
V-252938
|
High |
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 of a mixed OS environment, this can create the risk of short-term loss of availability of systems due to unintentional reboot. In a graphical user environment,... |
|
V-252937
|
High |
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 operating system. Multiple accounts with a UID of "0" afford an opportunity for potential intruders to guess a password for a privileged account. |
|
V-252930
|
High |
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 has not been tampered with and that it has been provided by a trusted vendor.
Accordingly, patches, service packs, device drivers, or operating system components must be signed... |
|
V-253137
|
Medium |
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 be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via... |
|
V-253136
|
Medium |
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 be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via... |
|
V-253135
|
Medium |
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 these applications, it may allow them to collect information such as logon IDs, passwords, and key exchanges between systems.
If the system is being used to perform a... |
|
V-253134
|
Medium |
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 unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Enabling reverse path filtering drops packets with... |
|
V-253133
|
Medium |
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 request to execute a command by checking a file, called sudoers. If the "sudoers" file is not configured correctly, any user defined on the system can initiate... |
|
V-253132
|
Medium |
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 unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors. |
|
V-253131
|
Medium |
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 host's route table and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle attack. |
|
V-253130
|
Medium |
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 host's route table and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle attack. |
|
V-253129
|
Medium |
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 information from the system's route table, possibly revealing portions of the network topology.
There are notable differences between Internet Protocol version 4 (IPv4) and Internet Protocol version... |
|
V-253128
|
Medium |
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 between Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6). IPv6 does not implement the same method of broadcast as IPv4. Instead, IPv6 uses multicast addressing to the all-hosts... |
|
V-253127
|
Medium |
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, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when forwarding is enabled and... |
|
V-253126
|
Medium |
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, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when forwarding is enabled and... |
|
V-253125
|
Medium |
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, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when forwarding is enabled and... |
|
V-253124
|
Medium |
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, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when forwarding is enabled and... |
|
V-253123
|
Medium |
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 information from the system's route table, possibly revealing portions of the network topology.
There are notable differences between Internet Protocol version 4 (IPv4) and Internet Protocol version... |
|
V-253121
|
Medium |
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 required, system network information may be unnecessarily transmitted across the network.
An illicit router advertisement message could result in a man-in-the-middle attack. |
|
V-253120
|
Medium |
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 required, system network information may be unnecessarily transmitted across the network.
An illicit router advertisement message could result in a man-in-the-middle attack. |
|
V-253119
|
Medium |
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 host's route table and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle attack. |
|
V-253118
|
Medium |
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 host's route table and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle attack. |
|
V-253115
|
Medium |
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 predict. Entropy in computer security is associated with the unpredictability of a source of randomness. The random source with high entropy tends to achieve a uniform distribution... |
|
V-253114
|
Medium |
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 unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Enabling hardening for the Berkeley Packet Filter... |
|
V-253113
|
Medium |
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 unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors. |
|
V-253112
|
Medium |
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 umask can be represented as a four-digit number, the first digit representing special access modes is typically ignored or required to be "0." This... |
|
V-253111
|
Medium |
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 unauthorized activity. |
|
V-253108
|
Medium |
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-253107
|
Medium |
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-253106
|
Medium |
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-253103
|
Medium |
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 display managers have a long history of security vulnerabilities and must not be used, unless approved and documented. |
|
V-253102
|
Medium |
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-253101
|
Medium |
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 cron facility by unauthorized and malicious users. |
|
V-253100
|
Medium |
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-253099
|
Medium |
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 without a valid group owner. |
|
V-253097
|
Medium |
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-253096
|
Medium |
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 opportunity for successful guesses and brute-force attacks. |
|
V-253095
|
Medium |
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 defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the... |
|
V-253093
|
Medium |
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. Security safeguards employed to protect memory include, for example, data execution prevention and address space layout randomization. Data execution prevention safeguards can be either hardware-enforced or software-enforced with... |
|
V-253092
|
Medium |
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 must operate at degraded capacity.
This requirement addresses the configuration of TOSS to mitigate the impact of DoS attacks that have occurred or are ongoing on... |
|
V-253091
|
Medium |
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 to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
Cryptographic mechanisms... |
|
V-253090
|
Medium |
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 Card (CAC) to support identity management and personal authentication for systems covered under Homeland Security Presidential Directive (HSPD) 12, as well as making the CAC a... |
|
V-253089
|
Medium |
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 systems with limited audit storage capacity.
TOSS installation media provides "rsyslogd." "rsyslogd" is a system utility providing support for message logging. Support for both internet and UNIX domain sockets... |
|
V-253088
|
Medium |
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, such as those providing remote access to network devices and information systems, which lack automated control capabilities, increase risk and make remote user access management difficult at best.... |
|
V-253087
|
Medium |
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 of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
TOSS utilizes "pwquality" as a mechanism to enforce password complexity. Note that... |
|
V-253086
|
Medium |
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 appropriate testing and approvals that are part of a robust change management process.
This requirement applies to TOSS with software libraries that are accessible and configurable,... |
|
V-253085
|
Medium |
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 modification of the information at rest.
Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the... |
|
V-253083
|
Medium |
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 management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle SSH session will also free up resources... |
|
V-253082
|
Medium |
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-000378-GPOS-00163 |
|
V-253081
|
Medium |
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 within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.
Operating systems are capable of providing a wide variety of functions and... |
|
V-253080
|
Medium |
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 unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a... |
|
V-253079
|
Medium |
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 unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a... |
|
V-253078
|
Medium |
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 unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Operating systems are capable of providing a... |
|
V-253077
|
Medium |
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 unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Failing to disconnect unused protocols can result... |
|
V-253076
|
Medium |
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 unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Failing to disconnect unused protocols can result... |
|
V-253075
|
Medium |
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 unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Failing to disconnect unused protocols can result... |
|
V-253074
|
Medium |
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 unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Failing to disconnect unused protocols can result... |
|
V-253073
|
Medium |
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 particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside the configured acceptable allowance (drift) may be inaccurate.
Not... |
|
V-253072
|
Medium |
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 unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Removing support for unneeded filesystem types reduces... |
|
V-253071
|
Medium |
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 unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
The IEEE 1394 (FireWire) is a serial... |
|
V-253070
|
Medium |
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 unnecessary capabilities or services are often overlooked and therefore may remain unsecured. They increase the risk to the platform by providing additional attack vectors.
Failing to disconnect from collaborative computing devices... |
|
V-253069
|
Medium |
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 complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that... |
|
V-253067
|
Medium |
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 limit the lifetime of passwords and force users to change their passwords, there is the risk that the operating system passwords could be compromised. |
|
V-253066
|
Medium |
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 users are allowed to immediately and continually change their password, then the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding... |
|
V-253065
|
Medium |
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 be plainly read (i.e., clear text) and easily compromised.
The rsh-server service provides an unencrypted remote access service that does not provide for the confidentiality and... |
|
V-253064
|
Medium |
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 be plainly read (i.e., clear text) and easily compromised.
Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot... |
|
V-253063
|
Medium |
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 increasing the window of opportunity for attempts at guessing and brute-force attacks.
The number of changed characters refers to the number of changes required with respect to the... |
|
V-253062
|
Medium |
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 of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that determines how long it... |
|
V-253061
|
Medium |
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 of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that determines how long it... |
|
V-253060
|
Medium |
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 of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that determines how long it... |
|
V-253058
|
Medium |
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 intercepted and either read or altered.
This requirement applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook... |
|
V-253057
|
Medium |
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 intercepted and either read or altered.
This requirement applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook... |
|
V-253056
|
Medium |
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, increase risk and make remote user access management difficult at best.
Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through... |
|
V-253055
|
Medium |
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 systems with limited audit storage capacity.
TOSS installation media provides "rsyslogd." "rsyslogd" is a system utility providing support for message logging. Support for both internet and UNIX domain sockets... |
|
V-253054
|
Medium |
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 systems with limited audit storage capacity.
TOSS installation media provides "rsyslogd." "rsyslogd" is a system utility providing support for message logging. Support for both internet and UNIX domain sockets... |
|
V-253052
|
Medium |
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 establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for... |
|
V-253051
|
Medium |
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 establishes a common security baseline across the DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed in hardware, software,... |
|
V-253050
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253049
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253048
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253047
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253046
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253045
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253044
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253043
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253042
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253041
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253040
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253039
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253038
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253037
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253036
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253035
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253034
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253033
|
Medium |
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 establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for... |
|
V-253032
|
Medium |
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 systems with limited audit storage capacity.
TOSS installation media provides "rsyslogd." "rsyslogd" is a system utility providing support for message logging. Support for both internet and UNIX domain sockets... |
|
V-253031
|
Medium |
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 storage capacity.
The task of allocating audit record storage capacity is usually performed during initial installation of TOSS.
If an external logging system... |
|
V-253030
|
Medium |
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 privileges required for execution are at a higher level than the privileges assigned to organizational users invoking such applications/programs, those users are indirectly provided with greater privileges than assigned by the organizations.... |
|
V-253029
|
Medium |
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 accomplish this is for the attacker to enable a new or disabled account. Auditing account modification actions provides logging that can be used for forensic purposes. |
|
V-253028
|
Medium |
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 accomplish this is for the attacker to enable a new or disabled account. Auditing account modification actions provides logging that can be used for forensic purposes. |
|
V-253027
|
Medium |
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 accomplish this is for the attacker to enable a new or disabled account. Auditing account modification actions provides logging that can be used for forensic purposes. |
|
V-253026
|
Medium |
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 accomplish this is for the attacker to enable a new or disabled account. Auditing account modification actions provides logging that can be used for forensic purposes. |
|
V-253025
|
Medium |
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 accomplish this is for the attacker to enable a new or disabled account. Auditing account modification actions provides logging that can be used for forensic purposes. |
|
V-253024
|
Medium |
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 accomplish this is for the attacker to enable a new or disabled account. Auditing account modification actions provides logging that can be used for forensic purposes. |
|
V-253023
|
Medium |
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 information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.
Audit tools include, but are not limited to, vendor-provided... |
|
V-253022
|
Medium |
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 tools is necessary to prevent unauthorized operation on audit information.
Operating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the... |
|
V-253021
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253020
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253019
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253018
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253017
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253016
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253015
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253014
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253013
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253012
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253011
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253010
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253009
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253008
|
Medium |
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 auditing of critical events. Misconfigured audits may degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate,... |
|
V-253007
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253006
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253005
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253004
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253003
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253002
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253001
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-253000
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-252999
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-252998
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-252997
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-252996
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-252995
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-252994
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-252993
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-252992
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-252991
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-252990
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-252989
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-252988
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-252987
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-252986
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-252985
|
Medium |
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, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-252984
|
Medium |
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 information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit TOSS system activity.
In immutable mode, unauthorized users cannot execute changes to the audit system to potentially... |
|
V-252983
|
Medium |
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 information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit TOSS system activity.
In immutable mode, unauthorized users cannot execute changes to the audit system to potentially... |
|
V-252982
|
Medium |
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 information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity.
Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029 |
|
V-252981
|
Medium |
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 information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity.
Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029 |
|
V-252980
|
Medium |
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 information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity.
Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029 |
|
V-252979
|
Medium |
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 information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity.
Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029 |
|
V-252978
|
Medium |
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 information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity.
Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029 |
|
V-252977
|
Medium |
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 information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity.
Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029 |
|
V-252976
|
Medium |
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 processing failures include: software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure... |
|
V-252975
|
Medium |
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 notification, the security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected.
Audit processing... |
|
V-252974
|
Medium |
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 organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of... |
|
V-252973
|
Medium |
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 would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this... |
|
V-252972
|
Medium |
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 accomplish this is for the attacker to modify an existing account. Auditing account modification actions provides logging that can be used for forensic purposes.
To address access... |
|
V-252971
|
Medium |
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 an SA through shared resources. |
|
V-252970
|
Medium |
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 an SA through shared resources. |
|
V-252969
|
Medium |
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 an SA through shared resources. |
|
V-252968
|
Medium |
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-252967
|
Medium |
TOSS must not have unnecessary accounts. |
Accounts providing no operational purpose provide additional opportunities for system compromise. Unnecessary accounts include user accounts for individuals not requiring access to the system and application accounts for applications not installed on the system. |
|
V-252965
|
Medium |
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-252964
|
Medium |
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 authenticated access to the system. |
|
V-252962
|
Medium |
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-252961
|
Medium |
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 unauthorized access to the user's files, and users that share the same group may not be able to access files that they legitimately should. |
|
V-252960
|
Medium |
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-252959
|
Medium |
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 capability to escalate a functional capability, it is critical the user reauthenticate. |
|
V-252958
|
Medium |
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 capability to escalate a functional capability, it is critical the user reauthenticate. |
|
V-252957
|
Medium |
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, is reduced. Limits are imposed by locking the account.
Due to the scale of HPC systems and the number of users in question, it is impractical to require... |
|
V-252956
|
Medium |
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.
Wireless technologies include, for example, microwave, packet radio (UHF/VHF), 802.11x, and Bluetooth. Wireless networks use authentication protocols (e.g., EAP/TLS, PEAP), which provide credential protection and mutual... |
|
V-252955
|
Medium |
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 state or can identify the operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel... |
|
V-252954
|
Medium |
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 required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system... |
|
V-252953
|
Medium |
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 access to the system. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained.
Operating systems need to track periods of inactivity and... |
|
V-252952
|
Medium |
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 using two or more factors to achieve authentication.
Factors include:
1) something a user knows (e.g., password/PIN);
2) something a user has (e.g., cryptographic identification device, token); and
3) something a... |
|
V-252951
|
Medium |
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 compromise of the system.
Interactive users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Interactive users (and processes acting on behalf of users)... |
|
V-252950
|
Medium |
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 not be available for forensic analysis.
There are various methods of mapping certificates to user/group accounts for TOSS. For the purposes of this requirement, the check... |
|
V-252949
|
Medium |
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 system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating... |
|
V-252948
|
Medium |
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 does not want to log out because of the temporary nature of the absence.
The session lock is implemented at the point where session... |
|
V-252946
|
Medium |
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 attacks, is reduced. Limits are imposed by locking the account. |
|
V-252944
|
Medium |
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, even in the event of misconfiguration elsewhere. |
|
V-252943
|
Medium |
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 system from an unauthenticated connection, potentially with root privileges. |
|
V-252942
|
Medium |
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 misconfiguration elsewhere. |
|
V-252941
|
Medium |
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 required, system network information may be unnecessarily transmitted across the network. |
|
V-252939
|
Medium |
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 sufficient for preventing unauthorized access to the system, as it does not require interactive identification and authentication of a connection request, or for the use of two-factor authentication. |
|
V-252936
|
Medium |
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 disabled by default, masking it adds an additional layer of assurance that it will not be enabled via a dependency in systemd. This also prevents attackers with physical... |
|
V-252935
|
Medium |
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 failure of security functions requiring name resolution, which may include time synchronization, centralized authentication, and remote system logging. |
|
V-252934
|
Medium |
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 intercepted and either read or altered.
This requirement applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook... |
|
V-252933
|
Medium |
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 options for configuring authentication, but this requirement will be focus on the System Security Services Daemon (SSSD). By default, sssd does not cache credentials. |
|
V-252932
|
Medium |
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 information system is compromised, credentials stored on the authentication device will not be affected.
Multifactor solutions that require devices separate from information systems gaining... |
|
V-252931
|
Medium |
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 capability to escalate a functional capability, it is critical the organization requires the user to reauthenticate when using the "sudo" command.
If the value is set to an integer... |
|
V-252929
|
Medium |
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 system. Changes to operating system configurations can have unintended side effects, some of which may be relevant to security.
Detecting such changes and providing an automated response can help... |
|
V-252928
|
Medium |
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 particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside the configured acceptable allowance (drift) may be inaccurate.
Synchronizing... |
|
V-252927
|
Medium |
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 state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system.... |
|
V-252926
|
Medium |
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 to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
Cryptographic mechanisms... |
|
V-252925
|
Medium |
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) encryption is a required security setting as a number of known vulnerabilities have been reported against Secure Sockets Layer (SSL) and earlier versions of TLS. Encryption of private information is essential to ensuring... |
|
V-252924
|
Medium |
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 to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
Cryptographic mechanisms... |
|
V-252922
|
Medium |
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 accomplish its mission or must operate at degraded capacity.
Managing excess capacity ensures that sufficient capacity is available to counter flooding attacks. Employing increased capacity and service... |
|
V-252921
|
Medium |
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 actions of prior users/roles (or the actions of processes acting on behalf of prior users/roles) from being available to any current users/roles (or current processes) that obtain access to shared system resources (e.g.,... |
|
V-252920
|
Medium |
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.
Security functions are the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the... |
|
V-252919
|
Medium |
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 to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.
Cryptographic mechanisms... |
|
V-252918
|
Medium |
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 confidentiality or integrity, and DoD data may be compromised.
TOSS systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
FIPS 140-2 is the... |
|
V-252917
|
Medium |
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 confidentiality or integrity, and DoD data may be compromised.
TOSS systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.
FIPS 140-2 is the... |
|
V-252916
|
Medium |
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-252915
|
Medium |
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 as root. In addition, logging on with a user-specific account provides individual accountability of actions performed on the system. |
|
V-252914
|
Medium |
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 systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for... |
|
V-252913
|
Medium |
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.
The cornerstone of the PKI is the private key used to encrypt or digitally sign information.
If the private key is stolen, this will lead... |
|
V-252912
|
Medium |
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 trusted.
A trust anchor is an authoritative entity represented via a public key and associated data. It is used in the context of public key infrastructures, X.509 digital... |
|
V-252911
|
Medium |
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 verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
System use notifications are required only for access via logon interfaces with human users... |
|
V-253117
|
Low |
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 predict. Entropy in computer security is associated with the unpredictability of a source of randomness. The random source with high entropy tends to achieve a uniform distribution... |
|
V-253116
|
Low |
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 predict. Entropy in computer security is associated with the unpredictability of a source of randomness. The random source with high entropy tends to achieve a uniform distribution... |
|
V-253105
|
Low |
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 with a file integrity tool, Advanced Intrusion Detection Environment (AIDE). |
|
V-253104
|
Low |
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 with a file integrity tool, Advanced Intrusion Detection Environment (AIDE). |
|
V-253094
|
Low |
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 adversaries. Some information technology products may remove older versions of software automatically from the information system. |
|
V-253084
|
Low |
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 defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the... |
|
V-253053
|
Low |
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 establish, correlate, and investigate the events leading up to an outage or attack.
Audit record content that may be necessary to satisfy this requirement includes, for... |
|
V-252947
|
Low |
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 number of allowed users and sessions per user is helpful in reducing the risks related to Denial of Service (DoS) attacks.
TOSS as an HPC operating system, is... |
|
V-252923
|
Low |
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 consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.
System use notifications are required only for access via logon interfaces with human users and are... |
