harbian-audit/docs/STIG-Benchmark/stig-Ubuntu_16-04_LTS.txt

Rule ID: SV-90069r1_rule
Severity: high
Rule Title: The Ubuntu operating system must be a vendor supported release.
Description: An Ubuntu 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.
Check_content: Verify the version of the Ubuntu operating system is vendor supported.\n\nCheck the version of the Ubuntu operating system with the following command:\n\n# cat /etc/lsb-release\n\nDISTRIB_RELEASE=16.04\nDISTRIB_CODENAME=xenial\nDISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"\n\nCurrent End of Life for Ubuntu 16.04 LTS is April 2021.\n\nIf the release is not supported by the vendor, this is a finding.
Fixtext: Upgrade to a supported version of the Ubuntu operating system.

Rule ID: SV-90071r5_rule
Severity: medium
Rule Title: Ubuntu vendor packaged system security patches and updates must be installed and up to date.
Description: Timely patching is critical for maintaining the operational availability, confidentiality, and integrity of information technology (IT) systems. However, failure to keep Ubuntu operating system and application software patched is a common mistake made by IT professionals. New patches are released daily, and it is often difficult for even experienced System Administrators to keep abreast of all the new patches. When new weaknesses in an Ubuntu operating system exist, patches are usually made available by the vendor to resolve the problems. If the most recent security patches and updates are not installed, unauthorized users may take advantage of weaknesses in the unpatched software. The lack of prompt attention to patching could result in a system compromise.
Check_content: Verify the Ubuntu operating system security patches and updates are installed and up to date. Updates are required to be applied with a frequency determined by the site or Program Management Office (PMO). \n\nObtain the list of available package security updates from Ubuntu. The URL for updates is https://www.Ubuntu.com/usn/. It is important to note that updates provided by Ubuntu may not be present on the system if the underlying packages are not installed.\n\nCheck that the available package security updates have been installed on the system with the following command:\n\n# /usr/lib/update-notifier/apt-check --human-readable\n\n246 packages can be updated.\n0 updates are security updates.\n\nIf security package updates have not been performed on the system within the timeframe that the site/program documentation requires, this is a finding. \n\nTypical update frequency may be overridden by Information Assurance Vulnerability Alert (IAVA) notifications from JFHQ-DoDIN.\n\nIf the Ubuntu operating system is in non-compliance with the Information Assurance Vulnerability Management (IAVM) process, this is a finding.
Fixtext: Install the Ubuntu operating system patches or updated packages available from Canonical within 30 days or sooner as local policy dictates.

Rule ID: SV-90073r3_rule
Severity: medium
Rule Title: The Ubuntu operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a graphical user logon.
Description: Display of a standardized and approved use notification before granting access to the Ubuntu 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 Ubuntu 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 Ubuntu operating systems that have severe limitations on the number of characters that can be displayed in the banner:\n\n"I\'ve read & consent to terms in IS user agreem\'t."\n\n
Check_content: Verify the Ubuntu operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the Ubuntu operating system via a Gnome graphical user logon. \n\nNote: If the system does not have a graphical user logon this item is Not Applicable. \n\nNote: If the system is using lightdm, this is a finding.  There is no greater configuration that can be applied to meet the requirement. \n\nCheck that the Ubuntu operating system displays a banner at the logon screen with the following command:\n\n# grep banner-message-enable /etc/dconf/db/local.d/*\nbanner-message-enable=true\n\nIf "banner-message-enable" is not set to "true", is missing, set to "false", or is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system.\n\nCreate a database that will contain the system wide graphical user logon settings (if it does not already exist) with the following command:\n\n# sudo touch /etc/dconf/db/local.d/01-banner-message\n\nAdd the following line to the "[org/gnome/login-screen]" section of the "/etc/dconf/db/local.d/01-banner-message" file:\n\n[org/gnome/login-screen]\nbanner-message-enable=true

Rule ID: SV-90115r3_rule
Severity: medium
Rule Title: The Ubuntu operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a command line user logon.
Description: Display of a standardized and approved use notification before granting access to the Ubuntu 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 Ubuntu operating systems:\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."
Check_content: [u'Verify the Ubuntu operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the Ubuntu operating system via a command line user logon.\n\nCheck that the Ubuntu operating system displays a banner at the command line login screen with the following command:\n\n# cat /etc/issue\n\nIf the banner is set correctly it will return the following text:\n\n\u201cYou 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.\u201d\n\nIf the banner text does not match the Standard Mandatory DoD Notice and Consent Banner exactly, this is a finding.
Fixtext: Configure the Ubuntu operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system via command line logon.\n\nEdit the "/etc/issue" file to replace the default text 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."

Rule ID: SV-90117r3_rule
Severity: medium
Rule Title: The Ubuntu operating system must enable a user session lock until that user re-establishes access using established identification and authentication procedures.
Description: A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence.\n\nThe session lock is implemented at the point where session activity can be determined.\n\nRegardless of where the session lock is determined and implemented, once invoked, the session lock shall remain in place until the user re-authenticates. No other activity aside from re-authentication shall unlock the system.
Check_content: Verify the operating system allows a user to lock the current graphical user interface (GUI) session. \n\nNote: If the Ubuntu operating system does not have GNOME installed, this requirement is Not Applicable.\n\nCheck to see if the Ubuntu operating system allows the user to lock the current GUI session with the following command:\n\n# gsettings get org.gnome.desktop.lock-enabled\n\ntrue\n\nIf "lock-enabled" is not set to "true", this is a finding.
Fixtext: Configure the Ubuntu operating system so that it allows a user to lock the current GUI session.\n\nNote: If the Ubuntu operating system does not have GNOME installed, this requirement is Not Applicable.\n\nSet the "lock-enabled" setting in GNOME to allow GUI session locks with the following command: \n\nNote: The command must be performed from a terminal window inside the graphical user interface (GUI).\n\n# sudo gsettings set org.gnome.desktop.lock-enabled true

Rule ID: SV-90119r2_rule
Severity: medium
Rule Title: All users must be able 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 operating systems need to provide users with the ability to manually invoke a session lock so users may secure their session should the need arise for them to temporarily vacate the immediate physical vicinity.\n\n
Check_content: Verify the Ubuntu operating system has the \'vlock\' package installed, by running the following command:\n\n# dpkg -l | grep vlock\n\nvlock_2.2.2-7\n\nIf "vlock" is not installed, this is a finding.
Fixtext: Install the "vlock" (if it is not already installed) package by running the following command:\n\n# sudo apt-get install vlock

Rule ID: SV-90121r2_rule
Severity: medium
Rule Title: Ubuntu operating system sessions must be automatically logged out after 15 minutes of inactivity.
Description: An Ubuntu operating system needs to be able to identify when a user's sessions has idled for longer than 15 minutes. The Ubuntu operating system must logout a users' session after 15 minutes to prevent anyone from gaining access to the machine while the user is away.
Check_content: Verify the Ubuntu operating system initiates a session logout after a "15" minutes of inactivity. \n\nCheck that the proper auto logout script exists with the following command:\n\n# cat /etc/profile.d/autologout.sh\nTMOUT=900\nreadonly TMOUT\nexport TMOUT\n\nIf the file "/etc/profile.d/autologout.sh" does not exist, the timeout values are commented out, the output from the function call are not the same, this is a finding.
Fixtext: Configure the Ubuntu operating system to initiate a session logout after a "15" minutes of inactivity. \n\nCreate a file to contain the system-wide session auto logout script (if it does not already exist) with the following command:\n\n# sudo touch /etc/profile.d/autologout.sh\n\nAdd the following lines to the "/etc/profile.d/autologout.sh" script:\n\nTMOUT=900\nreadonly TMOUT\nexport TMOUT

Rule ID: SV-90123r2_rule
Severity: low
Rule Title: The Ubuntu operating system must limit the number of concurrent sessions to ten for all accounts and/or account types.
Description: Ubuntu operating system management includes the ability to control the number of users and user sessions that utilize an Ubuntu operating system. Limiting the number of allowed users and sessions per user is helpful in reducing the risks related to 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 should be defined based upon mission needs and the operational environment for each system.
Check_content: Verify that the Ubuntu operating system limits the number of concurrent sessions to "10" for all accounts and/or account types by running the following command:\n\n# grep maxlogins /etc/security/limits.conf\n\nThe result must contain the following line:\n\n* hard maxlogins 10\n\nIf the "maxlogins" item is missing or the value is not set to "10" or less, or is commented out,  this is a finding.
Fixtext: Configure the Ubuntu operating system to limit the number of concurrent sessions to ten for all accounts and/or account types.\n\nAdd the following line to the top of the /etc/security/limits.conf:\n\n* hard maxlogins 10

Rule ID: SV-90125r3_rule
Severity: medium
Rule Title: The Ubuntu operating system must prevent direct login into the root account.
Description: To assure individual accountability and prevent unauthorized access, organizational users must be individually identified and authenticated.\n\nA group authenticator is a generic account used by multiple individuals. Use of a group authenticator alone does not uniquely identify individual users. Examples of the group authenticator is the UNIX OS "root" user account, the Windows "Administrator" account, the "sa" account, or a "helpdesk" account.\n\nFor example, the UNIX and Windows operating systems offer a \'switch user\' capability allowing users to authenticate with their individual credentials and, when needed, \'switch\' to the administrator role. This method provides for unique individual authentication prior to using a group authenticator.\n\nUsers (and any processes acting on behalf of users) 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 the Ubuntu operating system without identification or authentication.\n\nRequiring individuals to be authenticated with an individual authenticator prior to using a group authenticator allows for traceability of actions, as well as adding an additional level of protection of the actions that can be taken with group account knowledge.
Check_content: Verify the Ubuntu operating system prevents direct logins to the root account.\n\nCheck that the Ubuntu operating system prevents direct logins to the root account with the following command:\n\n#  grep root /etc/shadow \n\nroot L 11/11/2017 0 99999 7 -1  \n\nIf any output is returned and the second field is not an "L", this is a finding.
Fixtext: Configure the Ubuntu operating system to prevent direct logins to the root account.\n\nRun the following command to lock the root account:\n\n# passwd -l root

Rule ID: SV-90129r3_rule
Severity: medium
Rule Title: The Ubuntu operating system must enforce password complexity by requiring that at least one upper-case 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.
Check_content: Verify the Ubuntu operating system enforces password complexity by requiring that at least one upper-case character be used.\n\nDetermine if the field "ucredit" is set in the "/etc/security/pwquality.conf" or "/etc/pwquality.conf.d/*.conf" files with the following command:\n\n# grep -i "ucredit" /etc/security/pwquality.conf /etc/pwquality.conf.d/*.conf\nucredit=-1\n\nIf the "ucredit" parameter is not equal to "-1", or is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to enforce password complexity by requiring that at least one upper-case character be used.\n\nAdd or update the following line in the "/etc/security/pwquality.conf" file or a configuration file in the /etc/pwquality.conf.d/ directory to contain the "ucredit" parameter:\n\nucredit=-1

Rule ID: SV-90131r3_rule
Severity: medium
Rule Title: The Ubuntu operating system must enforce password complexity by requiring that at least one lower-case 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.
Check_content: Verify the Ubuntu operating system enforces password complexity by requiring that at least one lower-case character be used.\n\nDetermine if the field "lcredit" is set in the "/etc/security/pwquality.conf" or "/etc/pwquality.conf.d/*.conf" files with the following command:\n\n# grep -i "lcredit" /etc/security/pwquality.conf /etc/pwquality.conf.d/*.conf\nlcredit=-1\n\nIf the "lcredit" parameter is not equal to "-1", or is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to enforce password complexity by requiring that at least one lower-case character be used.\n\nAdd or update the following line in the "/etc/security/pwquality.conf" file or a configuration file in the /etc/pwquality.conf.d/ directory to contain the "lcredit" parameter:\n\nlcredit=-1

Rule ID: SV-90133r3_rule
Severity: medium
Rule Title: The Ubuntu operating system 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.
Check_content: Verify the Ubuntu operating system 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" or "/etc/pwquality.conf.d/*.conf" files with the following command:\n\n# grep -i "dcredit" /etc/security/pwquality.conf etc/pwquality.conf.d/*.conf\ndcredit=-1\n\nIf the "dcredit" parameter is not equal to "-1", or is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to enforce password complexity by requiring that at least one numeric character be used.\n\nAdd or update the following line in the "/etc/security/pwquality.conf" file or a configuration file in the /etc/pwquality.conf.d/ directory to contain the "dcredit" parameter:\n\ndcredit=-1

Rule ID: SV-90135r3_rule
Severity: medium
Rule Title: All passwords must contain at least one special character.
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: ~ ! @ # $ % ^ *.
Check_content: Verify the Ubuntu operating system enforces password complexity by requiring that at least one special character be used.\n\nDetermine if the field "ocredit" is set in the "/etc/security/pwquality.conf" file or "/etc/pwquality.conf.d/*.conf" files with the following command:\n\n# grep -i "ocredit" /etc/security/pwquality.conf /etc/pwquality.conf.d/*.conf\nocredit=-1\n\nIf the "ocredit" parameter is not equal to "-1", or is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system 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 or a configuration file in the /etc/pwquality.conf.d/ directory to contain the "ocredit" parameter:\n\nocredit=-1

Rule ID: SV-90137r3_rule
Severity: medium
Rule Title: The Ubuntu operating system must require the change of at least 8 characters when passwords are changed.
Description: If the Ubuntu operating system allows the user to consecutively reuse extensive portions of passwords, this increases the chances of password compromise by increasing the window of opportunity for attempts at guessing and brute-force attacks.\n\nThe number of changed characters refers to the number of changes required with respect to the total number of positions in the current password. In other words, characters may be the same within the two passwords; however, the positions of the like characters must be different.\n\nIf the password length is an odd number then number of changed characters must be rounded up. For example, a password length of 15 characters must require the change of at least 8 characters.
Check_content: Verify the Ubuntu operating system requires the change of at least "8" characters when passwords are changed.\n\nDetermine if the field "difok" is set in the "/etc/security/pwquality.conf" or "/etc/pwquality.conf.d/*.conf" files with the following command:\n\n# grep -i "difok" /etc/security/pwquality.conf /etc/pwquality.conf.d/*.conf\ndifok=8\n\nIf the "difok" parameter is less than "8", or is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to require the change of at least "8" characters when passwords are changed.\n\nAdd or update the following line in the "/etc/security/pwquality.conf" or "/etc/pwquality.conf.d/*.conf" files to include the "difok=8" parameter:\n\ndifok=8

Rule ID: SV-90139r1_rule
Severity: medium
Rule Title: The Ubuntu operating system must encrypt all stored passwords with a FIPS 140-2 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.\n\nUnapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised.\n\nFIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets DoD requirements.\n\n
Check_content: Verify that the shadow password suite configuration is set to encrypt password with a FIPS 140-2 approved cryptographic hashing algorithm.\n\nCheck the hashing algorithm that is being used to hash passwords with the following command:\n\n# cat /etc/login.defs | grep -i crypt\n\nENCRYPT_METHOD SHA512\n\nIf "ENCRYPT_METHOD" does not equal SHA512 or greater, this is a finding.
Fixtext: Configure the Ubuntu operating system 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

Rule ID: SV-90141r1_rule
Severity: medium
Rule Title: The Ubuntu operating system must employ a FIPS 140-2 approved cryptographic hashing algorithms for all stored passwords.
Description: The system must use a strong hashing algorithm to store the password. The system must use a sufficient number of hashing rounds to ensure the required level of entropy.\n\nPasswords 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.\n\n
Check_content: Verify the shadow password suite configuration is set to encrypt interactive user passwords using a strong cryptographic hash with the following command:\n\nConfirm that the interactive user account passwords are using a strong password hash with the following command:\n\n# sudo cut -d: -f2 /etc/shadow\n\n$6$kcOnRq/5$NUEYPuyL.wghQwWssXRcLRFiiru7f5JPV6GaJhNC2aK5F3PZpE/BCCtwrxRc/AInKMNX3CdMw11m9STiql12f/\n\nPassword hashes "!" or "*" indicate inactive accounts not available for logon and are not evaluated. If any interactive user password hash does not begin with "$6", this is a finding.
Fixtext: Configure the Ubuntu operating system to encrypt all stored passwords with a strong cryptographic hash.\n\nLock all interactive user accounts not using SHA-512 hashing until the passwords can be regenerated.

Rule ID: SV-90143r2_rule
Severity: medium
Rule Title: The Ubuntu operating system must employ FIPS 140-2 approved cryptographic hashing algorithms for all created passwords.
Description: The system must use a strong hashing algorithm to store the password. The system must use a sufficient number of hashing rounds to ensure the required level of entropy.\n\nPasswords 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.\n\n
Check_content: Verify the shadow password suite configuration is set to create passwords using a strong cryptographic hash with the following command:\n\nCheck that a minimum number of hash rounds is configured by running the following command:\n\n# grep rounds /etc/pam.d/common-password\n\npassword  [success=1 default=ignore]  pam_unix.so obscure sha512 rounds=5000\n\nIf "rounds" has a value below "5000", or is commented out, this is a finding.\n
Fixtext: Configure the Ubuntu operating system to encrypt all stored passwords with a strong cryptographic hash.\n\nEdit/modify the following line in the "/etc/pam.d/common-password" file and set "rounds" to a value no lower than "5000":\n\npassword  [success=1 default=ignore]  pam_unix.so obscure sha512 rounds=5000

Rule ID: SV-90145r2_rule
Severity: medium
Rule Title: The pam_unix.so module must use a FIPS 140-2 approved cryptographic hashing algorithm for system authentication.
Description: Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised.\n\nUbuntu operating systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules. \n\nFIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets DoD requirements. This allows for Security Levels 1, 2, 3, or 4 for use on a general purpose computing system.
Check_content: Verify that pam_unix.so auth is configured to use sha512.\n\nCheck that pam_unix.so auth is configured to use sha512 with the following command:\n\n# grep password /etc/pam.d/common-password | grep pam_unix\n\npassword        [success=1 default=ignore]      pam_unix.so obscure sha512\n\nIf "sha512" is not an option of the output, or is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to use a FIPS 140-2 approved cryptographic hashing algorithm for system authentication.\n\nEdit/modify the following line in the file "/etc/pam.d/common-password" file to include the sha512 option for pam_unix.so:\n\npassword        [success=1 default=ignore]      pam_unix.so obscure sha512 shadow remember=5

Rule ID: SV-90149r1_rule
Severity: medium
Rule Title: Emergency administrator accounts must never be automatically removed or disabled.
Description: Emergency accounts are privileged accounts that are established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability. \n\nEmergency accounts are different from infrequently used accounts (i.e., local logon accounts used by the organization's system administrators when network or normal logon/access is not available). Infrequently used accounts are not subject to automatic termination dates. Emergency accounts are accounts created in response to crisis situations, usually for use by maintenance personnel. The automatic expiration or disabling time period may be extended as needed until the crisis is resolved; however, it must not be extended indefinitely. A permanent account should be established for privileged users who need long-term maintenance accounts.\n\nTo address access requirements, many Ubuntu operating systems can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.
Check_content: Verify the Ubuntu operating system is configured such that the emergency administrator account is never automatically removed or disabled. \n\nCheck to see if the root account password or account expires with the following command:\n\n# sudo chage -l root\n\nPassword expires :never\n\nIf "Password expires" or "Account expires" is set to anything other than "never", this is a finding.
Fixtext: Replace "[Emergency_Administrator]" in the following command with the correct emergency administrator account. Run the following command as an administrator:\n\n# sudo chage -I -1 -M 99999 [Emergency_Administrator]

Rule ID: SV-90151r2_rule
Severity: medium
Rule Title: 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.
Check_content: Verify that the Ubuntu operating system enforces a 24 hours/1 day minimum password lifetime for new user accounts by running the following command:\n\n# grep -i pass_min_days /etc/login.defs\n\nPASS_MIN_DAYS    1\n\nIf the "PASS_MIN_DAYS" parameter value is less than or equal to "1", or commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system 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

Rule ID: SV-90153r2_rule
Severity: medium
Rule Title: 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 the Ubuntu operating system does not limit the lifetime of passwords and force users to change their passwords, there is the risk that the Ubuntu operating system passwords could be compromised.
Check_content: Verify that the Ubuntu operating system enforces a 60-day maximum password lifetime for new user accounts by running 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 commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system 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

Rule ID: SV-90155r2_rule
Severity: medium
Rule Title: Passwords must be prohibited from reuse for a minimum of five generations.
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 as per policy requirements.
Check_content: Verify that the Ubuntu operating system prevents passwords from being reused for a minimum of five generations by running the following command:\n\n# grep -i remember /etc/pam.d/common-password\n\npassword [success=1 default=ignore]      pam_unix.so obscure sha512 remember=5 rounds=5000\n\nIf the "remember" parameter value is not greater than or equal to "5", is commented out, or is not set at all this is a finding.
Fixtext: Configure the Ubuntu operating system prevents passwords from being reused for a minimum of five generations.\n\nAdd or modify the "remember" parameter value to the following line in "/etc/pam.d/common-password" file:\n\npassword [success=1 default=ignore]      pam_unix.so obscure sha512 remember=5 rounds=5000

Rule ID: SV-90157r3_rule
Severity: medium
Rule Title: Passwords must have a minimum of 15-characters.
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.
Check_content: Verify that the Ubuntu operating system enforces a minimum "15" character password length.\n\nDetermine if the field "minlen" is set in the "/etc/security/pwquality.conf" or "/etc/pwquality.conf.d/*.conf" files with the following command:\n\n# grep -i minlen /etc/security/pwquality.conf /etc/pwquality.conf.d/*.conf\nminlen=15\n\nIf "minlen" parameter value is not "15" or higher, or is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to enforce a minimum 15-character password length.\n\nAdd or update the following line in the "/etc/security/pwquality.conf" file or a configuration file in the /etc/pwquality.conf.d/ directory to contain the "minlen" parameter:\n\nminlen=15

Rule ID: SV-90159r1_rule
Severity: high
Rule Title: The Ubuntu operating system 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 should never be used in operational environments.
Check_content: To verify that null passwords cannot be used, run the following command: \n\n# grep pam_unix.so /etc/pam.d/* | grep nullok\nIf this produces any output, it may be possible to log on with accounts with empty passwords.\n\nIf null passwords can be used, this is a finding.
Fixtext: If an account is configured for password authentication but does not have an assigned password, it may be possible to log on to the account without authenticating.\n\nRemove any instances of the "nullok" option in files under "/etc/pam.d/" to prevent logons with empty passwords.

Rule ID: SV-90161r4_rule
Severity: medium
Rule Title: The Ubuntu operating system must prevent the use of dictionary words for passwords.
Description: If the Ubuntu operating system allows the user to select passwords based on dictionary words, this increases the chances of password compromise by increasing the opportunity for successful guesses and brute-force attacks.
Check_content: Verify the Ubuntu operating system prevents the use of dictionary words for passwords.\n\nDetermine if the field "dictcheck" is set in the "/etc/security/pwquality.conf" or "/etc/pwquality.conf.d/*.conf" files with the following command:\n\n# grep dictcheck /etc/security/pwquality.conf /etc/pwquality.conf.d/*.conf\n\ndictcheck=1\n\nIf the "dictcheck" parameter is not set to "1", or is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to prevent the use of dictionary words for passwords.\n\nAdd or update the following line in the "/etc/security/pwquality.conf" file or a configuration file in the /etc/pwquality.conf.d/ directory to contain the "dictcheck" parameter:\n\ndictcheck=1

Rule ID: SV-90163r1_rule
Severity: medium
Rule Title: The passwd command must be configured to prevent the use of dictionary words as passwords.
Description: If the Ubuntu operating system allows the user to select passwords based on dictionary words, this increases the chances of password compromise by increasing the opportunity for successful guesses and brute-force attacks.
Check_content: Verify the "passwd" command uses the common-password settings.\n\nCheck that the "passwd" command uses the common-password option with the following command:\n\n# grep common-password /etc/pam.d/passwd\n\n@ include common-password\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to prevent the use of dictionary words for passwords. \n\nEdit the file "/etc/pam.d/passwd" and add the following line: \n\n@ include common-password

Rule ID: SV-90165r3_rule
Severity: medium
Rule Title: Account identifiers (individuals, groups, roles, and devices) must disabled 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\nUbuntu operating systems need to track periods of inactivity and disable application identifiers after 35 days of inactivity.
Check_content: 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# sudo grep -i inactive /etc/default/useradd\n\nINACTIVE=35\n\nIf "INACTIVE" is not set to a value "0<[VALUE]<=35", or is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to disable account identifiers after 35 days of inactivity after the password expiration. \n\nRun the following command to change the configuration for useradd:\n\n# sudo useradd -D -f 35\n\nDoD recommendation is 35 days, but a lower value is acceptable. The value "-1" will disable this feature, and "0" will disable the account immediately after the password expires.

Rule ID: SV-90167r3_rule
Severity: medium
Rule Title: The Ubuntu operating system must automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts.
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\n
Check_content: Verify the Ubuntu operating system automatically locks an account until the account lock is released by an administrator when three unsuccessful logon attempts are made.\n\nCheck that the Ubuntu operating system automatically locks an account after three unsuccessful attempts with the following command:\n\n# grep pam_tally /etc/pam.d/common-auth\n\nauth required pam_tally2.so onerr=fail deny=3\n\nIf "onerr=fail deny=3" is not used in "/etc/pam.d/common-auth" or is called with "unlock_time", this is a finding.
Fixtext: Configure the Ubuntu operating system to automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts are made by appending the following line to the "/etc/pam.d/common-auth file":\n\n"auth required pam_tally2.so onerr=fail deny=3"

Rule ID: SV-90169r2_rule
Severity: medium
Rule Title: The Ubuntu operating system must require users to re-authenticate for privilege escalation and changing roles.
Description: Without re-authentication, users may access resources or perform tasks for which they do not have authorization. \n\nWhen Ubuntu operating systems provide the capability to escalate a functional capability or change security roles, it is critical the user re-authenticate.\n\n
Check_content: Verify that "/etc/sudoers" has no occurrences of "NOPASSWD" or "!authenticate".\n\nCheck that the "/etc/sudoers" file has no occurrences of "NOPASSWD" or "!authenticate" by running the following command:\n\n# sudo egrep -i \'(nopasswd|!authenticate)\' /etc/sudoers /etc/sudoers.d/*\n\n%wheel ALL=(ALL) NOPASSWD: ALL\n\nIf any occurrences of "NOPASSWD" or "!authenticate" return from the command, this is a finding.
Fixtext: Remove any occurrence of "NOPASSWD" or "!authenticate" found in "/etc/sudoers" file or files in the "/etc/sudoers.d" directory.

Rule ID: SV-90171r1_rule
Severity: medium
Rule Title: Temporary user accounts must be provisioned with an expiration time of 72 hours or less.
Description: If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of all temporary accounts must be set upon account creation.\n\nTemporary accounts are established as part of normal account activation procedures when there is a need for short-term accounts without the demand for immediacy in account activation.\n\nIf temporary accounts are used, the Ubuntu operating system must be configured to automatically terminate these types of accounts after a DoD-defined time period of 72 hours.\n\nTo address access requirements, many Ubuntu operating systems may be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.
Check_content: Verify that temporary accounts have been provisioned with an expiration date for 72 hours.\n\nFor every existing temporary account, run the following command to obtain its account expiration information.\n\n# sudo chage -l system_account_name\n\nVerify each of these accounts has an expiration date set within 72 hours.\nIf any temporary accounts have no expiration date set or do not expire within 72 hours, this is a finding.
Fixtext: If a temporary account must be created configure the system to terminate the account after a 72 hour time period with the following command to set an expiration date on it. Substitute "system_account_name" with the account to be created.\n\n# sudo chage -E `date -d "+3 days" +%Y-%m-%d` system_account_name

Rule ID: SV-90173r1_rule
Severity: medium
Rule Title: The Ubuntu operating system must enforce a delay of at least 4 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.
Check_content: Verify the Ubuntu operating system enforces a delay of at least 4 seconds between logon prompts following a failed logon attempt.\n\nCheck that the Ubuntu operating system enforces a delay of at least 4 seconds between logon prompts with the following command:\n\n# grep pam_faildelay /etc/pam.d/common-auth*\n\nauth required pam_faildelay.so delay=4000000\n\nIf the line is not present, or is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to enforce a delay of at least 4 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

Rule ID: SV-90175r3_rule
Severity: high
Rule Title: Unattended or automatic login via the GUI must not be allowed.
Description: Failure to restrict system access to authenticated users negatively impacts Ubuntu operating system security.
Check_content: Verify that unattended or automatic login via the GUI is disabled.\n\nCheck that unattended or automatic login is disabled with the following command:\n\n# sudo grep -i autologin-user /etc/lightdm/lightdm.conf\n\nautologin-user=<username>\nautologin-user-timeout=0\n\nIf the "autologin-user" parameter is blank, or is commented out, this is a finding.\nIf the "autologin-user-timeout" parameter is not 0, or is commented out, this is a finding.\n
Fixtext: Configure the GUI to not allow unattended or automatic login to the system.\n\nComment the following lines in "/etc/lightdm/lightdm.conf" file:\n\n#autologin-user=<username>\n#autologin-user-timeout=0

Rule ID: SV-90177r1_rule
Severity: low
Rule Title: The Ubuntu operating system must display the date and time of the last successful account logon upon logon.
Description: Providing users with feedback on when account accesses last occurred facilitates user recognition and reporting of unauthorized account use.
Check_content: Verify users are provided with feedback on when account accesses last occurred.\n\nCheck that "pam_lastlog" is used and not silent with the following command:\n\n# grep pam_lastlog /etc/pam.d/login\n\nsession required pam_lastlog.so showfailed\n\nIf "pam_lastlog" is missing from "/etc/pam.d/login" file, or the "silent" option is present, this is a finding.
Fixtext: Configure the Ubuntu operating system to provide users with feedback on when account accesses last occurred by setting the required configuration options in "/etc/pam.d/postlogin-ac". \n\nAdd the following line to the top of "/etc/pam.d/login":\n\nsession required pam_lastlog.so showfailed

Rule ID: SV-90179r1_rule
Severity: high
Rule Title: There must be no .shosts files on the Ubuntu operating system.
Description: The .shosts files are used to configure host-based authentication for individual users or the system via SSH. Host-based authentication is not sufficient for preventing unauthorized access to the system, as it does not require interactive identification and authentication of a connection request, or for the use of two-factor authentication.
Check_content: Verify there are no ".shosts" files on the Ubuntu operating system.\n\nCheck the system for the existence of these files with the following command:\n\n# sudo find / -name \'*.shosts\'\n\nIf any ".shosts" files are found, this is a finding.
Fixtext: Remove any found ".shosts" files from the Ubuntu operating system.\n\n# rm /[path]/[to]/[file]/.shosts

Rule ID: SV-90181r2_rule
Severity: high
Rule Title: There must be no shosts.equiv files on the Ubuntu operating system.
Description: The shosts.equiv files are used to configure host-based authentication for the system via SSH. Host-based authentication is not sufficient for preventing unauthorized access to the system, as it does not require interactive identification and authentication of a connection request, or for the use of two-factor authentication.
Check_content: Verify there are no "shosts.equiv" files on the Ubuntu operating system.\n\nCheck for the existence of these files with the following command:\n\n# find / -name shosts.equiv\n\nIf a "shosts.equiv" file is found, this is a finding.
Fixtext: Remove any found "shosts.equiv" files from the Ubuntu operating system.\n\n# rm /etc/ssh/shosts.equiv

Rule ID: SV-90183r2_rule
Severity: high
Rule Title: The Ubuntu operating system must implement NSA-approved cryptography to protect classified information 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. The Ubuntu operating system must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated.\n\n
Check_content: Verify the system is configured to run in FIPS mode.\n\nCheck that 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 the Ubuntu operating systems install.\n\nNote: Enabling a FIPS mode on a pre-existing system involves a number of modifications to the Ubuntu operating system. Refer to the Ubuntu Server 16.04 FIPS 140-2 security policy document for instructions. A subscription to the "Ubuntu Advantage" plan is required in order to obtain the FIPS Kernel cryptographic modules and enable FIPS.

Rule ID: SV-90185r3_rule
Severity: high
Rule Title: Ubuntu operating systems booted with a BIOS 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. Successful 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.
Check_content: [u'Verify that an encrypted root password is set. This is only applicable on systems that use a basic Input/Output System BIOS.\n\nRun the following command to verify the encrypted password is set:\n\n# grep \u2013i password /boot/grub/grub.cfg\n\npassword_pbkdf2 root grub.pbkdf2.sha512.10000.MFU48934NJA87HF8NSD34493GDHF84NG\n\nIf the root password entry does not begin with \u201cpassword_pbkdf2\u201d, 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\ngrub.pbkdf2.sha512.10000.MFU48934NJD84NF8NSD39993JDHF84NG\n\n\nIt will generate a long password encrypted like this:\ngrub.pbkdf2.sha512.10000.FC58373BCA15A797C418C1EA7FFB007BF5A5 \n\nCopy the complete generated code.\nEdit the file /etc/grub.d/40_custom (or a custom configuration file in the /etc/grub.d/ directory):\n\nAt the end of the file add the following commands:\n\nsetsuperusers="root"\npassword_pbkdf2 root grub.pbkdf2.sha512.10000.LONGSTRING\n\nSave the file and exit\nRun: sudo update-grub\nReboot

Rule ID: SV-90187r2_rule
Severity: high
Rule Title: Ubuntu operating systems booted with United Extensible Firmware Interface (UEFI) implemented must require authentication upon booting into single-user mode and maintenance.
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. Successful 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.
Check_content: [u'Verify that an encrypted root password is set. This is only applicable on Ubuntu operating systems that use UEFI.\n\nRun the following command to verify the encrypted password is set:\n\n# grep \u2013i password /boot/efi/EFI/grub.cfg\npassword_pbkdf2 root grub.pbkdf2.sha512.10000.VeryLongString\n\nIf the root password entry does not begin with \u201cpassword_pbkdf2\u201d, 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/10_linux" file with the following command to add a boot password for the root entry:\n\n# cat << EOF > set superusers="root" password_pbkdf2 root grub.pbkdf2.sha512.VeryLongString > EOF\n\nGenerate an updated "grub.conf" file with the new password using the following commands:\n\n# grub-mkconfig --output=/tmp/grub2.cfg\n# mv /tmp/grub2.cfg /boot/efi/EFI/grub.cfg

Rule ID: SV-90189r1_rule
Severity: high
Rule Title: All persistent disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at rest protection.
Description: Ubuntu operating systems handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest.\n\nSelection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields).\n\n
Check_content: [u'Verify the Ubuntu operating system prevents unauthorized disclosure or modification of all information requiring at rest protection by using disk encryption. \n\nIf there is a documented and approved reason for not having data-at-rest encryption, this requirement is Not Applicable.\n\nDetermine the partition layout for the system with the following command:\n\n# fdisk \u2013l\n\nVerify that 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. If any partitions other than pseudo file systems (such as /proc or /sys) are not listed, this is a finding.
Fixtext: Configure the Ubuntu operating system to prevent unauthorized modification of all information at rest by using disk encryption. \n\nEncrypting a partition in an already-installed system is more difficult, because you need to resize and change existing partitions. To encrypt an entire partition, dedicate a partition for encryption in the partition layout.

Rule ID: SV-90191r1_rule
Severity: medium
Rule Title: All public directories must be owned by root 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.
Check_content: Verify that all public directories are owned by root to prevent unauthorized and unintended information transferred via shared system resources.\n\nCheck to see that all public directories have the public sticky bit set by running the following command:\n\n# sudo find / -type d -perm -0002 -exec ls -lLd {} \\;\n\ndrwxrwxrwxt 7 root root 4096 Jul 26 11:19 /tmp\n\nIf any of the returned directories are not owned by root, this is a finding.
Fixtext: Configure all public directories to be owned by root to prevent unauthorized and unintended information transferred via shared system resources.\n\nSet the owner of all public directories as root using the command, replace "[Public Directory]" with any directory path not owned by root:\n\n# sudo chown root [Public Directory]

Rule ID: SV-90193r3_rule
Severity: medium
Rule Title: All world-writable directories must be group-owned by root, sys, bin, or an application group.
Description: If a world-writable directory has the sticky bit set and is not group-owned by a privileged Group Identifier (GID), unauthorized users may be able to modify files created by others.\n\nThe only authorized public directories are those temporary directories supplied with the system or those designed to be temporary file repositories. The setting is normally reserved for directories used by the system and by users for temporary file storage, (e.g., /tmp), and for directories requiring global read/write access.\n
Check_content: Verify that all world-writable directories are group-owned by root to prevent unauthorized and unintended information transferred via shared system resources.\n\nCheck the system for world-writable directories with the following command:\n\n# sudo find / -type d -perm -0002 -exec ls -lLd {} \\;\n\ndrwxrwxrwxt 7 root root 4096 Jul 26 11:19 /tmp\n\nIf any world-writable directories are not owned by root, sys, bin, or an application group associated with the directory, this is a finding.
Fixtext: Change the group of the world-writable directories to root, sys, bin, or an application group with the following command, replacing "[world-writable Directory]":\n\n# sudo chgrp root [world-writable Directory]

Rule ID: SV-90195r3_rule
Severity: medium
Rule Title: A file integrity tool must be installed to verify correct operation of all security functions in the Ubuntu operating system.
Description: Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters.\n\nThis requirement applies to Ubuntu operating systems performing security function verification/testing and/or systems and environments that require this functionality.
Check_content: Verify that Advanced Intrusion Detection Environment (AIDE) is installed and verifies the correct operation of all security functions.\n\nCheck that the AIDE package is installed with the following command:\n\n# sudo apt list aide\n\naide/xenial,now 0.16~a2.git20130520-3 amd64 [installed]\n\nIf AIDE is not installed, ask the System Administrator how file integrity checks are performed on the system. \n\nIf there is no application installed to perform integrity checks, this is a finding.
Fixtext: Install the AIDE package by running the following command:\n\n# sudo apt-get install aide

Rule ID: SV-90197r2_rule
Severity: medium
Rule Title: The file integrity tool must perform verification of the correct operation of security functions: upon system start-up and/or restart; upon command by a user with privileged access; and/or every 30 days.
Description: Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters.\n\nNotifications provided by information systems include, for example, electronic alerts to system administrators, messages to local computer consoles, and/or hardware indications, such as lights.\n\nThis requirement applies to Ubuntu operating systems performing security function verification/testing and/or systems and environments that require this functionality.
Check_content: Verify that Advanced Intrusion Detection Environment (AIDE) performs a verification of the operation of security functions every 30 days.\n\nNote: A file integrity tool other than AIDE may be used, but the tool must be executed at least once per week.\n\nCheck that AIDE is being executed every 30 days or less with the following command:\n\n# ls -al /etc/cron.daily/aide\n\n-rwxr-xr-x 1 root root 26049 Oct 24 2014 /etc/cron.daily/aide\n\nIf the "/etc/cron.daily/aide" file does not exist or the cron job is not configured to run at least every 30 days, this is a finding.
Fixtext: The cron file for AIDE is fairly complex as it creates the report. The easiest way to create the file is to update the AIDE package with the following command:\n\n# sudo apt-get install aide

Rule ID: SV-90199r3_rule
Severity: low
Rule Title: The file integrity tool must be configured to verify Access Control Lists (ACLs).
Description: ACLs can provide permissions beyond those permitted through the file mode and must be verified by file integrity tools.
Check_content: Verify the file integrity tool is configured to verify Access Control Lists (ACLs).\n\nUse the following command to determine if the file is in a location other than "/etc/aide/aide.conf":\n\n# find / -name aide.conf\n\nCheck the "aide.conf" file to determine if the "acl" rule has been added to the rule list being applied to the files and directories selection lists with the following command:\n\n# egrep "[+]?acl" /etc/aide/aide.conf\n\nVarFile = OwnerMode+n+l+X+acl\n\nIf the "acl" rule is not being used on all selection lines in the "/etc/aide.conf" file, is commented out, or ACLs are not being checked by another file integrity tool, this is a finding.
Fixtext: Configure the file integrity tool to check file and directory ACLs. \n\nIf AIDE is installed, ensure the "acl" rule is present on all file and directory selection lists.

Rule ID: SV-90201r1_rule
Severity: low
Rule Title: The file integrity tool must be configured to verify extended attributes.
Description: Extended attributes in file systems are used to contain arbitrary data and file metadata with security implications.
Check_content: Verify the file integrity tool is configured to verify extended attributes.\n\nCheck to see if Advanced Intrusion Detection Environment (AIDE) is installed with the following command:\n\n# dpkg -l |grep aide\n\nii aide 0.16~a2.git20130520-3\nii aide-common 0.16~a2.git20130520-3\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.\n\nNote: AIDE is highly configurable at install time. These commands assume the "aide.conf" file is under the "/etc" directory. \n\nUse the following command to determine if the file is in another location:\n\n# find / -name aide.conf\n\nCheck the "aide.conf" file to determine if the "xattrs" rule has been added to the rule list being applied to the files and directories selection lists with the following command:\n\n# egrep "[+]?xattrs" /etc/aide/aide.conf\n\nVarFile = OwnerMode+n+l+X+xattrs\n\nIf the "xattrs" rule is not being used on all selection lines in the "/etc/aide.conf" file, or extended attributes are not being checked by another file integrity tool, this is a finding.
Fixtext: Configure the file integrity tool to check file and directory extended attributes. \n\nIf AIDE is installed, ensure the "xattrs" rule is present on all file and directory selection lists.

Rule ID: SV-90203r3_rule
Severity: medium
Rule Title: The file integrity tool must notify the system administrator when changes to the baseline configuration or anomalies in the operation of any security functions are discovered.
Description: Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the Ubuntu operating system. Changes to Ubuntu operating system configurations can have unintended side effects, some of which may be relevant to security.\n\nSecurity 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\nDetecting such changes and providing an automated response can help avoid unintended, negative consequences that could ultimately affect the security state of the Ubuntu operating system. The Ubuntu operating system's IMO/ISSO and SAs must be notified via email and/or monitoring system trap when there is an unauthorized modification of a configuration item.\n\nNotifications provided by information systems include messages to local computer consoles, and/or hardware indications, such as lights.\n\nThis capability must take into account operational requirements for availability for selecting an appropriate response. The organization may choose to shut down or restart the information system upon security function anomaly detection.\n\n
Check_content: Verify that Advanced Intrusion Detection Environment (AIDE) notifies the system administrator when anomalies in the operation of any security functions are discovered.\n\nCheck that AIDE notifies the system administrator when anomalies in the operation of any security functions are discovered with the following command:\n\n# sudo grep SILENTREPORTS /etc/default/aide\n\nSILENTREPORTS=no\n\nIf the "/etc/cron.daily/aide" file does not exist, the cron job is configured with the "SILENTREPORTS=yes" option, or the line is commented out, this is a finding.
Fixtext: Modify the "SILENTREPORTS" parameter in "/etc/default/aide" file with a value "no" of if it does not already exist:\n\nSILENTREPORTS=no\n

Rule ID: SV-90205r2_rule
Severity: medium
Rule Title: The Ubuntu operating system 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 in order 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.
Check_content: Verify that Advanced Intrusion Detection Environment (AIDE) to properly configured to use cryptographic mechanisms to protect the integrity of audit tools.\n\nCheck the selection lines that aide is configured to add/check with the following command:\n\n# egrep '(\\/usr\\/sbin\\/(audit|au))' /etc/aide/aide.conf\n\n/usr/sbin/auditctl p+i+n+u+g+s+b+acl+xattr+sha512\n/usr/sbin/auditd p+i+n+u+g+s+b+acl+xattr+sha512\n/usr/sbin/ausearch p+i+n+u+g+s+b+acl+xattr+sha512\n/usr/sbin/aureport p+i+n+u+g+s+b+acl+xattr+sha512\n/usr/sbin/autrace p+i+n+u+g+s+b+acl+xattr+sha512\n/usr/sbin/audispd p+i+n+u+g+s+b+acl+xattr+sha512\n/usr/sbin/augenrules p+i+n+u+g+s+b+acl+xattr+sha512\n\nIf any of the seven audit tools does not have an appropriate selection line, this is a finding.
Fixtext: Add or update the following selection lines to "/etc/aide/aide.conf", in order to protect the integrity of the audit tools.\n\n# Audit Tools\n/usr/sbin/auditctl p+i+n+u+g+s+b+acl+xattr+sha512\n/usr/sbin/auditd p+i+n+u+g+s+b+acl+xattr+sha512\n/usr/sbin/ausearch p+i+n+u+g+s+b+acl+xattr+sha512\n/usr/sbin/aureport p+i+n+u+g+s+b+acl+xattr+sha512\n/usr/sbin/autrace p+i+n+u+g+s+b+acl+xattr+sha512\n/usr/sbin/audispd p+i+n+u+g+s+b+acl+xattr+sha512\n/usr/sbin/augenrules p+i+n+u+g+s+b+acl+xattr+sha512

Rule ID: SV-90207r2_rule
Severity: medium
Rule Title: Advance package Tool (APT) must be configured to prevent the installation of patches, service packs, device drivers, or Ubuntu operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization.
Description: Changes to any software components can have significant effects on the overall security of the Ubuntu operating system. This requirement ensures the software has not been tampered with and that it has been provided by a trusted vendor.\n\nAccordingly, patches, service packs, device drivers, or Ubuntu 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. Setting the "Verify-Peer" Boolean will determine whether or not the server\'s host certificate should be verified against trusted certificates. This ensures the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are disallowed by this requirement. The Ubuntu operating system should not have to verify the software again. This requirement does not mandate DoD certificates for this purpose; however, the certificate used to verify the software must be from an approved CA.
Check_content: Verify that Advance package Tool (APT) is configured to prevent the installation of patches, service packs, device drivers, or Ubuntu operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization.\n\nCheck that the "AllowUnauthenticated" variable is not set at all or set to "false" with the following command:\n\n# grep -i allowunauth /etc/apt/apt.conf.d/*\n/etc/apt/apt.conf.d/01-vendor-Ubuntu:APT::Get::AllowUnauthenticated "false";\n\nIf any of the files returned from the command with "AllowUnauthenticated" set to "true", this is a finding.
Fixtext: Configure Advance package Tool (APT) to prevent the installation of patches, service packs, device drivers, or Ubuntu operating system components without verification they have been digitally signed using a certificate that is recognized and approved by the organization.\n\nRemove/Update any APT configuration file 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";

Rule ID: SV-90209r1_rule
Severity: medium
Rule Title: Advance package Tool (APT) must remove 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.
Check_content: Verify Advance package Tool (APT) is configured to remove all software components after updated versions have been installed.\n\nCheck that APT is configured to remove all software components after updating with the following command:\n\n# grep -i remove-unused /etc/apt/apt.conf.d/50unattended-upgrades\nUnattended-Upgrade::Remove-Unused-Dependencies "true";\n\nIf the "Remove-Unused-Dependencies" parameter is not set to "true", or is missing, this is a finding.
Fixtext: Configure APT to remove all software components after updated versions have been installed.\n\nAdd or updated the following option to the "/etc/apt/apt.conf.d/50unattended-upgrades" file:\n\nUnattended-Upgrade::Remove-Unused-Dependencies "true";

Rule ID: SV-90211r2_rule
Severity: medium
Rule Title: Automatic mounting of Universal Serial Bus (USB) mass storage driver must be disabled.
Description: Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity.\n\nPeripherals include, but are not limited to, such devices as flash drives, external storage, and printers.
Check_content: [u'Verify that automatic mounting of the Universal Serial Bus (USB) mass storage driver has been disabled.\n\nCheck that the USB mass storage drive has not been loaded with the following command:\n\n#lsmod | grep usb-storage\n\nIf a "usb-storage" line is returned, this is a finding.\n\nCheck that automatic mounting of the USB mass storage driver has been disabled with the following command:\n\n#sudo modprobe -vn  usb-storage\n\ninstall /bin/true\n\nIf \u201cinstall /bin/true\u201d is not returned, this is a finding.
Fixtext: [u'Disable the mounting of the Universal Serial Bus (USB) mass storage driver by running the following command: \n\n# sudo echo \u201cinstall usb-storage /bin/true\u201d >> /etc/modprobe.d/DISASTIG.conf

Rule ID: SV-90213r2_rule
Severity: medium
Rule Title: File system automounter must be disabled unless required.
Description: Automatically mounting file systems permits easy introduction of unknown devices, thereby facilitating malicious activity.\n\n
Check_content: Verify the Ubuntu operating system disables the ability to automount devices.\n\nCheck to see if automounter service is active with the following command:\n\n# systemctl status autofs\n autofs.service - LSB: Automounts filesystems on demand\n   Loaded: loaded (/etc/init.d/autofs; bad; vendor preset: enabled)\n   Active: active (running) since Thu 2017-05-04 07:53:51 EDT; 6 days ago\n     Docs: man:systemd-sysv-generator(8)\n   CGroup: /system.slice/autofs.service\n           +-24206 /usr/sbin/automount --pid-file /var/run/autofs.pid\n\nIf the "autofs" status is set to "active" and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.
Fixtext: Configure the Ubuntu operating system to disable the ability to automount devices.\n\nTurn off the automount service with the following command:\n\n# sudo systemctl stop autofs\n\nIf "autofs" is required for Network File System (NFS), it must be documented with the Information System Security Officer (ISSO).

Rule ID: SV-90215r2_rule
Severity: medium
Rule Title: Pam_Apparmor must be configured to allow system administrators to pass information to any other Ubuntu operating system administrator or user, change security attributes, and to confine all non-privileged users from executing functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.
Description: Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via specified ownership assignment. DAC allows the owner to determine who will have access to objects they control. An example of DAC includes user-controlled file permissions.\n\nWhen discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing (i.e., the subjects have the discretion to pass) the information to other subjects or objects. A subject that is constrained in its operation by Mandatory Access Control policies is still able to operate under the less rigorous constraints of this requirement. Thus, while Mandatory Access Control imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, this requirement permits the subject to pass the information to any subject at the same sensitivity level. The policy is bounded by the information system boundary. Once the information is passed outside the control of the information system, additional means may be required to ensure the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control.\n\n
Check_content: Verify the Ubuntu operating system is configured to allow system administrators to pass information to any other Ubuntu operating system administrator or user.\n\nCheck that "Pam_Apparmor" is installed on the system with the following command:\n\n# sudo apt list libpam-apparmor\n\nlibpam-apparmor/xenial-updates,now 2.10.95-0ubuntu2.7 amd64 [installed]\n\nIf the "Pam_Apparmor" package is not installed, this is a finding.\n\nCheck that Pam_Apparmor has properly configured profiles\n\n# sudo apparmor_status\n\napparmor module is loaded.\n13 profiles are loaded.\n13 profiles are in enforce mode.\n   /sbin/dhclient\n   ...\n   lxc-container-default-with-nesting\n0 profiles are in complain mode.\n\nIf all loaded profiles are not in "enforce" mode, or there are any profiles in "complain" mode, this is a finding.
Fixtext: Configure the Ubuntu operating system to allow system administrators to pass information to any other Ubuntu operating system administrator or user.\n\nInstall "Pam_Apparmor" (if it is not installed) with the following command:\n\n# sudo apt-get install libpam-apparmor\n\nEnable/Activate "Apparmor" (if it is not already active) 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: Pam_Apparmor must have properly configured profiles. All configurations will be based on the actual system setup and organization. See the "Pam_Apparmor" documentation for more information on configuring profiles.

Rule ID: SV-90217r2_rule
Severity: medium
Rule Title: The Apparmor module must be configured to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs and limit the ability of non-privileged users to grant other users direct access to the contents of their home directories/folders.
Description: The organization must identify authorized software programs and permit execution of authorized software. The process used to identify software programs that are authorized to execute on organizational information systems is commonly referred to as whitelisting.\n\nUtilizing a whitelist provides a configuration management method for allowing the execution of only authorized software. Using only authorized software decreases risk by limiting the number of potential vulnerabilities. Verification of white-listed software occurs prior to execution or at system startup.\n\nUsers' home directories/folders may contain information of a sensitive nature. Non-privileged users should coordinate any sharing of information with an SA through shared resources.\n\n
Check_content: [u'Verify the Ubuntu operating system is configured to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs and access to user home directories.\n\nCheck that "Apparmor" is configured to employ application whitelisting and home directory access control with the following command:\n\n# sudo apparmor_status\n\napparmor module is loaded.\n13 profiles are loaded.\n13 profiles are in enforce mode.\n   /sbin/dhclient\n   ...\n   lxc-container-default-with-nesting\n0 profiles are in complain mode.\n\nIf the defined profiles do not match the organization\u2019s list of authorized software, this is a finding.
Fixtext: Configure the Ubuntu operating system to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs.\n\nInstall "Apparmor" (if it is not installed) with the following command:\n\n# sudo apt-get install libpam-apparmor\n\nEnable/Activate "Apparmor" (if it is not already active) 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. See the "Apparmor" documentation for more information on configuring profiles.

Rule ID: SV-90221r2_rule
Severity: high
Rule Title: The x86 Ctrl-Alt-Delete key sequence must be disabled.
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 GNOME 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.
Check_content: Verify the Ubuntu operating system is not configured to reboot the system when Ctrl-Alt-Delete is pressed.\n\nCheck that the "ctrl-alt-del.target" (otherwise also known as reboot.target) is not active with the following command:\n\n# systemctl status ctrl-alt-del.target\nreboot.target - Reboot\n   Loaded: loaded (/usr/lib/systemd/system/reboot.target; disabled)\n   Active: inactive (dead)\n     Docs: man:systemd.special(7)\n\nIf the "ctrl-alt-del.target" is active, this is a finding.
Fixtext: [u'Configure the system to disable the Ctrl-Alt-Delete sequence for the command line with the following command:\n\n# sudo systemctl mask ctrl-alt-del.target\n\nAnd reload the daemon to take effect \n\n# sudo systemctl daemon-reload\n\nIf GNOME is active on the system, create a database to contain the system-wide setting (if it does not already exist) with the following command: \n\n# cat /etc/dconf/db/local.d/00-disable-CAD \n\nAdd the setting to disable the Ctrl-Alt-Delete sequence for GNOME:\n\n[org/gnome/settings-daemon/plugins/media-keys]\nlogout=\u2019\u2019

Rule ID: SV-90223r2_rule
Severity: medium
Rule Title: Default permissions must be defined in such a way that all authenticated users can only read and modify their own files.
Description: Setting the most restrictive default permissions ensures that when new accounts are created they do not have unnecessary access.
Check_content: Verify the Ubuntu operating system defines default permissions for all authenticated users in such a way that the user can only read and modify their own files.\n\nCheck that the Ubuntu operating system defines default permissions for all authenticated users with the following command: \n\n# grep -i "umask" /etc/login.defs\n\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", "UMASK" is commented out or "UMASK" is missing completely, 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 only read and modify their own files.\n\nEdit the "UMASK" parameter in the "/etc/login.defs" file to match the example below:\n\nUMASK 077

Rule ID: SV-90225r2_rule
Severity: medium
Rule Title: The Ubuntu operating system must not have unnecessary accounts.
Description: Accounts providing no operational purpose provide additional opportunities for system compromise. Unnecessary accounts include user accounts for individuals not requiring access to the system and application accounts for applications not installed on the system.
Check_content: Verify all accounts on the system are assigned to an active system, application, or user account.\n\nObtain the list of authorized system accounts from the Information System Security Officer (ISSO).\n\nCheck the system accounts on the system with the following command:\n\n# more /etc/passwd\nroot:x:0:0:root:/root:/bin/bash\n...\ngames:x:5:60:games:/usr/games:/usr/sbin/nologin\n\nAccounts such as "games" and "gopher" are not authorized accounts as they do not support authorized system functions. \n\nIf the accounts on the system do not match the provided documentation, or accounts that do not support an authorized system function are present, this is a finding.
Fixtext: Configure the system so all accounts on the system are assigned to an active system, application, or user account. \n\nRemove accounts that do not support approved system activities or that allow for a normal user to perform administrative-level actions. \n\nDocument all authorized accounts on the system.

Rule ID: SV-90227r2_rule
Severity: medium
Rule Title: Duplicate User IDs (UIDs) must not exist for interactive users.
Description: To assure accountability and prevent unauthenticated access, interactive users must be identified and authenticated to prevent potential misuse and compromise of the system.\n\nInteractive users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Interactive users (and processes acting on behalf of users) 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\n
Check_content: Verify that the Ubuntu operating system contains no duplicate User IDs (UIDs) for interactive users.\n\nCheck that the Ubuntu operating system contains no duplicate 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 User ID (UID) with a unique UID.

Rule ID: SV-90229r1_rule
Severity: high
Rule Title: The root account must be the only account having unrestricted access to the system.
Description: If an account other than root also has a User Identifier (UID) of "0", it has root authority, giving that account unrestricted access to the entire Ubuntu operating system. Multiple accounts with a UID of "0" afford an opportunity for potential intruders to guess a password for a privileged account.
Check_content: Check the Ubuntu operating system for duplicate User ID (UID) "0" assignments with the following command:\n\n# awk -F: \'$3 == 0 {print $1}\' /etc/passwd\n\nroot\n\nIf any accounts other than root have a UID of "0", this is a finding.
Fixtext: Change the User ID (UID) of any account on the system, other than root, that has a UID of "0". \n\nIf the account is associated with system commands or applications, the UID should be changed to one greater than "0" but less than "1000". Otherwise, assign a UID of greater than "1000" that has not already been assigned.

Rule ID: SV-90231r1_rule   todo?
Severity: medium
Rule Title: User accounts with temporary passwords, must require an immediate change to a permanent password after login.
Description: Without providing this capability, an account may be created without a password. Non-repudiation cannot be guaranteed once an account is created if a user is not forced to change the temporary password upon initial logon.\n\nTemporary passwords are typically used to allow access when new accounts are created or passwords are changed. It is common practice for administrators to create temporary passwords for user accounts which allow the users to log on, yet force them to change the password once they have successfully authenticated.
Check_content: Verify a policy exists that ensures when a user account is created, it is created using a method that forces a user to change their password upon their next login.\n\nIf a policy does not exist, this is a finding.
Fixtext: Create a policy that ensures when a user is created, it is created using a method that forces a user to change their password upon their next login.\n\nBelow are two examples of how to create a user account that requires the user to change their password upon their next login.\n\n# chage -d 0 [UserName]\n\nor \n\n# passwd -e [UserName]

Rule ID: SV-90233r2_rule
Severity: medium
Rule Title: Pluggable Authentication Module (PAM) must prohibit 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.
Check_content: Verify that Pluggable Authentication Module (PAM) prohibits the use of cached authentications after one day.\n\nNote: If smart card authentication is not being used on the system this item is Not Applicable.\n\nCheck that PAM prohibits the use of cached authentications after one day with the following command:\n\n# sudo grep -i "timestamp_timeout" /etc/pam.d/*\n\ntimestamp_timeout=86400\n\nIf "timestamp_timeout" is not set to a value of "86400" or less, or is commented out, this is a finding.
Fixtext: Configure Pluggable Authentication Module (PAM) to prohibit the use of cached authentications after one day. \n\nAdd or change the following line in "/etc/pam.d/common-auth" or "/etc/pam.d/common-session" just below the line "[pam]".\n\ntimestamp_timeout = 86400

Rule ID: SV-90235r1_rule
Severity: medium
Rule Title: All files and directories must have a valid owner.
Description: Unowned files and directories may be unintentionally inherited if a user is assigned the same User Identifier "UID" as the UID of the un-owned files.
Check_content: Verify all files and directories on the Ubuntu operating system have a valid owner.\n\nCheck the owner of all files and directories with the following command:\n\n# sudo find / -nouser\n\nIf any files on the system do not have an assigned owner, this is a finding.
Fixtext: Either remove all files and directories from the system that do not have a valid user, or assign a valid user to all unowned files and directories on the Ubuntu operating system with the "chown" command:\n\n# sudo chown <user> <file>

Rule ID: SV-90237r1_rule
Severity: medium
Rule Title: All files and directories must have a valid group owner.
Description: Files without a valid group owner may be unintentionally inherited if a group is assigned the same Group Identifier (GID) as the GID of the files without a valid group owner.
Check_content: Verify all files and directories on the Ubuntu operating system have a valid group.\n\nCheck the owner of all files and directories with the following command:\n\n# sudo find / -nogroup\n\nIf any files on the system do not have an assigned group, this is a finding.
Fixtext: Either remove all files and directories from the Ubuntu operating system that do not have a valid group, or assign a valid group to all files and directories on the system with the "chgrp" command:\n\n# sudo chgrp <group> <file>

Rule ID: SV-90239r1_rule
Severity: medium
Rule Title: All local interactive users must have a home directory assigned in the /etc/passwd file.
Description: If local interactive users are not assigned a valid home directory, there is no place for the storage and control of files they should own.
Check_content: Verify local interactive users on the Ubuntu operating system have a home directory assigned.\n\nCheck for missing local interactive user home directories with the following command:\n\n# sudo pwck -r\nuser \'lp\': directory \'/var/spool/lpd\' does not exist\nuser \'news\': directory \'/var/spool/news\' does not exist\nuser \'uucp\': directory \'/var/spool/uucp\' does not exist\nuser \'www-data\': directory \'/var/www\' does not exist\n\nAsk the System Administrator (SA) if any users found without home directories are local interactive users. If the SA is unable to provide a response, check for users with a User Identifier (UID) of 1000 or greater with the following command:\n\n# sudo cut -d: -f 1,3 /etc/passwd | egrep ":[1-4][0-9]{2}$|:[0-9]{1,2}$"\n\nIf any interactive users do not have a home directory assigned, this is a finding.
Fixtext: Assign home directories to all local interactive users on the Ubuntu operating system that currently do not have a home directory assigned.

Rule ID: SV-90241r1_rule
Severity: medium
Rule Title: All local interactive user accounts, upon creation, must be assigned a home directory.
Description: If local interactive users are not assigned a valid home directory, there is no place for the storage and control of files they should own.
Check_content: Verify all local interactive users on the Ubuntu operating system are assigned a home directory upon creation.\n\nCheck to see if the system is configured to create home directories for local interactive users with the following command:\n\n# grep -i create_home /etc/login.defs\nCREATE_HOME yes\n\nIf the value for "CREATE_HOME" parameter is not set to "yes", the line is missing, or the line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to assign home directories to all new local interactive users by setting the "CREATE_HOME" parameter in "/etc/login.defs" to "yes" as follows.\n\nCREATE_HOME yes

Rule ID: SV-90243r1_rule
Severity: medium
Rule Title: All local interactive user home directories defined in the /etc/passwd file must exist.
Description: If a local interactive user has a home directory defined that does not exist, the user may be given access to the / directory as the current working directory upon logon. This could create a Denial of Service because the user would not be able to access their logon configuration files, and it may give them visibility to system files they normally would not be able to access.
Check_content: Verify the assigned home directory of all local interactive users on the Ubuntu operating system exists.\n\nCheck the home directory assignment for all local interactive non-privileged users with the following command:\n\n# ls -ld $(awk -F: \'($3>=1000)&&($1!="nobody"){print $6}\' /etc/passwd)\n\ndrwxr-xr-x 2 smithj admin 4096 Jun 5 12:41 smithj\n\nNote: This may miss interactive users that have been assigned a privileged User ID (UID). Evidence of interactive use may be obtained from a number of log files containing system logon information.\n\nCheck that all referenced home directories exist with the following command:\n\n# pwck -r\n\nuser \'smithj\': directory \'/home/smithj\' does not exist\n\nIf any home directories referenced in "/etc/passwd" are returned as not defined, this is a finding.
Fixtext: Create home directories to all local interactive users that currently do not have a home directory assigned. Use the following commands to create the user home directory assigned in "/etc/ passwd":\n\nNote: The example will be for the user smithj, who has a home directory of "/home/smithj", a User ID (UID) of "smithj", and a Group Identifier (GID) of "users assigned" in "/etc/passwd".\n\n# mkdir /home/smithj \n# chown smithj /home/smithj\n# chgrp users /home/smithj\n# chmod 0750 /home/smithj

Rule ID: SV-90245r1_rule
Severity: medium
Rule Title: All local interactive user home directories must have mode 0750 or less permissive.
Description: Excessive permissions on local interactive user home directories may allow unauthorized access to user files by other users.
Check_content: Verify the assigned home directory of all local interactive users has a mode of "0750" or less permissive.\n\nCheck the home directory assignment for all non-privileged users with the following command:\n\nNote: This may miss interactive users that have been assigned a privileged User Identifier (UID). Evidence of interactive use may be obtained from a number of log files containing system logon information.\n\n# ls -ld $(awk -F: \'($3>=1000)&&($1!="nobody"){print $6}\' /etc/passwd)\n\ndrwxr-x--- 2 smithj admin 4096 Jun 5 12:41 smithj\n\nIf home directories referenced in "/etc/passwd" do not have a mode of "0750" or less permissive, this is a finding.
Fixtext: [u'Change the mode of interactive user\u2019s home directories to "0750". To change the mode of a local interactive user\u2019s home directory, use the following command:\n\nNote: The example will be for the user "smithj".\n\n# chmod 0750 /home/smithj

Rule ID: SV-90247r1_rule
Severity: medium
Rule Title: All local interactive user home directories must be group-owned by the home directory owners primary group.
Description: If the Group Identifier (GID) of a local interactive user\u2019s home directory is not the same as the primary GID of the user, this would allow unauthorized access to the user\u2019s files, and users that share the same group may not be able to access files that they legitimately should.
Check_content: [u'Verify the assigned home directory of all local interactive users is group-owned by that user\u2019s primary Group Identifier (GID).\n\nCheck the home directory assignment for all non-privileged users on the system with the following command:\n\nNote: This may miss local interactive users that have been assigned a privileged UID. Evidence of interactive use may be obtained from a number of log files containing system logon information. The returned directory "/home/smithj" is used as an example.\n\n# ls -ld $(awk -F: \'($3>=1000)&&($1!="nobody"){print $6}\' /etc/passwd)\n\ndrwxr-x--- 2 smithj admin 4096 Jun 5 12:41 smithj\n\nCheck the user\'s primary group with the following command:\n\n# grep admin /etc/group\nadmin:x:250:smithj,jonesj,jacksons\n\nIf the user home directory referenced in "/etc/passwd" is not group-owned by that user\u2019s primary GID, this is a finding.
Fixtext: [u'Change the group owner of a local interactive user\u2019s home directory to the group found in "/etc/passwd". To change the group owner of a local interactive user\u2019s home directory, use the following command:\n\nNote: The example will be for the user "smithj", who has a home directory of "/home/smithj", and has a primary group of users.\n\n# chgrp users /home/smithj

Rule ID: SV-90249r1_rule
Severity: medium
Rule Title: All local initialization files must have mode 0740 or less permissive.
Description: Local initialization files are used to configure the user's shell environment upon logon. Malicious modification of these files could compromise accounts upon logon.
Check_content: Verify that all local initialization files have a mode of "0740" or less permissive.\n\nCheck the mode on all local initialization files with the following command:\n\nNote: The example will be for the smithj user, who has a home directory of "/home/smithj".\n\n# ls -al /home/smithj/.* | more\n-rwxr-xr-x 1 smithj users 896 Mar 10 2011 .profile\n-rwxr-xr-x 1 smithj users 497 Jan 6 2007 .login\n-rwxr-xr-x 1 smithj users 886 Jan 6 2007 .something\n\nIf any local initialization files have a mode more permissive than "0740", this is a finding.
Fixtext: Set the mode of the local initialization files to "0740" with the following command:\n\nNote: The example will be for the smithj user, who has a home directory of "/home/smithj".\n\n# chmod 0740 /home/smithj/.<INIT_FILE>

Rule ID: SV-90251r1_rule
Severity: medium
Rule Title: All local interactive user initialization files executable search paths must contain only paths that resolve to the system default or the users home directory.
Description: The executable search path (typically the PATH environment variable) contains a list of directories for the shell to search to find executables. If this path includes the current working directory executables in these directories may be executed instead of system commands. This variable is formatted as a colon-separated list of directories. If there is an empty entry, such as a leading or trailing colon or two consecutive colons, this is interpreted as the current working directory. If deviations from the default system search path for the local interactive user are required, they must be documented with the Information System Security Officer (ISSO).
Check_content: [u'Verify that all local interactive user initialization files\' executable search path statements do not contain statements that will reference a working directory other than the users\u2019 home directory or the system default.\n\nCheck the executable search path statement for all local interactive user initialization files in the users\' home directory with the following commands:\n\nNote: The example will be for the smithj user, which has a home directory of "/home/smithj".\n\n# grep -i path /home/smithj/.*\n/home/smithj/.bash_profile:PATH=$PATH:$HOME/.local/bin:$HOME/bin\n/home/smithj/.bash_profile:export PATH\n\nIf any local interactive user initialization files have executable search path statements that include directories outside of their home directory, and the additional path statements are not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.
Fixtext: Edit the local interactive user initialization files to change any PATH variable statements for executables that reference directories other than their home directory or the system default. If a local interactive user requires path variables to reference a directory owned by the application, it must be documented with the Information System Security Officer (ISSO).

Rule ID: SV-90253r1_rule
Severity: medium
Rule Title: Local initialization files must not execute world-writable programs.
Description: If user start-up files execute world-writable programs, especially in unprotected directories, they could be maliciously modified to destroy user files or otherwise compromise the system at the user level. If the system is compromised at the user level, it is easier to elevate privileges to eventually compromise the system at the root and network level.
Check_content: [u'Verify that local initialization files do not execute world-writable programs.\n\nCheck the system for world-writable files with the following command:\n\n# sudo find / -perm -002 -type f -exec ls -ld {} \\; | more\n\nFor all files listed, check for their presence in the local initialization files with the following commands:\n\nNote: The example will be for a system that is configured to create users\u2019 home directories in the "/home" directory.\n\n# grep <file> /home/*/.*\n\nIf any local initialization files are found to reference world-writable files, this is a finding.
Fixtext: Set the mode on files being executed by the local initialization files with the following command:\n\n# chmod 0755 <file>

Rule ID: SV-90255r2_rule
Severity: medium
Rule Title: File systems that contain user home directories must be mounted to prevent files with the setuid and setguid bit set from being executed.
Description: The "nosuid" mount option causes the system to not execute setuid and setgid files with owner privileges. This option must be used for mounting any file system not containing approved setuid and setguid files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
Check_content: Verify file systems that contain user home directories are mounted with the "nosuid" option.\n\nNote: If a separate file system has not been created for the user home directories (user home directories are mounted under "/"), this is not a finding as the "nosuid" option cannot be used on the "/" system.\n\nFind the file system(s) that contain the user home directories with the following command:\n\n# awk -F: \'($3>=1000)&&($1!="nobody"){print $1,$3,$6}\' /etc/passwd\n\nsmithj:1001: /home/smithj\nrobinst:1002: /home/robinst\n\nCheck the file systems that are mounted at boot time with the following command:\n\n# more /etc/fstab\n\nUUID=a411dc99-f2a1-4c87-9e05-184977be8539 /home ext4 rw,relatime,discard,data=ordered,nosuid 0 2\n\nIf a file system found in "/etc/fstab" refers to the user home directory file system and it does not have the "nosuid" option set, this is a finding.
Fixtext: Configure the "/etc/fstab" to use the "nosuid" option on file systems that contain user home directories for interactive users.

Rule ID: SV-90257r3_rule
Severity: medium
Rule Title: File systems that are used with removable media must be mounted to prevent files with the setuid and setguid bit set from being executed.
Description: The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
Check_content: Verify file systems that are used for removable media are mounted with the "nosuid" option.\n\nCheck the file systems that are mounted at boot time with the following command:\n\n# more /etc/fstab\n\nUUID=2bc871e4-e2a3-4f29-9ece-3be60c835222 /mnt/usbflash vfat noauto,owner,ro,nosuid 0 0\n\nIf a file system found in "/etc/fstab" refers to removable media and it does not have the "nosuid" option set, this is a finding.
Fixtext: Configure the "/etc/fstab" to use the "nosuid" option on file systems that are associated with removable media.

Rule ID: SV-90259r3_rule
Severity: medium
Rule Title: File systems that are being imported via Network File System (NFS) must be mounted to prevent files with the setuid and setguid bit set from being executed.
Description: The "nosuid" mount option causes the system to not execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
Check_content: Verify file systems that are being Network File System (NFS) imported are mounted with the "nosuid" option.\n\nFind the file system(s) that contain the directories being exported with the following command:\n\n# grep nfs /etc/fstab | grep nosuid\n\nUUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d    /store           nfs           rw,nosuid                                                    0 0\n\nIf a file system found in "/etc/fstab" refers to NFS and it does not have the "nosuid" option set, this is a finding.
Fixtext: Configure the "/etc/fstab" to use the "nosuid" option on file systems that are being imported via Network File System (NFS).

Rule ID: SV-90261r2_rule
Severity: medium
Rule Title: File systems that are being imported via Network File System (NFS) must be mounted to prevent binary files from being executed.
Description: The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.
Check_content: Verify file systems that are being Network File System (NFS) imported are mounted with the "noexec" option.\n\nFind the file system(s) that contain the directories being exported with the following command:\n\n# grep nfs /etc/fstab | grep noexec\n\nUUID=e06097bb-cfcd-437b-9e4d-a691f5662a7d    /store           nfs           rw,noexec                                                    0 0\n\nIf a file system found in "/etc/fstab" refers to NFS and it does not have the "noexec" option set, and use of NFS exported binaries is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.
Fixtext: Configure the "/etc/fstab" to use the "noexec" option on file systems that are being imported via Network File System (NFS).

Rule ID: SV-90263r2_rule
Severity: medium
Rule Title: All world-writable directories must be group-owned by root, sys, bin, or an application group.
Description: If a world-writable directory has the sticky bit set and is not group-owned by a privileged Group Identifier (GID), unauthorized users may be able to modify files created by others.\n\nThe only authorized public directories are those temporary directories supplied with the system or those designed to be temporary file repositories. The setting is normally reserved for directories used by the system and by users for temporary file storage, (e.g., /tmp), and for directories requiring global read/write access.
Check_content: Verify all world-writable directories are group-owned by root, sys, bin, or an application group.\n\nCheck the system for world-writable directories with the following command:\n\n#  sudo find / -perm -2 -type d ! -group sys ! -group root ! -group bin -exec ls -lLd {} \\;\ndrwxrwsrwt 2 root whoops 4096 Jun  6 07:44 /var/crash\ndrwxrwsrwt 2 root whoops 4096 Jul 19  2016 /var/metrics\n\nIf any world-writable directories are not owned by root, sys, bin, or an application group associated with the directory, this is a finding.
Fixtext: Change the group of the world-writable directories to root with the following command:\n\n# chgrp root <directory>

Rule ID: SV-90265r1_rule
Severity: medium
Rule Title: Kernel core dumps must be disabled unless needed.
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.
Check_content: Verify that kernel core dumps are disabled unless needed.\n\nCheck the status of the "kdump" service with the following command:\n\n# systemctl status kdump.service\nLoaded: not-found (Reason: No such file or directory)\nActive: inactive (dead)\n\nIf the "kdump" service is active, ask the System Administrator 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" service with the following command:\n\n# systemctl disable kdump.service\n\nIf kernel core dumps are required, document the need with the Information System Security Officer (ISSO).

Rule ID: SV-90267r2_rule
Severity: medium
Rule Title: A separate file system must be used for user home directories (such as /home or an equivalent).
Description: The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.
Check_content: [u'Verify that a separate file system/partition has been created for non-privileged local interactive user home directories.\n\nCheck the home directory assignment for all non-privileged users, users with a User Identifier (UID) greater than 1000, on the system with the following command:\n\n# awk -F: \'($3>=1000)&&($1!="nobody"){print $1,$3,$6}\' /etc/passwd\n\nadamsj 1001  /home/adamsj \njacksonm 1002 /home/jacksonm \nsmithj  1003 /home/smithj \n\nThe output of the command will give the directory/partition that contains the home directories for the non-privileged users on the system (in this example, "/home") and users\u2019 shell. All accounts with a valid shell (such as /bin/bash) are considered interactive users.\n\nCheck that a file system/partition has been created for the non-privileged interactive users with the following command:\n\nNote: The partition of "/home" is used in the example.\n\n# grep /home /etc/fstab\nUUID=333ada18    /home                   ext4    noatime,nobarrier,nodev  1 2\n\nIf a separate entry for the file system/partition that contains the non-privileged interactive users\' home directories does not exist, this is a finding.
Fixtext: Migrate the "/home" directory onto a separate file system/partition.

Rule ID: SV-90269r1_rule
Severity: low
Rule Title: The Ubuntu operating system must use a separate file system for /var.
Description: The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.
Check_content: Verify that a separate file system/partition has been created for "/var".\n\nCheck that a file system/partition has been created for "/var" with the following command:\n\n# grep /var /etc/fstab\nUUID=c274f65f /var ext4 noatime,nobarrier 1 2\n\nIf a separate entry for "/var" is not in use, this is a finding.
Fixtext: Migrate the "/var" path onto a separate file system.

Rule ID: SV-90271r1_rule
Severity: low
Rule Title: The Ubuntu operating system must use a separate file system for the system audit data path.
Description: The use of separate file systems for different paths can protect the system from failures resulting from a file system becoming full or failing.
Check_content: Verify that a separate file system/partition has been created for the system audit data path.\n\nCheck that a file system/partition has been created for the system audit data path with the following command:\n\nNote: /var/log/audit is used as the example as it is a common location.\n\n#grep /var/log/audit /etc/fstab\nUUID=3645951a /var/log/audit ext4 defaults 1 2\n\nIf a separate entry for "/var/log/audit" does not exist, ask the System Administrator if the system audit logs are being written to a different file system/partition on the system, then grep for that file system/partition. \n\nIf a separate file system/partition does not exist for the system audit data path, this is a finding.
Fixtext: Migrate the system audit data path onto a separate file system.

Rule ID: SV-90273r2_rule
Severity: medium
Rule Title: The /var/log directory must be group-owned by syslog.
Description: Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the Ubuntu operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.\n\nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.
Check_content: Verify the "/var/log" directory is group-owned by syslog.\n\nCheck that the "/var/log" directory is group owned by syslog with the following command:\n\n# ls -lad /var/log | cut -d\' \' -f4\n\nsyslog\n\nIf "syslog" is not returned as a result, this is a finding.
Fixtext: Change the group of the directory "/var/log" to "syslog" by running the following command:\n\n# sudo chgrp syslog /var/log 

Rule ID: SV-90275r2_rule
Severity: medium
Rule Title: The /var/log directory must be owned by root.
Description: Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the Ubuntu operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.\n\nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.
Check_content: Verify the /var/log directory is owned by root.\n\nCheck that the /var/log directory is owned by root with the following command:\n\n# ls -lad /var/log | cut -d\' \' -f3\n\nroot\n\nIf "root" is not returned as a result, this is a finding.
Fixtext: Change the owner of the directory /var/log to root by running the following command:\n\n# sudo chown root /var/log

Rule ID: SV-90277r3_rule
Severity: medium
Rule Title: The /var/log directory must have mode 0770 or less permissive.
Description: Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the Ubuntu operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.\n\nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.
Check_content: Verify that the "/var/log" directory has a mode of "0770" or less.\n\nCheck the mode of the "/var/log" directory with the following command:\n\n# stat -c "%a %n" /var/log\n\n770\n\nIf a value of "0770" or less permissive is not returned, this is a finding.
Fixtext: Change the permissions of the directory "/var/log" to "0770" by running the following command:\n\n# sudo chmod 0770 /var/log

Rule ID: SV-90279r2_rule
Severity: medium
Rule Title: The /var/log/syslog file must be group-owned by adm.
Description: Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the Ubuntu operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.\n\nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.
Check_content: Verify the "/var/log/syslog" file is group-owned by "adm".\n\nCheck that "/var/log/syslog" is group-owned by "adm" with the following command:\n\n# ls -la /var/log/syslog | cut -d\' \' -f4\n\nadm\n\nIf "adm" is not returned as a result, this is a finding.
Fixtext: Change the group of the file "/var/log/syslog" to "adm" by running the following command:\n\n# sudo chgrp adm /var/log/syslog

Rule ID: SV-90281r2_rule
Severity: medium
Rule Title: The /var/log/syslog file must be owned by syslog.
Description: Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the Ubuntu operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.\n\nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.
Check_content: Verify that the /var/log/syslog file is owned by syslog.\n\nCheck that the /var/log/syslog file is owned by syslog with the following command:\n\n# ls -la /var/log/syslog | cut -d\' \' -f3\n\nsyslog\n\nIf "syslog" is not returned as a result, this is a finding.
Fixtext: Change the owner of the file /var/log/syslog to syslog by running the following command:\n\n# sudo chown syslog /var/log/syslog

Rule ID: SV-90283r3_rule
Severity: medium
Rule Title: The /var/log/syslog file must have mode 0640 or less permissive.
Description: Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the Ubuntu operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.\n\nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.
Check_content: Verify that the "/var/log/syslog" file has mode "0640" or less permissive.\n\nCheck that "/var/log/syslog" has mode "0640" or less permissive with the following command:\n\n# stat -c "%a %n" /var/log/syslog\n\n640 /var/log/syslog\n\nIf a value of "640" or less permissive is not returned, this is a finding.
Fixtext: Change the permissions of the file "/var/log/syslog" to "0640" by running the following command:\n\n# sudo chmod 0640 /var/log

Rule ID: SV-90285r2_rule
Severity: medium
Rule Title: Library files must have mode 0755 or less permissive.
Description: If the Ubuntu operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process.\n\nThis requirement applies to Ubuntu operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals shall be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.
Check_content: Verify the system-wide shared library files contained in the following directories have mode "0755" or less permissive.\n\nCheck that the system-wide shared library files contained in the following directories have mode "0755" or less permissive with the following command:\n\nNote: Replace "[directory]" with one of the following paths:\n/lib\n/lib64\n/usr/lib\n\n# find /lib /lib64 /usr/lib -perm /022 -type f | xargs ls -la\n/usr/lib64/pkcs11-spy.so\n\nIf any system-wide shared library file is found to be group-writable or world-writable, this is a finding.
Fixtext: Configure the library files to be protected from unauthorized access. Run the following command, replacing "[file]" with any library file with a mode more permissive than 0755.\n\n# sudo chmod 0755 [file]

Rule ID: SV-90287r2_rule
Severity: medium
Rule Title: Library files must be owned by root.
Description: If the Ubuntu operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process.\n\nThis requirement applies to Ubuntu operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals shall be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.
Check_content: Verify the system-wide shared library files are owned by "root".\n\nCheck that the system-wide shared library files are owned by "root" with the following command:\n\n# sudo find /lib /usr/lib /lib64 ! -user root | xargs ls -la\n\nIf any system wide shared library file is returned, this is a finding.
Fixtext: Configure the system-wide shared library files (/lib, /usr/lib, /lib64) to be protected from unauthorized access. \n\nRun the following command, replacing "[FILE]" with any library file not owned by "root".\n\n# sudo chown root [FILE]

Rule ID: SV-90289r2_rule
Severity: medium
Rule Title: Library files must be group-owned by root.
Description: If the Ubuntu operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process.\n\nThis requirement applies to Ubuntu operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals shall be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.
Check_content: Verify the system-wide shared library files contained in the following directories are group-owned by "root".\n\nCheck that the system-wide shared library files are group-owned by "root" with the following command:\n\n# sudo find /lib /usr/lib /lib64 ! -group root | xargs ls -la\n\nIf any system wide shared library file is returned, this is a finding.
Fixtext: Configure the library files to be protected from unauthorized access. \n\nRun the following command, replacing "[FILE]" with any library file not group-owned by root.\n\n# sudo chgrp root [FILE]

Rule ID: SV-90291r2_rule
Severity: medium
Rule Title: System commands must have mode 0755 or less permissive.
Description: If the Ubuntu operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process.\n\nThis requirement applies to Ubuntu operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals shall be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.
Check_content: Verify the system commands contained in the following directories have mode "0755" or less permissive.\n\nCheck that the system command files contained in the following directories have mode "0755" or less permissive with the following command:\n\n# find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin -perm /022 | xargs ls -la\n\nIf any system commands are found to be group-writable or world-writable, this is a finding.
Fixtext: Configure the system commands to be protected from unauthorized access. \n\nRun the following command, replacing "[FILE]" with any system command with a mode more permissive than "0755".\n\n# sudo chmod 0755 [FILE]

Rule ID: SV-90293r2_rule
Severity: medium
Rule Title: System commands must be owned by root.
Description: If the Ubuntu operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process.\n\nThis requirement applies to Ubuntu operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals shall be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.
Check_content: Verify the system commands contained in the following directories are owned by "root".\n\nCheck that the system command files contained in the following 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 | xargs ls -la\n\nIf any system commands are returned, this is a finding.
Fixtext: Configure the system commands to be protected from unauthorized access. \n\nRun the following command, replacing "[FILE]" with any system command file not owned by "root".\n\n# sudo chown root [FILE]

Rule ID: SV-90295r2_rule
Severity: medium
Rule Title: System commands must be group-owned by root.
Description: If the Ubuntu operating system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process.\n\nThis requirement applies to Ubuntu operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals shall be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.
Check_content: Verify the system commands contained in the following directories are group-owned by "root".\n\nCheck that the system command files contained in the following 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 | xargs ls -la\n\nIf the command returns any files that are not group-owned by "root", and if they are not SGID and owned by a privileged group, this is a finding.
Fixtext: Configure the system commands to be protected from unauthorized access. \n\nRun the following command, replacing "[FILE]" with any system command file not group-owned by "root".\n\n# sudo chgrp root [FILE]

Rule ID: SV-90297r1_rule
Severity: medium
Rule Title: Audit records must contain information to establish what type of events occurred, the source of events, where events occurred, and the outcome of events.
Description: Without establishing what type of events occurred, the source of events, where events occurred, and the outcome of events, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.\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\nAssociating event types with detected events in the Ubuntu operating system audit logs provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured Ubuntu operating system.\n\n
Check_content: Verify the audit service is configured to produce audit records. \n\nCheck that the audit service is installed properly with the following command:\n\n# dpkg -l | grep auditd\n\nIf the "auditd" package is not installed, this is a finding.\n\nCheck that 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\nInstall the audit service (if the audit service is not already installed) with the following command:\n\n# sudo apt-get install auditd\n\nEnable the audit service with the following command:\n\n# sudo systemctl enable auditd.service\n\nRestart the audit service with the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90301r2_rule
Severity: medium
Rule Title: The Ubuntu operating system must allocate audit record storage capacity to store at least one weeks worth of audit records, when audit records are not immediately sent to a central audit record storage facility.
Description: In order to ensure Ubuntu operating systems have a sufficient storage capacity in which to write the audit logs, Ubuntu operating systems need to be able to allocate audit record storage capacity.\n\nThe task of allocating audit record storage capacity is usually performed during initial installation of the Ubuntu operating system.
Check_content: [u"Verify the Ubuntu operating system 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# df \u2013h /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#du \u2013sh [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. In normal circumstances, 10.0 GB of storage space for audit records will be sufficient.\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 "X" 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.

Rule ID: SV-90303r2_rule
Severity: medium
Rule Title: The Ubuntu operating system must notify the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) via email when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity.
Description: If security personnel are not notified immediately when storage volume reaches 75% utilization, they are unable to plan for audit record storage capacity expansion.
Check_content: Verify the Ubuntu operating system notifies the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) via email when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity.\n\nCheck that the Ubuntu operating system notifies the SA and ISSO (at a minimum) via email when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity with the following commands:\n\n#sudo grep space_left_action /etc/audit/auditd.conf\n\nspace_left_action email\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 parameter /etc/audit/auditd.conf\n\naction_mail_acct parameter root@localhost\n\nIf the space_left_action or the action_mail_accnt parameters are set to blanks, this is a finding.\n\nIf the space_left_action is set to "syslog", the system logs the event, this is not 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.\n\nThe action_mail_acct parameter, if missing, defaults to "root". If the "action_mail_acct parameter" is not set to the e-mail address of the system administrator(s) and/or ISSO, this is a finding.  \n\nNote: If the email address of the system administrator is on a remote system a mail package must be available.
Fixtext: Configure the operating system to immediately notify the SA and ISSO (at a minimum) via email when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity.\n\nEdit "/etc/audit/auditd.conf" and set the "space_left_action" parameter to "exec", "email", or "syslog". If the "space_left_action" parameter is set to "email" set the "action_mail_acct" parameter to an e-mail address for the System Administrator (SA) and Information System Security Officer (ISSO).

Rule ID: SV-90305r2_rule
Severity: medium
Rule Title: The System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) must be alerted of an audit processing failure event.
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.
Check_content: Verify that the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) are notified in the event of an audit processing failure.\n\nCheck that the Ubuntu operating system notifies the SA and ISSO (at a minimum) in the event of an audit processing failure with the following command:\n\n#sudo grep space_left_action /etc/audit/auditd.conf\n\naction_mail_acct = root\n\nIf the value of the "action_mail_acct" keyword is not set to "root" and/or other accounts for security personnel, the "action_mail_acct" keyword is missing, or the retuned line is commented out, this is a finding.
Fixtext: Configure "auditd" service to notify the System Administrator (SA) and Information System Security Officer (ISSO) in the event of an audit processing failure. \n\nEdit the following line in "/etc/audit/auditd.conf" to ensure that administrators are notified via email for those situations:\n\naction_mail_acct = root

Rule ID: SV-90307r1_rule
Severity: medium
Rule Title: The System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) must be alerted when the audit storage volume is full.
Description: It is critical that when the Ubuntu operating system is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit processing failures include: software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode.\n\nWhen availability is an overriding concern, other approved actions in response to an audit failure are as follows: \n\n1) If the failure was caused by the lack of audit record storage capacity, the Ubuntu operating system must continue generating audit records if possible (automatically restarting the audit service if necessary), overwriting the oldest audit records in a first-in-first-out manner.\n\n2) If audit records are sent to a centralized collection server and communication with this server is lost or the server fails, the Ubuntu operating system must queue audit records locally until communication is restored or until the audit records are retrieved manually. Upon restoration of the connection to the centralized collection server, action should be taken to synchronize the local audit data with the collection server.
Check_content: Verify that the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) are notified when the audit storage volume is full.\n\nCheck which action the Ubuntu operating system takes when the audit storage volume is full with the following command:\n\n# sudo grep max_log_file_action /etc/audit/auditd.conf\n\nmax_log_file_action=syslog\n\nIf the value of the "max_log_file_action" option is set to "ignore", "rotate", or "suspend", or the line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to notify the System Administrator (SA) and Information System Security Officer (ISSO) when the audit storage volume is full by configuring the "max_log_file_action" parameter in the "/etc/audit/auditd.conf" file with the a value of "syslog" or "keep_logs":\n\nmax_log_file_action=syslog

Rule ID: SV-90309r2_rule
Severity: medium
Rule Title: The audit system must take appropriate action when the audit storage volume is full.
Description: It is critical that when the Ubuntu operating system is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit processing failures include: software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode.\n\nWhen availability is an overriding concern, other approved actions in response to an audit failure are as follows: \n\n1) If the failure was caused by the lack of audit record storage capacity, the Ubuntu operating system must continue generating audit records if possible (automatically restarting the audit service if necessary), overwriting the oldest audit records in a first-in-first-out manner.\n\n2) If audit records are sent to a centralized collection server and communication with this server is lost or the server fails, the Ubuntu operating system must queue audit records locally until communication is restored or until the audit records are retrieved manually. Upon restoration of the connection to the centralized collection server, action should be taken to synchronize the local audit data with the collection server.
Check_content: Verify the Ubuntu operating system takes the appropriate action when the audit storage volume is full. \n\nCheck that the Ubuntu operating system takes the appropriate action when the audit storage volume is full with the following command:\n\n# sudo grep disk_full_action /etc/audit/auditd.conf\n\ndisk_full_action = HALT\n\nIf the value of the "disk_full_action" option is not "SYSLOG", "SINGLE", or "HALT", or the line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to shut down by default upon audit failure (unless availability is an overriding concern).\n\nAdd or update the following line (depending on configuration "disk_full_action" can be set to "SYSLOG" or "SINGLE" depending on configuration) in "/etc/audit/auditd.conf" file:\n\ndisk_full_action = HALT

Rule ID: SV-90311r2_rule
Severity: medium
Rule Title: The remote audit system must take appropriate action when audit storage is full.
Description: Information stored in one location is vulnerable to accidental or incidental deletion or alteration.\n\nOff-loading is a common process in information systems with limited audit storage capacity.
Check_content: Verify the action that the remote audit system takes when the storage volume becomes full.\n\nCheck the action that the remote audit system takes when the storage volume becomes full with the following command:\n\n# sudo grep disk_full /etc/audisp/audisp-remote.conf\n\ndisk_full_action = single\n\nIf the value of the "disk_full_action" option is not "syslog", "single", or "halt", or the line is commented out, this is a finding.
Fixtext: Configure the remote audit system to take an appropriate action when the audit storage is full.\n\nAdd, edit or uncomment the "disk_full_action" option in "/etc/audisp/audisp-remote.conf". Set it to "syslog", "single" or "halt" like the below example:\n\ndisk_full_action = single

Rule ID: SV-90313r1_rule
Severity: medium
Rule Title: Off-loading audit records to another system must be authenticated.
Description: Information stored in one location is vulnerable to accidental or incidental deletion or alteration.\n\nOff-loading is a common process in information systems with limited audit storage capacity.
Check_content: [u'Verify the audit system authenticates off-loading audit records to a different system.\n\nCheck that the off-loading of audit records to a different system is authenticated with the following command:\n\n# sudo grep enable /etc/audisp/audisp-remote.conf\n\nenable_krb5 = yes\n\nIf \u201cenable_krb5\u201d option is not set to "yes" or the line is commented out, this is a finding.
Fixtext: Configure the audit system to authenticate off-loading audit records to a different system.\n\nUncomment the "enable_krb5" option in "/etc/audisp/audisp-remote.conf" and set it to "yes". See the example below.\n\nenable_krb5 = yes

Rule ID: SV-90315r2_rule
Severity: medium
Rule Title: Audit logs must have a mode of 0600 or less permissive to prevent unauthorized read access.
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 Ubuntu operating system activity.\n\n
Check_content: Verify the audit logs have a mode of "0600" or less permissive.\n\nFirst determine 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 location of the audit log file, check if the audit log has a mode of "0600" or less permissive with the following command:\n\n# sudo stat -c "%a %n" /var/log/audit/audit.log\n\n600 /var/log/audit/audit.log\n\nIf the audit log has a mode more permissive than "0600", this is a finding.
Fixtext: Configure the audit log to be protected from unauthorized read access by setting the correct permissive mode with the following command:\n\n# sudo chmod 0600 [audit_log_file]\n\nReplace "[audit_log_file]" to the correct audit log path, by default this location is "/var/log/audit/audit.log".

Rule ID: SV-90317r2_rule
Severity: medium
Rule Title: Audit log directories must have a mode of 0750 or less permissive to prevent unauthorized read access.
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 Ubuntu operating system activity.\n\n
Check_content: Verify the audit log directories have a mode of "0750" or less permissive by first determining 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 location of the audit log, determine the directory where the audit logs are stored (ex: "/var/log/audit"). Run the following command to determine the permissions for the audit log folder:\n\n# sudo stat -c "%a %n" /var/log/audit\n750 /var/log/audit\n\nIf the audit log directory has a mode more permissive than "0750", this is a finding.
Fixtext: Configure the audit log directory to be protected from unauthorized read access by setting the correct permissive mode with the following command:\n\n# sudo chmod 0750 [audit_log_directory]\n\nReplace "[audit_log_directory]" to the correct audit log directory path, by default this location is "/var/log/audit".

Rule ID: SV-90319r2_rule
Severity: medium
Rule Title: Audit logs must be owned by root to prevent unauthorized read access.
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 Ubuntu operating system activity.\n\n
Check_content: Verify the audit logs are owned by "root". First determine 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 location of the audit log file, determine if the audit log is owned by "root" using the following command:\n\n# sudo ls -la /var/log/audit/audit.log\nrw------- 2 root root 8096 Jun 26 11:56 /var/log/audit/audit.log\n\nIf the audit log is not owned by "root", this is a finding.
Fixtext: Configure the audit log to be protected from unauthorized read access, by setting the correct owner as "root" with the following command:\n\n# sudo chown root [audit_log_file]\n\nReplace "[audit_log_file]" to the correct audit log path, by default this location is "/var/log/audit/audit.log".

Rule ID: SV-90321r2_rule
Severity: medium
Rule Title: Audit logs must be group-owned by root to prevent unauthorized read access.
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 Ubuntu operating system activity.\n\n
Check_content: Verify the audit logs are group-owned by "root". First determine 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 location of the audit log file, determine if the audit log is group-owned by "root" using the following command:\n\n# sudo ls -la /var/log/audit/audit.log\nrw------- 2 root root 8096 Jun 26 11:56 /var/log/audit/audit.log\n\nIf the audit log is not group-owned by "root", this is a finding.
Fixtext: Configure the audit log to be protected from unauthorized read access, by setting the correct group-owner as "root" with the following command:\n\n# sudo chgrp root [audit_log_file]\n\nReplace "[audit_log_file]" to the correct audit log path, by default this location is "/var/log/audit/audit.log".

Rule ID: SV-90323r2_rule
Severity: medium
Rule Title: Audit log directory must be owned by root to prevent unauthorized read access.
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 Ubuntu operating system activity.\n\n
Check_content: Verify the audit log directory is owned by "root" to prevent unauthorized read access.\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\nDetermine the audit log directory by using the output of the above command (ex: "/var/log/audit/"). Run the following command with the correct audit log directory path:\n\n# sudo ls -ld /var/log/audit\ndrwxr-x--- 2 root root 8096 Jun 26 11:56 /var/log/audit\n\nIf the audit log directory is not owned by "root", this is a finding.
Fixtext: Configure the audit log to be protected from unauthorized read access, by setting the correct owner as "root" with the following command:\n\n# sudo chown root [audit_log_directory]\n\nReplace "[audit_log_directory]" with the correct audit log directory path, by default this location is usually "/var/log/audit".

Rule ID: SV-90325r2_rule
Severity: medium
Rule Title: Audit log directory must be group-owned by root to prevent unauthorized read access.
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 Ubuntu operating system activity.\n\n
Check_content: Verify the audit log directory is group-owned by "root" to prevent unauthorized read access.\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\nDetermine the audit log directory by using the output of the above command (ex: "/var/log/audit/"). Run the following command with the correct audit log directory path:\n\n# sudo ls -ld /var/log/audit\ndrwxr-x--- 2 root root 8096 Jun 26 11:56 /var/log/audit\n\nIf the audit log directory is not group-owned by "root", this is a finding.
Fixtext: Configure the audit log to be protected from unauthorized read access, by setting the correct group-owner as "root" with the following command:\n\n# sudo chgrp root [audit_log_directory]\n\nReplace "[audit_log_directory]" with the correct audit log directory path, by default this location is usually "/var/log/audit".

Rule ID: SV-90327r1_rule
Severity: medium
Rule Title: The Ubuntu operating system must allow only the Information System Security Manager (ISSM) (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.
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. Misconfigured 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.
Check_content: Verify that the /etc/audit/audit.rule and /etc/audit/auditd.conf file have a mode of 0640 or less permissive by using the following command:\n\n# sudo ls -la /etc/audit/audit.rules\n\n-rw-r----- 1 root root 1280 Feb 16 17:09 audit.rules\n-rw-r----- 1 root root 621 Sep 22 2014 auditd.conf\n\nIf the "/etc/audit/audit.rule" or "/etc/audit/auditd.conf" file have a mode more permissive than "0640", this is a finding.
Fixtext: Configure the /etc/audit/audit.rule and /etc/audit/auditd.conf file to have a mode of 0640 with the following command:\n\n# sudo chmod 0640 /etc/audit/audit.rule\n# sudo chmod 0640 /etc/audit/audit.conf

Rule ID: SV-90329r2_rule
Severity: medium
Rule Title: The audit log files must be owned by root.
Description: Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the Ubuntu operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.\n\nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.
Check_content: Verify the audit log files are owned by "root". \n\nCheck where the audit logs are stored on the system using the following command:\n\n# sudo grep log_file /etc/audit/auditd.conf\nlog_file = /var/log/audit/audit.log\n\nUsing the audit log path from the command above, replace "[log_path]" in the following command:\n\n# sudo ls -la [log_path] | cut -d\' \' -f3\nroot\n\nIf the audit logs are not group-owned by "root", this is a finding.
Fixtext: Change the owner of the audit log file by running the following command:\n\nUse the following command to get the audit log path:\n\n# sudo grep log_file /etc/audit/auditd.conf\nlog_file = /var/log/audit/audit.log\n\nUsing the audit log path from the command above, replace "[log_path]" in the following command:\n\n# sudo chown root [log_path]

Rule ID: SV-90333r2_rule
Severity: medium
Rule Title: Audit tools must have 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\nUbuntu operating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the access to audit tools.\n\nAudit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.\n\n
Check_content: Verify the audit tools are protected from unauthorized access, deletion, or modification by checking the permissive mode.\n\nCheck the octal permission of each audit tool by running the following command:\n\n#stat -c "%a %n" /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/audispd /sbin/augenrules\n\n755 /sbin/augenrules\n\nIf any of the audit tools has a mode more permissive than "0755", this is a finding.
Fixtext: Configure the audit tools 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 permissive mode.

Rule ID: SV-90335r2_rule
Severity: medium
Rule Title: Audit tools must 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\nUbuntu operating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the access to audit tools.\n\nAudit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.\n\n
Check_content: Verify the audit tools are owned by "root" to prevent any unauthorized access, deletion, or modification.\n\nCheck the owner of each audit tool by running the following command:\n\n# ls -la /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/audispd /sbin/augenrules\n-rwxr-xr-x 1 root root 97128 Jan 18 2016 /sbin/augenrules\n\nIf any of the audit tools are not owned by "root", this is a finding.
Fixtext: Configure the audit tools to be owned by "root", by running the following command:\n\n# sudo chown root [audit_tool]\n\nReplace "[audit_tool]" with each audit tool not owned by "root".

Rule ID: SV-90337r2_rule
Severity: medium
Rule Title: Audit tools must 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\nUbuntu operating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the access to audit tools.\n\nAudit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.\n\n
Check_content: Verify the audit tools are group-owned by "root" to prevent any unauthorized access, deletion, or modification.\n\nCheck the owner of each audit tool by running the following commands:\n\n# ls -la /sbin/auditctl /sbin/aureport /sbin/ausearch /sbin/autrace /sbin/auditd /sbin/audispd /sbin/augenrules\n-rwxr-xr-x 1 root root 97128 Jan 18 2016 /sbin/augenrules\n\nIf any of the audit tools are not group-owned by "root", this is a finding.
Fixtext: Configure the audit tools to be group-owned by "root", by running the following command:\n\n# sudo chgrp root [audit_tool]\n\nReplace "[audit_tool]" with each audit tool not group-owned by "root".

Rule ID: SV-90339r2_rule
Severity: medium
Rule Title: The audit event multiplexor must be configured to off-load 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\nOff-loading is a common process in information systems with limited audit storage capacity.
Check_content: Verify the audit event multiplexor is configured to off-load audit records to a different system or storage media from the system being audited.\n\nCheck that the records are being off-loaded to a remote server with the following command:\n\n# sudo grep -i active /etc/audisp/plugins.d/au-remote.conf\n\nactive = yes\n\nIf "active" is not set to "yes", or the line is commented out, this is a finding.
Fixtext: Configure the audit event multiplexor to off-load audit records to a different system or storage media from the system being audited.\n\nSet the "active" option in "/etc/audisp/plugins.d/au-remote.conf" to "yes":\n\nactive = yes\n\nIn order for the changes to take effect, the audit daemon must be restarted. The audit daemon can be restarted with the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90341r4_rule
Severity: medium
Rule Title: The Ubuntu operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/passwd.
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).\n\n
Check_content: Verify the Ubuntu operating system generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd".\n\nCheck the auditing rules in "/etc/audit/audit.rules" with the following command:\n\n# sudo grep /etc/passwd /etc/audit/audit.rules\n\n-w /etc/passwd -p wa -k audit_rules_usergroup_modification\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/passwd".\n\nAdd or update the following file system rule to "/etc/audit/audit.rules":\n\n-w /etc/passwd -p wa -k identity\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90343r4_rule
Severity: medium
Rule Title: The Ubuntu operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/group.
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).\n\n
Check_content: Verify the Ubuntu operating system generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group".\n\nCheck the auditing rules in "/etc/audit/audit.rules" with the following command:\n\n# sudo grep /etc/group /etc/audit/audit.rules\n\n-w /etc/group -p wa -k audit_rules_usergroup_modification\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/group".\n\nAdd or update the following file system rule to "/etc/audit/audit.rules":\n\n-w /etc/group -p wa -k identity\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90345r4_rule
Severity: medium
Rule Title: The Ubuntu operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/gshadow.
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).\n\n
Check_content: Verify the Ubuntu operating system generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow".\n\nCheck the auditing rules in "/etc/audit/audit.rules" with the following command:\n\n# sudo grep /etc/gshadow /etc/audit/audit.rules\n\n-w /etc/gshadow -p wa -k audit_rules_usergroup_modification\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/gshadow".\n\nAdd or update the following file system rule to "/etc/audit/audit.rules":\n\n-w /etc/gshadow -p wa -k identity\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90347r4_rule
Severity: medium
Rule Title: The Ubuntu operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow.
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).\n\n
Check_content: Verify the Ubuntu operating system generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/shadow".\n\nCheck the auditing rules in "/etc/audit/audit.rules" with the following command:\n\n# sudo grep /etc/shadow /etc/audit/audit.rules\n\n-w /etc/shadow -p wa -k audit_rules_usergroup_modification\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/shadow".\n\nAdd or update the following file system rule to "/etc/audit/audit.rules":\n\n-w /etc/shadow -p wa -k identity\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90367r4_rule
Severity: medium
Rule Title: The Ubuntu operating system must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/security/opasswd.
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).\n\n
Check_content: Verify the Ubuntu operating system generates audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd".\n\nCheck the auditing rules in "/etc/audit/audit.rules" with the following command:\n\n# sudo grep /etc/security/opasswd /etc/audit/audit.rules\n\n-w /etc/security/opasswd -p wa -k audit_rules_usergroup_modification\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/security/opasswd".\n\nAdd or update the following file system rule to "/etc/audit/audit.rules":\n\n-w /etc/security/opasswd -p wa -k identity\n \nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90371r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the su command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates audit records when successful/unsuccessful attempts to use the "su" command occur.\n\nCheck for the following system call being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules": \n\n# sudo grep -iw /bin/su /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 path=/bin/su -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change\n-a always,exit -F arch=b64 path=/bin/su -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to generate audit records when successful/unsuccessful attempts to use the "su" command occur.\n\nAdd or update the following rule in "/etc/audit/audit.rules": \n\n-a always,exit -F arch=b32 path=/bin/su -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change\n-a always,exit -F arch=b64 path=/bin/su -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-priv_change\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90373r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the chfn command must generate an audit record.
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).\n\n
Check_content: Verify that an audit event is generated for any successful/unsuccessful use of the "chfn" command. \n\nCheck for the following system call being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep chfn /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 path=/usr/bin/chfn -F perm=x -F auid>=500 -F auid!=4294967295 -k privileged-chfn\n-a always,exit -F arch=b64 path=/usr/bin/chfn -F perm=x -F auid>=500 -F auid!=4294967295 -k privileged-chfn\n\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "passwd" command. Add or update the following rule in the "/etc/audit/audit.rules" file:\n\n-a always,exit -F arch=b32 path=/usr/bin/chfn -F perm=x -F auid>=500 -F auid!=4294967295 -k privileged-chfn\n-a always,exit -F arch=b64 path=/usr/bin/chfn -F perm=x -F auid>=500 -F auid!=4294967295 -k privileged-chfn\n\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90375r4_rule
Severity: low
Rule Title: Successful/unsuccessful uses of the mount command must generate an audit record.
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).\n\n
Check_content: Verify that an audit event is generated for any successful/unsuccessful use of the "mount" command.\n\nCheck for the following system call being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w mount /etc/audit/audit.rules\n\n-a always,exit -F arch=32 -S mount -F auid>=1000 -F auid!=4294967295 -k privileged-mount\n-a always,exit -F arch=64 -S mount -F auid>=1000 -F auid!=4294967295 -k privileged-mount\n\nIf the command does not return a line, or the line is commented out, this is a finding.
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/audit.rules" file:\n\n-a always,exit -F arch=32 -S mount -F auid>=1000 -F auid!=4294967295 -k privileged-mount\n-a always,exit -F arch=64 -S mount -F auid>=1000 -F auid!=4294967295 -k privileged-mount\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90377r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the umount command must generate an audit record.
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).\n\n
Check_content: Verify that an audit event is generated for any successful/unsuccessful use of the "umount" command.\n\nCheck for the following system call being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep umount /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 path=/bin/umount -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-mount\n-a always,exit -F arch=b64 path=/bin/umount -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-mount\n\nIf the command does not return a line, or the line is commented out, this is a finding.
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/audit.rules" file:\n\n-a always,exit -F arch=b32 path=/bin/umount -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-mount\n-a always,exit -F arch=b64 path=/bin/umount -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-mount\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90379r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the ssh-agent command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "ssh-agent" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep ssh-agent /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-ssh\n-a always,exit -F arch=b64 path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-ssh\n\nIf the command does not return a line, or the line is commented out, this is a finding.
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/audit.rules" file:\n\n-a always,exit -F arch=b32 path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-ssh\n-a always,exit -F arch=b64 path=/usr/bin/ssh-agent -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-ssh\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90387r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the ssh-keysign command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "ssh-keysign" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep ssh-keysign /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 path=/usr/lib/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-ssh\n-a always,exit -F arch=b64 path=/usr/lib/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-ssh\n\nIf the command does not return a line, or the line is commented out, this is a finding.
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/audit.rules" file:\n\n-a always,exit -F arch=b32 path=/usr/lib/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-ssh\n-a always,exit -F arch=b64 path=/usr/lib/openssh/ssh-keysign -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-ssh\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90389r2_rule
Severity: medium
Rule Title: The audit system must be configured to audit any usage of the insmod command.
Description: Without 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 records can be generated from various components within the information system (e.g., module or policy filter).\n\nThe list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records.\n\nDoD has defined the list of events for which the Ubuntu operating system will provide an audit record generation capability as the following: \n\n1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels);\n\n2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system;\n\n3) All account creations, modifications, disabling, and terminations; and \n\n4) All kernel module load, unload, and restart actions.\n\n
Check_content: Verify if the Ubuntu operating system is configured to audit the execution of the module management program "insmod", by running the following command:\n\n# sudo grep "/sbin/insmod" /etc/audit/audit.rules\n\n-w /sbin/insmod -p x -k modules\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to audit the execution of the module management program "insmod", by adding the following line to "/etc/audit/audit.rules":\n\n-w /sbin/insmod -p x -k modules\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90391r2_rule
Severity: medium
Rule Title: The audit system must be configured to audit any usage of the rmmod command.
Description: Without 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 records can be generated from various components within the information system (e.g., module or policy filter).\n\nThe list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records.\n\nDoD has defined the list of events for which the Ubuntu operating system will provide an audit record generation capability as the following: \n\n1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels);\n\n2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system;\n\n3) All account creations, modifications, disabling, and terminations; and \n\n4) All kernel module load, unload, and restart actions.\n\n
Check_content: Verify if the Ubuntu operating system is configured to audit the execution of the module management program "rmmod", by running the following command:\n\n# sudo grep "/sbin/rmmod" /etc/audit/audit.rules\n\n-w /sbin/rmmod -p x -k modules\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to audit the execution of the module management program "rmmod", by adding the following line to "/etc/audit/audit.rules":\n\n-w /sbin/rmmod -p x -k modules\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90393r2_rule
Severity: medium
Rule Title: The audit system must be configured to audit any usage of the modprobe command.
Description: Without 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 records can be generated from various components within the information system (e.g., module or policy filter).\n\nThe list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records.\n\nDoD has defined the list of events for which the Ubuntu operating system will provide an audit record generation capability as the following: \n\n1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels);\n\n2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system;\n\n3) All account creations, modifications, disabling, and terminations; and \n\n4) All kernel module load, unload, and restart actions.\n\n
Check_content: Verify if the Ubuntu operating system is configured to audit the execution of the module management program "modprobe", by running the following command:\n\n# sudo grep "/sbin/modprobe" /etc/audit/audit.rules\n\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.
Fixtext: Configure the Ubuntu operating system to audit the execution of the module management program "modprobe", by adding the following line to "/etc/audit/audit.rules":\n\n-w /sbin/modprobe -p x -k modules\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90395r2_rule
Severity: medium
Rule Title: The audit system must be configured to audit any usage of the kmod command.
Description: Without 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 records can be generated from various components within the information system (e.g., module or policy filter).\n\nThe list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records.\n\nDoD has defined the list of events for which the Ubuntu operating system will provide an audit record generation capability as the following: \n\n1) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels);\n\n2) Access actions, such as successful and unsuccessful logon attempts, privileged activities or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system;\n\n3) All account creations, modifications, disabling, and terminations; and \n\n4) All kernel module load, unload, and restart actions.\n\n
Check_content: Verify if the Ubuntu operating system is configured to audit the execution of the module management program "kmod", by running the following command:\n\n# sudo grep "/bin/kmod" /etc/audit/audit.rules\n\n-w /bin/kmod -p x -k modules\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to audit the execution of the module management program "kmod" by adding the following line to "/etc/audit/audit.rules":\n\n-w /bin/kmod -p x -k modules\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90397r3_rule
Severity: medium
Rule Title: The audit system must be configured to audit any usage of the setxattr system call.
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).\n\n
Check_content: Verify if the Ubuntu operating system is configured to audit the execution of the "setxattr" system call, by running the following command:\n\n# sudo grep -w setxattr /etc/audit/audit.rules\n\n\na always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\na always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n\n-a always,exit -F arch=b32 -S setxattr -F auid=0 -k perm_mod \n-a always,exit -F arch=b64 -S setxattr -F auid=0 -k perm_mod \n\nIf the command does not return all lines, or the lines are commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to audit the execution of the "setxattr" system call, by adding the following lines to "/etc/audit/audit.rules":\n\na always,exit -F arch=b32 -S setxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\na always,exit -F arch=b64 -S setxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n\n-a always,exit -F arch=b32 -S setxattr -F auid=0 -k perm_mod\n-a always,exit -F arch=b64 -S setxattr -F auid=0 -k perm_mod\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90399r3_rule
Severity: medium
Rule Title: The audit system must be configured to audit any usage of the lsetxattr system call.
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).\n\n
Check_content: Verify if the Ubuntu operating system is configured to audit the execution of the "lsetxattr" system call, by running the following command:\n\n# sudo grep -w lsetxattr /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n\n-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -k perm_mod \n-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -k perm_mod\n\nIf the command does not return all lines, or the lines are commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to audit the execution of the "lsetxattr" system call, by adding the following lines to "/etc/audit/audit.rules":\n\n-a always,exit -F arch=b32 -S lsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n-a always,exit -F arch=b64 -S lsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n\n-a always,exit -F arch=b32 -S lsetxattr -F auid=0 -k perm_mod \n-a always,exit -F arch=b64 -S lsetxattr -F auid=0 -k perm_mod\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90401r3_rule
Severity: medium
Rule Title: The audit system must be configured to audit any usage of the fsetxattr system call.
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).\n\n
Check_content: Verify if the Ubuntu operating system is configured to audit the execution of the "fsetxattr" system call, by running the following command:\n\n# sudo grep -w fsetxattr /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n-a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n\n-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -k perm_mod\n-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -k perm_mod\n\nIf the command does not return all lines, or the lines are commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to audit the execution of the "fsetxattr" system call, by adding the following lines to "/etc/audit/audit.rules":\n\n-a always,exit -F arch=b32 -S fsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n-a always,exit -F arch=b64 -S fsetxattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n\n-a always,exit -F arch=b32 -S fsetxattr -F auid=0 -k perm_mod\n-a always,exit -F arch=b64 -S fsetxattr -F auid=0 -k perm_mod\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90403r3_rule
Severity: medium
Rule Title: The audit system must be configured to audit any usage of the removexattr system call.
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).\n\n
Check_content: Verify if the Ubuntu operating system is configured to audit the execution of the "removexattr" system call, by running the following command:\n\n# sudo grep -w removexattr /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n-a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n\n-a always,exit -F arch=b32 -S removexattr -F auid=0 -k perm_mod\n-a always,exit -F arch=b64 -S removexattr -F auid=0 -k perm_mod \n\nIf the command does not return all lines, or the lines are commented out, this is a finding. 
Fixtext: Configure the Ubuntu operating system to audit the execution of the "removexattr" system call, by adding the following lines to "/etc/audit/audit.rules":\n\n-a always,exit -F arch=b32 -S removexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n-a always,exit -F arch=b64 -S removexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n\n-a always,exit -F arch=b32 -S removexattr -F auid=0 -k perm_mod\n-a always,exit -F arch=b64 -S removexattr -F auid=0 -k perm_mod \n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90405r3_rule
Severity: medium
Rule Title: The audit system must be configured to audit any usage of the lremovexattr system call.
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).\n\n
Check_content: Verify if the Ubuntu operating system is configured to audit the execution of the "lremovexattr" system call, by running the following command:\n\n# sudo grep -w lremovexattr /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n\n-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -k perm_mod\n-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -k perm_mod\n\nIf the command does not return all lines, or the lines are commented out, this is a finding. 
Fixtext: Configure the Ubuntu operating system to audit the execution of the "lremovexattr" system call, by adding the following lines to "/etc/audit/audit.rules":\n\n-a always,exit -F arch=b32 -S lremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n-a always,exit -F arch=b64 -S lremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n\n-a always,exit -F arch=b32 -S lremovexattr -F auid=0 -k perm_mod\n-a always,exit -F arch=b64 -S lremovexattr -F auid=0 -k perm_mod\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90407r4_rule
Severity: medium
Rule Title: The audit system must be configured to audit any usage of the fremovexattr system call.
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).\n\n
Check_content: Verify if the Ubuntu operating system is configured to audit the execution of the "fremovexattr" system call, by running the following command:\n\n# sudo grep -w fremovexattr /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n\n-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -k perm_mod\n-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -k perm_mod \n\nIf the command does not return all lines, or the lines are commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to audit the execution of the "fremovexattr" system call by adding the following lines to "/etc/audit/audit.rules":\n\n-a always,exit -F arch=b32 -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n-a always,exit -F arch=b64 -S fremovexattr -F auid>=1000 -F auid!=4294967295 -k perm_mod\n\n-a always,exit -F arch=b32 -S fremovexattr -F auid=0 -k perm_mod\n-a always,exit -F arch=b64 -S fremovexattr -F auid=0 -k perm_mod \n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90409r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the chown command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "chown" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w chown /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=4294967295 -k perm_chng\n-a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=4294967295 -k perm_chng\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chown" command by adding the following line to "/etc/audit/audit.rules":\n\n-a always,exit -F arch=b32 -S chown -F auid>=1000 -F auid!=4294967295 -k perm_chng\n-a always,exit -F arch=b64 -S chown -F auid>=1000 -F auid!=4294967295 -k perm_chng\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90411r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the fchown command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "fchown" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w fchown /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=4294967295 -k perm_mod\n-a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=4294967295 -k perm_mod\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful use of the "fchown" command by adding the following line to "/etc/audit/audit.rules": \n\n-a always,exit -F arch=b32 -S fchown -F auid>=1000 -F auid!=4294967295 -k perm_mod\n-a always,exit -F arch=b64 -S fchown -F auid>=1000 -F auid!=4294967295 -k perm_mod\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90413r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the fchownat command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "fchownat" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w fchownat /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=4294967295 -k perm_chng\n-a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=4294967295 -k perm_chng\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful use of the "fchownat" command by adding the following lines to "/etc/audit/audit.rules": \n\n-a always,exit -F arch=b32 -S fchownat -F auid>=1000 -F auid!=4294967295 -k perm_chng\n-a always,exit -F arch=b64 -S fchownat -F auid>=1000 -F auid!=4294967295 -k perm_chng\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90415r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the lchown command must generate an audit record.
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).\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "lchown" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w lchown /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=4294967295 -k perm_chng\n-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=4294967295 -k perm_chng\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful use of the "lchown" command by adding the following lines to "/etc/audit/audit.rules": \n\n-a always,exit -F arch=b32 -S lchown -F auid>=1000 -F auid!=4294967295 -k perm_chng\n-a always,exit -F arch=b64 -S lchown -F auid>=1000 -F auid!=4294967295 -k perm_chng\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90417r3_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the chmod command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "chmod" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w chmod /etc/audit/audit.rules\n\n-a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=4294967295 -k perm_chng\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful use of the "chmod" command by adding the following line to "/etc/audit/audit.rules":  \n\n-a always,exit -F arch=b64 -S chmod -F auid>=1000 -F auid!=4294967295 -k perm_chng\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90419r3_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the fchmod command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "fchmod" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w fchmod /etc/audit/audit.rules\n\n-a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=4294967295 -k perm_chng\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful use of the "fchmod" command by adding the following line to "/etc/audit/audit.rules":  \n\n-a always,exit -F arch=b64 -S fchmod -F auid>=1000 -F auid!=4294967295 -k perm_chng\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90421r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the fchmodat command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "fchmodat" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w fchmodat /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_chng\n-a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_chng\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful use of the "fchmodat" command by adding the following lines to "/etc/audit/audit.rules":  \n\n-a always,exit -F arch=b32 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_chng\n-a always,exit -F arch=b64 -S fchmodat -F auid>=1000 -F auid!=4294967295 -k perm_chng\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90423r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the open command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "open" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -iw open /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n\n-a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n\nIf the command does not return all lines, or the lines are commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful use of the "open" command. \n\nAdd or update the following rules in the "/etc/audit/audit.rules" file:\n\n-a always,exit -F arch=b32 -S open -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S open -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n\n-a always,exit -F arch=b32 -S open -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S open -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90425r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the truncate command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "truncate" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -iw truncate /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n\n-a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n\nIf the command does not return all lines, or the lines are commented out, this is a finding. 
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful use of the "truncate" command. \n\nAdd or update the following rules in the "/etc/audit/audit.rules" file:\n\n-a always,exit -F arch=b32 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S truncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n\n-a always,exit -F arch=b32 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S truncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90427r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the ftruncate command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "ftruncate" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -iw ftruncate /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n\n-a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n\nIf the command does not return all lines, or the lines are commented out, this is a finding. 
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful use of the "ftruncate" command. \n\nAdd or update the following rules in the "/etc/audit/audit.rules" file:\n\n-a always,exit -F arch=b32 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S ftruncate -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n\n-a always,exit -F arch=b32 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S ftruncate -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90429r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the creat command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "creat" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -iw creat /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n\n-a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n\nIf the command does not return all lines, or the lines are commented out, this is a finding. 
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful use of the "creat" command. \n\nAdd or update the following rules in the "/etc/audit/audit.rules" file:\n\n-a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n\n-a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90431r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the openat command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "openat" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -iw openat /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n\n-a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n\nIf the command does not return all lines, or the lines are commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful use of the "openat" command. \n\nAdd or update the following rules in the "/etc/audit/audit.rules" file:\n\n-a always,exit -F arch=b32 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S openat -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n\n-a always,exit -F arch=b32 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S openat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90433r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the open_by_handle_at command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "open_by_handle_at" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -iw open_by_handle_at /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n\n-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n\nIf the command does not return all lines, or the lines are commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful use of the "open_by_handle_at" command. \n\nAdd or update the following rules in the "/etc/audit/audit.rules" file:\n\n-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k perm_access\n\n-a always,exit -F arch=b32 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n-a always,exit -F arch=b64 -S open_by_handle_at -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k perm_access\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90435r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the sudo command must generate an audit record.
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).\n\n
Check_content: Verify that an audit event is generated for any successful/unsuccessful use of the "sudo" command. \n\nCheck for the following system call being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w sudo /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=4294967295 -k priv_cmd\n-a always,exit -F arch=b64 path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=4294967295 -k priv_cmd\n\nIf the command does not return a line, or the line is commented out, this is a finding.
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/audit.rules" file:\n\n-a always,exit -F arch=b32 path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=4294967295 -k priv_cmd\n-a always,exit -F arch=b64 path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=4294967295 -k priv_cmd\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90437r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the sudoedit command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "sudoedit" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w sudoedit /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=4294967295 -k priv_cmd\n-a always,exit -F arch=b64 path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=4294967295 -k priv_cmd\n\nIf the command does not return a line, or the line is commented out, this is a finding.
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/audit.rules" file:\n\n-a always,exit -F -arch=b32 path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=4294967295 -k priv_cmd\n-a always,exit -F -arch=b64 path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=4294967295 -k priv_cmd\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90439r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the chsh command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "chsh" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w chsh /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=4294967295 -k priv_cmd\n-a always,exit -F arch=b64 path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=4294967295 -k priv_cmd\n\nIf the command does not return a line, or the line is commented out, this is a finding.
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/audit.rules" file:\n\n-a always,exit -F arch=b32 path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=4294967295 -k priv_cmd\n-a always,exit -F arch=b64 path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=4294967295 -k priv_cmd\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90441r5_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the newgrp command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "newgrp" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w newgrp /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=4294967295 -k priv_cmd\n-a always,exit -F arch=b64 path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=4294967295 -k priv_cmd\n\nIf the command does not return a line, or the line is commented out, this is a finding.\n\n\n
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/audit.rules" file:\n\n-a always,exit -F arch=b32 path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=4294967295 -k priv_cmd\n-a always,exit -F arch=b64 path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=4294967295 -k priv_cmd\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90445r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the apparmor_parser command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "apparmor_parser" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w apparmor_parser /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 path=/sbin/apparmor_parser -F perm=x -F auid>=1000 -F auid!=4294967295 -k perm_chng\n-a always,exit -F arch=b64 path=/sbin/apparmor_parser -F perm=x -F auid>=1000 -F auid!=4294967295 -k perm_chng\n\nIf the command does not return a line, or the line is commented out, this is a finding.
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/audit.rules" file:\n\n-a always,exit -F arch=b32 path=/sbin/apparmor_parser -F perm=x -F auid>=1000 -F auid!=4294967295 -k perm_chng\n-a always,exit -F arch=b64 path=/sbin/apparmor_parser -F perm=x -F auid>=1000 -F auid!=4294967295 -k perm_chng\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90447r4_rule 
Severity: medium
Rule Title: Successful/unsuccessful uses of the setfacl command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "setfacl" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w setfacl /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=4294967295 -k perm_chng\n-a always,exit -F arch=b64 path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=4294967295 -k perm_chng\n\n\nIf the command does not return a line, or the line is commented out, this is a finding.
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/audit.rules" file:\n\n-a always,exit -F arch=b32 path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=4294967295 -k perm_chng\n-a always,exit -F arch=b64 path=/usr/bin/setfacl -F perm=x -F auid>=1000 -F auid!=4294967295 -k perm_chng\n\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90449r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the chacl command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "chacl" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w chacl /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=4294967295 -k perm_chng\n-a always,exit -F arch=b64 path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=4294967295 -k perm_chng\n\nIf the command does not return a line, or the line is commented out, this is a finding.
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/audit.rules" file:\n\n-a always,exit -F arch=b32 path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=4294967295 -k perm_chng\n-a always,exit -F arch=b64 path=/usr/bin/chacl -F perm=x -F auid>=1000 -F auid!=4294967295 -k perm_chng\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90451r3_rule
Severity: medium
Rule Title: Successful/unsuccessful modifications to the tallylog file must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful modifications to the "tallylog" file occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w tallylog /etc/audit/audit.rules\n\n-w /var/log/tallylog -p wa -k logins\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful modifications to the "tallylog" file occur. \n\nAdd or update the following rules in the "/etc/audit/audit.rules" file:\n\n-w /var/log/tallylog -p wa -k logins\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90453r3_rule
Severity: medium
Rule Title: Successful/unsuccessful modifications to the faillog file must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful modifications to the "faillog" file occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w faillog /etc/audit/audit.rules\n\n-w /var/log/faillog -p wa -k logins\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful modifications to the "faillog" file occur. \n\nAdd or update the following rules in the "/etc/audit/audit.rules" file:\n\n-w /var/log/faillog -p wa -k logins\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90455r3_rule
Severity: medium
Rule Title: Successful/unsuccessful modifications to the lastlog file must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful modifications to the "lastlog" file occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w lastlog /etc/audit/audit.rules\n\n-w /var/log/lastlog -p wa -k logins\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful modifications to the "lastlog" file occur. \n\nAdd or update the following rules in the "/etc/audit/audit.rules" file:\n\n-w /var/log/lastlog -p wa -k logins\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90457r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the passwd command must generate an audit record.
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).\n\n
Check_content: Verify that an audit event is generated for any successful/unsuccessful use of the "passwd" command. \n\nCheck for the following system call being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w passwd /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-passwd\n-a always,exit -F arch=b64 path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-passwd\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "passwd" command. Add or update the following rules in the "/etc/audit/audit.rules" file:\n\n-a always,exit -F arch=b32 path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-passwd\n-a always,exit -F arch=b64 path=/usr/bin/passwd -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-passwd\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90459r3_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the unix_update command must generate an audit record.
Description: Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.\n\nAt a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.\n\n
Check_content: Verify that an audit event is generated for any successful/unsuccessful use of the "unix_update" command.\n\nCheck for the following system call being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w "unix_update" /etc/audit/audit.rules\n\n-a always,exit -F path=/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-unix-update\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "unix_update" command. Add or update the following rules in the "/etc/audit/audit.rules" file:\n\n-a always,exit -F path=/sbin/unix_update -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-unix-update\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90461r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the gpasswd command must generate an audit record.
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).\n\n
Check_content: Verify that an audit event is generated for any successful/unsuccessful use of the "gpasswd" command. \n\nCheck for the following system call being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w gpasswd /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-gpasswd\n-a always,exit -F arch=b64 path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-gpasswd\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "gpasswd" command. Add or update the following rules in the "/etc/audit/audit.rules" file:\n\n-a always,exit -F arch=b32 path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-gpasswd\n-a always,exit -F arch=b64 path=/usr/bin/gpasswd -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-gpasswd\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90463r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the chage command must generate an audit record.
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).\n\n
Check_content: Verify that an audit event is generated for any successful/unsuccessful use of the "chage" command.\n\nCheck for the following system call being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w chage /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-chage\n-a always,exit -F arch=b64 path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-chage\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "chage" command. Add or update the following rules in the "/etc/audit/audit.rules" file:\n\n-a always,exit -F arch=b32 path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-chage\n-a always,exit -F arch=b64 path=/usr/bin/chage -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-chage\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90465r4_rule 
Severity: medium
Rule Title: Successful/unsuccessful uses of the usermod command must generate an audit record.
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).\n\n
Check_content: Verify that an audit event is generated for any successful/unsuccessful use of the "usermod" command.\n\nCheck for the following system call being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w usermod /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-usermod\n-a always,exit -F arch=b64 path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-usermod\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "usermod" command. Add or update the following rules in the "/etc/audit/audit.rules" file:\n\n-a always,exit -F arch=b32 path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-usermod\n-a always,exit -F arch=b64 path=/usr/sbin/usermod -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-usermod\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90467r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the crontab command must generate an audit record.
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).\n\n
Check_content: Verify that an audit event is generated for any successful/unsuccessful use of the "crontab" command.\n\nCheck for the following system call being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w crontab /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-crontab\n-a always,exit -F arch=b64 path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-crontab\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "crontab" command. Add or update the following rules in the "/etc/audit/audit.rules" file:\n\n-a always,exit -F arch=b32 path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-crontab\n-a always,exit -F arch=b64 path=/usr/bin/crontab -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-crontab\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90469r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the pam_timestamp_check command must generate an audit record.
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).\n\n
Check_content: Verify that an audit event is generated for any successful/unsuccessful use of the "pam_timestamp_check" command.\n\nCheck for the following system call being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w pam_timestamp_check /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-pam_timestamp_check\n-a always,exit -F arch=b64 path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-pam_timestamp_check\n\nIf the above command does not return the exact same output displayed in the example, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful uses of the "pam_timestamp_check" command. Add or update the following rules in the "/etc/audit/audit.rules" file:\n\n-a always,exit -F arch=b32 path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-pam_timestamp_check\n-a always,exit -F arch=b64 path=/usr/sbin/pam_timestamp_check -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged-pam_timestamp_check\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90471r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the init_module command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "init_module" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w "init_module" /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 -S init_module -F auid>=1000 -F auid!=4294967295 -k module_chng\n-a always,exit -F arch=b64 -S init_module -F auid>=1000 -F auid!=4294967295 -k module_chng\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful use of the "init_module" command. \n\nAdd or update the following rules in the "/etc/audit/audit.rules" file:\n\n-a always,exit -F arch=b32 -S init_module -F auid>=1000 -F auid!=4294967295 -k module_chng\n-a always,exit -F arch=b64 -S init_module -F auid>=1000 -F auid!=4294967295 -k module_chng\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90473r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the finit_module command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "finit_module" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w "finit_module" /etc/audit/audit.rules\n-a always,exit -F arch=b32 -S finit_module -F auid>=1000 -F auid!=4294967295 -k module_chng\n-a always,exit -F arch=b64 -S finit_module -F auid>=1000 -F auid!=4294967295 -k module_chng\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful use of the "finit_module" command. \n\nAdd or update the following rules in the "/etc/audit/audit.rules" file:\n\n-a always,exit -F arch=b32 -S finit_module -F auid>=1000 -F auid!=4294967295 -k module_chng\n-a always,exit -F arch=b64 -S finit_module -F auid>=1000 -F auid!=4294967295 -k module_chng\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90475r4_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the delete_module command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "delete_module" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w "delete_module" /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 -S delete_module -F auid>=1000 -F auid!=4294967295 -k module_chng\n-a always,exit -F arch=b64 -S delete_module -F auid>=1000 -F auid!=4294967295 -k module_chng\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the audit system to generate an audit event for any successful/unsuccessful use of the "delete_module" command. \n\nAdd or update the following rules in the "/etc/audit/audit.rules" file:\n\n-a always,exit -F arch=b32 -S delete_module -F auid>=1000 -F auid!=4294967295 -k module_chng\n-a always,exit -F arch=b64 -S delete_module -F auid>=1000 -F auid!=4294967295 -k module_chng\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-90477r2_rule
Severity: high
Rule Title: The telnet package must not be installed.
Description: It is detrimental for Ubuntu 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\nUbuntu operating 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.\n\n
Check_content: Verify that the telnet package is not installed on the Ubuntu operating system.\n\nCheck that the telnet daemon is not installed on the Ubuntu operating system by running the following command:\n\n# sudo apt list telnetd\n\nIf the package is installed, this is a finding.
Fixtext: Remove the telnet package from the Ubuntu operating system by running the following command:\n\n# sudo apt-get remove telnetd

Rule ID: SV-90479r2_rule
Severity: high
Rule Title: The Network Information Service (NIS) package must not be installed.
Description: Removing the Network Information Service (NIS) package decreases the risk of the accidental (or intentional) activation of NIS or NIS+ services.
Check_content: Verify that the Network Information Service (NIS) package is not installed on the Ubuntu operating system.\n\nCheck to see if the NIS package is installed with the following command:\n\n#  sudo apt list nis\n\nIf the NIS package is installed, this is a finding.
Fixtext: Configure the Ubuntu operating system to disable non-essential capabilities by removing the Network Information Service (NIS) package from the system with the following command:\n\n# sudo apt-get remove nis

Rule ID: SV-90481r2_rule
Severity: high
Rule Title: The rsh-server package must not be installed.
Description: It is detrimental for Ubuntu 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\nUbuntu operating 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\nThe rsh-server service provides an unencrypted remote access service that does not provide for the confidentiality and integrity of user passwords or the remote session and has very weak authentication.\n\nIf a privileged user were to log on using this service, the privileged user password could be compromised.
Check_content: Verify that the rsh-server package is not installed on the Ubuntu operating system.\n\nCheck to see if the rsh-server package is installed with the following command:\n\n# sudo apt list rsh-server\n\nIf the rsh-server package is installed, this is a finding.
Fixtext: Configure the Ubuntu operating system to disable non-essential capabilities by removing the rsh-server package from the system with the following command:\n\n# sudo apt-get remove rsh-server

Rule ID: SV-90483r2_rule
Severity: medium
Rule Title: An application firewall must be installed.
Description: Uncomplicated Firewall provides a easy and effective way to block/limit remote access to the system, via ports, services and protocols.\n\nRemote 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, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.\n\nUbuntu operating system 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).
Check_content: Verify that the Uncomplicated Firewall is installed.\n\nCheck that the Uncomplicated Firewall is installed with the following command:\n\n# sudo apt list ufw\n\nii  ufw         0.35-0Ubuntu2 [installed]\n\nIf the "ufw" package is not installed, ask the System Administrator if another application firewall is installed. If no application firewall is installed this is a finding.
Fixtext: Install Uncomplicated Firewall with the following command:\n\n# sudo apt-get install ufw

Rule ID: SV-90485r2_rule
Severity: medium
Rule Title: An application firewall must be enabled on the system.
Description: Firewalls protect computers from network attacks by blocking or limiting access to open network ports. Application firewalls limit which applications are allowed to communicate over the network.
Check_content: Verify the Uncomplicated Firewall is enabled on the system by running the following command:\n\n# sudo systemctl is-enabled ufw\n\nenabled\n\nIf the above command returns the status as "disabled", this is a finding.\n\nIf the Uncomplicated Firewall is not installed, ask the System Administrator if another application firewall is installed. If no application firewall is installed this is a finding.
Fixtext: Enable the Uncomplicated Firewall by using the following commands:\n\n# sudo systemctl start ufw\n\n# sudo systemctl enable ufw \n

Rule ID: SV-90487r2_rule
Severity: medium
Rule Title: An application firewall must employ a deny-all, allow-by-exception policy for allowing connections to other systems.
Description: Failure to restrict network connectivity only to authorized systems permits inbound connections from malicious systems. It also permits outbound connections that may facilitate exfiltration of DoD data.\n\n
Check_content: Verify the Uncomplicated Firewall is configured to employ a deny-all, allow-by-exception policy for allowing connections to other systems.\n\nCheck the Uncomplicated Firewall configuration with the following command:\n# sudo ufw status\nStatus: active\n\n     To                         Action      From\n     --                         ------      ----\n[ 1] 22                         LIMIT IN    Anywhere\n\nIf any services, ports, or applications are "allowed" and are not documented with the organization, this is a finding.
Fixtext: [u'Configure the Uncomplicated Firewall to employ a deny-all, allow-by-exception policy for allowing connections to other systems.\n\nRemove any service that is not needed or documented by the organization with the following command (replace [NUMBER] with the rule number):\n\n# sudo ufw delete [NUMBER]\n\nAnother option would be to set the Uncomplicated Firewall back to default with the following commands:\n\n# sudo ufw default deny incoming\n# sudo ufw default allow outgoing\n\nNote: UFW\u2019s defaults are to deny all incoming connections and allow all outgoing connections.

Rule ID: SV-90489r2_rule
Severity: medium
Rule Title: The Ubuntu operating system must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the Ports, Protocols, and Services Management (PPSM) Category Assignments List (CAL) and vulnerability assessments.
Description: In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols on information systems.\n\nUbuntu operating 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, the Ubuntu operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.
Check_content: Verify the Uncomplicated Firewall is configured to employ a deny-all, allow-by-exception policy for allowing connections to other systems.\n\nCheck the Uncomplicated Firewall configuration with the following command:\n# sudo ufw status\nStatus: active\n\n     To                         Action      From\n     --                         ------      ----\n[ 1] 22                         LIMIT IN    Anywhere\n\nIf any services, ports, or applications are "allowed" and are not documented with the organization, this is a finding.
Fixtext: ["Add/Modify the Ubuntu operating system's firewall settings and/or running services to comply with the Ports, Protocols, and Services Management (PPSM) Category Assignments List (CAL).

Rule ID: SV-90491r4_rule
Severity: medium
Rule Title: A sticky bit must be set 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.
Check_content: Verify that all world writable directories have the sticky bit set.\n\nCheck to see that all world writable directories have the sticky bit set by running the following command:\n\n# sudo find / -type d  \\( -perm -0002 -a ! -perm -1000 \\) -print 2>/dev/null\n\ndrwxrwxrwxt 7 root root 4096 Jul 26 11:19 /tmp\n\nIf any of the returned directories are world writable and do not have the sticky bit set, this is a finding.
Fixtext: Configure all world writable directories have the sticky bit set to prevent unauthorized and unintended information transferred via shared system resources.\n\nSet the sticky bit on all world writable directories using the command, replace "[World-Writable Directory]" with any directory path missing the sticky bit:\n\n# sudo chmod 1777 [World-Writable Directory]

Rule ID: SV-90493r2_rule
Severity: medium
Rule Title: The Ubuntu operating system must compare internal information system clocks at least every 24 hours with a server which is synchronized to an authoritative time source, such as the United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS).
Description: Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside the configured acceptable allowance (drift) may be inaccurate.\n\nSynchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network.\n\nOrganizations should consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints).
Check_content: The system clock must be configured to compare the system clock at least every 24 hours to the authoritative time source.\n\nNote: If the system is not networked this item is Not Applicable.\n\nCheck the value of "maxpoll" in the "/etc/ntp.conf" file with the following command:\n\n# sudo  grep -i maxpoll /etc/ntp.conf\nmaxpoll = 17\n\nIf "maxpoll" is not set to "17" or does not exist, this is a finding.\n\nVerify that the "ntp.conf" file is configured to an authoritative DoD time source by running the following command:\n\n# grep -i server /etc/ntp.conf\nserver 0.us.pool.ntp.org iburst\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.
Fixtext: Note: If the system is not networked this item is Not Applicable.\n\nTo configure the system clock to compare the system clock at least every 24 hours to the authoritative time source, edit the "/etc/ntp.conf" file. Add or correct the following lines, by replacing "[source]" in the following line with an authoritative DoD time source.\n\nmaxpoll = 17\nserver [source] iburst\n\nIf the "NTP" service was running and the value of "maxpoll" or "server" was updated then the service must be restarted using the following command:\n\n# sudo systemctl restart ntp.service\n\nIf the "NTP" service was not running then it must be started.

Rule ID: SV-90495r2_rule
Severity: medium
Rule Title: The Ubuntu operating system must synchronize internal information system clocks to the authoritative time source when the time difference is greater than one second.
Description: Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events.\n\nSynchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. Organizations should consider setting time periods for different types of systems (e.g., financial, legal, or mission-critical systems).\n\nOrganizations should 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 in order to determine the time difference.
Check_content: Verify that Network Time Protocol (NTP) is running in continuous mode.\n\nCheck that NTP is running in continuous mode with the following command:\n\n# grep ntpdate /etc/init.d/ntpd\n\n  if ntpdate -u -s -b -p 4 -t 5 $NTPSERVER ; then\n\nIf the option "-q" is present, this is a finding.
Fixtext: The Network Time Protocol (NTP) will run in continuous mode by default. If the query only option (-q) has been added to the ntpdate command in /etc/init.d/ntpd it must be removed.

Rule ID: SV-90497r2_rule   todo?
Severity: medium  
Rule Title: The Ubuntu operating system 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 the Ubuntu operating system 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.
Check_content: The time zone must be configured to use Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). To verify run the following command. \n\n# sudo timedatectl status | grep -i "time zone"\nTime zone: UTC (UTC, +0000)\n\nIf "Time zone" is not set to UTC or GMT, this is a finding.
Fixtext: To configure the system time zone to use Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT), run the following command replacing [ZONE] with UTC or GMT.\n\n# sudo timedatectl set-timezone [ZONE]

Rule ID: SV-90499r2_rule
Severity: medium
Rule Title: The Ubuntu operating system must implement non-executable data to protect its memory from unauthorized code execution.
Description: Some adversaries launch attacks with the intent of executing code in non-executable regions of memory or in memory locations that are prohibited. Security safeguards employed to protect memory include, for example, data execution prevention and address space layout randomization. Data execution prevention safeguards can either be hardware-enforced or software-enforced with hardware providing the greater strength of mechanism.\n\nExamples of attacks are buffer overflow attacks.
Check_content: Verify the NX (no-execution) bit flag is set on the system.\n\nCheck that the no-execution bit flag is set with the following commands:\n\n# dmesg | grep NX\n\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# less /proc/cpuinfo | grep -i flags\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: The NX bit execute protection must be enabled in the system BIOS.

Rule ID: SV-90501r2_rule
Severity: medium
Rule Title: The Ubuntu operating system 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 non-executable regions of memory or in memory locations that are prohibited. Security safeguards employed to protect memory include, for example, data execution prevention and address space layout randomization. Data execution prevention safeguards can either be hardware-enforced or software-enforced with hardware providing the greater strength of mechanism.\n\nExamples of attacks are buffer overflow attacks.
Check_content: Verify the Ubuntu operating system implements address space layout randomization (ASLR).\n\nCheck that ASLR is configured on the system with the following command:\n\n# sudo sysctl kernel.randomize_va_space\n\nkernel.randomize_va_space = 2\n\nIf nothing is returned; we must verify the kernel parameter "randomize_va_space" is set to "2" with the following command:\n\n# kernel.randomize_va_space" /etc/sysctl.conf /etc/sysctl.d/*\n\nkernel.randomize_va_space = 2\n\nIf "kernel.randomize_va_space" is not set to "2", this is a finding.
Fixtext: Configure the operating system implement virtual address space randomization.\n\nSet the system to the required kernel parameter by adding the following line to "/etc/sysctl.conf" (or modify the line to have the required value):\n\nkernel.randomize_va_space=2

Rule ID: SV-90503r1_rule
Severity: high
Rule Title: The Ubuntu operating system must enforce SSHv2 for network access to all accounts.
Description: A replay attack may enable an unauthorized user to gain access to the Ubuntu operating system. Authentication sessions between the authenticator and the Ubuntu operating system validating the user credentials must not be vulnerable to a replay attack.\n\nAn authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message.\n\nA privileged account is any information system account with authorizations of a privileged user.\n\nTechniques 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\n
Check_content: Verify that the Ubuntu operating system enforces SSH protocol 2 for network access.\n\nCheck the protocol versions that SSH allows with the following command:\n\n#grep -i protocol /etc/ssh/sshd_config\n\nProtocol 2\n\nIf the returned line allows for use of protocol "1", is commented out, or the line is missing, this is a finding.
Fixtext: Configure the Ubuntu operating system to enforce SSHv2 for network access to all accounts.\n\nAdd or update the following line in the "/etc/ssh/sshd_config" file:\n\nProtocol 2\n\nRestart the ssh service.\n\n# systemctl restart sshd.service

Rule ID: SV-90505r4_rule
Severity: medium
Rule Title: The Ubuntu operating system must display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system via a ssh logon and the user must acknowledge the usage conditions and take explicit actions to log on for further access.
Description: Display of a standardized and approved use notification before granting access to the Ubuntu 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 Ubuntu operating systems:\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."
Check_content: [u'Verify the Ubuntu operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the Ubuntu operating system via a ssh logon.\n\nCheck that the Ubuntu operating system displays the Standard Mandatory DoD Notice and Consent Banner before granting access to the Ubuntu operating system via a ssh logon with the following command:\n\n# grep -i banner /etc/ssh/sshd_config\n\nBanner=/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 this is a finding.\n\nCheck the specified banner file to check that it matches the Standard Mandatory DoD Notice and Consent Banner exactly:\n\n\u201cYou 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.\u201d\n\nIf the banner text does not match the Standard Mandatory DoD Notice and Consent Banner exactly, this is a finding.
Fixtext: Configure the Ubuntu operating system to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system via SSH logon.\n\nEdit the SSH daemon configuration "/etc/ssh/sshd_config" file. Uncomment the banner keyword and configure it to point to the file that contains the correct banner. An example of this configure is below:\n\nBanner=/etc/issue.net\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\nThe SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command:\n\n# sudo systemctl restart sshd.service

Rule ID: SV-90507r2_rule
Severity: medium
Rule Title: The Ubuntu operating system must not permit direct logons to the root account using remote access via SSH.
Description: Even though the communications channel may be encrypted, an additional layer of security is gained by extending the policy of not logging on directly as root. In addition, logging on with a user-specific account provides individual accountability of actions performed on the system.
Check_content: Verify remote access using SSH prevents users from logging on directly as "root".\n\nCheck that SSH prevents users from logging on directly as "root" with the following command:\n\n# grep PermitRootLogin /etc/ssh/sshd_config\nPermitRootLogin no\n\nIf the "PermitRootLogin" keyword is set to "yes", is missing, or is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to stop users from logging on remotely as the "root" user via SSH.\n\nEdit the appropriate  "/etc/ssh/sshd_config" file to uncomment or add the line for the "PermitRootLogin" keyword and set its value to "no":\n\nPermitRootLogin no\n\nThe SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command:\n\n# sudo systemctl restart sshd.service

Rule ID: SV-90509r3_rule
Severity: medium
Rule Title: The Ubuntu operating system must implement DoD-approved encryption to protect the confidentiality of SSH connections.
Description: Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session.\n\nRemote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.\n\nEncryption provides a means to secure the remote connection to prevent unauthorized access to the data traversing the remote access connection (e.g., RDP), thereby providing a degree of confidentiality. The encryption strength of a mechanism is selected based on the security categorization of the information.
Check_content: Verify the SSH daemon is configured to only implement DoD-approved encryption.\n\nCheck the SSH daemon\'s current configured ciphers by running the following command:\n\n# sudo grep -i ciphers /etc/ssh/sshd_config | grep -v \'^#\'\n\nCiphers aes128-ctr,aes192-ctr,aes256-ctr\n\nIf any ciphers other than "aes128-ctr", "aes192-ctr", or "aes256-ctr" are listed, the "Ciphers" keyword is missing, or the retuned line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to allow the SSH daemon to only implement DoD-approved encryption.\n\nEdit the SSH daemon configuration "/etc/ssh/sshd_config" and remove any ciphers not starting with "aes" and remove any ciphers ending with "cbc". If necessary, append the "Ciphers" line to the "/etc/ssh/sshd_config" document.\n\nCiphers aes128-ctr,aes192-ctr,aes256-ctr\n\nThe SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command:\n\n# sudo systemctl restart sshd.service

Rule ID: SV-90511r2_rule
Severity: medium
Rule Title: The SSH daemon must be configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved 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, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.\n\nCryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash.\n\n
Check_content: Verify the SSH daemon is configured to only use Message Authentication Codes (MACs) that employ FIPS 140-2 approved ciphers.\n\nCheck that the SSH daemon is configured to only use MACs that employ FIPS 140-2 approved ciphers with the following command:\n\n# sudo grep -i macs /etc/ssh/sshd_config\nMACs hmac-sha2-256,hmac-sha2-512\n\nIf any ciphers other than "hmac-sha2-256" or "hmac-sha2-512" are listed, or the retuned line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to allow the SSH daemon to only use Message Authentication Codes (MACs) that employ FIPS 140-2 approved ciphers.\n\nEdit the "/etc/ssh/sshd_config" file to uncomment or add the line for the "MACs" keyword and set its value to "hmac-sha2-256" and/or "hmac-sha2-512":\n\nMACs hmac-sha2-256,hmac-sha2-512\n\nThe SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command:\n\n# sudo systemctl restart sshd.service

Rule ID: SV-90513r2_rule
Severity: high
Rule Title: Unattended or automatic login via ssh must not be allowed.
Description: Failure to restrict system access to authenticated users negatively impacts Ubuntu operating system security.
Check_content: Verify that unattended or automatic login via ssh is disabled.\n\nCheck that unattended or automatic login via ssh is disabled with the following command:\n\n# egrep \'(Permit(.*?)(Passwords|Environment))\' /etc/ssh/sshd_config\n\nPermitEmptyPasswords no\nPermitUserEnvironment no\n\nIf "PermitEmptyPasswords" or "PermitUserEnvironment" keywords are not set to "no", is missing completely, or they are commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system 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\nThe SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command:\n\n# sudo systemctl restart sshd.service

Rule ID: SV-90515r2_rule
Severity: medium
Rule Title: The system must display the date and time of the last successful account logon upon an SSH logon.
Description: Providing users with feedback on when account accesses via SSH last occurred facilitates user recognition and reporting of unauthorized account use.
Check_content: Verify SSH provides users with feedback on when account accesses last occurred.\n\nCheck that "PrintLastLog" keyword in the sshd daemon configuration file is used and set to "yes" with the following command:\n\n# grep PrintLastLog /etc/ssh/sshd_config\nPrintLastLog yes\n\nIf the "PrintLastLog" keyword is set to "no", is missing, or is commented out, this is a finding.
Fixtext: Add or edit the following lines in the "/etc/ssh/sshd_config" file:\n\nPrintLastLog yes\n\nThe SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command:\n\n# sudo systemctl restart sshd.service

Rule ID: SV-90517r3_rule
Severity: medium
Rule Title: The Ubuntu operating system must be configured so that all network connections associated with SSH traffic are terminated at the end of the session or after 10 minutes of inactivity, except to fulfill documented and validated mission requirements.
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 operating system functionality where the system owner, data owner, or organization requires additional assurance.
Check_content: Verify that all network connections associated with SSH traffic are automatically terminated at the end of the session or after "10" minutes of inactivity.\n\nCheck that the "ClientAliveInterval" variable is set to a value of "600" or less by performing the following command:\n\n# sudo grep -i clientalive /etc/ssh/sshd_config\n\nClientAliveInterval 600\n\nIf "ClientAliveInterval" has a value that is greater than "600" and is not documented with the Information System Security Officer (ISSO) as an operational requirement, or is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system 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\nModify or append the following lines in the "/etc/ssh/sshd_config" file replacing "[Interval]" with a value of "600" or less:\n\nClientAliveInterval 600\n\nIn order for the changes to take effect, the SSH daemon must be restarted.\n\n# sudo systemctl restart sshd.service

Rule ID: SV-90521r2_rule
Severity: medium
Rule Title: The SSH daemon must not allow authentication using known hosts authentication.
Description: Configuring this setting for the SSH daemon provides additional assurance that remote logon via SSH will require a password, even in the event of misconfiguration elsewhere.
Check_content: Verify the SSH daemon does not allow authentication using known hosts authentication.\n\nTo determine how the SSH daemon\'s "IgnoreUserKnownHosts" option is set, run the following command:\n\n# grep IgnoreUserKnownHosts /etc/ssh/sshd_config\n\nIgnoreUserKnownHosts yes\n\nIf the value is returned as "no", the returned line is commented out, or no output is returned, this is a finding.
Fixtext: Configure the SSH daemon to not allow authentication using known hosts authentication.\n\nAdd the following line in "/etc/ssh/sshd_config", or uncomment the line and set the value to "yes":\n\nIgnoreUserKnownHosts yes\n\nThe SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command:\n\n# sudo systemctl restart sshd.service\n

Rule ID: SV-90523r2_rule
Severity: medium
Rule Title: The SSH public host key files must have mode 0644 or less permissive.
Description: If a public host key file is modified by an unauthorized user, the SSH service may be compromised.
Check_content: Verify the SSH public host key files have mode "0644" or less permissive.\n\nNote: SSH public key files may be found in other directories on the system depending on the installation.\n\nThe following command will find all SSH public key files on the system:\n\n# ls -l /etc/ssh/*.pub\n\n-rw-r--r--  1 root  wheel  618 Nov 28 06:43 ssh_host_dsa_key.pub\n-rw-r--r--  1 root  wheel  347 Nov 28 06:43 ssh_host_key.pub\n-rw-r--r--  1 root  wheel  238 Nov 28 06:43 ssh_host_rsa_key.pub\n\nIf any key.pub file has a mode more permissive than "0644", this is a finding.
Fixtext: Note: SSH public key files may be found in other directories on the system depending on the installation. \n\nChange the mode of public host key files under "/etc/ssh" to "0644" with the following command:\n\n# sudo chmod 0644 /etc/ssh/*key.pub\n\nThe SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command:\n\n# sudo systemctl restart sshd.service

Rule ID: SV-90525r2_rule
Severity: medium
Rule Title: The SSH private host key files must have mode 0600 or less permissive.
Description: If an unauthorized user obtains the private SSH host key file, the host could be impersonated.
Check_content: Verify the SSH private host key files have mode "0600" or less permissive.\n\nCheck the mode of the private host key files under "/etc/ssh" file with the following command:\n\n# ls -alL /etc/ssh/ssh_host*key\n\n-rw-------  1 root  wheel  668 Nov 28 06:43 ssh_host_dsa_key\n-rw-------  1 root  wheel  582 Nov 28 06:43 ssh_host_key\n-rw-------  1 root  wheel  887 Nov 28 06:43 ssh_host_rsa_key\n\nIf any private host key file has a mode more permissive than "0600", this is a finding.
Fixtext: Configure the mode of SSH private host key files under "/etc/ssh" to "0600" with the following command:\n\n#sudo chmod 0600 /etc/ssh/ssh_host*key\n\nThe SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command:\n\n# sudo systemctl restart sshd.service

Rule ID: SV-90527r2_rule
Severity: medium
Rule Title: The SSH daemon must perform strict mode checking of home directory configuration files.
Description: If other users have access to modify user-specific SSH configuration files, they may be able to log on to the system as another user.
Check_content: Verify the SSH daemon performs strict mode checking of home directory configuration files.\n\nCheck that the SSH daemon performs strict mode checking of home directory configuration files with the following command:\n\n# grep StrictModes /etc/ssh/sshd_config\n\nStrictModes yes\n\nIf "StrictModes" is set to "no", is missing, or the returned line is commented out, this is a finding.
Fixtext: Configure SSH to perform strict mode checking of home directory configuration files. Uncomment the "StrictModes" keyword in "/etc/ssh/sshd_config" and set the value to "yes":\n\nStrictModes yes\n\nThe SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command:\n\n# sudo systemctl restart sshd.service

Rule ID: SV-90529r2_rule
Severity: medium
Rule Title: The SSH daemon must use privilege separation.
Description: SSH daemon privilege separation causes the SSH process to drop root privileges when not needed, which would decrease the impact of software vulnerabilities in the unprivileged section.
Check_content: Check that the SSH daemon performs privilege separation with the following command:\n\n# grep UsePrivilegeSeparation /etc/ssh/sshd_config \n\nUsePrivilegeSeparation yes\n\nIf the "UsePrivilegeSeparation" keyword is set to "no", is missing, or the returned line is commented out, this is a finding.
Fixtext: Configure SSH to use privilege separation. Uncomment the "UsePrivilegeSeparation" keyword in "/etc/ssh/sshd_config" and set the value to "yes":\n\nUsePrivilegeSeparation yes\n\nThe SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command:\n\n# sudo systemctl restart sshd.service

Rule ID: SV-90531r2_rule
Severity: medium
Rule Title: The SSH daemon must not allow compression or must only allow compression after successful authentication.
Description: If compression is allowed in an SSH connection prior to authentication, vulnerabilities in the compression software could result in compromise of the system from an unauthenticated connection, potentially with root privileges.
Check_content: Verify the SSH daemon performs compression after a user successfully authenticates.\n\nCheck that the SSH daemon performs compression after a user successfully authenticates with the following command:\n\n# grep Compression /etc/ssh/sshd_config\nCompression delayed\n\nIf the "Compression" keyword is set to "yes", is missing, or the returned line is commented out, this is a finding.
Fixtext: Configure SSH to use compression. Uncomment the "Compression" keyword in "/etc/ssh/sshd_config" on the system and set the value to "delayed" or "no":\n\nCompression no\n\nThe SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command:\n\n# sudo systemctl restart sshd.service

Rule ID: SV-90533r2_rule
Severity: high
Rule Title: Remote X connections for interactive users must be encrypted.
Description: Open X displays allow an attacker to capture keystrokes and execute commands remotely.
Check_content: Verify remote X connections for interactive users are encrypted.\n\nCheck that remote X connections are encrypted with the following command:\n\n# grep -i x11forwarding /etc/ssh/sshd_config\nX11Forwarding yes\n\nIf the "X11Forwarding" keyword is set to "no", is missing, or is commented out, this is a finding.
Fixtext: Configure SSH to encrypt connections for interactive users.\n\nEdit the "/etc/ssh/sshd_config" file to uncomment or add the line for the "X11Forwarding" keyword and set its value to "yes":\n\nX11Forwarding yes\n\nThe SSH daemon must be restarted for the changes to take effect. To restart the SSH daemon, run the following command:\n\n# sudo systemctl restart sshd.service

Rule ID: SV-90535r1_rule
Severity: medium
Rule Title: An application firewall must protect against or limit the effects of Denial of Service (DoS) attacks by ensuring the Ubuntu operating system is implementing rate-limiting measures on impacted network interfaces.
Description: DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity.\n\nThis requirement addresses the configuration of the Ubuntu operating system to mitigate the impact of DoS attacks that have occurred or are ongoing on system availability. For each system, known and potential DoS attacks must be identified and solutions for each type implemented. A variety of technologies exist to limit or, in some cases, eliminate the effects of DoS attacks (e.g., limiting processes or establishing memory partitions). Employing increased capacity and bandwidth, combined with service redundancy, may reduce the susceptibility to some DoS attacks.
Check_content: Verify an application firewall is configured to rate limit any connection to the system.\n\nCheck that the Uncomplicated Firewall is configured to rate limit any connection to the system with the following command:\n\n# sudo ufw show raw\n\nChain ufw-user-input (1 references)\npkts bytes target prot opt in out source destination\n0 0 ufw-user-limit all -- eth0 * 0.0.0.0/0 0.0.0.0/0\nctstate NEW recent: UPDATE seconds: 30 hit_count: 6 name: DEFAULT side:\nsource mask: 255.255.255.255\n\n0 0 ufw-user-limit-accept all -- eth0 * 0.0.0.0/0 0.0.0.0/0\n\n\nIf any service is not rate limited by the Uncomplicated Firewall, this is a finding.
Fixtext: Configure the application firewall to protect against or limit the effects of Denial of Service (DoS) attacks by ensuring the Ubuntu operating system is implementing rate-limiting measures on impacted network interfaces.\n\nRun the following command replacing "[service]" with the service that needs to be rate limited.\n\n# sudo ufw limit [service]\n\nOr rate-limiting can be done on an interface. An example of adding a rate-limit on the eth0 interface:\n\n# sudo ufw limit in on eth0

Rule ID: SV-90537r1_rule
Severity: high
Rule Title: All networked systems must have and implement SSH to protect the confidentiality and integrity of transmitted and received information, as well as information during preparation for transmission.
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, logical means (cryptography) do not have to be employed, and vice versa.\n\n
Check_content: Verify the "ssh" meta-package is installed.\n\nCheck that the ssh package is installed with the following command:\n\n$ dpkg -l | grep openssh\n\nii openssh-client 1:7.2p2-4Ubuntu2.1\namd64 secure shell (SSH) client, for secure access to\nremote machines\nii openssh-server 1:7.2p2-4Ubuntu2.1\namd64 secure shell (SSH) server, for secure access\nfrom remote machines\nii openssh-sftp-server 1:7.2p2-4Ubuntu2.1\namd64 secure shell (SSH) sftp server module, for SFTP\naccess from remote machines\n\nIf the "openssh" server package is not installed, this is a finding.\n\nCheck that the "sshd.service" is loaded and active with the following command:\n\n# systemctl status sshd.service | egrep -i "(active|loaded)"\n\nLoaded: loaded (/usr/lib/systemd/system/sshd.service; enabled)\nActive: active (running) since Sun 2016-06-05 23:46:29 CDT; 1h 4min ago\n\nIf "sshd.service" is not active or loaded, this is a finding.
Fixtext: Install the "ssh" meta-package on the system with the following command:\n\n# sudo apt install ssh\n\nEnable the "ssh" service to start automatically on reboot with the following command:\n\n# sudo systemctl enable sshd.service

Rule ID: SV-90539r2_rule
Severity: medium
Rule Title: The audit system must take appropriate action when the network cannot be used to off-load audit records.
Description: Information stored in one location is vulnerable to accidental or incidental deletion or alteration.\n\nOff-loading is a common process in information systems with limited audit storage capacity.
Check_content: [u'Verify that the audit system takes appropriate action if the network cannot be used to off-load audit records.\n\nCheck what action will take place if the network connection fails with the following command:\n\n# sudo grep -iw "network_failure" /etc/audisp/audisp-remote.conf\n\nnetwork_failure_action = stop\n\nIf the value of the \u201cnetwork_failure_action\u201d option is not "syslog", "single", or "halt", or the line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to take appropriate action when the network cannot be used to off-load audit records.\n\nAdd, edit or uncomment the "network_failure_action" option in "/etc/audisp/audisp-remote.conf". Set it to "syslog", "single" or "halt" like the below example:\n\nnetwork_failure_action = single

Rule ID: SV-90543r2_rule
Severity: medium
Rule Title: All remote access methods must be monitored.
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, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.\n\nAutomated monitoring of remote access sessions allows organizations to detect cyber attacks 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).
Check_content: Verify that the Ubuntu operating system monitors all remote access methods.\n\nCheck that remote access methods are being logged by running the following command:\n\n# grep -E \'(auth.*|authpriv.*|daemon.*)\' /etc/rsyslog.d/50-default.conf\n\nauth,authpriv.* /var/log/auth.log\ndaemon.notice /var/log/messages\n\nIf "auth.*", "authpriv.*" or "daemon.*" are not configured to be logged, this is a finding.
Fixtext: Configure the Ubuntu operating system 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.notice /var/log/messages\n\nThe "rsyslog" service must be restarted for the changes to take effect. To restart the "rsyslog" service, run the following command:\n\n# sudo systemctl restart rsyslog.service

Rule ID: SV-90545r2_rule
Severity: medium
Rule Title: Cron logging must be implemented.
Description: Cron logging can be used to trace the successful or unsuccessful execution of cron jobs. It can also be used to spot intrusions into the use of the cron facility by unauthorized and malicious users.
Check_content: Verify that "rsyslog" is configured to log cron events.\n\nCheck the configuration of "/etc/rsyslog.d/50-default.conf" for the cron facility with the following commands:\n\nNote: If another logging package is used, substitute the utility configuration file for "/etc/rsyslog.d/50-default.conf". \n\n# grep cron /etc/rsyslog.d/50-default.conf\n\ncron.*                          /var/log/cron.log\n\nIf the commands do not return a response, check for cron logging all facilities by inspecting the "/etc/rsyslog.d/50-default.con" file:\n\n# more /etc/rsyslog.conf\n\nLook for the following entry:\n\n*.* /var/log/messages\n\nIf "rsyslog" is not logging messages for the cron facility or all facilities, this is a finding.
Fixtext: Configure "rsyslog" to log all cron messages by adding or updating the following line to "/etc/rsyslog.d/50-default.conf":\n\ncron.* /var/log/cron.log\n\nNote: The line must be added before the following entry if it exists in "/etc/rsyslog.d/50-default.conf":\n\n*.* ~ # discards everything

Rule ID: SV-90547r1_rule
Severity: medium
Rule Title: Wireless network adapters must be disabled.
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 the Ubuntu operating system.\n\nThis requirement applies to wireless peripheral technologies (e.g., wireless mice, keyboards, displays, etc.) used with an Ubuntu 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 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 the Ubuntu operating system. 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.\n\n
Check_content: Verify that there are no wireless interfaces configured on the system.\n\nCheck that the system does not have active wireless interfaces with the following command:\n\nNote: This requirement is Not Applicable for systems that do not have physical wireless network radios.\n\n# ifconfig -a | more\n\neth0 Link encap:Ethernet HWaddr ff:ff:ff:ff:ff:ff \ninet addr:192.168.2.100 Bcast:192.168.2.255 Mask:255.255.255.0\n...\n\neth1 IEEE 802.11b ESSID:"tacnet"\nMode:Managed Frequency:2.412 GHz Access Point: 00:40:E7:22:45:CD\n...\n\nlo Link encap:Local Loopback \ninet addr:127.0.0.1 Mask:255.0.0.0\ninet6 addr: ::1/128 Scope:Host\n...\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: Configure the system to disable all wireless network interfaces with the following command:\n\n# sudo ifdown [ADAPTER_NAME]

Rule ID: SV-90549r2_rule
Severity: medium
Rule Title: The Ubuntu operating system must be configured to use TCP syncookies.
Description: DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. \n\nManaging excess capacity ensures that sufficient capacity is available to counter flooding attacks. Employing increased capacity and service redundancy may reduce the susceptibility to some DoS attacks. Managing excess capacity may include, for example, establishing selected usage priorities, quotas, or partitioning.
Check_content: Verify the Ubuntu operating system is configured to use TCP syncookies.\n\nCheck the value of 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.
Fixtext: Configure the Ubuntu operating system to use TCP syncookies, by running the following command:\n\n# sudo sysctl -w net.ipv4.tcp_syncookies=1\n\nIf "1" is not the system\'s default value then add or update the following line in "/etc/sysctl.conf" or in the appropriate file under "/etc/sysctl.d":\n\nnet.ipv4.tcp_syncookies = 1

Rule ID: SV-90551r2_rule
Severity: low
Rule Title: For Ubuntu operating systems using Domain Name Servers (DNS) resolution, at least two name servers must be configured.
Description: To provide availability for name resolution services, multiple redundant name servers are mandated. A failure in name resolution could lead to the failure of security functions requiring name resolution, which may include time synchronization, centralized authentication, and remote system logging.
Check_content: [u'Determine whether the Ubuntu operating system is using local or Domain Name Server (DNS) name resolution with the following command:\n\n# grep hosts /etc/nsswitch.conf\nhosts:   files dns\n\nIf the DNS entry is missing from the host\u2019s line in the "/etc/nsswitch.conf" file, the "/etc/resolv.conf" file must be empty.\n\nIf the "/etc/resolv.conf" file is not empty, this is a finding.\n\nIf the DNS entry is found on the host\u2019s line of the "/etc/nsswitch.conf" file, verify the Ubuntu operating system is configured to use two or more name servers for DNS resolution.\n\nDetermine the name servers used by the system with the following command:\n\n# sudo grep nameserver /etc/resolv.conf\n\nnameserver 192.168.1.2\n\nnameserver 192.168.1.3\n\nIf less than two lines are returned that are not commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to use two or more name servers for Domain Name Server (DNS) resolution.\n\nEdit the "/etc/resolv.conf" file to uncomment or add the two or more "nameserver" option lines with the IP address of local authoritative name servers. If local host resolution is being performed, the "/etc/resolv.conf" file must be empty. An empty "/etc/resolv.conf" file can be created as follows:\n\n# echo -n > /etc/resolv.conf

Rule ID: SV-90553r3_rule
Severity: medium
Rule Title: The Ubuntu operating system must not forward Internet Protocol version 4 (IPv4) source-routed packets.
Description: Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when IPv4 forwarding is enabled and the system is functioning as a router.
Check_content: Verify the Ubuntu operating system does not accept IPv4 source-routed packets.\n\nCheck the value of the accept source route variable with the following command:\n\n# sudo sysctl net.ipv4.conf.all.accept_source_route\n\nnet.ipv4.conf.all.accept_source_route=0\n\nIf the returned line does not have a value of "0", a line is not returned, or the returned line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to not forward Internet Protocol version 4 (IPv4) source-routed packets with the following command:\n\n# sudo sysctl -w net.ipv4.conf.all.accept_source_route=0\n\nIf "0" is not the system\'s default value then add or update the following line in "/etc/sysctl.conf" or in the appropriate file under "/etc/sysctl.d":\n\nnet.ipv4.conf.all.accept_source_route=0

Rule ID: SV-90555r3_rule
Severity: medium
Rule Title: The Ubuntu operating system must not forward Internet Protocol version 4 (IPv4) source-routed packets by default.
Description: Source-routed packets allow the source of the packet to suggest that routers forward the packet along a different path than configured on the router, which can be used to bypass network security measures. This requirement applies only to the forwarding of source-routed traffic, such as when IPv4 forwarding is enabled and the system is functioning as a router.
Check_content: Verify the Ubuntu operating system does not accept  Internet Protocol version 4 (IPv4) source-routed packets by default.\n\nCheck the value of the accept source route variable with the following command:\n\n# sudo sysctl net.ipv4.conf.default.accept_source_route\nnet.ipv4.conf.default.accept_source_route=0\n\nIf the returned line does not have a value of "0", a line is not returned, or the returned line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to not forward Internet Protocol version 4 (IPv4) source-routed packets by default with the following command:\n\n# sudo sysctl -w net.ipv4.conf.default.accept_source_route=0\n\nIf "0" is not the system\'s default value then add or update the following line in "/etc/sysctl.conf" or in the appropriate file under "/etc/sysctl.d":\n\nnet.ipv4.conf.default.accept_source_route=0

Rule ID: SV-90557r2_rule
Severity: medium
Rule Title: The Ubuntu operating system must not respond to Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) echoes sent to a broadcast address.
Description: Responding to broadcast Internet Control Message Protocol (ICMP) echoes facilitates network mapping and provides a vector for amplification attacks.
Check_content: Verify the Ubuntu operating system does not respond to IPv4 Internet Control Message Protocol (ICMP) echoes sent to a broadcast address.\n\nCheck the value of the "icmp_echo_ignore_broadcasts" variable with the following command:\n\n# sudo sysctl net.ipv4.icmp_echo_ignore_broadcasts\nnet.ipv4.icmp_echo_ignore_broadcasts=1\n\nIf the returned line does not have a value of "1", a line is not returned, or the retuned line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to not respond to Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) echoes sent to a broadcast address with the following command:\n\n# sudo sysctl -w net.ipv4.icmp_echo_ignore_broadcasts=1\n\nIf "1" is not the system\'s default value then add or update the following line in "/etc/sysctl.conf" or in the appropriate file under "/etc/sysctl.d":\n\nnet.ipv4.icmp_echo_ignore_broadcasts=1

Rule ID: SV-90559r3_rule
Severity: medium
Rule Title: The Ubuntu operating system must prevent Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages from being accepted.
Description: Internet Control Message Protocol (ICMP) redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the host's route table and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle attack.
Check_content: Verify the Ubuntu operating system will not accept IPv4 Internet Control Message Protocol (ICMP) redirect messages.\n\nCheck the value of the default "accept_redirects" variables with the following command:\n\n# sudo sysctl net.ipv4.conf.default.accept_redirects\n\nnet.ipv4.conf.default.accept_redirects=0\n\nIf the returned line does not have a value of "0", or a line is not returned, this is a finding.
Fixtext: Configure the Ubuntu operating system to prevent Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages from being acceptedr with the following command:\n\n# sudo sysctl -w net.ipv4.conf.default.accept_redirects=0\n\nIf "0" is not the system\'s default value then add or update the following line in "/etc/sysctl.conf" or in the appropriate file under "/etc/sysctl.d":\n\nnet.ipv4.conf.default.accept_redirects=0

Rule ID: SV-90561r2_rule
Severity: medium
Rule Title: The Ubuntu operating system must ignore Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages.
Description: Internet Control Message Protocol (ICMP) redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages modify the host's route table and are unauthenticated. An illicit ICMP redirect message could result in a man-in-the-middle attack.
Check_content: Verify the Ubuntu operating system ignores Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages.\n\nCheck the value of the "accept_redirects" variables with the following command:\n\n# sudo sysctl net.ipv4.conf.all.accept_redirects\n\nnet.ipv4.conf.all.accept_redirects=0\n\nIf both of the returned lines do not have a value of "0", or a line is not returned, this is a finding.
Fixtext: Configure the Ubuntu operating system to ignore Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages with the following command:\n\n# sudo sysctl -w net.ipv4.conf.all.accept_redirects=0\n\nIf "0" is not the system\'s default value then add or update the following line in "/etc/sysctl.conf" or in the appropriate file under "/etc/sysctl.d":\n\nnet.ipv4.conf.all.accept_redirects=0

Rule ID: SV-90563r2_rule
Severity: medium
Rule Title: The Ubuntu operating system must not allow interfaces to perform Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects by default.
Description: Internet Control Message Protocol (ICMP) redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain information from the system's route table, possibly revealing portions of the network topology.
Check_content: Verify the Ubuntu operating system does not allow interfaces to perform Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects by default.\n\nCheck the value of the "default send_redirects" variables with the following command:\n\n# sudo sysctl net.ipv4.conf.default.send_redirects\n\nnet.ipv4.conf.default.send_redirects=0\n\nIf the returned line does not have a value of "0", or a line is not returned, this is a finding.
Fixtext: Configure the Ubuntu operating system to not allow interfaces to perform Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects by default with the following command:\n\n# sudo sysctl -w net.ipv4.conf.default.send_redirects=0\n\nIf "0" is not the system\'s default value then add or update the following line in "/etc/sysctl.conf" or in the appropriate file under "/etc/sysctl.d":\n\nnet.ipv4.conf.default.send_redirects=0

Rule ID: SV-90565r2_rule
Severity: medium
Rule Title: The Ubuntu operating system must not send Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects.
Description: Internet Control Message Protocol (ICMP) redirect messages are used by routers to inform hosts that a more direct route exists for a particular destination. These messages contain information from the system's route table, possibly revealing portions of the network topology.
Check_content: Verify the Ubuntu operating system does not send Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirect messages.\n\nCheck the value of the "all send_redirects" variables with the following command:\n\n#  sudo sysctl net.ipv4.conf.all.send_redirects\n\nnet.ipv4.conf.all.send_redirects=0\n\nIf the returned line does not have a value of "0", or a line is not returned, this is a finding.
Fixtext: Configure the Ubuntu operating system to not allow interfaces to perform Internet Protocol version 4 (IPv4) Internet Control Message Protocol (ICMP) redirects with the following command:\n\n# sudo sysctl -w net.ipv4.conf.all.send_redirects=0\n\nIf "0" is not the system\'s default value then add or update the following line in "/etc/sysctl.conf" or in the appropriate file under "/etc/sysctl.d":\n\nnet.ipv4.conf.all.send_redirects=0

Rule ID: SV-90567r2_rule
Severity: medium
Rule Title: The Ubuntu operating system must not be performing packet forwarding unless the system is a router.
Description: Routing protocol daemons are typically used on routers to exchange network topology information with other routers. If this software is used when not required, system network information may be unnecessarily transmitted across the network.
Check_content: Verify the Ubuntu operating system is not performing packet forwarding, unless the system is a router.\n\nCheck to see if IP forwarding is enabled using the following command:\n\n# /sbin/sysctl -a | grep  net.ipv4.ip_forward\nnet.ipv4.ip_forward=0\n\nIf IP forwarding value is "1" and is not documented with the Information System Security Officer (ISSO) as an operational requirement , this is a finding.
Fixtext: Configure the Ubuntu operating system to not allow packet forwarding, unless the system is a router with the following command:\n\n# sudo sysctl -w net.ipv4.ip_forward=0\n\nIf "0" is not the system\'s default value then add or update the following line in "/etc/sysctl.conf" or in the appropriate file under "/etc/sysctl.d":\n\nnet.ipv4.ip_forward=0

Rule ID: SV-90569r2_rule
Severity: medium
Rule Title: Network interfaces must not be in promiscuous mode.
Description: Network interfaces in promiscuous mode allow for the capture of all network traffic visible to the system. If unauthorized individuals can access these applications, it may allow then to collect information such as logon IDs, passwords, and key exchanges between systems.\n\nIf the system is being used to perform a network troubleshooting function, the use of these tools must be documented with the Information System Security Officer (ISSO) and restricted to only authorized personnel.
Check_content: Verify network interfaces are not in promiscuous mode unless approved by the Information System Security Officer (ISSO) and documented.\n\nCheck for the status with the following command:\n\n# ip link | grep -i promisc\n\nIf network interfaces are found on the system in promiscuous mode and their use has not been approved by the ISSO and documented, this is a finding.
Fixtext: Configure network interfaces to turn off promiscuous mode unless approved by the Information System Security Officer (ISSO) and documented.\n\nSet the promiscuous mode of an interface to "off" with the following command:\n\n# sudo ip link set dev <devicename> promisc off

Rule ID: SV-90571r2_rule  todo
Severity: medium
Rule Title: The Ubuntu operating system must be configured to prevent unrestricted mail relaying.
Description: If unrestricted mail relaying is permitted, unauthorized senders could use this host as a mail relay for the purpose of sending spam or other unauthorized activity.
Check_content: Determine if "postfix" is installed with the following commands:\n\nNote: If postfix is not installed, this is Not Applicable.\n\n# dpkg -l | grep postfix\nii  postfix                                    3.1.0-3 \n\nVerify the Ubuntu operating system is configured to prevent unrestricted mail relaying.\n\nIf postfix is installed, determine if it is configured to reject connections from unknown or untrusted networks with the following command:\n\n# postconf -n smtpd_client_restrictions\n\nsmtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, reject\n\nIf the "smtpd_relay_restrictions" parameter contains any entries other than "permit_mynetworks", "permit_sasl_authenticated" and "reject", is missing, or is commented out, this is a finding.
Fixtext: If "postfix" is installed, modify the "/etc/postfix/main.cf" file to restrict client connections to the local network with the following command:\n\n# sudo postconf -e \'smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, reject\'

Rule ID: SV-90573r2_rule  todo
Severity: medium
Rule Title: The Information System Security Officer (ISSO) and System Administrator (SA) (at a minimum) must have mail aliases to be notified 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.
Check_content: Verify that the administrators are notified in the event of an audit processing failure. \n\nNote: If postfix is not installed, this is Not Applicable.\n\nCheck that the "/etc/aliases" file has a defined value for "root".\n\n# sudo grep "postmaster: *root$" /etc/aliases\n\nIf the command does not return a line, or the line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to notify administrators in the event of an audit processing failure. \n\nAdd/update the following line in "/etc/aliases":\n\npostmaster: root

Rule ID: SV-90575r1_rule
Severity: high
Rule Title: A File Transfer Protocol (FTP) server package must not be installed unless needed.
Description: The FTP service provides an unencrypted remote access that does not provide for the confidentiality and integrity of user passwords or the remote session. If a privileged user were to log on using this service, the privileged user password could be compromised. SSH or other encrypted file transfer methods must be used in place of this service.
Check_content: Verify a File Transfer Protocol (FTP) server has not been installed on the system.\n\nCheck to see if a FTP server has been installed with the following commands:\n\n# dpkg -l | grep vsftpd\nii vsftpd 3.0.3-3Ubuntu2 \n\nIf "vsftpd" is installed and is not documented with the Information System Security Officer (ISSO) as an operational requirement, this is a finding.
Fixtext: Document the "vsftpd" package with the Information System Security Officer (ISSO) as an operational requirement or remove it from the system with the following command:\n\n# sudo apt-get remove vsftpd

Rule ID: SV-90577r2_rule
Severity: high
Rule Title: The Trivial File Transfer Protocol (TFTP) server package must not be installed if not required for operational support.
Description: If TFTP is required for operational support (such as the transmission of router configurations) its use must be documented with the Information System Security Officer (ISSO), restricted to only authorized personnel, and have access control rules established.
Check_content: Verify a Trivial File Transfer Protocol (TFTP) server has not been installed.\n\nCheck to see if a TFTP server has been installed with the following command:\n\n# dpkg -l | grep tftpd-hpa\nii tftpd-hpa 5.2+20150808-1Ubuntu1.16.04.1 \n\nIf TFTP is installed and the requirement for TFTP is not documented with the Information System Security Officer (ISSO), this is a finding.
Fixtext: Remove the Trivial File Transfer Protocol (TFTP) package from the system with the following command:\n\n# sudo apt-get remove tftpd-hpa

Rule ID: SV-90579r1_rule  todo?
Severity: medium
Rule Title: If the Trivial File Transfer Protocol (TFTP) server is required, the TFTP daemon must be configured to operate in secure mode.
Description: Restricting TFTP to a specific directory prevents remote users from copying, transferring, or overwriting system files.
Check_content: Verify the Trivial File Transfer Protocol (TFTP) daemon is configured to operate in secure mode.\n\nCheck to see if a TFTP server has been installed with the following commands:\n\n# dpkg -l | grep tftpd-hpa\nii tftpd-hpa 5.2+20150808-1Ubuntu1.16.04.1 \nIf a TFTP server is not installed, this is Not Applicable.\n\nIf a TFTP server is installed, check for the server arguments with the following command: \n\n# grep TFTP_OPTIONS /etc/default/tftpd-hpa\nTFTP_OPTIONS="--secure"\n\nIf "--secure" is not listed in the TFTP_OPTIONS, this is a finding.
Fixtext: Configure the Trivial File Transfer Protocol (TFTP) daemon to operate in the secure mode by adding the "--secure" option to TFTP_OPTIONS in /etc/default/tftpd-hpa and restart the tftpd daemon.

Rule ID: SV-90581r1_rule
Severity: medium
Rule Title: An X Windows display manager must not be installed unless approved.
Description: Internet services that are not required for system or application processes must not be active to decrease the attack surface of the system. X Windows has a long history of security vulnerabilities and will not be used unless approved and documented.
Check_content: Verify that if X Windows is installed it is authorized.\n\nCheck for the X11 package with the following command:\n\n# dpkg -l | grep lightdm\n\nAsk the System Administrator if use of the X Windows system is an operational requirement.\n\nIf the use of X Windows on the system is not documented with the Information System Security Officer (ISSO), this is a finding.
Fixtext: Document the requirement for an X Windows server with the Information System Security Officer (ISSO) or remove the related packages with the following commands:\n\n# sudo apt-get purge lightdm

Rule ID: SV-90583r1_rule todo?
Severity: medium
Rule Title: The Ubuntu operating system must have the packages required for multifactor authentication to be installed.
Description: Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device.\n\nMultifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD Common Access Card.\n\nA privileged account is defined as an information system account with authorizations of a privileged user.\n\nRemote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.\n\nThis requirement only applies to components where this is specific to the function of the device or has the concept of an organizational user (e.g., VPN, proxy capability). This does not apply to authentication for the purpose of configuring the device itself (management).\n\nRequires further clarification from NIST.\n\n
Check_content: Verify the Ubuntu operating system has the packages required for multifactor authentication installed.\n\nCheck for the presence of the packages required to support multifactor authentication with the following commands:\n\n# dpkg -l | grep libpam-pkcs11\n\nii libpam-pkcs11 0.6.8-4 amd64 Fully featured PAM module for using PKCS#11 smart cards\n\nIf the "libpam-pkcs11" package is not installed, this is a finding.
Fixtext: Configure the Ubuntu operating system to implement multifactor authentication by installing the required packages.\nInstall the "libpam-pkcs11" package on the system with the following command:\n\n# sudo apt install libpam-pkcs11

Rule ID: SV-90585r1_rule
Severity: medium
Rule Title: The Ubuntu operating system 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 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.
Check_content: Verify the Ubuntu operating system accepts Personal Identity Verification (PIV) credentials.\n\nCheck that the "opensc-pcks11" package is installed on the system with the following command:\n\n# dpkg -l | grep opensc-pkcs11\n\nii opensc-pkcs11:amd64 0.15.0-1Ubuntu1 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 the Ubuntu operating system to accept Personal Identity Verification (PIV) credentials.\n\nInstall the "opensc-pkcs11" package using the following command:\n\n# sudo apt-get install opensc-pkcs11

Rule ID: SV-90587r2_rule  todo?
Severity: medium
Rule Title: The Ubuntu operating system must implement certificate status checking for multifactor authentication.
Description: Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device.\n\nMultifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD Common Access Card.\n\nA privileged account is defined as an information system account with authorizations of a privileged user.\n\nRemote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.\n\nThis requirement only applies to components where this is specific to the function of the device or has the concept of an organizational user (e.g., VPN, proxy capability). This does not apply to authentication for the purpose of configuring the device itself (management).\n\nRequires further clarification from NIST.\n\n
Check_content: Verify the Ubuntu operating system implements certificate status checking for multifactor authentication.\n\nCheck that certificate status checking for multifactor authentication is implemented with the following command:\n\n# sudo grep cert_policy /etc/pam_pkcs11/pam_pkcs11.conf | grep ocsp_on \n\ncert_policy = ca,signature,ocsp_on;\n\nIf "cert_policy" is not set to "ocsp_on", has a value of "none", or the line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system to 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".

Rule ID: SV-90589r2_rule todo?
Severity: medium
Rule Title: The Ubuntu operating system, for PKI-based authentication, 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\n
Check_content: Verify the Ubuntu operating system, for PKI-based authentication, had valid certificates by constructing a certification path (which includes status information) to an accepted trust anchor.\n\nCheck 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 cert_policy /etc/pam_pkcs11/pam_pkcs11.conf\n\ncert_policy = ca,signature,ocsp_on;\n\nIf "cert_policy" is not set to "ca",  has a value of "none", or the line is commented out, this is a finding.
Fixtext: Configure the Ubuntu operating system, for PKI-based authentication, to validate certificates by constructing a certification path (which includes status information) 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;

Rule ID: SV-90591r1_rule  todo?
Severity: medium
Rule Title: The Ubuntu operating system must implement smart card logins for multifactor authentication for access to accounts.
Description: Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device.\n\nMultifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD Common Access Card.\n\nRemote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.\n\nThis requirement only applies to components where this is specific to the function of the device or has the concept of an organizational user (e.g., VPN, proxy capability). This does not apply to authentication for the purpose of configuring the device itself (management).\n\nRequires further clarification from NIST.\n\n
Check_content: Verify the Ubuntu operating system uses multifactor authentication for local access to accounts.\n\nCheck that the "pam_pkcs11.so" option is configured in the "/etc/pam.d/common-auth" file with the following command:\n\n# grep pam_pkcs11.so /etc/pam.d/common-auth\nauth [success=2 default=ignore] pam_pkcs11.so\n\nIf "pam_pkcs11.so" is not set in "/etc/pam.d/common-auth", this is a finding.
Fixtext: Configure the Ubuntu operating system to use multifactor authentication for local 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

Rule ID: SV-92701r1_rule
Severity: high
Rule Title: The system must use a DoD-approved virus scan program.
Description: Virus scanning software can be used to protect a system from penetration from computer viruses and to limit their spread through intermediate systems. \n\nThe virus scanning software should be configured to perform scans dynamically on accessed files. If this capability is not available, the system must be configured to scan, at a minimum, all altered files on the system on a daily basis.\n\nIf the system processes inbound SMTP mail, the virus scanner must be configured to scan all received mail.
Check_content: Verify the system is using a DoD-approved virus scan program.\n\n\nCheck for the presence of "McAfee VirusScan Enterprise for Linux" with the following command:\n\n\n# systemctl status nails\n\nnails - service for McAfee VirusScan Enterprise for Linux \n\n> Loaded: loaded /opt/NAI/package/McAfeeVSEForLinux/McAfeeVSEForLinux-2.0.2.<build_number>; enabled)\n\n> Active: active (running) since Mon 2015-09-27 04:11:22 UTC;21 min ago\n\n\nIf the "nails" service is not active, check for the presence of "clamav" on the system with the following command:\n\n\n# systemctl status clamav-daemon.socket\n\nsystemctl status clamav-daemon.socket\n\nclamav-daemon.socket - Socket for Clam AntiVirus userspace daemon\n\nLoaded: loaded (/lib/systemd/system/clamav-daemon.socket; enabled)\n\nActive: active (running) since Mon 2015-01-12 09:32:59 UTC; 7min ago\n\n\nIf neither of these applications are loaded and active, ask the System Administrator if there is an antivirus package installed and active on the system.\n\n\nIf no antivirus scan program is active on the system, this is a finding.
Fixtext: Install an approved DoD antivirus solution on the system.

Rule ID: SV-92703r1_rule
Severity: medium
Rule Title: The system must update the DoD-approved virus scan program every seven days or more frequently.
Description: Virus scanning software can be used to protect a system from penetration from computer viruses and to limit their spread through intermediate systems. \n\nThe virus scanning software should be configured to check for software and virus definition updates with a frequency no longer than seven days. If a manual process is required to update the virus scan software or definitions, it must be documented with the Information System Security Officer (ISSO).
Check_content: Verify the system is using a DoD-approved virus scan program and the virus definition file is less than seven days old.\n\nCheck for the presence of "McAfee VirusScan Enterprise for Linux" with the following command:\n\n# systemctl status nails\n\nnails - service for McAfee VirusScan Enterprise for Linux \n\n> Loaded: loaded /opt/NAI/package/McAfeeVSEForLinux/McAfeeVSEForLinux-2.0.2.<build_number>; enabled)\n\n> Active: active (running) since Mon 2015-09-27 04:11:22 UTC;21 min ago\n\nIf the "nails" service is not active, check for the presence of "clamav" on the system with the following command:\n\n# systemctl status clamav-daemon.socket\n\nsystemctl status clamav-daemon.socket\n\nclamav-daemon.socket - Socket for Clam AntiVirus userspace daemon\n\nLoaded: loaded (/lib/systemd/system/clamav-daemon.socket; enabled)\n\nActive: active (running) since Mon 2015-01-12 09:32:59 UTC; 7min ago\n\nIf "McAfee VirusScan Enterprise for Linux" is active on the system, check the dates of the virus definition files with the following command:\n\n# ls -al /opt/NAI/LinuxShield/engine/dat/*.dat\n\n-rwxr-xr-x 1 root root 243217 Mar 5 2017 avvclean.dat\n-rwxr-xr-x 1 root root 16995 Mar 5 2017 avvnames.dat\n-rwxr-xr-x 1 root root 4713245 Mar 5 2017 avvscan.dat\n\nIf the virus definition files have dates older than seven days from the current date, this is a finding.\n\nIf "clamav" is active on the system, check the dates of the virus database with the following commands:\n\n# grep -I databasedirectory /etc/clamav.conf\n\nDatabaseDirectory /var/lib/clamav\n\n# ls -al /var/lib/clamav/*.cvd\n\n-rwxr-xr-x 1 root root 149156 Mar 5 2011 daily.cvd\n\nIf the database file has a date older than seven days from the current date, this is a finding.\n
Fixtext: Update the approved DoD virus scan software and virus definition files.

Rule ID: SV-95669r1_rule
Severity: high
Rule Title: The x86 Ctrl-Alt-Delete key sequence in the Ubuntu operating system must be disabled if GNOME 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 GNOME 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.
Check_content: Verify the Ubuntu operating system is not configured to reboot the system when Ctrl-Alt-Delete is pressed when using GNOME.\n\nCheck that the "logout" target is not bound to an action with the following command:\n\n# grep logout /etc/dconf/db/local.d/*\n\nlogout=\'\'\n\nIf the "logout" key is bound to an action, is commented out, or is missing, this is a finding.
Fixtext: [u'Configure the system to disable the Ctrl-Alt-Delete sequence when using GNOME by creating or editing the /etc/dconf/db/local.d/00-disable-CAD file.\n\nAdd the setting to disable the Ctrl-Alt-Delete sequence for GNOME:\n\n[org/gnome/settings-daemon/plugins/media-keys]\nlogout=\u2019\u2019\n\nThen update the dconf settings:\n\n# dconf update

Rule ID: SV-95671r1_rule
Severity: medium
Rule Title: The auditd service must be running in the Ubuntu operating system.
Description: Configuring the Ubuntu operating system to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements.\n\nConfiguration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.
Check_content: Verify the audit service is active.\n\nCheck that the audit service is active with the following command:\n\n# service auditd status\nActive: active (running)\n\nIf the service is not active this is a finding.
Fixtext: Start the auditd service, and enable the auditd service with the following commands:\n\nStart the audit service.\n# systemctl start auditd.service\n\nEnable auditd in the targets of the system.\n# systemctl enable auditd.service

Rule ID: SV-95673r1_rule
Severity: medium
Rule Title: The Ubuntu operating system must notify the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity.
Description: If security personnel are not notified immediately when storage volume reaches 75% utilization, they are unable to plan for audit record storage capacity expansion.
Check_content: Verify the Ubuntu operating system notifies the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity.\n\nCheck the system configuration to determine the 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/"):\n\n# df -h /var/log/audit/\n1.0G /var/log/audit\n\nIf the audit records are not being written to a partition specifically created for audit records (in this example "/var/log/audit" is a separate partition), determine the amount of space other files in the partition are currently occupying with the following command:\n\n# du -sh <partition>\n1.0G /var\n\nDetermine what the threshold is for the system to take action when 75% of the repository maximum audit record storage capacity is reached:\n\n# grep -i space_left /etc/audit/auditd.conf\nspace_left = 250\n\nIf the value of the "space_left" keyword is not set to 25% of the total partition size, this is a finding.
Fixtext: Configure the operating system to immediately notify the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75% of the repository maximum audit record storage capacity.\n\nCheck the system configuration to determine the partition the audit records are being written to: \n\n# grep log_file /etc/audit/auditd.conf\n\nDetermine the size of the partition that audit records are written to (with the example being "/var/log/audit/"):\n\n# df -h /var/log/audit/\n\nSet the value of the "space_left" keyword in "/etc/audit/auditd.conf" to 25% of the partition size.

Rule ID: SV-95675r1_rule
Severity: medium
Rule Title: The audit log files in the Ubuntu operating system must have mode 0640 or less permissive.
Description: Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the Ubuntu operating system or platform. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.\n\nThe structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.
Check_content: Verify that the audit log files have a mode of "0640" or less permissive.\n\nCheck where the audit logs are stored on the system using the following command:\n\n# sudo grep log_file /etc/audit/auditd.conf\nlog_file = /var/log/audit/audit.log\n\nUsing the audit log path from the command above, replace "[log_path]" in the following command:\n\n# sudo ls -lad [log_file] | cut -d\' \' -f1\nls -lad /var/log/audit/audit.log | cut -d\' \' -f1\n-rw-r-----\n\nIf the audit log file does not have a mode of "0640" or less permissive, this is a finding.
Fixtext: Configure the octal permission value of the audit log to "0640" or less permissive. \n\nUse the following command to find where the audit log files are stored on the system:\n\n# sudo grep log_file /etc/audit/auditd.conf\nlog_file = /var/log/audit/audit.log\n\nUsing the audit log path from the command above, replace "[log_path]" in the following command:\n\n# sudo chmod 0640 [log_path]

Rule ID: SV-95677r1_rule
Severity: medium
Rule Title: The audit records must be off-loaded 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\nOff-loading is a common process in information systems with limited audit storage capacity.
Check_content: Verify the audit system off-loads audit records to a different system or storage media from the system being audited.\n\nCheck that the records are being off-loaded to a remote server with the following command:\n\n# sudo grep -i remote_server /etc/audisp/audisp-remote.conf\n\nremote_server = 10.0.1.2\n\nIf "remote_server" is not configured, or the line is commented out, this is a finding.
Fixtext: Configure the audit system to off-load audit records to a different system or storage media from the system being audited.\n\nSet the "remote_server" option in "/etc/audisp/audisp-remote.conf" with the IP address of the log server. See the example below.\n\nremote_server = 10.0.1.2\n\nIn order for the changes to take effect, the audit daemon must be restarted. The audit daemon can be restarted with the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-95681r2_rule
Severity: medium
Rule Title: Successful/unsuccessful uses of the chcon command must generate an audit record.
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).\n\n
Check_content: Verify the Ubuntu operating system generates an audit record when successful/unsuccessful attempts to use the "chcon" command occur.\n\nCheck that the following calls are being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":\n\n# sudo grep -w chcon /etc/audit/audit.rules\n\n:\n-a always,exit -F arch=b64 path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=4294967295 -k perm_chng\n\nIf the command does not return a line, or the line is commented out, this is a finding.
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/audit.rules" file:\n\n-a always,exit -F arch=b32 path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=4294967295 -k perm_chng\n-a always,exit -F arch=b64 path=/usr/bin/chcon -F perm=x -F auid>=1000 -F auid!=4294967295 -k perm_chng\n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service

Rule ID: SV-101015r1_rule
Severity: medium
Rule Title: The audit system must be configured to audit the execution of privileged functions and prevent all software from executing at higher privilege levels than users executing the software.
Description: Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse and identify the risk from insider threats and the advanced persistent threat.\n\n
Check_content: Verify the Ubuntu operating system audits the execution of privilege functions.\n\nCheck if the Ubuntu operating system is configured to audit the execution of the "execve" system call, by running the following command:\n\n# sudo grep execve /etc/audit/audit.rules\n\n-a always,exit -F arch=b32 -S execve -C uid!=euid -F key=execpriv \n-a always,exit -F arch=b64 -S execve -C uid!=euid -F key=execpriv\n \n-a always,exit -F arch=b32 -S execve -C gid!=egid -F key=execpriv \n-a always,exit -F arch=b64 -S execve -C gid!=egid -F key=execpriv\n\nIf the command does not return all lines, or the lines are commented out, this is a finding. 
Fixtext: Configure the Ubuntu operating system to audit the execution of the "execve" system call.\n\nAdd or update the following file system rules to "/etc/audit/audit.rules":\n\n-a always,exit -F arch=b32 -S execve -C uid!=euid -F key=execpriv \n-a always,exit -F arch=b64 -S execve -C uid!=euid -F key=execpriv\n \n-a always,exit -F arch=b32 -S execve -C gid!=egid -F key=execpriv \n-a always,exit -F arch=b64 -S execve -C gid!=egid -F key=execpriv \n\nThe audit daemon must be restarted for the changes to take effect. To restart the audit daemon, run the following command:\n\n# sudo systemctl restart auditd.service