Skip to content
Theme
OnDevice Tools

WindowsInsider Builds

Windows Server 2028 preview hardens security by default

Microsoft's Windows Server 2028 public preview ships with hardened security turned on by default, based on US government STIG benchmarks. The company warns the stricter setup may break older software.

Illustration of a Windows Server 2028 console showing hardened security settings enabled by default

Key takeaways

  • Windows Server 2028 ships with hardened security enabled by default, based on US government STIG benchmarks.
  • The hardened state applies only to Server Core installations, not the Desktop Experience version.
  • Kerberos replaces NTLM as the default, TLS is limited to modern ciphers, and post-quantum key exchange is added.
  • Microsoft warns the changes may break older software and notes a TLS bug that can crash LSASS.
In this article
  1. A security-first server preview
  2. What the hardened defaults include
  3. Server Core only, plus a faster storage stack
  4. Compatibility warnings and known bugs
  5. How to test the preview

A security-first server preview

Illustration: server, security, Microsoft logo, settings and the labels Microsoft, Server Core, Windows Server 2028

Microsoft has released a public preview of Windows Server 2028, and its main selling point is security that is active from the first boot. According to Ars Technica, the company revealed the build at its Ignite event and named the approach Hardened Server Core.

The change is a shift in thinking. In the past, administrators had to build a secure setup themselves, starting from a blank slate. Now the safe settings come switched on. Microsoft says this removes the risky window in which a new server is online but not yet locked down.

What the hardened defaults include

The new baseline is modelled on the security guides used by the US Department of Defense. Microsoft says the defaults align with hardened benchmarks. One example is the Security Technical Implementation Guide, or STIG, from the Defense Information Systems Agency. STIGs give administrators a standard set of steps to follow.

Several protocols now start in a stricter mode. Kerberos is preferred over the older NTLM for signing in, and the LSASS service, which handles credentials, gets extra protection. TLS, the encryption used for network traffic, is limited to modern cipher suites, which are agreed sets of encryption methods. Key exchange uses what Microsoft calls hybrid post-quantum key exchange, based on the quantum-safe ML-KEM method. This kind of encryption is designed to resist future quantum computers. Remote desktop sign-in and PowerShell script block logging are also tightened.

Server Core only, plus a faster storage stack

There is a limit on where the hardened state applies. It is only available for Server Core installations, the minimal version of the operating system that has no full desktop. The Desktop Experience installs, which include a graphical interface, do not get the new default posture.

Administrators still decide which security features to switch on, but the package now arrives pre-configured. Microsoft has also made its native NVMe storage driver the default. This driver first appeared in Windows Server 2025 but had to be enabled by hand. It removes a translation layer that used the older SCSI method, which the company says improves speed and cuts overhead.

Compatibility warnings and known bugs

Microsoft is open about the trade-off. The stricter settings may break software that relies on older protocols, legacy sign-in methods, or older management tools and scripts. Organisations that run older business software are the most likely to hit problems. The company wants feedback on which settings cause trouble for real workloads. It also wants to know which applications break and what had to change to fix them.

Some protections are not active yet. Hardware-backed protections such as Secure Boot and DMA rules, which limit direct memory access to devices, will not be enforced until a later preview. Blocking NTLM outright is also planned for a future build. The current release even works against one of its own goals. Microsoft's release notes describe a bug in the TLS hybrid key exchange code. It may crash the LSASS service when a TLS server negotiates hybrid groups. Until it is fixed, Microsoft advises turning off the hybrid key exchange groups.

How to test the preview

The preview is not a release candidate, so Microsoft warns against treating it as finished software. It is meant as a test bed for finding compatibility problems before the general release. Anyone who wants to try it, from IT staff to home lab hobbyists, can sign up through the Microsoft Windows Insider Program.

Sources

  1. Windows Server 2028 trades compatibility for out-of-the-box securityArs Technica

Tags

Spotted a mistake? See our corrections policy. Read how News by OnDevice works in our editorial policy.