Join the conversation to close the agent governance gap ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
|
|
|
|
|
|
|
Hi eddy,
86% of organizations have no insight into their AI data flows. Those agents are already running — traversing your network, touching sensitive systems, executing decisions. Some were handed corporate policies at build time. Almost none of them are being held to those policies at runtime, and almost no one is watching to find out.
The security conversation is often overly fixated on the prompt. Meanwhile, the real exposure is downstream: what the agent retrieves, what it decides, and what it does with both.
Join us for this roundtable as we discuss where the visibility gaps actually live in an agentic architecture, what a working monitoring framework looks like, and how to close the loop before your next audit does it for you.
We’ll explore how to:
- Establish continuous observability, moving beyond static logging to active governance, identifying "permission creep" in real-time before autonomous agents scale into your greatest liability.
- Neutralize indirect injections, and implement guardrails that prevent external data from hijacking internal workflows, stopping attackers from "prompting" your agents via email, web scrapes, or third-party APIs.
- Prevent autonomous exfiltration and secure unmonitored data flows to stop agents from inadvertently leaking PII, secrets, or intellectual property through non-deterministic outputs.
- Mitigate "runaway" logic & resource abuse by identifying and throttling agent overstepping and API consumption loops that create silent security incidents and "hallucinated" financial costs.
Join the conversation to close the agent governance gap and earn CPE credit for attending the live session.
Date/Time: Wednesday, May 6 @ 2:00 PM (ET)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|