| V-221652 | | The Oracle Linux operating system must be configured so that the file permissions, ownership, and group membership of system files and commands match the vendor values. | Discretionary access control is weakened if a user or group has access permissions to system files and directories greater than the default.
Satisfie... |
| V-221653 | | The Oracle Linux operating system must be configured so that the cryptographic hash of system files and commands matches vendor values. | Without cryptographic integrity protections, system command and files can be altered by unauthorized users without detection.
Cryptographic mechanism... |
| V-221687 | | The Oracle Linux operating system must not allow accounts configured with blank or null passwords. | If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords should ne... |
| V-221688 | | The Oracle Linux operating system must be configured so that the SSH daemon does not allow authentication using an empty password. | Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misc... |
| V-221694 | | The Oracle Linux operating system must not allow an unattended or automatic logon to the system via a graphical user interface. | Failure to restrict system access to authenticated users negatively impacts operating system security.... |
| V-221695 | | The Oracle Linux operating system must not allow an unrestricted logon to the system. | Failure to restrict system access to authenticated users negatively impacts operating system security.... |
| V-221700 | | Oracle Linux operating systems version 7.2 or newer with a Basic Input/Output System (BIOS) must require authentication upon booting into single-user and maintenance modes. | If the system does not require valid authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenanc... |
| V-221702 | | Oracle Linux operating systems version 7.2 or newer using Unified Extensible Firmware Interface (UEFI) must require authentication upon booting into single-user and maintenance modes. | If the system does not require valid authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenanc... |
| V-221704 | | The Oracle Linux operating system must not have the rsh-server package installed. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-221705 | | The Oracle Linux operating system must not have the ypserv package installed. | Removing the "ypserv" package decreases the risk of the accidental (or intentional) activation of NIS or NIS+ services.... |
| V-221710 | | The Oracle Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. | Changes to any software components can have significant effects on the overall security of the operating system. This requirement ensures the software... |
| V-221711 | | The Oracle Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. | Changes to any software components can have significant effects on the overall security of the operating system. This requirement ensures the software... |
| V-221717 | | The Oracle Linux operating system must be configured so that the x86 Ctrl-Alt-Delete key sequence is disabled on the command line. | A locally logged-on user who presses Ctrl-Alt-Delete when at the console, can reboot the system. If accidentally pressed, as could happen in the case ... |
| V-221719 | | The Oracle Linux operating system must be a vendor supported release. | An operating system release is considered "supported" if the vendor continues to provide security patches for the product. With an unsupported release... |
| V-221723 | | The Oracle Linux operating system must be configured so that the root account must be the only account having unrestricted access to the system. | If an account other than root also has a User Identifier (UID) of "0", it has root authority, giving that account unrestricted access to the entire op... |
| V-221758 | | The Oracle Linux operating system must implement NIST FIPS-validated cryptography for the following: to provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. | Use of weak or untested encryption algorithms undermines the purposes of using encryption to protect data. The operating system must implement cryptog... |
| V-221763 | | The Oracle Linux operating system must not have the telnet-server package installed. | It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessa... |
| V-221837 | | The Oracle Linux operating system must use a virus scan program. | Virus scanning software can be used to protect a system from penetration from computer viruses and to limit their spread through intermediate systems.... |
| V-221856 | | The Oracle Linux operating system must be configured so that the SSH daemon is configured to only use the SSHv2 protocol. | SSHv1 is an insecure implementation of the SSH protocol and has many well-known vulnerability exploits. Exploits of the SSH daemon could provide immed... |
| V-221870 | | The Oracle Linux operating system must not contain .shosts files. | The .shosts files are used to configure host-based authentication for individual users or the system via SSH. Host-based authentication is not suffici... |
| V-221871 | | The Oracle Linux operating system must not contain shosts.equiv files. | The shosts.equiv files are used to configure host-based authentication for the system via SSH. Host-based authentication is not sufficient for prevent... |
| V-221884 | | The Oracle Linux operating system must not have a File Transfer Protocol (FTP) server package installed unless needed. | The FTP service provides an unencrypted remote access that does not provide for the confidentiality and integrity of user passwords or the remote sess... |
| V-221885 | | The Oracle Linux operating system must not have the Trivial File Transfer Protocol (TFTP) server package installed if not required for operational support. | If TFTP is required for operational support (such as the transmission of router configurations) its use must be documented with the Information System... |
| V-221891 | | SNMP community strings on the Oracle Linux operating system must be changed from the default. | Whether active or not, default Simple Network Management Protocol (SNMP) community strings must be changed to maintain security. If the service is run... |
| V-228565 | | The Oracle Linux operating system must be configured so the x86 Ctrl-Alt-Delete key sequence is disabled in the Graphical User Interface. | A locally logged-on user who presses Ctrl-Alt-Delete, when at the console, can reboot the system. If accidentally pressed, as could happen in the case... |
| V-251698 | | The Oracle Linux operating system must not have accounts configured with blank or null passwords. | If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords must neve... |
| V-221654 | | The Oracle Linux operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a graphical user logon. | The display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification v... |
| V-221655 | | The Oracle Linux operating system must display the approved Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a graphical user logon. | Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbi... |
| V-221656 | | The Oracle Linux operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a command line user logon. | Display of a standardized and approved use notification before granting access to the operating system ensures privacy and security notification verbi... |
| V-221657 | | The Oracle Linux operating system must enable a user session lock until that user re-establishes access using established identification and authentication procedures. | A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but do... |
| V-221658 | | The Oracle Linux operating system must uniquely identify and must authenticate users using multifactor authentication via a graphical user logon. | To assure accountability and prevent unauthenticated access, users must be identified and authenticated to prevent potential misuse and compromise of ... |
| V-221659 | | The Oracle Linux operating system must prevent a user from overriding the screensaver lock-enabled setting for the graphical user interface. | A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but do... |
| V-221660 | | The Oracle Linux operating system must initiate a screensaver after a 15-minute period of inactivity for graphical user interfaces. | A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information syst... |
| V-221661 | | The Oracle Linux operating system must prevent a user from overriding the screensaver lock-delay setting for the graphical user interface. | A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information syst... |
| V-221662 | | The Oracle Linux operating system must prevent a user from overriding the session idle-delay setting for the graphical user interface. | A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information syst... |
| V-221664 | | The Oracle Linux operating system must initiate a session lock for the screensaver after a period of inactivity for graphical user interfaces. | A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information syst... |
| V-221665 | | The Oracle Linux operating system must prevent a user from overriding the screensaver idle-activation-enabled setting for the graphical user interface. | A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but do... |
| V-221666 | | The Oracle Linux operating system must initiate a session lock for graphical user interfaces when the screensaver is activated. | A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information syst... |
| V-221667 | | The Oracle Linux operating system must be configured so that /etc/pam.d/passwd implements /etc/pam.d/system-auth when changing passwords. | Pluggable authentication modules (PAM) allow for a modular approach to integrating authentication methods. PAM operates in a top-down processing model... |
| V-221668 | | The Oracle Linux operating system must be configured so that when passwords are changed or new passwords are established, pwquality must be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-221669 | | The Oracle Linux operating system must be configured so that when passwords are changed or new passwords are established, the new password must contain at least one upper-case character. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-221670 | | The Oracle Linux operating system must be configured so that when passwords are changed or new passwords are established, the new password must contain at least one lower-case character. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-221671 | | The Oracle Linux operating system must be configured so that when passwords are changed or new passwords are assigned, the new password must contain at least one numeric character. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-221672 | | The Oracle Linux operating system must be configured so that when passwords are changed or new passwords are established, the new password must contain at least one special character. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-221673 | | The Oracle Linux operating system must be configured so that when passwords are changed a minimum of eight of the total number of characters must be changed. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-221674 | | The Oracle Linux operating system must be configured so that when passwords are changed a minimum of four character classes must be changed. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-221675 | | The Oracle Linux operating system must be configured so that when passwords are changed the number of repeating consecutive characters must not be more than three characters. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-221676 | | The Oracle Linux operating system must be configured so that when passwords are changed the number of repeating characters of the same character class must not be more than four characters. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-221677 | | The Oracle Linux operating system must be configured so that the PAM system service is configured to store only encrypted representations of passwords. | Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can ... |
| V-221678 | | The Oracle Linux operating system must be configured to use the shadow file to store only encrypted representations of passwords. | Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can ... |
| V-221680 | | The Oracle Linux operating system must be configured so that user and group account administration utilities are configured to store only encrypted representations of passwords. | Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can ... |
| V-221681 | | The Oracle Linux operating system must be configured so that passwords for new users are restricted to a 24 hours/1 day minimum lifetime. | Enforcing a minimum password lifetime helps to prevent repeated password changes to defeat the password reuse or history enforcement requirement. If u... |
| V-221682 | | The Oracle Linux operating system must be configured so that passwords are restricted to a 24 hours/1 day minimum lifetime. | Enforcing a minimum password lifetime helps to prevent repeated password changes to defeat the password reuse or history enforcement requirement. If u... |
| V-221683 | | The Oracle Linux operating system must be configured so that passwords for new users are restricted to a 60-day maximum lifetime. | Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If the operating system does not... |
| V-221684 | | The Oracle Linux operating system must be configured so that existing passwords are restricted to a 60-day maximum lifetime. | Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If the operating system does not... |
| V-221686 | | The Oracle Linux operating system must be configured so that passwords are a minimum of 15 characters in length. | The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised.
Password complexit... |
| V-221689 | | The Oracle Linux operating system must disable account identifiers (individuals, groups, roles, and devices) if the password expires. | Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected ac... |
| V-221690 | | The Oracle Linux operating system must be configured to lock accounts for a minimum of 15 minutes after three unsuccessful logon attempts within a 15-minute timeframe. | By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, ... |
| V-221691 | | The Oracle Linux operating system must lock the associated account after three unsuccessful root logon attempts are made within a 15-minute period. | By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, ... |
| V-221692 | | The Oracle Linux operating system must be configured so that users must provide a password for privilege escalation. | Without reauthentication, users may access resources or perform tasks for which authorization has not been granted.
When operating systems provide t... |
| V-221693 | | The Oracle Linux operating system must be configured so that the delay between logon prompts following a failed console logon attempt is at least four seconds. | Configuring the operating system to implement organization-wide security implementation guides and security checklists verifies compliance with federa... |
| V-221696 | | The Oracle Linux operating system must not allow users to override SSH environment variables. | Failure to restrict system access to authenticated users negatively impacts operating system security.... |
| V-221697 | | The Oracle Linux operating system must not allow a non-certificate trusted host SSH logon to the system. | Failure to restrict system access to authenticated users negatively impacts operating system security.... |
| V-221699 | | The Oracle Linux operating system must require authentication upon booting into single-user and maintenance modes. | If the system does not require valid root authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maint... |
| V-221703 | | The Oracle Linux operating system must uniquely identify and must authenticate organizational users (or processes acting on behalf of organizational users) using multifactor authentication. | To ensure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and... |
| V-221707 | | The Oracle Linux operating system must prevent nonprivileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. | Preventing nonprivileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary ... |
| V-221708 | | The Oracle Linux operating system must be configured so that a file integrity tool verifies the baseline operating system configuration at least weekly. | Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the operating s... |
| V-221709 | | The Oracle Linux operating system must be configured so that designated personnel are notified if baseline configurations are changed in an unauthorized manner. | Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the operating s... |
| V-221712 | | The Oracle Linux operating system must be configured to disable USB mass storage. | USB mass storage permits easy introduction of unknown devices, thereby facilitating malicious activity.
Satisfies: SRG-OS-000114-GPOS-00059, SRG-OS-0... |
| V-221713 | | The Oracle Linux operating system must be configured so that the Datagram Congestion Control Protocol (DCCP) kernel module is disabled unless required. | Disabling DCCP protects the system against exploitation of any flaws in the protocol implementation.... |
| V-221714 | | The Oracle Linux operating system must disable the file system automounter unless required. | Automatically mounting file systems permits easy introduction of unknown devices, thereby facilitating malicious activity.
Satisfies: SRG-OS-000114-G... |
| V-221716 | | The Oracle Linux operating system must enable SELinux. | Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. Security function is de... |
| V-221718 | | The Oracle Linux operating system 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-221720 | | The Oracle Linux operating system security patches and updates must be installed and up to date. | Timely patching is critical for maintaining the operational availability, confidentiality, and integrity of information technology (IT) systems. Howev... |
| V-221721 | | The Oracle Linux operating system must not have unnecessary accounts. | Accounts providing no operational purpose provide additional opportunities for system compromise. Unnecessary accounts include user accounts for indiv... |
| V-221724 | | The Oracle Linux operating system must be configured so that all files and directories 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-221725 | | The Oracle Linux operating system must be configured so that all files and directories have a valid group owner. | Files without a valid group owner may be unintentionally inherited if a group is assigned the same Group Identifier (GID) as the GID of the files with... |
| V-221727 | | The Oracle Linux operating system must be configured so that all local interactive user accounts, upon creation, are assigned a home directory. | If local interactive users are not assigned a valid home directory, there is no place for the storage and control of owned files.... |
| V-221728 | | The Oracle Linux operating system must be configured so that all local interactive users have a home directory assigned and defined 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.
In additio... |
| V-221729 | | The Oracle Linux operating system must be configured so that all local interactive user home directories have mode 0750 or less permissive. | Excessive permissions on local interactive user home directories may allow unauthorized access to user files by other users.... |
| V-221730 | | The Oracle Linux operating system must be configured so that all local interactive user home directories are owned by their respective users. | If a local interactive user does not own their home directory, unauthorized users could access or modify the user's files, and the users may not be ab... |
| V-221731 | | The Oracle Linux operating system must be configured so that all local interactive user home directories are group-owned by the home directory owners primary group. | If the Group Identifier (GID) of a local interactive user's home directory is not the same as the primary GID of the user, this would allow unauthoriz... |
| V-221732 | | The Oracle Linux operating system must be configured so that all files and directories contained in local interactive user home directories 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-221733 | | The Oracle Linux operating system must be configured so that all files and directories contained in local interactive user home directories are group-owned by a group of which the home directory owner is a member. | If a local interactive user's files are group-owned by a group of which the user is not a member, unintended users may be able to access them.... |
| V-221734 | | The Oracle Linux operating system must be configured so that all files and directories contained in local interactive user home directories have a mode of 0750 or less permissive. | If a local interactive user files have excessive permissions, unintended users may be able to access or modify them.... |
| V-221735 | | The Oracle Linux operating system must be configured so that all local initialization files for interactive users are owned by the home directory user or root. | Local initialization files are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accou... |
| V-221736 | | The Oracle Linux operating system must be configured so that all local initialization files for local interactive users are be group-owned by the users primary group or root. | Local initialization files for interactive users are used to configure the user's shell environment upon logon. Malicious modification of these files ... |
| V-221737 | | The Oracle Linux operating system must be configured so that all local initialization files have mode 0740 or less permissive. | Local initialization files are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accou... |
| V-221738 | | The Oracle Linux operating system must be configured so that all local interactive user initialization files executable search paths contain only paths that resolve to the users home directory. | The executable search path (typically the PATH environment variable) contains a list of directories for the shell to search to find executables. If th... |
| V-221739 | | The Oracle Linux operating system must be configured so that local initialization files do not execute world-writable programs. | If user start-up files execute world-writable programs, especially in unprotected directories, they could be maliciously modified to destroy user file... |
| V-221740 | | The Oracle Linux operating system must be configured so that all system device files are correctly labeled to prevent unauthorized modification. | If an unauthorized or modified device is allowed to exist on the system, there is the possibility the system may perform unintended or unauthorized op... |
| V-221741 | | The Oracle Linux operating system must be configured so that file systems containing user home directories are mounted to prevent files with the setuid and setgid bit set from being executed. | The "nosuid" mount option causes the system not to execute setuid and setgid files with owner privileges. This option must be used for mounting any fi... |
| V-221742 | | The Oracle Linux operating system must prevent files with the setuid and setgid bit set from being executed on file systems that are used with removable media. | The "nosuid" mount option causes the system not to execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting an... |
| V-221743 | | The Oracle Linux operating system must prevent files with the setuid and setgid bit set from being executed on file systems that are being imported via Network File System (NFS). | The "nosuid" mount option causes the system not to execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting an... |
| V-221744 | | The Oracle Linux operating system must prevent binary files from being executed on file systems that are being imported via Network File System (NFS). | The "noexec" mount option causes the system not to execute binary files. This option must be used for mounting any file system not containing approved... |
| V-221748 | | The Oracle Linux operating system must be configured so that all world-writable directories are group-owned by root, sys, bin, or an application group. | If a world-writable directory is not group-owned by root, sys, bin, or an application Group Identifier (GID), unauthorized users may be able to modify... |
| V-221749 | | The Oracle Linux operating system must set the umask value to 077 for all local interactive user accounts. | The umask controls the default access mode assigned to newly created files. A umask of 077 limits new files to mode 700 or less permissive. Although u... |
| V-221750 | | The Oracle Linux operating system must have cron logging implemented. | Cron logging can be used to trace the successful or unsuccessful execution of cron jobs. It can also be used to spot intrusions into the use of the cr... |
| V-221751 | | The Oracle Linux operating system must be configured so that the cron.allow file, if it exists, is owned by root. | If the owner of the "cron.allow" file is not set to root, the possibility exists for an unauthorized user to view or to edit sensitive information.... |
| V-221752 | | The Oracle Linux operating system must be configured so that the cron.allow file, if it exists, is group-owned by root. | If the group owner of the "cron.allow" file is not set to root, sensitive information could be viewed or edited by unauthorized users.... |
| V-221753 | | The Oracle Linux operating system must disable Kernel core dumps unless needed. | Kernel core dumps may contain the full contents of system memory at the time of the crash. Kernel core dumps may consume a considerable amount of disk... |
| V-221761 | | The Oracle Linux operating system must use a file integrity tool that is configured to use FIPS 140-2 approved cryptographic hashes for validating file contents and directories. | File integrity tools use cryptographic hashes for verifying file contents and directories have not been altered. These hashes must be FIPS 140-2 appro... |
| V-221762 | | The Oracle Linux operating system must not allow removable media to be used as the boot loader unless approved. | Malicious users with removable boot media can gain access to a system configured to use removable media as the boot loader. If removable media is desi... |
| V-221764 | | The Oracle Linux operating system must be configured so that auditing is configured to produce records containing information to establish what type of events occurred, where the events occurred, the source of the events, and the outcome of the events. These audit records must also identify individual identities of group account users. | Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage o... |
| V-221765 | | The Oracle Linux operating system must shut down upon audit processing failure, unless availability is an overriding concern. If availability is a concern, the system must alert the designated staff (System Administrator [SA] and Information System Security Officer [ISSO] at a minimum) in the event of an audit processing failure. | It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notificatio... |
| V-221767 | | The Oracle Linux operating system must be configured to off-load audit logs 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.
Off-loading is a common process in information s... |
| V-221768 | | The Oracle Linux operating system must take appropriate action when the remote logging buffer is full. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information s... |
| V-221769 | | The Oracle Linux operating system must label all off-loaded audit logs before sending them to the central log server. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information s... |
| V-221770 | | The Oracle Linux operating system must off-load audit records onto a different system or media from the system being audited. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information s... |
| V-221771 | | The Oracle Linux operating system must encrypt the transfer of audit records off-loaded onto a different system or media from the system being audited. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information s... |
| V-221772 | | The Oracle Linux operating system must be configured so that the audit system takes appropriate action when the audit storage volume is full. | Taking appropriate action in case of a filled audit storage volume will minimize the possibility of losing audit records.
One method of off-loading au... |
| V-221773 | | The Oracle Linux operating system must be configured so that the audit system takes appropriate action when there is an error sending audit records to a remote system. | Taking appropriate action when there is an error sending audit records to a remote system will minimize the possibility of losing audit records.
One m... |
| V-221774 | | The Oracle Linux operating system must initiate an action to notify the System Administrator (SA) and Information System Security Officer (ISSO), at a minimum, when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity. | If security personnel are not notified immediately when storage volume reaches 75 percent utilization, they are unable to plan for audit record storag... |
| V-221775 | | The Oracle Linux operating system must immediately notify the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) via email when the threshold for the repository maximum audit record storage capacity is reached. | If security personnel are not notified immediately when the threshold for the repository maximum audit record storage capacity is reached, they are un... |
| V-221776 | | The Oracle Linux operating system must immediately notify the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) when the threshold for the repository maximum audit record storage capacity is reached. | If security personnel are not notified immediately when the threshold for the repository maximum audit record storage capacity is reached, they are un... |
| V-221777 | | The Oracle Linux operating system must audit all executions of privileged functions. | Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromise... |
| V-221778 | | The Oracle Linux operating system must audit all uses of the chown, fchown, fchownat, and lchown syscalls. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-221782 | | The Oracle Linux operating system must audit all uses of the chmod, fchmod, and fchmodat syscalls. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-221785 | | The Oracle Linux operating system must audit all uses of the setxattr, fsetxattr, lsetxattr, removexattr, fremovexattr, and lremovexattr syscalls. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-221792 | | The Oracle Linux operating system must audit all uses of the creat, open, openat, open_by_handle_at, truncate, and ftruncate syscalls. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-221797 | | The Oracle Linux operating system must audit all uses of the semanage command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-221798 | | The Oracle Linux operating system must audit all uses of the setsebool command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-221799 | | The Oracle Linux operating system must audit all uses of the chcon command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-221800 | | The Oracle Linux operating system must audit all uses of the setfiles command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-221801 | | The Oracle Linux operating system must generate audit records for all unsuccessful account access events. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-221802 | | The Oracle Linux operating system must generate audit records for all successful account access events. | Without generating audit records that to the security and mission needs of the organization, it would be difficult to establish, correlate, and invest... |
| V-221803 | | The Oracle Linux operating system must audit all uses of the passwd command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-221804 | | The Oracle Linux operating system must audit all uses of the unix_chkpwd command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-221805 | | The Oracle Linux operating system must audit all uses of the gpasswd command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-221806 | | The Oracle Linux operating system must audit all uses of the chage command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-221807 | | The Oracle Linux operating system must audit all uses of the userhelper command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-221808 | | The Oracle Linux operating system must audit all uses of the su command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-221809 | | The Oracle Linux operating system must audit all uses of the sudo command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-221810 | | The Oracle Linux operating system must audit all uses of the sudoers file and all files in the /etc/sudoers.d/ directory. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-221811 | | The Oracle Linux operating system must audit all uses of the newgrp command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-221812 | | The Oracle Linux operating system must audit all uses of the chsh command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-221813 | | The Oracle Linux operating system must audit all uses of the mount command and syscall. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-221814 | | The Oracle Linux operating system must audit all uses of the umount command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-221815 | | The Oracle Linux operating system must audit all uses of the postdrop command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-221816 | | The Oracle Linux operating system must audit all uses of the postqueue command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-221817 | | The Oracle Linux operating system must audit all uses of the ssh-keysign command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-221818 | | The Oracle Linux operating system must audit all uses of the crontab command. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organizat... |
| V-221819 | | The Oracle Linux operating system must audit all uses of the pam_timestamp_check command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-221820 | | The Oracle Linux operating system must audit all uses of the create_module syscall. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-221821 | | The Oracle Linux operating system must audit all uses of the init_module and finit_module syscalls. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-221823 | | The Oracle Linux operating system must audit all uses of the delete_module syscall. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-221824 | | The Oracle Linux operating system must audit all uses of the kmod command. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-221825 | | The Oracle Linux operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/passwd. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-221826 | | The Oracle Linux operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/group. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-221827 | | The Oracle Linux operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/gshadow. | Without generating audit specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigat... |
| V-221828 | | The Oracle Linux operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-221829 | | The Oracle Linux operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/security/opasswd. | Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and in... |
| V-221833 | | The Oracle Linux operating system must audit all uses of the unlink, unlinkat, rename, renameat, and rmdir syscalls. | If the system is not configured to audit certain activities and write them to an audit log, it is more difficult to detect and track system compromise... |
| V-221835 | | The Oracle Linux operating system must send rsyslog output to a log aggregation server. | Sending rsyslog output to another system ensures that the logs cannot be removed or modified in the event that the system is compromised or has a hard... |
| V-221836 | | The Oracle Linux operating system must be configured so that the rsyslog daemon does not accept log messages from other servers unless the server is being used for log aggregation. | Unintentionally running a rsyslog server accepting remote messages puts the system at increased risk. Malicious rsyslog messages sent to the server co... |
| V-221839 | | The Oracle Linux operating system must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the Ports, Protocols, and Services Management Component Local Service Assessment (PPSM CLSA) and vulnerability assessments. | In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types... |
| V-221840 | | The Oracle Linux 7 operating system must implement DoD-approved encryption to protect the confidentiality of SSH connections. | Unapproved mechanisms for authentication to the cryptographic module are not verified, and therefore cannot be relied upon to provide confidentiality ... |
| V-221841 | | The Oracle Linux operating system must be configured so that all network connections associated with a communication session are terminated at the end of the session or after 15 minutes of inactivity from the user at a command prompt, except to fulfill documented and validated mission requirements. | Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management se... |
| V-221842 | | The Oracle Linux operating system must display the Standard Mandatory DoD Notice and Consent Banner immediately prior to, or as part of, remote access logon prompts. | Display of a standardized and approved use notification before granting access to the publicly accessible operating system ensures privacy and securit... |
| V-221843 | | The Oracle Linux operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) authentication communications. | Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Cryptographic mechanisms used for pr... |
| V-221844 | | The Oracle Linux operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) communications. | Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Cryptographic mechanisms used for pr... |
| V-221845 | | The Oracle Linux operating system must implement cryptography to protect the integrity of Lightweight Directory Access Protocol (LDAP) communications. | Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Cryptographic mechanisms used for pr... |
| V-221846 | | The Oracle Linux operating system must implement virtual address space randomization. | Address space layout randomization (ASLR) makes it more difficult for an attacker to predict the location of attack code introduced into a process's a... |
| V-221847 | | The Oracle Linux operating system must be configured so that all networked systems have SSH installed. | Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercep... |
| V-221848 | | The Oracle Linux operating system must be configured so that all networked systems use SSH for confidentiality and integrity of transmitted and received information as well as information during preparation for transmission. | Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercep... |
| V-221849 | | The Oracle Linux operating system must be configured so that all network connections associated with SSH traffic are terminated after 10 minutes of becoming unresponsive. | Terminating an unresponsive SSH session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a m... |
| V-221850 | | The Oracle Linux operating system must be configured so that the SSH daemon does not allow authentication using RSA rhosts authentication. | Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misc... |
| V-221851 | | The Oracle Linux operating system must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive. | Terminating an unresponsive SSH session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a m... |
| V-221852 | | The Oracle Linux operating system must be configured so that the SSH daemon does not allow authentication using rhosts authentication. | Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misc... |
| V-221853 | | The Oracle Linux operating system must display the date and time of the last successful account logon upon an SSH logon. | Providing users with feedback on when account accesses via SSH last occurred facilitates user recognition and reporting of unauthorized account use.... |
| V-221854 | | The Oracle Linux operating system must not permit direct logons to the root account using remote access via SSH. | Even though the communications channel may be encrypted, an additional layer of security is gained by extending the policy of not logging on directly ... |
| V-221855 | | The Oracle Linux operating system must be configured so that the SSH daemon does not allow authentication using known hosts authentication. | Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misc... |
| V-221857 | | The Oracle Linux operating system must be configured so that the SSH daemon is configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms. | DoD information systems are required to use FIPS 140-2 approved cryptographic hash functions. The only SSHv2 hash algorithm meeting this requirement i... |
| V-221858 | | The Oracle Linux operating system must be configured so that the SSH public host key files 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-221859 | | The Oracle Linux operating system must be configured so the SSH private host key files have mode 0640 or less permissive. | If an unauthorized user obtains the private SSH host key file, the host could be impersonated.... |
| V-221860 | | The Oracle Linux operating system must be configured so that the SSH daemon does not permit Generic Security Service Application Program Interface (GSSAPI) authentication unless needed. | GSSAPI authentication is used to provide additional authentication mechanisms to applications. Allowing GSSAPI authentication through SSH exposes the ... |
| V-221861 | | The Oracle Linux operating system must be configured so that the SSH daemon does not permit Kerberos authentication unless needed. | Kerberos authentication for SSH is often implemented using Generic Security Service Application Program Interface (GSSAPI). If Kerberos is enabled thr... |
| V-221862 | | The Oracle Linux operating system must be configured so that the SSH daemon performs 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-221863 | | The Oracle Linux operating system must be configured so that the SSH daemon uses privilege separation. | SSH daemon privilege separation causes the SSH process to drop root privileges when not needed, which would decrease the impact of software vulnerabil... |
| V-221864 | | The Oracle Linux operating system must be configured so that the SSH daemon does not allow compression or only allows compression after successful authentication. | If compression is allowed in an SSH connection prior to authentication, vulnerabilities in the compression software could result in compromise of the ... |
| V-221866 | | The Oracle Linux operating system must, for networked systems, synchronize clocks with a server that is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, 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 a particular ev... |
| V-221867 | | The Oracle Linux operating system must protect against or limit the effects of Denial of Service (DoS) attacks by validating the operating system is implementing rate-limiting measures on impacted network interfaces. | DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or m... |
| V-221868 | | The Oracle Linux operating system must enable an application firewall, if available. | Firewalls protect computers from network attacks by blocking or limiting access to open network ports. Application firewalls limit which applications ... |
| V-221873 | | The Oracle Linux operating system must not forward Internet Protocol version 4 (IPv4) source-routed packets. | Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, ... |
| V-221874 | | The Oracle Linux operating system must use a reverse-path filter for IPv4 network traffic when possible on all interfaces. | Enabling reverse path filtering drops packets with invalid source addresses received on the interface. It should not be used on systems that are rout... |
| V-221875 | | The Oracle Linux operating system must use a reverse-path filter for IPv4 network traffic when possible by default. | Enabling reverse path filtering drops packets with invalid source addresses received on the interface. It should not be used on systems which are rout... |
| V-221876 | | The Oracle Linux operating system must not forward Internet Protocol version 4 (IPv4) source-routed packets by default. | Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, ... |
| V-221877 | | The Oracle Linux operating system must not respond to Internet Protocol version 4 (IPv4) 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.... |
| V-221878 | | The Oracle Linux operating system must prevent Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages from being accepted. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the hos... |
| V-221879 | | The Oracle Linux operating system must ignore Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the hos... |
| V-221880 | | The Oracle Linux operating system must not allow interfaces to perform Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects by default. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain inform... |
| V-221881 | | The Oracle Linux operating system must not send Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects. | ICMP redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain inform... |
| V-221882 | | Network interfaces configured on The Oracle Linux operating system must not be in promiscuous mode. | Network interfaces in promiscuous mode allow for the capture of all network traffic visible to the system. If unauthorized individuals can access thes... |
| V-221883 | | The Oracle Linux operating system must be configured to prevent unrestricted mail relaying. | If unrestricted mail relaying is permitted, unauthorized senders could use this host as a mail relay for the purpose of sending spam or other unauthor... |
| V-221886 | | The Oracle Linux operating system must be configured so that remote X connections are disabled, unless to fulfill documented and validated mission requirements. | The security risk of using X11 forwarding is that the client's X11 display server may be exposed to attack when the SSH client requests forwarding. A ... |
| V-221887 | | The Oracle Linux operating system must be configured so that if the Trivial File Transfer Protocol (TFTP) server is required, the TFTP daemon is configured to operate in secure mode. | Restricting TFTP to a specific directory prevents remote users from copying, transferring, or overwriting system files.... |
| V-221888 | | The Oracle Linux operating system must not have a graphical display manager installed unless approved. | Internet services not required for system or application processes must not be active to decrease the attack surface of the system. Graphical display ... |
| V-221889 | | The Oracle Linux operating system must not be performing packet forwarding unless the system is a router. | Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not ... |
| V-221890 | | The Oracle Linux operating system must be configured so that the Network File System (NFS) is configured to use RPCSEC_GSS. | When an NFS server is configured to use RPCSEC_SYS, a selected userid and groupid are used to handle requests from the remote user. The userid and gro... |
| V-221892 | | The Oracle Linux operating system access control program must be configured to grant or deny system access to specific hosts and services. | If the systems access control program is not configured with appropriate rules for allowing and denying access to system network resources, services m... |
| V-221893 | | The Oracle Linux operating system must not have unauthorized IP tunnels configured. | IP tunneling mechanisms can be used to bypass network filtering. If tunneling is required, it must be documented with the Information System Security ... |
| V-221894 | | The Oracle Linux operating system must not forward IPv6 source-routed packets. | Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, ... |
| V-221895 | | The Oracle Linux operating system must have the required packages for multifactor authentication installed. | Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is co... |
| V-221896 | | The Oracle Linux operating system must implement multifactor authentication for access to privileged accounts via pluggable authentication modules (PAM). | Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is co... |
| V-221897 | | The Oracle Linux operating system must implement certificate status checking for PKI authentication. | Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is co... |
| V-221898 | | The Oracle Linux operating system must be configured so that all wireless network adapters are disabled. | The use of wireless networking can introduce many different attack vectors into the organization's network. Common attack vectors such as malicious as... |
| V-221899 | | The Oracle Linux operating system must protect audit information from unauthorized read, modification, or deletion. | If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is i... |
| V-228566 | | The Oracle Linux operating system must be configured so that all world-writable directories are owned by root, sys, bin, or an application user. | If a world-writable directory is not owned by root, sys, bin, or an application User Identifier (UID), unauthorized users may be able to modify files ... |
| V-228567 | | The Oracle Linux operating system must disable the graphical user interface automounter unless required. | Automatically mounting file systems permits easy introduction of unknown devices, thereby facilitating malicious activity.
Satisfies: SRG-OS-000114-G... |
| V-228569 | | The Oracle Linux operating system must be configured so users must re-authenticate for privilege escalation. | Without re-authentication, users may access resources or perform tasks for which they do not have authorization.
When operating systems provide the ... |
| V-228570 | | The Oracle Linux operating system 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 functions are ... |
| V-233306 | | The Oracle Linux operating system SSH daemon must prevent remote hosts from connecting to the proxy display. | When X11 forwarding is enabled, there may be additional exposure to the server and client displays if the sshd proxy display is configured to listen o... |
| V-237627 | | The Oracle Linux operating system must restrict privilege elevation to authorized personnel. | The sudo command allows a user to execute programs with elevated (administrator) privileges. It prompts the user for their password and confirms your ... |
| V-237628 | | The Oracle Linux operating system must use the invoking user's password for privilege escalation when using "sudo". | The sudoers security policy requires that users authenticate themselves before they can use sudo. When sudoers requires authentication, it validates t... |
| V-237629 | | The Oracle Linux operating system must require re-authentication when using the "sudo" command. | Without re-authentication, users may access resources or perform tasks for which they do not have authorization.
When operating systems provide the ... |
| V-244555 | | Oracle Linux operating systems version 7.2 or newer booted with a BIOS must have a unique name for the grub superusers account when booting into single-user and maintenance modes. | If the system does not require valid authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenanc... |
| V-244556 | | Oracle Linux operating systems version 7.2 or newer booted with United Extensible Firmware Interface (UEFI) must have a unique name for the grub superusers account when booting into single-user mode and maintenance. | If the system does not require valid authentication before it boots into single-user or maintenance mode, anyone who invokes single-user or maintenanc... |
| V-250309 | | The Oracle Linux operating system must confine SELinux users to roles that conform to least privilege. | Preventing nonprivileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary ... |
| V-250310 | | The Oracle Linux operating system must not allow privileged accounts to utilize SSH. | Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary... |
| V-250311 | | The Oracle Linux operating system must elevate the SELinux context when an administrator calls the sudo command. | Preventing nonprivileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary ... |
| V-251699 | | The Oracle Linux operating system must specify the default "include" directory for the /etc/sudoers file. | The "sudo" command allows authorized users to run programs (including shells) as other users, system users, and root. The "/etc/sudoers" file is used ... |
| V-251700 | | The Oracle Linux operating system must not be configured to bypass password requirements for privilege escalation. | Without re-authentication, users may access resources or perform tasks for which they do not have authorization.
When operating systems provide the ... |
| V-251701 | | The Oracle Linux operating system must use a file integrity tool to verify correct operation of all security functions. | Without verification of the security functions, security functions may not operate correctly, and the failure may go unnoticed. Security function is d... |
| V-254522 | | The Oracle Linux operating system must automatically expire temporary accounts within 72 hours. | Temporary accounts are privileged or nonprivileged accounts that are established during pressing circumstances, such as new software or hardware confi... |
| V-255899 | | The Oracle Linux operating system SSH server must be configured to use only FIPS-validated key exchange algorithms. | The use of FIPS-validated cryptographic algorithms is enforced by enabling kernel FIPS mode. In the event that kernel FIPS mode is disabled, the use o... |
| V-255902 | | The Oracle Linux operating system must be configured to prevent overwriting of custom authentication configuration settings by the authconfig utility. | When using the authconfig utility to modify authentication configuration settings, the "system-auth" and "password-auth" files and any custom settings... |
| V-256975 | | The Oracle Linux operating system must ensure cryptographic verification of vendor software packages. | Cryptographic verification of vendor software packages ensures that all software packages are obtained from a valid source and protects against spoofi... |
| V-256976 | | The Oracle Linux operating system must disable the login screen user list for graphical user interfaces. | Leaving the user list enabled is a security risk as it allows anyone with physical access to the system to enumerate known user accounts without authe... |
| V-256977 | | The Oracle Linux operating system must be configured to allow sending email notifications of unauthorized configuration changes to designated personnel. | Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the operating s... |
| V-274875 | | OL 7 must audit any script or executable called by cron as root or by any privileged user. | Any script or executable called by cron as root or by any privileged user must be owned by that user and must have the permissions 755 or more restric... |
| V-221715 | | The Oracle Linux operating system must remove all software components after updated versions have been installed. | Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by advers... |
| V-221722 | | The Oracle Linux operating system must be configured so that all Group Identifiers (GIDs) referenced in the /etc/passwd file are defined in the /etc/group file. | If a user is assigned the GID of a group not existing on the system, and a group with the GID is subsequently created, the user may have unintended ri... |
| V-221747 | | The Oracle Linux operating system must mount /dev/shm with secure options. | The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved... |
| V-221754 | | The Oracle Linux operating system must be configured so that a separate file system is used for user home directories (such as /home or an equivalent). | The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.... |
| V-221755 | | The Oracle Linux operating system must use a separate file system for /var. | The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.... |
| V-221756 | | The Oracle Linux operating system must use a separate file system for the system audit data path large enough to hold at least one week of audit data. | The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.... |
| V-221757 | | The Oracle Linux operating system must use a separate file system for /tmp (or equivalent). | The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.... |
| V-221759 | | The Oracle Linux operating system must be configured so that the file integrity tool is configured to verify Access Control Lists (ACLs). | ACLs can provide permissions beyond those permitted through the file mode and must be verified by file integrity tools.... |
| V-221760 | | The Oracle Linux operating system must be configured so that the file integrity tool is configured to verify extended attributes. | Extended attributes in file systems are used to contain arbitrary data and file metadata with security implications.... |
| V-221838 | | The Oracle Linux operating system must limit the number of concurrent sessions to 10 for all accounts and/or account types. | Operating system management includes the ability to control the number of users and user sessions that utilize an operating system. Limiting the numbe... |
| V-221869 | | The Oracle Linux operating system must display the date and time of the last successful account logon upon logon. | Providing users with feedback on when account accesses last occurred facilitates user recognition and reporting of unauthorized account use.... |
| V-221872 | | For Oracle Linux operating systems using DNS resolution, at least two name servers must be configured. | To provide availability for name resolution services, multiple redundant name servers are mandated. A failure in name resolution could lead to the fai... |
| V-255901 | | The Oracle Linux operating system must restrict access to the kernel message buffer. | Restricting access to the kernel message buffer limits access only to root. This prevents attackers from gaining additional system information as a no... |
