I build defensible security systems.
Cybersecurity, AI/ML, and cyber–physical security — with a focus on the human behavior that drives breaches from the inside.
Building WeanTech: Opaque Clarity Security
I design defensible security systems across the cyber–physical boundary: identity, endpoints, cloud, logging, automation, and incident response — with a bias for measurable risk reduction and operational clarity under stress.
My background runs from Navy Master-at-Arms and Air Force Security Forces to municipal law enforcement, industrial operations, and software engineering. That path wasn't linear — it was adversarial. Every domain taught me something different about how systems fail, how people exploit gaps, and how defenders have to think if they want to stay ahead.
Security architecture
Design secure-by-default systems that remain defensible under real constraints — not just on paper.
- Identity + access (least privilege, conditional access)
- Endpoint + cloud hardening
- Logging strategy, detections, and evidence paths
- Cyber–physical integration and access control
Threat model first. No theater.
Threat model → prioritize → implement → validate. Every time. If a control can't be explained, tested, or reversed, it doesn't belong in the architecture.
- Adversary-first design
- Automation that is auditable and reversible
- AI only where it reduces toil and improves decisions
- Assume breach. Engineer the response before the incident.
- Navy Master-at-Arms
- Air Force Security Forces + CATM
- Municipal law enforcement
- Industrial Armed First Responder
- Regulatory compliance (food manufacturing)
- Cybersecurity & risk
- Cyber–physical security
- AI/ML for defense
- Insider threat & behavioral analytics
- Training & enablement
Email is the clean channel. I use Proton Mail by default.