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.
Simple, convenient and fast! Let's learn how to record TV shows on Samsung TV in the following article.
Step 1: Plug the USB / hard drive into the TV and wait for the TV to set up USB content (TV will automatically create a folder in the USB).
Step 2: After TV has finished USB test. Press the Menu / 123 button on the remote
Step 3: Start recording
- Select the REC button on the virtual keyboard on the screen to record, a bar will appear at the time to record. - The recording time depends on the remaining capacity of the storage device.
- Click the PAUSE button to pause recording- Click on PAUSE again to resume recording
- Click the STOP button to stop recording
Step 4: Review the content, select the SOURCE button on the remote to select the input source.
- Select USB
- Select the Contents folder (this is the folder created by the TV)
- Select the content you want to see
- Press select to play content
Note:
- A USB / hard drive must be connected to use the recording feature
- The USB / hard drive must have a capacity to record the content
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.