Enable FIPS Mode on SLES 15 and Verify the Boot State
Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.
The article uses illustrations from the 43-inch Panasonic TH-43CS630V Smart LED TV
Step 1: Select the MENU button on the remote, the TV main MENU interface will appear.
Step 2: In the menu interface, select Settings, and then select Analogue Search Menu.
Step 3: In the Analogue Search Menu, choose Auto Tuning, then select Start Auto Tuning (operate through the navigation key cluster on the remote). Now you need to wait 3 to 5 minutes for the TV to start tuning.
Step 4: After the search is complete, choose Exit to finish and you can start watching the TV channels you just recorded.
Note:
- The number of channels and image quality depends on the receiving antenna and the geographical location of the user.
- Searching time will last from 3-5 minutes.
The product I illustrated in the article
Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.
Compare YaST and cryptsetup for a new encrypted SLES data volume, choose LUKS1 or LUKS2, and verify unlock and mount behavior safely.
Create, refine, and verify a least-privilege AppArmor profile on SLES 15 SP7, with a clear note on SLES 16’s SELinux default.
Set up RMT on SLES 15, mirror entitled repositories, and verify HTTPS registration and package access from a test client.
Connect SLES 15 to AD with YaST’s SSSD-based logon management, then verify directory lookup, domain login, and Kerberos tickets.
Set up the right Live Patching path for SLES 16.0 or 15 SP7, apply eligible kernel fixes, and confirm what is active without confusing it with a reboot-required kernel update.
Load a custom SLES 15 kernel module without disabling Secure Boot. Match the running kernel, sign the .ko file, enroll a MOK key, and verify loading.
SLES 15 SP5 can migrate online to SP6, but each node must reboot. Use a tested rolling upgrade or blue-green cutover to keep workloads reachable.
Use SUSE’s supported STIG profile to scan SLES 15, test remediation, review remaining findings, and retain assessment evidence.
Trace a failed Cockpit connection through DNS, port 9090, the systemd socket, firewalld, TLS, and login settings using current SUSE guidance.