STIGQter: STIG Summary: SUSE Linux Enterprise Micro (SLEM) 5 Security Technical Implementation Guide Version: 1 Release: 4 Benchmark Date: 01 Apr 2026:

All SLEM 5 persistent disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at-rest protection.

DISA Rule

SV-261284r1184374_rule

Vulnerability Number

V-261284

Group Title

SRG-OS-000185-GPOS-00079

Rule Version

SLEM-05-231040

Severity

CAT I

CCI(s)

CCI-001199 - Protects the confidentiality and/or integrity of organization-defined information at rest.
CCI-002475 - Implement cryptographic mechanisms to prevent unauthorized modification of organization-defined information when at rest on organization-defined system components.
CCI-002476 - Implement cryptographic mechanisms to prevent unauthorized disclosure of organization-defined information at rest on organization-defined system components.

Weight

Fix Recommendation

Configure SLEM 5 to prevent unauthorized modification of all information at rest by using disk encryption.

Encrypting a partition in an already-installed system is more difficult because of the need to resize and change existing partitions. To encrypt an entire partition, dedicate a partition for encryption in the partition layout. The standard partitioning proposal as suggested by YaST (installation and configuration tool for Linux) does not include an encrypted partition by default. Add it manually in the partitioning dialog.

The following set of commands will switch SLEM 5 to work in FIPS mode:

> sudo transactional-update pkg install -t pattern microos-fips

> reboot

Add or modify the following line in the "/etc/default/grub" file to include "fips=1":

GRUB_CMDLINE_LINUX_DEFAULT="splash=silent swapaccount=1 apparmor=0 mitigations=auto quiet crashkernel=195M,high crashkernel=72M,low fips=1"

> sudo transactional-update grub.cfg

> sudo reboot

Check Contents

Verify SLEM 5 prevents unauthorized disclosure or modification of all information requiring at-rest protection by using disk encryption.

Verify the system partitions are all encrypted with the following commands:

> sudo blkid
/dev/sda1: "UUID=26d4a101-7f48-4394-b730-56dc00e65f64" TYPE="crypto_LUKS"
/dev/sda2: "UUID=f5b8a790-14cb-4b82-882d-707d52f27765" TYPE="crypto_LUKS"
/dev/sda3: "UUID=f2d86128-f975-478d-a5b0-25806c900eac" TYPE="crypto_LUKS"

Every persistent disk partition present must be of type "crypto_LUKS". If any partitions other than the boot partition or pseudo file systems (such as /proc or /sys) or temporary file systems (that are tmpfs) are not type "crypto_LUKS", ask the administrator to indicate how the partitions are encrypted. If there is no evidence that these partitions are encrypted, this is a finding.

> sudo more /etc/crypttab
cr_root UUID=26d4a101-7f48-4394-b730-56dc00e65f64
cr_home UUID=f5b8a790-14cb-4b82-882d-707d52f27765
cr_swap UUID=f2d86128-f975-478d-a5b0-25806c900eac

Every persistent disk partition present on the system must have an entry in the /etc/crypttab file.

If any partitions other than pseudo file systems (such as /proc or /sys) are not listed or "/etc/crypttab" does not exist, this is a finding.

Verify the system works in FIPS mode with the following command:

> sudo sysctl -a | grep fips
crypto.fips_enabled = 1

Vulnerability Number

V-261284

Documentable

False

Rule Version

SLEM-05-231040

Severity Override Guidance

Check Content Reference

Target Key

5596