Enterprise foundations
Understand enterprise infrastructure and dependencies before assessment.
- Windows
- Linux
- Networking
- Virtualization
- Active Directory
- DNS
- Group Policy
Leadership to engineering
How I got here
My transition into cybersecurity was shaped by a career of accountability, preparation, and leadership under pressure. Those habits now guide how I approach technical work: understand the mission, reduce assumptions, validate the result, and document what others need to reproduce.
Why this path
Why offensive security
Offensive security is most effective when it begins with operational understanding. Assessing an enterprise environment requires more than familiarity with tools; it requires knowing how identity, infrastructure, networking, administration, and defensive visibility are designed to work together.
Building the environment is deliberate preparation for assessing it. Breadth is being developed in service of focused offensive depth—not as an end in itself.
Engineering philosophy
How I approach the work
Evidence-based, repeatable engineering creates the operational context required for credible assessment.
- Understand systems before assessing them.
- Validate complete workflows, not isolated installations.
- Document decisions so engineering can be reproduced.
- Improve the platform through reviewed evidence.
Enterprise knowledge domains
The knowledge I’m building intentionally
These domains provide the operational understanding required to assess enterprise environments effectively.
Visibility & detection
Understand what defenders can observe, investigate, and validate.
- Splunk
- Sysmon
- Windows Logging
- Telemetry
- Threat Hunting
- Detection Engineering
Automation & tooling
Create repeatable engineering, analysis, and offensive workflows.
- Python
- PowerShell
- Git
- Automation
Modern enterprise
Understand modern enterprise identity, infrastructure, and cloud visibility.
- Cloud
- IAM
- Cloud Logging
- Microsoft Entra ID — Future
Evidence over claims