Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is SMB Protocol Security?

SMB carries Windows file sharing and far more besides. Removing SMBv1, enforcing signing, and blocking it at the perimeter close the paths that ransomware relies on.

Illustration for the cybersecurity term SMB Protocol Security
Home / Blog / Cybersecurity Terms / What Is SMB Protocol Security?
17 November 2026

What Is SMB Protocol Security?

What Is SMB Protocol Security?

Server Message Block is the protocol behind Windows file and printer sharing, and it does considerably more than move files. Named pipes carried over SMB are how remote service control, remote registry access, and much of the Windows administrative toolkit function, which is why SMB is central to lateral movement in nearly every intrusion involving Windows estates.

The Dialects and Why SMBv1 Must Go

SMB 1.0 dates from the 1980s. It has no secure negotiation, weak signing, and a long record of memory corruption flaws. EternalBlue, the exploit behind the WannaCry outbreak on 12 May 2017 that took large parts of the NHS offline, targeted SMBv1 through the vulnerability Microsoft patched as MS17-010 two months earlier. NotPetya used the same path in June of that year.

Microsoft removed SMBv1 from default installations of Windows 10 and Server 2016 onwards and now disables the client component on machines that have not used it for a fortnight. Despite that, it survives on older network attached storage, multifunction printers, imaging systems, and manufacturing equipment, and one such device is often enough to keep the protocol alive across an estate.

SMB 2.0 introduced secure dialect negotiation. SMB 3.0, shipped with Windows 8 and Server 2012, added encryption. SMB 3.1.1, from Windows 10 and Server 2016, added pre-authentication integrity using SHA-512, which prevents an attacker downgrading the negotiation, and AES-GCM encryption. SMB 3.1.1 is the target state.

Signing and Encryption

Signing places a message authentication code on every packet, which stops an on-path attacker modifying traffic and — crucially — stops SMB relay attacks. In a relay, an attacker coerces a machine into authenticating to them, usually via LLMNR poisoning or a coercion technique such as PetitPotam, then forwards that authentication to another server. If the target requires signing, the relayed session cannot be completed.

Domain controllers have required signing by default for years. Member servers and workstations historically did not, which is exactly where relay attacks succeed. Windows 11 version 24H2 and Windows Server 2025 require SMB signing by default on all connections, which is a significant change and one worth planning for rather than discovering.

Encryption protects confidentiality in transit. Enable it per share for anything sensitive, or estate-wide if your infrastructure can absorb the cost. Note that enabling encryption on a share blocks SMBv1 clients from accessing it, which is a useful forcing function.

A Hardening Checklist

Where It Fits in an Intrusion

Understanding the attack chain makes the controls easier to justify. An attacker lands on a workstation, poisons name resolution to collect authentication, relays it to a server without signing, gains local administrator rights, dumps credentials, and uses SMB to reach the next host. Later, SMB is how they enumerate shares to find data worth stealing, and how ransomware reaches file servers.

Signing breaks the relay step. Blocking workstation-to-workstation SMB breaks the spread. Disabling SMBv1 removes the exploit path. Egress blocking stops the credential leak. None of these are expensive; they are simply rarely all in place at once. Our Infrastructure Security Testing Services test the chain end to end and report which link actually holds.

FAQ – Frequently Asked Questions

How Do I Find SMBv1 on My Network?

Enable SMB1 auditing on servers, which logs every client that connects using the old dialect, and leave it running for several weeks to catch infrequent systems. Network traffic analysis also identifies SMBv1 negotiation. The usual survivors are older network attached storage, multifunction printers, scanners, and specialist manufacturing or medical equipment rather than Windows machines.

Why Should I Block Outbound Port 445?

Because a document, email, or web page can reference a remote SMB path, causing the client to authenticate to an external server and leak its NTLM credentials. The attacker then cracks or relays them. There is no legitimate reason for a corporate workstation to initiate SMB to the internet, so blocking it outbound removes an entire phishing technique.

Does SMB Signing Affect Performance?

There is a measurable cost, historically significant on older hardware and much smaller on modern processors with cryptographic acceleration. Windows 11 version 24H2 and Windows Server 2025 require signing by default, which reflects Microsoft’s view that the protection outweighs the overhead. Test on your file servers under load, but assume the answer is to enable it.

Is SMB Encryption Necessary if the Network Is Internal?

Internal networks are not trusted boundaries. An attacker with a foothold can capture traffic, and signing alone protects integrity rather than confidentiality. Enable encryption at least on shares holding personal data, financial records, or credentials. Be aware that enabling it on a share also prevents SMBv1 clients connecting, which is usually a benefit.

Related Terms

You May Be Interested In These

What Is RPKI?

Cybersecurity Terms

17 November 2026

What Is RPKI?

Read More
What Is Electricity Market System Security?

Cybersecurity Terms

17 November 2026

What Is Electricity Market System Security?

Read More
What Is PwnKit?

Cybersecurity Terms

17 November 2026

What Is PwnKit?

Read More