ProtoStackv0.1

Interactive Protocol Visualizer

Application LayerProfessional trackIntermediateOSI: Application LayerDefault Port: 445Standard: [MS-SMB2]

SMB

— Server Message Block

SMB is the native file-sharing protocol of Windows and is implemented by Samba on Unix. SMB2 and SMB3 carry file operations, authentication, and locking over TCP port 445, with SMB3 adding encryption, signing, and multichannel throughput.

Read first: TCPContent reviewed 2026-11-18

Interactive Session: How SMB Works

Step through the packet exchange sequence between nodes.

Interactive Execution Sandbox

Interact with a live or clearly-labelled simulated instance of SMB.

Threat Model & Attack Simulation

How this protocol is attacked in practice, what defenders can see, and which control stops it.

Threat model & attack simulation

Simulated

Defensive education. Every step runs in this page; no traffic is generated or sent.

Attack library

NTLM relay

Interception

Coerced authentication is relayed to another SMB server that accepts NTLM, granting the attacker the victim session.

Attackersimulated
SMBtarget
Attack step 1 of 3
Coerce authentication

The victim is tricked into authenticating to the attacker.

What a defender can see

Outbound SMB or WebDAV authentication attempts.

Impact if unmitigated

Lateral movement with the victim privileges.

Defences that matter
  • Require SMB signing
  • Disable NTLM where possible
  • Extended Protection for Authentication and segmentation

This is a conceptual model for defenders, not an exploit toolkit. It contains no payloads, tooling or instructions for attacking systems you do not own.

Protocol Specification & Architecture

Key characteristics, real-world deployment patterns, and trade-offs.

Core Technical Features

  • SMB2 NEGOTIATE selects the dialect and capabilities for the session
  • SESSION_SETUP authenticates with NTLM or Kerberos and yields a session id
  • CREATE, READ, WRITE, and CLOSE operate on file handles called FileIds
  • SMB3 adds AES encryption, signing, leases, and multichannel

Real-World Use Cases

  • Windows file shares mapped as network drives
  • Domain-controller SYSVOL and Group Policy distribution
  • Samba shares for mixed Windows and Linux networks

Advantages & Strengths

  • Native integration with Windows ACLs, Active Directory, and Group Policy
  • SMB3 encryption and signing protect data and integrity in transit

Limitations & Vulnerabilities

  • Historically targeted by ransomware and relay attacks
  • Legacy SMB1 is insecure and should be disabled