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.
On the new Windows 10 operating system, managing users is now simple and it also gives you more options so you can control the user's Microsoft account. You can use more than one Microsoft account on a Windows 10 device.
It's fine if you're using a personal computer, but if you do use it, you will sometimes see another Microsoft account logged into your Windows 10 operating system. It is also no problem but you have to log out and log in to your account to use. If you want to manage the use of Microsoft account, you can follow the instructions in the article below.
Step 1: First click on Start , then scroll down and select Windows Administrator Tools , select Local Security Policy.

Step 2: In the Local Security Policy table, select Local Policies> Security Options , in the Policy pane on the right, double-click Account: Block Microsoft Accounts.
Step 3: In the Accounts selection box : Block Microsoft accounts Properties . You will have two options:
Details of these two options are below.
This is the Users can't add Microsoft accounts option in the Accounts table : Block Microsoft accounts Properties when you select this option, you will have the following features.
Corresponding to the option, Users can't add or log on with Microsoft accounts: This option will have the following features:
Based on the features available on the two options, you should choose the first option (Users can't add Microsoft accounts) to prevent users from adding Microsoft accounts to your Windows 10. Then click Apply and OK to finish.
Some computers have additional Microsoft account errors due to the above settings, so if you encounter errors, please check the settings in this custom.
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.