Security as Code: Getting Started with OPA and Rego — Part 1

Why Security Policies Belong in Code — Not Documents Security policies have traditionally lived in documents — PDFs, wikis, and runbooks that describe what should happen. Engineers read them sometimes, interpret them inconsistently, and implement them manually. The gap between documented policy and enforced reality is exactly where breaches are born. Security as Code closes…

OPA

LANCE: An Open Source Framework for Automated Red Teaming of LLMs (2025)

Every New Attack Surface Arrives Before the Tooling Does SQL injection was being exploited in production years before parameterised queries became standard. Cross-site scripting tore through the early web while developers were still debating whether it was really a vulnerability. Insecure deserialization, XXE, SSRF — each one went through the same cycle: technique emerges, attackers…

lance

End-to-End LLM Security Architecture: How All the Defenses Fit Together

Introduction If you’ve followed this series from the beginning, you’ve seen the full attack landscape: direct prompt injection, indirect injection through RAG pipelines, and multi-agent cascades where a single poisoned document can ripple across an entire agent network. Each post ended with defenses specific to that attack. But defenses in isolation don’t make a security…

LLM security architecture