15 years securing cloud infrastructure at Palo Alto Networks, Amazon AWS, and Microsoft Azure — now building HIPAA-compliant, SOC 2-ready AI security programs for regulated companies.
"I don't consult on security programs. I build them — the same way I did at Palo Alto Networks, AWS, and Microsoft."
I started in network security at Rackspace in 2011, building automated security platforms before "security automation" was a common phrase. Three years of IDS, WAF, and Cisco ASA work taught me that the difference between a good security program and a paper one is whether it actually runs when you're not watching.
That philosophy carried through Amazon AWS, where I designed hybrid cloud architectures and led ECS automation migrations. At Microsoft, I became the escalation engineer for the company's highest-severity Azure security cases — the ones that went to senior engineers when standard support couldn't resolve them. At Palo Alto Networks I spent 4.5 years inside enterprise CSPM implementations at Fortune 500 scale, across five cloud providers, delivering HIPAA, PCI, FedRAMP, and GDPR compliance.
Now I take that full stack to regulated AI companies — healthcare AI, fintech, and AI-native startups navigating HIPAA and NIST AI RMF for the first time. I build the actual infrastructure, write the SOPs, and operate the orchestration pipelines. Not as a vendor. As the security engineer your team doesn't have yet.
Not a generalist consultant who read the documentation. I spent years as a practitioner inside AWS, Microsoft, and Palo Alto Networks before going independent.
Not surface-level familiarity. These are tools I have run in production environments at enterprise scale.
Representative engagements and the outcomes they produced. All work produced from scratch — no templated artifacts.
90 minutes. A 2-page gap report identifying your top three security exposures — no pitch, no obligation. Written by someone who has operated these programs from the inside.