Windows Server 2025 Hardening Checklist: 25 Steps to Secure Your Server

Windows Server 2025 Hardening Checklist: 25 Steps to Secure Your Server

A fresh Windows Server 2025 install is more secure than any earlier version, but “secure by default” isn’t the same as hardened. Default settings have to work for every customer, so they leave doors open that most small and medium businesses don’t need.

This checklist walks through 25 practical hardening steps, grouped by area, with PowerShell commands to check each one. It’s written for IT generalists and small IT teams looking after a handful of servers, not for a dedicated security team with a SIEM and a six-month project plan.

Before you start: test changes on one server first, make sure you have a working backup, and change one area at a time. Hardening that breaks a line-of-business application isn’t a win.

1. Plan the server’s role

1. Install only what the server needs

Every role, feature and application adds code that can be attacked. List what the server is for (file server, domain controller, application server) and remove everything else.

Get-WindowsFeature | Where-Object Installed | Select-Object Name, DisplayName

Remove anything you don’t need with Uninstall-WindowsFeature -Name <FeatureName>.

2. Prefer Server Core where possible

Server Core has no desktop experience, which means fewer components to patch and attack. Domain controllers, DNS, DHCP, file servers and Hyper-V hosts run well on Core and can be managed remotely with Windows Admin Center or PowerShell.

3. Don’t run other software on domain controllers

Domain controllers should be domain controllers. No file shares for users, no web browsing, no line-of-business apps, no remote-access tools that aren’t strictly needed.

2. Patching and updates

4. Install updates monthly, within days of release

Most successful attacks on servers use vulnerabilities that already have a patch. Set a monthly maintenance window shortly after Microsoft’s Patch Tuesday and stick to it. Use Windows Server Update Services (WSUS), Azure Update Manager or your RMM tool to track compliance.

Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

5. Consider hotpatching

Windows Server 2025 supports hotpatching for Azure Arc-connected servers (as a paid subscription) and for Azure Edition. Hotpatches install most security updates without a reboot, which makes it much easier to patch quickly. See our guide to Azure Arc for on-premises servers.

6. Keep firmware and drivers current

Update BIOS/UEFI, RAID controllers, network cards and the out-of-band management controller (iLO, iDRAC, XClarity). Out-of-band controllers are often forgotten, and they give full control of the hardware.

3. Accounts and administration

7. Use separate admin accounts

Administrators should use a normal account for email and browsing and a separate account for server administration. Never browse the web or read email while signed in as a domain admin.

8. Keep Domain Admins small

Check who is in the most powerful groups and remove anyone who doesn’t need permanent membership:

Get-ADGroupMember "Domain Admins" | Select-Object Name, SamAccountName
Get-ADGroupMember "Enterprise Admins" | Select-Object Name, SamAccountName

Add privileged accounts to the Protected Users group, which blocks weaker authentication methods such as NTLM and cached credentials for those accounts. Test first, because some older applications break.

9. Manage local administrator passwords with Windows LAPS

If every server shares the same local administrator password, one compromised server gives the attacker all of them. Windows LAPS is built into Windows Server 2025. It sets a unique, rotating password for each server’s local admin account and stores it in Active Directory or Microsoft Entra ID.

For Active Directory, extend the schema once and grant computers permission to update their own passwords:

Update-LapsADSchema
Set-LapsADComputerSelfPermission -Identity "OU=Servers,DC=example,DC=com"

Then enable LAPS through Group Policy (Computer Configuration > Administrative Templates > System > LAPS).

10. Disable or rename unused built-in accounts

Make sure the Guest account is disabled and remove any old local accounts created for vendors or testing:

Get-LocalUser | Select-Object Name, Enabled, LastLogon

11. Use MFA for remote administration

Put remote admin access behind multi-factor authentication. Options include Remote Desktop Gateway with MFA, a VPN with MFA, or a privileged access tool. Never expose RDP directly to the internet.

4. Network protocols

12. Make sure SMBv1 is off

SMBv1 is obsolete and was used by WannaCry and NotPetya. It’s not installed by default on modern Windows Server, but in-place upgrades and old installation scripts can bring it back.

Get-WindowsFeature FS-SMB1
Get-SmbServerConfiguration | Select-Object EnableSMB1Protocol

If it’s enabled, remove it: Uninstall-WindowsFeature -Name FS-SMB1.

13. Require SMB signing

SMB signing protects against relay and tampering attacks. Windows Server 2025 tightens SMB signing defaults, but upgraded servers and mixed environments can still have it optional. Check both sides:

Get-SmbServerConfiguration | Select-Object RequireSecuritySignature
Get-SmbClientConfiguration | Select-Object RequireSecuritySignature

Set it with Group Policy (“Microsoft network server: Digitally sign communications (always)”) or Set-SmbServerConfiguration -RequireSecuritySignature $true. Older NAS devices and printers that scan to SMB shares sometimes don’t support signing, so test first.

14. Reduce NTLM and enforce LDAP signing

NTLM is older and weaker than Kerberos. Start by auditing NTLM use (Group Policy: “Network security: Restrict NTLM: Audit incoming NTLM traffic”), then block it where nothing depends on it. On domain controllers, require LDAP signing and channel binding to stop LDAP relay attacks.

15. Disable services you don’t use

The Print Spooler is a frequent target. If a server doesn’t print or share printers, especially a domain controller, disable it:

Stop-Service -Name Spooler
Set-Service -Name Spooler -StartupType Disabled

Review the other running services with Get-Service | Where-Object Status -eq Running.

16. Use only modern TLS

Make sure TLS 1.0 and 1.1 are disabled and that TLS 1.2 and 1.3 are used for web, RDP and application traffic. Newer Windows builds disable the old protocols by default, but upgraded servers and application settings may re-enable them. Tools such as IIS Crypto make this easier to check.

5. Firewall and remote access

17. Keep Windows Defender Firewall on for all profiles

Get-NetFirewallProfile | Format-Table Name, Enabled, DefaultInboundAction

All three profiles should be enabled with inbound traffic blocked by default. Don’t turn the firewall off “to fix a problem”. Add a specific rule instead.

18. Restrict RDP to management networks

Limit Remote Desktop to the IP addresses or subnets your admins use, and make sure Network Level Authentication is required:

(Get-CimInstance -Namespace root\cimv2\terminalservices -ClassName Win32_TSGeneralSetting).UserAuthenticationRequired

A value of 1 means NLA is on.

19. Restrict WinRM and management ports

Remote PowerShell (WinRM), WMI and Windows Admin Center should only be reachable from admin workstations or a jump server, not from the whole network.

6. Protection against malware and credential theft

20. Turn on Microsoft Defender protections

Make sure real-time protection and tamper protection are on, and that signatures update daily:

Get-MpComputerStatus | Select-Object AMServiceEnabled, RealTimeProtectionEnabled, IsTamperProtected, AntivirusSignatureLastUpdated

If you use another EDR product, check its equivalent. Enable attack surface reduction (ASR) rules in audit mode first, then block mode.

21. Protect credentials in memory

Credential Guard and LSA protection make it much harder for attackers to steal password hashes with tools such as Mimikatz. Credential Guard is enabled by default on Windows Server 2025 member servers that meet the hardware requirements. Check its status with:

Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard | Select-Object SecurityServicesRunning

A 1 in the results means Credential Guard is running. Enable LSA protection as well (Group Policy: “Configure LSASS to run as a protected process”). Test with your backup and monitoring agents first.

7. Logging and monitoring

22. Enable advanced audit policies

Default auditing misses important events. Check the current policy:

auditpol /get /category:*

At a minimum, audit logon events, account management, security group changes, process creation and policy changes. Increase the Security log size (for example to 1 GB) so events aren’t overwritten within hours.

23. Enable PowerShell logging

Attackers love PowerShell. Turn on script block logging and module logging through Group Policy (Administrative Templates > Windows Components > Windows PowerShell). This records what scripts actually ran.

24. Send logs somewhere central

Logs that stay on the server can be deleted by the attacker. Forward them to a central log server, SIEM or Microsoft Sentinel, or at least to a Windows Event Collector server. See our guide to network monitoring.

8. Baselines and backups

25. Apply a security baseline and keep backups you can restore

You don’t have to configure hundreds of settings by hand. Use one of these:

  • Microsoft security baselines from the Security Compliance Toolkit, applied with Group Policy
  • OSConfig on Windows Server 2025, which applies Microsoft’s baseline with PowerShell and keeps it from drifting
  • CIS Benchmarks, which also explain why each setting matters

Start in a test environment and roll out in stages.

Finally, hardening reduces risk but doesn’t remove it. Keep offline or immutable backups, back up the system state of domain controllers, and test a full restore at least twice a year. See our server hardening overview for the wider picture.

Windows Server 2025 hardening checklist (summary)

AreaCheck
RoleOnly required roles and features installed; Server Core where possible
UpdatesMonthly patching; firmware and BMC updated
AccountsSeparate admin accounts; small Domain Admins group; Protected Users
Local adminWindows LAPS enabled
Remote accessNo internet-exposed RDP; MFA for remote admin; NLA on
ProtocolsSMBv1 off; SMB signing required; NTLM reduced; LDAP signing on DCs
ServicesPrint Spooler disabled where not needed; unused services off
TLSTLS 1.0/1.1 disabled
FirewallAll profiles on; inbound blocked by default; management ports restricted
MalwareDefender real-time and tamper protection on; ASR rules
CredentialsCredential Guard and LSA protection on
LoggingAdvanced audit policy; PowerShell logging; central log collection
BaselineMicrosoft baseline, OSConfig or CIS applied
RecoveryOffline or immutable backups; restore tested

Work through the list one area at a time, and keep a short record of what you changed and when. Our next guides cover the Windows 11 workstation hardening checklist and Linux server hardening.