As reported by BleepingComputer, Microsoft used its Ignite 2026 platform to unveil Windows Server 2028, and the headline that matters most to defenders isn't the AI accelerator support or NVMe-over-TCP — it's the hardened Server Core configuration enabled by default. This is a philosophical shift worth pausing on.
Why Secure-by-Default Is the Real Story
For most of Windows Server's history, security hardening has been an opt-in exercise. Administrators deployed the OS, then layered Group Policy, DISA STIGs, or CIS Benchmarks on top to compensate for defaults that prioritized compatibility and ease of use. Windows Server 2028 inverts that model: hundreds of hardening settings ship enabled from first boot, and the burden shifts from adding security to justifying any relaxation.
The most important security control is the one that's on when nobody's looking. Defaults shape outcomes more than policies do.
The specific defaults Microsoft has described — Kerberos over NTLM, LSASS protection, SMB signing and encryption enforced, firewall active in every profile, TLS restricted to modern suites, WinRM rejecting Basic/Digest/unencrypted, RDP requiring NLA — collectively close attack paths that adversaries have abused for years. Credential theft via LSASS dumping, NTLM relay attacks, SMB downgrade attacks, and RDP brute-force intrusions all become materially harder at the platform level rather than at the policy level.
Post-Quantum Readiness Signals Long-Term Thinking
Notably, Windows Server 2028 ships with hybrid post-quantum key exchange using ML-KEM for TLS. While quantum cryptanalysis isn't an active threat today, Microsoft's decision to bake ML-KEM into the default cipher suite is a forward-looking signal. Organizations subject to long-data-lifetime confidentiality requirements — healthcare, defense, financial services — should factor this into their server refresh planning. Harvest-now-decrypt-later remains a strategic concern for data with decades-long sensitivity windows.
Where the Gaps Remain
Microsoft was candid that several hardening items are still in progress: NTLM blocking, hardware-backed platform protection, and print/RPC hardening are not yet in the default baseline. Defenders managing environments where NTLM is still present should not assume Windows Server 2028 will eliminate that exposure on day one. Similarly, while Trusted Launch and Confidential VM support extend boot integrity to virtualized workloads, the value depends heavily on whether your hypervisor and cloud provider support the underlying CVM hardware.
Operational Implications for Enterprises
Shield53 Recommendations
- Begin a compatibility audit of all server-hosted applications against the published Windows Server 2028 hardening baseline. Prioritize anything using NTLM, SMB1, unauthenticated RPC, or Basic-auth remote management.
- Inventory NTLM dependencies now. Since NTLM blocking isn't yet in the default baseline, use the transition period to identify and eliminate NTLM usage so you're not blindsided when Microsoft adds it.
- Pilot Trusted Launch and Confidential VMs in non-production environments to validate hypervisor and hardware support before committing to production rollouts.
- Update hardening documentation — your existing CIS or STIG-based baselines may need reconciliation against Microsoft's new defaults rather than wholesale replacement.
- Establish AI workload security policies for the new inference capabilities. Treat model deployment endpoints as any other network-exposed service: authentication, logging, network segmentation, and access review.
Windows Server 2028 won't eliminate the need for layered defense, but it meaningfully raises the floor. The organizations that benefit most will be those who treat the migration not just as an OS upgrade, but as a security architecture refresh.