Blog Post

Windows Server News and Best Practices
5 MIN READ

Announcing Hardened Server Core for Windows Server Insiders

Christina_Curlette's avatar
Nov 17, 2026

For years, Windows Server shipped compatible by default. Making the server secure was up to you, usually by applying the Security Baseline or your own hardening scripts after setup. Until that work was done, every new server ran in a less secure state, and that gap was easy to miss.

Security threats have grown, so with Windows Server 2028 we are changing that approach. Windows Server is now secure by default: you start from a hardened configuration and relax only the settings your workloads need. 

Starting with Windows Server Insider Preview build 29706, Server Core installs hardened. Hundreds of security settings are on from first boot. They're aligned with the industry benchmarks you're already measured against, such as CIS and DISA STIG. The secure configuration is the starting state, not a project you run after setup. That closes the window where a newly deployed server sits exposed while it waits to be hardened. 

Important: Because the defaults are now locked down, some things that worked on Windows Server 2025 may not work on Windows Server 2028 without changes. This includes older protocols, legacy authentication, and some management tools and scripts. Test your applications and operational tooling against the hardened configuration before deployment and relax specific settings only where a workload requires it.

What is hardened, layer by layer 

The settings were chosen with the teams that own each component and validated as a set, so they work together. That last part matters more than any single setting. 

  • Identity and authentication. Credentials are hard to steal and hard to reuse: Kerberos over NTLM, LSASS protected, strong passwords and account lockout, no consumer accounts. 
  • Network exposure. The server talks only over signed, encrypted, authenticated channels: SMB signing and encryption, the firewall on in every profile, legacy name resolution and unauthenticated RPC off. 
  • Cryptography. TLS is limited to modern cipher suites, key exchange is hybrid post-quantum (ML-KEM), and stored keys get strong protection. 
  • Privilege and admin access. Admins approve elevation, powerful rights stay with Administrators, Guests cannot sign in, and installers cannot elevate on their own. 
  • Platform and code integrity. The sign-in process runs only Microsoft-signed code. Signature validation is stricter. The paging file is encrypted. 
  • Remote access and observability. RDP with NLA and TLS, WinRM without Basic, Digest or unencrypted traffic, advanced audit with command lines, PowerShell script block logging and larger event logs.    

Defaults that hold 

Hardened values are delivered as policy, in the policy hive (HKLM\SOFTWARE\Policies) wherever the component supports one. Policy wins over local configuration, so a cmdlet, script or installer that writes local configuration cannot silently weaken a hardened default. It is also where industry benchmarks evaluate and score. 

You stay in control. OSConfig can manage these settings, extend them and keep them from drifting. Group Policy, local or domain, or another management tool works as well. Whichever one sets a value, OSConfig or a GPO, owns it. The firewall stays locally manageable by design. 

One thing will surprise you the first time: gpresult and RSOP report these settings as Not Configured. That is expected. The defaults are built into the image, so there is no .pol file for those tools to read. Use MSHardenedPolicyEval to see what is actually in force. Once you apply a security baseline with OSConfig, OSConfig reports compliance and corrects drift for every setting in that baseline. 

MSHardenedPolicyEval: score, apply, restore 

The MSHardenedPolicyEval PowerShell module ships in the box. Run its cmdlets from an elevated PowerShell session: 

  • Get-MSHardenedPolicyScore scores the server per category and overall against the hardened state. 
  • Restore-MSHardenedPolicy removes the hardened policy values for a category, or the whole server, so standard Windows Server behavior returns when a workload needs it. 
  • Set-MSHardenedPolicy re-applies the hardened values the same way. 

The same policy tables drive evaluation, apply and restore, so a setting that counts toward your score is exactly the setting Set-MSHardenedPolicy configures. Both write cmdlets support -WhatIf, so you can see what a change will touch before you make it, and both warn when a restart may be needed. If you work from a command prompt, MSHardenedPolicyEval.exe in %SystemRoot%\System32 does the same job and can also write results to a log file and the event log for your monitoring. 

Once OSConfig, Group Policy or another management tool manages the server, use the in-box tooling, the MSHardenedPolicyEval cmdlets or MSHardenedPolicyEval.exe, for scoring only, and let that management tool own the settings. Applying or restoring values with the in-box tooling on a managed server can put the two tools in conflict, and the server can end up in a different state than either one expects. 

Expect a score below 100% on this build. The tool is still being refined: 

  • Some settings are not measured yet, such as TLS cipher suites and ECC curves. 
  • Some scores depend on components that are not installed by default. 
  • On servers that run the Key Distribution Center (KDC), such as domain controllers, some settings can show as unmet even though they are applied. 
  • The tool and its cmdlets may be renamed in a later preview flight. Treat the names in this post as temporary. 

What is not hardened yet in this preview 

We are still hardening the product. These will arrive in future previews: 

  • NTLM blocking 
  • Hardware-backed platform protection: Secure Boot and DMA protection requirements, and kernel shadow stacks 
  • Print and RPC hardening, including Windows Protected Print 
  • More settings, such as the logon banner 

Try it 

1. Install the Windows Server Insider Preview build

Hardened Server Core is available starting with build 29706. Download the Server Core image and install it on a physical server or a VM. 

2. Check the hardened state

From an elevated PowerShell session: 

Get-MSHardenedPolicyScore | Format-Table Name, PassingPolicyCount, PolicyCount, Score 

Example output:

Name                          PassingPolicyCount PolicyCount Score
----                          ------------------ ----------- -----
Overall                                      191         237 80.59
AuditPolicy                                   17          17   100
CredentialAndLSAProtection                     3           3   100
CryptographyAndTLS                             3           3   100
RemoteDesktop                                 11          11   100
RemoteManagement                               6           6   100
SMBAndFileSharing                             18          19 94.73
WindowsFirewall                               30          30   100
...

You get an Overall row and one row per category, such as RemoteManagement, SMBAndFileSharing or WindowsFirewall. Get-MSHardenedPolicyCategories lists the names -Category accepts, so you can narrow the score to the categories you care about.

3. See a hardened default hold

WinRM Basic authentication is off by policy. Try to turn it on locally: 

Set-Item WSMan:\localhost\Service\Auth\Basic -Value $true 

The change is refused: 

The config setting Basic cannot be changed because is controlled by policies. The policy would need to be set to "Not Configured" in order to change the config setting. 

The setting reads back as false. Nothing weakened it.

4. Restore one category when you need to

If nothing manages the server yet and a workload genuinely needs a change, restore only the category that covers it: 

Restore-MSHardenedPolicy -Category RemoteManagement 

The hardened policy value is reverted, so the local change is now allowed. The cmdlet warns that a restart may be needed before the new state takes effect. Restore returns standard Windows Server behavior, not a snapshot of your earlier configuration.

5. Re-apply the hardened values

Set-MSHardenedPolicy -Category RemoteManagement 

Run step 3 again and the change is refused. Protection is restored. Pass several categories at once (-Category Audit, LSA), or leave out -Category to apply every one.           

Tell us what breaks 

We want to hear where a hardened default gets in the way of a real workload: which setting, which application, and what you had to change to get it working. That is how the defaults get better before general availability. 

Share feedback in the Windows Server Insiders forum. If you want to work with us directly on the hardened preview, join the Technology Adoption Program at aka.ms/WSTap. 
 

Carlos Mayol Berral / Christina Curlette (and the Windows Server team)

Updated Nov 17, 2026
Version 2.0
No CommentsBe the first to comment