I strive to build and protect essential services that people rely on, and keep them secure and resilient. For me that means city water and wastewater plants, police and fire networks, courts, emergency operations and public utilities, the systems most people never think about until they stop working.

I’m a security engineer who cares less about shiny dashboards and more about whether a team can find the real signal, close the right risk, and sleep after an incident.

By day I’m a Senior Security Engineer at Resultant, delivering managed cybersecurity for municipal government clients across Indiana. That means alert triage, account takeover investigations, vulnerability ownership, and deciding whether a risky login is a real compromise or a salesperson on hotel Wi-Fi. Before that I ran the cybersecurity risk program for the City of Carmel, covering 25+ policy domains for a city of 100,000 residents, including water treatment, wastewater, police, fire and emergency operations.

I got here the long way. I started at a county sheriff’s office, then worked cable installation, a hospital service desk, a NOC watching 25,000 route miles of fiber, network engineering, threat intelligence, DevOps in a HIPAA shop, a SOC and municipal security. That’s fourteen years in IT, eight of them in security. The useful part of that route is that I’ve operated every layer I’m now responsible for defending, so when I ask an infrastructure team to change something, I know what I’m asking of them.

What I believe Link to heading

Noise is a security failure. An alert that fires 154 times without meaning trains people to ignore the next one that matters. Tuning, exceptions and clear ownership are security work, not housekeeping.

Automation should shrink time-to-decision. The Python reporting framework I built didn’t exist to impress a demo. It cut monthly vulnerability analysis from hours to under 30 seconds so humans could act.

Programs outlast people. When I left Carmel, the runbook and handoff package covering 40+ segments mattered as much as the posture score. Security that depends on one brain isn’t security.

Write down the trade-offs. On Scott’s Lab I document specific problems in specific environments, what I chose, what it cost, and what I’d do differently. No listicles.

Serving the community Link to heading

I volunteer with the Indiana Civilian Cyber Corps, the Indiana Adjutant General’s program that brings Hoosier cybersecurity professionals together to provide training, advisement and incident response support to organizations that couldn’t otherwise respond to a cyber incident. My application to InfraGard Indiana, the partnership between the FBI and the private sector to protect critical infrastructure, is pending.

I’m also a member of the Cyber Leadership Institute and am completing induction into the WGU chapter of the National Society of Leadership and Success, both part of my move toward security leadership.

Outside the ticket queue Link to heading

The Lab is where that work gets published. It covers a home-lab SIEM with custom detections, forensics pipelines, Ansible and Ludus automation, open tools, and notes on AI in security ops. I also keep public security utilities on GitHub and experiment with AI coding agents and MCP-integrated automation in sandboxed, credential-scoped setups.

I’m CISSP-certified through ISC2 and studying for the CCSP. I’m also working through Microsoft’s SC-300, SC-200, SC-500 and SC-100 track and Elastic’s Security for SIEM training, and I expect to finish my B.S. in Cybersecurity and Information Assurance at Western Governors University in June 2027.