AI agents are already at work inside regulated organizations: preparing payments, reading customer records, and querying systems that hold sensitive data. Every person who touches those systems was registered, authenticated, and approved for what they can do. Most agents skipped that process entirely.
That leaves three questions security, risk, and audit teams can’t answer cleanly yet. Which agents are running? Who is accountable for each one? And who can stop a high-risk action before it happens? Examiners and auditors are starting to ask them too.
Join Kenn Chong, Product Manager for Agentic Identity at RSA, and moderator Esther Yoon for a candid, practical session on bringing identity discipline to AI agents. Kenn will demo RSA Agent ID, coming November 2026, working live in a regulated scenario and take your questions.
You’ll discover:
How to find the AI agents running across your environment and give each one a named owner
How to require an authenticated human approval before the high-risk actions you designate can run
Why where agent decisions are made matters, and how to keep enforcement inside your own environment
What evidence looks like when it’s mapped to the frameworks you report against, such as NIST AI RMF, DORA, and NYDFS Part 500
Concrete use cases for financial services, government, and other highly regulated organizations
Kenn Chong
Product Manager, Agentic Identity
Esther Yoon
Mohamed Salah
Advisor, Channel Marketing
Mohamed Salah is a Channel Marketing Operations Advisor at RSA Security. He has spent more than five years at the company across Sales Operations, Revenue Operations and partner marketing. He now runs the operations side of RSA's partner marketing programs, including MDF and Co-op fund tracking, the partner relationship management (PRM) platform, and the Power BI dashboards that show fund use and campaign ROI.