{"stig":{"title":"Canonical Ubuntu 24.04 LTS Security Technical Implementation Guide","version":"1","release":"5"},"checks":[{"vulnId":"V-270645","ruleId":"SV-270645r1068357_rule","severity":"low","ruleTitle":"Ubuntu 24.04 LTS 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 with 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. Purge the remaining configuration files for \"systemd-timesyncd\" from Ubuntu 24.04 LTS:\n\n$ sudo apt-get purge systemd-timesyncd","ccis":["CCI-000366"]},{"vulnId":"V-270646","ruleId":"SV-270646r1068358_rule","severity":"low","ruleTitle":"Ubuntu 24.04 LTS 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 with 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 using the following command:\n\n$ sudo apt remove ntp\n\nIf there are additional configuration files on the system that must be removed, the following command can be used instead:\n\n$ sudo apt-get purge ntp","ccis":["CCI-000366"]},{"vulnId":"V-270647","ruleId":"SV-270647r1066430_rule","severity":"high","ruleTitle":"Ubuntu 24.04 LTS must not have the telnet package installed.","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 24.04 LTS 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 telnet package is not installed on Ubuntu 24.04 LTS with the following command: \n \n$ dpkg -l | grep telnetd \n\nIf the telnetd package is installed, this is a finding.","fixText":"Remove the telnet package from Ubuntu 24.04 LTS with the following command: \n \n$ sudo apt remove telnetd","ccis":["CCI-000197"]},{"vulnId":"V-270648","ruleId":"SV-270648r1066433_rule","severity":"high","ruleTitle":"Ubuntu 24.04 LTS 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 \nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). \n \nExamples of nonessential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled.","checkContent":"Verify the rsh-server package is installed with the following command: \n \n$ dpkg -l | grep rsh-server \n \nIf the rsh-server package is installed, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to disable nonessential capabilities by removing the rsh-server package from the system with the following command: \n \n$ sudo apt remove rsh-server","ccis":["CCI-000381"]},{"vulnId":"V-270649","ruleId":"SV-270649r1067136_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must use a file integrity tool to verify correct operation of all security functions.","description":"Without verification, 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 24.04 LTS performing security function verification/testing and/or systems and environments that require this functionality.","checkContent":"Verify that Advanced Intrusion Detection Environment (AIDE) is installed and verifies the correct operation of all security functions with the following command:\n\n$ dpkg -l | grep aide\nii  aide     0.18.6-2build2     amd64     Advanced Intrusion Detection Environment - dynamic binary\nii  aide-common     0.18.6-2build2     all     Advanced Intrusion Detection Environment - Common files\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\" file integrity package:\n\n$ sudo apt install -y aide","ccis":["CCI-002696"]},{"vulnId":"V-270650","ruleId":"SV-270650r1155241_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must configure AIDE to perform file integrity checking on the file system if installed.","description":"Without verification, 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 24.04 LTS performing security function verification/testing and/or systems and environments that require this functionality.","checkContent":"Note: If a file integrity tool other than Advanced Intrusion Detection Environment (AIDE) is employed, this requirement is not applicable.\n\nVerify AIDE is configured on the system by performing a manual check:\n\n$ sudo aide -c /etc/aide/aide.conf --check\n\nExample output:\n...\nStart timestamp: 2024-10-30 14:22:38 -0400 (AIDE 0.18.6)\nAIDE found differences between database and filesystem!!\n...\n\nIf AIDE is being used for system file integrity checking and the command fails, this is a finding.","fixText":"Initialize the AIDE package (this may take a few minutes):\n$ sudo aideinit\nRunning aide --init...\n\nThe new database will need to be renamed to be read by AIDE:\n$ sudo cp -p /var/lib/aide/aide.db.new /var/lib/aide/aide.db\n\nPerform a manual check:\n$ sudo aide -c /etc/aide/aide.conf --check\n\nExample output:\n...\nStart timestamp: 2024-10-30 14:22:38 -0400 (AIDE 0.18.6)\nAIDE found differences between database and filesystem!!\n...\n\nDone.","ccis":["CCI-002696"]},{"vulnId":"V-270651","ruleId":"SV-270651r1068395_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must be configured so that the script which runs each 30 days or less to check file integrity is the default one.","description":"Without verification, 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 24.04 LTS performing security function verification/testing and/or systems and environments that require this functionality.","checkContent":"Note: If AIDE is not installed, this finding is not applicable.\n\nCheck the AIDE configuration file integrity installed on the system (the default configuration file is located at /etc/aide/aide.conf or in /etc/aide/aide.conf.d/) with the following command:\n$ sudo sha256sum /etc/aide/aide.conf\nf3bbea2552f2c5b475627850d8a5fba1659df6466986d5a18948d9821ecbe491  /etc/aide/aide.conf\n\nDownload the original aide-common package in the /tmp directory: \n$ cd /tmp; apt download aide-common \n\nGenerate the checksum from the aide.conf file in the downloaded .deb package:\n$ sudo dpkg-deb --fsys-tarfile /tmp/aide-common_0.18.6-2build2_all.deb | tar -xO ./usr/share/aide/config/aide/aide.conf | sha256sum\nf3bbea2552f2c5b475627850d8a5fba1659df6466986d5a18948d9821ecbe491  -\n\nIf the checksums of the system file (/etc/aide/aide.conf) and the extracted file do not match, this is a finding.\n\nTo verify the frequency of the file integrity checks, inspect the contents of the scheduled jobs as follows:\n\nChecking scheduled cron jobs:\n$ grep -r aide /etc/cron* /etc/crontab\n/etc/cron.daily/dailyaidecheck:SCRIPT=\"/usr/share/aide/bin/dailyaidecheck\"\n\nChecking the systemd timer (this will show when the next scheduled run occurs and the last time the AIDE check was triggered):\n$ sudo systemctl list-timers | grep aide\nThu 2024-10-31 02:01:58 EDT           10h Wed 2024-10-30 13:47:41 EDT            - dailyaidecheck.timer           dailyaidecheck.service\n\nThe contents of these files can be inspected with the following commands:\n$ sudo systemctl cat dailyaidecheck.timer\n$ sudo systemctl cat dailyaidecheck.service\n\nIf there is no AIDE script file in the cron directories or in the systemd timer, 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 \nDownload the original package to the /tmp dir: \n \n$ cd /tmp; apt download aide-common \n \nExtract the aide script to its original place: \n\n$ dpkg-deb --fsys-tarfile /tmp/aide-common_*.deb | sudo tar -x --wildcards ./usr/share/aide/config/cron.daily/dailyaidecheck* -C /\n \nCopy it to the cron.daily directory: \n \n$  sudo cp -f /usr/share/aide/config/cron.daily/aide /etc/cron.daily/dailyaidecheck*","ccis":["CCI-002699"]},{"vulnId":"V-270652","ruleId":"SV-270652r1067138_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must notify designated personnel if baseline configurations are changed in an unauthorized manner. The file integrity tool must notify the system administrator (SA) when changes to the baseline configuration or anomalies in the operation of any security functions are discovered.","description":"Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to Ubuntu 24.04 LTS. Changes to Ubuntu 24.04 LTS 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 Ubuntu 24.04 LTS. Ubuntu 24.04 LTS' IMO/information system security officer (ISSO) and 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-000447-GPOS-00201, SRG-OS-000363-GPOS-00150","checkContent":"Verify that Advanced Intrusion Detection Environment (AIDE) notifies the SA when anomalies in the operation of any security functions are discovered with the following command: \n \n$ grep SILENTREPORTS /etc/default/aide\nSILENTREPORTS=no\n \nIf \"SILENTREPORTS\" is set to \"yes\", is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to notify designated personnel if baseline configurations are changed in an unauthorized manner. \n \nModify the \"SILENTREPORTS\" parameter in the \"/etc/default/aide\" file with a value of \"no\" if it does not already exist as follows:\n\nSILENTREPORTS=no","ccis":["CCI-002702","CCI-001744"]},{"vulnId":"V-270653","ruleId":"SV-270653r1067141_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 with the following command: \n \n$ dpkg -l | grep rsyslog \nii  rsyslog     8.2312.0-3ubuntu9      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 with the following command: \n \n$ systemctl is-enabled rsyslog\nenabled \n \nIf the command above returns \"disabled\", this is a finding. \n \nCheck that the log service is properly running and active on the system with the following command: \n \n$ systemctl is-active rsyslog\nactive \n \nIf the command above returns \"inactive\", this is a finding.","fixText":"Configure the log service to collect failure events. \n \nInstall the log service (if the log service is not already installed) with the following command: \n \n$ sudo apt install -y rsyslog \n \nEnable the log service with the following command: \n \n$ sudo systemctl enable --now rsyslog","ccis":["CCI-001665"]},{"vulnId":"V-270654","ruleId":"SV-270654r1067143_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must have an application firewall installed in order 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 24.04 LTS 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 that the Uncomplicated Firewall (ufw) is installed with the following command: \n \n$ dpkg -l | grep ufw\nii  ufw         0.36.2-6     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 install -y ufw","ccis":["CCI-002314"]},{"vulnId":"V-270655","ruleId":"SV-270655r1067145_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS 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).\n\nSatisfies: SRG-OS-000297-GPOS-00115, SRG-OS-000480-GPOS-00232","checkContent":"Verify the ufw is enabled on the system with the following command: \n \n$ sudo ufw status\nStatus: active\n \nIf the above command returns the status as \"inactive\" or any type of error, this is a finding. \n\nIf the ufw is not installed, ask the system administrator if another application firewall is installed. If a different firewall is active on the system, this is not a finding.","fixText":"Enable the ufw by using the following command: \n \n$ sudo ufw enable\n\nNote: Enabling the firewall will potentially disrupt ssh sessions.","ccis":["CCI-002314"]},{"vulnId":"V-270656","ruleId":"SV-270656r1067148_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 Ubuntu 24.04 LTS does not provide the ability to centrally review Ubuntu 24.04 LTS logs, forensic analysis is negatively impacted. \n \nAssociating event types with detected events in Ubuntu 24.04 LTS 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-000365-GPOS-00152, SRG-OS-000337-GPOS-00129, SRG-OS-000062-GPOS-00031, SRG-OS-000475-GPOS-00220, SRG-OS-000042-GPOS-00020, SRG-OS-000042-GPOS-00021, 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-000051-GPOS-00024, SRG-OS-000054-GPOS-00025, SRG-OS-000122-GPOS-00063, 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","checkContent":"Verify the audit service is configured to produce audit records with the following command: \n \n$ dpkg -l | grep auditd \nii  auditd     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":"Configure the audit service to produce audit records containing the information needed to establish when (date and time) an event occurred. \n \nInstall the audit service (if the audit service is not already installed) with the following command: \n \n$ sudo apt install -y auditd","ccis":["CCI-003938","CCI-001914","CCI-000169","CCI-000172","CCI-000135","CCI-000130","CCI-000131","CCI-000132","CCI-000133","CCI-000134","CCI-000154","CCI-000158","CCI-001876","CCI-001875","CCI-001877","CCI-001878","CCI-001879","CCI-001880","CCI-001881","CCI-001882"]},{"vulnId":"V-270657","ruleId":"SV-270657r1066460_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 Ubuntu 24.04 LTS does not provide the ability to centrally review Ubuntu 24.04 LTS logs, forensic analysis is negatively impacted. \n \nAssociating event types with detected events in Ubuntu 24.04 LTS 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-000365-GPOS-00152, SRG-OS-000337-GPOS-00129, SRG-OS-000062-GPOS-00031, SRG-OS-000475-GPOS-00220, SRG-OS-000042-GPOS-00020, SRG-OS-000042-GPOS-00021, 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-000051-GPOS-00024, SRG-OS-000054-GPOS-00025, SRG-OS-000122-GPOS-00063, 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","checkContent":"Verify the audit service is enabled with the following command: \n \n$ systemctl is-enabled auditd.service \nenabled\n\nIf the command above returns \"disabled\", this is a finding. \n \nVerify the audit service is properly running and active on the system with the following command: \n \n$ systemctl is-active auditd.service \nactive \n \nIf the command above returns \"inactive\", this is a finding.","fixText":"Configure the audit service to produce audit records containing the information needed to establish when (date and time) an event occurred. \n \nEnable the audit service with the following command: \n \n$ sudo systemctl enable auditd.service \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-003938","CCI-001914","CCI-000169","CCI-000172","CCI-000135","CCI-000130","CCI-000131","CCI-000132","CCI-000133","CCI-000134","CCI-000154","CCI-000158","CCI-001876","CCI-001875","CCI-001877","CCI-001878","CCI-001879","CCI-001880","CCI-001881","CCI-001882"]},{"vulnId":"V-270658","ruleId":"SV-270658r1067151_rule","severity":"low","ruleTitle":"Ubuntu 24.04 LTS audit event multiplexor must be configured to offload audit logs onto a different system or storage media from the system being audited.","description":"Information stored in one location is vulnerable to accidental or incidental deletion or alteration. \n \nOffloading is a common process in information systems with limited audit storage capacity.\n\nSatisfies: SRG-OS-000342-GPOS-00133, SRG-OS-000479-GPOS-00224","checkContent":"Verify the audit event multiplexor is configured to offload audit records to a different system or storage media from the system being audited. \n \nCheck that audisp-remote plugin is installed:\n\n$ dpkg -l | grep audispd-plugins\nii  audispd-plugins     1:3.1.2-2.1build1.1     amd64     Plugins for the audit event dispatcher \n\nIf the packet is \"not installed\", this is a finding. \n \nCheck that the records are being offloaded to a remote server with the following command: \n \n$ sudo grep -i active /etc/audit/plugins.d/au-remote.conf\nactive = 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\nremote_server = 192.168.122.126 \n \nIf the \"remote_server\" parameter is not set, is set with a local address, or is set with an invalid address, this is a finding.","fixText":"Configure the audit event multiplexor to offload audit records to a different system or storage media from the system being audited. \n \nInstall the audisp-remote plugin: \n \n$ sudo apt install -y 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 address of the remote machine by editing the \"/etc/audit/audisp-remote.conf\" file: \n \n$ sudo sed -i -E 's/(remote_server\\s*=).*/\\1 <remote addr>/' /etc/audit/audisp-remote.conf \n \nwhere <remote addr> must be substituted by the address of the remote server receiving the audit log. \n \nMake the audit service reload its configuration files: \n \n$ sudo systemctl restart auditd.service","ccis":["CCI-001851"]},{"vulnId":"V-270659","ruleId":"SV-270659r1066466_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must have AppArmor 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 Ubuntu 24.04 LTS-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 24.04 LTS has AppArmor installed with the following command:\n \n$ dpkg -l | grep apparmor\nii  apparmor                                4.0.1really4.0.1-0ubuntu0.24.04.3        amd64        user-space parser utility for AppArmor\nii  libapparmor1:amd64                      4.0.1really4.0.1-0ubuntu0.24.04.3        amd64        changehat AppArmor library\n \nIf the AppArmor package is not installed, this is a finding.","fixText":"Install \"AppArmor\" with the following command: \n \n$ sudo apt install apparmor \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. Refer to the AppArmor documentation for more information on configuring profiles.","ccis":["CCI-002165","CCI-001764","CCI-001774"]},{"vulnId":"V-270660","ruleId":"SV-270660r1066469_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 Ubuntu 24.04 LTS-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-000324-GPOS-00125, SRG-OS-000370-GPOS-00155","checkContent":"Verify Ubuntu 24.04 LTS AppArmor active with the following commands: \n \n$ systemctl is-active apparmor.service\nactive \n \nIf \"active\" is not returned, this is a finding. \n \n$ systemctl is-enabled apparmor.service \nenabled \n \nIf \"enabled\" is not returned, this is a finding.","fixText":"Enable \"apparmor\" with the following command:\n \n$ sudo systemctl enable apparmor.service \n \nStart \"apparmor\" with the following command: \n \n$ sudo systemctl start apparmor.service \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. Refer to the AppArmor documentation for more information on configuring profiles.","ccis":["CCI-001764","CCI-002235","CCI-001774"]},{"vulnId":"V-270661","ruleId":"SV-270661r1067175_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS has the \"libpam-pwquality\" package installed with the following command: \n \n$ dpkg -l | grep libpam-pwquality\nii  libpam-pwquality:amd64     1.4.5-3build1     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 install -y libpam-pwquality","ccis":["CCI-000366"]},{"vulnId":"V-270662","ruleId":"SV-270662r1067156_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must have the \"SSSD\" package installed.","description":"Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased. \n \nMultifactor authentication requires using two or more factors to achieve authentication. \n \nFactors include:  \n1) Something a user knows (e.g., password/PIN); \n2) Something a user has (e.g., cryptographic identification device, token); and \n3) Something a user is (e.g., biometric). \n \nA privileged account is defined as an information system account with authorizations of a privileged user. \n \nNetwork access is defined as access to an information system by a user (or a process acting on behalf of a user) communicating through a network (e.g., local area network, wide area network, or the internet). \n \nThe DOD common access card (CAC) with DOD-approved PKI is an example of multifactor authentication.\n\nSatisfies: SRG-OS-000705-GPOS-00150, SRG-OS-000105-GPOS-00052, SRG-OS-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000108-GPOS-00055, SRG-OS-000375-GPOS-00160","checkContent":"Verify Ubuntu 24.04 LTS has the packages required for multifactor authentication installed with the following command:\n\n$ dpkg -l | grep sssd\nii  sssd     2.9.4-1.1ubuntu6.1     amd64     System Security Services Daemon -- metapackage\nii  sssd-ad     2.9.4-1.1ubuntu6.1     amd64     System Security Services Daemon -- Active Directory back end\nii  sssd-ad-common     2.9.4-1.1ubuntu6.1     amd64     System Security Services Daemon -- PAC responder\nii  sssd-common     2.9.4-1.1ubuntu6.1     amd64     System Security Services Daemon -- common files\nii  sssd-ipa     2.9.4-1.1ubuntu6.1     amd64     System Security Services Daemon -- IPA back end\nii  sssd-krb5     2.9.4-1.1ubuntu6.1     amd64     System Security Services Daemon -- Kerberos back end\nii  sssd-krb5-common     2.9.4-1.1ubuntu6.1     amd64     System Security Services Daemon -- Kerberos helpers\nii  sssd-ldap     2.9.4-1.1ubuntu6.1     amd64     System Security Services Daemon -- LDAP back end\nii  sssd-proxy     2.9.4-1.1ubuntu6.1     amd64     System Security Services Daemon -- proxy back end\n\nIf the \"sssd\" package is not installed, this is a finding. The additional sssd components listed by the command may differ from configuration to configuration.  \n\nEnsure that \"libpam-sss\" (the PAM integration module for SSSD) is installed with the following command:\n\n$ dpkg -l | grep libpam-sss\ni  libpam-sss:amd64     2.9.4-1.1ubuntu6.1     amd64     Pam module for the System Security Services Daemon\n\nEnsure that \"libnss-sss\" (the NSS module for retrieving user and group information) is installed with the following command:\n\n$ dpkg -l | grep libnss-sss\nii  libnss-sss:amd64     2.9.4-1.1ubuntu6.1      amd64     Nss library for the System Security Services Daemon","fixText":"Install the sssd.service and the required pam packages with the following commands: \n \n$ sudo apt install -y sssd\n\n$ sudo apt install -y libpam-sss\n\n$ sudo apt install -y libnss-sss","ccis":["CCI-004046","CCI-004047","CCI-000765","CCI-000766"]},{"vulnId":"V-270663","ruleId":"SV-270663r1066478_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must use the \"SSSD\" package for multifactor authentication services.","description":"Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased. \n \nMultifactor authentication requires using two or more factors to achieve authentication. \n \nFactors include:  \n1) Something a user knows (e.g., password/PIN); \n2) Something a user has (e.g., cryptographic identification device, token); and \n3) Something a user is (e.g., biometric). \n \nA privileged account is defined as an information system account with authorizations of a privileged user. \n \nNetwork access is defined as access to an information system by a user (or a process acting on behalf of a user) communicating through a network (e.g., local area network, wide area network, or the internet). \n \nThe DOD common access card (CAC) with DOD-approved PKI is an example of multifactor authentication.\n\nSatisfies: SRG-OS-000705-GPOS-00150, SRG-OS-000105-GPOS-00052, SRG-OS-000106-GPOS-00053, SRG-OS-000107-GPOS-00054, SRG-OS-000108-GPOS-00055, SRG-OS-000375-GPOS-00160","checkContent":"Verify the \"sssd.service\" is enabled and active with the following commands: \n \n$ sudo systemctl is-enabled sssd\nenabled\n\n$ sudo systemctl is-active sssd\nactive\n\nIf \"sssd.service\" is not active or enabled, this is a finding.","fixText":"Enable the \"sssd.service to start automatically on reboot with the following command: \n \n$ sudo systemctl enable sssd.service \n \nensure the \"sssd\" service is running \n \n$ sudo systemctl start sssd.service","ccis":["CCI-004046","CCI-004047","CCI-000765","CCI-000766"]},{"vulnId":"V-270664","ruleId":"SV-270664r1068359_rule","severity":"low","ruleTitle":"Ubuntu 24.04 LTS must have the \"chrony\" 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 \"chrony\" package is installed using the following command:\n \n$ dpkg -l | grep chrony\nii  chrony     4.5-1ubuntu4.1     amd64     Versatile implementation of the Network Time Protocol\n\nIf the \"chrony\" package is not installed, this is a finding.","fixText":"Install the \"chrony\" network time protocol package using the following command:\n\n$ sudo apt install -y chrony","ccis":["CCI-000366"]},{"vulnId":"V-270665","ruleId":"SV-270665r1067133_rule","severity":"high","ruleTitle":"Ubuntu 24.04 LTS must have SSH installed.","description":"Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered.  \n \nThis requirement applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification.  \n \nProtecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa.\n\nSatisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190","checkContent":"Verify the SSH package is installed with the following command: \n \n$ dpkg -l | grep openssh \nii  openssh-client     1:9.6p1-3ubuntu13.5     amd64     secure shell (SSH) client, for secure access to remote machines\nii  openssh-server     1:9.6p1-3ubuntu13.5     amd64     secure shell (SSH) server, for secure access from remote machines\nii  openssh-sftp-server     1:9.6p1-3ubuntu13.5     amd64     secure shell (SSH) sftp server module, for SFTP access from remote machines\n \nIf the \"openssh\" server package is not installed, this is a finding.","fixText":"Install the \"ssh\" meta-package on the system with the following command: \n \n$ sudo apt install -y ssh","ccis":["CCI-002418","CCI-002420","CCI-002422"]},{"vulnId":"V-270666","ruleId":"SV-270666r1066487_rule","severity":"high","ruleTitle":"Ubuntu 24.04 LTS must use SSH to protect the confidentiality and integrity of transmitted information.","description":"Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered.  \n \nThis requirement applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification.  \n \nProtecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa.\n\nSatisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190","checkContent":"Verify the \"sshd.service\" is enabled and active with the following commands: \n \n$ sudo systemctl is-enabled ssh\nenabled\n\n$ sudo systemctl is-active ssh\nactive\n\nIf \"ssh.service\" is not active or loaded, this is a finding.","fixText":"Enable the \"ssh\" service to start automatically on reboot with the following command: \n \n$ sudo systemctl enable ssh.service \n \nensure the \"ssh\" service is running \n \n$ sudo systemctl start ssh.service","ccis":["CCI-002418","CCI-002420","CCI-002422"]},{"vulnId":"V-270667","ruleId":"SV-270667r1067107_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must configure the SSH daemon to use FIPS 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 that have common application in digital signatures, checksums, and message authentication codes.\n\nSatisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000394-GPOS-00174, SRG-OS-000424-GPOS-00188","checkContent":"Verify that the SSH daemon is configured to implement only FIPS-approved algorithms with the following command:\n\n$ sudo grep -r 'Ciphers' /etc/ssh/sshd_config*\nCiphers aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes128-ctr\n \nIf any ciphers other than \"Ciphers aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes128-ctr\" are listed, the \"Ciphers\" keyword is missing, or the returned line is commented out, or if multiple conflicting ciphers are returned, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to allow the SSH daemon to only implement FIPS-approved algorithms. \n \nAdd the following line (or modify the line to have the required value) to the \"/etc/ssh/sshd_config\" file (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor): \n \nCiphers aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes128-ctr\n \nRestart the \"sshd\" service for changes to take effect: \n \n$ sudo systemctl restart sshd","ccis":["CCI-000068","CCI-003123","CCI-002421"]},{"vulnId":"V-270668","ruleId":"SV-270668r1067110_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must configure the SSH daemon to use Message Authentication Codes (MACs) employing FIPS 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 that 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 daemon is configured to only use MACs that employ FIPS 140-3 approved ciphers with the following command:\n\n$ grep -irs macs /etc/ssh/sshd_config*\nMACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512,hmac-sha2-256\n\nIf any algorithms other than \"hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512,hmac-sha2-256\" are listed, the returned line is commented out, or if conflicting results are returned, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to allow the SSH daemon to only use MACs that employ FIPS 140-3 approved ciphers. \n \nAdd the following line (or modify the line to have the required value) to the \"/etc/ssh/sshd_config\" file (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor): \n \nMACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512,hmac-sha2-256\n \nRestart the \"sshd\" service for changes to take effect:\n\n$ sudo systemctl restart sshd","ccis":["CCI-001453","CCI-002890","CCI-002421"]},{"vulnId":"V-270669","ruleId":"SV-270669r1134804_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS SSH server must be configured to use only FIPS 140-3 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.","checkContent":"Verify that the SSH daemon is configured to use only FIPS-validated key exchange algorithms with the following command:\n\n$ sudo grep -ir kexalgorithms /etc/ssh/sshd_config*\nKexAlgorithms ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group14-sha256\n \nIf \"KexAlgorithms\" does not contain only the algorithms \"ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group14-sha256\", is commented out, or is missing, this is a finding.","fixText":"Configure the SSH daemon to use only FIPS-validated key exchange algorithms by adding or modifying the following line in \"/etc/ssh/sshd_config\":\n\nKexAlgorithms ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group14-sha256\n\nRestart the \"sshd\" service for changes to take effect:\n\n$ sudo systemctl restart sshd","ccis":["CCI-000068"]},{"vulnId":"V-270670","ruleId":"SV-270670r1067115_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must configure the SSH client to use FIPS 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 that 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.","checkContent":"Verify the SSH client is configured to use only ciphers employing FIPS 140-3 approved algorithms with the following command:\n\n$ sudo grep -r 'Ciphers' /etc/ssh/ssh_config*\nCiphers aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes128-ctr\n \nIf any ciphers other than \"Ciphers aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes128-ctr\" are listed, the \"Ciphers\" keyword is missing, or the returned line is commented out, or if multiple conflicting ciphers are returned, this is a finding.","fixText":"Configure the Ubuntu 24.04 LTS SSH client to use only ciphers employing FIPS 140-3 approved algorithms by updating the \"/etc/ssh/ssh_config\" file with the following line:\n\nCiphers aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes128-ctr\n\nRestart the \"ssh\" service for changes to take effect:\n\n$ sudo systemctl restart ssh","ccis":["CCI-001453"]},{"vulnId":"V-270671","ruleId":"SV-270671r1155244_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS SSH client must be configured to use only Message Authentication Codes (MACs) employing FIPS 140-3 validated cryptographic hash algorithms.","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 that have common application in digital signatures, checksums, and message authentication codes.","checkContent":"Verify the SSH client is configured to only use MACs employing FIPS 140-3 approved algorithms with the following command:\n\n$ sudo grep -ir macs /etc/ssh/ssh_config*\nMACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512,hmac-sha2-256\n\nIf any MACs other than \"hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512,hmac-sha2-256\" are listed, or the returned line is commented out, this is a finding.","fixText":"Configure the Ubuntu 24.04 LTS SSH client to use only MACs employing FIPS 140-3 approved algorithms by updating the \"/etc/ssh/ssh_config\" file with the following line:\n\nMACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512,hmac-sha2-256\n\nRestart the \"ssh\" service for changes to take effect:\n\n$ sudo systemctl restart ssh","ccis":["CCI-001453"]},{"vulnId":"V-270672","ruleId":"SV-270672r1067161_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must accept Personal Identity Verification (PIV) credentials.","description":"The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. \n \nDOD has mandated the use of the common access card (CAC) to support identity management and personal authentication for systems covered under Homeland Security Presidential Directive (HSPD) 12, as well as making the CAC a primary component of layered protection for national security systems.","checkContent":"Verify the \"opensc-pcks11\" package is installed on the system with the following command: \n \n$ dpkg -l | grep opensc-pkcs11 \nii  opensc-pkcs11:amd64        0.25.0~rc1-1build2    amd64        Smart card utilities with support for PKCS#15 compatible cards \n \nIf the \"opensc-pcks11\" package is not installed, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to accept PIV credentials. \n \nInstall the \"opensc-pkcs11\" package using the following command: \n \n$ sudo apt install -y opensc-pkcs11","ccis":["CCI-001953"]},{"vulnId":"V-270673","ruleId":"SV-270673r1067164_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must accept Personal Identity Verification (PIV) credentials managed through the Privileged Access Management (PAM)  framework.","description":"The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. \n \nDOD has mandated the use of the common access card (CAC) to support identity management and personal authentication for systems covered under Homeland Security Presidential Directive (HSPD) 12, as well as making the CAC a primary component of layered protection for national security systems.","checkContent":"Verify the \"libpam-pcks11\" package is installed on the system with the following command: \n \n$ dpkg -l | grep libpam-pkcs11 \nii  libpam-pkcs11     0.6.12-2build3     amd64     Fully featured PAM module for using PKCS#11 smart cards\n \nIf the \"libpam-pcks11\" package is not installed, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to accept PIV credentials that are managed through the PAM framework. \n \nInstall the \"libpam-pkcs11\" package using the following command: \n \n$ sudo apt install -y libpam-pkcs11","ccis":["CCI-001953"]},{"vulnId":"V-270674","ruleId":"SV-270674r1067167_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTSs 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-000031-GPOS-00012, SRG-OS-000030-GPOS-00011","checkContent":"Verify Ubuntu 24.04 LTS has the \"vlock\" package installed with the following command: \n \n$ dpkg -l | grep vlock \nii  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 (if it is not already installed) by running the following command: \n \n$ sudo apt install -y vlock","ccis":["CCI-000060","CCI-000057"]},{"vulnId":"V-270675","ruleId":"SV-270675r1137691_rule","severity":"high","ruleTitle":"Ubuntu 24.04 LTS when booted 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 24.04 LTS requires a password for authentication upon booting into single-user and maintenance modes with the following command: \n \n$ sudo grep -i password /boot/grub/grub.cfg \npassword_pbkdf2 root grub.pbkdf2.sha512.10000.MFU48934NJA87HF8NSD34493GDHF84NG \n \nIf the root password entry does not begin with \"password_pbkdf2\", this is a finding.","fixText":"Configure the system to require a password for authentication upon booting into single-user and maintenance modes. \n \nGenerate an encrypted (grub) password for root with the following command: \n \n$ grub-mkpasswd-pbkdf2 \nEnter Password: \nReenter Password: \nPBKDF2 hash of your password is grub.pbkdf2.sha512.10000.MFU48934NJD84NF8NSD39993JDHF84NG \n \nUsing the hash from the output, modify the \"/etc/grub.d/40_custom\" file with the following command to add a boot password: \n \n$ sudo sed -i '$i set superusers=\\\"root\\\"\\npassword_pbkdf2 root <hash>' /etc/grub.d/40_custom \n \nwhere <hash> 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-270676","ruleId":"SV-270676r1155245_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must initiate session audits at system startup.","description":"If auditing is enabled late in the startup process, the actions of some startup processes may not be audited. Some audit systems also maintain state information only available if auditing is enabled before a given process is created.","checkContent":"Verify Ubuntu 24.04 LTS enables auditing at system startup in GRUB. \n\nCheck the main GRUB defaults to ensure that auditing is enabled:\n$ sudo grep -ir GRUB_CMDLINE_LINUX /etc/default/grub\n/etc/default/grub:GRUB_CMDLINE_LINUX_DEFAULT=\"audit=1\"\n/etc/default/grub:GRUB_CMDLINE_LINUX=\"audit=1\"\n \nIf any linux lines do not contain \"audit=1\", this is a finding.\n\nCheck the generated GRUB configuration to ensure that the setting is propagated to the bootloader:\n$ sudo grep \"^\\s*linux\" /boot/grub/grub.cfg \nlinux   /vmlinuz-6.8.0-31-generic root=UUID=c92a542f-aee4-4af9-94b2-203624ccb8e3 ro audit=1 quiet splash $vt_handoff\nlinux   /vmlinuz-6.8.0-31-generic root=UUID=c92a542f-aee4-4af9-94b2-203624ccb8e3 ro recovery nomodeset dis_ucode_ldr audit=1\n \nIf any linux lines do not contain \"audit=1\", this is a finding.\n\nNote: Output details may vary by system.","fixText":"Configure Ubuntu 24.04 LTS to produce audit records at system startup.  \n \nEdit the \"/etc/default/grub\" file and add \"audit=1\" to the \"GRUB_CMDLINE_LINUX\" option and to the \"GRUB_CMDLINE_LINUX_DEFAULT\" option. \n\nGRUB_CMDLINE_LINUX_DEFAULT=\"audit=1\"\nGRUB_CMDLINE_LINUX=\"audit=1\"\n \nTo update the grub config file, run: \n \n$ sudo update-grub","ccis":["CCI-001464"]},{"vulnId":"V-270677","ruleId":"SV-270677r1101774_rule","severity":"low","ruleTitle":"Ubuntu 24.04 LTS must limit the number of concurrent sessions to 10 for all accounts and/or account types.","description":"Ubuntu 24.04 LTS management includes the ability to control the number of users and user sessions that utilize an operating system. Limiting the number of allowed users and sessions per user is helpful in reducing the risks related to denial-of-service (DoS) attacks. \n \nThis requirement addresses concurrent sessions for information system accounts and does not address concurrent sessions by single users via multiple system accounts. The maximum number of concurrent sessions must be defined based upon mission needs and the operational environment for each system.","checkContent":"Verify Ubuntu 24.04 LTS limits the number of concurrent sessions to 10 for all accounts and/or account types with the following command: \n \n$ grep -r maxlogins /etc/security/limits.conf /etc/security/limits.d/*.conf\n/etc/security/limits.d/maxlogins.conf:* hard maxlogins 10\n \nIf the \"maxlogins\" item does not have a value of \"10\" or less, is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to limit the number of concurrent sessions to 10 for all accounts and/or account types. \n \nAdd the following line to the top of the /etc/security/limits.conf or in a \".conf\" file defined in /etc/security/limits.d/: \n \n* hard maxlogins 10","ccis":["CCI-000054"]},{"vulnId":"V-270678","ruleId":"SV-270678r1101791_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must initiate a graphical session lock after 10 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 24.04 LTS must remain in place until the user reauthenticates. No other activity aside from reauthentication must unlock the system.","checkContent":"Note: If Ubuntu 24.04 LTS does not have a graphical user interface installed, this requirement is not applicable. \n\nVerify the Ubuntu operation system has a graphical user interface session lock configured to activate after 10 minutes of inactivity with the following commands:  \n \nSet the following settings to verify the graphical user interface session is configured to lock the graphical user session after 10 minutes of inactivity: \n  \n**$ gsettings get org.gnome.desktop.screensaver lock-enabled\ntrue\n\n$ gsettings get org.gnome.desktop.screensaver lock-delay\nuint32 0\n\n$ gsettings get org.gnome.desktop.session idle-delay\nuint32 600\n\nNote: If \"lock-enabled\" is not set to \"true\", 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 \"600\", or either settings are missing, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to lock the current graphical user interface session after 10 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/session]\nidle-delay=uint32 900\n\n[org/gnome/desktop/screensaver]\nlock-enabled=true\nlock-delay=uint32 600\n\nUpdate the dconf settings:\n\n$ sudo dconf update","ccis":["CCI-000057"]},{"vulnId":"V-270679","ruleId":"SV-270679r1107295_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must prevent a user from overriding the disabling of the graphical user interface automount function.","description":"A nonprivileged account is any operating system account with authorizations of a nonprivileged user.\n\nSatisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163, SRG-OS-000480-GPOS-00227","checkContent":"Note: This requirement assumes the use of the Ubuntu 24.04 LTS default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable.\n\nVerify Ubuntu 24.04 LTS disables the ability of the user to override the graphical user interface automount setting.\n\nDetermine which profile the system database is using with the following command:\n\n$ sudo grep system-db /etc/dconf/profile/user\n\nsystem-db:local\n\nCheck that the automount setting is locked from nonprivileged user modification with the following command:\n\nNote: The example below is using the database \"local\" for the system, so the path is \"/etc/dconf/db/local.d\". This path must be modified if a database other than \"local\" is being used.\n\n$ grep 'automount-open' /etc/dconf/db/local.d/locks/* \n\n/org/gnome/desktop/media-handling/automount-open\n\nIf the command does not return at least the example result, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS so the GNOME desktop does not allow a user to change the setting that disables automated mounting of removable media.\n\nAdd the following line to \"/etc/dconf/db/local.d/locks/00-security-settings-lock\" to prevent user modification:\n\n/org/gnome/desktop/media-handling/automount-open\n\nUpdate the dconf system databases:\n\n$ sudo dconf update","ccis":["CCI-000056"]},{"vulnId":"V-270680","ruleId":"SV-270680r1066529_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must automatically terminate a user session after inactivity timeouts have expired.","description":"Automatic session termination addresses the termination of user-initiated logical sessions in contrast to the termination of network connections associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. \n \nSession termination terminates all processes associated with a user's logical session except those processes specifically created by the user (i.e., session owner) to continue after the session is terminated. \n \nConditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on information system use. \n \nThis capability is typically reserved for specific operating system functionality where the system owner, data owner, or organization requires additional assurance.","checkContent":"Verify Ubuntu 24.04 LTS automatically terminates a user session after inactivity timeouts have expired with 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=600 \n\nIf \"TMOUT\" is not set, or if the value is \"0\" or is commented out, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to automatically terminate a user session after inactivity timeouts have expired or at shutdown. \n \nCreate the file \"/etc/profile.d/99-terminal_tmout.sh\" file if it does not exist. \n \nModify or append the following line in the \"/etc/profile.d/99-terminal_tmout.sh \" file: \n \nTMOUT=600 \n \nThis will set a timeout value of 10 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=600","ccis":["CCI-002361"]},{"vulnId":"V-270681","ruleId":"SV-270681r1134806_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS monitors all remote access methods with the following command: \n \n$  grep -E -r '^(auth,authpriv\\.\\*|daemon\\.\\*)' /etc/rsyslog.* \n/etc/rsyslog.d/50-default.conf:auth,authpriv.* /var/log/auth.log\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 24.04 LTS to monitor all remote access methods by adding the following lines to the \"/etc/rsyslog.d/50-default.conf\" file: \n \nauth.*,authpriv.* /var/log/secure \ndaemon.* /var/log/messages \n \nFor the changes to take effect, restart the \"rsyslog\" service with the following command: \n \n$ sudo systemctl restart rsyslog.service","ccis":["CCI-000067"]},{"vulnId":"V-270682","ruleId":"SV-270682r1066535_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must automatically remove or disable emergency accounts after 72 hours.","description":"Temporary accounts are privileged or nonprivileged accounts established during pressing circumstances, such as new software or hardware configuration or an incident response, where the need for prompt account activation requires bypassing normal account authorization procedures. If any inactive temporary accounts are left enabled on the system and are not either manually removed or automatically expired within 72 hours, the security posture of the system will be degraded and exposed to exploitation by unauthorized users or insider threat actors.\n\nTemporary accounts are different from emergency accounts. Emergency accounts, also known as \"last resort\" or \"break glass\" accounts, are local logon accounts enabled on the system for emergency use by authorized system administrators to manage a system when standard logon methods are failing or not available. Emergency accounts are not subject to manual removal or scheduled expiration requirements.\n\nThe automatic expiration of temporary accounts may be extended as needed by the circumstances but it must not be extended indefinitely. A documented permanent account must be established for privileged users who need long-term maintenance accounts.\n\nSatisfies: SRG-OS-000002-GPOS-00002, SRG-OS-000123-GPOS-00064","checkContent":"Verify temporary accounts have been provisioned with an expiration date of 72 hours with the following command:\n\n$ sudo chage -l <temporary_account_name> | grep -i \"account expires\"\n\nVerify each of these accounts has an expiration date set within 72 hours.\n\nIf any temporary accounts have no expiration date set or do not expire within 72 hours, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to expire temporary accounts after 72 hours with the following command:\n\n$ sudo chage -E $(date -d +3days +%Y-%m-%d) <temporary_account_name>","ccis":["CCI-000016","CCI-001682"]},{"vulnId":"V-270683","ruleId":"SV-270683r1066538_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must disable account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity.","description":"Inactive identifiers pose a risk to systems and applications because attackers may exploit an inactive identifier and potentially obtain undetected access to the system. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained. \n \nOperating systems need to track periods of inactivity and disable application identifiers after 35 days of inactivity.\n\nSatisfies: SRG-OS-000118-GPOS-00060, SRG-OS-000590-GPOS-00110","checkContent":"Verify the account identifiers (individuals, groups, roles, and devices) are disabled after 35 days of inactivity with the following command: \n \nCheck the account inactivity value by performing the following command: \n \n$ grep INACTIVE /etc/default/useradd\nINACTIVE=35 \n \nIf \"INACTIVE\" is not set to a value 0<[VALUE]<=35, is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to disable account identifiers after 35 days of inactivity after the password expiration.  \n \nRun the following command to change the configuration for adduser: \n \n$ sudo useradd -D -f 35 \n \nNote: DOD recommendation is 35 days, but a lower value is acceptable. The value \"0\" will disable the account immediately after the password expires.","ccis":["CCI-003627","CCI-003628"]},{"vulnId":"V-270684","ruleId":"SV-270684r1066541_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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","checkContent":"Verify Ubuntu 24.04 LTS generates audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/passwd\" with 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\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.","fixText":"Configure Ubuntu 24.04 LTS to generate audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/passwd\". \n \nAdd or update the following rule 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","ccis":["CCI-000018","CCI-001403","CCI-001404","CCI-001405","CCI-002130","CCI-000172"]},{"vulnId":"V-270685","ruleId":"SV-270685r1066544_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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","checkContent":"Verify Ubuntu 24.04 LTS generates audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/group\" with 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\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.","fixText":"Configure Ubuntu 24.04 LTS to generate audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/group\". \n \nAdd or update the following rule 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","ccis":["CCI-000018","CCI-001403","CCI-001404","CCI-001405","CCI-002130","CCI-000172"]},{"vulnId":"V-270686","ruleId":"SV-270686r1066547_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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","checkContent":"Verify Ubuntu 24.04 LTS generates audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/shadow\" with 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\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.","fixText":"Configure Ubuntu 24.04 LTS to generate audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/shadow\". \n \nAdd or update the following rule 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","ccis":["CCI-000018","CCI-001403","CCI-001404","CCI-001405","CCI-002130","CCI-000172"]},{"vulnId":"V-270687","ruleId":"SV-270687r1066550_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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","checkContent":"Verify Ubuntu 24.04 LTS generates audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/gshadow\" with 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\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.","fixText":"Configure Ubuntu 24.04 LTS to generate audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/gshadow\". \n \nAdd or update the following rule 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","ccis":["CCI-000018","CCI-001403","CCI-001404","CCI-001405","CCI-002130","CCI-000172"]},{"vulnId":"V-270688","ruleId":"SV-270688r1066553_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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","checkContent":"Verify Ubuntu 24.04 LTS generates audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/security/opasswd\" with 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\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.","fixText":"Configure Ubuntu 24.04 LTS to generate audit records for all account creations, modifications, disabling, and termination events that affect \"/etc/security/opasswd\". \n \nAdd or update the following rule 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","ccis":["CCI-000018","CCI-001403","CCI-001404","CCI-001405","CCI-002130","CCI-000172"]},{"vulnId":"V-270689","ruleId":"SV-270689r1066556_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS audits the execution of privilege functions by auditing the \"execve\" system call with 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 \nNotes: \n- For 32-bit architectures, only the 32-bit specific output lines from the commands are required. \n- The \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.","fixText":"Configure Ubuntu 24.04 LTS to audit the execution of all privileged functions. \n \nAdd or update the following rules 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 -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 \nNotes: For 32-bit architectures, only the 32-bit specific entries are required. \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-002233","CCI-002234","CCI-004188"]},{"vulnId":"V-270690","ruleId":"SV-270690r1067126_rule","severity":"low","ruleTitle":"Ubuntu 24.04 LTS must automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts have been made.","description":"By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced. Limits are imposed by locking the account.\n\nSatisfies: SRG-OS-000021-GPOS-00005, SRG-OS-000329-GPOS-00128","checkContent":"Verify that Ubuntu 24.04 LTS utilizes the \"pam_faillock\" module with the following command:\n\n$ grep faillock /etc/pam.d/common-auth \nauth     [default=die]  pam_faillock.so authfail\nauth     sufficient     pam_faillock.so authsucc\n\nIf the pam_faillock.so module is not present in the \"/etc/pam.d/common-auth\" file, this is a finding.\n\nVerify the pam_faillock module is configured to use the following options:\n\n$ sudo egrep 'silent|audit|deny|fail_interval| unlock_time' /etc/security/faillock.conf\naudit\nsilent\ndeny = 3\nfail_interval = 900\nunlock_time = 0\n\nIf the \"silent\" keyword is missing or commented out, this is a finding.\nIf the \"audit\" keyword is missing or commented out, this is a finding.\nIf the \"deny\" keyword is missing, commented out, or set to a value greater than \"3\", this is a finding.\nIf the \"fail_interval\" keyword is missing, commented out, or set to a value greater than \"900\", this is a finding.\nIf the \"unlock_time\" keyword is missing, commented out, or not set to \"0\", this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to utilize the \"pam_faillock\" module. \n\nEdit the /etc/pam.d/common-auth file to add the following lines below the \"auth\" definition for pam_unix.so:\nauth     [default=die]  pam_faillock.so authfail\nauth     sufficient     pam_faillock.so authsucc\n\nConfigure the \"pam_faillock\" module to use the following options:\n\nEdit the /etc/security/faillock.conf file and add/update the following keywords and values:\naudit\nsilent\ndeny = 3\nfail_interval = 900\nunlock_time = 0","ccis":["CCI-000044","CCI-002238"]},{"vulnId":"V-270691","ruleId":"SV-270691r1066562_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must display the Standard Mandatory DOD Notice and Consent Banner before granting access to via an SSH logon.","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. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: \n \n\"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. \n \nBy 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 \n-At any time, the USG may inspect and seize data stored on this IS. \n \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 \n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. \n \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 \nUse the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: \n \n\"I've read (literal ampersand) consent to terms in IS user agreem't.\"\n\nSatisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000228-GPOS-00088","checkContent":"Verify Ubuntu 24.04 LTS displays the Standard Mandatory DOD Notice and Consent Banner before granting access via an SSH logon with the following command: \n \n$ sudo grep -ir banner /etc/ssh/sshd_config* \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 provided for USG-authorized use only. \n \nBy 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 \n-At any time, the USG may inspect and seize data stored on this IS. \n \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 \n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. \n \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 \nIf the banner text does not match the Standard Mandatory DOD Notice and Consent Banner exactly, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to display the Standard Mandatory DOD Notice and Consent Banner before granting access via an SSH logon.\n\nSet 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 \nEither create the file containing the banner or replace the text in the file with the Standard Mandatory DOD Notice and Consent Banner. The DOD required text is: \n \n\"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. \n \nBy 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 \n-At any time, the USG may inspect and seize data stored on this IS. \n \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 \n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. \n \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-000048","CCI-001384","CCI-001385","CCI-001386","CCI-001387","CCI-001388"]},{"vulnId":"V-270692","ruleId":"SV-270692r1066565_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must enable the graphical user logon banner to display the Standard Mandatory DOD Notice and Consent Banner before granting local access to the system via a graphical user logon.","description":"Display of a standardized and approved use notification before granting access to Ubuntu 24.04 LTS 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. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: \n \n\"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. \n \nBy 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 \n-At any time, the USG may inspect and seize data stored on this IS. \n \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 \n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. \n \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 \nUse the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: \n \n\"I've read (literal ampersand) consent to terms in IS user agreem't.\"","checkContent":"Note: If the system does not have a graphical user interface installed, this requirement is not applicable. \n\nVerify Ubuntu 24.04 LTS is configured to display the Standard Mandatory DOD Notice and Consent Banner before granting access to Ubuntu 24.04 LTS via a graphical user logon with the following command: \n \n$ grep ^banner-message-enable /etc/gdm3/greeter.dconf-defaults\nbanner-message-enable=true\n \nIf the value for \"banner-message-enable\" is set to \"false\", the line is commented out, or no value is returned, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to display the Standard Mandatory DOD Notice and Consent Banner before granting access to Ubuntu 24.04 LTS via a graphical user logon.\n\nEdit the \"/etc/gdm3/greeter.dconf-defaults\" file. \n \nLook for the \"banner-message-enable\" parameter under the \"[org/gnome/login-screen]\" section and uncomment it (remove the leading \"#\" characters): \n[org/gnome/login-screen] \nbanner-message-enable=true \n \nUpdate the GDM with the new configuration: \n \n$ sudo dconf update \n$ sudo systemctl restart gdm3","ccis":["CCI-000048"]},{"vulnId":"V-270693","ruleId":"SV-270693r1066568_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must display the Standard Mandatory DOD Notice and Consent Banner before granting local access to the system via a graphical user logon.","description":"Display of a standardized and approved use notification before granting access to Ubuntu 24.04 LTS 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. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: \n \n\"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. \n \nBy 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 \n-At any time, the USG may inspect and seize data stored on this IS. \n \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 \n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. \n \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 \nUse the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: \n \n\"I've read (literal ampersand) consent to terms in IS user agreem't.\"","checkContent":"Note: If the system does not have a graphical user interface installed, this requirement is not applicable. \n\nVerify Ubuntu 24.04 LTS displays the Standard Mandatory DOD Notice and Consent Banner before granting access to Ubuntu 24.04 LTS via a graphical user logon with the command: \n \n$ grep ^banner-message-text /etc/gdm3/greeter.dconf-defaults \nbanner-message-text=\"You are accessing a U.S. Government \\(USG\\) Information System \\(IS\\) that is provided for USG-authorized use only.\\s+By using this IS \\(which includes any device attached to this IS\\), you consent to the following conditions:\\s+-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.\\s+-At any time, the USG may inspect and seize data stored on this IS.\\s+-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.\\s+-This IS includes security measures \\(e.g., authentication and access controls\\) to protect USG interests--not for your personal benefit or privacy.\\s+-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 \nIf the banner-message-text is missing, commented out, or does not match the Standard Mandatory DOD Notice and Consent Banner exactly, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS displays the Standard Mandatory DOD Notice and Consent Banner before granting access to Ubuntu 24.04 LTS via a graphical user logon.\n\nEdit the \"/etc/gdm3/greeter.dconf-defaults\" file. \n \nSet the \"banner-message-text\" line to contain the appropriate banner message text as shown below: \n \nbanner-message-text='You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\\n\\nBy 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\\n-At any time, the USG may inspect and seize data stored on this IS.\\n\\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\\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\\n\\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 \nUpdate the GDM with the new configuration: \n \n$ sudo dconf update \n$ sudo systemctl restart gdm3","ccis":["CCI-000048"]},{"vulnId":"V-270694","ruleId":"SV-270694r1066571_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must be configured to enforce the acknowledgement of the Standard Mandatory DOD Notice and Consent Banner for all SSH connections.","description":"The banner must be acknowledged by the user prior to allowing the user access to Ubuntu 24.04 LTS. This provides assurance that the user has seen the message and accepted the conditions for access. If the consent banner is not acknowledged by the user, DOD will not be in compliance with system use notifications required by law. \n \nUbuntu 24.04 LTS must prevent further activity until the user executes a positive action to manifest agreement.","checkContent":"Verify Ubuntu 24.04 LTS is configured to prompt a user to acknowledge the Standard Mandatory DOD Notice and Consent Banner before granting access with the following command:\n\n$ less /etc/profile.d/ssh_confirm.sh\n#!/bin/bash\n\nif [ -n \"$SSH_CLIENT\" ] || [ -n \"$SSH_TTY\" ]; then\n        while true; do\n                read -p \" \n\n\nYou are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\n\nBy 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\n-At any time, the USG may inspect and seize data stored on this IS.\n\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\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n\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\nDo you agree? [y/N] \" yn\n                case $yn in\n                        [Yy]* ) break ;;\n                        [Nn]* ) exit 1 ;;\n                esac\n        done\nfi\n\nIf the output does not match the text above, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to prompt a user to acknowledge the Standard Mandatory DOD Notice and Consent Banner before granting access:\n\n$ sudo vi /etc/profile.d/ssh_confirm.sh\n#!/bin/bash\n\nif [ -n \"$SSH_CLIENT\" ] || [ -n \"$SSH_TTY\" ]; then\n        while true; do\n                read -p \" \n\nYou are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\n\nBy 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\n-At any time, the USG may inspect and seize data stored on this IS.\n\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\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n\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\nDo you agree? [y/N] \" yn\n                case $yn in\n                        [Yy]* ) break ;;\n                        [Nn]* ) exit 1 ;;\n                esac\n        done\nfi\n\nNote: The \"ssh_confirm.sh\" script is provided as a supplemental file to this document.","ccis":["CCI-000050"]},{"vulnId":"V-270695","ruleId":"SV-270695r1066574_rule","severity":"low","ruleTitle":"Ubuntu 24.04 LTS Advance Package Tool (APT) must be configured to prevent the installation of patches, service packs, device drivers, or Ubuntu 24.04 LTS components without verification they have been digitally signed using a certificate that is recognized and approved by the organization.","description":"Changes to any software components can have significant effects on the overall security of Ubuntu 24.04 LTS. 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. Ubuntu 24.04 LTS will 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 CA.","checkContent":"Verify that APT is configured to prevent the installation of patches, service packs, device drivers, or Ubuntu 24.04 LTS components without verification they have been digitally signed using a certificate recognized and approved by the organization with the following command: \n \n$ grep AllowUnauthenticated /etc/apt/apt.conf.d/* \n \nIf any files are returned from the command with \"AllowUnauthenticated\" are set to \"true\", this is a finding.","fixText":"Configure APT to prevent the installation of patches, service packs, device drivers, or Ubuntu 24.04 LTS components without verification they have been digitally signed using a certificate recognized and approved by the organization. \n \nRemove/update any APT configuration files that contain the variable \"AllowUnauthenticated\" to \"false\" or remove \"AllowUnauthenticated\" entirely from each file. Below is an example of setting the \"AllowUnauthenticated\" variable to \"false\": \n \nAPT::Get::AllowUnauthenticated \"false\";","ccis":["CCI-003992"]},{"vulnId":"V-270696","ruleId":"SV-270696r1107306_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS library files must have mode 0755 or less permissive.","description":"If Ubuntu 24.04 LTS 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\", \"/usr/lib\", and \"/usr/lib64\" have mode 0755 or less permissive.\n\nCheck that the systemwide shared library files have mode 0755 or less permissive with the following command:\n\n$ sudo find /lib /lib64 /usr/lib /usr/lib64 -type f -name '*.so*' -perm /022 -exec stat -c \"%n %a\" {} +\n\nIf any output is returned, this is a finding.","fixText":"Configure the systemwide shared library files contained in the directories \"/lib\", \"/lib64\", \"/usr/lib\", and \"/usr/lib64\" to have mode 0755 or less permissive with the following command:\n\n$ sudo find /lib /lib64 /usr/lib /usr/lib64 -type f -name '*.so*' -perm /022 -exec chmod go-w {} +","ccis":["CCI-001499"]},{"vulnId":"V-270697","ruleId":"SV-270697r1107308_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS library files must be owned by root.","description":"If Ubuntu 24.04 LTS 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\", \"/usr/lib\", and \"/usr/lib64\" are owned by root with the following command:\n\n$ sudo find /lib /lib64 /usr/lib /usr/lib64 -type f -name '*.so*' ! -user root -exec stat -c \"%n %U\" {} +\n\nIf any output is returned, this is a finding.","fixText":"Configure the systemwide shared library files contained in the directories \"/lib\", \"/lib64\", \"/usr/lib\", and \"/usr/lib64\" to be owned by root with the following command:\n\n$ sudo find /lib /lib64 /usr/lib /usr/lib64 -type f -name '*.so*' ! -user root -exec chown root {} +","ccis":["CCI-001499"]},{"vulnId":"V-270698","ruleId":"SV-270698r1101751_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS library directories must be owned by root.","description":"If Ubuntu 24.04 LTS 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\", \"/usr/lib\", and \"/usr/lib64\" are owned by root with the following command: \n \n$ sudo find /lib /lib64 /usr/lib /usr/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 /lib64 /usr/lib /usr/lib64 ! -user root -type d -exec chown root '{}' \\;","ccis":["CCI-001499"]},{"vulnId":"V-270699","ruleId":"SV-270699r1107310_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS library files must be group-owned by root or a system account.","description":"If Ubuntu 24.04 LTS 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\", \"/usr/lib\", and \"/usr/lib64\" are group owned by root with the following command:\n\n$ sudo find /lib /lib64 /usr/lib /usr/lib64 -type f -name '*.so*' ! -group root -exec stat -c \"%n %G\" {} +\n\nIf any output is returned, this is a finding.","fixText":"Configure the systemwide shared library files contained in the directories \"/lib\", \"/lib64\", \"/usr/lib\", and \"/usr/lib64\" to be group owned by root with the following command:\n\n$ sudo find /lib /lib64 /usr/lib /usr/lib64 -type f -name '*.so*' ! -group root -exec chown :root {} +","ccis":["CCI-001499"]},{"vulnId":"V-270700","ruleId":"SV-270700r1066589_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS library directories must be group-owned by root.","description":"If Ubuntu 24.04 LTS 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 with 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 the system 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-270701","ruleId":"SV-270701r1066592_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must have system commands set to a mode of 0755 or less permissive.","description":"If Ubuntu 24.04 LTS 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 24.04 LTS 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 0755 or less permissive with 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 the system 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-270702","ruleId":"SV-270702r1066595_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must have system commands owned by root or a system account.","description":"If Ubuntu 24.04 LTS 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 24.04 LTS 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, with 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 not owned by a required system account, this is a finding.","fixText":"Configure the system commands and their respective parent directories to be protected from unauthorized access. Run the following command, replacing \"[FILE]\" with any system command file not owned by \"root\" or a required system account: \n \n$ sudo chown root [FILE]","ccis":["CCI-001499"]},{"vulnId":"V-270703","ruleId":"SV-270703r1066598_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must have system commands group-owned by root or a system account.","description":"If Ubuntu 24.04 LTS 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 24.04 LTS 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 with the following command: \n \n$ find /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin \\-type f -perm -u=x -exec stat --format=\"%n %G\" {} + |  \\awk '$2 != \"root\" && $2 != \"daemon\" && $2 != \"adm\" && $2 != \"shadow\" && $2 != \"mail\" && $2 != \"crontab\" && $2 != \"_ssh\"'\n\nNote: The above command uses awk to filter out common system accounts. If your system uses other required system accounts, add them to the awk condition to filter them out of the results.\n\nIf any system commands are returned that are not group-owned by a required system account, this is a finding.","fixText":"Configure the system commands to be protected from unauthorized access. Run the following command, replacing \"[FILE]\" with any system command file not group-owned by \"root\" or a required system account: \n \n$ sudo chgrp [SYSTEMACCOUNT] [FILE]","ccis":["CCI-001499"]},{"vulnId":"V-270704","ruleId":"SV-270704r1066601_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must prevent the use of dictionary words for passwords.","description":"Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords or passphrases are preferable over shorter passwords. Enforced composition rules provide marginal security benefits while decreasing usability. However, organizations may choose to establish certain rules for password generation (e.g., minimum character length for long passwords) under certain circumstances and can enforce this requirement in IA-5(1)(h). Account recovery can occur, for example, in situations when a password is forgotten. Cryptographically protected passwords include salted one-way cryptographic hashes of passwords. The list of commonly used, compromised, or expected passwords includes passwords obtained from previous breach corpuses, dictionary words, and repetitive or sequential characters. The list includes context-specific words, such as the name of the service, username, and derivatives thereof.","checkContent":"Verify Ubuntu 24.04 LTS uses the \"cracklib\" library to prevent the use of dictionary words with the following command: \n \n$ grep dictcheck /etc/security/pwquality.conf\ndictcheck=1 \n \nIf the \"dictcheck\" parameter is not set to \"1\" or is commented out, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to prevent the use of dictionary words for passwords. \n \nAdd or update the following line in the \"/etc/security/pwquality.conf\" file to include the \"dictcheck=1\" parameter: \n \ndictcheck=1","ccis":["CCI-004061"]},{"vulnId":"V-270705","ruleId":"SV-270705r1066604_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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.","checkContent":"Verify that Ubuntu 24.04 LTS uses \"pwquality\" to enforce the password complexity rules.  \n \nVerify the pwquality module is being enforced by Ubuntu 24.04 LTS with the following command: \n \n$ grep -i enforcing /etc/security/pwquality.conf\nenforcing = 1 \n \nIf the value of \"enforcing\" is not \"1\", or the line is commented out, this is a finding. \n \nCheck for the use of \"pwquality\" with the following command: \n \n$ cat /etc/pam.d/common-password | grep requisite | grep pam_pwquality\npassword requisite pam_pwquality.so retry=3 \n \nIf the value of \"retry\" is set to \"0\" or is greater than \"3\", or if a line is not returned, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to use \"pwquality\" to enforce password complexity rules. \n \nAdd the following line to \"/etc/security/pwquality.conf\" (or modify the line to have the required value): \n \nenforcing = 1 \n \nAdd the following line to \"/etc/pam.d/common-password\" (or modify the line to have the required value): \n \npassword requisite pam_pwquality.so retry=3 \n \nNote: Ensure the value of \"retry\" is between \"1\" and \"3\".","ccis":["CCI-000366"]},{"vulnId":"V-270706","ruleId":"SV-270706r1068361_rule","severity":"low","ruleTitle":"Ubuntu 24.04 LTS 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.\n\nThe delay option is set in microseconds.","checkContent":"Verify Ubuntu 24.04 LTS enforces a delay of at least four seconds between logon prompts following a failed logon attempt with the following command: \n \n$ grep pam_faildelay /etc/pam.d/common-auth\nauth    required    pam_faildelay.so    delay=4000000\n \nIf the value for \"delay\" is not set to \"4000000\" or greater, the line is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to enforce a delay of at least four seconds between logon prompts following a failed logon attempt. \n \nEdit the file \"/etc/pam.d/common-auth\" and set the parameter \"pam_faildelay\" to a value of \"4000000\" or greater: \n \nauth    required    pam_faildelay.so    delay=4000000","ccis":["CCI-000366"]},{"vulnId":"V-270707","ruleId":"SV-270707r1101786_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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.","checkContent":"Verify the \"/etc/sudoers\" file has no occurrences of \"!authenticate\" with the following command: \n \n$ sudo egrep -iR '!authenticate' /etc/sudoers /etc/sudoers.d/\n \nIf any occurrences of \"!authenticate\" return from the command, this is a finding.","fixText":"Remove any occurrence of \"!authenticate\" found in \"/etc/sudoers\" file or files in the \"/etc/sudoers.d\" directory.","ccis":["CCI-000366"]},{"vulnId":"V-270708","ruleId":"SV-270708r1066613_rule","severity":"high","ruleTitle":"Ubuntu 24.04 LTS 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. A system administrator (SA) must protect clients that may expose 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 may then be able to 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 must be disabled or restricted as appropriate to the system's needs.","checkContent":"Verify that X11Forwarding is disabled with the following command: \n \n$ sudo grep -ir x11forwarding /etc/ssh/sshd_config* | grep -v \"^#\"\nX11Forwarding no \n \nIf the \"X11Forwarding\" keyword is set to \"yes\" and is not documented with the information system security officer (ISSO) as an operational requirement, is missing, or multiple conflicting results are returned, this is a finding.","fixText":"Edit the \"/etc/ssh/sshd_config\" file to uncomment or add the line for the \"X11Forwarding\" keyword and set its value to \"no\" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor): \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-270709","ruleId":"SV-270709r1066616_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 daemon prevents remote hosts from connecting to the proxy display with the following command:\n\n$ sudo grep -ir x11uselocalhost /etc/ssh/sshd_config*\nX11UseLocalhost yes\n\nIf the \"X11UseLocalhost\" keyword is set to \"no\", is commented out, is missing, or multiple conflicting results are returned, this is a finding.","fixText":"Configure the SSH daemon to prevent remote hosts from connecting to the proxy display. \n \nEdit the \"/etc/ssh/sshd_config\" file to uncomment or add the line for the \"X11UseLocalhost\" keyword and set its value to \"yes\" (this file may be named differently or be in a different location if using a version of SSH that is provided by a third-party vendor): \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-270711","ruleId":"SV-270711r1184069_rule","severity":"high","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS is not configured to reboot the system when Ctrl-Alt-Delete is pressed when using a graphical user interface with the following command:\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 24.04 LTS 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-mediakeys with the following contents:\n\n[org/gnome/settings-daemon/plugins/media-keys]\nlogout=@as []\n\nUpdate the dconf settings:\n\n$ sudo dconf update","ccis":["CCI-000366"]},{"vulnId":"V-270712","ruleId":"SV-270712r1068363_rule","severity":"high","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS is not configured to reboot the system when Ctrl-Alt-Delete is pressed with the following command:\n\n$ systemctl status ctrl-alt-del.target\no   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 the system to disable the Ctrl-Alt-Delete sequence for the command line with the following commands:\n\n$ sudo systemctl disable ctrl-alt-del.target\n[...]\n\n$ sudo systemctl mask ctrl-alt-del.target\nCreated symlink /etc/systemd/system/ctrl-alt-del.target ? /dev/null.\n\nReload the daemon to take effect: \n\n$ sudo systemctl daemon-reload","ccis":["CCI-000366"]},{"vulnId":"V-270713","ruleId":"SV-270713r1066628_rule","severity":"high","ruleTitle":"Ubuntu 24.04 LTS 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":"Check the \"/etc/shadow\" file for blank passwords with 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 with the following commands:\n\nPerform a password reset:\n$ sudo passwd [username]\n\nLock an account:\n$ sudo passwd -l [username]","ccis":["CCI-000366"]},{"vulnId":"V-270714","ruleId":"SV-270714r1134808_rule","severity":"high","ruleTitle":"Ubuntu 24.04 LTS must not allow accounts configured in Pluggable Authentication Modules (PAM) 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":"To verify null passwords cannot be used, run the following command: \n\n$ grep nullok /etc/pam.d/common-password /etc/pam.d/common-auth\n\nIf this produces any output, this is a finding.","fixText":"If an account is configured for password authentication but does not have an assigned password, it is possible to log on to the account without authenticating.\n\nRemove any instances of the \"nullok\" option in \"/etc/pam.d/common-password\" to prevent logons with empty passwords.","ccis":["CCI-000366"]},{"vulnId":"V-270715","ruleId":"SV-270715r1066634_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS generates audit records for all events that affect \"/var/log/journal\" with 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\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.","fixText":"Configure Ubuntu 24.04 LTS to generate audit records for events that affect \"/var/log/journal\". \n \nAdd or update the following rule 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","ccis":["CCI-000366"]},{"vulnId":"V-270716","ruleId":"SV-270716r1066637_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS default filesystem permissions must be defined in such a way that all authenticated users can read and modify only their own files.","description":"Setting the most restrictive default permissions ensures that when new accounts are created, they do not have unnecessary access.","checkContent":"Verify Ubuntu 24.04 LTS defines default permissions for all authenticated users in such a way that the user can read and modify only their own files with the following command:\n \n$ grep -i '^\\s*umask' /etc/login.defs\nUMASK 077 \n \nIf the \"UMASK\" variable is set to \"000\", this is a finding with the severity raised to a CAT I. \n \nIf the value of \"UMASK\" is not set to \"077\", is commented out, or is missing, this is a finding.","fixText":"Configure the system to define the default permissions for all authenticated users in such a way that the user can read and modify only their own files. \n \nEdit the \"UMASK\" parameter in the \"/etc/login.defs\" file to match the example below: \n \nUMASK 077","ccis":["CCI-000366"]},{"vulnId":"V-270717","ruleId":"SV-270717r1067177_rule","severity":"high","ruleTitle":"Ubuntu 24.04 LTS must not allow unattended or automatic login via SSH.","description":"Failure to restrict system access to authenticated users negatively impacts Ubuntu 24.04 LTS security.","checkContent":"Verify unattended or automatic login via SSH is disabled with the following command:\n\n$ egrep -r '(Permit(.*?)(Passwords|Environment))' /etc/ssh/sshd_config\nPermitEmptyPasswords no\nPermitUserEnvironment no\n\nIf the \"PermitEmptyPasswords\" or \"PermitUserEnvironment\" keywords are set to a value other than \"no\", are commented out, are both missing, or conflicting results are returned, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to allow the SSH daemon to not allow unattended or automatic login to the system. \n \nAdd or edit 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-270718","ruleId":"SV-270718r1134811_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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, devices such as flash drives, external storage, and printers.\n\nSatisfies: SRG-OS-000690-GPOS-00140, SRG-OS-000378-GPOS-00163","checkContent":"Verify that Ubuntu 24.04 LTS disables the ability to load the USB storage kernel module with the following command:\n\n$ sudo grep usb-storage /etc/modprobe.d/* | grep \"/bin/false\" \n/etc/modprobe.d/DISASTIG.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 24.04 LTS disables the ability to use USB mass storage devices.\n\n$ sudo grep usb-storage /etc/modprobe.d/* | grep -i \"blacklist\"\n/etc/modprobe.d/DISASTIG.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 24.04 LTS to disable using the USB storage kernel module with the following command: \n\n$ sudo su -c \"echo install usb-storage /bin/false >> /etc/modprobe.d/DISASTIG.conf\"\n\nConfigure Ubuntu 24.04 LTS to disable the ability to use USB mass storage devices with the following command:\n\n$ sudo su -c \"echo blacklist usb-storage >> /etc/modprobe.d/DISASTIG.conf\"","ccis":["CCI-003959","CCI-001958"]},{"vulnId":"V-270719","ruleId":"SV-270719r1067172_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 wide 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, Ubuntu 24.04 LTS 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 with the following command:\n \n$ sudo ufw show raw \nChain OUTPUT (policy ACCEPT) \ntarget  prot opt sources    destination \nChain INPUT (policy ACCEPT 1 packets, 40 bytes) \n    pkts      bytes target     prot opt in     out     source               destination \n \nChain FORWARD (policy ACCEPT 0 packets, 0 bytes) \n    pkts      bytes target     prot opt in     out     source               destination \n \nChain 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 <direction> <port/protocol/service> \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 <direction> <port/protocol/service>","ccis":["CCI-000382"]},{"vulnId":"V-270720","ruleId":"SV-270720r1066649_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS contains no duplicate User IDs (UIDs) for interactive users with 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-270721","ruleId":"SV-270721r1066652_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must implement smart card logins for multifactor authentication for local and network access to privileged and nonprivileged accounts.","description":"Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased. \n \nMultifactor authentication requires using two or more factors to achieve authentication. \n \nFactors include:  \n1) Something a user knows (e.g., password/PIN); \n2) Something a user has (e.g., cryptographic identification device, token); and \n3) Something a user is (e.g., biometric). \n \nA privileged account is defined as an information system account with authorizations of a privileged user. \n \nNetwork access is defined as access to an information system by a user (or a process acting on behalf of a user) communicating through a network (e.g., local area network, wide area network, or the internet). \n \nThe DOD common access card (CAC) with DOD-approved PKI is an example of multifactor authentication.\n\nSatisfies: SRG-OS-000105-GPOS-00052, SRG-OS-000107-GPOS-00054, SRG-OS-000106-GPOS-00053, SRG-OS-000108-GPOS-00055","checkContent":"Verify that the \"pam_pkcs11.so\" module is configured with the following command:\n\n$ grep -r pam_pkcs11.so /etc/pam.d/common-auth\nauth    [success=2 default=ignore] pam_pkcs11.so\n\nIf the module is not configured, is missing, or commented out, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to use multifactor authentication for access to accounts. \n \nAdd or update \"pam_pkcs11.so\" in \"/etc/pam.d/common-auth\" to match the following line: \n \nauth    [success=2 default=ignore] pam_pkcs11.so","ccis":["CCI-000765","CCI-000766"]},{"vulnId":"V-270722","ruleId":"SV-270722r1067130_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must implement smart card logins for multifactor authentication for local and network access to privileged and nonprivileged accounts over SSH.","description":"Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased. \n \nMultifactor authentication requires using two or more factors to achieve authentication. \n \nFactors include:  \n1) Something a user knows (e.g., password/PIN); \n2) Something a user has (e.g., cryptographic identification device, token); and \n3) Something a user is (e.g., biometric). \n \nA privileged account is defined as an information system account with authorizations of a privileged user. \n \nNetwork access is defined as access to an information system by a user (or a process acting on behalf of a user) communicating through a network (e.g., local area network, wide area network, or the internet). \n \nThe DOD common access card (CAC) with DOD-approved PKI is an example of multifactor authentication.\n\nSatisfies: SRG-OS-000105-GPOS-00052, SRG-OS-000107-GPOS-00054, SRG-OS-000106-GPOS-00053, SRG-OS-000108-GPOS-00055","checkContent":"Verify the sshd daemon allows public key authentication with the following command:\n \n$ sudo grep -r ^PubkeyAuthentication /etc/ssh/sshd_config*\n/etc/ssh/sshd_config:PubkeyAuthentication yes\n\nIf \"PubkeyAuthentication\" is not set to \"yes\", is commented out, is missing, or conflicting results are returned, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to use multifactor authentication for access to accounts. \n \nSet the sshd option \"PubkeyAuthentication\" to \"yes\" in the \"/etc/ssh/sshd_config\" file.\n\nPubkeyAuthentication yes","ccis":["CCI-000765","CCI-000766"]},{"vulnId":"V-270723","ruleId":"SV-270723r1066658_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must electronically verify Personal Identity Verification (PIV) credentials.","description":"The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. \n \nDOD has mandated the use of the common access card (CAC) to support identity management and personal authentication for systems covered under Homeland Security Presidential Directive (HSPD) 12, as well as making the CAC a primary component of layered protection for national security systems.","checkContent":"Verify Ubuntu 24.04 LTS electronically verifies PIV credentials via certificate status checking with the following command: \n \n$ sudo grep use_pkcs11_module /etc/pam_pkcs11/pam_pkcs11.conf | awk '/pkcs11_module opensc {/,/}/' /etc/pam_pkcs11/pam_pkcs11.conf | grep cert_policy | grep ocsp_on \n \ncert_policy = ca,signature,ocsp_on; \n \nIf every returned \"cert_policy\" line is not set to \"ocsp_on\", or the line is commented out, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to do certificate status checking for multifactor authentication. \n \nModify all of the \"cert_policy\" lines in \"/etc/pam_pkcs11/pam_pkcs11.conf\" to include \"ocsp_on\".","ccis":["CCI-001954"]},{"vulnId":"V-270724","ruleId":"SV-270724r1066661_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must prevent direct login to 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 are 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) need to 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 Ubuntu 24.04 LTS 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 24.04 LTS prevents direct logins to the root account with the following command: \n \n$ sudo passwd -S root\nroot L 04/08/2024 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 24.04 LTS to prevent direct logins to the root account by performing the following operations: \n \n$ sudo passwd -l root","ccis":["CCI-004045"]},{"vulnId":"V-270725","ruleId":"SV-270725r1101789_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must store only encrypted representations of passwords.","description":"Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. If the information system or 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 per policy requirements.","checkContent":"Verify the Ubuntu operating system stores only encrypted representations of passwords with the following command:\n\n$ grep pam_unix.so /etc/pam.d/common-password\npassword [success=1 default=ignore] pam_unix.so obscure sha512 shadow rounds=100000\n\nIf \"sha512\" is missing from the \"pam_unix.so\" line, or if the \"rounds\" is set to less than 100000, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to store encrypted representations of passwords.\n\nAdd or modify the \"sha512\" parameter value to the following line in \"/etc/pam.d/common-password\" file:\n\npassword [success=1 default=ignore] pam_unix.so obscure sha512 shadow rounds=100000","ccis":["CCI-004062"]},{"vulnId":"V-270726","ruleId":"SV-270726r1066667_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must enforce password complexity by requiring that 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.\n\nSatisfies: SRG-OS-000069-GPOS-00037, SRG-OS-000730-GPOS-00190","checkContent":"Verify Ubuntu 24.04 LTS enforces password complexity by requiring that at least one uppercase character be used with the following command: \n \n$ grep -i \"ucredit\" /etc/security/pwquality.conf\nucredit=-1 \n \nIf the \"ucredit\" parameter is greater than \"-1\", is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to enforce password complexity by requiring that at least one uppercase character be used. \n\nAdd or update the \"/etc/security/pwquality.conf\" file to contain the \"ucredit\" parameter: \n \nucredit=-1","ccis":["CCI-004065","CCI-004066"]},{"vulnId":"V-270727","ruleId":"SV-270727r1066670_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must enforce password complexity by requiring that 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.\n\nSatisfies: SRG-OS-000070-GPOS-00038, SRG-OS-000730-GPOS-00190","checkContent":"Verify Ubuntu 24.04 LTS enforces password complexity by requiring that at least one lowercase character be used with the following command: \n \n$ grep -i \"lcredit\" /etc/security/pwquality.conf\nlcredit=-1 \n \nIf the \"lcredit\" parameter is greater than \"-1\", is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to enforce password complexity by requiring that at least one lowercase character be used. \n\nAdd or update the \"/etc/security/pwquality.conf\" file to contain the \"lcredit\" parameter: \n \nlcredit=-1","ccis":["CCI-004065","CCI-004066"]},{"vulnId":"V-270728","ruleId":"SV-270728r1066673_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must enforce password complexity by requiring that 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.\n\nSatisfies: SRG-OS-000071-GPOS-00039, SRG-OS-000730-GPOS-00190","checkContent":"Verify Ubuntu 24.04 LTS enforces password complexity by requiring that at least one numeric character be used. \n \nDetermine if the field \"dcredit\" is set in the \"/etc/security/pwquality.conf\" file with the following command: \n \n$ grep -i \"dcredit\" /etc/security/pwquality.conf\ndcredit=-1 \n \nIf the \"dcredit\" parameter is greater than \"-1\", is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to enforce password complexity by requiring that at least one numeric character be used. \n \nAdd or update the \"/etc/security/pwquality.conf\" file to contain the \"dcredit\" parameter: \n \ndcredit=-1","ccis":["CCI-004065","CCI-004066"]},{"vulnId":"V-270729","ruleId":"SV-270729r1066676_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must require the change of at least eight characters when passwords are changed.","description":"If Ubuntu 24.04 LTS 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, then 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.\n\nSatisfies: SRG-OS-000072-GPOS-00040, SRG-OS-000730-GPOS-00190","checkContent":"Verify Ubuntu 24.04 LTS requires the change of at least eight characters when passwords are changed with the following command:\n \n$ grep -i \"difok\" /etc/security/pwquality.conf\ndifok=8 \n \nIf the \"difok\" parameter is less than \"8\" or is commented out, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to require the change of at least eight characters when passwords are changed. \n \nAdd or update the \"/etc/security/pwquality.conf\" file to include the \"difok=8\" parameter: \n \ndifok=8","ccis":["CCI-004065","CCI-004066"]},{"vulnId":"V-270730","ruleId":"SV-270730r1066679_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must enforce 24 hours/1 day as the minimum password lifetime. Passwords for new users must have a 24 hours/1 day minimum password lifetime restriction.","description":"Enforcing a minimum password lifetime helps to prevent repeated password changes to defeat the password reuse or history enforcement requirement. If users are allowed to immediately and continually change their password, then the password could be repeatedly changed in a short period of time to defeat the organization's policy regarding password reuse.\n\nSatisfies: SRG-OS-000075-GPOS-00043, SRG-OS-000730-GPOS-00190","checkContent":"Verify Ubuntu 24.04 LTS enforces a 24 hours/1 day minimum password lifetime for new user accounts with the following command: \n \n$ grep -i ^PASS_MIN_DAYS /etc/login.defs \nPASS_MIN_DAYS    1 \n \nIf the \"PASS_MIN_DAYS\" parameter value is less than \"1\" or is commented out, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to enforce a 24 hours/1 day minimum password lifetime. \n \nAdd or modify the following line in the \"/etc/login.defs\" file: \n \nPASS_MIN_DAYS    1","ccis":["CCI-004065","CCI-004066"]},{"vulnId":"V-270731","ruleId":"SV-270731r1066682_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must enforce a 60-day maximum password lifetime restriction. Passwords for new users must have a 60-day maximum password lifetime restriction.","description":"Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If Ubuntu 24.04 LTS does not limit the lifetime of passwords and force users to change their passwords, there is the risk that Ubuntu 24.04 LTS passwords could be compromised.\n\nSatisfies: SRG-OS-000076-GPOS-00044, SRG-OS-000730-GPOS-00190","checkContent":"Verify Ubuntu 24.04 LTS enforces a 60-day maximum password lifetime for new user accounts with the following command:\n \n$ grep -i ^PASS_MAX_DAYS /etc/login.defs\nPASS_MAX_DAYS    60 \n \nIf the \"PASS_MAX_DAYS\" parameter value is less than \"60\" or is commented out, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to enforce a 60-day maximum password lifetime. \n \nAdd or modify the following line in the \"/etc/login.defs\" file: \n \nPASS_MAX_DAYS    60","ccis":["CCI-004065","CCI-004066"]},{"vulnId":"V-270732","ruleId":"SV-270732r1066685_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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.\n\nSatisfies: SRG-OS-000078-GPOS-00046, SRG-OS-000730-GPOS-00190","checkContent":"Verify the pwquality configuration file enforces a minimum 15-character password length with the following command:\n\n$ grep -i minlen /etc/security/pwquality.conf\nminlen=15\n\nIf \"minlen\" parameter value is not \"15\" or higher, is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to enforce a minimum 15-character password length. \n \nAdd or modify the \"minlen\" parameter value to the \"/etc/security/pwquality.conf\" file: \n \nminlen=15","ccis":["CCI-004065","CCI-004066"]},{"vulnId":"V-270733","ruleId":"SV-270733r1066688_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must enforce password complexity by requiring that 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: ~ ! @ # $ % ^ *.\n\nSatisfies: SRG-OS-000266-GPOS-00101, SRG-OS-000730-GPOS-00190","checkContent":"Determine if the field \"ocredit\" is set in the \"/etc/security/pwquality.conf\" file with the following command: \n \n$ grep -i \"ocredit\" /etc/security/pwquality.conf\nocredit=-1 \n \nIf the \"ocredit\" parameter is greater than \"-1\", is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to enforce password complexity by requiring that at least one special character be used.  \n \nAdd or update the following line in the \"/etc/security/pwquality.conf\" file to include the \"ocredit=-1\" parameter: \n \nocredit=-1","ccis":["CCI-004065","CCI-004066"]},{"vulnId":"V-270734","ruleId":"SV-270734r1155240_rule","severity":"low","ruleTitle":"Ubuntu 24.04 LTS 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":"Note: If smart card authentication is not being used on the system, this requirement is not applicable. \n\nVerify PAM prohibits the use of cached authentications after one day with the following command:\n \n$ sudo grep offline_credentials_expiration /etc/sssd/sssd.conf /etc/sssd/conf.d/*.conf \noffline_credentials_expiration = 1 \n \nIf \"offline_credentials_expiration\" in \"/etc/sssd/sssd.conf\" or in a file with a name ending in .conf in the \"/etc/sssd/conf.d/\" directory, 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. Add or change the following line in \"/etc/sssd/sssd.conf\" 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-270735","ruleId":"SV-270735r1066694_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS, for PKI-based authentication, SSSD must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor.","description":"Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted. \n \nA trust anchor is an authoritative entity represented via a public key and associated data. It is used in the context of public key infrastructures, X.509 digital certificates, and DNSSEC. \n \nWhen there is a chain of trust, usually the top entity to be trusted becomes the trust anchor; it can be, for example, a certification authority (CA). A certification path starts with the subject certificate and proceeds through a number of intermediate certificates up to a trusted root certificate, typically issued by a trusted CA. \n \nThis requirement verifies that a certification path to an accepted trust anchor is used for certificate validation and that the path includes status information. Path validation is necessary for a relying party to make an informed trust decision when presented with any certificate not already explicitly trusted. Status information for certification paths includes certificate revocation lists or online certificate status protocol responses. Validation of the certificate status information is out of scope for this requirement.\n\nSatisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000775-GPOS-00230","checkContent":"Verify Ubuntu 24.04 LTS, for PKI-based authentication, has valid certificates by constructing a certification path to an accepted trust anchor. \n\nEnsure the pam service is listed under [sssd] with the following command:\n\n$ sudo grep -A 1 '^\\[sssd\\]' /etc/sssd/sssd.conf\n[sssd]\nservices = nss,pam,ssh\n\nIf \"pam\" is not listed in services, this is a finding.\n\nAdditionally, ensure the pam service is set to use pam for smart card authentication in the [pam] section of /etc/sssd/sssd.conf with the following command:\n\n$ sudo grep -A 1 '^\\[pam]' /etc/sssd/sssd.conf\n[pam]\npam_cert_auth = True\n\nIf \"pam_cert_auth = True\" is not returned, this is a finding.\n\nEnsure \"ca\" is enabled in \"certificate_verification\" with the following command: \n  \n$ sudo grep certificate_verification /etc/sssd/sssd.conf\ncertificate_verification = ca_cert,ocsp\n \nIf \"certificate_verification\" is not set to \"ca\" or the line is commented out, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS, for PKI-based authentication, to validate certificates by constructing a certification path to an accepted trust anchor. \n \nAdd or update the /etc/sssd/sssd.conf so that the following entries are in the correct sections of the file: \n \n$ sudo vi /etc/sssd/sssd.conf\n\n[sssd]\nservices = nss,pam,ssh\nconfig_file_version = 2\n\n[pam]\npam_cert_auth = True\n\n[domain/example.com]\nldap_user_certificate = usercertificate;binary\ncertificate_verification = ca_cert,ocsp\nca_cert = /etc/ssl/certs/ca-certificates.crt","ccis":["CCI-000185","CCI-004909"]},{"vulnId":"V-270736","ruleId":"SV-270736r1066697_rule","severity":"high","ruleTitle":"Ubuntu 24.04 LTS must map the authenticated identity to the user or group account for PKI-based authentication.","description":"Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the individual user or group will not be available for forensic analysis.","checkContent":"Verify that authenticated certificates are mapped to the appropriate user group in the \"/etc/sssd/sssd.conf\" file with the following command: \n \n$ grep -i ldap_user_certificate /etc/sssd/sssd.conf\nldap_user_certificate=userCertificate;binary","fixText":"Configure sssd to map authenticated certificates to the appropriate user group by adding the following line to the \"/etc/sssd/sssd.conf\" file:\n\nldap_user_certificate=userCertificate;binary","ccis":["CCI-000187"]},{"vulnId":"V-270737","ruleId":"SV-270737r1067178_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS, for PKI-based authentication, Privileged Access Management (PAM) must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor.","description":"Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted. \n \nA trust anchor is an authoritative entity represented via a public key and associated data. It is used in the context of public key infrastructures, X.509 digital certificates, and DNSSEC. \n \nWhen there is a chain of trust, usually the top entity to be trusted becomes the trust anchor; it can be, for example, a certification authority (CA). A certification path starts with the subject certificate and proceeds through a number of intermediate certificates up to a trusted root certificate, typically issued by a trusted CA. \n \nThis requirement verifies that a certification path to an accepted trust anchor is used for certificate validation and that the path includes status information. Path validation is necessary for a relying party to make an informed trust decision when presented with any certificate not already explicitly trusted. Status information for certification paths includes certificate revocation lists or online certificate status protocol responses. Validation of the certificate status information is out of scope for this requirement.\n\nSatisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000775-GPOS-00230","checkContent":"Verify Ubuntu 24.04 LTS, for PKI-based authentication, has valid certificates by constructing a certification path to an accepted trust anchor. \n \nDetermine which pkcs11 module is being used via the \"use_pkcs11_module\" in \"/etc/pam_pkcs11/pam_pkcs11.conf\" and then ensure \"ca\" is enabled in \"cert_policy\" with the following command: \n  \n$ sudo grep use_pkcs11_module /etc/pam_pkcs11/pam_pkcs11.conf | awk '/pkcs11_module opensc {/,/}/' /etc/pam_pkcs11/pam_pkcs11.conf | grep cert_policy | grep ca  \n \ncert_policy = ca,signature,ocsp_on; \n \nIf \"cert_policy\" is not set to \"ca\" or the line is commented out, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS, for PKI-based authentication, to validate certificates by constructing a certification path to an accepted trust anchor. \n \nDetermine which pkcs11 module is being used via the \"use_pkcs11_module\" in \"/etc/pam_pkcs11/pam_pkcs11.conf\" and ensure \"ca\" is enabled in \"cert_policy\". \n \nAdd or update the \"cert_policy\" to ensure \"ca\" is enabled: \n \ncert_policy = ca,signature,ocsp_on; \n \nIf the system is missing an \"/etc/pam_pkcs11/\" directory and an \"/etc/pam_pkcs11/pam_pkcs11.conf\", find an example to copy into place and modify accordingly at \"https://manpages.ubuntu.com/manpages/xenial/man8/pam_pkcs11.8.html\".","ccis":["CCI-000185","CCI-004909"]},{"vulnId":"V-270738","ruleId":"SV-270738r1066703_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS for PKI-based authentication, must implement a local cache of revocation data in case of the inability to access revocation information via the network.","description":"Without configuring a local cache of revocation data, there is the potential to allow access to users who are no longer authorized (users with revoked certificates).","checkContent":"Note: If smart card authentication is not being used on the system, this is not applicable. \n \nVerify Ubuntu 24.04 LTS, for PKI-based authentication, uses local revocation data when unable to access it from the network with the following command:\n\n$ grep cert_policy /etc/pam_pkcs11/pam_pkcs11.conf | grep  -E -- 'crl_auto|crl_offline' \ncert_policy = ca,signature,ocsp_on,crl_auto; \n \nIf \"cert_policy\" is not set to include \"crl_auto\" or \"crl_offline\", this is a finding.","fixText":"Configure Ubuntu 24.04 LTS, for PKI-based authentication, to use local revocation data when unable to access the network to obtain it remotely. \n \nAdd or update the \"cert_policy\" option in \"/etc/pam_pkcs11/pam_pkcs11.conf\" to include \"crl_auto\" or \"crl_offline\". \n \ncert_policy = ca,signature,ocsp_on, crl_auto; \n \nIf the system is missing an \"/etc/pam_pkcs11/\" directory and an \"/etc/pam_pkcs11/pam_pkcs11.conf\", find an example to copy into place and modify accordingly at \"/usr/share/doc/libpam-pkcs11/examples/pam_pkcs11.conf.example.gz\".","ccis":["CCI-004068"]},{"vulnId":"V-270739","ruleId":"SV-270739r1067124_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must encrypt all stored passwords with a FIPS 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 the shadow password suite configuration is set to encrypt passwords with a FIPS 140-3 approved cryptographic hashing algorithm with the following command: \n \n$ grep -i ENCRYPT_METHOD /etc/login.defs \nENCRYPT_METHOD SHA512 \n \nIf \"ENCRYPT_METHOD\" does not equal SHA512 or greater, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to encrypt all stored passwords.  \n \nEdit/modify the following line in the \"/etc/login.defs\" file and set \"ENCRYPT_METHOD\" to SHA512: \n \nENCRYPT_METHOD SHA512","ccis":["CCI-000803"]},{"vulnId":"V-270740","ruleId":"SV-270740r1066709_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS audits activities performed during nonlocal maintenance and diagnostic sessions with 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\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.","fixText":"Configure Ubuntu 24.04 LTS to audit activities performed during nonlocal maintenance and diagnostic sessions. \n \nAdd or update the following rules 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","ccis":["CCI-002884","CCI-000172"]},{"vulnId":"V-270741","ruleId":"SV-270741r1066712_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS is configured to use strong authenticators in the establishment of nonlocal maintenance and diagnostic maintenance with the following command:\n\n$ sudo grep -r ^UsePAM /etc/ssh/sshd_config*\n/etc/ssh/sshd_config:UsePAM yes\n\nIf \"UsePAM\" is not set to \"yes\", conflicting results are returned, the line is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS 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","ccis":["CCI-000877"]},{"vulnId":"V-270742","ruleId":"SV-270742r1066715_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must immediately terminate all network connections associated with SSH traffic after a period of inactivity.","description":"Automatic session termination addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. \n \nSession termination terminates all processes associated with a user's logical session except those processes that are specifically created by the user (i.e., session owner) to continue after the session is terminated. \n \nConditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on information system use. \n \nThis capability is typically reserved for specific Ubuntu 24.04 LTS functionality where the system owner, data owner, or organization requires additional assurance.","checkContent":"Verify that all network connections associated with SSH traffic automatically terminate after a period of inactivity with the following command: \n\n$ sudo grep -ir ClientAliveCountMax /etc/ssh/sshd_config*\n/etc/ssh/sshd_config:ClientAliveCountMax  1\n\nIf \"ClientAliveCountMax\" is not to \"1\", if conflicting results are returned, is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to automatically terminate inactive SSH sessions after a period of inactivity. \n \nModify or append the following line in the \"/etc/ssh/sshd_config\" file, replacing \"[Count]\" with a value of 1: \n \nClientAliveCountMax 1 \n \nRestart the SSH daemon for the changes to take effect: \n \n$ sudo systemctl restart ssh.service","ccis":["CCI-001133"]},{"vulnId":"V-270743","ruleId":"SV-270743r1066718_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must immediately terminate all network connections associated with SSH traffic at the end of the session or after 10 minutes of inactivity.","description":"Terminating an idle 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 session will also free up resources committed by the managed network element.  \n \nTerminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at Ubuntu 24.04 LTS level, and de-allocating networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. This does not mean that Ubuntu 24.04 LTS terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.","checkContent":"Verify that all network connections associated with SSH traffic are automatically terminated at the end of the session or after 10 minutes of inactivity with the following command:\n\n$ grep -ir ClientAliveInterval /etc/ssh/sshd_config*\n/etc/ssh/sshd_config:ClientAliveInterval 600\n\nIf \"ClientAliveInterval\" does not exist, is not set to a value of \"600\" or less in \"/etc/ssh/sshd_config\", if conflicting results are returned, is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to automatically terminate all network connections associated with SSH traffic at the end of a session or after a 10-minute period of inactivity.\n\nIn the file /etc/ssh/sshd_config set ClientAliveInterval to a value of \"600\" or less: \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-270744","ruleId":"SV-270744r1137699_rule","severity":"high","ruleTitle":"Ubuntu 24.04 LTS must implement NIST FIPS-validated cryptography to protect classified information and for the following: To provision digital signatures, to generate cryptographic hashes, and to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards.","description":"Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. Ubuntu 24.04 LTS 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-000478-GPOS-00223, SRG-OS-000396-GPOS-00176","checkContent":"Verify the system is configured to run in FIPS mode with the following command: \n \n$ grep -i 1 /proc/sys/crypto/fips_enabled\n1 \n \nIf a value of \"1\" is not returned, this is a finding.","fixText":"Configure the system to run in FIPS mode. Add \"fips=1\" to the kernel parameter during Ubuntu 24.04 LTSs install. \n \nEnabling a FIPS mode on a pre-existing system involves a number of modifications to Ubuntu 24.04 LTS. 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\n\nThe basic steps use the following commands:\n\n$ sudo pro attach <token>\n$ sudo pro enable fips-updates","ccis":["CCI-002450"]},{"vulnId":"V-270745","ruleId":"SV-270745r1066724_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must use DOD PKI-established certificate authorities (CAs) for verification of the establishment of protected sessions.","description":"Untrusted CAs can issue certificates, but they may be issued by organizations or individuals that seek to compromise DOD systems or by organizations with insufficient security controls. If the CA used for verifying the certificate is not a DOD-approved CA, trust of this CA has not been established. \n \nThe DOD will only accept PKI-certificates obtained from a DOD-approved internal or external certificate authority. Reliance on CAs for the establishment of secure sessions includes, for example, the use of SSL/TLS certificates.","checkContent":"Verify the directory containing the root certificates for Ubuntu 24.04 LTS contains certificate files for DOD PKI-established CAs by iterating over all files in the \"/etc/ssl/certs\" directory and checking if, at least one, has the subject matching \"DOD ROOT CA\".\n\n$ grep -ir DOD /etc/ssl/certs\nDOD_PKE_CA_chain.pem\n\nIf no root certificate is found, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to use of DOD PKI-established CAs for verification of the establishment of protected sessions. \n \nEdit the \"/etc/ca-certificates.conf\" file, adding the character \"!\" to the beginning of all uncommented lines that do not start with the \"!\" character with the following command: \n \n$ sudo sed -i -E 's/^([^!#]+)/!\\1/' /etc/ca-certificates.conf \n \nAdd at least one CA to the \"/usr/local/share/ca-certificates\" directory in the PEM format. \n \nUpdate the \"/etc/ssl/certs\" directory with the following command: \n \n$ sudo update-ca-certificates","ccis":["CCI-002470"]},{"vulnId":"V-270746","ruleId":"SV-270746r1155242_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 unless needed with the following command: \n \n$ systemctl status kdump-tools.service\no kdump-tools.service\n     Loaded: masked (Reason: Unit kdump-tools.service is masked.)\n     Active: inactive (dead)\n\nIf kdump-tools is not installed the output will be:\nUnit kdump-tools.service could not be found.\n\nIf \"kdump-tools.service\" is not masked and inactive, 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 and is not documented, this is a finding.","fixText":"If kernel core dumps are not required, disable the \"kdump-tools\" service with the following command: \n \n$ sudo systemctl disable kdump-tools.service\n \nIf kernel core dumps are required, document the need with the ISSO.","ccis":["CCI-001190"]},{"vulnId":"V-270747","ruleId":"SV-270747r1066730_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS handling data requiring \"data at rest\" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.","description":"Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive and tape drive, when used for backups) within an operating system. \n \nThis requirement addresses protection of user-generated data, as well as operating system-specific configuration data. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate, in accordance with the security category and/or classification of the information.\n\nSatisfies: SRG-OS-000185-GPOS-00079, SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS-00184, SRG-OS-000780-GPOS-00240","checkContent":"Note: If there is a documented and approved mission requirement for data-at-rest to not be encrypted, this requirement is not applicable. \n \nVerify Ubuntu 24.04 LTS prevents unauthorized disclosure or modification of all information requiring at-rest protection by using disk encryption.  \n\nDetermine the partition layout for the system with the following command: \n \n$ sudo fdisk -l \n(..) \nDisk /dev/vda: 15 GiB, 16106127360 bytes, 31457280 sectors \nUnits: sectors of 1 * 512 = 512 bytes \nSector size (logical/physical): 512 bytes / 512 bytes \nI/O size (minimum/optimal): 512 bytes / 512 bytes \nDisklabel type: gpt \nDisk identifier: 83298450-B4E3-4B19-A9E4-7DF147A5FEFB \n \nDevice       Start      End  Sectors Size Type \n/dev/vda1     2048     4095     2048   1M BIOS boot \n/dev/vda2     4096  2101247  2097152   1G Linux filesystem \n/dev/vda3  2101248 31455231 29353984  14G Linux filesystem \n(...) \n \nVerify the system partitions are all encrypted with 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-270748","ruleId":"SV-270748r1066733_rule","severity":"high","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS restricts access to security functions through the use of access control mechanisms and by implementing least privilege capabilities.","checkContent":"Verify the sudo group has only members who require access to security functions with the following command:  \n \n$ grep sudo /etc/group\nsudo:x:27:foo \n \nIf the sudo group contains users not needing access to security functions, this is a finding.","fixText":"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 <username> sudo","ccis":["CCI-001084"]},{"vulnId":"V-270749","ruleId":"SV-270749r1137695_rule","severity":"low","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS is configured to restrict access to the kernel message buffer with the following command:\n\n$ sysctl kernel.dmesg_restrict\nkernel.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 -r 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 any instance of \"kernel.dmesg_restrict\" is uncommented and set to \"0\", or if conflicting results are returned, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to restrict access to the kernel message buffer.\n\nSet the system to the required kernel parameter by adding or modifying the following line in /etc/sysctl.conf or a config file in the /etc/sysctl.d/ directory:\n\n     kernel.dmesg_restrict = 1\n\nRemove any configurations that conflict with the above from the following locations: \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 with the following command:\n\n     $ sudo sysctl --system","ccis":["CCI-001090"]},{"vulnId":"V-270750","ruleId":"SV-270750r1137695_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 all public (world-writeable) directories have the public sticky bit set with the following command:  \n \n$ sudo find / -type d -perm -002 ! -perm -1000 \n \nIf any world-writable 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 \"[Public Directory]\" with any directory path missing the sticky bit: \n \n$ sudo chmod +t  [Public Directory]","ccis":["CCI-001090"]},{"vulnId":"V-270751","ruleId":"SV-270751r1066742_rule","severity":"low","ruleTitle":"Ubuntu 24.04 LTS must compare internal information system clocks at least every 24 hours with an authoritative time server.","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 must consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints).\n\nSatisfies: SRG-OS-000785-GPOS-00250, SRG-OS-000355-GPOS-00143","checkContent":"Note: If the system is not networked, this requirement is not applicable.\n\nVerify Ubuntu 24.04 LTS is configured to compare the system clock at least every 24 hours to an authoritative time source with the following command:\n\n$ sudo grep -ir maxpoll /etc/chrony*\nserver [source] iburst maxpoll 16\n\nIf the parameter \"server\" is not set, is not set to an authoritative DOD time source, or is commented out, this is a finding.\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.","fixText":"To configure the system clock to compare to the authoritative time source at least every 24 hours, edit the \"/etc/chrony/chrony.conf\" file. Add or correct the following lines, by replacing \"[source]\" in the following line with an authoritative time source: \n\nserver [source] iburst maxpoll 16 \n\nIf the \"chrony\" service was running and the value of \"maxpoll\" or \"server\" was updated, the service must be restarted using the following command: \n\n$ sudo systemctl restart chrony.service","ccis":["CCI-004922","CCI-004923"]},{"vulnId":"V-270752","ruleId":"SV-270752r1068365_rule","severity":"low","ruleTitle":"Ubuntu 24.04 LTS 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 must 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 because a comparison must be done to determine the time difference.","checkContent":"Verify Ubuntu 24.04 LTS synchronizes internal system clocks to the authoritative time source when the time difference is greater than one second. \n \nCheck the value of \"makestep\" with the following command: \n \n$ grep makestep /etc/chrony/chrony.conf\nmakestep 1 -1 \n \nIf the makestep option is not set to \"1 -1\", is commented out, or is missing, 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 \nmakestep 1 -1 \n \nRestart the chrony service: \n \n$ sudo systemctl restart chrony.service","ccis":["CCI-004926"]},{"vulnId":"V-270753","ruleId":"SV-270753r1066748_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must be configured to use TCP syncookies.","description":"Denial of service (DoS) occurs when a resource is not available for legitimate users, resulting in the organization not being able to accomplish its mission or causing it to operate at degraded capacity.  \n \nManaging excess capacity ensures 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 24.04 LTS is configured to use TCP syncookies with the following command:\n \n$ sysctl net.ipv4.tcp_syncookies \nnet.ipv4.tcp_syncookies = 1 \n \nIf the value is not \"1\", this is a finding. \n \nCheck the saved value of TCP syncookies with 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/etc/sysctl.d/99-sysctl.conf:net.ipv4.tcp_syncookies=1\n/etc/sysctl.conf:net.ipv4.tcp_syncookies=1\n\nIf the \"net.ipv4.tcp_syncookies\" option is not set to \"1\", is commented out, or is missing, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to use TCP syncookies with 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 \nnet.ipv4.tcp_syncookies = 1","ccis":["CCI-001095"]},{"vulnId":"V-270754","ruleId":"SV-270754r1066751_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must configure the uncomplicated firewall to rate-limit impacted network interfaces.","description":"Denial of service (DoS) occurs when a resource is not available for legitimate users, resulting in the organization not being able to accomplish its mission or causing it to operate at degraded capacity.\n \nThis requirement addresses the configuration of Ubuntu 24.04 LTS 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 with the following command: \n \n$ ss -l46ut \nNetid               State          Recv-Q          Send-Q                               Local Address:Port            Peer Address:Port               Process                \ntcp                 LISTEN               0                     511                                           *:http                                          *:* \ntcp                 LISTEN               0                     128                                           [::]:ssh                                        [::]:*\ntcp                 LISTEN               0                     128                                           [::]:ipp                                        [::]:* \ntcp                 LISTEN               0                     128                                           [::]:smtp                                    [::]:*\n\n \nFor each entry, verify the Uncomplicated Firewall (ufw) is configured to rate limit the service ports with the following command: \n \n$ sudo ufw status \nStatus: active \n \nTo                           Action     From \n--                             ------         ---- \n80/tcp                    LIMIT       Anywhere\n25/tcp                    LIMIT       Anywhere\nAnywhere            DENY       177.60.7.4\n443                           LIMIT      Anywhere       \n22/tcp                     LIMIT      Anywhere    \n80/tcp (v6)            LIMIT      Anywhere\n25/tcp (v6)            LIMIT      Anywhere               \n22/tcp (v6)            LIMIT      Anywhere (v6) \n\n25                             DENY OUT    Anywhere\n25 (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. If the Status is set to anything other than \"active\" this is a finding.","fixText":"Configure the application firewall to protect against or limit the effects of DoS attacks by ensuring Ubuntu 24.04 LTS is implementing rate-limiting measures on impacted network interfaces. \n \nTo change the Status of ufw to \"active\" use the following command:\n$ sudo ufw enable\n\nCheck all the services listening to the ports with the following command: \n \n$ sudo ss -l46ut \nNetid               State                Recv-Q                Send-Q                               Local Address:Port                               Peer Address:Port               Process                \ntcp                 LISTEN               0                     128                                           [::]:ssh                                        [::]:* \n \nFor each service with a port listening to connections, run the following command, replacing \"[service]\" with the service that needs to be rate limited. \n \n$ sudo ufw limit [service] \n \nRate-limiting can also be done on an interface. An example of adding a rate-limit on the eth0 interface follows: \n \n$ sudo ufw limit in on eth0","ccis":["CCI-002385"]},{"vulnId":"V-270755","ruleId":"SV-270755r1066754_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must disable all wireless network adapters.","description":"Without protection of communications with wireless peripherals, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read, altered, or used to compromise Ubuntu 24.04 LTS. \n \nThis requirement applies to wireless peripheral technologies (e.g., wireless mice, keyboards, displays, etc.) used with an operating system. Wireless peripherals (e.g., Wi-Fi/Bluetooth/IR Keyboards, Mice, and Pointing Devices and Near Field Communications [NFC]) present a unique challenge by creating an open, unsecured port on a computer. Wireless peripherals must meet DOD requirements for wireless data transmission and be approved for use by the approving authority (AO). Even though some wireless peripherals, such as mice and pointing devices, do not ordinarily carry information that need to be protected, modification of communications with these wireless peripherals may be used to compromise Ubuntu 24.04 LTS. Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. \n \nProtecting the confidentiality and integrity of communications with wireless peripherals can be accomplished by physical means (e.g., employing physical barriers to wireless radio frequencies) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa. If the wireless peripheral is only passing telemetry data, encryption of the data may not be required.","checkContent":"Note: This requirement is not applicable for systems that do not have physical wireless network radios.\n\nVerify there are no wireless interfaces configured on the system with the following command: \n \n$ ls -L -d /sys/class/net/*/wireless | xargs dirname | xargs basename \n \nIf a wireless interface is configured and has not been documented and approved by the information system security officer (ISSO), this is a finding.","fixText":"List all the wireless interfaces with the following command: \n \n$ ls -L -d /sys/class/net/*/wireless | xargs dirname | xargs basename \n \nFor each interface, configure the system to disable wireless network interfaces with the following command: \n \n$ sudo ifdown <interface name> \n \nFor each interface listed, find their respective module with the following command: \n \n$ basename $(readlink -f /sys/class/net/<interface name>/device/driver) \n \nwhere <interface name> must be substituted by the actual interface name. \n \nCreate a file in the \"/etc/modprobe.d\" directory and for each module, add the following line: \n \ninstall <module name> /bin/true \n \nFor each module from the system, execute the following command to remove it: \n \n$ sudo modprobe -r <module name>","ccis":["CCI-002418"]},{"vulnId":"V-270756","ruleId":"SV-270756r1134814_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 organizations must carefully consider the content and structure of error messages. \n \nThe 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. Additionally, Canonical recommends excluding the history.log and eipp.log.xz from consideration in this check.","checkContent":"Verify Ubuntu 24.04 LTS has all system log files under the /var/log directory with a permission set to \"640\" or less permissive with the following command:\n\nNote: The btmp, wtmp, lastlog, history, and eipp.log.xz files are excluded from this check. Refer to the 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 24.04 LTS 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, lastlog, history, and eipp.log.xz files are excluded. Refer to the 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-270757","ruleId":"SV-270757r1184072_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 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.","checkContent":"Verify the /run/log/journal and /var/log/journal directories have permissions set to \"640\" or less permissive with the following command:\n\n$ sudo find /run/log/journal /var/log/journal  -type d -exec stat -c \"%n %a\" {} \\;\n/run/log/journal 640\n/var/log/journal 640\n/var/log/journal/6a52424faa6e480ea5fc7346b9345792 640\n\nIf any output returned has a permission set greater than 640, 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 with the following command:\n\n$ sudo find /run/log/journal /var/log/journal  -type f -exec stat -c \"%n %a\" {} \\;\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/system.journal 640\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/user-1000@0005f97cd4a8c9b5a.journal~ 640\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/system@0005f97cd2a1e0a7-d58b848af46813a4.journal~ 640\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/system@0005f97cb900e501-55ea053b7f75ae1c.journal~ 640\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/user-1000.journal 640\n\nIf any output returned has a permission set greater than \"640\", this is a finding.","fixText":"Configure the system to set the appropriate permissions to the files and directories used by the systemd journal.\n\nCreate a drop-in file if it does not already exist with the following command:\n\n$ sudo vi /etc/tmpfiles.d/zzz-systemd-stig.conf\n \nAdd or modify the following lines in the \"/usr/lib/tmpfiles.d/zzz-systemd-stig.conf\" file: \n\nz /run/log/journal 0640 root systemd-journal - -\nZ /run/log/journal/%m ~0640 root systemd-journal - -\nz /var/log/journal 0640 root systemd-journal - -\nz /var/log/journal/%m 0640 root systemd-journal - -\nz /var/log/journal/%m/system.journal 0640 root systemd-journal - -\n\nNote: Restart the system for these settings to take effect.","ccis":["CCI-001312"]},{"vulnId":"V-270758","ruleId":"SV-270758r1066763_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 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 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.","checkContent":"Verify the journalctl command has a permission set of \"740\" with 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-270759","ruleId":"SV-270759r1068367_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must be configured so that the \"journalctl\" command is owned by \"root\".","description":"Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS 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 journalctl command is owned by \"root\" with 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-001314"]},{"vulnId":"V-270760","ruleId":"SV-270760r1066769_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must be configured so that the \"journalctl\" command is group-owned by \"root\".","description":"Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS 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 journalctl command is group-owned by \"root\" with 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-001314"]},{"vulnId":"V-270761","ruleId":"SV-270761r1184074_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must configure the directories used by the system journal to be group-owned by \"systemd-journal\".","description":"Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS 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\" with 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/d5745ad455d34fb8b6f78be37c1fcd3e systemd-journal\n\nIf any output returned is not group-owned by \"systemd-journal\", this is a finding.","fixText":"Configure the system to set the appropriate group-ownership to the directories used by the systemd journal.\n\nCreate a drop-in file if it does not already exist with the following command:\n\n$ sudo vi /etc/tmpfiles.d/zzz-systemd-stig.conf\n \nAdd or modify the following lines in the \"/usr/lib/tmpfiles.d/zzz-systemd-stig.conf\" file: \n\nz /run/log/journal 0640 root systemd-journal - -\nz /var/log/journal 0640 root systemd-journal - -\n\nNote: Restart the system for these settings to take effect.","ccis":["CCI-001314"]},{"vulnId":"V-270762","ruleId":"SV-270762r1184076_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must configure the files used by the system journal to be group-owned by \"systemd-journal\".","description":"Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS 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\" with the following command:\n\n$ sudo find /run/log/journal /var/log/journal  -type f -exec stat -c \"%n %G\" {} \\; \n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/system.journal systemd-journal\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/user-1000@0005f97cd4a8c9b5-f088232c3718485a.journal~ systemd-journal\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/system@0005f97cd2a1e0a7-d58b848af46813a4.journal~ systemd-journal\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/system@0005f97cb900e501-55ea053b7f75ae1c.journal~ systemd-journal\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/user-1000.journal systemd-journal\n\nIf any output returned is not group-owned by \"systemd-journal\", this is a finding.","fixText":"Configure the system to set the appropriate group-ownership to the files used by the systemd journal.\n\nCreate a drop-in file if it does not already exist with the following command:\n\n$ sudo vi /etc/tmpfiles.d/zzz-systemd-stig.conf\n \nAdd or modify the following lines in the \"/usr/lib/tmpfiles.d/zzz-systemd-stig.conf\" file: \n\nZ /run/log/journal/%m ~0640 root systemd-journal - -\nz /var/log/journal/%m 0640 root systemd-journal - -\nz /var/log/journal/%m/system.journal 0640 root systemd-journal - -\n\nNote: Restart the system for these settings to take effect.","ccis":["CCI-001314"]},{"vulnId":"V-270763","ruleId":"SV-270763r1184078_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must configure the directories used by the system journal to be owned by \"root\".","description":"Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS 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\" with 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/d5745ad455d34fb8b6f78be37c1fcd3e root\n\nIf any output returned is not owned by \"root\", this is a finding.","fixText":"Configure the system to set the appropriate ownership to the directories used by the systemd journal.\n\nCreate a drop-in file if it does not already exist with the following command:\n\n$ sudo vi /etc/tmpfiles.d/zzz-systemd-stig.conf\n \nAdd or modify the following lines in the \"/usr/lib/tmpfiles.d/zzz-systemd-stig.conf\" file: \n\nz /run/log/journal 0640 root systemd-journal - -\nz /var/log/journal 0640 root systemd-journal - -\n\nNote: Restart the system for these settings to take effect.","ccis":["CCI-001314"]},{"vulnId":"V-270764","ruleId":"SV-270764r1184080_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must configure the files used by the system journal to be owned by \"root\"","description":"Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS 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\" with the following command:\n\n$ sudo find /run/log/journal /var/log/journal  -type f -exec stat -c \"%n %U\" {} \\; \n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/system.journal root\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/user-1000@0005f97cd4a8c9b5-f088232c3718485a.journal~ root\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/system@0005f97cd2a1e0a7-d58b848af46813a4.journal~ root\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/system@0005f97cb900e501-55ea053b7f75ae1c.journal~ root\n/var/log/journal/d5745ad455d34fb8b6f78be37c1fcd3e/user-1000.journal root\n\nIf any output returned is not owned by \"root\", this is a finding.","fixText":"Configure the system to set the appropriate ownership to the files used by the systemd journal.\n\nCreate a drop-in file if it does not already exist with the following command:\n\n$ sudo vi /etc/tmpfiles.d/zzz-systemd-stig.conf\n \nAdd or modify the following lines in the \"/usr/lib/tmpfiles.d/zzz-systemd-stig.conf\" file: \n\nZ /run/log/journal/%m ~0640 root systemd-journal - -\nz /var/log/journal/%m 0640 root systemd-journal - -\nz /var/log/journal/%m/system.journal 0640 root systemd-journal - -\n\nNote: Restart the system for these settings to take effect.","ccis":["CCI-001314"]},{"vulnId":"V-270765","ruleId":"SV-270765r1066784_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must configure the /var/log directory to be group-owned by syslog.","description":"Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS 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 24.04 LTS configures the /var/log directory to be group-owned by \"syslog\" with 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 24.04 LTS to have syslog group-own the /var/log directory with the following command: \n \n$ sudo chgrp syslog /var/log","ccis":["CCI-001314"]},{"vulnId":"V-270766","ruleId":"SV-270766r1066787_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must configure the /var/log directory to be owned by root.","description":"Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS 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 24.04 LTS configures the /var/log directory to be owned by \"root\" with 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 24.04 LTS to have root own the /var/log directory by running the following command: \n \n$ sudo chown root /var/log","ccis":["CCI-001314"]},{"vulnId":"V-270767","ruleId":"SV-270767r1066790_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must configure the /var/log directory to have mode \"0755\" or less permissive.","description":"Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS 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":"Note: If rsyslog is active and enabled on Ubuntu 24.04 LTS, this requirement is not applicable.\n\nVerify Ubuntu 24.04 LTS configures the /var/log directory with a mode of \"755\" or less permissive with the following command:\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 Ubuntu 24.04 LTS to have permissions of \"0755\" for the /var/log directory by running the following command: \n \n$ sudo chmod 0755 /var/log","ccis":["CCI-001314"]},{"vulnId":"V-270768","ruleId":"SV-270768r1066793_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must configure the /var/log/syslog file to be group-owned by adm.","description":"Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS 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 24.04 LTS configures the /var/log/syslog file to be group-owned by \"adm\" with 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 24.04 LTS to have adm group-own the /var/log/syslog file by running the following command: \n \n$ sudo chgrp adm /var/log/syslog","ccis":["CCI-001314"]},{"vulnId":"V-270769","ruleId":"SV-270769r1066796_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must configure /var/log/syslog file to be owned by syslog.","description":"Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS 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 24.04 LTS configures the /var/log/syslog file to be owned by \"syslog\" with the following command: \n \n$ stat -c \"%n %U\" /var/log/syslog \n/var/log/syslog syslog \n \nIf the \"/var/log/syslog\" file is not owned by syslog, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to have syslog own the /var/log/syslog file by running the following command: \n \n$ sudo chown syslog /var/log/syslog","ccis":["CCI-001314"]},{"vulnId":"V-270770","ruleId":"SV-270770r1066799_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must configure /var/log/syslog file with mode \"0640\" or less permissive.","description":"Only authorized personnel are to be made aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify Ubuntu 24.04 LTS 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 24.04 LTS configures the /var/log/syslog file with mode \"0640\" or less permissive with 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 24.04 LTS to have permissions of \"0640\" for the /var/log/syslog file by running the following command: \n \n$ sudo chmod 0640 /var/log/syslog","ccis":["CCI-001314"]},{"vulnId":"V-270771","ruleId":"SV-270771r1066802_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 with 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 cpuinfo settings with the following command:  \n \n$ grep flags /proc/cpuinfo | grep -w nx | sort -u \nflags       : fpu vme de pse tsc ms nx rdtscp lm constant_tsc \n \nIf \"flags\" does not contain the \"nx\" flag, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to enable NX. \n \nIf \"nx\" is not showing up in \"/proc/cpuinfo\", and the system's BIOS setup configuration permits toggling the No Execution bit, set it to \"enable\".","ccis":["CCI-002824"]},{"vulnId":"V-270772","ruleId":"SV-270772r1066805_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 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 Ubuntu 24.04 LTS implements address space layout randomization (ASLR) with the following command: \n \n$ sysctl kernel.randomize_va_space\nkernel.randomize_va_space = 2 \n \nIf nothing is returned, verify the kernel parameter \"randomize_va_space\" is set to \"2\" with the following command: \n \n$ cat /proc/sys/kernel/randomize_va_space\n2 \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 egrep -R \"^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 \nAfter the line has been removed, the kernel settings from all system configuration files must be reloaded before any of the changes will take effect. Run the following command to reload all of the kernel system configuration files: \n \n$ sudo sysctl --system","ccis":["CCI-002824"]},{"vulnId":"V-270773","ruleId":"SV-270773r1066808_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must be configured so that Advance Package Tool (APT) removes all software components after updated versions have been installed.","description":"Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by adversaries. Some information technology products may remove older versions of software automatically from the information system.","checkContent":"Verify APT is configured to remove all software components after updated versions have been installed with the following command: \n \n$ grep -i remove-unused /etc/apt/apt.conf.d/50unattended-upgrades \nUnattended-Upgrade::Remove-Unused-Dependencies \"true\"; \nUnattended-Upgrade::Remove-Unused-Kernel-Packages \"true\"; \n \nIf the \"::Remove-Unused-Dependencies\" and \"::Remove-Unused-Kernel-Packages\" parameters are not set to \"true\", are commented out, or are missing, this is a finding.","fixText":"Configure APT to remove all software components after updated versions have been installed. \n \nAdd or update the following options to the \"/etc/apt/apt.conf.d/50unattended-upgrades\" file: \n \nUnattended-Upgrade::Remove-Unused-Dependencies \"true\"; \nUnattended-Upgrade::Remove-Unused-Kernel-Packages \"true\";","ccis":["CCI-002617"]},{"vulnId":"V-270775","ruleId":"SV-270775r1068369_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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/rules.d/*, and /etc/audit/auditd.conf files have a mode of \"0640\" or less permissive with the following command: \n \n$ sudo ls -al /etc/audit/ /etc/audit/rules.d/\n/etc/audit/: \n \n-rw-r-----   1 root root   804 Nov 25 11:01 auditd.conf \n -rw-r-----   1 root root  9128 Dec 27 09:56 audit.rules \n-rw-r-----   1 root root   127 Feb  7  2018 audit-stop.rules \n \ndrwxr-x---   2 root root  4096 Dec 27 09:56 rules.d \n \n/etc/audit/rules.d/: \n\n -rw-r----- 1 root root 244 Dec 27 09:56 audit.rules \n-rw-r----- 1 root root 10357 Dec 27 09:56 stig.rules \n \nIf /etc/audit/audit.rule, /etc/audit/rules.d/*, or /etc/audit/auditd.conf files have a mode more permissive than \"0640\", this is a finding.","fixText":"Configure /etc/audit/audit.rules, /etc/audit/rules.d/*, and /etc/audit/auditd.conf files to have a mode of \"0640\" by using the following command: \n \n$ sudo chmod -R 0640 /etc/audit/audit*.{rules,conf} /etc/audit/rules.d/*","ccis":["CCI-000171"]},{"vulnId":"V-270776","ruleId":"SV-270776r1066817_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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/rules.d/*, and /etc/audit/auditd.conf files are owned by \"root\" account with the following command: \n \n$ sudo ls -al /etc/audit/ /etc/audit/rules.d/ \n/etc/audit/: \n \n-rw-r-----   1 root root   804 Nov 25 11:01 auditd.conf \n -rw-r-----   1 root root  9128 Dec 27 09:56 audit.rules \n-rw-r-----   1 root root   127 Feb  7  2018 audit-stop.rules \n \ndrwxr-x---   2 root root  4096 Dec 27 09:56 rules.d \n \n/etc/audit/rules.d/: \n\n -rw-r----- 1 root root 244 Dec 27 09:56 audit.rules \n-rw-r----- 1 root root 10357 Dec 27 09:56 stig.rules \n \nIf the /etc/audit/audit.rules, /etc/audit/rules.d/*, or /etc/audit/auditd.conf file is 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\" user by using the following command: \n \n$ sudo chown root /etc/audit/audit*.{rules,conf} /etc/audit/rules.d/*","ccis":["CCI-000171"]},{"vulnId":"V-270777","ruleId":"SV-270777r1066820_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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/rules.d/*, and /etc/audit/auditd.conf files are owned by \"root\" group with the following command: \n \n$ sudo ls -al /etc/audit/ /etc/audit/rules.d/\n/etc/audit/: \n \n-rw-r-----   1 root root   804 Nov 25 11:01 auditd.conf \n -rw-r-----   1 root root  9128 Dec 27 09:56 audit.rules \n-rw-r-----   1 root root   127 Feb  7  2018 audit-stop.rules \n \ndrwxr-x---   2 root root  4096 Dec 27 09:56 rules.d \n \n/etc/audit/rules.d/: \n\n -rw-r----- 1 root root 244 Dec 27 09:56 audit.rules \n-rw-r----- 1 root root 10357 Dec 27 09:56 stig.rules \n \nIf the \"/etc/audit/audit.rules\", \"/etc/audit/rules.d/*\", or \"/etc/audit/auditd.conf\" file is 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 :root /etc/audit/audit*.{rules,conf} /etc/audit/rules.d/*","ccis":["CCI-000171"]},{"vulnId":"V-270778","ruleId":"SV-270778r1066823_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the su 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 24.04 LTS generates audit records upon successful/unsuccessful attempts to use the \"su\" command with the following command: \n \n$ sudo auditctl -l | grep /bin/su \n-a always,exit -F path=/bin/su -F perm=x -F auid>=1000 -F auid!=-1 -k 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 \"-k\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.","fixText":"Configure Ubuntu 24.04 LTS to generate audit records when successful/unsuccessful attempts to use the \"su\" command occur. \n \nAdd or update the following rules 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!=-1 -k privileged-priv_change  \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270779","ruleId":"SV-270779r1066826_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS generates audit records upon successful/unsuccessful attempts to use the \"chfn\" command with the following command: \n \n$ sudo auditctl -l | grep /usr/bin/chfn \n-a always,exit -F path=/usr/bin/chfn -F perm=x -F auid>=1000 -F auid!=-1 -k 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 \"-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 uses of the \"chfn\" command. \n \nAdd or update the following rules 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!=-1 -k privileged-chfn \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270780","ruleId":"SV-270780r1066829_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS generates audit records upon successful/unsuccessful attempts to use the \"mount\" command with the following command: \n \n$ sudo auditctl -l | grep /usr/bin/mount \n-a always,exit -F path=/usr/bin/mount -F perm=x -F auid>=1000 -F auid!=-1 -k 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 \"-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 \"mount\" command.  \n \nAdd or update the following rules 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!=-1 -k privileged-mount \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270781","ruleId":"SV-270781r1066832_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS generates audit records upon successful/unsuccessful attempts to use the \"umount\" command with the following command: \n \n$ sudo auditctl -l | grep /usr/bin/umount\n-a always,exit -F path=/usr/bin/umount -F perm=x -F auid>=1000 -F auid!=-1 -k 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 \"-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 \"umount\" command.  \n \nAdd or update the following rules 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!=-1 -k privileged-umount \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270782","ruleId":"SV-270782r1066835_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"ssh-agent\" command with the following command: \n \n$ sudo auditctl -l | grep /usr/bin/ssh-agent\n-a always,exit -F path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=-1 -k 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 \"-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 \"ssh-agent\" command.  \n \nAdd or update the following rules 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!=-1 -k privileged-ssh \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270783","ruleId":"SV-270783r1066838_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the ssh-keysign 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 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"ssh-keysign\" command with the following command:\n \n$ sudo auditctl -l | grep ssh-keysign\n-a always,exit -F path=/usr/lib/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=-1 -k 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 \"-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 \"ssh-keysign\" command.  \n \nAdd or update the following rules 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!=-1 -k privileged-ssh \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270784","ruleId":"SV-270784r1068371_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 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 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"setxattr\", \"fsetxattr\", \"lsetxattr\", \"removexattr\", \"fremovexattr\", and \"lremovexattr\" system calls with 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 -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!=-1 -k 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 \nNotes: \n- For 32-bit architectures, only the 32-bit specific output lines from the commands are required. \n- 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 \"setxattr\", \"fsetxattr\", \"lsetxattr\", \"removexattr\", \"fremovexattr\", and \"lremovexattr\" system calls. \n \nAdd or update the following rules 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!=-1 -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!=-1 -k perm_mod \n-a always,exit -F arch=b64 -S setxattr,fsetxattr,lsetxattr,removexattr,fremovexattr,lremovexattr -F auid=0 -k perm_mod  \n \nNote: For 32-bit architectures, only the 32-bit specific entries are required.\n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270785","ruleId":"SV-270785r1068373_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"chown\", \"fchown\", \"fchownat\", and \"lchown\" system calls with 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 -k perm_chng \n-a always,exit -F arch=b64 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=-1 -k 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 \nNotes: \n- For 32-bit architectures, only the 32-bit specific output lines from the commands are required. \n- 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 \"chown\", \"fchown\", \"fchownat\", and \"lchown\" system calls. \n \nAdd or update the following rules 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!=-1 -k perm_chng \n-a always,exit -F arch=b64 -S chown,fchown,fchownat,lchown -F auid>=1000 -F auid!=-1 -k perm_chng \n \nNote: For 32-bit architectures, only the 32-bit specific entries are required.  \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270786","ruleId":"SV-270786r1068375_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"chmod\", \"fchmod\", and \"fchmodat\" system calls with 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 -k perm_chng \n-a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=-1 -k 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 \nNotes: \n- For 32-bit architectures, only the 32-bit specific output lines from the commands are required. \n- 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 \"chmod\", \"fchmod\", and \"fchmodat\" system calls. \n \nAdd or update the following rules 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!=-1 -k perm_chng \n-a always,exit -F arch=b64 -S chmod,fchmod,fchmodat -F auid>=1000 -F auid!=-1 -k perm_chng \n \nNote: For 32-bit architectures, only the 32-bit specific entries are required.  \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270787","ruleId":"SV-270787r1068378_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS generates an audit record upon unsuccessful attempts to use the \"creat\", \"open\", \"openat\", \"open_by_handle_at\", \"truncate\", and \"ftruncate\" system calls with 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 -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!=-1 -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!=-1 -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!=-1 -k 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 \nNotes: \n- For 32-bit architectures, only the 32-bit specific output lines from the commands are required. \n- 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 unsuccessful use of the \"creat\", \"open\", \"openat\", \"open_by_handle_at\", \"truncate\", and \"ftruncate\" system calls.  \n \nAdd or update the following rules 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!=-1 -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!=-1 -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!=-1 -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!=-1 -k perm_access \n \nNote: For 32-bit architectures, only the 32-bit specific entries are required.  \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270788","ruleId":"SV-270788r1066853_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 with the following command:\n \n$ sudo auditctl -l | grep /usr/bin/sudo\n-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=-1 -k 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 \"-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 \"sudo\" command.  \n \nAdd or update the following rules 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!=-1 -k priv_cmd \n   \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270789","ruleId":"SV-270789r1066856_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"sudoedit\" command with the following command: \n \n$ sudo auditctl -l | grep /usr/bin/sudoedit\n-a always,exit -F path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=-1 -k 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 \"-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 \"sudoedit\" command.  \n \nAdd or update the following rules 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!=-1 -k priv_cmd \n   \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270790","ruleId":"SV-270790r1068380_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"chsh\" command with the following command: \n \n$ sudo auditctl -l | grep chsh\n-a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=-1 -k 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 \"-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 update the following rules 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!=-1 -k priv_cmd \n   \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270791","ruleId":"SV-270791r1066862_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"newgrp\" command with the following command:  \n \n$ sudo auditctl -l | grep newgrp\n-a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=-1 -k 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 \"-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 \"newgrp\" command.  \n \nAdd or update the following rules 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!=-1 -k priv_cmd \n   \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270792","ruleId":"SV-270792r1066865_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"chcon\" command with the following command: \n \n$ sudo auditctl -l | grep chcon\n-a always,exit -F path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=-1 -k 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 \"-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 \"chcon\" command.  \n \nAdd or update the following rules 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!=-1 -k perm_chng \n   \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270793","ruleId":"SV-270793r1066868_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"apparmor_parser\" command with the following command: \n \n$ sudo auditctl -l | grep apparmor_parser\n-a always,exit -F path=/sbin/apparmor_parser -F perm=x -F auid>=1000 -F auid!=-1 -k 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 \"-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 \"apparmor_parser\" command.  \n \nAdd or update the following rules 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!=-1 -k perm_chng \n   \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270794","ruleId":"SV-270794r1066871_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"setfacl\" command with the following command: \n \n$ sudo auditctl -l | grep setfacl\n-a always,exit -F path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=-1 -k 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 \"-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 \"setfacl\" command.  \n \nAdd or update the following rules 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!=-1 -k perm_chng \n   \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270795","ruleId":"SV-270795r1066874_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS generates an audit record upon successful/unsuccessful attempts to use the \"chacl\" command with the following command:  \n\n$ sudo audtctl -l | grep chacl\n-a always,exit -F path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=-1 -k 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 \"-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 \"chacl\" command.  \n \nAdd or update the following rules 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!=-1 -k perm_chng \n    \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270796","ruleId":"SV-270796r1066877_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must generate audit records for the use and modification of 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 24.04 LTS generates an audit record upon successful/unsuccessful modifications to the \"faillog\" file with 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\" 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 modifications to the \"faillog\" file.  \n \nAdd or update the following rules 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","ccis":["CCI-000172"]},{"vulnId":"V-270797","ruleId":"SV-270797r1066880_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS generates an audit record when successful/unsuccessful modifications to the \"lastlog\" file occur with 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\" 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 modifications to the \"lastlog\" file.  \n \nAdd or update the following rules 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","ccis":["CCI-000172"]},{"vulnId":"V-270798","ruleId":"SV-270798r1068382_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 that an audit event is generated for any successful/unsuccessful use of the \"passwd\" command with 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 \"-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 uses of the \"passwd\" command.  \n \nAdd or update the following rule 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!=-1 -k privileged-passwd \n   \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270799","ruleId":"SV-270799r1066886_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 that an audit event is generated for any successful/unsuccessful use of the \"unix_update\" command with the following command:  \n \n$ sudo auditctl -l | grep -w unix_update\n-a always,exit -F path=/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=-1 -k 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 \"-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 uses of the \"unix_update\" command.  \n \nAdd or update the following rules 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!=-1 -k privileged-unix-update \n  \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270800","ruleId":"SV-270800r1066889_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 that an audit event is generated for any successful/unsuccessful use of the \"gpasswd\" command with the following command:\n \n$ sudo auditctl -l | grep -w gpasswd\n-a always,exit -F path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=-1 -k 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 \"-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 uses of the \"gpasswd\" command.  \n \nAdd or update the following rules 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!=-1 -k privileged-gpasswd \n   \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270801","ruleId":"SV-270801r1066892_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 that an audit event is generated for any successful/unsuccessful use of the \"chage\" command with the following command: \n \n$ sudo auditctl -l | grep -w chage\n-a always,exit -F path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=-1 -k 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 \"-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 uses of the \"chage\" command.  \n \nAdd or update the following rules 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!=-1 -k privileged-chage \n   \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270802","ruleId":"SV-270802r1066895_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 with the following command: \n \n$ sudo auditctl -l | grep -w usermod\n-a always,exit -F path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=-1 -k 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 \"-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 uses of the \"usermod\" command.  \n \nAdd or update the following rules 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!=-1 -k privileged-usermod \n   \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270803","ruleId":"SV-270803r1066898_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 with the following command: \n \n$ sudo auditctl -l | grep -w crontab\n-a always,exit -F path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=-1 -k 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 \"-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 uses of the \"crontab\" command.  \n \nAdd or update the following rules 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!=-1 -k privileged-crontab \n   \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270804","ruleId":"SV-270804r1066901_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 with the following command: \n  \n$ sudo auditctl -l | grep -w pam_timestamp_check\n-a always,exit -F path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=-1 -k 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 \"-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 uses of the \"pam_timestamp_check\" command.  \n \nAdd or update the following rules 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!=-1 -k privileged-pam_timestamp_check \n   \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270805","ruleId":"SV-270805r1068384_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the init_module and finit_module syscalls.","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-000471-GPOS-00216","checkContent":"Verify Ubuntu 24.04 LTS generates an audit record for any successful/unsuccessful attempts to use the \"init_module\" and \"finit_module\" syscalls with 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 -k module_chng \n-a always,exit -F arch=b64 -S init_module,finit_module -F auid>=1000 -F auid!=-1 -k 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 \nNotes: \n- For 32-bit architectures, only the 32-bit specific output lines from the commands are required. \n- 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 \"init_module\" and \"finit_module\" syscalls.  \n \nAdd or update the following rules 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!=-1 -k module_chng \n-a always,exit -F arch=b64 -S init_module,finit_module -F auid>=1000 -F auid!=-1 -k module_chng \n  \nNote: For 32-bit architectures, only the 32-bit specific entries are required.  \n  \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270806","ruleId":"SV-270806r1068386_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must generate audit records for successful/unsuccessful uses of the delete_module syscall.","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-000477-GPOS-00222","checkContent":"Verify Ubuntu 24.04 LTS generates an audit record for any successful/unsuccessful attempts to use the \"delete_module\" syscall with 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 -k module_chng \n-a always,exit -F arch=b64 -S delete_module -F auid>=1000 -F auid!=-1 -k 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 \nNotes: \n- For 32-bit architectures, only the 32-bit specific output lines from the commands are required. \n- 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 \"delete_module\" syscall.  \n \nAdd or update the following rules 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!=-1 -k module_chng \n-a always,exit -F arch=b64 -S delete_module -F auid>=1000 -F auid!=-1 -k module_chng \n  \nNote: For 32-bit architectures, only the 32-bit specific entries are required.  \n  \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270807","ruleId":"SV-270807r1066910_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS generates audit records for all modifications that affect \"/etc/sudoers\" with 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\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.","fixText":"Configure Ubuntu 24.04 LTS to generate audit records for all modifications that affect \"/etc/sudoers\".  \n\nAdd or update the following rule 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","ccis":["CCI-000172"]},{"vulnId":"V-270808","ruleId":"SV-270808r1067100_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS generates audit records for all modifications that affect \"/etc/sudoers.d\" directory with 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\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.","fixText":"Configure Ubuntu 24.04 LTS to generate audit records for all modifications that affect \"/etc/sudoers.d\" directory.  \n\nAdd or update the following rule 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","ccis":["CCI-000172"]},{"vulnId":"V-270809","ruleId":"SV-270809r1068388_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS generates audit records for any successful/unsuccessful use of \"unlink\", \"unlinkat\", \"rename\", \"renameat\", and \"rmdir\" system calls with 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 \nNotes: \n- For 32-bit architectures, only the 32-bit specific output lines from the commands are required. \n- 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 audit events for any successful/unsuccessful use of \"unlink\", \"unlinkat\", \"rename\", \"renameat\", and \"rmdir\" system calls. \n \nAdd or update the following rules 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!=-1 -k delete \n-a always,exit -F arch=b32 -S unlink,unlinkat,rename,renameat,rmdir -F auid>=1000 -F auid!=-1 -k delete \n\nNote: For 32-bit architectures, only the 32-bit specific entries are required. \n \nTo reload the rules file, issue the following command: \n \n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-270810","ruleId":"SV-270810r1066919_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must generate audit records for the /var/log/wtmp file.","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 24.04 LTS generates audit records showing start and stop times for user access to the system via the \"/var/log/wtmp\" file with 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\" 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 showing start and stop times for user access via the \"/var/log/wtmp\" file. \n \nAdd or update the following rules 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","ccis":["CCI-000172"]},{"vulnId":"V-270811","ruleId":"SV-270811r1066922_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS generates audit records showing start and stop times for user access to the system via the \"/var/run/utmp\" file with 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\" 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 showing start and stop times for user access via the \"/var/run/utmp\" file. \n \nAdd or update the following rules 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","ccis":["CCI-000172"]},{"vulnId":"V-270812","ruleId":"SV-270812r1066925_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 24.04 LTS generates audit records showing start and stop times for user access to the system via the \"/var/log/btmp\" file with 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\" 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 showing start and stop times for user access via the \"/var/log/btmp file\". \n \nAdd or update the following rules 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","ccis":["CCI-000172"]},{"vulnId":"V-270813","ruleId":"SV-270813r1066928_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must generate audit records when 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 if Ubuntu 24.04 LTS 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\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.","fixText":"Configure Ubuntu 24.04 LTS to audit the execution of the module management program \"modprobe\". \n \nAdd or update the following rule 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","ccis":["CCI-000172"]},{"vulnId":"V-270814","ruleId":"SV-270814r1066931_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must generate audit records when 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 24.04 LTS is configured to audit the execution of the module management program \"kmod\" with 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\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.","fixText":"Configure Ubuntu 24.04 LTS to audit the execution of the module management program \"kmod\". \n \nAdd or update the following rule 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","ccis":["CCI-000172"]},{"vulnId":"V-270815","ruleId":"SV-270815r1066934_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must generate audit records when 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 24.04 LTS is configured to audit the execution of the partition management program \"fdisk\" with 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\" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.","fixText":"Configure Ubuntu 24.04 LTS to audit the execution of the partition management program \"fdisk\". \n \nAdd or update the following rule 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","ccis":["CCI-000172"]},{"vulnId":"V-270816","ruleId":"SV-270816r1066937_rule","severity":"low","ruleTitle":"Ubuntu 24.04 LTS must allocate audit record storage capacity to store at least one week's worth of audit records, when audit records are not immediately sent to a central audit record storage facility.","description":"To ensure operating systems have a sufficient storage capacity in which to write the audit logs, operating systems must be able to allocate audit record storage capacity. \n \nThe task of allocating audit record storage capacity is usually performed during initial installation of Ubuntu 24.04 LTS.","checkContent":"Verify Ubuntu 24.04 LTS allocates audit record storage capacity to store at least one week's worth of audit records when audit records are not immediately sent to a central audit record storage facility. \n \nDetermine which partition the audit records are being written to with the following command: \n \n$ sudo grep ^log_file /etc/audit/auditd.conf\nlog_file = /var/log/audit/audit.log \n \nCheck the size of the partition that audit records are written to (with the example being \"/var/log/audit/\") with the following command: \n \n$ sudo df -h /var/log/audit/\n/dev/sda2 24G 10.4G 13.6G 43% /var/log/audit \n \nIf the audit records are not written to a partition made specifically for audit records (\"/var/log/audit\" is a separate partition), determine the amount of space being used by other files in the partition with the following command: \n \n$ sudo du -sh [audit_partition]\n1.8G /var/log/audit \n \nNote: The partition size needed to capture a week's worth of audit records is based on the activity level of the system and the total storage capacity available. \n \nIf the audit record partition is not allocated for sufficient storage capacity, this is a finding.","fixText":"Allocate enough storage capacity for at least one week's worth of audit records when audit records are not immediately sent to a central audit record storage facility. \n \nIf audit records are stored on a partition made specifically for audit records, use the \"parted\" program to resize the partition with sufficient space to contain one week's worth of audit records. \n \nIf audit records are not stored on a partition made specifically for audit records, a new partition with sufficient amount of space will need be to be created. \n \nSet the auditd server to point to the mount point where the audit records must be located: \n \n$ sudo sed -i -E 's@^(log_file\\s*=\\s*).*@\\1 <log mountpoint>/audit.log@' /etc/audit/auditd.conf \n \nwhere <log mountpoint> is the aforementioned mount point.","ccis":["CCI-001849"]},{"vulnId":"V-270817","ruleId":"SV-270817r1066940_rule","severity":"low","ruleTitle":"Ubuntu 24.04 LTS must have a crontab script running weekly to offload audit events of standalone systems.","description":"Information stored in one location is vulnerable to accidental or incidental deletion or alteration. \n \nOffloading is a common process in information systems with limited audit storage capacity.","checkContent":"Note: If this is an interconnected system, this is not applicable.\n \nVerify there is a script that offloads audit data and that script runs weekly with the following command:\n\n$ ls /etc/cron.weekly \naudit-offload \n \nCheck if the script inside the file offloads audit logs to external media. \n \nIf the script file does not exist or does not offload audit logs, this is a finding.","fixText":"Create a script that offloads 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-270818","ruleId":"SV-270818r1066943_rule","severity":"low","ruleTitle":"Ubuntu 24.04 LTS must immediately notify the system administrator (SA) and information system security officer (ISSO) (at a minimum) when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity.","description":"If security personnel are not notified immediately when storage volume reaches 75 percent utilization, they are unable to plan for audit record storage capacity expansion.","checkContent":"Verify Ubuntu 24.04 LTS notifies the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75 percent of the repository maximum audit record storage capacity with the following command: \n \nNote: If the space_left_action is set to \"email\", an email package must be available.\n\n$ sudo grep ^space_left_action /etc/audit/auditd.conf\nspace_left_action email \n \n$ sudo grep ^space_left /etc/audit/auditd.conf\nspace_left 250000 \n \nIf the \"space_left\" parameter is set to \"syslog\", is missing, set to blanks, or set to a value less than 25 percent of the space free in the allocated audit record storage, this is a finding. \n \nIf the \"space_left_action\" parameter is missing or set to blanks, this is a finding. \n\nIf the \"space_left_action\" is set to \"email\", check the value of the \"action_mail_acct\" parameter with the following command: \n \n$ sudo grep ^action_mail_acct /etc/audit/auditd.conf\naction_mail_acct root@localhost \n \nThe \"action_mail_acct\" parameter, if missing, defaults to \"root\". If the \"action_mail_acct parameter\" is not set to the email address of the SA(s) and/or ISSO, this is a finding.   \n \nIf 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":"Edit \"/etc/audit/auditd.conf\" and set the \"space_left_action\" parameter to \"exec\" or \"email\".  \n \nIf the \"space_left_action\" parameter is set to \"email\", set the \"action_mail_acct\" parameter to an email address for the SA and ISSO. \n \nIf the \"space_left_action\" parameter is set to \"exec\", ensure the command being executed notifies the SA and ISSO. \n \nEdit \"/etc/audit/auditd.conf\" and set the \"space_left\" parameter to be at least 25 percent of the repository maximum audit record storage capacity.","ccis":["CCI-001855"]},{"vulnId":"V-270819","ruleId":"SV-270819r1068390_rule","severity":"low","ruleTitle":"Ubuntu 24.04 LTS must alert the system administrator (SA) and information system security officer (ISSO) (at a minimum) 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.","checkContent":"Verify that the SA and ISSO (at a minimum) are notified in the event of an audit processing failure with the following command: \n \n$ sudo grep '^action_mail_acct' /etc/audit/auditd.conf\naction_mail_acct = <administrator_account> \n \nIf the value of the \"action_mail_acct\" keyword is not set to an account for security personnel, the returned line is commented out, or the keyword 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 \nEdit the following line in \"/etc/audit/auditd.conf\" to ensure administrators are notified via email for those situations: \n \naction_mail_acct = <administrator_account> \n \nNote: Change \"administrator_account\" to an account for security personnel. \n \nRestart the \"auditd\" service so the changes take effect: \n \n$ sudo systemctl restart auditd.service","ccis":["CCI-000139"]},{"vulnId":"V-270820","ruleId":"SV-270820r1066949_rule","severity":"low","ruleTitle":"Ubuntu 24.04 LTS must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT).","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 Ubuntu 24.04 LTS include date and time. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC.","checkContent":"Verify the time zone is configured to use UTC or GMT with the following command: \n \n$ timedatectl status | grep -i \"time zone\"\nTime zone: UTC (UTC, +0000) \n \nIf \"Timezone\" is not set to UTC or GMT, this is a finding.","fixText":"To configure the system time zone to use UTC or GMT, run the following command, replacing [ZONE] with UTC or GMT: \n \n$ sudo timedatectl set-timezone [ZONE]","ccis":["CCI-001890"]},{"vulnId":"V-270821","ruleId":"SV-270821r1134818_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must configure audit tools with a mode of \"0755\" 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, roles identifying the user accessing the tools, and the corresponding user rights to make decisions regarding 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-000257-GPOS-00098, SRG-OS-000256-GPOS-00097","checkContent":"Verify Ubuntu 24.04 LTS configures the audit tools to have a file permission of \"0755\" or less to prevent unauthorized access with 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/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 24.04 LTS to be protected from unauthorized access by setting the correct permissive mode using the following command: \n \n$ sudo chmod 0755 [audit_tool] \n \nReplace \"[audit_tool]\" with the audit tool that does not have the correct permissions.","ccis":["CCI-001494","CCI-001493"]},{"vulnId":"V-270822","ruleId":"SV-270822r1134821_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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, roles identifying the user accessing the tools, and the corresponding user rights to make decisions regarding 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-000257-GPOS-00098, SRG-OS-000256-GPOS-00097","checkContent":"Verify Ubuntu 24.04 LTS 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/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 24.04 LTS to be protected from unauthorized access by setting the file owner as root using the following command: \n \n$ sudo chown root [audit_tool] \n \nReplace \"[audit_tool]\" with each audit tool not owned by root.","ccis":["CCI-001494","CCI-001493"]},{"vulnId":"V-270823","ruleId":"SV-270823r1134824_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must configure the audit tools to be 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, roles identifying the user accessing the tools, and the corresponding user rights to make decisions regarding 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-000257-GPOS-00098, SRG-OS-000256-GPOS-00097","checkContent":"Verify Ubuntu 24.04 LTS configures the audit tools to be group owned by root to prevent any unauthorized access with the following command: \n \n$ stat -c \"%n %G\" /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/augenrules root \n \nIf any of the audit tools are not group owned by root, this is a finding.","fixText":"Configure the audit tools on Ubuntu 24.04 LTS to be protected from unauthorized access by setting the file group as root using the following command: \n \n$ sudo chown :root [audit_tool] \n \nReplace \"[audit_tool]\" with each audit tool not group owned by root.","ccis":["CCI-001494","CCI-001493"]},{"vulnId":"V-270824","ruleId":"SV-270824r1066961_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must have directories that contain system commands set to a mode of \"0755\" 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 \"0755\" or less permissive with 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 the system 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-270825","ruleId":"SV-270825r1066964_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 with 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 the system 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-270826","ruleId":"SV-270826r1066967_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 with 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 the system 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-270827","ruleId":"SV-270827r1066970_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 \"0600\" or less permissive. \n \nDetermine where the audit logs are stored with the following command: \n \n$ sudo grep -iw log_file /etc/audit/auditd.conf\nlog_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 \"0600\" or less with 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 \"0600\", this is a finding.","fixText":"Configure the audit log files to have a mode of \"0600\" or less permissive. \n \nDetermine where the audit logs are stored with the following command: \n \n$ sudo grep -iw log_file /etc/audit/auditd.conf \n\nlog_file = /var/log/audit/audit.log \n \nUsing the path of the directory containing the audit logs, configure the audit log files to have a mode of \"0600\" or less permissive by using the following command: \n \n$ sudo chmod 0600 /var/log/audit/*","ccis":["CCI-000162","CCI-000163"]},{"vulnId":"V-270828","ruleId":"SV-270828r1066973_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 with the following command: \n \n$ sudo grep -iw log_file /etc/audit/auditd.conf\nlog_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 with 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 \nDetermine where the audit logs are stored with the following command: \n \n$ sudo grep -iw log_file /etc/audit/auditd.conf \n\nlog_file = /var/log/audit/audit.log \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-270829","ruleId":"SV-270829r1066976_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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.\n\nSatisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029","checkContent":"Verify the group owner is set to own newly created audit logs in the audit configuration file with the following command: \n\n$ sudo grep -iw log_group /etc/audit/auditd.conf\nlog_group = root \n\nIf the value of the \"log_group\" parameter is other than \"root\", this is a finding.\n\nDetermine where the audit logs are stored with the following command: \n\n$ sudo grep -iw log_file /etc/audit/auditd.conf\nlog_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\" group with the following command: \n\n$ sudo stat -c \"%n %G\" /var/log/audit/*\n/var/log/audit/audit.log root \n\nIf the audit log files are owned by a group other than \"root\", this is a finding.","fixText":"Configure the audit log directory and its underlying files to be owned by \"root\" group.\n\nSet the \"log_group\" parameter of the audit configuration file to the \"root\" value so when a new log file is created, its group owner is properly set:\n\n$ sudo sed -i '/^log_group/D' /etc/audit/auditd.conf\n$ sudo sed -i /^log_file/a'log_group = root' /etc/audit/auditd.conf\n\nSignal the audit daemon to reload the configuration file to update the group owners of existing files:\n\n$ sudo systemctl kill auditd -s SIGHUP","ccis":["CCI-000162","CCI-000163","CCI-000164"]},{"vulnId":"V-270830","ruleId":"SV-270830r1068397_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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, Ubuntu 24.04 LTS 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 that the audit log directory has a mode of \"0750\" or less permissive. \n \nDetermine where the audit logs are stored with the following command: \n \n$ sudo grep -iw ^log_file /etc/audit/auditd.conf\nlog_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 \"0750\" or less with 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 \"0750\", this is a finding.","fixText":"Configure the audit log directory to have a mode of \"0750\" or less permissive. \n \nDetermine where the audit logs are stored with the following command: \n \n$ sudo grep -iw ^log_file /etc/audit/auditd.conf \n\nlog_file = /var/log/audit/audit.log \n \nUsing the path of the directory containing the audit logs, configure the audit log directory to have a mode of \"0750\" or less permissive by using the following command: \n \n$ sudo chmod -R  750 /var/log/audit","ccis":["CCI-000164"]},{"vulnId":"V-270831","ruleId":"SV-270831r1135002_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS 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 with the following command: \n \n$ egrep '(\\/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 seven audit tools do not have appropriate selection lines, this is a finding.","fixText":"Add or update the following selection lines for \"/etc/aide/aide.conf\" to protect the integrity of the audit tools: \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-270832","ruleId":"SV-270832r1068399_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS audit system must protect auditing rules from unauthorized change.","description":"Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality. Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit Ubuntu 24.04 LTS system activity. In immutable mode, unauthorized users cannot execute changes to the audit system to potentially hide malicious activity and then put the audit rules back. A system reboot would be noticeable, and a system administrator could then investigate the unauthorized changes.","checkContent":"Verify the audit system prevents unauthorized changes to the rules with the following command:\n\n$ grep -E '^-e 2' /etc/audit/audit.rules\n-e 2\n\nIf the audit system is not set to be immutable by adding the \"-e 2\" option to the end of \"/etc/audit/audit.rules\", this is a finding.","fixText":"Configure the audit system to set the audit rules to be immutable by adding the following line to the end of \"/etc/audit/rules.d/audit.rules\":\n\n-e 2","ccis":["CCI-000163"]},{"vulnId":"V-274868","ruleId":"SV-274868r1107313_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must require users to provide a password for privilege escalation.","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 that the user reauthenticate.\n\nSatisfies: SRG-OS-000373-GPOS-00156, SRG-OS-000373-GPOS-00157, SRG-OS-000373-GPOS-00158","checkContent":"Verify that \"/etc/sudoers\" has no occurrences of \"NOPASSWD\" with the following command:\n\n$ sudo egrep -iR 'NOPASSWD' /etc/sudoers /etc/sudoers.d/\n\nIf any occurrences of \"NOPASSWD\" are returned from the command and have not been documented with the information system security officer (ISSO) as an organizationally defined administrative group using multifactor authentication (MFA), this is a finding.","fixText":"Configure the operating system to not allow users to execute privileged actions without authenticating with a password.\n\nRemove any occurrence of \"NOPASSWD\" found in \"/etc/sudoers\" file or files in the \"/etc/sudoers.d\" directory.\n\n$ sudo find /etc/sudoers /etc/sudoers.d -type f -exec sed -i '/NOPASSWD/ s/^/# /g' {} \\;","ccis":["CCI-000366"]},{"vulnId":"V-274869","ruleId":"SV-274869r1107312_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must restrict privilege elevation to authorized personnel.","description":"If the \"sudoers\" file is not configured correctly, any user defined on the system can initiate privileged actions on the target system.","checkContent":"Verify the operating system restricts privilege elevation to authorized personnel with the following command:\n\n$ sudo grep -iwR 'ALL' /etc/sudoers /etc/sudoers.d/ | grep -v '#'\n\nIf either of the following entries are returned, this is a finding:\nALL     ALL=(ALL) ALL\nALL     ALL=(ALL:ALL) ALL","fixText":"Configure the operating system to restrict privilege elevation to authorized personnel.\n\nRemove the following entries from the /etc/sudoers file or any configuration file under /etc/sudoers.d/:\n\nALL     ALL=(ALL) ALL\nALL     ALL=(ALL:ALL) ALL","ccis":["CCI-002038","CCI-004895"]},{"vulnId":"V-274870","ruleId":"SV-274870r1155243_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must audit any script or executable called by cron as root or by any privileged user.","description":"Any script or executable called by cron as root or by any privileged user must be owned by that user, must have the permissions 755 or more restrictive, and should have no extended rights that allow any nonprivileged user to modify the script or executable.","checkContent":"Verify Ubuntu 24.04 LTS is configured to audit the execution of any system call made by cron as root or as any privileged user.\n\n$ sudo auditctl -l | grep /etc/cron.d\n-w /etc/cron.d -p wa -k cronjobs\n\n$ sudo auditctl -l | grep /var/spool/cron\n-w /var/spool/cron -p wa -k cronjobs\n\nIf either of these commands does not return the expected output, or the lines are commented out, this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to audit the execution of any system call made by cron as root or as any privileged user.\n\nAdd or update the following file system rules to \"/etc/audit/rules.d/audit.rules\":\n-w /etc/cron.d/ -p wa -k cronjobs\n-w /var/spool/cron/ -p wa -k cronjobs\n\nTo load the rules to the kernel immediately, use the following command:\n\n$ sudo augenrules --load","ccis":["CCI-000172"]},{"vulnId":"V-274871","ruleId":"SV-274871r1107302_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must conceal, via the session lock, information previously visible on the display with a publicly viewable image.","description":"Setting the screensaver mode to blank-only conceals the contents of the display from passersby.","checkContent":"Note: This requirement assumes the use of the Ubuntu 24.04 LTS default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable.\n\nTo verify the screensaver is configured to be blank, run the following command:\n\n$ gsettings writable org.gnome.desktop.screensaver picture-uri\n \nfalse\n \nIf \"picture-uri\" is writable and the result is \"true\", this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to prevent a user from overriding the picture-uri setting for graphical user interfaces.\n\nIn the file \"/etc/dconf/db/local.d/00-security-settings\", add or update the following lines:\n\n[org/gnome/desktop/screensaver]\npicture-uri=''\n\nPrevent user modification by adding the following line to \"/etc/dconf/db/local.d/locks/00-security-settings-lock\":\n\n/org/gnome/desktop/screensaver/picture-uri\n\nUpdate the dconf system databases:\n\n$ sudo dconf update","ccis":["CCI-000060"]},{"vulnId":"V-274872","ruleId":"SV-274872r1107297_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must prevent a user from overriding the disabling of the graphical user interface autorun function.","description":"Techniques used to address this include protocols using nonces (e.g., numbers generated for a specific one-time use) or challenges (e.g., TLS, WS_Security). Additional techniques include time-synchronous or challenge-response one-time authenticators.\n\nSatisfies: SRG-OS-000114-GPOS-00059, SRG-OS-000378-GPOS-00163, SRG-OS-000480-GPOS-00227","checkContent":"Note: This requirement assumes the use of the Ubuntu 24.04 LTS default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable.\n\nVerify Ubuntu 24.04 LTS disables ability of the user to override the graphical user interface autorun setting.\n\nDetermine which profile the system database is using with the following command:\n\n$ gsettings writable org.gnome.desktop.media-handling autorun-never\n \nfalse\n \nIf \"autorun-never\" is writable, the result is \"true\". If this is not documented with the information system security officer (ISSO) as an operational requirement, this is a finding.","fixText":"Configure the Ubuntu 24.04 LTS GNOME desktop to not allow a user to change the setting that disables autorun on removable media.\n\nAdd the following line to \"/etc/dconf/db/local.d/locks/00-security-settings-lock\" to prevent user modification:\n\n/org/gnome/desktop/media-handling/autorun-never\n\nUpdate the dconf system databases:\n\n$ sudo dconf update","ccis":["CCI-000778","CCI-001958"]},{"vulnId":"V-274873","ruleId":"SV-274873r1107300_rule","severity":"medium","ruleTitle":"Ubuntu 24.04 LTS must prevent a user from overriding the disabling of the graphical user smart card removal action.","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 24.04 LTS must provide users with the ability to manually invoke a session lock so users can secure their session if it is necessary to temporarily vacate the immediate physical vicinity.\n\nSatisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000030-GPOS-00011","checkContent":"Note: This requirement assumes the use of the Ubuntu 24.04 LTS default graphical user interface, the GNOME desktop environment. If the system does not have any graphical user interface installed, this requirement is Not Applicable.\n\nVerify Ubuntu 24.04 LTS disables the ability of the user to override the smart card removal action setting.\n\n$ gsettings writable org.gnome.settings-daemon.peripherals.smartcard removal-action\n \nfalse\n \nIf \"removal-action\" is writable and the result is \"true\", this is a finding.","fixText":"Configure Ubuntu 24.04 LTS to prevent a user from overriding the disabling of the graphical user smart card removal action.\n\nAdd the following line to \"/etc/dconf/db/local.d/locks/00-security-settings-lock\":\n\n/org/gnome/settings-daemon/peripherals/smartcard/removal-action\n\nUpdate the dconf system databases:\n\n$ sudo dconf update","ccis":["CCI-000056","CCI-000057","CCI-000058"]},{"vulnId":"V-278917","ruleId":"SV-278917r1155246_rule","severity":"high","ruleTitle":"Ubuntu 24.04 LTS must be a vendor-supported release.","description":"An operating system release is considered \"supported\" if the vendor continues to provide security patches for the product. With an unsupported release, it will not be possible to resolve security issues discovered in the system software.\n\nThe support status of the OS depends on its subscription status.  \n\nEnd Of Life dates for Ubuntu 24.04 releases are as follows:\nStandard Support: April 2029\nExtended Security Maintenance (ESM): April 2036\n\nESM is available via an Ubuntu Pro subscription.","checkContent":"Verify the version of Ubuntu 24.04 LTS is vendor supported with the following command:\n\n$ grep DISTRIB_DESCRIPTION /etc/lsb-release\nDISTRIB_DESCRIPTION=\"Ubuntu 24.04.3 LTS\"\n\nCheck the subscription status of the system with the following command:\n$ pro status\n\nIf the installed version of Ubuntu 24.04 LTS is not supported, this is a finding.","fixText":"Upgrade to a supported version of Ubuntu 24.04 LTS.","ccis":["CCI-000366"]},{"vulnId":"V-279938","ruleId":"SV-279938r1156367_rule","severity":"high","ruleTitle":"Ubuntu 24.04 LTS must not have the nfs-kernel-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 \nOperating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). \n \nExamples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled.","checkContent":"Verify Ubuntu 24.04 LTS does not have nfs packages installed.\n\nCheck if packages are installed:\n$sudo dpkg -l | grep -E 'nfs-common | nfs-kernel-server'\n\nIf the nfs-common or nfs-kernel-server packages are installed, this is a finding","fixText":"Configure Ubuntu 24.04 LTS to disable non-essential capabilities by removing the nfs-common and nfs-kernel-server packages from the system with the following commands:\n\nRemove packages if present:\n$ sudo apt purge --yes nfs-common nfs-kernel-server\n\nRemove any unneeded dependencies\n$ sudo apt autoremove --yes\n\nVerify NFS services are gone:\n$ sudo systemctl list-units --type=service | grep nfs","ccis":["CCI-000381"]}]}