About

I'm a security engineer with more than ten years in corporate IT, security operations and security engineering. Most of my work has been identity, endpoint security, detection and incident response. At one company I was the first internal owner of IT and security.

Resume (PDF) LinkedIn Email

Experience

Certifications and education

GCIH · CompTIA Security+ · CompTIA Network+ · CompTIA A+ · CompTIA Secure Infrastructure Specialist (CSIS)
Economics, CSU East Bay

How I work

I test access by trying things that should fail. If a monitoring account can delete backups, I want to find that out myself.

I keep security decisions in code. In my triage agent, the model summarizes and suggests, and code validates every tool call. The agent has no tools that change anything. Actions that would need my approval are designed but not built yet.

I check the logs before I call something done. In one test the Okta console showed a permission as granted. The audit log showed it wasn't, and the log was right.

When something looks broken, I measure it before I fix it, and I keep my notes when I turn out to be wrong. One of my write-ups is about that.

I keep secrets out of my repos and my logs. Every push to this site runs gitleaks and a check for internal hostnames and IDs.

In my lab

The tools I use in my homelab. My work tools are in the experience above.

IdentityOkta: Terraform provider, OAuth service apps, admin roles, network zones, MFA policy
DetectionElastic Security, Sigma and pySigma, threshold rules, test cases kept with each rule
InfrastructureLinux, Docker, systemd timers, Elasticsearch snapshots and restore tests, Tailscale
AutomationPython, Bash, Terraform, unit tests with fakes in place of outside services
AI securityAn agent with read-only tools and limits on each run, prompt-injection tests; approval for actions designed, not built yet
Email and domainCloudflare DNS and Email Routing, DMARC monitoring

Resume

Download my resume (PDF) or find me on LinkedIn.