Skip to content
StrikeCyberStrikeCyber
Field Manual · Concept

SMB Signing

Reviewed November 14, 2026Concept 2 min read

Quick answer

SMB signing adds a cryptographic signature to Windows file-sharing traffic so it cannot be tampered with or relayed. It only protects you when it is required, not just enabled: a server that merely allows signing can still be targeted by NTLM relay attacks, which are one of the most common paths to domain compromise in internal tests.

On this page

SMB is the protocol Windows uses for file shares, printers and much of its remote administration. Without required signing, an attacker who captures a Windows login can relay it to a server and act as that user, often as an administrator. Requiring SMB signing is one of the highest-value, lowest-cost hardening changes in an Active Directory network.

01

How It Works

When signing is in use, each SMB message carries a signature derived from the session key, which only the genuine client and server know. A relayed connection cannot produce valid signatures, so a server that requires signing rejects it.

SettingWhat it meansStops relay?
Not supported or disabledNever signsNo
Enabled (negotiated)Signs only if the other side asksNo
RequiredRefuses unsigned connectionsYes

The two Group Policy settings that matter are "Microsoft network server: Digitally sign communications (always)" and "Microsoft network client: Digitally sign communications (always)", under Computer Configuration, Windows Settings, Security Settings, Local Policies, Security Options.

02

Why It Matters

In internal penetration tests, servers without required signing are one of the most common reasons a single compromised account leads to wider access. Combined with coercion techniques such as PetitPotam or poisoning with Responder, an attacker can relay machine and user logins to every server that does not require signing.

03

How to Test for It

  1. List every host that does not require SMB signing (tools such as NetExec report this across a network in minutes).
  2. Check domain controllers (required by default), file servers, application servers and workstations separately.
  3. Check non-Windows SMB devices such as NAS appliances and printers.
  4. In an authorized test, confirm whether a relayed login gives access to any of those hosts.
04

How to Reduce the Risk

Require SMB signing for servers and clients through Group Policy, starting with servers that hold sensitive data or where privileged users log in, then workstations. Test file-heavy workloads first, upgrade or isolate devices that cannot sign, and remove SMBv1 entirely. Then close the other relay targets: LDAP signing and channel binding and AD CS web enrollment, and work towards restricting NTLM.

05

Regulatory and Framework Context

For US organizations, SMB signing is part of CIS Benchmarks for Windows and CISA and NSA Active Directory hardening guidance. We check it in every internal penetration test and Active Directory security assessment.

Latest intel on this topic

Updated hourly from the daily briefing.

Common questions

What is the difference between SMB signing enabled and required?

Enabled means a device will sign if the other side asks. Required means it refuses unsigned connections. Only required stops relay attacks, because an attacker simply does not ask for signing.

Does SMB signing slow things down?

Signing adds some processing overhead, which was noticeable on older hardware and high-throughput file servers. On modern systems the impact is usually small, but test heavy file workloads before enforcing everywhere.

Is SMB signing required by default now?

Newer Windows releases require signing by default for more connections, including Windows 11 version 24H2 and Windows Server 2025. Older servers, upgraded systems and non-Windows devices often still do not, so check rather than assume.

Does SMB signing stop all relay attacks?

No. It stops relay to SMB. Attackers can still relay to LDAP, AD CS web enrollment and other services, so LDAP signing and channel binding and Extended Protection are needed too.

Change log

  1. November 14, 2026First published.
(877) 657-8496