OpsAgents AI Invite Michal

// speaker

Michal Shatz

Founder, OpsAgents AI · building reasoning agents since 1999

The question that decides an enterprise AI deployment is not “is it accurate”. It is “who is accountable when it acts”.

Michal Shatz on stage at AINext Dubai 2026, holding a microphone

// featured talk

Cybersecurity in the Age of Generative AI

AINext Awards & Conference Dubai 2026 · panel · 22 October 2026 · Crowne Plaza Dubai, Deira

Full answer · 2:35

The moderator, Amit Grover, asked how companies can give AI agents real access to systems and still keep control. Michal’s answer: stop treating the agent as software.

For decades security was deterministic. The bug lived in the code, and so did the vulnerability, and attackers used deterministic tools against deterministic systems. An agent is not deterministic. It behaves more like a new employee than like a program, so manage it like one:

  • the same boundaries and zero trust you give a new hire
  • evals, harnesses and checks inside the agent loop
  • more freedom only after it passes the test you set
  • boundaries that stay in place even when trust grows

Autonomy is earned, not granted. That is the idea behind SOSA, the methodology OpsAgents AI builds on.

On the panel with Rizwan Shaikh, Chris Michael, Christopher Booth and AbdelRahman El-Sergani.

// clips

Short cuts from the panel

Is an AI agent software or an employee? 0:44
Why AI broke the old security model 0:40
How much should you trust an AI agent? 0:41
AI is not deterministic. Neither is a new hire 0:27
Test it, and keep the boundaries 0:16
Give the deterministic work to tools 0:26
Stop making your agent do deterministic work 0:22

// topics

What Michal speaks about

An agent is a new hire, not software

Why the deterministic security model breaks on AI agents, and how onboarding, least access and zero trust carry over from people to agents.

Autonomy is earned, not granted

Giving agents real access step by step: tests inside the loop, a human on anything that cannot be undone, and a log of every action and whose authority it ran on.

Architected, not prompted

Designing agent systems that are governed and supervised from the start, instead of assembled from prompts and patched later.

The supervision gap

“Most companies are buying AI. Very few are learning to supervise it.” What teams need to learn so their people stay accountable for what agents do.

// bio

About Michal

Michal Shatz has been building reasoning agents since 1999, when she modelled a lawyer’s reasoning in a Hebrew Prolog-style language at a Weizmann Institute programme for Israel’s Ministry of Education. That was more than two decades before the current wave, not adjacent to it. At Reichman she worked on hologram-based virtual presence, letting a busy person send a version of themselves into a meeting, and drew European research funding for it. She went on to spend years shipping regulated, high-stakes software, applications that unlock cars and move live insurance payments, and the security and compliance work that comes with it.

Today she is the founder of OpsAgents AI, where she designs the agent architecture rather than prompting it. She is a certified Claude Developer and Claude Architect, and ten people on her team are completing the same certification. Her position: the companies that win will not be the ones that bought AI. They will be the ones whose people learned to supervise it.

// on stage

Photos

The AINext Dubai 2026 cybersecurity panel on stage, with the session title on the screen behind Panel line-up at AINext Dubai 2026, Michal Shatz second from left Michal Shatz listening on stage, her name card on the screen behind Michal Shatz on a second AINext Dubai 2026 panel

Invite Michal to your stage

Keynotes, panels and closed-door sessions on AI agent security, governance and supervision. In English.

michal@opsagents.agency →