V2R8 changes
Canonical Ubuntu 18.04 LTS STIG V2R8 (2022-07-27) replaced V2R7 (2022-04-27): 4 checks updated. It has 175 checks, against 175 in V2R7.
V2R8 checklistV2R7 checklist Compare V2R7 and V2R8 in STIG Compare
- 0 added
- 0 removed
- 4 updated
Updated fields: Check text 4Fix text 4Title 1
Updated in V2R8 (4)
V-219208CAT IIThe Ubuntu operating system must have system commands group-owned by root or a system account.Title, Check text, Fix text
Title
The Ubuntu operating system must have system commands group-owned by root or a system account.
Check text
Verify the system commands contained in the following directories are group-owned by root or a system account:
/bin
/sbin
/usr/bin
/usr/sbin
/usr/local/bin
/usr/local/sbin
Run the check with the following command:
$ sudo find -L /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin ! -group root -type f -exec stat -c "%n %G" '{}' 1;
If any system commands are returned that are not Set Group ID up on execution (SGID) files and group-owned by a privilegedrequired system account, this is a finding.
Fix text
Configure the system commands to be protected from unauthorized access. Run the following command:
$, sudoreplacing find"[FILE]" /binwith /sbinany /usr/binsystem /usr/sbincommand /usr/local/binfile /usr/local/sbinnot ! -group-owned by "root" -typeor fa !required -permsystem /2000account.
$ -execsudo chgrp root '{}' 1;[FILE]
V-219212CAT IThe Ubuntu Operating system must disable the x86 Ctrl-Alt-Delete key sequence.Check text, Fix text
Check text
Verify the Ubuntu operating system is not configured to reboot the system when Ctrl-Alt-Delete is pressed.
Check that the "ctrl-alt-del.target" (otherwise also known as reboot.target) is not active with the following command:
#$ sudo systemctl status ctrl-alt-del.target
rebootctrl-alt-del.target - Reboot
Loaded: loadedmasked (/usrdev/lib/systemd/system/reboot.targetnull; disabledbad)
Active: inactive (dead)
Docs: man:systemd.special(7)
If the "ctrl-alt-del.target" is activenot masked, this is a finding.
Fix text
Configure the system to disable the Ctrl-Alt-Delete sequence for the command line with the following commandcommands:
#$ sudo systemctl disable ctrl-alt-del.target
$ sudo systemctl mask ctrl-alt-del.target
And reload the daemon to take effect :
#$ sudo systemctl daemon-reload
V-219306CAT IIThe Ubuntu operating system must monitor remote access methods.Check text, Fix text
Check text
Verify that the Ubuntu operating system monitors all remote access methods.
Check that remote access methods are being logged by running the following command:
#$ grep -E -r '^(auth,authpriv1.1*|daemon1.1*)' /etc/rsyslog.*
/etc/rsyslog.d/50-default.conf:auth,authpriv.* /var/log/auth.log
/etc/rsyslog.d/50-default.conf:daemon.notice* /var/log/messages
If "auth.*", "authpriv.*" or "daemon.*" are not configured to be logged in at least one of the config files, this is a finding.
Fix text
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:
auth.*,authpriv.* /var/log/secure
daemon.notice* /var/log/messages
In order for the changes to take effect the "rsyslog" service must be restarted with the following command:
#$ sudo systemctl restart rsyslog.service
V-251507CAT IThe Ubuntu operating system must not allow accounts configured with blank or null passwords.Check text, Fix text
Check text
To verify that null passwords cannot be used, run the following command:
#$ grep nullok /etc/pam.d/common_passwordcommon-password
If this produces any output, it may be possible to log on with accounts with empty passwords.
If null passwords can be used, this is a finding.
Fix text
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.
Remove any instances of the "nullok" option in "/etc/pam.d/common_passwordcommon-password" to prevent logons with empty passwords.
How these changes are found
Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V2R8 no longer has.
Comparing other releases, or this one against an older release? Pick any two in STIG Compare.