Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

We asked eight security and product leaders who's accountable when an agent ships to production and breaks something. Nobody said the model. Harish Gaggar named the reason. An agent runs on permissions someone approved and configuration someone set. Ron Reiter drew the line in the same place, accountability sits with whoever decided what the agent could actually do. As agents act across more systems, the accountability trail gets harder to follow. Most teams cannot determine which human granted an agent access.

Autonomous AI agents writing and executing code at machine speed present an urgent compliance challenge for modern software organizations. As global regulations tighten, engineering leaders must establish clear governance layers over agentic workflows, external tool calls, and Model Context Protocol integrations to ensure full accountability. In this session, Mend.io experts Asaf Saar and Ben Goldberg unpack the intersection of AI compliance, software supply chain security, and enterprise risk management. Learn how to bridge the accountability gap without sacrificing development velocity.

This demo shows a CloudCasa DR failover for a file-server application running on HPE Kubernetes Service clusters. - HPE Kubernetes Service clusters (or HKS) is HPE’s managed Kubernetes offering, provisioned through the HPE Morpheus VM Essentials console. A primary HKS cluster runs the file-server app on a volume backed by an HPE Alletra MP B10000 array, replicated to a second Alletra array at a recovery site where a second HKS cluster stands ready.

In the video you are currently watching, we will show CloudCasa failing the same file-server application back from the recovery site to the original primary site, once the primary is healthy again.