Windows Server 2028’s public preview introduces a security-first default configuration for Server Core, shifting hardening from an extra task for administrators to the system’s starting state. Microsoft says the approach follows hardened government benchmarks, including DISA’s Security Technical Implementation Guide, and is intended to reduce the exposure of newly deployed servers before admins can apply security settings. The change does not apply to installations using Desktop Experience, and administrators can still choose which protections to enable. Defaults include preferring Kerberos over NTLM, strengthening protections for LSASS, limiting TLS to modern cipher suites, using hybrid post-quantum key exchange based on ML-KEM, and tightening remote desktop authentication and PowerShell script-block logging. The native NVMe storage stack, which previously required manual activation, will also be enabled by default.
The stronger defaults may disrupt older applications, protocols, authentication methods, and management scripts, so Microsoft is asking preview users to test real workloads and report what breaks. This is an early test build, not a release candidate: Secure Boot and DMA protections are not yet enforced, and blocking NTLM remains a future step. The preview also has a TLS hybrid-key-exchange race condition that can crash LSASS when a server negotiates hybrid groups; Microsoft advises disabling those groups until it is fixed. A policy-evaluation tool can help assess hardening, though Microsoft says its scoring is still being refined. The central trade-off is clearer baseline security in exchange for potential compatibility work during deployment.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.