Microsoft enables various controls to Windows users by providing multiple configuration capabilities since the organization needs to implement control over their security configurations.
Generally, Window security baseline applies to Windows 10, Windows Server 2016 and office 2016, But this final release of security configuration baseline settings referred only with Windows 10 and windows server.
A security baseline is a group of Microsoft-recommended configuration settings that explains their security impact. These settings are based on feedback from Microsoft security engineering teams, product groups, partners, and customers.
Microsoft defined over 3,000 Group Policy settings for Windows 10, which does not include over 1,800 Internet Explorer 11 settings. Of these 4,800 settings, only some are security-related.
New security configuration baseline settings
Microsoft brings some of the major updates with this new security baseline settings for Windows 10 and Windows server. Here some of the notable Baseline settings in this final release that updated by Microsoft.
- Enable svchost.exe mitigation options – Enforces Stricter security on Windows services hosted in svchost.exe that controls all binaries loaded by svchost.exe must be signed by Microsoft. So it never allows 3rd party apps if its try to use the svchost.exe hosting process.
- App Privacy setting – This baseline setting denies users to interact with applications using speech while the system is locked.
- Disabling multicast name resolution– It eliminates the mitigate server spoofing threats.
- Domain Controller baseline – Adding Recommended auditing settings for Kerberos authentication service.
- Dropping the password-expiration policies – It stop the Password expiration policies for Windows, which required users to change their password periodically.
- Cipher strength settings in BitLocker drive encryption – This baseline require the strongest available BitLocker encryption.
We can say that the implementation of shutting down the password expiration policy for Windows signifies one of the significant changes in this final security Configuration Baseline Settings for Windows 10. Read here why its shut down.
Disabling of the built-in Administrator & Guest accounts.
Microsoft also dropping the enforced disabling of the built-in Administrator and Guest accounts.
According to Microsoft, To keep baselines useful and manageable, we tend to enforce secure defaults for policy settings only when,
1) non-administrative users could otherwise override those defaults, or 2) misinformed administrators are otherwise likely to make poor choices about the setting. Neither of those conditions are true regarding enforcing the default disabling of the Administrator and Guest accounts.
The built-in Guest account -The Guest account (RID -501) is disabled by default on Windows 10 and Windows Server. Only an administrator can enable the Guest account, and an admin would presumably do so only for a valid reason such as for a kiosk system.
The built-in Administrator account – The local Administrator account (RID -500) is disabled by default on Windows 10 but not on Windows Server.
You can Download the content from the Microsoft Security Compliance Toolkit.
You can Download Free E-book to learn about complete Enterprise Security Implementation & Mitigation Steps – Download Free-Ebook Here.