Critical Infrastructure & Security
Securing what matters most
Overview
- Period
- April 2011 – May 2019
- Overview
- Securing what matters most
- Engagements
- 3
Positioning
By 2011, the conversation around infrastructure had shifted — it was no longer enough to build systems that worked; they had to be hardened against failure, intrusion, and consequence. I moved into an environment where the stakes were fundamentally different: the systems I was responsible for didn't just support operations, they underpinned decisions that affected public safety and national continuity. That context sharpened everything.
Over nearly a decade, I architected and governed critical infrastructure at a scale where downtime wasn't a service metric — it was a crisis. Security wasn't a layer added at the end; it was the foundational constraint around which everything else was designed. I learned to think in threat models before I thought in architectures, and to treat resilience not as a feature but as a discipline. That shift in perspective — from building for performance to building for trust — became one of the defining lenses I carry into every engagement that followed.
Engagements
Arriving early
The technology transitions arrive in wave 2.