Rubrik Announces 2026 Cyber-Recovery Expansions for AWS, DevOps and Google Cloud

What Rubrik Just Expanded Across AWS, Azure and Google Cloud

Rubrik has announced new cyber-recovery capabilities spanning three major public clouds in one release: deeper protection for AWS workloads, a DevOps Protection Enterprise Edition covering Azure DevOps and GitHub, and general availability of agentless, immutable backup for Google BigQuery alongside Google Cloud Storage. The company is also extending Hourglass, its project to secure autonomous AI agents such as Anthropic's Claude Code, according to Blocks & Files.

Chief Product Officer Anneka Gupta framed the AWS additions as delivering "continuous cyber resilience from initial detection through complete business recovery" — Gupta's framing of Rubrik's positioning, rather than confirmation that Rubrik now operates as an end-to-end incident response layer.

Why Multi-Cloud Backup Complexity Is Becoming a Board-Level Risk

The sheer granularity of this release — different detection windows, different recovery mechanics, different retention models for AWS, Azure DevOps/GitHub and Google Cloud — illustrates a problem that may be familiar to UK infrastructure teams: protection policies and recovery evidence can become fragmented once application teams self-manage their own cloud workloads.

That fragmentation is exactly why comparing suppliers like Veeam, Rubrik, and Commvault has become a specialist exercise rather than a procurement checkbox. As vendors layer detection, blast-radius analysis and surgical recovery onto every cloud service separately, UK resilience teams need a consolidated view of what is actually covered before they can sign off a renewal with confidence.

AWS: Faster Detection, Narrower Blast Radius, Surgical Recovery

On AWS, Rubrik has announced near real-time deletion detection that is designed to flag the removal of critical cloud resources within seconds rather than at the next scheduled backup, plus a centralised impact investigation view and sensitive-data blast-radius reporting using LLM-powered classification. These capabilities are expected to become generally available in the coming months.

Rubrik has also announced a surgical recovery feature designed to remove malicious or encrypted files from cloud VMs and roll forward clean changes, rather than rolling back an entire VM to a prior snapshot — intended to reduce data loss compared with a full restore. This capability is likewise expected to become generally available in the coming months.

Autonomous Business Recovery for AWS Cloud Applications is now generally available and extended beyond EC2 instances and RDS databases to containerised workloads on Amazon EKS, Amazon ECR, AWS Lambda functions and Amazon S3. ABR's goal is to recover an organisation's minimum viable business — the applications and services that keep revenue, customers, employees and operations running — and is designed to establish and use a verified, pre-incident clean recovery point, via a Preemptive Recovery Engine that continuously identifies that clean state before an incident occurs.

Azure DevOps and GitHub: Treating Source Code as a Recovery Asset

Rubrik has announced a DevOps Protection Enterprise Edition that is intended to connect anomaly detection, blast-radius investigation and surgical recovery for Azure DevOps and GitHub into a single workflow, with these cyber-recovery capabilities expected to become generally available in the coming months. The planned workflow would baseline audit logs against Rubrik backup metadata to flag suspicious identity activity, map which repositories, commits, pipelines, workflows, pull requests and settings were touched, and recover only the attacker's changes rather than forcing an organisation-wide code freeze.

Rubrik has also announced broader Foundation Edition backup coverage — issues, pull requests, Azure Boards, wikis, packages and organisation settings — so that recovery can eventually restore the full developer collaboration context, not just the code itself. Gupta noted that "one stolen token or poisoned dependency can impact thousands of repositories before anyone notices," a comment that, for UK organisations, may raise board-level questions about source-code resilience.

For UK software and fintech teams holding both code repositories and VM estates, this reinforces the case for clean room recovery vaults — air-gapped, immutable copies that remain trustworthy even if production identity systems are compromised.

BigQuery and Google Cloud Storage: Protecting the AI Data Layer

Rubrik's framing for BigQuery is explicit: as AI agents move from pilot to production, BigQuery is no longer just a data warehouse but the layer agents reason over and act on. The new GA capability backs up whole datasets or single tables, with views and routines intact, at what Rubrik describes as petabyte scale, recoverable in place or exported to another project or region.

Backups can be stored in a customer's own Google Cloud Storage bucket or in Rubrik Cloud Vault using Object Retention Locks for immutability, with setup described by Rubrik as agentless and achievable in minutes. Rubrik says it overcomes BigQuery's native seven-day time-travel limit with unlimited retention and unified compliance reporting — a capability that could be relevant for UK organisations in regulated sectors, subject to their own retention and compliance obligations.

What UK Buyers Should Do Before Their Next Renewal

Rubrik's broader strategy — anomaly detection, threat scanning, ransomware recovery, sensitive-data discovery, and now agent-facing telemetry via Model Context Protocol — is pushing cyber recovery well beyond traditional backup. For UK infrastructure buyers, that raises a practical question: does your current estate actually need protection across three clouds, or are you paying for breadth you'll never use?

No public list pricing has been identified for these capabilities, and enterprise buyers should expect cost to depend on protected capacity, workload type, retention and which cyber-recovery features are switched on. Before committing, run the likely blast radius of an AWS, GitHub or BigQuery incident through a backup and DR sizing calculator to see whether consolidating onto one platform genuinely reduces cost and complexity, or simply relocates it. Teams still weighing options — including those considering migrating from Veeam to Rubrik — should separate currently available functionality from anything still rolling out before locking in a multi-year contract.