← CCDC profile

REPORT./001

Competition defense

CCDC Leadership & Defense

How I organized weekly defensive practice, built shared infrastructure, and led a 15+ member team to first place in Kentucky.

Role
President + team captain
Cadence
Weekly practice
Environment
Windows, Linux, AD, Proxmox
Result
1st place in Kentucky

Practice defense as an operating system.

Team brief

CCDC combines service availability, system hardening, incident response, and business communication under time pressure. My job was to turn those demands into repeatable weekly practice for more than 15 members.

Connect people, platforms, and priorities.

LeadSet practice objectives and assign system ownership.
BuildMaintain Windows Server, Active Directory, Linux, and Proxmox labs.
CoachTeach hardening, persistence review, firewalling, and incident response.
CoordinateKeep evidence, escalation, and status updates moving across the team.

Give every service a named defender.

ServiceNamed owner
BaselineKnow normalHardenReduce exposureMonitorDetect driftEscalateShare context
A clear owner ties service health, configuration changes, suspicious activity, and communication together.

First place in Kentucky.

The placement mattered, but the lasting result was a stronger practice culture built around documentation, accountability, and calm response.

01Weekly repetition
02Shared infrastructure
03Clear ownership
04Coordinated response
The strongest defenders pair technical depth with organization under pressure.

Team leadership, Windows and Linux administration, Active Directory, virtualization, hardening, persistence detection, incident response, and operational communication.