Microsoft has opened public preview of Windows Server 2028, introducing a major shift in how servers are secured out of the box. Instead of shipping in a permissive state and relying on admins to lock things down, new installations now start in a hardened configuration. Hundreds of security features are enabled by default at first boot—meaning less manual effort is required to meet baseline security standards.
What’s Locked Down—and How It Compares to Prior Practices
Under the new “Hardened Server Core” model, the initial setup follows strict policies across a number of critical security layers. On identity and authentication, Kerberos is preferred over NTLM, the Local Security Authority Subsystem Service (LSASS) gets protection, strong password rules and account lockout are enforced, and consumer accounts are disallowed. Network protections include mandatory encryption and signing for Server Message Block (SMB), active firewalls on every profile, and disabling of legacy name resolution and unauthenticated RPC.
Cryptographic standards are updated as well: TLS is restricted to modern cipher suites and key exchange uses hybrid post-quantum methods (specifically ML-KEM). Administrative privileges must be approved; guest accounts are blocked; installers can’t elevate themselves. Platform integrity measures include only allowing Microsoft-signed code during sign-in and encrypting the paging file. Remote access safeguards enforce NLA with TLS for RDP, block WinRM use of Basic and Digest authentication, and require encrypted traffic. Auditing is beefed up: enhanced event logging, PowerShell script block logging, and command-line recording are on by default in this preview release.
Where It’s Still In Flux & How to Prepare
This hardened baseline starts with Insider Preview build 29706, which integrates settings aligned with benchmarks such as CIS and DISA STIG. All key components supporting these protections use policy settings under HKLM\SOFTWARE\Policies, meaning that built-in defaults cannot be quietly overridden by local scripts. Microsoft supplies tools: Get-MSHardenedPolicyScore to measure compliance (e.g. in testing the server met 191 of 237 checks, scoring ~80.6%), Set-MSHardenedPolicy to apply hardened settings, and Restore-MSHardenedPolicy to roll back category-specific or full server settings—all supporting a -WhatIf option for previewing changes.
Caveats: Some protections aren’t yet enforced in this preview—NTLM blocking across all components, Secure Boot, DMA protections, kernel shadow stacks, and hardened printing or RPC features. Legacy management tools or scripts may fail under these stricter defaults. The broader release is expected to bring additional protections (like Trusted Launch, confidential VM runtimes, automatic certificate management, and post-quantum cryptography) along with performance and compatibility testing tools.
Administrators should run this preview in labs first, test workloads against hardened defaults, and identify which settings need relaxation only for legitimate functional needs. In the meantime, ensuring SMB signing, Kerberos‐first authentication, and robust firewalls on current servers will ease the transition to Server 2028.
Why this Matters: This shift signals Microsoft’s recognition that weak defaults have long been exploited—security hardening after installation has been a known gap. By embedding stronger protections upfront, Windows Server 2028 aims to reduce the window in which new deployments are vulnerable. But this also puts pressure on organizations: tools, scripts, and legacy applications may confront breaking changes.