Microsoft Unveils Windows Server 2028 With Hundreds of Security Protections Enabled by Default

Blog WriterCybersecurity News - Original News Source is cybersecuritynews.com


Microsoft has released Windows Server 2028 in public preview. The biggest change is that a new server now starts in a locked-down state rather than an open one.

Hundreds of security settings are on from the first boot, so admins no longer need to harden the system by hand after setup. Microsoft announced the release on November 17, 2026.

For years, Windows Server shipped in a “compatible by default” form. Admins had to apply the Security Baseline or their own scripts to secure it. Until that work was done, every new server ran in a weaker state, and the gap was easy to miss.

In its Hardened Server Core announcement, Microsoft says this approach is changing. Admins now start from a hardened setup and relax only what a workload needs.

Layer What is hardened
Identity and authentication Kerberos is preferred over NTLM. LSASS is protected. Strong passwords and account lockout are on. Consumer accounts are not allowed.
Network exposure SMB signing and encryption are on. The firewall is on in every profile. Legacy name resolution and unauthenticated RPC are off.
Cryptography TLS is limited to modern cipher suites. Key exchange is hybrid post-quantum (ML-KEM). Stored keys get strong protection.
Privilege and admin access Admins must approve elevation. Powerful rights stay with Administrators. Guests cannot sign in. Installers cannot elevate on their own.
Platform and code integrity The sign-in process runs only Microsoft-signed code. Signature validation is stricter. The paging file is encrypted.
Remote access and observability RDP needs NLA and TLS. WinRM blocks Basic, Digest and unencrypted traffic. Advanced audit records command lines. PowerShell script block logging is on. Event logs are larger.

Hardened Settings in Windows Server 2028

The change starts with Windows Server Insider Preview build 29706, where Server Core installs hardened. The settings line up with industry benchmarks such as CIS and DISA STIG.

This closes the window in which a freshly deployed server sits exposed while it waits to be hardened. Microsoft grouped the settings by layer, and it says they were validated together so they work as a set. On identity, Kerberos is preferred over NTLM, LSASS is protected, and strong passwords and account lockout are on. Consumer accounts are not allowed.

On the network side, the server talks only over signed, encrypted, and authenticated channels. SMB signing and encryption are on, and the firewall runs in every profile. Legacy name resolution and unauthenticated RPC are off.

Cryptography also gets stronger. TLS is limited to modern cipher suites, and key exchange uses hybrid post-quantum protection with ML-KEM. Admins must approve privilege elevation, and Guests cannot sign in. The sign-in process runs only Microsoft-signed code, and the paging file is encrypted.

For remote access, RDP needs NLA and TLS. WinRM blocks Basic and Digest logins and unencrypted traffic. Audit logs now record command lines, PowerShell script block logging is on, and event logs are larger.

These choices target problems that defenders have seen for years. Cyber Security News has covered how Windows SMB client flaws let intruders take over Active Directory when relay protections are weak. Many of those cases worked because SMB signing was optional on most servers.

A proof-of-concept for CVE-2026-24294 showed the same pattern. It gave SYSTEM-level access on a default Windows Server 2025 install where signing was not enforced. Microsoft fixed that path in March 2026.

The research still warned that as long as NTLM stays common and signing stays optional, new tricks will keep appearing. Turning on signing, encryption, and Kerberos preference at install time removes much of that room. It also matches the advice researchers keep repeating.

Cymulate noted that turning off NTLM alone is not enough and that anti-relay protections must be enforced on every service. Microsoft delivers the hardened values as policy in the HKLMSOFTWAREPolicies hive wherever a component supports it. Policy wins over local settings, so a script or installer cannot quietly weaken a default.

In Microsoft’s test, trying to turn on WinRM Basic authentication was refused because policy controls it.Admins keep control. OSConfig, Group Policy or another management tool can manage the settings, and whichever tool sets a value owns it. One surprise is that gpresult and RSOP report these settings as Not Configured.

The defaults are built into the image, so there is no policy file for those tools to read. A new PowerShell module called MSHardenedPolicyEval ships in the box. The Get-MSHardenedPolicyScore cmdlet scores the server by category. In Microsoft’s example output, the server passed 191 of 237 checks, an overall score of 80.59 percent.

Restore-MSHardenedPolicy removes hardened values for one category or the whole server. Set-MSHardenedPolicy applies them again. Both support -WhatIf, so admins can preview a change before making it.

Microsoft warns that names may change in later previews, and that scores below 100 percent are expected on this build. Microsoft says some things that worked on Windows Server 2025 may break. Older protocols, legacy authentication, and some management tools and scripts are the likely trouble spots.

Teams should test apps and admin tooling against the hardened setup first. They should relax only the specific setting a workload needs.

Some protections are also still missing from this preview. These include NTLM blocking, Secure Boot and DMA protection requirements, kernel shadow stacks, and Windows Protected Print. Print and RPC hardening is also on the list, along with extra settings such as the logon banner.

The wider release adds more protection. Trusted Launch helps guarantee boot integrity across virtual machine fleets. Confidential VM support begins a path toward integrity-protected runtimes on supported hardware.

Microsoft is also working on automatic certificate management and post-quantum cryptography. Windows Server 2028 also adds native NVMe storage by default, along with NVMe over TCP and RDMA. Intune management for Windows Server is in preview, and Windows Admin Center Virtualization Mode is now generally available.

Microsoft further plans AI inference on local servers, with AMD Instinct MI350P cards in preview from the first half of 2027. The preview is open through the Windows Server Insider Program. Teams that want early access and direct contact with engineers can apply to the Windows Server Technology Adoption Program at aka.ms/WSTAP.

Admins should try the build in a lab, score it, and report any workload that breaks. Microsoft says this feedback will shape the defaults before general availability.

For now, keep patching current servers and enforce SMB signing and Kerberos where possible. Doing so will make a move to Windows Server 2028 much smoother when it arrives.

The post Microsoft Unveils Windows Server 2028 With Hundreds of Security Protections Enabled by Default appeared first on Cyber Security News.