Pontos principais

• A soberania mínima viável (MVS) concentra-se em aplicar o nível adequado de controle às cargas de trabalho certas.
• Tratar todas as cargas de trabalho da mesma forma pode levar a complexidade e custos desnecessários ou a proteção insuficiente.
• As organizações geralmente se enquadram em três perfis de soberania: soberania total, empresa regulamentada e multicloud híbrido.
• A governança consistente em ambientes mistos é um dos maiores desafios operacionais.

There is a version of the digital sovereignty conversation that leads organizations somewhere expensive, operationally burdensome, and – if they’re being honest – further than their actual obligations require. Maximum sovereignty sounds responsible. In practice, it’s often a miscalibration.

There is an equally common version that leads somewhere dangerously thin – controls that satisfy a checklist but wouldn’t survive an audit, an incident, or a regulator who has stopped accepting documented intent as proof of demonstrated control.

The organizations that get sovereignty right tend to do something more rigorous and more practical than either extreme: They ask what they actually owe, to whom, and for what. Then they build to that standard – no more, no less.

This is the discipline of MVS, introduced in the Relatório de Readiness para a Soberania Digital  and developed in full here.

MVS isn’t a shortcut. It’s a recognition that the goal is the right level of control, applied consistently, across every workload that requires it.

Nem todas as cargas de trabalho são iguais

The starting point for an MVS approach is workload classification – and most organizations skip it entirely.

A trading system processing regulated financial data carries fundamentally different sovereignty obligations than an internal HR collaboration tool. A database holding personal data of EU citizens is subject to a different legal and regulatory regime than a development environment running anonymized test data.

Treating all of these identically – either by applying maximum sovereign controls across the board or by assuming a single deployment model covers everything – is how organizations end up either over-engineered or under-protected.

The right question before any deployment decision: What does this workload require across each of the four sovereignty pillars? The Readiness Report includes a self-assessment structured around exactly that question.

The Three Profiles – and What They Actually Need

As empresas regulamentadas se enquadram em três perfis reconhecíveis, cada um com diferentes motivadores principais e prioridades de investimento.

• The True Sovereign. Government agencies, defense contractors, and critical national infrastructure operators. For these organizations, sovereignty is not a compliance requirement – it is an operational mandate. Maximum control over every dimension of the technology stack is often legally required, and the cost tradeoffs are accepted because the alternative is not.
• The Regulated Organization. Financial services firms, healthcare organizations, energy companies. These organizations face binding requirements from DORA, NIS2, GDPR, and sector-specific frameworks. Compliance obligations may also map to EU certification schemes – including EUCS, EUCC, BSI C5, and SecNumCloud – depending on sector and deployment context.

on-negotiable in certain areas – particularly around data residency, operational access controls, and recovery within jurisdictional boundaries. But not every workload carries the same obligation.

• The Hybrid Multi-Cloud Organization. Organizations with existing hyperscaler investments facing increasing sovereignty pressure from customers, regulators, or procurement requirements. Their challenge is not wholesale migration – it’s layering sovereign controls onto a mixed estate and maintaining consistent governance across it.

O custo de um ajuste incorreto

Over-engineering sovereignty creates its own operational risks. Organizations that apply maximum sovereign controls to workloads that don’t require them absorb cost and complexity that serves no regulatory or business purpose.

Under-engineering is the more common failure mode, and the more dangerous one. It typically doesn’t show up until the audit arrives – or, more seriously, until an incident occurs and recovery becomes a legally constrained problem. (That failure mode is the subject of the quarta postagem desta série.)

Um ponto de partida prático

Uma abordagem MVS segue três etapas:

1. Classify workloads by their actual sovereignty requirements across each pillar – don’t start with deployment models.
2. Mapeie cada classe de carga de trabalho para o nível de implantação que atenda a esses requisitos, em todo o espectro, desde regiões de hiperescaladores públicos até nuvem pública soberana e ambientes gerenciados no local.
3. Govern the resulting mixed estate consistently – controls, audit evidence, and recovery capabilities must be demonstrable across the full environment, not just the most-sovereign tier.

The third step is where most programs struggle. Maintaining consistent sovereignty controls across a mixed estate is an operational governance challenge – and specifically the domain of Operational Sovereignty – tema da terceira postagem desta série, o pilar que a maioria das estratégias trata como algo secundário.

Use a autoavaliação doRelatório de Readiness para a Soberania Digitalpara identificar sua posição atual em todos os quatro pilares.

Perguntas frequentes

P: O que é soberania mínima viável (MVS)?

R: O MVS é a prática de aplicar controles de soberania com base nas necessidades reais da empresa e nas exigências regulatórias. Seu objetivo é ajudar a evitar tanto o excesso de complexidade quanto a proteção insuficiente.

P: Por que a classificação da carga de trabalho é importante?

R: Cargas de trabalho diferentes acarretam obrigações regulatórias e operacionais distintas. A classificação das cargas de trabalho ajuda as organizações a aplicar o nível adequado de controles de soberania.

P: Quais são os três perfis comuns de soberania?

R: Os três perfis são: organizações verdadeiramente soberanas, organizações regulamentadas e organizações híbridas em multicloud. Cada um deles apresenta requisitos operacionais e de conformidade distintos.

P: Quais são os riscos decorrentes de uma abordagem excessivamente técnica em relação à soberania?

R: Controles excessivos podem aumentar a complexidade operacional e os custos sem gerar conformidade significativa nem valor comercial.

P: Por que os ambientes mistos geram desafios de governança?

R: As organizações costumam operar em diversos modelos de nuvem e infraestrutura. É difícil manter controles, evidências de auditoria e padrões de Recovery consistentes em todos os ambientes.

Ruben Renders é Diretor de Soluções, MSP, na Commvault.

Pontos principais

• Data residency addresses where data is stored, but digital sovereignty also requires control over access, operations, and proper understanding of jurisdictional implications.
• Operational sovereignty is often the weakest and least-audited part of most sovereignty programs.
• A complete sovereignty posture depends on four pillars: data locality, technological sovereignty, operational sovereignty, and jurisdictional sovereignty.
• Sovereignty is not binary; organizations must define a posture aligned to their regulatory and operational obligations.

Here is a question worth sitting with: When your organization made its sovereignty decision, what exactly did it decide?

For most, the answer is some version of the same thing. Pick a region. Move the workloads. Choose a cloud provider with data centers in-country. Check the box. The question of where data lives was answered, and the sovereignty conversation was considered closed.

But it wasn’t closed. It had barely started.

Data residency answers one question: Where? Digital sovereignty asks three more – who, how, and under what conditions?

The conflation of residency with sovereignty is understandable. Hyperscalers have made region selection feel like a sovereignty decision. Compliance checklists ask where data is stored. Regulatory guidance, at least in its earlier iterations, focused heavily on geography.

Choosing a sovereign cloud region is a real thing – it matters, it has operational implications, and it’s a necessary first step. But it is only a first step. And most organizations stopped there.

What Residency Doesn’t Answer

Think of it this way: Choosing a sovereign cloud region is like buying a safe. It tells you where your valuables are stored. It says nothing about who has a copy of the combination, who manufactured the safe, which country’s laws govern the manufacturer, or whether you can open it if compelled to.

Region selection answers one question. Three more remain entirely open – and these are the questions regulators, procurement committees, and auditors are now asking with increasing precision:

• Who can operate your environment, and from where? Whether your cloud provider’s support personnel are subject to foreign jurisdiction is a sovereignty question that data residency cannot resolve. A routine maintenance window performed by a support engineer in a different legal jurisdiction is an access pathway your residency policy doesn’t cover. This is the domain of Operational Sovereignty – the hardest pillar to audit and the most commonly overlooked.
• Under what legal regime can your data be accessed? A foreign technology provider operating infrastructure in-country does not automatically remove the reach of their home jurisdiction’s law. The extraterritorial reach of foreign legal regimes is a risk that geography alone cannot eliminate.
• Can you recover your data if something goes wrong? Most sovereignty programs are built around access control. Very few address recovery – whether your data can be restored cleanly, within defined tolerances, by personnel who operate within your sovereignty boundary. That gap is where sovereignty postures most commonly fail under real conditions.

The Framework that Fills the Gap

A complete sovereignty posture spans four interdependent pillars. The Relatório de Readiness para a Soberania Digital – available at readiverse.com – walks through each in full. In brief:

• Data locality addresses where data and metadata actually travel.
• Technological sovereignty covers control over encryption, key custody, and architecture portability.
• Operational sovereignty covers who runs the environment and from where.
• Jurisdictional sovereignty establishes the legal framework governing and affecting all of the above.

No single pillar is sufficient. A strong data locality posture with weak operational controls is not sovereignty – it is residency with unexamined risk.

What makes the framework useful is not its complexity. It’s the questions it generates. When an organization maps its current posture against all four pillars for the first time, it almost always finds gaps it didn’t know were there – not because the controls are absent, but because the questions were never asked.

Sovereignty Is a Sliding Scale

One more thing worth naming: Sovereignty is not a binary state. There is no certification that grants it and no single deployment model that guarantees it. It is a posture – a set of deliberate, auditable decisions. And the right level of that posture varies by organization, by workload, and by what you actually owe regulators and customers.

That calibration is what minimum viable sovereignty is about – the subject of the second post in this series.

Regulatory confidence is built long before the audit itself – through clearly defined requirements, not assumptions tied to geography.

Download the Relatório de Readiness para a Soberania Digital for the four-pillar framework and a practical self-assessment tool.

Perguntas frequentes

Q: What is the difference between data residency and digital sovereignty?

A: Data residency focuses on where data is physically stored. Digital sovereignty goes further by addressing who can access the data, how systems are operated, and exposure to which jurisdictions may create legal risk.

Q: Why is region selection not enough for sovereignty?

A: Choosing a cloud region only addresses geography. It does not resolve issues related to operational access, legal risks exposure, or recovery capabilities.

Q: What are the four pillars of digital sovereignty?

A: The four pillars are data locality, technological sovereignty, operational sovereignty, and jurisdictional sovereignty. Together, they create, what we believe, is a more complete framework for assessing sovereign readiness.

Q: Why is operational sovereignty difficult to manage?

A: Operational sovereignty involves monitoring who can access systems, where they operate from, and under which legal regime. These controls are harder to audit than simple data location requirements.

Q: Is digital sovereignty a fixed certification?

A: No. Sovereignty is an ongoing posture based on deliberate, auditable decisions that vary by organization, workload, and regulatory environment.

Ruben Renders is Solutions Director, MSP, at Commvault.

Pontos principais

• Os ataques de vishing aumentaram drasticamente, com grupos organizados industrializando a engenharia social para obter acesso inicial por meio de centrais de atendimento.
• Os invasores passam rapidamente de contas humanas comprometidas para identidades de máquina persistentes, como tokens OAuth e contas de serviço.
• A maioria das organizações carece de governança e visibilidade sobre identidades não humanas (NHI), criando um grande ponto cego de segurança.
• Readiness eficaz depende da correlação de sinais de identidade e do tratamento das identidades de máquinas como ativos de alto risco.
• A verdadeira resiliência requer a capacidade de detectar e reverter alterações não autorizadas de privilégios antes que os invasores estabeleçam persistência.

Your help desk staff just got a phone call. The caller knew the employee’s name, their manager, and the last four digits of their badge number. They asked for a password reset. Standard procedure. The IT rep complied.

That call was a fraud. And the attacker is now inside.

Voice phishing – vishing – jumped 449% em 2025. Grupos de adversários transformaram a engenharia social em uma operação escalável: recrutando operadores, escrevendo roteiros epagando de US$ 500 a US$ 1.000 per successful help desk impersonation. They’re not looking for your data. They’re looking for a foothold.

Once inside, attackers don’t linger on the human account. They move laterally – stealing OAuth tokens, creating new administrative service accounts, embedding access in machine-layer credentials that nobody watches. Unlike human passwords, those credentials are rarely rotated. They don’t trigger login alerts. They can survive a full remediation of the original compromised user.

By the time your security team closes the ticket on the help desk incident, the attacker may have been quietly persistent in your environment for weeks. The governance gap makes it worse.

Menos de 25% of organizations have formal policies for creating or decommissioning NHIs – the service accounts, API keys, and OAuth tokens that now outnumber human users by 144 para 1. Nearly all of them carry permissions far beyond what their function requires.

Most organizations have almost no confidence in their ability to detect an attack targeting this layer. That’s not a prevention failure. It’s a recovery planning failure.

Como se apresenta a Readiness

Prevention at the help desk matters – training, callback verification, out-of-band confirmation. But it isn’t enough on its own. Attackers are industrializing faster than awareness programs can keep pace.

Readiness means correlating the signals: A help desk interaction followed immediately by a multi-factor authentication (MFA) reset or a new token creation is a high-probability indicator of compromise.

It means treating machine identities as Tier 0 assets – governing their creation, scoping their permissions, and monitoring for unauthorized escalation. And it means having the ability to detect and roll back malicious privilege changes quickly, before they become the new normal.

Explore how a resiliência de identidade da Commvaultoferece suporte à detecção rápida, reversão e Recovery do seu ambiente de identidade.

Perguntas frequentes

P: O que é um ataque de vishing no contexto da segurança corporativa?

A: Vishing (voice phishing) uses phone calls to impersonate employees and manipulate IT help desks into granting access – typically through password or MFA resets. It’s increasingly industrialized, with organized groups recruiting callers and using pre-written scripts to maximize success rates.

P: Por que os invasores passam a atacar identidades de máquinas após um ataque de vishing?

A: Human accounts get remediated. NHIs – OAuth tokens, service accounts, API keys – are more persistent and rarely rotated, often invisible to traditional monitoring. Migrating access to the machine layer allows attackers to maintain that persistence long after the original human credential breach is detected and closed.

Q: What does “identity resilience” mean in practice?

A: It means your organization can help detect unauthorized privilege changes in near real time and help restore the identity environment to a trusted state quickly. Detection alone isn’t sufficient – the ability to roll back malicious activity and verify that machine identities haven’t been tampered with (or if tampered with, to be rolled back to a prior good point in time) is what separates readiness from exposure.

Vidya Shankaran é diretor de tecnologia (CTO) da Commvault.

Pontos principais

• A engenharia social no suporte técnico tornou-se atualmente um dos principais pontos de entrada, com os ataques de vishing (phishing por voz) aumentando rapidamente e levando ao comprometimento de credenciais.
• Identidades não humanas, como contas de serviço e tokens, constituem um grande ponto cego de segurança, muitas vezes não gerenciadas e amplamente exploradas para movimentação lateral.
• O Active Directory (AD) é um alvo de grande valor devido ao seu controle centralizado e às possíveis configurações incorretas.
• A prevenção por si só não é suficiente; as organizações precisam de recursos robustos de detecção e recuperação rápida para limitar os danos.
• Immediate operational actions – like auditing accounts and correlating help desk activity with identity changes – can significantly reduce risk.

O AD continua sendo um dos principais alvos dos invasores, pois está no centro da identidade corporativa.Pesquisas recentes mostram queAtualmente, 67% dos incidentes envolvem violações relacionadas à identidade, with attackers going after critical systems like AD within hours of initial access.Once compromised, recovery can take days or weeks – causing significant business disruption.
The question worth asking isn’t whether AD is a target.It’s how attackers get tSaiba mais no SHIFT 2025 – and why the path is so much shorter than security teams might expect.

3 Passos para um Compromisso Total

Grupos mal-intencionados como o ShinyHunters e o Scattered Spider transformaram a engenharia social em uma operação em grande escala.Voice phishing – vishing – jumped 449% in 2025.Os operadores são recrutados, recebem orientações sobre o que dizer epagou até US$ 1.000 depending on success and hit rate.
That means, it’s possible to start an attack with one step: Get a password reset or multi-factor authentication (MFA) change.That’s it.
From that single credential, the attacker moves laterally into cloud and virtualized environments.They harvest OAuth tokens, create new administrative service accounts, and embed access in machine-layer credentials.These non-human identities – service accounts, API keys, tokens – now outnumber human users 144 to 1.A expansão descontrolada e os custos operacionais tornam a rotação e a auditoria difíceis. Esse movimento lateral tem um destino: o Active Directory.

A publicidade é o alvo

AD is the central nervous system of enterprise identity.Control it and you control everything – user accounts, group policies, and access to every domain-joined system in the network.The reason it’s so attractive to attackers – and so difficult to defend – is structural.Any authenticated user can read the entire directory.Every domain-joined system inherits trust from it.
Group Policy Objects linked at the domain head can be weaponized to disable security controls outright.Legacy protocols left enabled for application compatibility provide straightforward access.Microsoft’s own documentation says that “most identity attacks utilize common misconfigurations in Active Directory.”

When an attacker reaches the AD, they don’t need to force entry.The door is usually open.

A prevenção é necessária, mas não suficiente

The standard security stack – MFA, endpoint detection, email filtering – is built around human behavior.It wasn’t designed to govern the machine identity layer or to detect the kind of slow, legitimate-looking privilege escalation that characterizes modern AD attacks.An attacker that moves from a compromised human account to a service account to a domain administrator over 72 hours may never trigger a single alert.
This is why the conversation must shift from prevention-first to recovery-first.
Prevention still matters.Least-privilege access, auditing AD changes, hardening default configurations, disabling inactive accounts – these can help reduce the attack surface.But given that half of organizations have already experienced an AD attack, designing only for prevention means designing to fail.
True identity resilience requires the ability to detect unauthorized privilege escalations in near real time, roll back malicious changes before they propagate, and restore the identity environment to a known-trusted state quickly – not in days or weeks, but fast enough to contain the blast radius.That means treating AD and the non-human identity layer as Tier 0 assets, with the same governance and recovery investment you’d apply to any other mission-critical system.

O que fazer agora mesmo para garantir a resiliência da identidade

The gap between wSaiba mais no SHIFT 2025 most organizations are and wSaiba mais no SHIFT 2025 they need to be on identity resilience is real.But it’s closeable.The immediate priorities are unglamorous and operational:

1. Audit what’s in your AD.
2. Find the accounts that shouldn’t still exist.
3. Rotate the credentials that haven’t been touched in years.
4. Correlacione a atividade do help desk com os eventos de criação de tokens e contas.

A help desk interaction followed by an MFA reset followed by a new service account is a high-confidence attack signal – and it’s detectable if you’re looking for it.
The longer-term work is architectural: Build recovery capability into your identity program so that when an attack succeeds – and it’s usually when, not if – you can contain it, reverse it, and try to restore trust faster than the attacker can consolidate their position.
Attackers are counting on your AD being ungoverned, your machine identities being invisible, and your recovery plan being theoretical.Close one of those gaps this quarter.Close all three and you’ve fundamentally changed the math. 

Saiba como o Commvault Cloud oferece proteção abrangente para o AD – from vulnerability assessment to one-click rollback and full forest recovery.
I recently joined Vidya Shankaran on the STRIVE podcast to talk about the governance gap for non-human identities.Check out our episode Saiba mais no SHIFT 2025.And be sure to read Vidya’s blog, O ponto cego da identidade das máquinas é agora uma superfície de ataque primária.

Perguntas frequentes

Q: Why are help desks becoming a major security risk?

A: Help desks are often trusted to reset passwords and modify MFA settings, making them attractive targets for social engineering.Attackers exploit this trust to gain initial access with minimal resistance.
Q: What role do non-human identities play in attacks?

A: Sprawl and operational overhead make rotation and audit of non-human identities, such as service accounts and API keys, difficult.Attackers use them to maintain persistence and move undetected across systems.
Q: Why is AD such a critical target?

A: AD controls authentication and access across the network.Gaining control of it allows attackers to manage users, policies, and systems at scale.
Q: Isn’t MFA and endpoint security enough to stop these attacks?

A: These tools focus on human behavior and may not detect slow, legitimate-looking privilege escalation.Attackers can operate within normal patterns and avoid triggering alerts.
Q: What does a recovery-first security approach mean?

A: It means preparing for the reality that breaches will happen and prioritizing the ability to detect, contain, and reverse them quickly.This approach helps reduce downtime and can help limit overall impact.
Q: What are the most important steps to take immediately?

A: Start by auditing your AD, removing unnecessary accounts, rotating old credentials, and monitoring for suspicious sequences of help desk and identity-related activities.
Dan Conrad é Tecnólogo-chefe e Diretor de Tecnologia de Campo na Commvault.

Pontos principais

• A migração de máquinas virtuais para o Red Hat OpenShift Virtualization é um processo gradual que exige proteção consistente em ambientes híbridos.
• Uma platform unificada de proteção de dados nativa do Kubernetes platform reduzir a complexidade e platform eliminar a necessidade de ferramentas ou processos separados.
• Reliable resilience – including immutable backups and threat detection – is critical during migration, when risks are highest.
• As opções flexíveis de recuperação permitem que as organizações se adaptem rapidamente caso as etapas da migração falhem ou os prazos sejam alterados.
• A consolidação da proteção para máquinas virtuais e contêineres ajuda a reduzir a proliferação de ferramentas e a manter uma governança consistente.

If you’re an IT leader today, chances are your virtualization strategy is under active review.

Rising costs, licensing uncertainty, and long-term vendor lock-in have many organizations reassessing their reliance on traditional hypervisors. At the same time, Kubernetes has matured into the operational foundation for modern applications.

These two realities are converging – and for many enterprises, Red Hat OpenShift Virtualization is emerging as a preferred destination for running virtual machines within a Kubernetes-native operating model.

This transition is accelerating across industries. As organizations modernize infrastructure on their own terms, Red Hat OpenShift Virtualization is increasingly viewed as a way to modernize the platform without the need for application refactoring. With that momentum comes a critical question:

How do you migrate virtual machines while maintaining consistent protection, resilience, and recoverability throughout the process?

To answer it, you need to examine how most enterprise migrations actually unfold – and where protection and resilience become critical.

A migração é uma jornada, não um evento pontual

Seasoned IT leaders know that infrastructure transitions rarely happen all at once.

For enterprises opting to move from hypervisors like VMware to Red Hat OpenShift Virtualization, the transition typically unfolds in phases. During this time, organizations inevitably operate in a mixed state:

• As máquinas virtuais baseadas em VMware continuam a dar suporte às principais operações comerciais.
• Máquinas virtuais que passaram a ser executadas recentemente no Red Hat OpenShift Virtualization.
• Aplicativos em contêineres que compartilham os mesmos clusters do Red Hat OpenShift.

This coexistence period introduces complexity and risk. Data is in motion, environments are changing, and protection gaps can appear if tooling and processes don’t evolve alongside workloads.

É essencial manter uma proteção confiável

A Commvault oferece, há muito tempo, proteção e recuperação de dados tanto para ambientes VMware quanto para cargas de trabalho do Kubernetes em execução no Red Hat OpenShift. Esse mesmo modelo de proteção nativo do Kubernetes e orientado por políticas agora se estende às máquinas virtuais em execução no Red Hat OpenShift Virtualization. O que realmente chama a atenção dos clientes é a consistência:

• Uma única platform proteção e recuperação.
• Operações baseadas em políticas aplicadas de maneira uniforme em todas as cargas de trabalho.
• Projetado para funcionar com suas ferramentas e processos atuais, à medida que os ambientes evoluem.

As máquinas virtuais em execução no Red Hat OpenShift Virtualization são protegidas por meio dos mesmos fluxos de trabalho e estruturas de governança utilizadas para aplicativos em contêineres. Essa abordagem unificada está sendo adotada por organizações que estão padronizando suas infraestruturas com o Red Hat OpenShift e que buscam uma maneira mais simples e consistente de gerenciar dados em todos os ambientes. Esse recurso já está disponível.A Commvault Cloudoferece suporte à proteção de ambientes de virtualização do Red Hat OpenShift alinhados com a versão de suporte de longo prazo 11.40 e a versão de inovação 11.42, o que significa que os clientes já podem colocar esses recursos em produção.

You Shouldn’t Need to Manage Protection Differently

Once VMs move to Red Hat OpenShift Virtualization, they shouldn’t require special handling from a protection standpoint.

A Commvault Cloud discovers and protects Red Hat OpenShift Virtualization VMs alongside containerized applications, helping give teams centralized visibility, consistent policy enforcement, and simplified recovery operations. Virtualized and containerized workloads are managed together – without introducing operational silos.

For organizations managing diverse application portfolios, this treatment of VMs inside Kubernetes helps reduce operational friction while maintaining enterprise-grade controls.

A resiliência cibernética é fundamental quando a migração aumenta o risco.

Migration periods represent a uniquely vulnerable window. Change creates complexity, and complexity increases exposure to data loss and ransomware.

A Commvault Cloud helps maintain resilience throughout this phase with:

• Backups isolados e imutáveis para cargas de trabalho do Red Hat OpenShift Virtualization.
• Dados de backup que apoiam a detecção de ameaças e a análise forense, ajudando as equipes a validar a prontidão para a recuperação antes de restaurar as cargas de trabalho.
• Advanced recovery capabilities designed to help organizations minimize operational disruption.

Independentemente de as cargas de trabalho estarem na fase pré-migração, em transição ou já em pleno funcionamento no Red Hat OpenShift Virtualization, o nível de resiliência permanece inalterado.

A flexibilidade na recuperação traz confiança

Every modernization initiative needs room for adjustment.

Commvault supports both in-place and out-of-place recovery for Red Hat OpenShift Virtualization virtual machines, including full VM context and configuration. If a migration step doesn’t go as planned – or timelines need to shift – teams may recover quickly and move forward without compromising availability or data integrity.

Proteção nativa do Kubernetes além das VMs

For many enterprises, virtualization is only one piece of a broader application modernization strategy.

A Commvault Cloud also provides application-centric, Kubernetes-native protection for containerized workloads, including persistent volumes and application metadata, across all CNCF-certified Kubernetes distributions. This enables mobility and recovery for cloud-native applications while helping maintain operational consistency across environments.

Reduzindo a proliferação de ferramentas à medida que a infraestrutura evolui

Platform transitions often introduce new tools, new processes – and new complexity.

By using A Commvault Cloud as a unified protection platform for:

• Máquinas virtuais VMware.
• Máquinas virtuais do Red Hat OpenShift Virtualization.
• Aplicativos em contêineres.

As organizações podem ajudar a reduzir a proliferação de ferramentas, simplificar a administração e manter uma governança consistente, mesmo à medida que as estratégias de infraestrutura evoluem.

Como tudo se encaixa

During any migration, it helps to understand how the pieces work together. Red Hat’s Migration Toolkit for Virtualization takes care of moving VMs from VMware into Red Hat OpenShift Virtualization.

A Commvault Cloud helps provide the protection and resilience that stays with your workloads throughout the process, so data can remain protected before, during, and after migration. This can help keep recoverability from falling behind as workloads move.

Continuing the Conversation at Red Hat Summit

We’re already working with customers that are actively moving virtual machines onto OpenShift Virtualization – and we’re continuing these discussions at Red Hat Summit, May 11–14 in Atlanta.

At the Commvault booth, we’ll be:

• Conversando com líderes de TI sobre os desafios reais da resiliência.
• Compartilhando orientações práticas para realizar a migração com confiança.
• Demonstrating A Commvault Cloud protection for Red Hat OpenShift Virtualization.

If maintaining resilience and recoverability throughout your virtualization strategy is a priority, we’d welcome the opportunity to connect.

Seguindo em frente com confiança

Red Hat OpenShift Virtualization is becoming a foundational component of modern enterprise infrastructure. But you can’t rush migration at any cost; you must build protection, resilience, and recovery into the process from the beginning.

With A Commvault Cloud, protecting Red Hat OpenShift Virtualization workloads isn’t a future aspiration. It’s something customers already are doing – using a unified platform to modernize confidently while staying resilient and recoverable.

“Red Hat OpenShift Virtualization delivers a reliable, consistent foundation for organizations to support their entire virtualized estate,” says Steve Gordon, Senior Director, Product Management, Hybrid Cloud Platforms, at Red Hat. “By leveraging an optimized integration like A Commvault Cloud with Red Hat OpenShift Virtualization, our customers can move forward with greater confidence, knowing their workloads are protected consistently before, during, and after migration.”

Perguntas frequentes

P: Por que a migração de máquinas virtuais é considerada um processo em várias fases?

R: A maioria das empresas não consegue migrar todas as cargas de trabalho de uma só vez; por isso, operam em um ambiente híbrido, com ambientes legados e novos em execução simultânea. Essa abordagem em fases traz complexidade, tornando essenciais a proteção e a visibilidade consistentes ao longo de toda a transição.

P: Qual é o papel da resiliência durante a migração de máquinas virtuais?

R: A resiliência permite que as organizações mantenham a proteção dos dados, se recuperem rapidamente de falhas e se defendam contra ameaças como o ransomware. Durante a migração, quando os sistemas estão em transição, medidas robustas de resiliência podem ajudar a evitar a perda de dados e interrupções operacionais.

Q: How does A Commvault Cloud simplify protection across environments?

A: A Commvault Cloud provides a single platform with policy-driven protection for VMware VMs, OpenShift Virtualization VMs, and containerized applications. This unified approach enables consistent operations without introducing new tools or workflows.

P: Por que a proteção nativa do Kubernetes é importante?

R: A proteção nativa do Kubernetes se alinha à forma como as aplicações modernas são implantadas e gerenciadas, abrangendo tanto contêineres quanto máquinas virtuais. Ela permite o gerenciamento simples de dados, a mobilidade e a recuperação em ambientes cloud.

P: De que forma a flexibilidade na recuperação aumenta a confiança na migração?

R: Opções flexíveis de recuperação, como restaurações no local e fora do local, podem ajudar as equipes a recuperar rapidamente as cargas de trabalho caso ocorra algum problema. Essa adaptabilidade ajuda a reduzir o tempo de inatividade e permite que as organizações ajustem seus planos de migração sem comprometer a integridade dos dados.

P: Como as organizações podem reduzir a complexidade durante as transições de infraestrutura?

A: By adopting a unified data protection platform, organizations can manage all workloads – virtualized and containerized – through a single interface. This approach helps reduce tool sprawl, simplify administration, and maintain consistent governance across evolving environments.

Jason Gizaé gerente sênior de Marketing de Parcerias de Conteúdo Global na Commvault.

Pontos principais

• A Academia Readiverse lançou um caminho de certificação estruturado e em níveis, que vai desde conhecimentos básicos até especialização avançada cloud .
• As certificações estão alinhadas às funções profissionais reais, ajudando os alunos a desenvolver habilidades relevantes para suas responsabilidades em Cloud Commvault Cloud .
• The program includes four tiers – Practitioner, Specialist, Professional, and Expert – each increasing in depth and operational capability.
• A aprendizagem se baseia em três pilares fundamentais: platform , resiliência cibernética e conhecimento especializado em cargas de trabalho.
• Opções flexíveis de aprendizagem, incluindo formatos individualizados e ministrados por instrutor, permitem que os profissionais avancem de acordo com seus horários e objetivos.

The environments you protect with Commvault® Cloud are increasingly complex, and the expectations on your teams that run them are higher than ever. It’s no longer just about knowing the platform. It’s about being able to operate, protect, and recover, often under pressure.

If you’ve already started your learning journey in the Academia Readiverse, welcome back. And if you’re new here, you’re joining at the right time.

Today, we’re introducing a structured, tiered certification approach that gives learners a clear, skill‑based path from foundational platform knowledge to advanced cloud engineering expertise.

Criamos conteúdo para você

Commvault Cloud environments demand expertise across multiple responsibilities, often within the same role. Administrators, security specialists, cloud engineers, and workload owners require different depths and breadths of knowledge. And not everyone needs to learn the same things, in the same order, to be effective.

The new Academia Readiverse certification tiers reflect that reality. Learners progress through clearly defined levels that build on one another so that your certification aligns to what you actually do and validates those capabilities to the teams you work with.

• Commvault Cloud Practitioner – foundational platform and resilience knowledge.
• Commvault Cloud Specialist – expanded operational and security depth.
• Commvault Cloud Professional – advanced recovery and workload expertise.
• Commvault Cloud Expert – full cloud engineering and resilience leadership.

Each tier is earned through a combination of coursework, hands‑on lab activities, and validated assessments. As learners progress, the scope and depth of operational capability demonstrated increases accordingly.

Um caminho claro: de iniciante a especialista

O programa de certificação está estruturado em torno de três pilares de competências essenciais que permeiam todos os níveis:

• platform básicas platform
• Conceitos de resiliência cibernética
• Carga de trabalho e especialização em funcionalidades

Cada nível acrescenta requisitos específicos relacionados a esses pilares. Os alunos podem concluir cursos individuais ou combinar requisitos específicos para atingir as metas de certificação.

Already in Academia Readiverse? What this Means for You.

With a new structure like this, the most important question is what it means for the progress you’ve already made. If you’ve already completed courses or earned certifications in the Academia Readiverse, congratulations! Your investment matters, and we want to be clear about what happens next.

Those certifications represent your history and accomplishments with Commvault. The new program is aligned to our expanded portfolio of cyber resilience features for Commvault Software, Commvault SaaS, and hybrid environments. As your needs grow to require more from Commvault, these courses and certifications will help you configure, manage, and optimize Commvault to meet your organization’s unique needs.

There is no direct progression from the previous certification tracks to the new program, but your existing certifications validate your expertise on the former product releases. As those releases are retired, those certifications will reach end of life as well. Learners who are already invested in the Academia Readiverse are well positioned to progress quickly.

Who Should Take Academia Readiverse Courses and Certifications

Academia Readiverse certifications are designed for professionals working across Commvault SaaS, Commvault Software, and hybrid environments.

• Platform administrators managing day‑to‑day operations.
• Especialistas em segurança dedicados à proteção de dados e ao fortalecimento de ambientes.
• Cloud responsáveis pela configuração do plano de controle e pela resiliência avançada.
• Responsáveis por cargas de trabalho que precisam de proficiência em domínios específicos de dados.

All training is available for self‑paced learning, with select courses also offered in instructor‑led formats, so learners can progress in a way that fits their role and schedule.

Como começar ou dar continuidade à sua jornada de aprendizado

Whether you’re starting fresh or continuing your journey, the next step is simple and designed to meet you where you are.

• Faça login ou cadastre-se no sitecommvault.com.
• É novo na Commvault? Comece com o curso “Commvault Cloud ”.
• Responsável pelo apoio à gestão da carga de trabalho? Confira nosso catálogo de cursos, que abrange praticamente tudo.
• Procurando estratégias para apoiar a recuperação após um ataque cibernético? O curso sobre Resiliência Cibernética é o seu primeiro passo.

O que vem a seguir

Our goal is to make advancement predictable, transparent, and aligned to real‑world roles to help learners know what’s next and how to prepare for it.

We are committed to giving every Commvault Cloud user the knowledge to operate, protect, and recover their environment with confidence. Because when it matters most, certification isn’t about credentials. It’s about being resilient and ready to recover.

Perguntas frequentes

Q: What is the purpose of the Academia Readiverse certification program?

R: O programa oferece um percurso de aprendizagem estruturado e baseado em competências que ajuda os profissionais a evoluir do platform básico platform até a especialização avançada cloud . Ele alinha o treinamento às responsabilidades do mundo real para permitir que os alunos apliquem seus conhecimentos de forma eficaz em ambientes complexos.

P: Quais são os diferentes níveis de certificação disponíveis?

R: Existem quatro níveis: Commvault Cloud , Specialist, Professional e Expert. Cada nível se baseia no anterior, aumentando em profundidade técnica, escopo operacional e capacidade de liderança.

Q: Who should enroll in Academia Readiverse courses?

R: Os cursos foram desenvolvidos para platform , especialistas em segurança, cloud e responsáveis por cargas de trabalho que atuam em ambientes SaaS, de software e híbridos. Cada função pode seguir um plano de aprendizagem personalizado, de acordo com suas responsabilidades.

P: Como se obtêm as certificações?

R: As certificações são obtidas por meio de uma combinação de cursos, laboratórios práticos e avaliações validadas. À medida que os alunos avançam, eles demonstram níveis crescentes de especialização nas áreas de platform, segurança e cargas de trabalho.

Q: What happens to existing Academia Readiverse certifications?

R: As certificações existentes continuam válidas como comprovação de experiência anterior, mas estão vinculadas a versões anteriores do produto. À medida que essas versões forem descontinuadas, as certificações chegarão ao fim de sua validade, incentivando os alunos a fazer a transição para o novo programa.

P: Como alguém pode começar a usar o novo programa?

R: Os novos alunos podem começar pelo curso Cloud Commvault Cloud , enquanto os usuários já cadastrados podem fazer login para dar continuidade ao seu progresso. Há cursos adicionais disponíveis de acordo com objetivos específicos, como gerenciamento de cargas de trabalho ou estratégias de resiliência cibernética.

Suzanne Klausner é diretor de Estratégia de Capacitação do Cliente na Commvault.

Pontos principais

• A maioria dos exercícios simulados serve para avaliar o desempenho, em vez de revelar lacunas reais na resposta a incidentes.
• Para que os exercícios sejam eficazes, eles devem introduzir atrito, ambiguidade e pressão, a fim de refletir situações reais.
• Limitar o escopo do exercício a alguns cenários críticos e definir o sucesso como a identificação de problemas, em vez de apenas causar boa impressão, pode levar a insights mais significativos e práticos.
• A participação de diversas áreas, e não apenas das equipes técnicas, é essencial para avaliar com precisão a resposta da organização.
• A verdadeira resiliência é comprovada por meio de testes reais de recuperação, e não apenas por cenários baseados em discussões.

There is a moment most security leaders recognize, even if they do not say it out loud. The tabletop just wrapped. The team is filing out. Everyone looks reasonably satisfied. And somewhere in the back of your mind, a quiet question surfaces: Did we actually learn anything?

If you are honest, the answer is often no.
That is not because tabletop exercises are a bad idea. They are one of the most valuable tools a security leader has. The problem is how most organizations run them – and what they are actually measuring when they do.

A Armadilha do Desempenho

The most common mistake in tabletop exercises has nothing to do with the scenario. It has to do with the goal. Most teams, consciously or not, build exercises designed to demonstrate competence rather than discover gaps.
The scenario generally follows a clean arc. Information arrives in a logical sequence. The right people say the right things. Everyone feels prepared. And that feeling – confident, well-rehearsed, almost collegial – is exactly the problem.
Real incidents do not run on clean arcs. They arrive with incomplete information, conflicting signals, unavailable people, and a business demanding answers faster than the facts support. If your tabletop does not create that kind of friction, you have not tested incident response. You have practiced a conversation.
When the exercise is designed to validate rather than stress-test, a second problem follows: People stop being honest. Nobody says, “I don’t know who owns that decision” or “we have never actually tested that recovery path.” They say what sounds right. And the gaps that should surface in a controlled environment stay hidden until they surface in a real one.

O que um bom exercício realmente avalia

Before you build a scenario, you need to answer a simpler question: What do you actually want to learn? Not 20 things. Three or four.
Can your team make a shutdown decision fast enough, and does everyone know who has the authority to make it? When security, IT, legal, and communications are all in the room with conflicting priorities, can they actually reach decisions together? Can you explain the business impact of an incident clearly enough for leadership to act – not just understand? And if you had to restore a critical system in the next four hours, could you really do it?

Once you know what you are testing, build a scenario with real friction. Make a key person unavailable mid-exercise. Introduce a customer escalation. Have a regulator ask a question the team cannot answer from the runbook.
Give people incomplete information and see how they make decisions anyway. The value is not in watching people succeed under pressure. It is in finding the places where the process breaks down while the stakes are still low enough to fix it.

Diga isso em voz alta logo no início: hoje em dia, sucesso significa identificar problemas, e não causar boa impressão. Essa única frase muda o que as pessoas estão dispostas a dizer na sala.

O Problema das Pessoas

Uma simulação que envolva apenas segurança e TI é uma discussão técnica, não um exercício de resposta a incidentes. Se o departamento jurídico não estiver presente, se o departamento de comunicação não estiver presente, se os responsáveis pelas áreas de negócios e a alta liderança estiverem ausentes, você não estará testando como sua organização realmente responde a uma crise. Você estará testando como um grupo de pessoas inteligentes discute uma situação hipotética. Incidentes reais são tratados em toda a empresa. O exercício deve refletir isso.

Conversar sobre o assunto não é suficiente

This is where most organizations stop short. A paper exercise is important – but it is not confidence.
Talking through a recovery scenario tells you something. Actually restoring a system tells you something different. Can you bring identity back to a clean point in time? Can you validate that what you are recovering is trustworthy? Can you restore a Tier 1 application and confirm it comes back cleanly, without carrying the infection with it?

Those are not questions you can answer in a conference room. At some point, the plan has to meet the environment – and you need to know whether they match.

Após o término do exercício

The debrief tells you whether the exercise mattered. If the hot wash is quiet, vague, or full of “good reminders,” the exercise did not push hard enough. A well-run tabletop should leave you with a short list of real findings, clear owners, and deadlines. If you cannot answer what broke, who is fixing it, and by when, you ran an event, not an exercise.
The goal was never to pass the exercise. It was to learn something important while the cost of being wrong was still just time.
Watch our recent episode of the STRIVE podcast, where I join my colleague Chris Mierzwa, Senior Director, Portfolio Marketing, for sobre exercícios simulados.

Perguntas frequentes

P: Por que a maioria dos exercícios simulados não consegue agregar valor real?

R: Muitos exercícios são elaborados para que as equipes pareçam preparadas, em vez de revelar pontos fracos. Isso leva a discussões ensaiadas, que não refletem a imprevisibilidade e a pressão de incidentes reais.

P: Qual deve ser o objetivo de um exercício de simulação?

R: Deve se concentrar em responder a um pequeno número de questões essenciais, como velocidade na tomada de decisões, clareza quanto à responsabilidade e capacidade de recuperação. Esse foco ajuda as equipes a identificar lacunas significativas, em vez de apenas observações superficiais.

P: Como as organizações podem tornar os exercícios mais realistas?

R: Introduza incertezas, informações ausentes e interrupções inesperadas durante o cenário. Esses elementos obrigam as equipes a pensar criticamente e agir sob pressão, em condições mais próximas às de um incidente real.

P: Quem deve participar de um exercício simulado?

R: Além das equipes de segurança e TI, equipes como as de assuntos jurídicos e de comunicação, líderes de negócios e executivos devem participar. Isso permite que o exercício reflita a forma como incidentes reais são gerenciados em toda a organização.

P: Por que falar sobre a recuperação não é suficiente?

R: As discussões podem destacar os planos, mas somente testes reais comprovam se os sistemas podem, de fato, ser restaurados de forma limpa e rápida. A validação prática é necessária para confirmar a prontidão para a recuperação.

P: O que define um resultado bem-sucedido em um exercício de simulação?

R: Um exercício bem conduzido resulta em conclusões claras, responsáveis designados e prazos definidos para a correção. Se esses elementos estiverem ausentes, é provável que o exercício não tenha desafiado a equipe o suficiente.

Chris Bevil is Principal, Global Cyber Resilience & AI, at Commvault.

Every organization that has ever failed a recovery – and there are more than anyone publicly acknowledges – had one thing in common: They believed they could recover before they tried.

The belief came from somewhere. A completed tabletop exercise. A backup system that showed green. An annual disaster recovery test that passed. All of it documented. All of it, at some point, accurate. None of it current when the incident actually hit.

This is the confidence gap. And it is the gap that continuous recovery validation is designed to close.

What ‘Testing’ Actually Means in Most Organizations

Pergunte à maioria dos líderes de segurança ou de TI com que frequência eles testam sua capacidade de recuperação, e a resposta geralmente é “uma vez por ano”, às vezes “duas vezes por ano”. O teste envolve restaurar um subconjunto de sistemas a partir de um backup em um ambiente de teste, confirmar se eles entram em operação e elaborar um relatório. Às vezes, um exercício simulado é realizado paralelamente a isso. O que esse tipo de teste não faz: validar se os dados de backup estão livres de malware; confirmar se a sequência de recuperação funciona para serviços interdependentes. Testa a recuperação de identidade, o que é essencial quando credenciais comprometidas foram o que possibilitou o ataque. Confirma se a equipe que realmente executaria a recuperação conhece os manuais de procedimento atuais. Ou produz evidências significativas o suficiente para convencer um órgão regulador, um auditor ou um conselho de que a capacidade de recuperação é real e está atualizada. Em resumo, ela valida um momento específico. As operações de resiliência (ResOps) exigem que a validação seja um estado contínuo.

O Modelo de Validação Contínua

Continuous recovery validation is not a single test run more frequently. It is a set of integrated practices that produce ongoing, evidence-based proof of recoverability across critical services.

Automated backup integrity scanning. Every backup, continuously evaluated for anomalies, encryption patterns, and malware signatures. Not at restore time – before restore time. The goal is to know whether your recovery points are clean before you need them, not during an incident.

Scheduled Cleanroom Recovery drills. Bi-annual at minimum, restoring from immutable backup points into an isolated Cleanroom Recovery environment – not production, not a production-adjacent test environment, but a genuinely isolated space where forensic analysis can happen without risk of reinfection. These drills produce documented evidence of recoverability against defined impact tolerances.

Identity recovery validation. With o uso indevido de credenciais é o vetor de violação mais comum, Active Directory and Entra ID recovery must be tested alongside data recovery. Organizations that restore systems without restoring a verified-clean identity layer may find attackers re-enter through the same door.

Service Resilience Indicator (SRI) dashboards. SRIs – continuous signals drawn from backup telemetry, dependency mapping, and test results – that give CISOs, CIOs, and boards a live view of recoverability posture. Not a point-in-time report. An ongoing operational signal.

Each of these practices feeds what Deloitte and Commvault call the resilience backlog: a continuously updated, prioritized list of gaps identified through testing and tracked to resolution. It is the mechanism by which validation drives improvement rather than just producing reports.

O que significa a variação no tempo médio de recuperação da limpeza

Traditional recovery metrics – recovery time objective (RTO) and recovery point objective (RPO) – measure speed and data recency. They say nothing about whether the data being restored can be trusted. Mean Time to Clean Recovery (MTCR) fills that gap: It measures the time required to restore data that is verifiably clean, not just technically available.

MTCR matters because in a ransomware incident, the adversary’s goal is often to corrupt recovery options, not just encrypt production systems. An organization that restores quickly but restores from a compromised backup has not recovered. It has re-infected itself.

Building MTCR into your resilience measurement framework, alongside RTO and RPO, changes what you optimize for and what you report to the board. Speed plus recency plus integrity: that is the complete picture of recovery readiness.

Resiliência que você pode comprovar

The organizations that navigate cyber disruptions with the least damage share one characteristic: They treat recovery capability as something to be continuously demonstrated, not periodically asserted. They know their MTCR. Their SRIs are current. Their cleanroom recovery has been tested in the last 90 days.

That posture is not the result of better technology alone. It is the result of an operating discipline – ResOps – that makes resilience continuous, measurable, and governable. Commvault’s platform provides the technical foundation: clean recovery, automated validation, and the unified visibility across data, identity, and services that ResOps requires at scale.

For the organizational side of that equation – how to define impact tolerances, align executive leadership, and build the governance structure that sustains the discipline – see the Deloitte companion blog, A conversa sobre resiliência que seu conselho ainda não está tendo. E para conhecer a estrutura completa do ResOps, incluindo os seis domínios do ResOps e o modelo de medição que vincula a recuperabilidade técnica à responsabilidade do conselho administrativo, leia o white paper conjunto:Da Viabilidade Mínima à Resiliência Operacional: ResOps na prática.Bill O’Connell é diretor de segurança da Commvault.

Pontos principais:

• Os ataques cibernéticos têm como alvo, cada vez mais, tanto os ambientes de produção quanto os de backup, tornando essencial uma recuperação limpa e verificável.
• A detecção integrada de anomalias e ameaças reforça a resiliência cibernética ao identificar dados comprometidos, validar pontos de recuperação confiáveis e acelerar a restauração.
• Quando integradas aos fluxos de trabalho de proteção de dados, as funcionalidades de detecção de anomalias e ameaças podem ajudar a fornecer as evidências necessárias para uma recuperação rápida, segura e confiável.

Por que a resiliência cibernética depende da detecção integrada de anomalias e ameaças

Anomaly detection identifies unusual behavior in backup data that may indicate compromise. Threat detection identifies known malicious activity using signatures, heuristic analysis, and scanning techniques. Together, they help validate recovery points and enable clean data recovery.

For years, security leaders focused on preventing breaches. In today’s era of persistent attacks and AI-driven threats, organizations increasingly assume compromise and design systems that can withstand disruption and recover safely when it occurs.

Modern adversaries don’t always hide their presence – they reveal it when it serves their objective. Attackers try to infiltrate environments quietly, observe systems over time, and position themselves inside critical infrastructure. The moment an attack becomes visible is rarely the moment it begins; it is the moment the attacker chooses to act.

By then, compromised data may already be woven into backup copies. Integrated anomaly and threat detection can help organizations identify compromised backup data, validate clean recovery points, and assist recovery after a cyberattack.

For security and IT teams, the challenge is no longer simply detecting an attack but predicting and managing an attacker’s possible impact. Understanding what was affected, what remains trustworthy, and how the organization can recover safely without escalating business disruption is the solution.

This is why cyber resilience benefits tremendously from integrated anomaly and threat detection. When detection capabilities are embedded into data protection and recovery workflows, they help provide the shared intelligence that teams need to identify compromised data, validate trusted recovery points, and guide response decisions with evidence rather than guesswork.

This approach aligns with the emerging ResOps™ operating modelemergente, no qual as equipes de segurança, TI e recuperação trabalham com base em uma visão compartilhada e em caminhos de recuperação validados para responderem em conjunto aos incidentes.

A nova realidade: a recuperação exige provas, não suposições

Traditional threat detection tools focus on spotting threats along the perimeter. But once attackers are inside, visibility can become fragmented and determining which systems and data have been affected becomes a challenge.

Further, attackers increasingly target backup environments specifically to undermine recovery. And the moment organizations cannot confidently prove that backups remain untouched, suspicion becomes unavoidable. The result is uncertainty. Restore quickly and risk reinfection? Or delay recovery while investigating which copies remain trustworthy? IT teams are forced to guess which data is safe while downtime accumulates.

By building intelligence directly into data protection workflows, anomaly and threat detection helps transform recovery from a reactive guess into a disciplined, evidence-driven process. These capabilities can help organizations pinpoint tampered copies, validate data cleanliness, and assemble the most recent uncompromised recovery points – helping you accelerate cyber recovery and reduce operational impact.

Detecção de anomalias: seu sinal precoce do desconhecido

Anomaly detection acts as a sentinel, guarding your protected data integrity. It establishes a baseline of normal behavior – file sizes, growth patterns, deduplication changes, access attempts – and alerts teams when something deviates from that norm. These deviations can surface signs of silent tampering long before malware signatures do. In an era of novel and polymorphic threats, anomaly detection helps offer what static tools can’t: visibility into the unexpected.

Detecção de ameaças: defesa direcionada contra atividades maliciosas conhecidas

While anomalies reveal what’s unusual, threat detection exposes what is malicious. By scanning protected data directly for ransomware, malware signatures, encryption patterns, and custom indicators of compromise (IoCs), threat detection helps validate that the data you protect is not already compromised.

Por que uma abordagem combinada é importante

Nem a detecção de anomalias nem a detecção de ameaças, por si só, oferecem uma visão completa. Juntas, elas proporcionam uma estratégia de defesa em profundidade: a detecção de anomalias pode identificar sinais suspeitos, enquanto a detecção de ameaças pode investigar mais a fundo para verificar se há intenção maliciosa. Essa combinação ajuda as organizações a distinguir anomalias inofensivas de verdadeiros ataques e a manter dados confiáveis e validados para uma recuperação rápida.

Meeting Today’s Challenges with Commvault® Cloud

Os invasores têm como alvo cada vez mais os ambientes de backup, e o malware oculto nos dados de backup pode aumentar o risco de reinfecção durante a recuperação. As organizações precisam de uma validação baseada em dados para garantir uma recuperação segura e confiável.A Commvault Cloud addresses this by combining data protection workflows with anomaly detection, threat intelligence, AI-enabled analytics, and isolated clean instances. With anomaly and threat insights applied before, during, and after backup operations, Commvault can help empower organizations to recover faster, cleaner, and confidently.

Read the full white paper, “Can You Prove You’re Recoverable Right Now?”para obter mais informações.

Perguntas frequentes

Q: What is anomaly detection in data protection?

A: Anomaly detection identifies unusual behaviors – such as unexpected backup size changes or abnormal file activity – that may signal tampering, ransomware, or emerging threats within protected data.

Q: Why do CISOs need threat detection in their backup workflows?

A: Backup environments are now prime attacker targets. Threat detection helps prevent organizations from storing or restoring compromised data, which helps reduce reinfection risk and improve chances for clean recovery.

Q: How does Commvault help enable clean data recovery?

A: Commvault uses AI-assisted threat scanning, encryption detection, custom IoC matching, and cyber deception to help validate backup integrity and assemble the most recent uncompromised data for rapid recovery.

Q: Why combine anomaly and threat detection?

A: Anomalies identify the unknown; threat detection validates the known. Together, they provide comprehensive visibility into suspicious activity, helping enable faster investigation and more confident data recovery.

Lista de Paulineé gerente de marketing de produto na Commvault