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.
By default of the Windows operating system, the files created and saved on the computer will be yellow, the file names are black. Normally, users will not have any way to change this, except for changing the icons (icons for those files). But if you want to try a little naughty, we still have a way to change the file color and the name of the files in it.
To change the color of the file name, we can do it directly on the computer, but if you want to change the folder color, it will need support, and Rainbow Folders is the tool to help us do that.
Step 1: After downloading and installing the Rainbow Folders, you run the RainbowFolders.exe.

Step 2: The interface of Rainbow Folders appears, follow the instructions:
Step 3: Go back to the main screen, you will see the selected folder has "changed" other colors. It also looks quite striking and fancy!
Step 1: You choose right-click the folder you want to change the name of the folder color inside, click Properties . After the new interface appears, continue to click on Advanced.
Step 2: Advanced Attributes appear, click on Compress contents to save disk space under Compress or Encrypt attributes, then OK . At Confirm Attributes Changes, you will have two options:
Tick the option you want and then click OK to finish.
And here is our result, the folder name color change has been successful!
And this is the color of the filenames inside the selected folder.
This way, there is a restriction that we cannot arbitrarily change the color of the file name , only the default will be blue. But anyway, this color-changing tip of the folder also makes our computer interface change, fancy and more beautiful than the original default settings.
I wish you successful implementation!
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.