Microsoft framed the release as a security-forward, performance-aware update to its server platform. The company shipped Windows Server 2028 with a hardened Server Core configuration enabled by default and introduced a new security baseline designed so administrators can selectively relax settings where necessary. The announcement pairs a long checklist of default protections with management and performance changes intended for large deployments and modern workloads.
Hardened Server Core defaults
Windows Server 2028's most visible change is the decision to ship Server Core in a hardened state from first boot. The company published an extensive list of default settings covering identity, network exposure, cryptography, privilege controls, platform integrity, and remote access. Highlights described by Microsoft include:
- Identity and authentication: Kerberos over NTLM, LSASS protected, strong passwords and account lockout, and no consumer accounts.
- Network exposure: SMB signing and encryption, firewall on in every profile, legacy name resolution and unauthenticated RPC disabled.
- Cryptography: TLS limited to modern cipher suites, hybrid post-quantum key exchange (ML-KEM), and strong protection for stored keys.
- Privilege and admin access: elevation requires admin approval, powerful rights reserved for Administrators, Guests cannot sign in, and installers cannot self-elevate.
- Platform and code integrity: the sign-in process runs only Microsoft-signed code, signature validation is stricter, and the paging file is encrypted.
- Remote access and observability: RDP with NLA and TLS, WinRM without Basic or Digest or unencrypted traffic, advanced audit with command lines, PowerShell script block logging, and larger event logs.
Microsoft acknowledged the configuration is not yet complete: the company said it is still working on adding NTLM blocking, hardware-backed platform protection, print and RPC hardening, and additional settings drawn from the “hundreds of security settings enabled from first boot.”
New security baseline and administrative flexibility
The release pairs default hardening with a new security baseline that, per Microsoft, allows administrators to relax specific settings where operational requirements demand. That baseline is positioned as a means to reduce the work required to reach a secure posture “from day 1.” The baseline and hardened defaults together aim to make a tighter configuration the easiest path for new and refreshed servers, while preserving the ability for shops with legacy dependencies to adjust individual controls.

This site is the portfolio.
OSINTSights runs on Cloudflare Workers, D1, R2, and Vectorize, with an AI pipeline on Hetzner ARM. Nubivance designed, built, and operates it. We do the same for clients.
See what we buildTrusted Launch, Confidential VMs, and platform integrity
Microsoft called out platform-focused protections meant to extend integrity guarantees into virtualized environments. Trusted Launch is described as extending protection to virtual machines and “guaranteeing boot integrity across your VM fleet.” The company also said Confidential VM support “begins a journey to support integrity‑protected runtimes on supported CVM hardware.”
These platform changes align with the broader platform and code integrity defaults: sign-in enforcing Microsoft-signed code and stricter signature validation, together with encryption of the paging file, are intended to reduce attack surface at the lowest levels of the stack.
Management at scale, NVMe performance, and new AI accelerators
Windows Server 2028 adds management and performance features targeted at large and persistent server fleets. Intune management for Windows Servers brings endpoint-management workflows—configuration, compliance, applications, and updates—to eligible, persistent servers, according to Microsoft.
Performance changes include native NVMe storage enabled by default, support for NVMe over TCP and RDMA transports, and the ability to boot from ReFS. Microsoft also announced new AI accelerators and management for accelerated hardware: admins can deploy and configure inference environments, manage accelerated hardware, and run open-weight and custom models. The company named supported runtimes and model frameworks including Windows ML, Foundry Local, vLLM, and Llama.cpp.
Neil Hinnant framed this as the start of a broader push: “It also begins our long term investments extending Microsoft Foundry to bring AI inference to fleets of local token factories, giving customers more choices to put the right intelligence in the right place with the right cost structure.”
What this means for technologists, procurement leaders, and adversaries
- Technologists and security teams: will gain a default posture that emphasizes Kerberos, modern TLS, stricter code signing, and expanded telemetry (command-line audit, larger event logs), but must plan for remaining gaps—Microsoft signaled NTLM blocking, hardware-backed platform protections, and print/RPC hardening are still in progress.
- Procurement and operations leaders: should evaluate Intune management for persistent servers, NVMe-by-default storage, NVMe-over-TCP/RDMA transports, and the option to boot from ReFS when planning hardware refreshes or new server purchases; early access routes include the Windows Insider Program for Windows Server or the Windows Server Technology Adoption Program (TAP).
- Adversaries and red teams: will face host- and VM-level integrity measures such as Trusted Launch, enforced Microsoft-signed sign-in code, stricter signature checks, and encrypted paging—factors that raise the bar for certain classes of attack but leave noted areas (NTLM, hardware-backed protections) as potential windows while Microsoft finishes work.
Microsoft presented Windows Server 2028 as a major release that couples default hardening with management and AI-centred features aimed at enterprise customers. Administrators who want to test the platform are directed to the Windows Insider Program for Windows Server or to apply for earlier access through the Windows Server TAP. The record is concrete about what ships now and what Microsoft says it will harden next—NTLM blocking, hardware-backed protections, and additional RPC/print mitigations remain explicitly on the company’s to-do list.




