AppSec · DevSecOps · LLM Red Teaming. I attack RAG pipelines, map prompt injection to OWASP LLM Top 10, and build automated guardrails before adversaries find the gap.
I started in Electrical and Electronics Engineering, then moved deliberately into cybersecurity. I hold a Master's in Cybersecurity Operations and Leadership from the University of San Diego (3.98 GPA, Merit Scholarship) and 3+ years of experience in AppSec, DevSecOps, and AI security.
My work sits at the intersection of offensive and defensive security. I run deep-dive application, API, and AI security assessments in federal and enterprise environments, build and harden CI/CD pipelines, and architect cloud security controls in AWS and GCP.
My current focus is LLM and AI agent security: prompt injection, data poisoning, model leakage, supply-chain compromise, and RAG/agentic workflows. I hold the CAISP certification, have attacked and hardened RAG systems, and actively map AI attack surfaces to OWASP LLM Top 10 and MITRE ATLAS.
I believe security teams should be enablers, not gatekeepers — so I build tooling and workflows that make the right security decisions the easy ones.
I mentor through WiCyS and spoke at The Diana Initiative 2026 on AI security fundamentals.
Hands-on attacks and defenses mapped to OWASP LLM Top 10 and MITRE ATLAS. Click any case study to expand.
Problem
A RAG-based AI assistant was exposed to potential prompt injection and data leakage risks. Could an attacker extract PII by manipulating retrieval context or user prompts?
Approach
What broke
Guardrails built
Problem
A sentiment classifier in production was vulnerable to adversarial inputs that could flip predictions while preserving semantic meaning, bypassing human review.
Approach
What broke
Guardrails built
Problem
AI-powered features were being shipped without LLM-specific security checks. Traditional pipeline scanning missed prompt injection patterns and model integrity risks.
What I built
Pipeline stages
Portfolio projects demonstrating hands-on AI security research and tooling.
| STRIDE | THREAT | RISK |
|---|---|---|
| Spoofing | Attacker spoofs user identity | Critical |
| Spoofing | Adversary deploys fake AI model (evil twin) | Medium |
| Tampering | Attacker tampers with training data (poisoning) | High |
| Tampering | Malicious data injected into trained model weights | Medium |
| Repudiation | Attacker deletes or alters audit logs | Medium |
| Info Disclosure | AI system discloses PII / confidential data | Critical |
| Info Disclosure | Attacker reverse-engineers model via repeated queries | High |
| Denial of Service | Attacker floods AI service with excessive requests | Critical |
| Denial of Service | Overload training resources / crash pipeline | Medium |
| Elevation | Exploit API Gateway / Auth to reach training pipeline | Medium |
Security practitioners are increasingly handed AI targets to audit — yet many still treat the model as a black box. This talk opens that box: eight processing layers between user input and model output, each one mapped to its attack surface. From tokenization tricks that bypass WAFs to temperature abuse at inference time — with every attack mapped to OWASP LLM Top 10 and MITRE ATLAS.
Practical, grounded-in-real-attack-surfaces writing. Built for people who actually build and break things.
Open to full-time AI security, AppSec, and DevSecOps roles, consulting, and speaking engagements. Whether you're building something that needs to be secure or something that needs to be broken — I'm interested in the conversation.
If you're hiring for AI security, AppSec, or DevSecOps, I'm especially interested in roles where I can red team AI systems and build guardrails.