Security Compliance Enforcement for Linux – sce_linux v2.1.0 has been released
We’re excited to announce that Security Compliance Enforcement for Linux – sce_linux v2.1.0 is now available.
With SCE for Linux v2.1.0, you can now enforce security controls on a broader range of operating systems. SCE now enforces the following Center for Internet Security (CIS) Benchmarks: AlmaLinux 9, v1.0.0; Rocky Linux 9, v1.0.0; and Ubuntu 22.04, v2.0.0. You can also enforce updated CIS benchmarks on Red Hat Enterprise Linux (RHEL) 7 and Oracle Linux 7 operating systems.
New benchmarks added:
* CIS Ubuntu 22.04 Benchmark v2.0.0, Server Level 1.
* CIS AlmaLinux 9 Benchmark v1.0.0, Server Levels 1 and 2.
* CIS Rocky Linux 9 Benchmark v1.0.0, Server Levels 1 and 2.
Updates to existing supported benchmarks:
* For users of the Red Hat Enterprise Linux 7 operating system, the CIS Benchmark was upgraded from v3.1.1 to v4.0.0. For a list of control updates, see Control updates introduced for CIS Red Hat Enterprise Linux 7 Benchmark v4.0.0
https://help.puppet.com/sce/current/linux/scel_cisupdate_rhel_7_v400.htm .
* For users of the Oracle Linux 7 operating system, the CIS Benchmark was upgraded from v3.1.1 to v4.0.0. For a list of control updates, see Control updates introduced for CIS Oracle Linux 7 Benchmark v4.0.0
https://help.puppet.com/sce/current/linux/scel_cisupdate_oracle_lin_7_v400.htm.
Additional enhancements
* You can now enjoy more flexibility when specifying CIS or STIG controls to enforce. Starting with this release, you can apply both the only and ignore keys in a single configuration file. If both keys are used, SCE first applies the only key to narrow the scope, and then applies the ignore key to exclude specific controls from that group. For more information, see Enforce and ignore controls within a single configuration
https://help.puppet.com/sce/current/linux/scel_config_enforce_and_ignore.htm.
* An update was introduced to improve usability of the vlock utility, which locks virtual console sessions to prevent unauthorized access. Previously, if vlock locked a sudo shell session, the user was prompted for the root account password. Now, users can specify a setting in the control_config hash to prompt for the non-sudo account password, as shown in the following example:
set -g lock-command 'if [ -z "$SUDO_USER" ];then vlock;else sudo -u $SUDO_USER vlock;fi'
* You can now use new parameters to modify the permissions and ownership of the /var/log/audit/ directory, where audit logs are stored. Previously, the directory permissions were hard-coded when enforcing certain controls. Now, the directory permissions are fully configurable. To find detailed information about parameters for the controls that you are enforcing, see the Reference
https://forge.puppet.com/modules/puppetlabs/sce_linux/reference tab on Puppet Forge.
* An update was introduced to support more flexibility in assigning mount options. With this update, if /tmp is a mounted directory using a file system other than the Temporary File System (tmpfs), the noexec, nosuid, and nodev options will be directly assigned to the file system in /etc/fstab. If /tmp is mounted using tmpfs, or if no mount for /tmp exists, systemd is used to mount /tmp with the tmpfs file system, as in previous releases. To restore the previous behavior, you can set the parameter force_tmpfs to true on the controls that manage /tmp mount options.
Resolved issues
* Resolved an issue that occurred when configuring custom firewall rules in SCE for Linux. The issue generated error messages about dependency cycles. The issue is resolved, and the documentation is updated to provide a custom configuration example. See Configure the firewall type
https://help.puppet.com/sce/current/linux/scel_config_firewall.htm.