Lockdown Lab #21 HIGH Windows Server

Disable SMBv1

Disable SMBv1

WannaCry, NotPetya, EternalBlue. If those names don’t send a shiver down your spine, you’ve been lucky. The common thread? SMBv1. This isn’t ancient history; it’s still a live threat.

SMBv1 is an obsolete protocol. There’s no legitimate reason for it to be running in any modern environment. Even patched systems are vulnerable to new zero-days targeting this specific protocol. Keeping it enabled is just asking for trouble.

This is basic hygiene. Do it. The commands are straightforward and remove a massive attack surface.

Here’s how: Set-SmbServerConfiguration -EnableSMB1Protocol $false -Force Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol -NoRestart

If you haven’t done this, you’re leaving a gaping hole. Close it today.

The fix

# PowerShell

Set-SmbServerConfiguration -EnableSMB1Protocol $false -Force

# Disable SMBv1 client

Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol -NoRestart

Reference: CIS Windows Server Benchmark 18.3.3

Mark this as done

Open the interactive hardening checklist and tick this off in your environment.

Open interactive checklist →

Related Posts

Enable Windows Firewall on all profiles

How many times have I seen "unauthorized access" turn out to be a lack of basic perimeter control? Far too many. If your Windows Servers...

lockdown-labhardeningwindowsnetwork
/Shimi Cohen

Require NTLMv2 and refuse LM/NTLMv1

Stop handing attackers your credentials on a silver platter. I've seen far too many environments where a simple NTLM relay or brute-force attack on weak...

lockdown-labhardeningwindowsidentity
/Shimi Cohen

Enforce account lockout policy

Brute-force attacks against user accounts are not sophisticated, but they are incredibly effective. If your Windows Servers aren't locking accounts, you're essentially providing an infinite...

lockdown-labhardeningwindowsidentity
/Shimi Cohen