Red teaming AI agents before they ship
About this event
Guardrails hold when something goes wrong, but they don’t tell you whether something will go wrong before your users find out. That’s what red teaming is for.
Here’s a pattern the Ejento team often sees. An agent passes every eval, answers accurately, stays grounded, and still gets talked into breaking its own rules by a user who knows how to push it. Evaluation asks “does this agent give good answers?” Red teaming asks “can I make it misbehave?”
We will share our experience and take questions from the audience.
What you'll learn
- Why red teaming, guardrails, and evaluation are different questions, and why you need all three
- Key categories of adversarial testing: jailbreaks, prompt injection, data exfiltration, policy evasion, role abuse
- How red teaming an LLM differs from traditional penetration testing
- Why automated red team runs need to happen on every deployment, not just once before launch
- A live look at the red teaming dashboard inside the Ejento platform



