█████╗ ██████╗ ██╗ ██████╗ ██╗ █████╗ ██╔══██╗██╔══██╗██║██╔═══██╗██║ ██╔══██╗ ███████║██████╔╝██║██║ ██║██║ ███████║ ██╔══██║██╔══██╗██║██║ ██║██║ ██╔══██║ ██║ ██║██████╔╝██║╚██████╔╝███████╗██║ ██║ ╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═════╝ ╚══════╝╚═╝ ╚═╝
I've spent the last five years working the overlap between IT operations and security. Not purely one or the other: device management at scale, then federal security work, and now both running at the same time.
The early years were endpoint and infrastructure. ExxonMobil Bay Area, then BART, where I came up from intern to analyst to administrator to where I am now. Mixed Windows and macOS fleets, JAMF, Intune, SCCM, BigFix, full lifecycle from imaging through retirement. Large user bases, transit infrastructure, real operational pressure.
The role that shifted my focus was MSTS, supporting the DOE Special Technologies Laboratory in Santa Barbara. Infrastructure Analyst II and Cyber Security Analyst II on the same seat. Federal environment under DOE security requirements: NIST 800-61, Tenable Nessus vulnerability assessments, SIEM monitoring, and infrastructure availability where compliance gaps have real consequences. Working in that environment made security feel like the actual job, not a layer on top of it.
Outside the day job I run a home lab. Wazuh SIEM, Suricata IDS, Kali Linux for attack simulation. I've run Hydra brute-force attempts, Metasploit sessions, and nmap sweeps against my own environment and tuned detection rules off the alerts. I build tooling and infrastructure outside work to stay sharp — this site runs on the same VPS I administer daily.
CompTIA Security+ certified (SY0-701), pursuing VMware VCP-DCV. Currently in the Bay Area, relocating to Dallas, TX. Targeting cybersecurity analyst and IT infrastructure roles. Open to remote.