Engineer. Securing the systems that run things.

Security engineer working at the intersection of operational technology, industrial networks, and AI-enabled automation.

The through-line of my career is systems that cannot afford to fail. It started in military communications, RF and satellite, moved into large-scale IP network engineering, and is now focused on the security of industrial environments where software increasingly makes physical decisions. When OT and AI share infrastructure, the question is not whether to secure the boundary but how to do it without breaking the thing you are trying to protect.

The technical scope is deliberately wide. I work across IEC 62443 compliance, remote access architecture, cross-domain risk, and the instrumentation needed to make an estate legible. Problems that fall between disciplines are the ones I tend to be called in for.

In parallel, I have spent the past year building in Python: MLOps pipelines, data lineage, drift detection, adversarial robustness. The goal is the same as on the OT side, make the system observable, make failure recoverable, keep humans in a position to intervene.

I hold an MSc in Cyber Security. My dissertation examined how cryptographic transparency mechanisms could strengthen provenance and identity in industrial supply chains. Signatures and attestation logs are now standard tools; distributed ledgers where they genuinely reduce risk, not as a reflex.

I measure outcomes, not effort. Lower MTTR, fewer false positives, safer change windows. Simple architectures that can be understood and recovered. Code that replaces runbooks. Earlier in my career I founded and closed an AI company, not because it failed, but because the timing was wrong. That decision shaped how I think about pragmatism and commitment.