{"stig":{"title":"Riverbed NetIM OS Security Technical Implementation Guide","version":"1","release":"1"},"checks":[{"vulnId":"V-275534","ruleId":"SV-275534r1147652_rule","severity":"medium","ruleTitle":"Ubuntu OS must be configured so that audit configuration files are not write-accessible by unauthorized users.","description":"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. \n \nMisconfigured audits may degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.","checkContent":"Verify \"/etc/audit/audit.rules\", \"/etc/audit/auditd.conf\", and \"/etc/audit/rules.d/*\" files have a mode of \"640\" or less permissive by using the following command: \n \n $ sudo ls -al /etc/audit/audit.rules /etc/audit/auditd.conf /etc/audit/rules.d/* | awk '{print $1, $9}' \n -rw-r----- /etc/audit/audit.rules \n -rw-r----- /etc/audit/auditd.conf \n -rw-r----- /etc/audit/rules.d/audit.rules \n \nIf \"/etc/audit/audit.rules\", \"/etc/audit/auditd.conf\", or \"/etc/audit/rules.d/*\" files have a mode more permissive than \"640\", this is a finding.","fixText":"Configure /etc/audit/audit.rules\", \"/etc/audit/auditd.conf\", and \"/etc/audit/rules.d/*\" files to have a mode of \"640\" by using the following command: \n \n $ sudo chmod -R 640 /etc/audit/audit.rules /etc/audit/auditd.conf /etc/audit/rules.d/*","ccis":["CCI-000171"]},{"vulnId":"V-275565","ruleId":"SV-275565r1147745_rule","severity":"medium","ruleTitle":"Ubuntu OS must disable the x86 Ctrl-Alt-Delete key sequence.","description":"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.","checkContent":"Verify Ubuntu OS is not configured to reboot the system when Ctrl-Alt-Delete is pressed by using the following command: \n \n $ systemctl status ctrl-alt-del.target \n ctrl-alt-del.target \n Loaded: masked (Reason: Unit ctrl-alt-del.target is masked.) \n Active: inactive (dead) \n \nIf the \"ctrl-alt-del.target\" is not masked, this is a finding.","fixText":"Configure Ubuntu OS to disable the Ctrl-Alt-Delete sequence for the command line by using the following commands: \n \n $ sudo systemctl disable ctrl-alt-del.target \n \n $ sudo systemctl mask ctrl-alt-del.target \n \nReload the daemon to take effect: \n \n $ sudo systemctl daemon-reload","ccis":["CCI-000366"]},{"vulnId":"V-275566","ruleId":"SV-275566r1147748_rule","severity":"high","ruleTitle":"Ubuntu OS must require authentication upon booting into single-user and maintenance modes.","description":"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 access. \n \nSuccessful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. \n \nAccess control policies include identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.","checkContent":"Verify Ubuntu OS requires a password for authentication upon booting into single-user and maintenance modes by using the following command: \n \n $ sudo grep -i password /boot/grub/grub.cfg \n \n password_pbkdf2 root grub.pbkdf2.sha512.10000.03255F190F0E2F7B4F0D1C3216012309162F022A7A636771 \n \nIf the root password entry does not begin with \"password_pbkdf2\", this is a finding.","fixText":"Configure Ubuntu OS to require a password for authentication upon booting into single-user and maintenance modes. \n\nNote: GRUB password will need to be disabled prior to upgrade of the NETIM System if done unattended.\n \nGenerate an encrypted (grub) password for root by using the following command: \n \n $ grub-mkpasswd-pbkdf2 \n Enter Password: \n Reenter Password: \n PBKDF2 hash of your password is grub.pbkdf2.sha512.10000.03255F190F0E2F7B4F0D1C3216012309162F022A7A636771 \n \nUsing the hash from the output, modify the \"/etc/grub.d/40_custom\" file by using the following command to add a boot password: \n \n $ sudo sed -i '$i set superusers=\\\"root\\\"\\npassword_pbkdf2 root ' /etc/grub.d/40_custom \n \nwhere is the hash generated by grub-mkpasswd-pbkdf2 command. \n \nGenerate an updated \"grub.conf\" file with the new password by using the following command: \n \n $ sudo update-grub","ccis":["CCI-000213"]},{"vulnId":"V-275567","ruleId":"SV-275567r1147751_rule","severity":"medium","ruleTitle":"Ubuntu OS must restrict access to the kernel message buffer.","description":"Restricting access to the kernel message buffer limits access only to root. This prevents attackers from gaining additional system information as a nonprivileged user.","checkContent":"Verify Ubuntu OS is configured to restrict access to the kernel message buffer by using the following command: \n \n $ sysctl kernel.dmesg_restrict \n kernel.dmesg_restrict = 1 \n \nIf \"kernel.dmesg_restrict\" is not set to \"1\" or is missing, this is a finding. \n \nVerify there are no configurations that enable the kernel dmesg function: \n \n $ sudo grep -ir kernel.dmesg_restrict /run/sysctl.d/* /etc/sysctl.d/* /usr/local/lib/sysctl.d/* /usr/lib/sysctl.d/* /lib/sysctl.d/* /etc/sysctl.conf 2> /dev/null \n /etc/sysctl.d/10-kernel-hardening.conf:kernel.dmesg_restrict = 1 \n \nIf \"kernel.dmesg_restrict\" is not set to \"1\", is commented out, is missing, or conflicting results are returned, this is a finding.","fixText":"Configure Ubuntu OS to restrict access to the kernel message buffer. \n \nAdd or modify the following line in the \"/etc/sysctl.conf\" file: \n \nkernel.dmesg_restrict = 1 \n \nRemove any configurations that conflict with the above from the following locations: \n \n/run/sysctl.d/ \n/etc/sysctl.d/ \n/usr/local/lib/sysctl.d/ \n/usr/lib/sysctl.d/ \n/lib/sysctl.d/ \n/etc/sysctl.conf \n \nReload settings from all system configuration files by using the following command: \n \n $ sudo sysctl --system\n\nNote: This is set by default as part of the NetIM Ubuntu baseline.","ccis":["CCI-001090"]},{"vulnId":"V-275568","ruleId":"SV-275568r1148289_rule","severity":"medium","ruleTitle":"Ubuntu OS must disable kernel core dumps.","description":"Kernel core dumps may contain the full contents of system memory at the time of the crash. Kernel core dumps may consume a considerable amount of disk space and may result in denial of service by exhausting the available space on the target file system partition.","checkContent":"Verify kernel core dumps are disabled with the following command: \n \n$ systemctl is-active kdump.service\ninactive \n \nIf the \"kdump\" service is active, ask the system administrator (SA) if the use of the service is required and documented with the information system security officer (ISSO). \n \nIf the service is active, this is a finding.","fixText":"Disable the \"kdump\" service with the following command: \n \n$ sudo systemctl disable kdump.service \n \nIf kernel core dumps are required, document the need with the ISSO.","ccis":["CCI-001190"]},{"vulnId":"V-275569","ruleId":"SV-275569r1147757_rule","severity":"medium","ruleTitle":"Ubuntu OS must implement address space layout randomization to protect its memory from unauthorized code execution.","description":"Some adversaries launch attacks with the intent of executing code in nonexecutable regions of memory or in prohibited memory locations. Security safeguards employed to protect memory include, for example, data execution prevention and address space layout randomization. Data execution prevention safeguards can either be hardware-enforced or software-enforced with hardware providing the greater strength of mechanism. \n \nExamples of attacks are buffer overflow attacks.","checkContent":"Verify Ubuntu OS implements address space layout randomization (ASLR) by using the following command: \n \n $ sysctl kernel.randomize_va_space \n kernel.randomize_va_space = 2 \n \nIf no output is returned, verify the kernel parameter \"randomize_va_space\" is set to \"2\" by using the following command: \n \n $ cat /proc/sys/kernel/randomize_va_space \n 2 \n \nIf \"kernel.randomize_va_space\" is not set to \"2\", this is a finding. \n \nVerify that a saved value of the \"kernel.randomize_va_space\" variable is not defined. \n \n $ sudo grep -ER \"^kernel.randomize_va_space=[^2]\" /etc/sysctl.conf /etc/sysctl.d \n \nIf this returns a result, this is a finding.","fixText":"Remove the \"kernel.randomize_va_space\" entry found in the \"/etc/sysctl.conf\" file or any file located in the \"/etc/sysctl.d/\" directory. \n \nReload the system configuration files for the changes to take effect by using the following command: \n \n $ sudo sysctl --system","ccis":["CCI-002824"]},{"vulnId":"V-275570","ruleId":"SV-275570r1147760_rule","severity":"medium","ruleTitle":"Ubuntu OS must implement nonexecutable data to protect its memory from unauthorized code execution.","description":"Some adversaries launch attacks with the intent of executing code in nonexecutable 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 either be hardware-enforced or software-enforced with hardware providing the greater strength of mechanism. \n \nExamples of attacks are buffer overflow attacks.","checkContent":"Verify the NX (no-execution) bit flag is set on the system by using the following command: \n \n $ sudo dmesg | grep -i \"execute disable\" \n [ 0.000000] NX (Execute Disable) protection: active \n \nIf \"dmesg\" does not show \"NX (Execute Disable) protection: active\", check the hardware capabilities of the installed CPU by using the following command: \n \n $ grep flags /proc/cpuinfo | grep -o nx | sort -u \n nx \n \nIf no output is returned, this is a finding.","fixText":"Configure Ubuntu OS to enable NX. \n \nIf the installed CPU is hardware capable of NX protection, check if the system's BIOS/UEFI setup configuration permits toggling the \"NX bit\" or \"no execution bit\", and set it to \"enabled\".","ccis":["CCI-002824"]},{"vulnId":"V-275571","ruleId":"SV-275571r1147763_rule","severity":"high","ruleTitle":"Ubuntu OS must be configured so that the Advance Package Tool (APT) prevents the installation of patches, service packs, device drivers, or operating system components without verification they have been digitally signed using a certificate recognized and approved by the organization.","description":"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.\n \nAccordingly, patches, service packs, device drivers, or operating system components must be signed with a certificate recognized and approved by the organization.\n \nVerifying the authenticity of the software prior to installation validates the integrity of the patch or upgrade received from a vendor. This ensures the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The operating system should not have to verify the software again. This requirement does not mandate DOD certificates for this purpose; however, the certificate used to verify the software must be from an approved certificate authority (CA).","checkContent":"Verify APT is configured to prevent the installation of patches, service packs, device drivers, or Ubuntu operating system components without verification they have been digitally signed using a certificate recognized and approved by the organization by using the following command: \n \n $ grep -i allowunauthenticated /etc/apt/apt.conf.d/* \n /etc/apt/apt.conf.d/01-vendor-ubuntu:APT::Get::AllowUnauthenticated \"false\"; \n \nIf \"APT::Get::AllowUnauthenticated\" is not set to \"false\", is commented out, or is missing, this is a finding.","fixText":"Configure APT to prevent the installation of patches, service packs, device drivers, or Ubuntu operating system components without verification they have been digitally signed using a certificate recognized and approved by the organization. \n \nAdd or modify the following line in any file under the \"/etc/apt/apt.conf.d/\" directory: \n \nAPT::Get::AllowUnauthenticated \"false\";","ccis":["CCI-003992"]},{"vulnId":"V-275573","ruleId":"SV-275573r1147769_rule","severity":"medium","ruleTitle":"Ubuntu OS must have the \"libpam-pwquality\" package installed.","description":"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. \"pwquality\" enforces complex password construction configuration and has the ability to limit brute-force attacks on the system.","checkContent":"Verify Ubuntu OS has the \"libpam-pwquality\" package installed with the following command: \n \n $ dpkg -l | grep libpam-pwquality \n ii libpam-pwquality:amd64 1.4.4-1build2 amd64 PAM module to check password strength \n \nIf \"libpam-pwquality\" is not installed, this is a finding.","fixText":"Install the \"pam_pwquality\" package by using the following command: \n \n $ sudo apt-get install libpam-pwquality","ccis":["CCI-000366"]},{"vulnId":"V-275574","ruleId":"SV-275574r1147772_rule","severity":"medium","ruleTitle":"Ubuntu OS must not have the \"systemd-timesyncd\" package installed.","description":"Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time 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.\n\nOrganizations must consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints).","checkContent":"Verify the \"systemd-timesyncd\" package is not installed by using the following command: \n \n $ dpkg -l | grep systemd-timesyncd \n \nIf the \"systemd-timesyncd\" package is installed, this is a finding.","fixText":"The \"systemd-timesyncd\" package will be uninstalled as part of the \"chrony\" package install. The remaining configuration files for \"systemd-timesyncd\" must be purged from the operating system: \n \n $ sudo dpkg -P --force-all systemd-timesyncd","ccis":["CCI-000366"]},{"vulnId":"V-275575","ruleId":"SV-275575r1147775_rule","severity":"medium","ruleTitle":"Ubuntu OS must not have the \"ntp\" package installed.","description":"Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time 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. \n\nOrganizations must consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints).","checkContent":"Verify the \"ntp\" package is not installed by using the following command: \n \n $ dpkg -l | grep ntp \n \nIf the \"ntp\" package is installed, this is a finding.","fixText":"Uninstall the \"ntp\" package by using the following command: \n \n $ sudo dpkg -P --force-all ntp","ccis":["CCI-000366"]},{"vulnId":"V-275576","ruleId":"SV-275576r1147778_rule","severity":"medium","ruleTitle":"Ubuntu OS must not have the \"rsh-server\" package installed.","description":"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. \n \nRemote Shell (RSH) is a client/server application protocol that provides an unencrypted remote access service, which does not provide for the confidentiality and integrity of user passwords or the remote session. If users were allowed to login to a system using RSH, the privileged user passwords and communications could be compromised. \n \nRemoving the \"rsh-server\" package decreases the risk of accidental or intentional activation of the RSH service.","checkContent":"Verify the \"rsh-server\" package is not installed by using the following command: \n \n $ dpkg -l | grep rsh-server \n \nIf the \"rsh-server\" package is installed, this is a finding.","fixText":"Remove the \"rsh-server\" package by using the following command: \n \n $ sudo apt-get remove rsh-server","ccis":["CCI-000381"]},{"vulnId":"V-275577","ruleId":"SV-275577r1147781_rule","severity":"high","ruleTitle":"Ubuntu OS must not have the \"telnet\" package installed.","description":"It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities are often overlooked and therefore, may remain unsecure. They increase the risk to the platform by providing additional attack vectors. \n \nTelnet is a client/server application protocol that provides an unencrypted remote access service that does not provide for the confidentiality and integrity of user passwords or the remote session. If users were allowed to log in to a system using Telnet, the privileged user passwords and communications could be compromised. \n \nRemoving the \"telnetd\" package decreases the risk of accidental or intentional activation of the Telnet service.","checkContent":"Verify the \"telnetd\" package is not installed on Ubuntu OS by using the following command: \n \n $ dpkg -l | grep telnetd \n \nIf the \"telnetd\" package is installed, this is a finding.","fixText":"Remove the \"telnetd\" package by using the following command: \n \n $ sudo apt-get remove telnetd","ccis":["CCI-000197"]},{"vulnId":"V-275578","ruleId":"SV-275578r1147784_rule","severity":"medium","ruleTitle":"Ubuntu OS must implement cryptographic mechanisms to prevent unauthorized disclosure and modification of all information that requires protection at rest.","description":"Operating systems handling data requiring \"data at rest\" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. \n \nSelection 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 security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields).\n\nSatisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS-00184, SRG-OS-000780-GPOS-00240","checkContent":"Verify Ubuntu OS prevents unauthorized disclosure or modification of all information requiring at-rest protection by using disk encryption. \n \nNote: If there is a documented and approved reason for not having data-at-rest encryption, this requirement is not applicable. \n \nDetermine the partition layout for the system by using the following command: \n \n $ sudo fdisk -l \n \n ... \n Device Start End Sectors Size Type \n /dev/sda1 2048 2203647 2201600 1G EFI System \n /dev/sda2 2203648 6397951 4194304 2G Linux filesystem \n /dev/sda3 6397952 536868863 530470912 252.9G Linux filesystem \n ... \n \nVerify the system partitions are all encrypted by using the following command: \n \n # more /etc/crypttab \n \nEvery persistent disk partition present must have an entry in the file. \n \nIf any partitions other than the boot partition or pseudo file systems (such as /proc or /sys) are not listed, this is a finding.","fixText":"To encrypt an entire partition, dedicate a partition for encryption in the partition layout. \n \nNote: Encrypting a partition in an already-installed system is more difficult because it will need to be resized, and existing partitions changed.","ccis":["CCI-001199","CCI-002475","CCI-002476","CCI-004910"]},{"vulnId":"V-275579","ruleId":"SV-275579r1147787_rule","severity":"medium","ruleTitle":"Ubuntu OS must have directories that contain system commands set to a mode of \"755\" or less permissive.","description":"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. \n \nOperating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user has to make access decisions regarding the deletion of audit tools. \n \nAudit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.","checkContent":"Verify the system commands directories have mode \"755\" or less permissive by using the following command: \n \n $ find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 -type d -exec stat -c \"%n %a\" '{}' \\; \n \nIf any directories are found to be group-writable or world-writable, this is a finding.","fixText":"Configure Ubuntu OS commands directories to be protected from unauthorized access. Run the following command: \n \n $ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 -type d -exec chmod -R 755 '{}' \\;","ccis":["CCI-001495"]},{"vulnId":"V-275580","ruleId":"SV-275580r1147790_rule","severity":"medium","ruleTitle":"Ubuntu OS must have system commands set to a mode of \"755\" or less permissive.","description":"If Ubuntu OS 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. \n \nThis requirement applies to Ubuntu OS with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.","checkContent":"Verify the system commands contained in the following directories have mode \"755\" or less permissive by using the following command: \n \n $ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 -type f -exec stat -c \"%n %a\" '{}' \\; \n \nIf any files are found to be group-writable or world-writable, this is a finding.","fixText":"Configure Ubuntu OS commands to be protected from unauthorized access. Run the following command: \n \n $ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 -type f -exec chmod 755 '{}' \\;","ccis":["CCI-001499"]},{"vulnId":"V-275581","ruleId":"SV-275581r1147793_rule","severity":"medium","ruleTitle":"Ubuntu OS library files must have mode \"755\" or less permissive.","description":"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. \n \nThis requirement applies to operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.","checkContent":"Verify the systemwide shared library files contained in the directories \"/lib\", \"/lib64\", and \"/usr/lib\" have mode \"755\" or less permissive by using the following command: \n \n $ sudo find /lib /lib64 /usr/lib -perm /022 -type f -exec stat -c \"%n %a\" '{}' \\; \n \nIf any files are found to be group-writable or world-writable, this is a finding.","fixText":"Configure the library files to be protected from unauthorized access. Run the following command: \n \n $ sudo find /lib /lib64 /usr/lib -perm /022 -type f -exec chmod 755 '{}' \\;","ccis":["CCI-001499"]},{"vulnId":"V-275582","ruleId":"SV-275582r1147796_rule","severity":"medium","ruleTitle":"Ubuntu OS must configure the \"/var/log\" directory to have mode \"755\" or less permissive.","description":"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 or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.","checkContent":"Verify the \"/var/log\" directory has mode of \"755\" or less permissive by using the following command: \n \nNote: If rsyslog is active and enabled on the operating system, this requirement is not applicable. \n \n $ stat -c \"%n %a\" /var/log \n /var/log 755 \n \nIf a value of \"755\" or less permissive is not returned, this is a finding.","fixText":"Configure the \"/var/log\" directory to have permissions of \"0755\" by using the following command: \n \n $ sudo chmod 0755 /var/log","ccis":["CCI-001314"]},{"vulnId":"V-275583","ruleId":"SV-275583r1147799_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.","description":"Any operating system providing too much information in error messages risks compromising the data and security of the structure, and content of error messages needs to be carefully considered by the organization. \n \nOrganizations carefully consider the structure/content of error messages. The extent to which information systems are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, erroneous logon attempts with passwords entered by mistake as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information, such as account numbers, social security numbers, and credit card numbers. \n \nThe /var/log/btmp, /var/log/wtmp, and /var/log/lastlog files have group write and global read permissions to allow for the lastlog function to perform. Limiting the permissions beyond this configuration will result in the failure of functions that rely on the lastlog database.","checkContent":"Verify Ubuntu OS has all system log files under the \"/var/log\" directory with a permission set to \"640\" or less permissive by using the following command: \n \nNote: The btmp, wtmp, and lastlog files are excluded. Refer to the Vul Discussion for details. \n \n $ sudo find /var/log -perm /137 ! -name '*[bw]tmp' ! -name '*lastlog' -type f -exec stat -c \"%n %a\" {} \\; \n \nIf the command displays any output, this is a finding.","fixText":"Configure Ubuntu OS to set permissions of all log files under the \"/var/log\" directory to \"640\" or more restricted by using the following command: \n \nNote: The btmp, wtmp, and lastlog files are excluded. Refer to the Vul Discussion for details. \n \n $ sudo find /var/log -perm /137 ! -name '*[bw]tmp' ! -name '*lastlog' -type f -exec chmod 640 '{}' \\;","ccis":["CCI-001312"]},{"vulnId":"V-275584","ruleId":"SV-275584r1147802_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate system journal entries without revealing information that could be exploited by adversaries.","description":"Any operating system providing too much information in error messages risks compromising the data and security of the structure, and content of error messages must be carefully considered by the organization. \n \nOrganizations carefully consider the structure/content of error messages. The extent to which information systems are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, erroneous logon attempts with passwords entered in error as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information, such as account numbers, social security numbers, and credit card numbers.","checkContent":"Verify the /run/log/journal and /var/log/journal directories have permissions set to \"2750\" or less permissive by using the following command:\n\n$ sudo find /run/log/journal /var/log/journal -type d -exec stat -c \"%n %a\" {} \\;\n/run/log/journal 2750\n/var/log/journal 2750\n/var/log/journal/3b018e681c904487b11671b9c1987cce 2750 \n \nIf any output returned has a permission set greater than \"2750\", this is a finding. \n \nVerify all files in the /run/log/journal and /var/log/journal directories have permissions set to \"640\" or less permissive by using the following command: \n \n $ sudo find /run/log/journal /var/log/journal -type f -exec stat -c \"%n %a\" {} \\; \n /var/log/journal/3b018e681c904487b11671b9c1987cce/system@99dcc72bb1134aaeae4bf157aa7606f4-0000000000003c7a-0006073f8d1c0fec.journal 640 \n /var/log/journal/3b018e681c904487b11671b9c1987cce/system.journal 640\n /var/log/journal/3b018e681c904487b11671b9c1987cce/user-1000.journal 640 \n /var/log/journal/3b018e681c904487b11671b9c1987cce/user-1000@bdedf14602ff4081a77dc7a6debc8626-00000000000062a6-00060b4b414b617a.journal 640\n /var/log/journal/3b018e681c904487b11671b9c1987cce \n \nIf any output returned has a permission set greater than \"640\", this is a finding.","fixText":"Configure Ubuntu OS to set the appropriate permissions to the files and directories used by the systemd journal: \n \nAdd or modify the following lines in the \"`/usr/lib/tmpfiles.d/systemd.conf\" file: \nz /run/log/journal 2750 root systemd-journal - - \nZ /run/log/journal/%m ~2750 root systemd-journal - - \nz /var/log/journal 2750 root systemd-journal - - \nz /var/log/journal/%m 2750 root systemd-journal - - \nz /var/log/journal/%m/system.journal 0640 root systemd-journal - - \n\nRestart the system for the changes to take effect.","ccis":["CCI-001312"]},{"vulnId":"V-275585","ruleId":"SV-275585r1147805_rule","severity":"medium","ruleTitle":"Ubuntu OS must configure \"/var/log/syslog\" file with mode \"640\" or less permissive.","description":"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 or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.","checkContent":"Verify that Ubuntu OS configures the \"/var/log/syslog\" file with mode \"640\" or less permissive by using the following command: \n \n $ stat -c \"%n %a\" /var/log/syslog \n /var/log/syslog 640 \n \nIf a value of \"640\" or less permissive is not returned, this is a finding.","fixText":"Configure Ubuntu OS to have permissions of \"640\" for the \"/var/log/syslog\" file by using the following command: \n \n $ sudo chmod 0640 /var/log/syslog","ccis":["CCI-001315"]},{"vulnId":"V-275586","ruleId":"SV-275586r1147808_rule","severity":"medium","ruleTitle":"Ubuntu OS must configure audit tools with a mode of \"755\" or less permissive.","description":"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. \n \nOperating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys to make access decisions regarding the access to audit tools. \n \nAudit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.\n\nSatisfies: SRG-OS-000256-GPOS-00097, SRG-OS-000257-GPOS-00098","checkContent":"Verify Ubuntu OS configures the audit tools to have a file permission of \"755\" or less to prevent unauthorized access by using the following command: \n \n $ stat -c \"%n %a\" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/audispd* /sbin/augenrules \n /sbin/auditctl 755 \n /sbin/aureport 755 \n /sbin/ausearch 755 \n /sbin/autrace 755 \n /sbin/auditd 755 \n /sbin/audispd-zos-remote 755 \n /sbin/augenrules 755 \n \nIf any of the audit tools have a mode more permissive than \"0755\", this is a finding.","fixText":"Configure the audit tools on Ubuntu OS to be protected from unauthorized access by setting the correct permissive mode using the following command: \n \n $ sudo chmod 755 \n \nReplace \"\" with the audit tool that does not have the correct permissions.","ccis":["CCI-001493","CCI-001494"]},{"vulnId":"V-275587","ruleId":"SV-275587r1147811_rule","severity":"medium","ruleTitle":"Ubuntu OS must have directories that contain system commands owned by \"root\".","description":"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. \n \nOperating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user has to make access decisions regarding the deletion of audit tools. \n \nAudit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.","checkContent":"Verify the system commands directories are owned by \"root\" by using the following command: \n \n $ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -user root -type d -exec stat -c \"%n %U\" '{}' \\; \n \nIf any system commands directories are returned, this is a finding.","fixText":"Configure Ubuntu OS commands directories to be protected from unauthorized access. Run the following command: \n \n $ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -user root -type d -exec chown root '{}' \\;","ccis":["CCI-001495"]},{"vulnId":"V-275588","ruleId":"SV-275588r1147814_rule","severity":"medium","ruleTitle":"Ubuntu OS must have directories that contain system commands group-owned by \"root\".","description":"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. \n \nOperating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user has to make access decisions regarding the deletion of audit tools. \n \nAudit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.","checkContent":"Verify the system commands directories are group-owned by \"root\" by using the following command: \n \n $ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -group root -type d -exec stat -c \"%n %G\" '{}' \\; \n \nIf any system commands directories are returned that are not Set Group ID up on execution (SGID) files and owned by a privileged account, this is a finding.","fixText":"Configure Ubuntu OS commands directories to be protected from unauthorized access. Run the following command: \n \n $ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -group root -type d -exec chgrp root '{}' \\;","ccis":["CCI-001495"]},{"vulnId":"V-275589","ruleId":"SV-275589r1147817_rule","severity":"medium","ruleTitle":"Ubuntu OS must have system commands owned by \"root\" or a system account.","description":"If Ubuntu OS were to allow any user to make changes to software libraries, then those changes could be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. \n \nThis requirement applies to Ubuntu OS with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.","checkContent":"Verify the system commands contained in the following directories are owned by \"root\", or a required system account, by using the following command: \n \n $ sudo find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -user root -type f -exec stat -c \"%n %U\" '{}' \\; \n \nIf any system commands are returned and are not owned by a required system account, this is a finding.","fixText":"Configure Ubuntu OS commands and their respective parent directories to be protected from unauthorized access. Run the following command, replacing \"\" with any system command not owned by \"root\" or a required system account: \n \n $ sudo chown root ","ccis":["CCI-001499"]},{"vulnId":"V-275590","ruleId":"SV-275590r1147820_rule","severity":"medium","ruleTitle":"Ubuntu OS must have system commands group-owned by \"root\" or a system account.","description":"If Ubuntu OS were to allow any user to make changes to software libraries, then those changes could be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. \n \nThis requirement applies to Ubuntu OS with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.","checkContent":"Verify the system commands contained in the following directories are group-owned by \"root\" or a required system account by using the following command: \n \n $ sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -group root -type f ! -perm /2000 -exec stat -c \"%n %G\" '{}' \\; \n \nIf any system commands are returned that are not Set Group ID upon execution (SGID) files and group-owned by a required system account, this is a finding.","fixText":"Configure Ubuntu OS commands to be protected from unauthorized access.\n\nRun the following command, replacing \"\" with any system command not group-owned by \"root\" or a required system account: \n \n $ sudo chgrp root ","ccis":["CCI-001499"]},{"vulnId":"V-275591","ruleId":"SV-275591r1147823_rule","severity":"medium","ruleTitle":"Ubuntu OS library directories must be owned by \"root\".","description":"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. \n \nThis requirement applies to operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.","checkContent":"Verify the systemwide shared library directories \"/lib\", \"/lib64\", and \"/usr/lib\" are owned by \"root\" by using the following command: \n \n $ sudo find /lib /usr/lib /lib64 ! -user root -type d -exec stat -c \"%n %U\" '{}' \\; \n \nIf any systemwide library directory is returned, this is a finding.","fixText":"Configure the library files and their respective parent directories to be protected from unauthorized access. Run the following command: \n \n $ sudo find /lib /usr/lib /lib64 ! -user root -type d -exec chown root '{}' \\;","ccis":["CCI-001499"]},{"vulnId":"V-275592","ruleId":"SV-275592r1147826_rule","severity":"medium","ruleTitle":"Ubuntu OS library directories must be group-owned by \"root\".","description":"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. \n \nThis requirement applies to operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.","checkContent":"Verify the systemwide library directories \"/lib\", \"/lib64\", and \"/usr/lib\" are group-owned by \"root\" by using the following command: \n \n $ sudo find /lib /usr/lib /lib64 ! -group root -type d -exec stat -c \"%n %G\" '{}' \\; \n \nIf any systemwide shared library directory is returned, this is a finding.","fixText":"Configure Ubuntu OS library directories to be protected from unauthorized access. Run the following command: \n \n $ sudo find /lib /usr/lib /lib64 ! -group root -type d -exec chgrp root '{}' \\;","ccis":["CCI-001499"]},{"vulnId":"V-275593","ruleId":"SV-275593r1147829_rule","severity":"medium","ruleTitle":"Ubuntu OS library files must be owned by \"root\".","description":"If the operating system were to allow any user to make changes to software libraries, then those changes could be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. \n \nThis requirement applies to operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.","checkContent":"Verify the systemwide shared library files contained in the directories \"/lib\", \"/lib64\", and \"/usr/lib\" are owned by \"root\" by using the following command: \n \n $ sudo find /lib /usr/lib /lib64 ! -user root -type f -exec stat -c \"%n %U\" '{}' \\; \n \nIf any systemwide library file is returned, this is a finding.","fixText":"Configure Ubuntu OS library files to be protected from unauthorized access. Run the following command: \n \n $ sudo find /lib /usr/lib /lib64 ! -user root -type f -exec chown root '{}' \\;","ccis":["CCI-001499"]},{"vulnId":"V-275594","ruleId":"SV-275594r1147832_rule","severity":"medium","ruleTitle":"Ubuntu OS library files must be group-owned by \"root\".","description":"If the operating system were to allow any user to make changes to software libraries, then those changes could be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process. \n \nThis requirement applies to operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs that execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.","checkContent":"Verify the systemwide library files contained in the directories \"/lib\", \"/lib64\", and \"/usr/lib\" are group-owned by \"root\", or a required system account, by using the following command: \n \n $ sudo find /lib /lib64 /usr/lib /usr/lib64 ! -group root -type f -exec stat -c \"%n %G\" '{}' \\; \n \nIf any systemwide shared library file is returned and is not group-owned by a required system account, this is a finding.","fixText":"Configure Ubuntu OS library files to be protected from unauthorized access. \n\nRun the following command, replacing \"\" with any system command not group-owned by \"root\" or a required system account: \n \n $ sudo chgrp root ","ccis":["CCI-001499"]},{"vulnId":"V-275595","ruleId":"SV-275595r1147835_rule","severity":"medium","ruleTitle":"Ubuntu OS must configure the directories used by the system journal to be owned by \"root\".","description":"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 or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.","checkContent":"Verify the /run/log/journal and /var/log/journal directories are owned by \"root\" by using the following command: \n \n $ sudo find /run/log/journal /var/log/journal -type d -exec stat -c \"%n %U\" {} \\; \n /run/log/journal root \n /var/log/journal root \n /var/log/journal/3b018e681c904487b11671b9c1987cce root \n \nIf any output returned is not owned by \"root\", this is a finding.","fixText":"Configure Ubuntu OS to set the appropriate ownership to the directories used by the systemd journal: \n \nAdd or modify the following lines in the \"/usr/lib/tmpfiles.d/systemd.conf\" file: \n \nz /run/log/journal 2640 root systemd-journal - - \nz /var/log/journal 2640 root systemd-journal - - \n \nRestart the system for the changes to take effect.","ccis":["CCI-001316"]},{"vulnId":"V-275596","ruleId":"SV-275596r1147838_rule","severity":"medium","ruleTitle":"Ubuntu OS must configure the directories used by the system journal to be group-owned by \"systemd-journal\".","description":"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 or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.","checkContent":"Verify the /run/log/journal and /var/log/journal directories are group-owned by \"systemd-journal\" by using the following command: \n \n $ sudo find /run/log/journal /var/log/journal -type d -exec stat -c \"%n %G\" {} \\; \n /run/log/journal systemd-journal \n /var/log/journal systemd-journal \n /var/log/journal/3b018e681c904487b11671b9c1987cce systemd-journal \n \nIf any output returned is not group-owned by \"systemd-journal\", this is a finding.","fixText":"Configure Ubuntu OS to set the appropriate group-ownership to the directories used by the systemd journal: \n \nAdd or modify the following lines in the \"/usr/lib/tmpfiles.d/systemd.conf\" file: \n \nz /run/log/journal 2640 root systemd-journal - - \nz /var/log/journal 2640 root systemd-journal - - \n \nRestart the system for the changes to take effect.","ccis":["CCI-001317"]},{"vulnId":"V-275597","ruleId":"SV-275597r1147841_rule","severity":"medium","ruleTitle":"Ubuntu OS must configure the files used by the system journal to be owned by \"root\".","description":"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 or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.","checkContent":"Verify the /run/log/journal and /var/log/journal files are owned by \"root\" by using the following command: \n \n $ sudo find /run/log/journal /var/log/journal -type f -exec stat -c \"%n %U\" {} \\; \n /var/log/journal/3b018e681c904487b11671b9c1987cce/system@99dcc72bb1134aaeae4bf157aa7606f4-0000000000003c7a-0006073f8d1c0fec.journal root \n /var/log/journal/3b018e681c904487b11671b9c1987cce/system.journal root \n /var/log/journal/3b018e681c904487b11671b9c1987cce/user-1000.journal root \n /var/log/journal/3b018e681c904487b11671b9c1987cce/user-1000@bdedf14602ff4081a77dc7a6debc8626-00000000000062a6-00060b4b414b617a.journal root \n /var/log/journal/3b018e681c904487b11671b9c1987cce/system@99dcc72bb1134aaeae4bf157aa7606f4-0000000000005301-000609a409\n593.journal root \n /var/log/journal/3b018e681c904487b11671b9c1987cce/system@99dcc72bb1134aaeae4bf157aa7606f4-0000000000000001-000604dae53225ee.journal root \n /var/log/journal/3b018e681c904487b11671b9c1987cce/user-1000@bdedf14602ff4081a77dc7a6debc8626-000000000000083b-000604dae72c7e3b.journal root \n \nIf any output returned is not owned by \"root\", this is a finding.","fixText":"Configure Ubuntu OS to set the appropriate ownership to the files used by the systemd journal: \n \nAdd or modify the following lines in the \"/usr/lib/tmpfiles.d/systemd.conf\" file: \n \nZ /run/log/journal/%m ~2640 root systemd-journal - - \nz /var/log/journal/%m 2640 root systemd-journal - - \nz /var/log/journal/%m/system.journal 0640 root systemd-journal - - \n \nRestart the system for the changes to take effect.","ccis":["CCI-001318"]},{"vulnId":"V-275598","ruleId":"SV-275598r1147844_rule","severity":"medium","ruleTitle":"Ubuntu OS must configure the files used by the system journal to be group-owned by \"systemd-journal\".","description":"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 or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.","checkContent":"Verify the /run/log/journal and /var/log/journal files are group-owned by \"systemd-journal\" by using the following command: \n \n $ sudo find /run/log/journal /var/log/journal -type f -exec stat -c \"%n %G\" {} \\; \n /var/log/journal/3b018e681c904487b11671b9c1987cce/system@99dcc72bb1134aaeae4bf157aa7606f4-0000000000003c7a-0006073f8d1c0fec.journal systemd-journal \n /var/log/journal/3b018e681c904487b11671b9c1987cce/system.journal systemd-journal \n /var/log/journal/3b018e681c904487b11671b9c1987cce/user-1000.journal systemd-journal \n /var/log/journal/3b018e681c904487b11671b9c1987cce/user-1000@bdedf14602ff4081a77dc7a6debc8626-00000000000062a6-00060b4b414b617a.journal systemd-journal \n /var/log/journal/3b018e681c904487b11671b9c1987cce/system@99dcc72bb1134aaeae4bf157aa7606f4-0000000000005301-000609a409\n593.journal systemd-journal \n /var/log/journal/3b018e681c904487b11671b9c1987cce/system@99dcc72bb1134aaeae4bf157aa7606f4-0000000000000001-000604dae53225ee.journal systemd-journal \n /var/log/journal/3b018e681c904487b11671b9c1987cce/user-1000@bdedf14602ff4081a77dc7a6debc8626-000000000000083b-000604dae72c7e3b.journal systemd-journal \n \nIf any output returned is not group-owned by \"systemd-journal\", this is a finding.","fixText":"Configure Ubuntu OS to set the appropriate group-ownership to the files used by the systemd journal: \n \nAdd or modify the following line in the \"/usr/lib/tmpfiles.d/systemd.conf\" file: \n \nZ /run/log/journal/%m ~2640 root systemd-journal - - \nz /var/log/journal/%m 2640 root systemd-journal - - \nz /var/log/journal/%m/system.journal 0640 root systemd-journal - - \n \nRestart the system for the changes to take effect.","ccis":["CCI-001319"]},{"vulnId":"V-275599","ruleId":"SV-275599r1147847_rule","severity":"medium","ruleTitle":"Ubuntu OS must be configured so that the \"journalctl\" command is owned by \"root\".","description":"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 or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.","checkContent":"Verify that the \"journalctl\" command is owned by \"root\" by using the following command: \n \n $ sudo find /usr/bin/journalctl -exec stat -c \"%n %U\" {} \\; \n /usr/bin/journalctl root \n \nIf \"journalctl\" is not owned by \"root\", this is a finding.","fixText":"Configure \"journalctl\" to be owned by \"root\": \n \n $ sudo chown root /usr/bin/journalctl","ccis":["CCI-001320"]},{"vulnId":"V-275600","ruleId":"SV-275600r1147850_rule","severity":"medium","ruleTitle":"Ubuntu OS must be configured so that the \"journalctl\" command is group-owned by \"root\".","description":"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 or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.","checkContent":"Verify that the \"journalctl\" command is group-owned by \"root\" by using the following command: \n \n $ sudo find /usr/bin/journalctl -exec stat -c \"%n %G\" {} \\; \n /usr/bin/journalctl root \n \nIf \"journalctl\" is not group-owned by \"root\", this is a finding.","fixText":"Configure \"journalctl\" to be group-owned by \"root\": \n \n $ sudo chown :root /usr/bin/journalctl","ccis":["CCI-001321"]},{"vulnId":"V-275601","ruleId":"SV-275601r1147853_rule","severity":"medium","ruleTitle":"Ubuntu OS must configure audit tools to be owned by \"root\".","description":"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. \n \nOperating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys to make access decisions regarding the access to audit tools. \n \nAudit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.","checkContent":"Verify Ubuntu OS configures the audit tools to be owned by \"root\" to prevent any unauthorized access with the following command: \n \n $ stat -c \"%n %U\" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/audispd* /sbin/augenrules \n /sbin/auditctl root \n /sbin/aureport root \n /sbin/ausearch root \n /sbin/autrace root \n /sbin/auditd root \n /sbin/audispd-zos-remote root \n /sbin/augenrules root \n \nIf any of the audit tools are not owned by \"root\", this is a finding.","fixText":"Configure the audit tools on Ubuntu OS to be protected from unauthorized access by setting the file owner as root using the following command: \n \n $ sudo chown root \n \nReplace \"\" with each audit tool not owned by \"root\".","ccis":["CCI-001493","CCI-001494"]},{"vulnId":"V-275602","ruleId":"SV-275602r1147856_rule","severity":"medium","ruleTitle":"Ubuntu OS must configure the \"/var/log\" directory to be owned by \"root\".","description":"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 or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.","checkContent":"Verify Ubuntu OS configures the \"/var/log\" directory to be owned by \"root\" by using the following command: \n \n $ stat -c \"%n %U\" /var/log \n /var/log root \n \nIf the \"/var/log\" directory is not owned by \"root\", this is a finding.","fixText":"Configure Ubuntu OS to have root own the \"/var/log\" directory by using the following command: \n \n $ sudo chown root /var/log","ccis":["CCI-001321"]},{"vulnId":"V-275603","ruleId":"SV-275603r1147859_rule","severity":"medium","ruleTitle":"Ubuntu OS must configure the \"/var/log\" directory to be group-owned by \"syslog\".","description":"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 or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.","checkContent":"Verify that Ubuntu OS configures the \"/var/log\" directory to be group-owned by \"syslog\" by using the following command: \n \n $ stat -c \"%n %G\" /var/log \n /var/log syslog \n \nIf the \"/var/log\" directory is not group-owned by \"syslog\", this is a finding.","fixText":"Configure Ubuntu OS to have syslog group-own the \"/var/log\" directory by using the following command: \n \n $ sudo chgrp syslog /var/log","ccis":["CCI-001321"]},{"vulnId":"V-275604","ruleId":"SV-275604r1147862_rule","severity":"medium","ruleTitle":"Ubuntu OS must configure \"/var/log/syslog\" file to be owned by \"syslog\".","description":"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 or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.","checkContent":"Verify that Ubuntu OS configures the \"/var/log/syslog\" file to be owned by \"syslog\" by using the following command: \n \n $ stat -c \"%n %U\" /var/log/syslog \n /var/log/syslog \n \nIf the \"/var/log/syslog\" file is not owned by \"syslog\", this is a finding.","fixText":"Configure Ubuntu OS to have syslog own the \"/var/log/syslog\" file by using the following command: \n \n $ sudo chown syslog /var/log/syslog","ccis":["CCI-001321"]},{"vulnId":"V-275605","ruleId":"SV-275605r1147865_rule","severity":"medium","ruleTitle":"Ubuntu OS must configure the \"/var/log/syslog\" file to be group-owned by \"adm\".","description":"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 or their designated representatives. \n \nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.","checkContent":"Verify that Ubuntu OS configures the \"/var/log/syslog\" file to be group-owned by \"adm\" by using the following command: \n \n $ stat -c \"%n %G\" /var/log/syslog \n /var/log/syslog adm \n \nIf the \"/var/log/syslog\" file is not group-owned by \"adm\", this is a finding.","fixText":"Configure Ubuntu OS to have adm group-own the \"/var/log/syslog\" file by using the following command: \n \n $ sudo chgrp adm /var/log/syslog","ccis":["CCI-001321"]},{"vulnId":"V-275606","ruleId":"SV-275606r1147868_rule","severity":"medium","ruleTitle":"Ubuntu OS must be configured so that the \"journalctl\" command is not accessible by unauthorized users.","description":"Any operating system providing too much information in error messages risks compromising the data and security of the structure, and content of error messages needs to be carefully considered by the organization. \n \nOrganizations carefully consider the structure/content of error messages. The extent to which information systems are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, erroneous logon attempts with passwords entered in error as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information, such as account numbers, social security numbers, and credit card numbers.","checkContent":"Verify that the \"journalctl\" command has a permission set of \"740\" by using the following command: \n \n $ sudo find /usr/bin/journalctl -exec stat -c \"%n %a\" {} \\; \n /usr/bin/journalctl 740 \n \nIf \"journalctl\" is not set to \"740\", this is a finding.","fixText":"Configure \"journalctl\" to have a permission set of \"740\": \n \n $ sudo chmod 740 /usr/bin/journalctl","ccis":["CCI-001312"]},{"vulnId":"V-275607","ruleId":"SV-275607r1147871_rule","severity":"medium","ruleTitle":"Ubuntu OS must set a sticky bit on all public directories to prevent unauthorized and unintended information transferred via shared system resources.","description":"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., registers, main memory, hard disks) after those resources have been released back to information systems. The control of information in shared resources is also commonly referred to as object reuse and residual information protection. \n \nThis requirement generally applies to the design of an information technology product, but it can also apply to the configuration of particular information system components that are, or use, such products. This can be verified by acceptance/validation processes in DOD or other government agencies. \n \nThere may be shared resources with configurable protections (e.g., files in storage) that may be assessed on specific information system components.","checkContent":"Verify that all public directories have the public sticky bit set by using the following command: \n \n $ sudo find / -type d -perm -002 ! -perm -1000 \n \nIf any public directories are found missing the sticky bit, this is a finding.","fixText":"Configure all public directories to have the sticky bit set to prevent unauthorized and unintended information transferred via shared system resources. \n \nSet the sticky bit on all public directories using the following command, replacing \"\" with any directory path missing the sticky bit: \n \n $ sudo chmod +t ","ccis":["CCI-001090"]},{"vulnId":"V-275608","ruleId":"SV-275608r1147874_rule","severity":"medium","ruleTitle":"Ubuntu OS must have an application firewall installed to control remote access methods.","description":"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. \n \nRemote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. \n \nUbuntu OS functionality (e.g., RDP) must be capable of taking enforcement action if the audit reveals unauthorized activity. Automated control of remote access sessions allows organizations to ensure ongoing compliance with remote access policies by enforcing connection rules of remote access applications on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets).","checkContent":"Verify the Uncomplicated Firewall (ufw) is installed by using the following command: \n \n $ dpkg -l | grep ufw \n ii ufw 0.36.1-4ubuntu0.1 all program for managing a Netfilter firewall \n \nIf the \"ufw\" package is not installed, ask the system administrator if another application firewall is installed. \n \nIf no application firewall is installed, this is a finding.","fixText":"Install the ufw by using the following command: \n \n $ sudo apt-get install ufw","ccis":["CCI-002314"]},{"vulnId":"V-275609","ruleId":"SV-275609r1147877_rule","severity":"medium","ruleTitle":"Ubuntu OS must enable and run the Uncomplicated Firewall (ufw).","description":"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. \n \nRemote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. \n \nUbuntu OS functionality (e.g., RDP) must be capable of taking enforcement action if the audit reveals unauthorized activity. Automated control of remote access sessions allows organizations to ensure ongoing compliance with remote access policies by enforcing connection rules of remote access applications on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets).","checkContent":"Verify the ufw is enabled on the system with the following command: \n \n $ sudo ufw status \n Status: active \n \nIf the above command returns the status as \"inactive\" or any type of error, this is a finding.","fixText":"Enable the ufw by using the following command: \n \n $ sudo ufw enable","ccis":["CCI-002314"]},{"vulnId":"V-275610","ruleId":"SV-275610r1147880_rule","severity":"medium","ruleTitle":"Ubuntu OS must have an application firewall enabled.","description":"Firewalls protect computers from network attacks by blocking or limiting access to open network ports. Application firewalls limit which applications are allowed to communicate over the network.","checkContent":"Verify the Uncomplicated Firewall (ufw) is enabled on the system with the following command: \n \n $ systemctl status ufw.service | grep -i \"active:\" \n Active: active (exited) since Thu 2022-12-25 00:00:01 NZTD; 365 days 11h ago \n \nIf \"ufw.service\" is \"inactive\", this is a finding. \n \nIf the ufw is not installed, ask the system administrator if another application firewall is installed. If no application firewall is installed, this is a finding.","fixText":"Enable and start the ufw by using the following command: \n \n $ sudo systemctl enable ufw.service --now","ccis":["CCI-000366"]},{"vulnId":"V-275611","ruleId":"SV-275611r1147883_rule","severity":"medium","ruleTitle":"Ubuntu OS must configure the Uncomplicated Firewall (ufw) to rate limit impacted network interfaces.","description":"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. \n \nThis requirement addresses the configuration of the operating system to mitigate the impact of DoS attacks that have occurred or are ongoing on system availability. For each system, known and potential DoS attacks must be identified and solutions for each type implemented. A variety of technologies exist to limit or, in some cases, eliminate the effects of DoS attacks (e.g., limiting processes or establishing memory partitions). Employing increased capacity and bandwidth, combined with service redundancy, may reduce the susceptibility to some DoS attacks.","checkContent":"Verify an application firewall is configured to rate limit any connection to the system. \n \nCheck all the services listening to the ports by using the following command: \n \n $ ss -l46ut \n Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process \n tcp LISTEN 0 511 *:http *:* \n tcp LISTEN 0 128 [::]:ssh \n tcp LISTEN 0 128 [::]:ipp [::]:* \n tcp LISTEN 0 128 [::]:smtp [::]:* \n \n \nFor each entry, verify that the ufw is configured to rate limit the service ports by using the following command: \n \n $ sudo ufw status \n Status: active \n \n To Action From \n -- ------ ---- \n 80/tcp LIMIT Anywhere \n 25/tcp LIMIT Anywhere \n Anywhere DENY 240.9.19.81 \n 443 LIMIT Anywhere \n 22/tcp LIMIT Anywhere \n 80/tcp (v6) LIMIT Anywhere \n 25/tcp (v6) LIMIT Anywhere \n 22/tcp (v6) LIMIT Anywhere (v6) \n \n 25 DENY OUT Anywhere \n 25 (v6) DENY OUT Anywhere (v6) \n \nIf any port with a state of \"LISTEN\" that does not have an action of \"DENY\", is not marked with the \"LIMIT\" action, this is a finding.","fixText":"Configure the application firewall to protect against or limit the effects of DoS attacks by ensuring Ubuntu OS is implementing rate-limiting measures on impacted network interfaces. \n \nFor each service with a port listening to connections, run the following command, replacing \"\" with the service that needs to be rate limited. \n \n $ sudo ufw limit \n \nRate-limiting can also be done on an interface. An example of adding a rate limit on the \"ens160\" interface follows: \n \n $ sudo ufw limit in on ens160","ccis":["CCI-002385"]},{"vulnId":"V-275612","ruleId":"SV-275612r1147886_rule","severity":"medium","ruleTitle":"Ubuntu OS 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 Category Assurance List (PPSM CAL) and vulnerability assessments.","description":"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. \n \nOperating systems are capable of providing a variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component. \n\nTo support the requirements and principles of least functionality, the operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.","checkContent":"Check the firewall configuration for any unnecessary or prohibited functions, ports, protocols, and/or services by using the following command: \n \n $ sudo ufw show raw \n Chain INPUT (policy ACCEPT 0 packets, 0 bytes) \n pkts bytes target prot opt in out source destination \n \n Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) \n pkts bytes target prot opt in out source destination \n \n Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes) \n pkts bytes target prot opt in out source destination \n \nAsk the system administrator for the site or program PPSM Components Local Services Assessment (CLSA). Verify the services allowed by the firewall match the PPSM CLSA. \n \nIf there are any additional ports, protocols, or services that are not included in the PPSM CLSA, this is a finding. \n \nIf there are any ports, protocols, or services that are prohibited by the PPSM CAL, this is a finding.","fixText":"Add all ports, protocols, or services allowed by the PPSM CLSA by using the following command: \n \n $ sudo ufw allow \n \nWhere the direction is \"in\" or \"out\" and the port is the one corresponding to the protocol or service allowed. \n \nTo deny access to ports, protocols, or services, use: \n \n $ sudo ufw deny ","ccis":["CCI-000382"]},{"vulnId":"V-275613","ruleId":"SV-275613r1149439_rule","severity":"medium","ruleTitle":"Ubuntu OS must compare internal information system clocks at least every 24 hours with a server 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) to synchronize clocks between NetIM components.","description":"Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time 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. \n \nSynchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. \n \nOrganizations should consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints). \n \nNote that USNO offers authenticated NTP service to DOD and U.S. Government agencies operating on the NIPR and SIPR networks. Visit https://www.usno.navy.mil/USNO/time/ntp/DOD-customers for more information.\n\nSatisfies: SRG-OS-000355-GPOS-00143, SRG-OS-000785-GPOS-00250","checkContent":"Verify Ubuntu OS is configured to compare the system clock at least every 24 hours to the authoritative time source by using the following command: \n \nNote: If the system is not networked, this requirement is not applicable. \n \n $ sudo grep maxpoll -ir /etc/chrony* \n server tick.usno.navy.mil iburst maxpoll 16 \n \nIf the \"maxpoll\" option is set to a number greater than 16, the line is commented out, or is missing, this is a finding. \n \nVerify that the \"chrony.conf\" file is configured to an authoritative DOD time source by using the following command: \n \n $ sudo grep -ir server /etc/chrony* \n server tick.usno.navy.mil iburst maxpoll 16 \n server tock.usno.navy.mil iburst maxpoll 16 \n server ntp2.usno.navy.mil iburst maxpoll 16 \n \nIf \"server\" is not defined, is not set to an authoritative DOD time source, is commented out, or missing, this is a finding.","fixText":"Configure Ubuntu OS to compare the system clock at least every 24 hours to the authoritative time source. \n \nAdd or modify the following line in the \"/etc/chrony/chrony.conf\" file: \n \nserver [source] iburst maxpoll = 16 \n \nRestart \"chrony.service\" for the changes to take effect by using the following command: \n \n $ sudo systemctl restart chrony.service","ccis":["CCI-004923"]},{"vulnId":"V-275614","ruleId":"SV-275614r1147892_rule","severity":"medium","ruleTitle":"Ubuntu OS must synchronize internal information system clocks to the authoritative time source when the time difference is greater than one second.","description":"Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. \n \nSynchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. Organizations should consider setting time periods for different types of systems (e.g., financial, legal, or mission-critical systems). \n \nOrganizations must also consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints). This requirement is related to the comparison done every 24 hours in SRG-OS-000355 to determine the time difference.","checkContent":"Verify Ubuntu OS synchronizes internal system clocks to the authoritative time source when the time difference is greater than one second. \n \nNote: If the system is not networked, this requirement is not applicable. \n \nCheck the value of \"makestep\" by using the following command: \n \n $ grep -ir makestep /etc/chrony* \n makestep 1 -1 \n \nIf \"makestep\" is not set to \"1 -1\", is commented out, or is missing, this is a finding. \n \nVerify the NTP service is active and the system clock is synchronized with the authoritative time source: \n \n $ timedatectl | grep -Ei '(synchronized|service)' \n System clock synchronized: yes \n NTP service: active \n \nIf the NTP service is not active, this is a finding.\n\nIf the system clock is not synchronized, this is a finding.","fixText":"Configure chrony to synchronize the internal system clocks to the authoritative source when the time difference is greater than one second by doing the following: \n \nEdit the \"/etc/chrony/chrony.conf\" file and add: \n \n makestep 1 -1 \n \nRestart the chrony service: \n \n $ sudo systemctl restart chrony.service","ccis":["CCI-004926"]},{"vulnId":"V-275615","ruleId":"SV-275615r1147895_rule","severity":"low","ruleTitle":"Ubuntu OS must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC).","description":"If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. \n \nTime stamps generated by the operating system include date and time. Time is commonly expressed in UTC or local time with an offset from UTC.\n\nSatisfies: SRG-OS-000359-GPOS-00146, SRG-OS-000055-GPOS-00026","checkContent":"Verify the time zone is configured to use UTC by using the following command: \n \n $ timedatectl status | grep -i \"time zone\" \n Time zone: Etc/UTC (UTC, +0000) \n \nIf \"Time zone\" is not set to UTC, this is a finding.","fixText":"To Configure Ubuntu OS time zone to use UTC, run the following command:\n \n $ sudo timedatectl set-timezone Etc/UTC","ccis":["CCI-001890","CCI-000159"]},{"vulnId":"V-275616","ruleId":"SV-275616r1147898_rule","severity":"medium","ruleTitle":"Ubuntu OS must be configured to use TCP syncookies.","description":"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. \n \nManaging excess capacity ensures that sufficient capacity is available to counter flooding attacks. Employing increased capacity and service redundancy may reduce the susceptibility to some DoS attacks. Managing excess capacity may include, for example, establishing selected usage priorities, quotas, or partitioning.","checkContent":"Verify Ubuntu OS is configured to use TCP syncookies by using the following command: \n \n $ sysctl net.ipv4.tcp_syncookies \n net.ipv4.tcp_syncookies = 1 \n \nIf the value is not \"1\", this is a finding. \n \nCheck the saved value of TCP syncookies by using the following command: \n \n $ sudo grep -ir net.ipv4.tcp_syncookies /etc/sysctl.d/*.conf /run/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf 2> /dev/null \n \nIf the \"net.ipv4.tcp_syncookies\" option is not set to \"1\", is commented out, or is missing, this is a finding. \n \nIf conflicting results are returned, this is a finding.","fixText":"Configure Ubuntu OS to use TCP syncookies by using the following command: \n \n $ sudo sysctl -w net.ipv4.tcp_syncookies=1 \n \nIf \"1\" is not the system's default value, add or update the following line in \"/etc/sysctl.conf\": \n \n net.ipv4.tcp_syncookies = 1","ccis":["CCI-001095"]},{"vulnId":"V-275617","ruleId":"SV-275617r1148290_rule","severity":"medium","ruleTitle":"Ubuntu OS must restrict SSH access to allow only NetIM internal communication.","description":"Remote access is not authorized for connection to the Riverbed NetIM shell to minimize and deter system administrators from accessing the shell, bash commands, or root account remotely. Though the device is not critical to the infrastructure, compromise of this device at the OS level could lead to compromise of other devices on the network.","checkContent":"Verify firewall rule exists to restrict SSH to allow specific IP addresses only by using the following commands:\n\n$ sudo ufw status\n\nIf a firewall rule does not exist to restrict port 22 to allow specific IP addresses and deny all other address, this is a finding.","fixText":"Deny all other SSH connections and allow SSH connections from a specific IP address by using the following commands. Allow from NetIM core/worker(s)/manager in a base configuration with UFW allow. \n\n$ sudo ufw deny from any to any port 22\n$ sudo ufw allow from to any port 22\n\nWhere NETIM_IP_ADDRESS list are the list of NETIM IP addresses for all nodes.\n\nNote: This will restrict system admins to use of the CONSOLE mechanism available depending on the Virtual Platform being used.","ccis":["CCI-002418","CCI-002420","CCI-002422"]},{"vulnId":"V-275619","ruleId":"SV-275619r1147907_rule","severity":"medium","ruleTitle":"Ubuntu OS must display the Standard Mandatory DOD Notice and Consent Banner before granting any user connection to the OS.","description":"Display of a standardized and approved use notification before granting access to the publicly accessible operating system ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.\n\nSystem use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist.\n\nThe banner must be formatted in accordance with applicable DOD policy.\n\nSatisfies: SRG-OS-000228-GPOS-00088, SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007","checkContent":"Verify Ubuntu 22.04 LTS displays the Standard Mandatory DOD Notice and Consent Banner before granting access to Ubuntu 22.04 LTS via an SSH logon by using the following command: \n \n $ sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\\r' | tr '\\n' ' ' | xargs sudo grep -iH 'banner' \n /etc/ssh/sshd_config:Banner /etc/issue.net \n \nThe command will return the banner option along with the name of the file that contains the SSH banner. If the line is commented out, missing, or conflicting results are returned, this is a finding. \n \nVerify the specified banner file matches the Standard Mandatory DOD Notice and Consent Banner exactly: \n \n $ cat /etc/issue.net \n You are accessing a U.S. Government (USG) Information System (IS) that is \n provided for USG-authorized use only. By using this IS (which includes any \n device attached to this IS), you consent to the following conditions: \n -The USG routinely intercepts and monitors communications on this IS for \n purposes including, but not limited to, penetration testing, COMSEC monitoring, \n network operations and defense, personnel misconduct (PM), law enforcement \n (LE), and counterintelligence (CI) investigations. \n -At any time, the USG may inspect and seize data stored on this IS. \n -Communications using, or data stored on, this IS are not private, are subject \n to routine monitoring, interception, and search, and may be disclosed or used \n for any USG-authorized purpose. \n -This IS includes security measures (e.g., authentication and access controls) \n to protect USG interests--not for your personal benefit or privacy. \n -Notwithstanding the above, using this IS does not constitute consent to PM, LE \n or CI investigative searching or monitoring of the content of privileged \n communications, or work product, related to personal representation or services \n by attorneys, psychotherapists, or clergy, and their assistants. Such \n communications and work product are private and confidential. See User \n Agreement for details. \n \nIf the banner text does not match the Standard Mandatory DOD Notice and Consent Banner exactly, this is a finding.","fixText":"Set the parameter Banner in \"/etc/ssh/sshd_config\" to point to the \"/etc/issue.net\" file: \n \n $ sudo sed -i '/^Banner/d' /etc/ssh/sshd_config \n $ sudo sed -i '$aBanner /etc/issue.net' /etc/ssh/sshd_config \n \nReplace the text in \"/etc/issue.net\" with the Standard Mandatory DOD Notice and Consent Banner: \n \nYou are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions:\n\n-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. \n-At any time, the USG may inspect and seize data stored on this IS. \n-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. \n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. \n-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. \n \nRestart the SSH daemon for the changes to take effect and then signal the SSH server to reload the configuration file: \n \n $ sudo systemctl -s SIGHUP kill sshd","ccis":["CCI-001384","CCI-001385","CCI-001386","CCI-001387","CCI-001388","CCI-000048","CCI-000050"]},{"vulnId":"V-275620","ruleId":"SV-275620r1147910_rule","severity":"high","ruleTitle":"Ubuntu OS must not allow unattended or automatic login via SSH.","description":"Failure to restrict system access to authenticated users negatively impacts Ubuntu OS security.","checkContent":"Verify unattended or automatic login via SSH is disabled by using the following command: \n \n $ sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\\r' | tr '\\n' ' ' | xargs sudo grep -iEH '(permit(.*?)(passwords|environment))' \n /etc/ssh/sshd_config:PermitEmptyPasswords no \n /etc/ssh/sshd_config:PermitUserEnvironment no \n \nIf \"PermitEmptyPasswords\" and \"PermitUserEnvironment\" are not set to \"no\", are commented out, are missing, or conflicting results are returned, this is a finding.","fixText":"Configure the SSH server to not allow unattended or automatic login to the system. \n \nAdd or modify the following lines in the \"/etc/ssh/sshd_config\" file: \n \nPermitEmptyPasswords no \nPermitUserEnvironment no \n \nRestart the SSH daemon for the changes to take effect: \n \n $ sudo systemctl restart sshd.service","ccis":["CCI-000366"]},{"vulnId":"V-275621","ruleId":"SV-275621r1147913_rule","severity":"medium","ruleTitle":"Ubuntu OS must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive.","description":"Terminating an unresponsive 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 committed by the managed network element. \n \nTerminating network connections associated with communications sessions includes, for example, deallocating associated TCP/IP address/port pairs at the operating system level and deallocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean the operating system terminates all sessions or network access; it only ends the unresponsive session and releases the resources associated with that session.","checkContent":"Verify the SSH server automatically terminates a user session after the SSH client has been unresponsive for 10 minutes by using the following command: \n \n $ sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\\r' | tr '\\n' ' ' | xargs sudo grep -iH 'clientaliveinterval' \n /etc/ssh/sshd_config:ClientAliveInterval 600 \n \nIf \"ClientAliveInterval\" does not exist, is not set to a value of \"600\" or less, if conflicting results are returned, is commented out, or is missing, this is a finding.","fixText":"Configure the SSH server to terminate a user session automatically after the SSH client has been unresponsive for 10 minutes. \n \nNote: This setting must be applied in conjunction with RIIM-OS-255040 to function correctly. \n \nAdd or modify the following line in the \"/etc/ssh/sshd_config\" file: \n \nClientAliveInterval 600 \n \nRestart the SSH daemon for the changes to take effect: \n \n $ sudo systemctl restart sshd.service","ccis":["CCI-001133"]},{"vulnId":"V-275622","ruleId":"SV-275622r1147916_rule","severity":"medium","ruleTitle":"Ubuntu OS must be configured so that remote X connections are disabled, unless to fulfill documented and validated mission requirements.","description":"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. For example, a system administrator needs to protect clients from exposing themselves to attack by unwittingly requesting X11 forwarding, which can warrant a ''no'' setting. \n \nX11 forwarding must be enabled with caution. Users with the ability to bypass file permissions on the remote host (for the user's X11 authorization database) can access the local X11 display through the forwarded connection. An attacker could then perform activities such as keystroke monitoring if the ForwardX11Trusted option is also enabled. \n \nIf X11 services are not required for the system's intended function, they should be disabled or restricted as appropriate to the system's needs.","checkContent":"Verify X11 forwarding is disabled by using the following command: \n \n $ sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\\r' | tr '\\n' ' ' | xargs sudo grep -iH 'x11forwarding' \n /etc/ssh/sshd_config:X11Forwarding no \n \nIf \"X11Forwarding\" is set to \"yes\" and is not documented with the information system security officer as an operational requirement, is commented out, is missing, or conflicting results are returned, this is a finding.","fixText":"Configure the SSH server to disable X11 forwarding. \n \nAdd or modify the following line in the \"/etc/ssh/sshd_config\" file: \n \nX11Forwarding no \n \nRestart the SSH daemon for the changes to take effect: \n \n $ sudo systemctl restart sshd.service","ccis":["CCI-000366"]},{"vulnId":"V-275623","ruleId":"SV-275623r1147919_rule","severity":"medium","ruleTitle":"Ubuntu OS SSH daemon must prevent remote hosts from connecting to the proxy display.","description":"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 on the wildcard address. By default, sshd binds the forwarding server to the loopback address and sets the hostname part of the DISPLAY environment variable to localhost. This prevents remote hosts from connecting to the proxy display.","checkContent":"Verify the SSH server prevents remote hosts from connecting to the proxy display by using the following command: \n \n $ sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\\r' | tr '\\n' ' ' | xargs sudo grep -iH 'x11uselocalhost' \n /etc/ssh/sshd_config:X11UseLocalhost yes \n \nIf \"X11UseLocalhost\" is set to \"no\", is commented out, is missing, or conflicting results are returned, this is a finding.","fixText":"Configure the SSH server to prevent remote hosts from connecting to the proxy display. \n \nAdd or modify the following line in the \"/etc/ssh/sshd_config\" file: \n \nX11UseLocalhost yes \n \nRestart the SSH daemon for the changes to take effect: \n \n $ sudo systemctl restart sshd.service","ccis":["CCI-000366"]},{"vulnId":"V-275624","ruleId":"SV-275624r1147922_rule","severity":"medium","ruleTitle":"Ubuntu OS must configure the SSH daemon to use FIPS 140-2/140-3 approved ciphers to prevent the unauthorized disclosure of information and/or detect changes to information during transmission.","description":"Without cryptographic integrity protections, information can be altered by unauthorized users without detection. \n \nRemote access (e.g., RDP) is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. \n \nNonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the internet) or an internal network. \n \nLocal maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. \n \nEncrypting information for transmission protects information from unauthorized disclosure and modification. Cryptographic mechanisms implemented to protect information integrity include, for example, cryptographic hash functions which have common application in digital signatures, checksums, and message authentication codes. \n \nBy specifying a cipher list with the order of ciphers being in a \"strongest to weakest\" orientation, the system will automatically attempt to use the strongest cipher for securing SSH connections.\n\nSatisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000394-GPOS-00174, SRG-OS-000424-GPOS-00188","checkContent":"Verify the SSH server is configured to only implement FIPS-approved ciphers with the following command: \n \n $ sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\\r' | tr '\\n' ' ' | xargs sudo grep -iH 'ciphers' \n /etc/ssh/sshd_config:Ciphers aes256-ctr,aes256-gcm@openssh.com,aes192-ctr,aes128-ctr,aes128-gcm@openssh.com \n \nIf \"Ciphers\" does not contain only the ciphers \"aes256-ctr,aes256-gcm@openssh.com,aes192-ctr,aes128-ctr,aes128-gcm@openssh.com\" in exact order, is commented out, is missing, or conflicting results are returned, this is a finding.","fixText":"Configure the SSH server to only implement FIPS-approved ciphers. \n \nAdd or modify the following line in the \"/etc/ssh/sshd_config\" file: \n \nCiphers aes256-ctr,aes256-gcm@openssh.com,aes192-ctr,aes128-ctr,aes128-gcm@openssh.com \n \nRestart the SSH server for the changes to take effect: \n \n $ sudo systemctl restart sshd.service","ccis":["CCI-000068","CCI-002421","CCI-003123"]},{"vulnId":"V-275625","ruleId":"SV-275625r1147925_rule","severity":"high","ruleTitle":"Ubuntu OS must configure the SSH daemon to use Message Authentication Codes (MACs) employing FIPS 140-2/140-3 -approved cryptographic hashes to prevent the unauthorized disclosure of information and/or detect changes to information during transmission.","description":"Without cryptographic integrity protections, information can be altered by unauthorized users without detection. \n \nRemote access (e.g., RDP) is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the internet) or an internal network. \n \nLocal maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. \n \nEncrypting information for transmission protects information from unauthorized disclosure and modification. Cryptographic mechanisms implemented to protect information integrity include, for example, cryptographic hash functions, which have common application in digital signatures, checksums, and message authentication codes.\n\nSatisfies: SRG-OS-000250-GPOS-00093, SRG-OS-000393-GPOS-00173, SRG-OS-000424-GPOS-00188","checkContent":"Verify the SSH server is configured to only use MACs that employ FIPS 140-2/140-3-approved ciphers by using the following command: \n \n $ sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\\r' | tr '\\n' ' ' | xargs sudo grep -iH 'macs' \n /etc/ssh/sshd_config:MACs hmac-sha2-512,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha2-256-etm@openssh.com \n \nIf \"MACs\" does not contain only the hashes \"hmac-sha2-512,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha2-256-etm@openssh.com\" in exact order, is commented out, is missing, or conflicting results are returned, this is a finding.","fixText":"Configure the SSH server to only use MACs that employ FIPS 140-2/140-3-approved hashes. \n \nAdd or modify the following line in the \"/etc/ssh/sshd_config\" file: \n \nMACs hmac-sha2-512,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha2-256-etm@openssh.com \n \nRestart the SSH server for the changes to take effect: \n \n $ sudo systemctl reload sshd.service","ccis":["CCI-001453","CCI-002421","CCI-002890"]},{"vulnId":"V-275626","ruleId":"SV-275626r1147928_rule","severity":"high","ruleTitle":"Ubuntu OS SSH server must be configured to use only FIPS-validated key exchange algorithms.","description":"Without cryptographic integrity protections provided by FIPS-validated cryptographic algorithms, information can be viewed and altered by unauthorized users without detection. \n \nThe system will attempt to use the first algorithm presented by the client that matches the server list. Listing the values \"strongest to weakest\" is a method to ensure the use of the strongest algorithm available to secure the SSH connection.","checkContent":"Verify that the SSH server is configured to use only FIPS-validated key exchange algorithms by using the following command: \n \n $ sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\\r' | tr '\\n' ' ' | xargs sudo grep -iH 'kexalgorithms' \n /etc/ssh/sshd_config:KexAlgorithms ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256 \n \nIf \"KexAlgorithms\" does not contain only the algorithms \"ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256\" in exact order, is commented out, is missing, or conflicting results are returned, this is a finding.","fixText":"Configure the SSH server to use only FIPS-validated key exchange algorithms. \n \nAdd or modify the following line in the \"/etc/ssh/sshd_config\" file: \n \nKexAlgorithms ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256 \n \nRestart the SSH server for changes to take effect: \n \n $ sudo systemctl restart sshd.service","ccis":["CCI-000068"]},{"vulnId":"V-275627","ruleId":"SV-275627r1147931_rule","severity":"high","ruleTitle":"Ubuntu OS must use strong authenticators in establishing nonlocal maintenance and diagnostic sessions.","description":"Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. Typically, strong authentication requires authenticators that are resistant to replay attacks and employ multifactor authentication. Strong authenticators include, for example, PKI where certificates are stored on a token protected by a password, passphrase, or biometric.","checkContent":"Verify Ubuntu OS is configured to use strong authenticators in the establishment of nonlocal maintenance and diagnostic maintenance by using the following command: \n \n $ sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\\r' | tr '\\n' ' ' | xargs sudo grep -iH 'usepam' \n /etc/ssh/sshd_config:UsePAM yes \n \nIf \"UsePAM\" is not set to \"yes\", is commented out, is missing, or conflicting results are returned, this is a finding.","fixText":"Configure Ubuntu OS to use strong authentication when establishing nonlocal maintenance and diagnostic sessions. \n \nAdd or modify the following line to /etc/ssh/sshd_config: \n \nUsePAM yes \n \nRestart the SSH server for changes to take effect: \n \n $ sudo systemctl restart sshd.service","ccis":["CCI-000877"]},{"vulnId":"V-275628","ruleId":"SV-275628r1147934_rule","severity":"medium","ruleTitle":"Ubuntu OS must retain a user's session lock until that user reestablishes access using established identification and authentication procedures.","description":"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. \n \nThe session lock is implemented at the point where session activity can be determined. \n \nRegardless of where the session lock is determined and implemented, once invoked, a session lock of Ubuntu OS must remain in place until the user reauthenticates. No other activity aside from reauthentication must unlock the system.","checkContent":"Verify Ubuntu OS has a graphical user interface session lock enabled by using the following command: \n \nNote: If no graphical user interface is installed, this requirement is not applicable. \n \n $ sudo gsettings get org.gnome.desktop.screensaver lock-enabled \n true \n \nIf \"lock-enabled\" is not set to \"true\", is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu OS to allow a user to lock the current graphical user interface session. \n \nCreate or edit a file named /etc/dconf/db/local.d/00-screensaver with the following contents:\n\n[org/gnome/desktop/screensaver]\nlock-enabled=true","ccis":["CCI-000056"]},{"vulnId":"V-275629","ruleId":"SV-275629r1147937_rule","severity":"medium","ruleTitle":"Ubuntu OS must initiate a graphical session lock after 15 minutes of inactivity.","description":"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. \n \nThe session lock is implemented at the point where session activity can be determined. \n \nRegardless of where the session lock is determined and implemented, once invoked, a session lock of Ubuntu OS must remain in place until the user reauthenticates. No other activity aside from reauthentication must unlock the system.","checkContent":"Verify Ubuntu OS has a graphical user interface session lock configured to activate after 15 minutes of inactivity by using the following commands: \n \nNote: If no graphical user interface is installed, this requirement is not applicable. \n \nGet the following settings to verify the graphical user interface session is configured to lock the graphical user session after 15 minutes of inactivity: \n \n $ gsettings get org.gnome.desktop.screensaver lock-enabled \n true \n \n $ gsettings get org.gnome.desktop.screensaver lock-delay \n uint32 0 \n \n $ gsettings get org.gnome.desktop.session idle-delay \n uint32 900 \n \nIf \"lock-enabled\" is not set to \"true\", is commented out, or is missing, this is a finding. \n \nIf \"lock-delay\" is set to a value greater than \"0\", or if \"idle-delay\" is set to a value greater than \"900\", is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu OS to lock the current graphical user interface session after 15 minutes of inactivity. \n\nCreate or edit a file named /etc/dconf/db/local.d/00-screensaver with the following contents:\n\n[org/gnome/desktop/screensaver]\nlock-enabled=true\nlock-delay=0\n\n[org/gnome/desktop/session]\nidle-delay=600","ccis":["CCI-000057"]},{"vulnId":"V-275630","ruleId":"SV-275630r1147940_rule","severity":"medium","ruleTitle":"Ubuntu OS must disable the x86 Ctrl-Alt-Delete key sequence if a graphical user interface is installed.","description":"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 the graphical environment, risk of unintentional reboot from the Ctrl-Alt-Delete sequence is reduced because the user will be prompted before any action is taken.","checkContent":"Verify Ubuntu OS is not configured to reboot the system when Ctrl-Alt-Delete is pressed when using a graphical user interface by using the following command: \n \nNote: If no graphical user interface is installed, this requirement is not applicable. \n \n $ gsettings get org.gnome.settings-daemon.plugins.media-keys logout \n @as [] \n \nIf the \"logout\" key is bound to an action, is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu OS to disable the Ctrl-Alt-Delete sequence when using a graphical user interface.\n\nCreate or edit a file named /etc/dconf/db/local.d/00-screensaver with the following contents:\n\n[org/gnome/settings-daemon/plugins/media-keys]\nlogout=\"\"\n\nUpdate the dconf settings:\n\n$ sudo dconf update","ccis":["CCI-000366"]},{"vulnId":"V-275631","ruleId":"SV-275631r1147943_rule","severity":"medium","ruleTitle":"Ubuntu OS must disable automatic mounting of Universal Serial Bus (USB) mass storage driver.","description":"Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. \n \nPeripherals include, but are not limited to, such devices as flash drives, external storage, and printers.\n\nSatisfies: SRG-OS-000378-GPOS-00163, SRG-OS-000690-GPOS-00140","checkContent":"Verify Ubuntu OS disables ability to load the USB storage kernel module by using the following command: \n \n $ grep usb-storage /etc/modprobe.d/* | grep \"/bin/false\" \n /etc/modprobe.d/stig.conf:install usb-storage /bin/false \n \nIf the command does not return any output, or the line is commented out, this is a finding. \n \nVerify Ubuntu OS disables the ability to use USB mass storage device. \n \n $ grep usb-storage /etc/modprobe.d/* | grep -i \"blacklist\" \n /etc/modprobe.d/stig.conf:blacklist usb-storage \n \nIf the command does not return any output, or the line is commented out, this is a finding.","fixText":"Configure Ubuntu OS to disable using the USB storage kernel module. \n \nCreate and/or append a custom file under \"/etc/modprobe.d/\" to contain the following: \n \n $ sudo su -c \"echo install usb-storage /bin/false >> /etc/modprobe.d/stig.conf\" \n \nConfigure Ubuntu OS to disable the ability to use USB mass storage devices. \n \n $ sudo su -c \"echo blacklist usb-storage >> /etc/modprobe.d/stig.conf\"","ccis":["CCI-001958","CCI-003959"]},{"vulnId":"V-275633","ruleId":"SV-275633r1147949_rule","severity":"medium","ruleTitle":"Ubuntu OS must prevent direct login into the root account.","description":"To ensure individual accountability and prevent unauthorized access, organizational users must be individually identified and authenticated. \n \nA group authenticator is a generic account used by multiple individuals. Use of a group authenticator alone does not uniquely identify individual users. Examples of the group authenticator is the Unix OS \"root\" user account, the Windows \"Administrator\" account, the \"sa\" account, or a \"helpdesk\" account. \n \nFor example, the Unix and Windows operating systems offer a \"switch user\" capability allowing users to authenticate with their individual credentials and, when needed, \"switch\" to the administrator role. This method provides for unique individual authentication prior to using a group authenticator. \n \nUsers (and any processes acting on behalf of users) must be uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization, which outlines specific user actions that can be performed on the operating system without identification or authentication. \n \nRequiring individuals to be authenticated with an individual authenticator prior to using a group authenticator allows for traceability of actions, as well as adding an additional level of protection of the actions that can be taken with group account knowledge.","checkContent":"Verify Ubuntu OS prevents direct logins to the root account by using the following command: \n \n $ sudo passwd -S root \n root L 08/09/2022 0 99999 7 -1 \n \nIf the output does not contain \"L\" in the second field to indicate the account is locked, this is a finding.","fixText":"Configure Ubuntu OS to prevent direct logins to the root account by using the following command: \n \n $ sudo passwd -l root","ccis":["CCI-004045"]},{"vulnId":"V-275634","ruleId":"SV-275634r1147952_rule","severity":"medium","ruleTitle":"Ubuntu OS must uniquely identify interactive users.","description":"To ensure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. \n \nOrganizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and processes acting on behalf of users) must be uniquely identified and authenticated to all accesses, except for the following: \n \n1. Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and \n \n2. Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals in group accounts (e.g., shared privilege accounts) or for detailed accountability of individual activity.\n\nSatisfies: SRG-OS-000104-GPOS-00051, SRG-OS-000121-GPOS-00062","checkContent":"Verify Ubuntu OS contains no duplicate User IDs (UIDs) for interactive users by using the following command: \n \n $ awk -F \":\" 'list[$3]++{print $1, $3}' /etc/passwd \n \nIf output is produced and the accounts listed are interactive user accounts, this is a finding.","fixText":"Edit the file \"/etc/passwd\" and provide each interactive user account that has a duplicate UID with a unique UID.","ccis":["CCI-000764","CCI-000804"]},{"vulnId":"V-275640","ruleId":"SV-275640r1147970_rule","severity":"low","ruleTitle":"Ubuntu OS must enforce a delay of at least four seconds between logon prompts following a failed logon attempt.","description":"Limiting the number of logon attempts over a certain time interval reduces the chances that an unauthorized user may gain access to an account.","checkContent":"Verify Ubuntu OS enforces a delay of at least four seconds between console logon prompts following a failed logon attempt with the following command:\n\n$ grep -i fail_delay /etc/login.defs\n\nFAIL_DELAY 4\n\nIf the value of \"FAIL_DELAY\" is not set to \"4\" or greater, or the line is commented out, this is a finding.","fixText":"Configure the Ubuntu OS to enforce a delay of at least four seconds between logon prompts following a failed console logon attempt.\n\nModify the \"/etc/login.defs\" file to set the \"FAIL_DELAY\" parameter to 4 or greater:\n\nFAIL_DELAY 4","ccis":["CCI-000366"]},{"vulnId":"V-275642","ruleId":"SV-275642r1147976_rule","severity":"medium","ruleTitle":"Ubuntu OS must allow users to directly initiate a session lock for all connection types.","description":"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. \n \nThe session lock is implemented at the point where session activity can be determined. Rather than be forced to wait for a period of time to expire before the user session can be locked, Ubuntu OS need to provide users with the ability to manually invoke a session lock so users may secure their session if they need to temporarily vacate the immediate physical vicinity.\n\nSatisfies: SRG-OS-000030-GPOS-00011, SRG-OS-000031-GPOS-00012","checkContent":"Verify Ubuntu OS has the \"vlock\" package installed by using the following command: \n \n $ dpkg -l | grep vlock \n ii vlock 2.2.2-10 amd64 Virtual Console locking program \n \nIf \"vlock\" is not installed, this is a finding.","fixText":"Install the \"vlock\" package by using the following command: \n \n $ sudo apt-get install vlock","ccis":["CCI-000057","CCI-000060","CCI-000058"]},{"vulnId":"V-275643","ruleId":"SV-275643r1147979_rule","severity":"medium","ruleTitle":"Ubuntu OS must automatically exit interactive command shell user sessions after five minutes of inactivity.","description":"Terminating an idle interactive command shell user session within a short time period reduces the window of opportunity for unauthorized personnel to take control of it when left unattended in a virtual terminal or physical console.","checkContent":"Verify Ubuntu OS is configured to automatically exit interactive command shell user sessions after five minutes of inactivity or less by using the following command: \n \n $ sudo grep -E \"\\bTMOUT=[0-9]+\" /etc/bash.bashrc /etc/profile.d/* \n /etc/profile.d/99-terminal_tmout.sh:TMOUT=300 \n \nIf \"TMOUT\" is not set to \"300\" or less, is set to \"0\", is commented out, or missing, this is a finding.","fixText":"Configure Ubuntu OS to exit interactive command shell user sessions after five minutes of inactivity. \n \nCreate and/or append a custom file under \"/etc/profile.d/\" by using the following command: \n \n $ sudo su -c \"echo TMOUT=300 >> /etc/profile.d/99-terminal_tmout.sh\" \n \nThis will set a timeout value of five minutes for all future sessions. \n \nTo set the timeout for the current sessions, execute the following command over the terminal session: \n \n $ export TMOUT=300","ccis":["CCI-002361"]},{"vulnId":"V-275645","ruleId":"SV-275645r1147985_rule","severity":"medium","ruleTitle":"Ubuntu OS must have the \"apparmor\" package installed.","description":"Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system level. \n \nSome of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline. \n \nMethods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles).\n\nSatisfies: SRG-OS-000312-GPOS-00124, SRG-OS-000368-GPOS-00154, SRG-OS-000370-GPOS-00155","checkContent":"Verify Ubuntu OS has the \"apparmor\" package installed by using the following command: \n \n $ dpkg -l | grep apparmor \n ii apparmor 3.0.4-2ubuntu2.3 amd64 user-space parser utility for AppArmor \n \nIf the \"apparmor\" package is not installed, this is a finding.","fixText":"Install the \"appArmor\" package by using the following command: \n \n $ sudo apt-get install apparmor","ccis":["CCI-001764"]},{"vulnId":"V-275646","ruleId":"SV-275646r1147988_rule","severity":"medium","ruleTitle":"Ubuntu OS must be configured to use AppArmor.","description":"Control of program execution is a mechanism used to prevent execution of unauthorized programs. Some operating systems may provide a capability that runs counter to the mission or provides users with functionality that exceeds mission requirements. This includes functions and services installed at the operating system level. \n \nSome of the programs, installed by default, may be harmful or may not be necessary to support essential organizational operations (e.g., key missions, functions). Removal of executable programs is not always possible; therefore, establishing a method of preventing program execution is critical to maintaining a secure system baseline. \n \nMethods for complying with this requirement include restricting execution of programs in certain environments, while preventing execution in other environments; or limiting execution of certain program functionality based on organization-defined criteria (e.g., privileges, subnets, sandboxed environments, or roles).\n\nSatisfies: SRG-OS-000368-GPOS-00154, SRG-OS-000370-GPOS-00155, SRG-OS-000324-GPOS-00125","checkContent":"Verify Ubuntu OS AppArmor is active by using the following commands: \n \n $ systemctl is-enabled apparmor.service \n enabled \n \n $ systemctl is-active apparmor.service \n active \n \nIf \"apparmor.service\" is not enabled and active, this is a finding. \n \nCheck if AppArmor profiles are loaded and enforced by using the following command: \n \n $ sudo apparmor_status | grep -i profile \n 32 profiles are loaded. \n 32 profiles are in enforce mode. \n 0 profiles are in complain mode. \n 0 profiles are in kill mode. \n 0 profiles are in unconfined mode. \n 2 processes have profiles defined. \n 0 processes are unconfined but have a profile defined. \n \nIf no profiles are loaded and enforced, this is a finding.","fixText":"Enable and start \"apparmor.service\" by using the following command: \n \n $ sudo systemctl enable apparmor.service --now \n \nNote: AppArmor must have properly configured profiles for applications and home directories. All configurations will be based on the actual system setup and organization and normally are on a per role basis. See the AppArmor documentation for more information on configuring profiles.","ccis":["CCI-001764","CCI-001774","CCI-002235"]},{"vulnId":"V-275647","ruleId":"SV-275647r1147991_rule","severity":"medium","ruleTitle":"Ubuntu OS must require users to reauthenticate for privilege escalation or when changing roles.","description":"Without reauthentication, users may access resources or perform tasks for which they do not have authorization. \n \nWhen operating systems provide the capability to escalate a functional capability, it is critical the user reauthenticate.\n\nSatisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00158","checkContent":"Verify the \"/etc/sudoers\" file has no occurrences of \"NOPASSWD\" or \"!authenticate\" by using the following command: \n \n $ sudo grep -Ei '(nopasswd|!authenticate)' /etc/sudoers /etc/sudoers.d/* \n \nIf any occurrences of \"NOPASSWD\" or \"!authenticate\" return from the command, this is a finding.","fixText":"Remove any occurrence of \"NOPASSWD\" or \"!authenticate\" found in \"/etc/sudoers\" file or files in the \"/etc/sudoers.d\" directory.","ccis":["CCI-002038"]},{"vulnId":"V-275648","ruleId":"SV-275648r1147994_rule","severity":"high","ruleTitle":"Ubuntu OS must ensure only users who need access to security functions are part of sudo group.","description":"An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions. \n \nSecurity 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 protection is based. Operating systems implement code separation (i.e., separation of security functions from nonsecurity functions) in a number of ways, including through the provision of security kernels via processor rings or processor modes. For nonkernel code, security function isolation is often achieved through file system protections that serve to protect the code on disk and address space protections that protect executing code. \n \nDevelopers and implementers can increase the assurance in security functions by employing well-defined security policy models; structured, disciplined, and rigorous hardware and software development techniques; and sound system/security engineering principles. Implementation may include isolation of memory space and libraries. \n \nUbuntu OS restricts access to security functions through the use of access control mechanisms and by implementing least privilege capabilities.","checkContent":"From the NetIM shell, verify the sudo group has only members who require access to security functions by using the following command: \n \n [netimsh] :~$ shell cat /etc/group |more\n \n For the entries with sudo:x:27:, verify the only username on the list is NetIMAdmin. \n\n \nIf the sudo group contains users not needing access to security functions, this is a finding.","fixText":"From the bash shell, configure the sudo group with only members requiring access to security functions. \n \nTo remove a user from the sudo group, run: \n \n $ sudo gpasswd -d sudo","ccis":["CCI-001084"]},{"vulnId":"V-275649","ruleId":"SV-275649r1147997_rule","severity":"medium","ruleTitle":"Ubuntu OS must enforce password complexity by requiring at least one uppercase character be used.","description":"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. \n \nPassword complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.","checkContent":"Verify Ubuntu OS enforces password complexity by requiring at least one uppercase character be used by using the following command: \n \n $ grep -i ucredit /etc/security/pwquality.conf \n ucredit = -1 \n \nIf \"ucredit\" is greater than \"-1\", is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu OS and NetIMAdmin account to enforce password complexity by requiring that at least one uppercase character be used. \n \nAdd or modify the following line in the \"/etc/security/pwquality.conf\" file: \n \nucredit = -1","ccis":["CCI-004066"]},{"vulnId":"V-275650","ruleId":"SV-275650r1148000_rule","severity":"medium","ruleTitle":"Ubuntu OS must enforce password complexity by requiring at least one lowercase character be used.","description":"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. \n \nPassword complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.","checkContent":"Verify Ubuntu OS enforces password complexity by requiring that at least one lowercase character be used by using the following command: \n \n $ grep -i lcredit /etc/security/pwquality.conf \n lcredit = -1 \n \nIf \"lcredit\" is greater than \"-1\", is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu OS to enforce password complexity by requiring that at least one lowercase character be used. \n \nAdd or modify the following line in the \"/etc/security/pwquality.conf\" file: \n \nlcredit = -1","ccis":["CCI-004066"]},{"vulnId":"V-275651","ruleId":"SV-275651r1148003_rule","severity":"medium","ruleTitle":"Ubuntu OS must enforce password complexity by requiring at least one numeric character be used.","description":"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. \n \nPassword complexity is one factor of several that determines how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised.","checkContent":"Verify with the following command that Ubuntu OS enforces password complexity by requiring at least one numeric character be used: \n \n $ grep -i dcredit /etc/security/pwquality.conf \n dcredit = -1 \n \nIf \"dcredit\" is greater than \"-1\", is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu OS to enforce password complexity by requiring at least one numeric character be used. \n \nAdd or modify the following line in the \"/etc/security/pwquality.conf\" file: \n \ndcredit = -1","ccis":["CCI-004066"]},{"vulnId":"V-275652","ruleId":"SV-275652r1148006_rule","severity":"medium","ruleTitle":"Ubuntu OS must enforce password complexity by requiring at least one special character be used.","description":"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. \n \nPassword complexity is one factor in determining how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. \n \nSpecial characters are those characters that are not alphanumeric. Examples include: ~ ! @ # $ % ^ *.","checkContent":"Verify with the following command that Ubuntu OS enforces password complexity by requiring at least one special character be used: \n \n $ grep -i ocredit /etc/security/pwquality.conf \n ocredit = -1 \n \nIf \"ocredit\" is greater than \"-1\", is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu OS to enforce password complexity by requiring at least one special character be used. \n \nAdd or modify the following line in the \"/etc/security/pwquality.conf\" file: \n \nocredit = -1","ccis":["CCI-004066"]},{"vulnId":"V-275653","ruleId":"SV-275653r1148009_rule","severity":"medium","ruleTitle":"Ubuntu OS must prevent the use of dictionary words for passwords.","description":"If Ubuntu OS 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.\n\nSatisfies: SRG-OS-000480-GPOS-00225, SRG-OS-000710-GPOS-00160","checkContent":"Verify Ubuntu OS prevents the use of dictionary words for passwords by using the following command: \n \n $ grep -i dictcheck /etc/security/pwquality.conf \n dictcheck = 1 \n \nIf \"dictcheck\" is not set to \"1\", is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu OS to prevent the use of dictionary words for passwords. \n \nAdd or modify the following line in the \"/etc/security/pwquality.conf\" file: \n \ndictcheck = 1","ccis":["CCI-000366"]},{"vulnId":"V-275654","ruleId":"SV-275654r1148012_rule","severity":"medium","ruleTitle":"Ubuntu OS must enforce a minimum 15-character password length.","description":"The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised. \n \nPassword 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 helps to determine strength and how long it takes to crack a password. Use of more characters in a password helps to exponentially increase the time and/or resources required to compromise the password.","checkContent":"Verify with the following command that the pwquality configuration file enforces a minimum 15-character password length: \n \n $ grep -i minlen /etc/security/pwquality.conf \n minlen = 15 \n \nIf \"minlen\" is not \"15\" or higher, is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu OS to enforce a minimum 15-character password length. \n \nAdd or modify the following line in the \"/etc/security/pwquality.conf\" file: \n \nminlen = 15","ccis":["CCI-004066"]},{"vulnId":"V-275655","ruleId":"SV-275655r1148015_rule","severity":"medium","ruleTitle":"Ubuntu OS must require the change of at least eight characters when passwords are changed.","description":"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. \n \nThe number of changed characters refers to the number of changes required with respect to the total number of positions in the current password. In other words, characters may be the same within the two passwords; however, the positions of the like characters must be different. \n \nIf the password length is an odd number, the number of changed characters must be rounded up. For example, a password length of 15 characters must require the change of at least eight characters.","checkContent":"Verify Ubuntu OS requires the change of at least eight characters when passwords are changed by using the following command: \n \n $ grep -i difok /etc/security/pwquality.conf \n difok = 8 \n \nIf \"difok\" is less than \"8\", is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu OS to require the change of at least eight characters when passwords are changed. \n \nAdd or modify the following line in the \"/etc/security/pwquality.conf\" file: \n \ndifok = 8","ccis":["CCI-004066"]},{"vulnId":"V-275656","ruleId":"SV-275656r1148018_rule","severity":"medium","ruleTitle":"Ubuntu OS must be configured so that when passwords are changed or new passwords are established, pwquality must be used.","description":"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. \"pwquality\" enforces complex password construction configuration and has the ability to limit brute-force attacks on the system.\n\nSatisfies: SRG-OS-000710-GPOS-00160, SRG-OS-000725-GPOS-00180, SRG-OS-000730-GPOS-00190, SRG-OS-000480-GPOS-00225","checkContent":"Verify Ubuntu OS enforces password complexity rules by using the following command: \n \n $ grep -i enforcing /etc/security/pwquality.conf \n enforcing = 1 \n \nIf \"enforcing\" is not \"1\", is commented out, or is missing, this is a finding. \n \nCheck for the use of \"pwquality\" by using the following command: \n \n $ cat /etc/pam.d/common-password | grep requisite | grep pam_pwquality \n password requisite pam_pwquality.so retry=3 \n \nIf \"retry\" is set to \"0\" or is greater than \"3\", or is missing, this is a finding.","fixText":"Configure Ubuntu OS to enforce password complexity rules. \n \nAdd or modify the following line in the \"/etc/security/pwquality.conf\" file: \n \nenforcing = 1 \n \nAdd or modify the following line in the \"/etc/pam.d/common-password\" file: \n \npassword requisite pam_pwquality.so retry=3 \n \nNote: The value of \"retry\" should be between \"1\" and \"3\".","ccis":["CCI-004061","CCI-004064","CCI-004065","CCI-000366"]},{"vulnId":"V-275657","ruleId":"SV-275657r1148272_rule","severity":"high","ruleTitle":"Ubuntu OS must store only encrypted representations of passwords.","description":"Passwords must 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. If the application allows the user to consecutively reuse their password when that password has exceeded its defined lifetime, the end result is a password that is not changed as per policy requirements.","checkContent":"Verify the Ubuntu operating stores only encrypted representations of passwords with the following command: \n \n $ grep pam_unix.so /etc/pam.d/common-password \n password [success=1 default=ignore] pam_unix.so obscure sha512 shadow remember=5 rounds=100000\n \nIf \"sha512\" is missing from the \"pam_unix.so\" line, this is a finding.","fixText":"Configure Ubuntu OS to store encrypted representations of passwords. \n \nAdd or modify the following line in the \"/etc/pam.d/common-password\" file: \n \npassword [success=1 default=ignore] pam_unix.so obscure sha512 shadow remember=5 rounds=100000","ccis":["CCI-004062"]},{"vulnId":"V-275658","ruleId":"SV-275658r1148024_rule","severity":"medium","ruleTitle":"Ubuntu OS must not allow accounts configured with blank or null passwords.","description":"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 never be used in operational environments.","checkContent":"Verify null passwords cannot be used. Run the following command: \n \n $ grep nullok /etc/pam.d/common-auth /etc/pam.d/common-password\n \nIf this produces any output, this is a finding.","fixText":"Remove any instances of the \"nullok\" option in \"/etc/pam.d/common-password\" to prevent logons with empty passwords.\n\nRemove any instances of the \"nullok\" option in \"/etc/pam.d/common-auth\" and \"/etc/pam.d/common-password\".","ccis":["CCI-000366"]},{"vulnId":"V-275659","ruleId":"SV-275659r1148027_rule","severity":"medium","ruleTitle":"Ubuntu OS must not have accounts configured with blank or null passwords.","description":"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 never be used in operational environments.","checkContent":"Verify all accounts on the system have a password by using the following command: \n \n $ sudo awk -F: '!$2 {print $1}' /etc/shadow \n \nIf the command returns any results, this is a finding.","fixText":"Configure all accounts on the system to have a password or lock the account by using the following commands: \n \nSet the account password: \n \n $ sudo passwd \n \nOr lock the account: \n \n $ sudo passwd -l ","ccis":["CCI-000366"]},{"vulnId":"V-275660","ruleId":"SV-275660r1148030_rule","severity":"medium","ruleTitle":"Ubuntu OS must encrypt all stored passwords with a FIPS 140-2/140-3-approved cryptographic hashing algorithm.","description":"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.","checkContent":"Verify that the shadow password suite configuration is set to encrypt passwords with a FIPS 140-2/140-3 approved cryptographic hashing algorithm by using the following command: \n \n $ grep -i '^\\s*encrypt_method' /etc/login.defs \n ENCRYPT_METHOD SHA512 \n \nIf \"ENCRYPT_METHOD\" does not equal SHA512 or greater, is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu OS to encrypt all stored passwords. \n \nAdd or modify the following line in the \"/etc/login.defs\" file: \n \nENCRYPT_METHOD SHA512","ccis":["CCI-000803"]},{"vulnId":"V-275668","ruleId":"SV-275668r1148054_rule","severity":"medium","ruleTitle":"Ubuntu OS must be configured such that Pluggable Authentication Module (PAM) prohibits the use of cached authentications after one day.","description":"If cached authentication information is out-of-date, the validity of the authentication information may be questionable.","checkContent":"Verify PAM prohibits the use of cached authentications after one day by using the following command: \n \nNote: If smart card authentication is not being used on the system, this requirement is not applicable. \n \n $ sudo grep -i '^\\s*offline_credentials_expiration' /etc/sssd/sssd.conf /etc/sssd/conf.d/*.conf \n /etc/sssd/sssd.conf:offline_credentials_expiration = 1 \n \nIf \"offline_credentials_expiration\" is not set to \"1\", is commented out, is missing, or conflicting results are returned, this is a finding.","fixText":"Configure PAM to prohibit the use of cached authentications after one day. \n \nAdd or modify the following line in the \"/etc/sssd/sssd.conf\" file, just below the line \"[pam]\": \n \noffline_credentials_expiration = 1 \n \nNote: It is valid for this configuration to be in a file with a name that ends with \".conf\" and does not begin with a \".\" in the \"/etc/sssd/conf.d/\" directory instead of the \"/etc/sssd/sssd.conf\" file.","ccis":["CCI-002007"]},{"vulnId":"V-275669","ruleId":"SV-275669r1148057_rule","severity":"medium","ruleTitle":"Ubuntu OS must use a file integrity tool to verify correct operation of all security functions.","description":"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 protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. \n \nThis requirement applies to Ubuntu OS performing security function verification/testing and/or systems and environments that require this functionality.","checkContent":"Verify that Advanced Intrusion Detection Environment (AIDE) is installed by using the following command: \n \n $ dpkg -l | grep aide \n ii aide 0.17.4-1 amd64 Advanced Intrusion Detection Environment - dynamic binary \n \nIf AIDE is not installed, ask the system administrator how file integrity checks are performed on the system. \n \nIf there is no application installed to perform integrity checks, this is a finding.","fixText":"Install the \"aide\" package: \n \n $ sudo apt install aide","ccis":["CCI-002696"]},{"vulnId":"V-275670","ruleId":"SV-275670r1148060_rule","severity":"medium","ruleTitle":"Ubuntu OS must configure AIDE to perform file integrity checking on the file system.","description":"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 protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. \n \nThis requirement applies to Ubuntu OS performing security function verification/testing and/or systems and environments that require this functionality.","checkContent":"Verify that Advanced Intrusion Detection Environment (AIDE) is configured and operating correctly by using the following command (this will take a few minutes): \n \nNote: If AIDE is not installed, this requirement is not applicable. \n \n $ sudo aide -c /etc/aide/aide.conf --check \n \nExample output: \n \nStart timestamp: 2024-04-01 04:20:00 +1300 (AIDE 0.17.4) \nAIDE found differences between database and filesystem!! \nIgnored e2fs attributes: EIh \n... \n \nIf AIDE is being used to perform file integrity checks but the command fails, this is a finding.","fixText":"Initialize AIDE (this will take a few minutes): \n \n $ sudo aideinit \n Running aide --init... \n \nExample output: \n \nStart timestamp: 2024-04-01 04:20:00 +1300 (AIDE 0.17.4) \nAIDE initialized database at /var/lib/aide/aide.db.new \nIgnored e2fs attributes: EIh \n \nNumber of entries: 146185 \n \n--------------------------------------------------- \nThe attributes of the (uncompressed) database(s): \n--------------------------------------------------- \n \n/var/lib/aide/aide.db.new \n SHA256 : UrYbC/KBOJcs8zKcSlKoifnnoPK66DEC \n Aw6odu/BpgY= \n SHA512 : ezENbbuh937SPWvtsdjRzy3i47XjLg7j \n L3UGmr0EcgY6u8rczxgbn2RuwJfrIpef \n 0c1qMNobzrLXyDnnqEqAqw== \n RMD160 : yBq2xio+g5ne4kvZzzMZ2v+EO9w= \n TIGER : GkJ/xkzJGu/aSQqk9A5LN271IOAQC3d0 \n CRC32 : g/beXA== \n HAVAL : zZm220YZiGna2edJ6Gi0rPv16AlpqeHB \n y/XLB3hIPEY= \n WHIRLPOOL : k6veoXavJ/BH9L125pCYAfTB8w5ZJkdC \n DvVmYS0+cgmg7M0y/S2v42FNCEJ993mc \n 3kZMXJR/VVmwKg/7ntGixQ== \n GOST : psjiyix6mJlNsE984D0NwbfgBmB0ETGl \n /R4PNvm/wKg= \n \nEnd timestamp: 2024-04-01 04:29:16 +1300 (run time: 9m 16s)","ccis":["CCI-002696"]},{"vulnId":"V-275671","ruleId":"SV-275671r1148063_rule","severity":"medium","ruleTitle":"Ubuntu OS must notify designated personnel if baseline configurations are changed in an unauthorized manner.","description":"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. \n \nDetecting such changes and providing an automated response can help avoid unintended negative consequences that could ultimately affect the security state of the operating system. The operating system's information management officer (IMO)/information system security officer (ISSO) and system administrators (SAs) must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item.\n\nSatisfies: SRG-OS-000363-GPOS-00150, SRG-OS-000447-GPOS-00201","checkContent":"Verify that Advanced Intrusion Detection Environment (AIDE) notifies the system administrator when anomalies in the operation of any security functions are discovered by using the following command: \n \n $ grep -i '^\\s*silentreports' /etc/default/aide \n SILENTREPORTS=no \n \nIf \"SILENTREPORTS\" is set to \"yes\", is commented out, or is missing, this is a finding.","fixText":"Configure AIDE to notify designated personnel if baseline configurations are changed in an unauthorized manner. The 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.\n \nAdd or modify the following line in the \"/etc/default/aide\" file: \n \nSILENTREPORTS=no","ccis":["CCI-001744","CCI-002702"]},{"vulnId":"V-275672","ruleId":"SV-275672r1148066_rule","severity":"medium","ruleTitle":"Ubuntu OS must be configured so that the script that runs each 30 days or less to check file integrity is the default.","description":"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 protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. \n \nNotifications provided by information systems include, for example, electronic alerts to system administrators, messages to local computer consoles, and/or hardware indications, such as lights. \n \nThis requirement applies to Ubuntu OS performing security function verification/testing and/or systems and environments that require this functionality.","checkContent":"Verify that the Advanced Intrusion Detection Environment (AIDE) default script used to check file integrity each 30 days or less is unchanged. \n \nDownload the original aide-common package in the /tmp directory: \n \n $ cd /tmp; apt download aide-common \n \nFetch the SHA1 of the original script file: \n \n $ dpkg-deb --fsys-tarfile /tmp/aide-common_*.deb | tar -xO ./usr/share/aide/config/cron.daily/aide | sha1sum \n b71bb2cafaedf15ec3ac2f566f209d3260a37af0 - \n \nCompare with the SHA1 of the file in the daily or monthly cron directory: \n \n $ sha1sum /etc/cron.{daily,monthly}/aide 2>/dev/null \n b71bb2cafaedf15ec3ac2f566f209d3260a37af0 /etc/cron.daily/aide \n \nIf there is no AIDE script file in the cron directories, or the SHA1 value of at least one file in the daily or monthly cron directory does not match the SHA1 of the original, this is a finding.","fixText":"The cron file for AIDE is fairly complex as it creates the report. This file is installed with the \"aide-common\" package, and the default can be restored by copying it from the package: \n \nExtract the aide script from the \"aide-common\" package to its original place: \n \n $ dpkg-deb --fsys-tarfile /tmp/aide-common_*.deb | sudo tar -x ./usr/share/aide/config/cron.daily/aide -C / \n \nCopy it to the cron.daily directory: \n \n $ sudo cp -f /usr/share/aide/config/cron.daily/aide /etc/cron.daily/aide","ccis":["CCI-002699"]},{"vulnId":"V-275673","ruleId":"SV-275673r1148069_rule","severity":"high","ruleTitle":"Ubuntu OS must use cryptographic mechanisms to protect the integrity of audit tools.","description":"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. \n \nAudit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators. \n \nIt is not uncommon for attackers to replace the audit tools or inject code into the existing tools with the purpose of providing the capability to hide or erase system activity from the audit logs. \n \nTo address this risk, audit tools must be cryptographically signed to provide the capability to identify when the audit tools have been modified, manipulated, or replaced. An example is a checksum hash of the file or files.","checkContent":"Verify that Advanced Intrusion Detection Environment (AIDE) is properly configured to use cryptographic mechanisms to protect the integrity of audit tools by using the following command: \n \n $ grep -E '(\\/sbin\\/(audit|au))' /etc/aide/aide.conf \n /sbin/auditctl p+i+n+u+g+s+b+acl+xattrs+sha512 \n /sbin/auditd p+i+n+u+g+s+b+acl+xattrs+sha512 \n /sbin/ausearch p+i+n+u+g+s+b+acl+xattrs+sha512 \n /sbin/aureport p+i+n+u+g+s+b+acl+xattrs+sha512 \n /sbin/autrace p+i+n+u+g+s+b+acl+xattrs+sha512 \n /sbin/augenrules p+i+n+u+g+s+b+acl+xattrs+sha512 \n \nIf any of the lines do not appear as shown, are commented out, or are missing, this is a finding.","fixText":"Configure AIDE to protect the integrity of audit tools: \n \nAdd or modify the following lines in the \"/etc/aide/aide.conf\" file: \n \n# Audit Tools \n/sbin/auditctl p+i+n+u+g+s+b+acl+xattrs+sha512 \n/sbin/auditd p+i+n+u+g+s+b+acl+xattrs+sha512 \n/sbin/ausearch p+i+n+u+g+s+b+acl+xattrs+sha512 \n/sbin/aureport p+i+n+u+g+s+b+acl+xattrs+sha512 \n/sbin/autrace p+i+n+u+g+s+b+acl+xattrs+sha512 \n/sbin/augenrules p+i+n+u+g+s+b+acl+xattrs+sha512","ccis":["CCI-001496"]},{"vulnId":"V-275674","ruleId":"SV-275674r1148072_rule","severity":"low","ruleTitle":"Ubuntu OS must have a crontab script running weekly to off-load audit events of standalone systems.","description":"Information stored in one location is vulnerable to accidental or incidental deletion or alteration. \n \nOff-loading is a common process in information systems with limited audit storage capacity.","checkContent":"Verify there is a script that off-loads audit data and the script runs weekly by using the following command: \n \nNote: If the system is not connected to a network, this requirement is not applicable. \n \n $ ls /etc/cron.weekly \n \n \nCheck if the script inside the file off-loads audit logs to external media. \n \nIf the script file does not exist or does not off-load audit logs, this is a finding.","fixText":"Create a script that off-loads audit logs to external media and runs weekly. \n \nThe script must be located in the \"/etc/cron.weekly\" directory.","ccis":["CCI-001851"]},{"vulnId":"V-275675","ruleId":"SV-275675r1148075_rule","severity":"medium","ruleTitle":"Ubuntu OS must be configured to preserve log records from failure events.","description":"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. \n \nPreserving operating system state information helps to facilitate operating system restart and return to the operational mode of the organization with least disruption to mission/business processes.","checkContent":"Verify the log service is installed properly by using the following command: \n \n $ dpkg -l | grep rsyslog \n ii rsyslog 8.2112.0-2ubuntu2.2 amd64 reliable system and kernel logging daemon \n \nIf the \"rsyslog\" package is not installed, this is a finding. \n \nCheck that the log service is enabled and active by using the following commands: \n \n $ systemctl is-enabled rsyslog.service \n enabled \n \n $ systemctl is-active rsyslog.service \n active \n \nIf \"rsyslog.service\" is not enabled and active, this is a finding.","fixText":"Install the log service by using the following command: \n \n $ sudo apt-get install rsyslog \n \nEnable and activate the log service by using the following command: \n \n $ sudo systemctl enable rsyslog.service --now","ccis":["CCI-001665"]},{"vulnId":"V-275676","ruleId":"SV-275676r1148078_rule","severity":"medium","ruleTitle":"Ubuntu OS must monitor remote access methods.","description":"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. \n \nRemote access is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. \n \nAutomated monitoring of remote access sessions allows organizations to detect cyberattacks and also ensure ongoing compliance with remote access policies by auditing connection activities of remote access capabilities, such as Remote Desktop Protocol (RDP), on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets).","checkContent":"Verify that Ubuntu OS monitors all remote access methods by using the following command: \n \n $ grep -Er '^(auth\\.\\*,authpriv\\.\\*|daemon\\.\\*)' /etc/rsyslog.* \n /etc/rsyslog.d/50-default.conf:auth.*,authpriv.* /var/log/secure \n /etc/rsyslog.d/50-default.conf:daemon.* /var/log/messages \n \nIf \"auth.*\", \"authpriv.*\", or \"daemon.*\" are not configured to be logged in at least one of the config files, this is a finding.","fixText":"Configure Ubuntu OS to monitor all remote access methods. \n \nAdd or modify the following line in the \"/etc/rsyslog.d/50-default.conf\" file: \n \nauth.*,authpriv.* /var/log/secure \ndaemon.* /var/log/messages \n \nRestart \"rsyslog.service\" for the changes to take effect by using the following command: \n \n $ sudo systemctl restart rsyslog.service","ccis":["CCI-000067"]},{"vulnId":"V-275677","ruleId":"SV-275677r1148081_rule","severity":"medium","ruleTitle":"Ubuntu OS must have the \"auditd\" package installed.","description":"Without establishing the when, where, type, source, and outcome of events that occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. \n \nWithout the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. \n \nReconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. \n \nSuccessful incident response and auditing relies on timely, accurate system information and analysis to allow the organization to identify and respond to potential incidents in a proficient manner. If the operating system does not provide the ability to centrally review the operating system logs, forensic analysis is negatively impacted. \n \nAssociating event types with detected events in Ubuntu OS audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system.\n\nSatisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000038-GPOS-00016, SRG-OS-000039-GPOS-00017, SRG-OS-000040-GPOS-00018, SRG-OS-000041-GPOS-00019, SRG-OS-000042-GPOS-00020, SRG-OS-000042-GPOS-00021, SRG-OS-000051-GPOS-00024, SRG-OS-000054-GPOS-00025, SRG-OS-000062-GPOS-00031, SRG-OS-000122-GPOS-00063, SRG-OS-000337-GPOS-00129, SRG-OS-000348-GPOS-00136, SRG-OS-000349-GPOS-00137, SRG-OS-000350-GPOS-00138, SRG-OS-000351-GPOS-00139, SRG-OS-000352-GPOS-00140, SRG-OS-000353-GPOS-00141, SRG-OS-000354-GPOS-00142, SRG-OS-000365-GPOS-00152, SRG-OS-000475-GPOS-00220, SRG-OS-000461-GPOS-00205, SRG-OS-000465-GPOS-00209, SRG-OS-000467-GPOS-00211, SRG-OS-000255-GPOS-00096","checkContent":"Verify the \"auditd\" package is installed by using the following command: \n \n $ dpkg -l | grep auditd \n ii libauditd 1:3.0.7-1build1 amd64 User space tools for security auditing \n \nIf the \"auditd\" package is not installed, this is a finding.","fixText":"Install the \"auditd\" package by using the following command: \n \n $ sudo apt-get install auditd","ccis":["CCI-000130","CCI-000131","CCI-000132","CCI-000133","CCI-000134","CCI-000135","CCI-000154","CCI-000158","CCI-000169","CCI-000172","CCI-003938","CCI-001875","CCI-001876","CCI-001877","CCI-001878","CCI-001879","CCI-001880","CCI-001881","CCI-001882","CCI-001914","CCI-001814","CCI-001487"]},{"vulnId":"V-275678","ruleId":"SV-275678r1148084_rule","severity":"medium","ruleTitle":"Ubuntu OS must produce audit records and reports containing information to establish when, where, what type, the source, and the outcome for all DOD-defined auditable events and actions in near real time.","description":"Without establishing the when, where, type, source, and outcome of events that occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. \n \nWithout the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. \n \nAudit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. \n \nReconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. \n \nSuccessful incident response and auditing relies on timely, accurate system information and analysis to allow the organization to identify and respond to potential incidents in a proficient manner. If the operating system does not provide the ability to centrally review the operating system logs, forensic analysis is negatively impacted. \n \nAssociating event types with detected events in Ubuntu OS audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system.\n\nSatisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000038-GPOS-00016, SRG-OS-000039-GPOS-00017, SRG-OS-000040-GPOS-00018, SRG-OS-000041-GPOS-00019, SRG-OS-000042-GPOS-00020, SRG-OS-000042-GPOS-00021, SRG-OS-000051-GPOS-00024, SRG-OS-000054-GPOS-00025, SRG-OS-000062-GPOS-00031, SRG-OS-000122-GPOS-00063, SRG-OS-000337-GPOS-00129, SRG-OS-000348-GPOS-00136, SRG-OS-000349-GPOS-00137, SRG-OS-000350-GPOS-00138, SRG-OS-000351-GPOS-00139, SRG-OS-000352-GPOS-00140, SRG-OS-000353-GPOS-00141, SRG-OS-000354-GPOS-00142, SRG-OS-000365-GPOS-00152, SRG-OS-000475-GPOS-00220, SRG-OS-000461-GPOS-00205, SRG-OS-000465-GPOS-00209, SRG-OS-000467-GPOS-00211, SRG-OS-000255-GPOS-00096","checkContent":"Verify the \"auditd.service\" is enabled and active by using the following commands: \n \n $ systemctl is-enabled auditd.service \n enabled \n \n $ systemctl is-active auditd.service \n active \n \nIf the \"auditd.service\" is not enabled and active, this is a finding.","fixText":"Enable and start the \"auditd.service\" by using the following command: \n \n $ sudo systemctl enable auditd.service --now","ccis":["CCI-000130","CCI-000131","CCI-000132","CCI-000133","CCI-000134","CCI-000135","CCI-000154","CCI-000158","CCI-000169","CCI-000172","CCI-003938","CCI-001875","CCI-001876","CCI-001877","CCI-001878","CCI-001879","CCI-001880","CCI-001881","CCI-001882","CCI-001914","CCI-001814","CCI-001487"]},{"vulnId":"V-275679","ruleId":"SV-275679r1148087_rule","severity":"medium","ruleTitle":"Ubuntu OS audit event multiplexor must be configured to off-load audit logs onto a different system from the system being audited.","description":"Information stored in one location is vulnerable to accidental or incidental deletion or alteration. \n \nOff-loading is a common process in information systems with limited audit storage capacity. \n \nThe auditd service does not include the ability to send audit records to a centralized server for management directly. However, it can use a plug-in for audit event multiplexor to pass audit records to a remote server.","checkContent":"Verify the audit event multiplexor is configured to off-load audit records to a different system from the system being audited. \n \nCheck if the \"audispd-plugins\" package is installed: \n \n $ dpkg -l | grep audispd-plugins \n ii audispd-plugins 1:3.0.7-1build1 amd64 Plugins for the audit event dispatcher \n \nIf the \"audispd-plugins\" package is not installed, this is a finding. \n \nCheck that the records are being off-loaded to a remote server by using the following command: \n \n $ sudo grep -i active /etc/audit/plugins.d/au-remote.conf \n active = yes \n \nIf \"active\" is not set to \"yes\", or the line is commented out, or is missing, this is a finding. \n \nCheck that audisp-remote plugin is configured to send audit logs to a different system: \n \n $ sudo grep -i remote_server /etc/audit/audisp-remote.conf \n remote_server = 240.9.19.81 \n \nIf the \"remote_server\" parameter is not set, is set with a local IP address, or is set with an invalid IP address, this is a finding.","fixText":"Configure the audit event multiplexor to off-load audit records to a different system from the system being audited. \n \nInstall the \"audisp-plugins\" package by using the following command: \n \n $ sudo apt-get install audispd-plugins \n \nSet the audisp-remote plugin as active by editing the \"/etc/audit/plugins.d/au-remote.conf\" file: \n \n $ sudo sed -i -E 's/active\\s*=\\s*no/active = yes/' /etc/audit/plugins.d/au-remote.conf \n \nSet the IP address of the remote system by editing the \"/etc/audit/audisp-remote.conf\" file: \n \n $ sudo sed -i -E 's/(remote_server\\s*=).*/\\1 /' /etc/audit/audisp-remote.conf \n \nRestart the \"auditd.service\" for the changes to take effect: \n \n $ sudo systemctl restart auditd.service","ccis":["CCI-001851"]},{"vulnId":"V-275680","ruleId":"SV-275680r1148090_rule","severity":"medium","ruleTitle":"Ubuntu OS must alert the information system security officer (ISSO) and system administrator (SA) in the event of an audit processing failure.","description":"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. \n \nAudit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. \n \nThis requirement applies to each audit data storage repository (i.e., distinct information system component where audit records are stored), the centralized audit storage capacity of organizations (i.e., all audit data storage repositories combined), or both.\n\nSatisfies: SRG-OS-000046-GPOS-00022, SRG-OS-000344-GPOS-00135","checkContent":"Verify that the SA and ISSO are notified in the event of an audit processing failure by using the following command: \n \n $ sudo grep -i action_mail_acct /etc/audit/auditd.conf \n action_mail_acct = \n \nIf \"action_mail_acct\" is not set to the email address of the SA and/or ISSO, is commented out, or is missing, this is a finding.","fixText":"Configure \"auditd\" service to notify the SA and ISSO in the event of an audit processing failure. \n \nAdd or modify the following line in the \"/etc/audit/auditd.conf \" file: \n \naction_mail_acct = \n \nNote: Change \"administrator_email_account\" to the email address of the SA and/or ISSO. \n \nRestart the \"auditd\" service for the changes take effect: \n \n $ sudo systemctl restart auditd.service\n\nNote: An email package must be installed on the system for email notifications to be sent.","ccis":["CCI-000139"]},{"vulnId":"V-275682","ruleId":"SV-275682r1148096_rule","severity":"low","ruleTitle":"Ubuntu OS must immediately notify the system administrator (SA) and information system security officer (ISSO) when the audit record storage volume reaches 25 percent remaining of the allocated capacity.","description":"If security personnel are not notified immediately when storage volume reaches 25 percent remaining of the allocated capacity, they are unable to plan for audit record storage capacity expansion.","checkContent":"Verify Ubuntu OS is configured to notify the SA and ISSO when the audit record storage volume reaches 25 percent remaining of the allocated capacity by using the following command: \n \n $ sudo grep -i space_left /etc/audit/auditd.conf \n space_left = 25% \n space_left_action = email \n \nIf \"space_left\" is set to a value less than \"25%\", is commented out, or is missing, this is a finding.\n\nIf \"space_left_action\" is not set to \"email\", is commented out, or is missing, this is a finding. \n \nNote: If the \"space_left_action\" is set to \"exec\", the system executes a designated script. If this script informs the SA of the event, this is not a finding.","fixText":"Configure Ubuntu OS to notify the SA and ISSO when the audit record storage volume reaches 25 percent remaining of the allocated capacity. \n \nAdd or modify the following lines in the \"/etc/audit/auditd.conf \" file: \n \nspace_left = 25% \nspace_left_action = email \n \nRestart the \"auditd\" service for the changes to take effect: \n \n $ sudo systemctl restart auditd.service \n \nNote: If the \"space_left_action\" parameter is set to \"exec\", ensure the command being executed notifies the SA and ISSO.","ccis":["CCI-001855"]},{"vulnId":"V-275683","ruleId":"SV-275683r1148099_rule","severity":"medium","ruleTitle":"Ubuntu OS must be configured so that audit log files are not read- or write-accessible by unauthorized users.","description":"Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality. \n \nAudit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity.\n\nSatisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028","checkContent":"Verify that the audit log files have a mode of \"600\" or less permissive. \n \nDetermine where the audit logs are stored by using the following command: \n \n $ sudo grep -iw log_file /etc/audit/auditd.conf \n log_file = /var/log/audit/audit.log \n \nUsing the path of the directory containing the audit logs, determine if the audit log files have a mode of \"600\" or less by using the following command: \n \n $ sudo stat -c \"%n %a\" /var/log/audit/* \n /var/log/audit/audit.log 600 \n \nIf the audit log files have a mode more permissive than \"600\", this is a finding.","fixText":"Configure the audit log files to have a mode of \"600\" or less permissive. \n \nUsing the path of the directory containing the audit logs, configure the audit log files to have a mode of \"600\" or less permissive by using the following command: \n \n $ sudo chmod 600 /var/log/audit/*","ccis":["CCI-000162","CCI-000163"]},{"vulnId":"V-275684","ruleId":"SV-275684r1148102_rule","severity":"medium","ruleTitle":"Ubuntu OS must be configured to permit only authorized users ownership of the audit log files.","description":"Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality. \n \nAudit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity.\n\nSatisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029","checkContent":"Verify the audit log files are owned by \"root\" account. \n \nDetermine where the audit logs are stored by using the following command: \n \n $ sudo grep -iw log_file /etc/audit/auditd.conf \n log_file = /var/log/audit/audit.log \n \nUsing the path of the directory containing the audit logs, determine if the audit log files are owned by the \"root\" user by using the following command: \n \n $ sudo stat -c \"%n %U\" /var/log/audit/* \n /var/log/audit/audit.log root \n \nIf the audit log files are owned by a user other than \"root\", this is a finding.","fixText":"Configure the audit log directory and its underlying files to be owned by \"root\" user. \n \nUsing the path of the directory containing the audit logs, configure the audit log files to be owned by \"root\" user by using the following command: \n \n $ sudo chown root /var/log/audit/*","ccis":["CCI-000162","CCI-000163","CCI-000164"]},{"vulnId":"V-275685","ruleId":"SV-275685r1148105_rule","severity":"medium","ruleTitle":"Ubuntu OS must permit only authorized groups ownership of the audit log files.","description":"Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality. \n \nAudit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity.","checkContent":"Verify the group owner of newly created audit logs is \"root\" by using the following command: \n \n $ sudo grep -iw log_group /etc/audit/auditd.conf \n log_group = root \n \nIf \"log_group\" is not set to \"root\", this is a finding.","fixText":"Configure the group owner of newly created audit logs to be \"root\". \n \nAdd or modify the following lines in the \"/etc/audit/auditd.conf \" file: \n \nlog_group = root \n \nReload the configuration file of the audit service to update the group ownership of existing files: \n \n $ sudo systemctl kill auditd -s SIGHUP","ccis":["CCI-000162","CCI-000163","CCI-000164"]},{"vulnId":"V-275686","ruleId":"SV-275686r1148108_rule","severity":"medium","ruleTitle":"Ubuntu OS must be configured so that the audit log directory is not write-accessible by unauthorized users.","description":"If audit information were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. \n \nTo ensure the veracity of audit information, the operating system must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods, which will depend upon system architecture and design. \n \nAudit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity.","checkContent":"Verify the audit log directory has a mode of \"750\" or less permissive. \n \nDetermine where the audit logs are stored by using the following command: \n \n $ sudo grep -iw log_file /etc/audit/auditd.conf \n log_file = /var/log/audit/audit.log \n \nUsing the path of the directory containing the audit logs, determine if the directory has a mode of \"750\" or less by using the following command: \n \n $ sudo stat -c \"%n %a\" /var/log/audit \n /var/log/audit 750 \n \nIf the audit log directory has a mode more permissive than \"750\", this is a finding.","fixText":"Configure the audit log directory to have a mode of \"750\" or less permissive. \n \nUsing the path of the directory containing the audit logs, configure the audit log directory to have a mode of \"750\" or less permissive by using the following command: \n \n $ sudo chmod -R g-w,o-rwx /var/log/audit","ccis":["CCI-000164"]},{"vulnId":"V-275687","ruleId":"SV-275687r1148111_rule","severity":"medium","ruleTitle":"Ubuntu OS must permit only authorized accounts to own the audit configuration files.","description":"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. \n \nMisconfigured audits may degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.","checkContent":"Verify \"/etc/audit/audit.rules\", \"/etc/audit/auditd.conf\", and \"/etc/audit/rules.d/*\" files are owned by root account by using the following command: \n \n $ sudo ls -al /etc/audit/audit.rules /etc/audit/auditd.conf /etc/audit/rules.d/* | awk '{print $3, $9}' \n root /etc/audit/audit.rules \n root /etc/audit/auditd.conf \n root /etc/audit/rules.d/audit.rules \n \nIf \"/etc/audit/audit.rules\", \"/etc/audit/auditd.conf\", or \"/etc/audit/rules.d/*\" files are owned by a user other than \"root\", this is a finding.","fixText":"Configure \"/etc/audit/audit.rules\", \"/etc/audit/rules.d/*\", and \"/etc/audit/auditd.conf\" files to be owned by root by using the following command: \n \n $ sudo chown -R root /etc/audit/audit.rules /etc/audit/auditd.conf /etc/audit/rules.d/*","ccis":["CCI-000171"]},{"vulnId":"V-275688","ruleId":"SV-275688r1148114_rule","severity":"medium","ruleTitle":"Ubuntu OS must permit only authorized groups to own the audit configuration files.","description":"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. \n \nMisconfigured audits may degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.","checkContent":"Verify \"/etc/audit/audit.rules\", \"/etc/audit/auditd.conf\", and \"/etc/audit/rules.d/*\" files are owned by root group by using the following command: \n \n $ sudo ls -al /etc/audit/audit.rules /etc/audit/auditd.conf /etc/audit/rules.d/* | awk '{print $4, $9}' \n root /etc/audit/audit.rules \n root /etc/audit/auditd.conf \n root /etc/audit/rules.d/audit.rules \n \nIf \"/etc/audit/audit.rules\", \"/etc/audit/auditd.conf\", or \"/etc/audit/rules.d/*\" files are owned by a group other than \"root\", this is a finding.","fixText":"Configure \"/etc/audit/audit.rules\", \"/etc/audit/rules.d/*\", and \"/etc/audit/auditd.conf\" files to be owned by root group by using the following command: \n \n $ sudo chown -R :root /etc/audit/audit.rules /etc/audit/auditd.conf /etc/audit/rules.d/*","ccis":["CCI-000171"]},{"vulnId":"V-275689","ruleId":"SV-275689r1148117_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the apparmor_parser command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS generates an audit record upon successful/unsuccessful attempts to use the \"apparmor_parser\" command by using the following command: \n \n $ sudo auditctl -l | grep apparmor_parser \n -a always,exit -S all -F path=/sbin/apparmor_parser -F perm=x -F auid>=1000 -F auid!=-1 -F key=perm_chng \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"apparmor_parser\" command. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/sbin/apparmor_parser -F perm=x -F auid>=1000 -F auid!=unset -k perm_chng \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275690","ruleId":"SV-275690r1148120_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the chacl command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS generates an audit record upon successful/unsuccessful attempts to use the \"chacl\" command by using the following command: \n \n $ sudo auditctl -l | grep chacl \n -a always,exit -S all -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=-1 -F key=perm_chng \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"chacl\" command. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_chng \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275691","ruleId":"SV-275691r1148123_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the chage command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify an audit event is generated for any successful/unsuccessful use of the \"chage\" command by using the following command: \n \n $ sudo auditctl -l | grep -w chage \n -a always,exit -S all -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=-1 -F key=privileged-chage \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful uses of the \"chage\" command. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chage \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275692","ruleId":"SV-275692r1148126_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the chcon command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS generates an audit record upon successful/unsuccessful attempts to use the \"chcon\" command by using the following command: \n \n $ sudo auditctl -l | grep chcon \n -a always,exit -S all -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=-1 -F key=perm_chng \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding.\n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"chcon\" command. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=unset -k perm_chng \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275693","ruleId":"SV-275693r1148129_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the chfn command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS generates audit records upon successful/unsuccessful attempts to use the \"chfn\" command by using the following command: \n \n $ sudo auditctl -l | grep /usr/bin/chfn \n -a always,exit -S all -F path=/usr/bin/chfn -F perm=x -F auid>=1000 -F auid!=-1 -F key=privileged-chfn \n \nIf the command does not return lines that match the example or the lines are commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful uses of the \"chfn\" command. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/chfn -F perm=x -F auid>=1000 -F auid!=unset -k privileged-chfn \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275694","ruleId":"SV-275694r1148132_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the chsh command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS generates an audit record upon successful/unsuccessful attempts to use the \"chsh\" command by using the following command: \n \n $ sudo auditctl -l | grep chsh \n -a always,exit -S all -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=-1 -F key=priv_cmd \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNotes: The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"chsh\" command. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=unset -k priv_cmd \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275695","ruleId":"SV-275695r1148135_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the crontab command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify an audit event is generated for any successful/unsuccessful use of the \"crontab\" command by using the following command: \n \n $ sudo auditctl -l | grep -w crontab \n -a always,exit -S all -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=-1 -F key=privileged-crontab \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful uses of the \"crontab\" command. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=unset -k privileged-crontab \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275696","ruleId":"SV-275696r1148138_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful attempts to use the fdisk command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS is configured to audit the execution of the partition management program \"fdisk\" by using the following command: \n \n $ sudo auditctl -l | grep fdisk \n -w /usr/sbin/fdisk -p x -k fdisk \n \nIf the command does not return a line, or the line is commented out, this is a finding. \n \nNote: The \"-k\" value is arbitrary and can be different from the example output above.","fixText":"Configure Ubuntu OS to audit the execution of the partition management program \"fdisk\". \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-w /usr/sbin/fdisk -p x -k fdisk \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275697","ruleId":"SV-275697r1148141_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the gpasswd command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify an audit event is generated for any successful/unsuccessful use of the \"gpasswd\" command by using the following command: \n \n $ sudo auditctl -l | grep -w gpasswd \n -a always,exit -S all -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=-1 -F key=privileged-gpasswd \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful uses of the \"gpasswd\" command. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-gpasswd \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275698","ruleId":"SV-275698r1148144_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful attempts to use the kmod command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS is configured to audit the execution of the module management program \"kmod\" by using the following command: \n \n $ sudo auditctl -l | grep kmod \n -w /bin/kmod -p x -k module \n \nIf the command does not return a line, or the line is commented out, this is a finding. \n \nNote: The \"-k\" value is arbitrary and can be different from the example output above.","fixText":"Configure Ubuntu OS to audit the execution of the module management program \"kmod\". \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-w /bin/kmod -p x -k modules \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275699","ruleId":"SV-275699r1148147_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful attempts to use modprobe command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS is configured to audit the execution of the module management program \"modprobe\" with the following command: \n \n $ sudo auditctl -l | grep /sbin/modprobe \n -w /sbin/modprobe -p x -k modules \n \nIf the command does not return a line, or the line is commented out, this is a finding. \n \nNote: The \"-k\" value is arbitrary and can be different from the example output above.","fixText":"Configure Ubuntu OS to audit the execution of the module management program \"modprobe\". \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-w /sbin/modprobe -p x -k modules \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275700","ruleId":"SV-275700r1148150_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the mount command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS generates audit records upon successful/unsuccessful attempts to use the \"mount\" command by using the following command: \n \n $ sudo auditctl -l | grep /usr/bin/mount \n -a always,exit -S all -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=-1 -F key=privileged-mount \n \nIf the command does not return lines that match the example or the lines are commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"mount\" command. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-mount \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275701","ruleId":"SV-275701r1148153_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the newgrp command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS generates an audit record upon successful/unsuccessful attempts to use the \"newgrp\" command by using the following command: \n \n $ sudo auditctl -l | grep newgrp \n -a always,exit -S all -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=-1 -F key=priv_cmd \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"newgrp\" command. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=unset -k priv_cmd \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275702","ruleId":"SV-275702r1148156_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the pam_timestamp_check command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify an audit event is generated for any successful/unsuccessful use of the \"pam_timestamp_check\" command by using the following command: \n \n $ sudo auditctl -l | grep -w pam_timestamp_check \n -a always,exit -S all -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=-1 -F key=privileged-pam_timestamp_check \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful uses of the \"pam_timestamp_check\" command. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=unset -k privileged-pam_timestamp_check \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275703","ruleId":"SV-275703r1148159_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the passwd command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify an audit event is generated for any successful/unsuccessful use of the \"passwd\" command by using the following command: \n \n $ sudo auditctl -l | grep -w passwd \n -a always,exit -S all -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=-1 -F key=privileged-passwd \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"key\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful uses of the \"passwd\" command. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=unset -k privileged-passwd \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275704","ruleId":"SV-275704r1148162_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the setfacl command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS generates an audit record upon successful/unsuccessful attempts to use the \"setfacl\" command by using the following command: \n \n $ sudo auditctl -l | grep setfacl \n -a always,exit -S all -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=-1 -F key=perm_chng \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"setfacl\" command. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=unset -k perm_chng \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275705","ruleId":"SV-275705r1148165_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the ssh-agent command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS generates an audit record upon successful/unsuccessful attempts to use the \"ssh-agent\" command by using the following command: \n \n $ sudo auditctl -l | grep /usr/bin/ssh-agent \n -a always,exit -S all -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=-1 -F key=privileged-ssh \n \nIf the command does not return lines that match the example or the lines are commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"ssh-agent\" command. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275706","ruleId":"SV-275706r1148168_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the ssh-keysign command.","description":"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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS generates an audit record upon successful/unsuccessful attempts to use the \"ssh-keysign\" command by using the following command: \n \n $ sudo auditctl -l | grep ssh-keysign \n -a always,exit -S all -F path=/usr/lib/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=-1 -F key=privileged-ssh \n \nIf the command does not return lines that match the example or the lines are commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"ssh-keysign\" command. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/lib/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=unset -k privileged-ssh \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275707","ruleId":"SV-275707r1148171_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the su command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS generates audit records upon successful/unsuccessful attempts to use the \"su\" command by using the following command: \n \n $ sudo auditctl -l | grep /bin/su \n -a always,exit -S all -F path=/bin/su -F perm=x -F auid>=1000 -F auid!=-1 -F key=privileged-priv_change \n \nIf the command does not return lines that match the example or the lines are commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure Ubuntu OS to generate audit records when successful/unsuccessful attempts to use the \"su\" command occur. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/bin/su -F perm=x -F auid>=1000 -F auid!=unset -k privileged-priv_change \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275708","ruleId":"SV-275708r1148174_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the sudo command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify an audit event is generated for any successful/unsuccessful use of the \"sudo\" command by using the following command: \n \n $ sudo auditctl -l | grep /usr/bin/sudo \n -a always,exit -S all -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=-1 -F key=priv_cmd \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"sudo\" command. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k priv_cmd \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275709","ruleId":"SV-275709r1148177_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the sudoedit command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS generates an audit record upon successful/unsuccessful attempts to use the \"sudoedit\" command by using the following command: \n \n $ sudo auditctl -l | grep /usr/bin/sudoedit \n -a always,exit -S all -F path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=-1 -F key=priv_cmd \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"sudoedit\" command. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\": \n \n-a always,exit -F path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=unset -k priv_cmd \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275710","ruleId":"SV-275710r1148180_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the umount command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS generates audit records upon successful/unsuccessful attempts to use the \"umount\" command by using the following command: \n \n $ sudo auditctl -l | grep /usr/bin/umount \n -a always,exit -S all -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=-1 -F key=privileged-umount \n \nIf the command does not return lines that match the example or the lines are commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"umount\" command. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=unset -k privileged-umount \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275711","ruleId":"SV-275711r1148183_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the unix_update command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify an audit event is generated for any successful/unsuccessful use of the \"unix_update\" command by using the following command: \n \n $ sudo auditctl -l | grep -w unix_update \n -a always,exit -S all -F path=/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=-1 -F key=privileged-unix-update \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful uses of the \"unix_update\" command. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=unset -k privileged-unix-update \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275712","ruleId":"SV-275712r1148186_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the usermod command.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify an audit event is generated for any successful/unsuccessful use of the \"usermod\" command by using the following command: \n \n $ sudo auditctl -l | grep -w usermod \n -a always,exit -S all -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=-1 -F key=privileged-usermod \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful uses of the \"usermod\" command. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=unset -k privileged-usermod \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275713","ruleId":"SV-275713r1148189_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/group.","description":"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 create an account. Auditing account creation actions provides logging that can be used for forensic purposes. \n \nTo address access requirements, many operating systems may be integrated with enterprise level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.\n\nSatisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000476-GPOS-00221, SRG-OS-000001-GPOS-00001, SRG-OS-000274-GPOS-00104, , SRG-OS-000275-GPOS-00105, SRG-OS-000276-GPOS-00106, SRG-OS-000277-GPOS-00107, SRG-OS-000304-GPOS-00121","checkContent":"Verify Ubuntu OS generates audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/group\" by using the following command: \n \n $ sudo auditctl -l | grep group \n -w /etc/group -p wa -k usergroup_modification \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" value is arbitrary and can be different from the example output above.","fixText":"Configure Ubuntu OS to generate audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/group\". \n \nAdd or modify the following line to \"/etc/audit/rules.d/stig.rules\": \n \n-w /etc/group -p wa -k usergroup_modification \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000018","CCI-000172","CCI-001403","CCI-001404","CCI-001405","CCI-002130","CCI-000015"]},{"vulnId":"V-275714","ruleId":"SV-275714r1148192_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/gshadow.","description":"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 create an account. Auditing account creation actions provides logging that can be used for forensic purposes. \n \nTo address access requirements, many operating systems may be integrated with enterprise level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.\n\nSatisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000476-GPOS-00221, SRG-OS-000001-GPOS-00001, SRG-OS-000274-GPOS-00104, , SRG-OS-000275-GPOS-00105, SRG-OS-000276-GPOS-00106, SRG-OS-000277-GPOS-00107, SRG-OS-000304-GPOS-00121","checkContent":"Verify Ubuntu OS generates audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/gshadow\" by using the following command: \n \n $ sudo auditctl -l | grep gshadow \n -w /etc/gshadow -p wa -k usergroup_modification \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" value is arbitrary and can be different from the example output above.","fixText":"Configure Ubuntu OS to generate audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/gshadow\". \n \nAdd or modify the following line to \"/etc/audit/rules.d/stig.rules\": \n \n-w /etc/gshadow -p wa -k usergroup_modification \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000018","CCI-000172","CCI-001403","CCI-001404","CCI-001405","CCI-002130","CCI-000015"]},{"vulnId":"V-275715","ruleId":"SV-275715r1148195_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/opasswd.","description":"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 create an account. Auditing account creation actions provides logging that can be used for forensic purposes. \n \nTo address access requirements, many operating systems may be integrated with enterprise level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.\n\nSatisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000476-GPOS-00221, SRG-OS-000001-GPOS-00001, SRG-OS-000274-GPOS-00104, , SRG-OS-000275-GPOS-00105, SRG-OS-000276-GPOS-00106, SRG-OS-000277-GPOS-00107, SRG-OS-000304-GPOS-00121","checkContent":"Verify Ubuntu OS generates audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/security/opasswd\" by using the following command: \n \n $ sudo auditctl -l | grep opasswd \n -w /etc/security/opasswd -p wa -k usergroup_modification \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" value is arbitrary and can be different from the example output above.","fixText":"Configure Ubuntu OS to generate audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/security/opasswd\". \n \nAdd or modify the following line to \"/etc/audit/rules.d/stig.rules\": \n \n-w /etc/security/opasswd -p wa -k usergroup_modification \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000018","CCI-000172","CCI-001403","CCI-001404","CCI-001405","CCI-002130","CCI-000015"]},{"vulnId":"V-275716","ruleId":"SV-275716r1148198_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/passwd.","description":"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 create an account. Auditing account creation actions provides logging that can be used for forensic purposes. \n \nTo address access requirements, many operating systems may be integrated with enterprise level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.\n\nSatisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000476-GPOS-00221, SRG-OS-000001-GPOS-00001, SRG-OS-000274-GPOS-00104, , SRG-OS-000275-GPOS-00105, SRG-OS-000276-GPOS-00106, SRG-OS-000277-GPOS-00107, SRG-OS-000304-GPOS-00121, SRG-OS-000470-GPOS-00214","checkContent":"Verify Ubuntu OS generates audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/passwd\" by using the following command: \n \n $ sudo auditctl -l | grep passwd \n -w /etc/passwd -p wa -k usergroup_modification \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" value is arbitrary and can be different from the example output above.","fixText":"Configure Ubuntu OS to generate audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/passwd\". \n \nAdd or modify the following line to \"/etc/audit/rules.d/stig.rules\": \n \n-w /etc/passwd -p wa -k usergroup_modification \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000018","CCI-000172","CCI-001403","CCI-001404","CCI-001405","CCI-002130","CCI-000015"]},{"vulnId":"V-275717","ruleId":"SV-275717r1148201_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow.","description":"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 create an account. Auditing account creation actions provides logging that can be used for forensic purposes. \n \nTo address access requirements, many operating systems may be integrated with enterprise level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.\n\nSatisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000239-GPOS-00089, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000303-GPOS-00120, SRG-OS-000458-GPOS-00203, SRG-OS-000463-GPOS-00207, SRG-OS-000476-GPOS-00221, SRG-OS-000001-GPOS-00001, SRG-OS-000274-GPOS-00104, , SRG-OS-000275-GPOS-00105, SRG-OS-000276-GPOS-00106, SRG-OS-000277-GPOS-00107, SRG-OS-000304-GPOS-00121","checkContent":"Verify Ubuntu OS generates audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/shadow\" by using the following command: \n \n $ sudo auditctl -l | grep shadow \n -w /etc/shadow -p wa -k usergroup_modification \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" value is arbitrary and can be different from the example output above.","fixText":"Configure Ubuntu OS to generate audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/shadow\". \n \nAdd or modify the following line to \"/etc/audit/rules.d/stig.rules\": \n \n-w /etc/shadow -p wa -k usergroup_modification \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000018","CCI-000172","CCI-001403","CCI-001404","CCI-001405","CCI-002130","CCI-000015"]},{"vulnId":"V-275718","ruleId":"SV-275718r1148292_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the chmod, fchmod, and fchmodat system calls.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter). \n \nThe system call rules are loaded into a matching engine that intercepts each syscall that all programs on the system makes. Therefore, it is very important to only use syscall rules when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, though, by combining syscalls into one rule whenever possible.\n\nSatisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206","checkContent":"Verify Ubuntu OS generates an audit record upon successful/unsuccessful attempts to use the \"chmod\", \"fchmod\", and \"fchmodat\" system calls by using the following command: \n \n $ sudo auditctl -l | grep chmod \n -a always,exit -F arch=b32 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=-1 -F key=perm_chng \n -a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=-1 -F key=perm_chng \n \nIf the command does not return audit rules for the \"chmod\", \"fchmod\", and \"fchmodat\" syscalls or the lines are commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"chmod\", \"fchmod\", and \"fchmodat\" system calls. \n \nAdd or modify the following lines in the \"/etc/audit/rules.d/stig.rules\": \n \n-a always,exit -F arch=b32 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=unset -k perm_chng \n-a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=unset -k perm_chng \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275719","ruleId":"SV-275719r1148207_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the chown, fchown, fchownat, and lchown system calls.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter). \n \nThe system call rules are loaded into a matching engine that intercepts each syscall that all programs on the system makes. Therefore, it is very important to only use syscall rules when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, though, by combining syscalls into one rule whenever possible.\n\nSatisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206","checkContent":"Verify Ubuntu OS generates an audit record upon successful/unsuccessful attempts to use the \"chown\", \"fchown\", \"fchownat\", and \"lchown\" system calls by using the following command: \n \n $ sudo auditctl -l | grep chown \n -a always,exit -F arch=b32 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=-1 -F key=perm_chng \n -a always,exit -F arch=b64 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=-1 -F key=perm_chng \n \nIf the command does not return audit rules for the \"chown\", \"fchown\", \"fchownat\", and \"lchown\" syscalls or the lines are commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"chown\", \"fchown\", \"fchownat\", and \"lchown\" system calls. \n \nAdd or modify the following lines in the \"/etc/audit/rules.d/stig.rules\": \n \n-a always,exit -F arch=b32 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=unset -k perm_chng \n-a always,exit -F arch=b64 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=unset -k perm_chng \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275720","ruleId":"SV-275720r1148270_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the creat, open, openat, open_by_handle_at, truncate, and ftruncate system calls.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter). \n \nThe system call rules are loaded into a matching engine that intercepts each syscall that all programs on the system makes. Therefore, it is very important to only use syscall rules when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, though, by combining syscalls into one rule whenever possible.\n\nSatisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000474-GPOS-00219","checkContent":"Verify Ubuntu OS generates an audit record upon unsuccessful attempts to use the \"creat\", \"open\", \"openat\", \"open_by_handle_at\", \"truncate\", and \"ftruncate\" system calls by using the following command: \n \n $ sudo auditctl -l | grep 'open\\|truncate\\|creat' \n -a always,exit -F arch=b32 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=-1 -F key=perm_access \n -a always,exit -F arch=b32 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=-1 -F key=perm_access \n -a always,exit -F arch=b64 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=-1 -F key=perm_access \n -a always,exit -F arch=b64 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=-1 -F key=perm_access \n \nIf the command does not return audit rules for the \"creat\", \"open\", \"openat\", \"open_by_handle_at\", \"truncate\", and \"ftruncate\" syscalls or the lines are commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any unsuccessful use of the \"creat\", \"open\", \"openat\", \"open_by_handle_at\", \"truncate\", and \"ftruncate\" system calls. \n \nAdd or modify the following lines in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F arch=b32 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k perm_access \n-a always,exit -F arch=b32 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k perm_access \n-a always,exit -F arch=b64 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=unset -k perm_access \n-a always,exit -F arch=b64 -S creat,open,openat,open_by_handle_at,truncate,ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=unset -k perm_access \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275721","ruleId":"SV-275721r1148213_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the delete_module system call.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS generates an audit record for any successful/unsuccessful attempts to use the \"delete_module\" syscall by using the following command: \n \n $ sudo auditctl -l | grep -w delete_module \n -a always,exit -F arch=b32 -S delete_module -F auid>=1000 -F auid!=-1 -F key=module_chng \n -a always,exit -F arch=b64 -S delete_module -F auid>=1000 -F auid!=-1 -F key=module_chng \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"delete_module\" syscall. \n \nAdd or modify the following lines in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F arch=b32 -S delete_module -F auid>=1000 -F auid!=unset -k module_chng \n-a always,exit -F arch=b64 -S delete_module -F auid>=1000 -F auid!=unset -k module_chng \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275722","ruleId":"SV-275722r1148216_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for successful/unsuccessful uses of the init_module and finit_module system calls.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter). \n \nThe system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to only use syscall rules when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, though, by combining syscalls into one rule whenever possible.\n\nSatisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000471-GPOS-00216","checkContent":"Verify Ubuntu OS generates an audit record for any successful/unsuccessful attempts to use the \"init_module\" and \"finit_module\" syscalls by using the following command: \n \n $ sudo auditctl -l | grep init_module \n -a always,exit -F arch=b32 -S init_module,finit_module -F auid>=1000 -F auid!=-1 -F key=module_chng \n -a always,exit -F arch=b64 -S init_module,finit_module -F auid>=1000 -F auid!=-1 -F key=module_chng \n \nIf the command does not return audit rules for the \"init_module\" and \"finit_module\" syscalls or the lines are commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"init_module\" and \"finit_module\" syscalls. \n \nAdd or modify the following lines in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F arch=b32 -S init_module,finit_module -F auid>=1000 -F auid!=unset -k module_chng \n-a always,exit -F arch=b64 -S init_module,finit_module -F auid>=1000 -F auid!=unset -k module_chng \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275723","ruleId":"SV-275723r1148219_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for any use of the setxattr, fsetxattr, lsetxattr, removexattr, fremovexattr, and lremovexattr system calls.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter). \n \nThe system call rules are loaded into a matching engine that intercepts each syscall made by all programs on the system. Therefore, it is very important to only use syscall rules when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, though, by combining syscalls into one rule whenever possible.\n\nSatisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000462-GPOS-00206","checkContent":"Verify Ubuntu OS generates an audit record upon successful/unsuccessful attempts to use the \"setxattr\", \"fsetxattr\", \"lsetxattr\", \"removexattr\", \"fremovexattr\", and \"lremovexattr\" system calls by using the following command: \n \n $ sudo auditctl -l | grep xattr \n -a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=-1 -F key=perm_mod \n -a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod \n -a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=-1 -F key=perm_mod \n -a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod \n \nIf the command does not return audit rules for the \"setxattr\", \"fsetxattr\", \"lsetxattr\", \"removexattr\", \"fremovexattr\" and \"lremovexattr\" syscalls or the lines are commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful use of the \"setxattr\", \"fsetxattr\", \"lsetxattr\", \"removexattr\", \"fremovexattr\", and \"lremovexattr\" system calls. \n \nAdd or modify the following lines in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=unset -k perm_mod \n-a always,exit -F arch=b32 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod \n-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid>=1000 -F auid!=unset -k perm_mod \n-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275724","ruleId":"SV-275724r1148222_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for any successful/unsuccessful use of unlink, unlinkat, rename, renameat, and rmdir system calls.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter). \n \nThe system call rules are loaded into a matching engine that intercepts each syscall that all programs on the system makes. Therefore, it is very important to only use syscall rules when absolutely necessary since these affect performance. The more rules, the bigger the performance hit. The performance is helped, though, by combining syscalls into one rule whenever possible.","checkContent":"Verify Ubuntu OS generates audit records for any successful/unsuccessful use of \"unlink\", \"unlinkat\", \"rename\", \"renameat\", and \"rmdir\" system calls by using the following command: \n \n $ sudo auditctl -l | grep 'unlink\\|rename\\|rmdir' \n -a always,exit -F arch=b64 -S unlink,unlinkat,rename,renameat,rmdir -F auid>=1000 -F auid!=-1 -F key=delete \n -a always,exit -F arch=b32 -S unlink,unlinkat,rename,renameat,rmdir -F auid>=1000 -F auid!=-1 -F key=delete \n \nIf the command does not return audit rules for the \"unlink\", \"unlinkat\", \"rename\", \"renameat\", and \"rmdir\" syscalls or the lines are commented out, this is a finding. \n \nNote: The \"key\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.","fixText":"Configure the audit system to generate audit events for any successful/unsuccessful use of \"unlink\", \"unlinkat\", \"rename\", \"renameat\", and \"rmdir\" system calls. \n \nAdd or modify the following lines in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F arch=b64 -S unlink,unlinkat,rename,renameat,rmdir -F auid>=1000 -F auid!=unset -k delete \n-a always,exit -F arch=b32 -S unlink,unlinkat,rename,renameat,rmdir -F auid>=1000 -F auid!=unset -k delete \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275725","ruleId":"SV-275725r1148225_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for all events that affect the systemd journal files.","description":"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 system level binaries and their operation. Auditing the systemd journal files provides logging that can be used for forensic purposes. \n \nTo address access requirements, many operating systems may be integrated with enterprise level authentication/access/auditing mechanisms that meet or exceed access control policy requirements.","checkContent":"Verify Ubuntu OS generates audit records for all events that affect \"/var/log/journal\" by using the following command: \n \n $ sudo auditctl -l | grep journal \n -w /var/log/journal -p wa -k systemd_journal \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" value is arbitrary and can be different from the example output above.","fixText":"Configure Ubuntu OS to generate audit records for events that affect \"/var/log/journal\". \n \nAdd or modify the following line to \"/etc/audit/rules.d/stig.rules\": \n \n-w /var/log/journal -p wa -k systemd_journal \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000366"]},{"vulnId":"V-275726","ruleId":"SV-275726r1148228_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for the /var/log/btmp file.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS generates audit records showing start and stop times for user access to the system via the \"/var/log/btmp\" file by using the following command: \n \n $ sudo auditctl -l | grep '/var/log/btmp' \n -w /var/log/btmp -p wa -k logins \n \nIf the command does not return a line matching the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate audit events showing start and stop times for user access via the \"/var/log/btmp file\". \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-w /var/log/btmp -p wa -k logins \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275727","ruleId":"SV-275727r1148231_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for the /var/log/wtmp file.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS generates audit records showing start and stop times for user access to the system via the \"/var/log/wtmp\" file by using the following command: \n \n $ sudo auditctl -l | grep '/var/log/wtmp' \n -w /var/log/wtmp -p wa -k logins \n \nIf the command does not return a line matching the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate audit events showing start and stop times for user access via the \"/var/log/wtmp\" file. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-w /var/log/wtmp -p wa -k logins \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275728","ruleId":"SV-275728r1148234_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for the /var/run/utmp file.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS generates audit records showing start and stop times for user access to the system via the \"/var/run/utmp\" file by using the following command: \n \n $ sudo auditctl -l | grep '/var/run/utmp' \n -w /var/run/utmp -p wa -k logins \n \nIf the command does not return a line matching the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate audit events showing start and stop times for user access via the \"/var/run/utmp\" file. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-w /var/run/utmp -p wa -k logins \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275729","ruleId":"SV-275729r1148237_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for the use and modification of the faillog file.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).\n\nSatisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000470-GPOS-00214, SRG-OS-000473-GPOS-00218","checkContent":"Verify Ubuntu OS generates an audit record upon successful/unsuccessful modifications to the \"faillog\" file by using the following command: \n \n $ sudo auditctl -l | grep faillog \n -w /var/log/faillog -p wa -k logins \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful modifications to the \"faillog\" file. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-w /var/log/faillog -p wa -k logins \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275730","ruleId":"SV-275730r1148240_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for the use and modification of the lastlog file.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).\n\nSatisfies: SRG-OS-000064-GPOS-00033, SRG-OS-000470-GPOS-00214, SRG-OS-000473-GPOS-00218","checkContent":"Verify Ubuntu OS generates an audit record when successful/unsuccessful modifications to the \"lastlog\" file occur by using the following command: \n \n $ sudo auditctl -l | grep lastlog \n -w /var/log/lastlog -p wa -k logins \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" value is arbitrary and can be different from the example output above.","fixText":"Configure the audit system to generate an audit event for any successful/unsuccessful modifications to the \"lastlog\" file. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-w /var/log/lastlog -p wa -k logins \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275731","ruleId":"SV-275731r1148243_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records when successful/unsuccessful attempts to modify the /etc/sudoers file occur.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS generates audit records for all modifications that affect \"/etc/sudoers\" by using the following command: \n \n $ sudo auditctl -l | grep sudoers \n -w /etc/sudoers -p wa -k privilege_modification \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" value is arbitrary and can be different from the example output above.","fixText":"Configure Ubuntu OS to generate audit records for all modifications that affect \"/etc/sudoers\". \n \nAdd or modify the following line to \"/etc/audit/rules.d/stig.rules\": \n \n-w /etc/sudoers -p wa -k privilege_modification \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275732","ruleId":"SV-275732r1148294_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records when successful/unsuccessful attempts to modify the /etc/sudoers.d directory occur.","description":"Without generating audit records 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. \n \nAudit records can be generated from various components within the information system (e.g., module or policy filter).","checkContent":"Verify Ubuntu OS generates audit records for all modifications that affect \"/etc/sudoers.d\" directory by using the following command: \n \n $ sudo auditctl -l | grep sudoers.d \n -w /etc/sudoers.d -p wa -k privilege_modification \n \nIf the command does not return a line that matches the example or the line is commented out, this is a finding. \n \nNote: The \"-k\" value is arbitrary and can be different from the example output above.","fixText":"Configure Ubuntu OS to generate audit records for all modifications that affect \"/etc/sudoers.d\" directory. \n \nAdd or modify the following line to \"/etc/audit/rules.d/stig.rules\": \n \n-w /etc/sudoers.d -p wa -k privilege_modification \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172"]},{"vulnId":"V-275733","ruleId":"SV-275733r1148249_rule","severity":"medium","ruleTitle":"Ubuntu OS 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.","description":"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. \n \nSome programs and processes are required to operate at a higher privilege level and therefore, must be excluded from the organization-defined software list after review.\n\nSatisfies: SRG-OS-000326-GPOS-00126, SRG-OS-000327-GPOS-00127, SRG-OS-000755-GPOS-00220","checkContent":"Verify Ubuntu OS audits the execution of privilege functions by auditing the \"execve\" system call by using the following command: \n \n $ sudo auditctl -l | grep execve \n -a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -F key=execpriv \n -a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -F key=execpriv \n -a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -F key=execpriv \n -a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -F key=execpriv \n \nIf the command does not return lines that match the example or the lines are commented out, this is a finding. \n \nNote: The \"key=\" value is arbitrary and can be different from the example output above.","fixText":"Configure Ubuntu OS to audit the execution of all privileged functions. \n \nAdd or modify the following lines in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-a always,exit -F arch=b64 -S execve -C uid!=euid -F euid=0 -k execpriv \n-a always,exit -F arch=b64 -S execve -C gid!=egid -F egid=0 -k execpriv \n-a always,exit -F arch=b32 -S execve -C uid!=euid -F euid=0 -k execpriv \n-a always,exit -F arch=b32 -S execve -C gid!=egid -F egid=0 -k execpriv \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-002233","CCI-002234","CCI-004188"]},{"vulnId":"V-275734","ruleId":"SV-275734r1148252_rule","severity":"medium","ruleTitle":"Ubuntu OS must generate audit records for privileged activities, nonlocal maintenance, diagnostic sessions, and other system-level access.","description":"If events associated with nonlocal administrative access or diagnostic sessions are not logged, a major tool for assessing and investigating attacks would not be available. \n \nThis requirement addresses auditing-related issues associated with maintenance tools used specifically for diagnostic and repair actions on organizational information systems. \n \nNonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. \n \nThis requirement applies to hardware/software diagnostic test equipment or tools. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system, for example, the software implementing \"ping,\" \"ls,\" \"ipconfig,\" or the hardware and software implementing the monitoring port of an Ethernet switch.\n\nSatisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000471-GPOS-00215","checkContent":"Verify Ubuntu OS audits activities performed during nonlocal maintenance and diagnostic sessions by using the following command: \n \n $ sudo auditctl -l | grep sudo.log \n -w /var/log/sudo.log -p wa -k maintenance \n \nIf the command does not return lines that match the example or the lines are commented out, this is a finding. \n \nNote: The \"-k\" value is arbitrary and can be different from the example output above.","fixText":"Configure Ubuntu OS to audit activities performed during nonlocal maintenance and diagnostic sessions. \n \nAdd or modify the following line in the \"/etc/audit/rules.d/stig.rules\" file: \n \n-w /var/log/sudo.log -p wa -k maintenance \n \nTo reload the rules file, issue the following command: \n \n $ sudo augenrules --load \n \nNote: The \"-k \" at the end of the line gives the rule a unique meaning to help during an audit investigation. The does not need to match the example above.","ccis":["CCI-000172","CCI-002884","CCI-004188"]},{"vulnId":"V-275735","ruleId":"SV-275735r1148255_rule","severity":"high","ruleTitle":"Ubuntu OS must implement NIST FIPS-validated cryptography.","description":"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.\n\nSatisfies: SRG-OS-000396-GPOS-00176, SRG-OS-000478-GPOS-00223, SRG-OS-000112-GPOS-00057, SRG-OS-000113-GPOS-00058","checkContent":"Verify the system is configured to run in FIPS mode by using the following command: \n \n $ grep -i 1 /proc/sys/crypto/fips_enabled \n 1 \n \nIf a value of \"1\" is not returned, this is a finding.","fixText":"Configure Ubuntu OS to run in FIPS mode. Add \"fips=1\" to the kernel parameter during Ubuntu OS install. \n \nEnabling a FIPS mode on a pre-existing system involves a number of modifications to Ubuntu OS. Refer to the Ubuntu Pro security certification documentation for instructions. \n \nA subscription to the Ubuntu Pro plan is required to obtain the FIPS Kernel cryptographic modules and enable FIPS. \n \nNote: Ubuntu Pro security certification instructions can be found at: https://ubuntu.com/security/certifications/docs/fips-enablement.","ccis":["CCI-002450","CCI-001941"]}]}