Veeam unveils iResOps to track and restore data changed by AI agents
Veeam announced Veeam Intelligent ResOps (iResOps) at its VeeamON Global Launch virtual event, with Microsoft 365 as the first generally available workload. The company said iResOps for Veeam Data Platform and Okta are in private preview, with GitHub, Azure DevOps and Google IAM previews planned for the fourth quarter. In a SiliconANGLE column, analyst Zeus Kerravala argues agentic AI is merging security and data resilience, citing Veeam's survey finding that 88% of organizations use or pilot AI agents while only 7% are truly AI-ready.
Veeam CEO Anand Eswaran argues that unlike theft, data modification cannot be disclosed away and must be precisely identified and reversed, which is why the company is pitching data-side recovery as the control point for agent activity.
For two decades, security and data resilience have been neighbors who share a fence but rarely a budget. Security kept bad actors out, while resilience brought the business back when they got in. Agentic artificial intelligence is tearing down that fence, yet most organizations haven’t noticed.
Last year, I wrote that Veeam Software Group GmbH’s acquisition of Securiti AI positioned it as the industry’s first AI resiliency company. At VeeamON 2026 in May, the company foreshadowed what that would look like.
At its recent VeeamON Global Launch virtual event, Veeam announced a product: Veeam Intelligent ResOps, or iResOps, with Microsoft 365 as the first generally available workload. Whether you call it AI resiliency or resilience operations, the idea is the same. When software agents act on data at machine speed, you can’t secure what you can’t recover, and you can’t recover what you don’t understand.
Assume failure, assume breach, assume drift
Chief Executive Anand Eswaran (pictured) opened with an example that should make every chief information security officer squirm a little. A company in Spain recently told its regulator that an AI agent, acting largely on its own, breached it by finding a flaw in a live application and modifying personal data and billing records. Eswaran framed the 72-hour disclosure requirement as an engineering problem. “Somebody has to answer three questions: Which records did it change? What did it change them to? And what were they before?”
#Veeam#Veeam Intelligent ResOps#Microsoft 365#Veeam Data Platform#Okta#GitHub#Azure DevOps#Google IAM#Securiti AI#Anand Eswaran