Industry

Windows Server 2028 Preview Prioritizes Security Out of the Box, With Caveats

Microsoft's latest server operating system ships with hardened defaults aligned to military security standards, but administrators will need to test for compatibility issues before the general release.

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

At its Ignite conference this week, Microsoft unveiled the Windows Server 2028 Public Preview, introducing what the company describes as a security-first approach through a feature called Hardened Server Core. The new operating system will deploy a default security posture that Microsoft says mirrors hardened Defense Information Systems Agency (DISA) Security Technical Implementation Guide (STIG) benchmarks used by the Department of Defense.

Traditionally, system administrators began with a baseline configuration and then layered on hardening measures after deployment. STIGs provide a standardized framework for this process, but applying them has always been optional. Microsoft is changing that model. "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 company stated.

The hardened-by-default configuration applies only to Server Core installations. Windows Server Desktop Experience deployments will not receive these changes.

Security Changes in the Preview

System administrators retain control over which security measures remain active, but the new baseline ships pre-configured with multiple protections. Kerberos becomes the preferred authentication method instead of NTLM, with added safeguards for LSASS. Transport Layer Security (TLS) connections automatically restrict themselves to current cipher suites. Key exchange now employs what Microsoft calls "hybrid post-quantum key exchange" based on the quantum-safe ML-KEM standard. Remote desktop authentication and PowerShell script block logging both receive stricter enforcement.

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. Credit: Microsoft Blog

Microsoft's proprietary NVMe storage stack, initially rolled out as an optional update to Windows Server 2025, will become enabled by default in the 2028 version. That stack removes NVMe translation through a SCSI layer, delivering faster performance and lower computational overhead.

Compatibility Concerns and Testing Requirements

Microsoft acknowledges that the hardened defaults could create problems for environments running older software, legacy authentication systems, or outdated management utilities and scripts. The company is actively soliciting feedback during the preview phase. "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 wrote in a blog post. "That is how the defaults get better before general availability."

The preview build is intended as an experimental platform for identifying compatibility gaps, not as a release candidate. Several security features will not be enforced until subsequent preview builds arrive. Hardware-backed protections including Secure Boot and DMA requirements remain optional for now. NTLM blocking itself will not be mandatory until a later preview release, though Kerberos is already the default preference.

The current preview contains a known defect that undermines its security 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 as a temporary workaround until the issue is resolved.

Administrators and enthusiasts can access the Windows Server 2028 preview by enrolling through the Microsoft Windows Insider Program.

Source: Ars Technica · Reporting supplemented by The Silicon Ledger staff.