Microsoft Pushes Default-Hardened Security in Windows Server 2028 Preview
The public preview marks a shift toward out-of-the-box protections that may break legacy tooling, as Microsoft asks administrators to test and report compatibility friction before general release.
A Shift in Default Posture
Microsoft has released the first public preview of Windows Server 2028, and the build signals a deliberate change in philosophy: security protections that previously required manual activation will now ship enabled. The company acknowledges that this approach may introduce friction with older software, legacy authentication mechanisms, and existing management scripts, but it is treating the preview phase as an opportunity to map those pain points before the operating system reaches general availability.
The preview represents a bet that the cost of breaking some existing workflows is worth the reduction in attack surface for organisations that deploy the server platform without deep security expertise. By inverting the default, Microsoft is effectively asking: which protections can remain on for the majority of deployments, and where does genuine business need justify an exception?
NVMe Storage Stack Now Default
One concrete example of the new approach is the native NVMe storage stack, which Microsoft introduced as an opt-in feature in an update to Windows Server 2025. That stack bypassed the translation layer that had previously routed NVMe commands through a SCSI compatibility shim, cutting overhead and improving throughput. In Windows Server 2028, the native stack will be active by default.
The change reflects a broader pattern: features that improve performance or security but require administrator action to enable often see low adoption, even when the trade-offs are favourable. By making the native NVMe path the default, Microsoft is assuming that most new server deployments are running on hardware that benefits from the direct approach, and that the older translation path can be relegated to a fallback for edge cases.
Kerberos Preference and NTLM Blocking
Authentication is another area where the preview build adjusts defaults. Kerberos is now the preferred protocol over NTLM, a shift that aligns with long-standing security guidance but has historically been left to administrators to enforce. NTLM, which dates to the 1990s and lacks the cryptographic protections of Kerberos, remains a common vector for credential relay attacks.
The preview does not yet block NTLM entirely; that enforcement is planned for a later build. The staged rollout suggests Microsoft is aware that many enterprise environments still rely on NTLM for specific applications or legacy systems, and the company wants to gather data on where those dependencies exist before making the protocol unavailable by default.
Hardware-Backed Protections Deferred
Notably, the current preview does not enforce hardware-backed security features such as Secure Boot or direct memory access (DMA) protections. Those requirements will appear in a subsequent preview release. The phased introduction indicates that Microsoft is prioritising software-layer hardening first, likely because those changes can be tested and adjusted more easily than hardware prerequisites, which may force organisations to audit or replace physical infrastructure.
The deferral also suggests that the company is still calibrating the acceptable floor for hardware requirements. Secure Boot has been a standard feature on client devices for years, but server deployments often involve longer hardware refresh cycles and a wider variety of form factors, including embedded systems and appliances that may not support the same firmware features as rack-mounted units.
Known Issue in TLS Hybrid Key Exchange
The preview build ships with a documented flaw that undermines some of its hardening goals. A race condition in the implementation of TLS hybrid key exchange can cause the Local Security Authority Subsystem Service (LSASS) to crash when a TLS server negotiates hybrid groups. LSASS is a critical component responsible for enforcing security policy and handling authentication, and a crash can disrupt service availability.
Microsoft has recommended disabling hybrid key exchange groups as a temporary workaround until the issue is resolved. The presence of this bug in the initial preview underscores the experimental nature of the release; the company is explicit that this is not a release candidate and should not be deployed in production environments.
Feedback as a Design Input
Microsoft is framing the preview as a collaborative exercise. The Windows Server Team has asked users to report specific scenarios where the hardened defaults interfere with real workloads, including which setting caused the problem, which application was affected, and what configuration change was needed to restore functionality. That level of detail is intended to inform decisions about which defaults can remain strict and which may need to be relaxed or made conditional.
The request for feedback reflects a recognition that server environments are heterogeneous. A setting that works well for a greenfield deployment running containerised workloads may break a line-of-business application that has been in production for a decade. By gathering data during the preview phase, Microsoft can identify patterns and decide whether certain legacy behaviours warrant continued support or whether the ecosystem should be nudged toward newer alternatives.
Implications for Asia-Pacific Deployments
The shift toward hardened defaults has particular relevance for organisations in Asia-Pacific markets, where server infrastructure often spans a wide range of maturity levels. In markets such as Singapore and Hong Kong, cloud-native deployments and modern DevOps practices are common, and the new defaults may align well with existing security postures. In contrast, sectors such as manufacturing and logistics in markets including Thailand, Vietnam, and Indonesia may still rely on older enterprise resource planning systems and custom management scripts that assume NTLM availability or specific storage behaviours.
For managed service providers and system integrators operating across the region, the preview period offers a window to audit client environments and identify dependencies that may require adjustment. The cost of that work must be weighed against the security benefit of reducing the number of legacy protocols and configurations that remain active by default.
Testing and Adoption Path
System administrators and infrastructure teams interested in evaluating the preview can register with the Microsoft Windows Insider Program to gain access to the build. The company has emphasised that the preview is intended for testing and feedback, not for production use. Organisations considering an eventual migration to Windows Server 2028 can use the preview to validate compatibility with existing applications, management tooling, and automation scripts.
The preview phase also provides an opportunity to assess whether the hardened defaults align with internal security policies or whether specific settings will need to be adjusted. For organisations that have already adopted a zero-trust architecture or implemented strict network segmentation, the new defaults may require little additional configuration. For those with more permissive environments, the preview can serve as a forcing function to identify and remediate legacy dependencies.
A Broader Industry Trend
Microsoft's approach with Windows Server 2028 reflects a broader industry shift toward secure-by-default configurations. Similar patterns have emerged in other enterprise platforms, where vendors are increasingly willing to accept short-term compatibility friction in exchange for long-term reductions in attack surface. The challenge lies in calibrating those defaults so that they protect the majority of users without imposing undue burden on organisations with legitimate technical constraints.
The success of this strategy will depend in part on how effectively Microsoft can use the preview feedback to refine the final release. If the company can identify and accommodate the most common compatibility issues, the hardened defaults may become a net positive for the ecosystem. If the final release ships with settings that break widely used applications or management tools, adoption may be slower, and organisations may revert to less secure configurations to maintain operational continuity.
The preview build of Windows Server 2028 is available now through the Windows Insider Program, with additional features and enforcement mechanisms expected in later preview releases ahead of general availability.



