Back to Enterprise Identity Defense Lab

BLUE TEAM · DETECTION ENGINEERING

Kerberoasting Detection Lab

Active Directory + Wazuh SIEM

MITRE ATT&CK T1558.003Event ID 4769Event ID 4104Event ID 4688WazuhActive DirectoryPowerShellGroup Policy

Overview

Objective

Build a realistic blue-team lab where a domain workstation requests a Kerberos service ticket for an SPN-backed service account, then trace useful activity across the endpoint, domain controller, and SIEM.

Environment

wazuh
Ubuntu Server · SIEM
dc01
Domain Controller · LAB.LOCAL
win10-lab
Domain-joined endpoint
svc_sql
SPN-backed service account

Telemetry chain

4769
Kerberos service ticket request
4104
PowerShell script block content
4688
Process creation and command line
Wazuh
Centralized collection and review

Evidence

1 · Audit policy

Kerberos Service Ticket Operations auditing enabled on dc01 via Group Policy; the policy is associated with Event ID 4769.

Domain controller audit policy verification in PowerShell

2 · SIEM telemetry

PowerShell Script Block Logging (Event ID 4104) from win10-lab ingested and reviewed in the Wazuh Threat Hunting dashboard.

Wazuh Threat Hunting event details showing PowerShell Operational telemetry from the lab endpoint

3 · Process evidence

Event ID 4688 records setspn.exe -T lab.local -Q */* spawned from PowerShell for SPN enumeration in the lab.

Windows process creation event 4688 with setspn command line details

Click a screenshot to view it full size.

Lab outcome

Enabled Kerberos and endpoint auditing, routed PowerShell telemetry to Wazuh, and validated the investigation trail against the source Windows logs.

Tools: Wazuh · Active Directory · Windows Event Logging · PowerShell · VirtualBox

This project was conducted in an isolated learning environment. Screenshots retain lab-only hostnames and private network addresses.