Windows Server 2028 trades compatibility for out-of-the-box security





Hardened Defaults

Windows Server 2028 trades compatibility for out-of-the-box security

Hardened defaults align with DoD standards, but there may be growing pains.


Nick Indge

–


|

2





Photo of data server room


Credit:

Getty Images


Credit:

Getty Images




Story text








Microsoft’s Ignite announcements this week went beyond the Office-in-Copilot overhaul with the reveal of the Windows Server 2028 Public Preview and its new security-by-default stance and what Microsoft calls Hardened Server Core. Windows Server 2028 will implement a default security framework that Microsoft says is aligned with hardened DoD benchmarks, such as the Defense Information Systems Agency’s (DISA) Security Technical Implementation Guide (STIG).

STIGs work by providing a standard security framework for system administrators to follow recommended guidance. In the past, Windows Server admins were left to start from a blank canvas and then implement hardening configurations for operations. Secure baselines were available but not the default. Microsoft says that concern is now managed: “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.”

The new Windows Server 2028 hardened-by-default state will only be available for the Server Core installs. Windows Server Desktop Experience installs do not include the changed stance.

This isn’t to say that system administrators won’t still have the final say on which security protocols are activated, just that the default package now ships in a pre-hardened state. Kerberos is now the default over NTLM, with protections added to LSASS; TLS is automatically restricted to modern cipher suites; key exchange uses “hybrid post-quantum key exchange” based on the quantum-safe ML-KEM; and remote desktop authentication and PowerShell script block logging get stricter as well.


An example from Microsoft of how to check the secure state of Windows Server 2028

An example output of the MSHardenedPolicyEval system. Microsoft cautions users that the scoring tool is still being refined.

An example output of the MSHardenedPolicyEval system. Microsoft cautions users that the scoring tool is still being refined.


Credit:

Microsoft Blog


Microsoft’s native NVMe storage stack was originally introduced via an update to Windows Server 2025, but it required administrators to enable it manually. The update eliminated NVMe translation through a SCSI stack while improving speeds and reducing overhead. The redesigned stack will now be default-on in Windows Server 2028.

Microsoft is upfront, noting that the new hardened security settings may break things due to software compatibility issues with older protocols, legacy authentication, or management tools and scripts. The company encourages users to try things and provide feedback about what goes wrong. “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,” the Windows Server Team said in a blog post. “That is how the defaults get better before general availability.”

Microsoft suggests that users use the preview build as a test bed to determine where issues like compatibility still arise. This is not a release candidate build and shouldn’t be treated as such. Despite the new security stance that comes with the preview build, hardware-backed protections like Secure Boot and DMA requirements won’t be enforced until a later preview build. Kerberos is now the default preference over NTLM, but NTLM blocking itself will still have to wait for a later preview release.

Beyond those limitations, the current build has a known issue that cuts into its hardened goals. According to the release notes, “A race condition in the TLS hybrid key exchange implementation may cause the LSASS service to crash when hybrid groups are negotiated by a TLS server.” Microsoft recommends disabling hybrid-key exchange groups until the problem is addressed.

System administrators and curious homelabbers interested in testing the new Windows Server 2028 can do so by registering with the Microsoft Windows Insider Program.

Photo of Nick Indge


Nick Indge

Senior Technology Reporter
Nick Indge is a Senior Technology Reporter at Ars Technica covering hardware, embedded systems, and self-hosted infrastructure. A former security investigator turned tech writer, he writes to help readers escape subscription traps and regain ownership of their digital lives. He lives in Chicagoland with his family and a goofball husky.


2 Comments

Leer artículo original en Ars Technica