ProtoStackv0.1

Interactive Protocol Visualizer

Security & AuthProfessional trackAdvancedOSI: Application LayerDefault Port: 88Standard: RFC 4120

Kerberos

— Kerberos Network Authentication Protocol

Kerberos is the default authentication protocol for Microsoft Active Directory and enterprise domains. It uses trusted third-party Key Distribution Centers (KDC) to issue cryptographic Ticket Granting Tickets (TGT) and service tickets, preventing passwords from ever traveling over the wire.

Read first: UDP, TCPContent reviewed 2026-11-18

Interactive Session: How Kerberos Works

Step through the packet exchange sequence between nodes.

Interactive Execution Sandbox

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

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

Kerberoasting

Credential attack

Any authenticated user can request a service ticket for an account with an SPN and crack its password offline.

Attackersimulated
Kerberostarget
Attack step 1 of 3
Request service tickets

The attacker enumerates SPNs and asks the KDC for tickets.

What a defender can see

Many TGS requests for service accounts.

Impact if unmitigated

Service account compromise and lateral movement.

Defences that matter
  • Long random service account passwords
  • Managed service accounts and gMSAs
  • AES-only tickets and anomaly detection

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

  • Key Distribution Center (KDC) with Authentication Server (AS) and Ticket Granting Server (TGS)
  • Ticket Granting Ticket (TGT) mechanism for single sign-on without re-entering credentials
  • Mutual authentication (client verifies server, and server verifies client)
  • Timestamp-based replay protection (strict clock skew requirement <= 5 minutes)

Real-World Use Cases

  • Windows Active Directory corporate logon
  • Enterprise single sign-on (SSO) to intranet file shares (SMB/CIFS)
  • Hadoop cluster distributed authentication

Advantages & Strengths

  • Passwords never cross the network in any form
  • Single sign-on across thousands of domain services

Limitations & Vulnerabilities

  • KDC represents a single point of failure without clustering
  • Strict dependence on synchronized time via NTP