Detection-as-code
Rules in Git, written in Sigma and the native SIEM languages, reviewed and tested like any other code.
~/scotty $ whoami
SOC Analyst → Detection Engineer
I turn alert noise into detection logic: triaging real threats in the SOC today, and building the rules that catch them earlier tomorrow.
01 About
I work in a SOC every day, which means I know exactly what a bad detection costs: the 3 a.m. notable that goes nowhere, the alert nobody trusts, the gap nobody noticed until it mattered.
Over three-plus years I moved from SOC Analyst to Tier 2, triaging and investigating across Splunk Enterprise Security, CrowdStrike Falcon and network telemetry from Corelight/Zeek and Palo Alto. I hold a master’s in cybersecurity plus Security+, TryHackMe SAL1 and ACTRA.
Now I’m deliberately moving from consuming alerts to building them: writing, testing and tuning detections, and treating the SIEM as an engineering system rather than a dashboard.
Rules in Git, written in Sigma and the native SIEM languages, reviewed and tested like any other code.
Map every rule to a technique so coverage gaps are visible, not guessed.
Tune for signal: enrich at ingest, document false positives, retire rules that do not earn their keep.
02 Toolstack
What I use on shift, what I run at home, and what I’m actively building skill in. Tagged honestly.
Notable triage, investigation and SPL searching.
ES|QL / EQL detections and Kibana investigations; also my lab SIEM.
Host monitoring and firewall syslog ingest in the homelab.
EDR alert investigation, host triage and containment.
Network metadata for hunting and detection logic.
NGFW policy and logs at work; a PA-440 guards my lab.
Tunnel, Access, DNS and edge protection.
Searches and correlation logic in Splunk.
Translating and writing detections for Elastic.
Building fluency for Microsoft-stack detections.
Vendor-neutral rules as the source of truth.
Coverage mapping and gap analysis.
LXC-based lab on a Dell PowerEdge R640.
Compose-managed SIEM and service stacks.
Serves this site with hardened headers and a hash-based CSP.
03 Projects
Open any card for the architecture, decisions and lessons.
04 Detections
Rules I write, test and tune, each tied to a technique and a data source. The framework is live; entries appear here as they ship.
Every published rule follows the same contract: a technique ID, a named data source, a severity, and documented false positives, so analysts know what it means and what it won’t catch.
# EXAMPLE TEMPLATE — shows the shape every published rule will take
title: Suspicious Encoded PowerShell Command Line
id: 00000000-0000-0000-0000-000000000000
status: experimental
description: Detects PowerShell launched with an encoded command argument.
references:
- https://attack.mitre.org/techniques/T1059/001/
tags:
- attack.execution
- attack.t1059.001
logsource:
category: process_creation
product: windows
detection:
selection_img:
Image|endswith: '\powershell.exe'
selection_cli:
CommandLine|contains:
- ' -enc '
- ' -EncodedCommand '
condition: selection_img and selection_cli
falsepositives:
- Software deployment tooling that encodes its own commands
level: medium
05 Writeups
Writeups on detection engineering, SIEM migration and self-hosted security. First posts are in the pipeline.
What breaks when a detection moves between SIEMs, and how to verify your data before you trust a rule.
A practical walkthrough of rule evaluation order, NAT interplay and service routes on a PA-440.
Hash-based CSP, per-location headers and atomic deploys for a site that is just files.
Coverage is not a count of rules. How to measure what you can actually see.
06 Resume
Grand Canyon Education
Grand Canyon Education
M.S., CybersecurityMaster’s degree
07 Contact
Open to detection engineering and security engineering roles, and always happy to compare notes on SIEM, ATT&CK and homelabs.