Punti di forza

• La sovranità minima necessaria (MVS) si concentra sull’applicazione del giusto livello di controllo ai carichi di lavoro appropriati.
• Trattare tutti i carichi di lavoro allo stesso modo può comportare complessità e costi superflui o una protezione insufficiente.
• Le organizzazioni rientrano in genere in tre profili di sovranità: sovranità totale, impresa regolamentata e multi-cloud ibrido.
• Una governance coerente in ambienti misti rappresenta una delle maggiori sfide operative.

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 Rapporto sulla Readiness per la sovranità digitale  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.

Non tutti i carichi di lavoro sono uguali

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

Le imprese soggette a regolamentazione rientrano in tre profili ben definiti, ciascuno con motivazioni principali e priorità di investimento diverse.

• 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.

Il costo di una calibrazione errata

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 quarto articolo di questa serie.)

Un punto di partenza pratico

Un approccio MVS prevede tre passaggi:

1. Classify workloads by their actual sovereignty requirements across each pillar – don’t start with deployment models.
2. Mappare ciascuna classe di carico di lavoro al livello di implementazione che soddisfa tali requisiti, nell’intero spettro che va dalle regioni degli hyperscaler pubblici al cloud pubblico sovrano fino agli ambienti gestiti on-premise.
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 – argomento del terzo articolo di questa serie, il pilastro che la maggior parte delle strategie considera come un aspetto secondario.

Utilizzate l’autovalutazione contenuta nelRapporto sulla Readiness per la sovranità digitaleper individuare la vostra posizione attuale rispetto a tutti e quattro i pilastri.

Domande frequenti

D: Che cos’è la “sovranità minima funzionante” (MVS)?

A: L’MVS consiste nell’applicare controlli di sovranità in base alle effettive esigenze aziendali e normative. Ha lo scopo di evitare sia un eccesso di complessità che una protezione insufficiente.

D: Perché è importante la classificazione del carico di lavoro?

A: Carichi di lavoro diversi comportano obblighi normativi e operativi diversi. La classificazione dei carichi di lavoro aiuta le organizzazioni ad applicare il livello appropriato di controlli di sovranità.

D: Quali sono i tre profili di sovranità più comuni?

A: I tre profili sono: organizzazioni sovrane vere e proprie, organizzazioni regolamentate e organizzazioni ibride multi-cloud. Ciascuna di esse presenta requisiti operativi e di conformità distinti.

D: Quali rischi comporta un approccio eccessivamente ingegneristico alla sovranità?

A: Controlli eccessivi possono aumentare la complessità operativa e i costi senza garantire una conformità significativa né apportare valore aggiunto all’azienda.

D: Perché gli ambienti misti comportano sfide in termini di governance?

A: Le organizzazioni operano spesso su più modelli di cloud e infrastrutture. È difficile garantire la coerenza dei controlli, delle prove di audit e degli standard di Recovery in tutti gli ambienti.

Ruben Renders è direttore delle soluzioni MSP presso Commvault.

Punti di forza

• La residenza dei dati indica il luogo in cui questi sono archiviati, ma la sovranità digitale richiede anche il controllo sull’accesso, sulle operazioni e una corretta comprensione delle implicazioni giurisdizionali.
• La sovranità operativa è spesso l’aspetto più debole e meno sottoposto a verifica della maggior parte dei programmi di sovranità.
• Una posizione di sovranità completa si basa su quattro pilastri: la località dei dati, la sovranità tecnologica, la sovranità operativa e la sovranità giurisdizionale.
• La sovranità non è una questione binaria; le organizzazioni devono definire una strategia in linea con i propri obblighi normativi e operativi.

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.

Il quadro di riferimento che colma il divario

A complete sovereignty posture spans four interdependent pillars. The Rapporto sulla Readiness per la sovranità digitale – 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.

La sovranità è una scala mobile

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 secondo articolo di questa serie.

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

Download the Rapporto sulla Readiness per la sovranità digitale for the four-pillar framework and a practical self-assessment tool.

Domande frequenti

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.

Punti di forza

• Gli attacchi di vishing hanno registrato un’impennata, con gruppi organizzati che hanno trasformato l’ingegneria sociale in una pratica sistematica per ottenere l’accesso iniziale tramite i servizi di assistenza.
• Gli aggressori passano rapidamente dagli account utente compromessi a identità machine persistenti, come i token OAuth e gli account di servizio.
• La maggior parte delle organizzazioni non dispone di meccanismi di governance e visibilità sulle identità non umane (NHI), creando così un grave punto cieco in termini di sicurezza.
• Un’efficace Readiness dipende dalla correlazione dei segnali di identità e dal considerare le identità delle macchine come risorse ad alto rischio.
• Una vera resilienza richiede la capacità di individuare e annullare le modifiche non autorizzate ai privilegi prima che gli aggressori riescano a stabilire una presenza persistente.

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 del 449% nel 2025. I gruppi di hacker hanno trasformato l’ingegneria sociale in un’operazione scalabile: reclutano operatori telefonici, redigono copioni eda 500 a 1.000 dollari 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.

Meno del 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 a 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.

Come si presenta la 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 Resilienza delle identità di Commvaultconsente il rilevamento rapido, il rollback e il Recovery del vostro ambiente di gestione delle identità.

Domande frequenti

D: Che cos’è un attacco di vishing nel contesto della sicurezza aziendale?

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.

D: Perché gli autori degli attacchi passano alle identità delle macchine dopo essersi introdotti tramite 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 è il Field CTO di Commvault.

Punti di forza

• L’ingegneria sociale nei servizi di assistenza è ormai diventata uno dei principali punti di accesso, con gli attacchi di vishing (phishing vocale) in rapido aumento che portano alla compromissione delle credenziali.
• Le identità non umane, come gli account di servizio e i token, rappresentano un grave punto cieco in termini di sicurezza: spesso non vengono gestite e sono oggetto di gravi abusi finalizzati al movimento laterale.
• Active Directory (AD) rappresenta un obiettivo di grande valore a causa del suo controllo centralizzato e delle potenziali configurazioni errate.
• La prevenzione da sola non basta; le organizzazioni hanno bisogno di solide capacità di rilevamento e di ripristino rapido per limitare i danni.
• Immediate operational actions – like auditing accounts and correlating help desk activity with identity changes – can significantly reduce risk.

AD rimane uno degli obiettivi principali degli hacker poiché è il fulcro della gestione delle identità aziendali.Ricerche recenti dimostrano cheil 67% degli incidenti comporta ormai una compromissione legata alle identità, 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 tqui – and why the path is so much shorter than security teams might expect.

3 passi verso un compromesso completo

Gruppi di malintenzionati come ShinyHunters e Scattered Spider hanno trasformato l’ingegneria sociale in un’operazione su larga scala.Voice phishing – vishing – jumped 449% in 2025.I chiamanti vengono reclutati, istruiti su copioni prestabiliti epagati fino a 1.000 dollari 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.La proliferazione e i costi operativi rendono difficili la rotazione e l’audit. Quel movimento laterale ha una destinazione: Active Directory.

La pubblicità è l’obiettivo

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.

La prevenzione è necessaria ma non sufficiente

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.

Cosa fare subito per rafforzare la resilienza dell’identità

The gap between wqui most organizations are and wqui 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. Correlare l’attività dell’help desk con gli eventi relativi alla creazione di token e account.

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. 

: dalla valutazione delle vulnerabilità al rollback con un solo clic, fino al ripristino completo della foresta.
Recentemente ho partecipato al podcast STRIVE insieme a Vidya Shankaran per parlare del divario di governance relativo alle identità non umane. Ascolta la nostra puntata – 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 qui.And be sure to read Vidya’s blog, Il punto cieco dell’identità delle macchine è ormai diventato una delle principali superfici di attacco.

Domande frequenti

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 è responsabile tecnico e CTO sul campo presso Commvault.

Punti di forza

• La migrazione delle macchine virtuali a Red Hat OpenShift Virtualization è un percorso graduale che richiede una protezione costante in tutti gli ambienti ibridi.
• Una platform unificata e nativa di Kubernetes per la protezione dei dati platform ridurre la complessità ed elimina la necessità di ricorrere a strumenti o processi separati.
• Reliable resilience – including immutable backups and threat detection – is critical during migration, when risks are highest.
• Le opzioni di ripristino flessibili consentono alle organizzazioni di adattarsi rapidamente in caso di fallimento delle fasi di migrazione o di variazioni delle tempistiche.
• Il consolidamento della protezione per le macchine virtuali e i container contribuisce a ridurre la proliferazione degli strumenti e a garantire una governance coerente.

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.

La migrazione è un percorso, non un evento isolato

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:

• Le macchine virtuali basate su VMware continuano a supportare le operazioni aziendali fondamentali.
• Macchine virtuali che girano da poco su Red Hat OpenShift Virtualization.
• Applicazioni in container che condividono gli stessi cluster 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.

È fondamentale garantire una protezione affidabile

Commvault offre da tempo soluzioni di protezione e ripristino dei dati sia per gli ambienti VMware che per i carichi di lavoro Kubernetes in esecuzione su Red Hat OpenShift. Lo stesso modello di protezione nativo per Kubernetes e basato su policy si estende ora alle macchine virtuali in esecuzione su Red Hat OpenShift Virtualization. Ciò che colpisce davvero i clienti è la coerenza:

• Un’unica platform la protezione e il ripristino.
• Operazioni basate su criteri applicate in modo uniforme a tutti i carichi di lavoro.
• Progettato per integrarsi con gli strumenti e i processi già in uso, al passo con l’evoluzione degli ambienti.

Le macchine virtuali in esecuzione su Red Hat OpenShift Virtualization sono protette utilizzando gli stessi flussi di lavoro e gli stessi meccanismi di governance delle applicazioni containerizzate. Questo approccio unificato sta riscuotendo successo tra le organizzazioni che stanno adottando Red Hat OpenShift come standard e che desiderano un modo più semplice e coerente per gestire i dati in tutti gli ambienti. Questa funzionalità è già disponibile.Commvault Cloudsupporta la protezione degli ambienti Red Hat OpenShift Virtualization in linea con la versione 11.40 (Long-Term Support) e la versione 11.42 (Innovation), il che significa che i clienti possono già implementare queste funzionalità in produzione.

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.

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.

La resilienza informatica è fondamentale quando la migrazione aumenta i rischi.

I periodi di migrazione rappresentano una fase particolarmente vulnerabile. Il cambiamento genera complessità, e la complessità aumenta l’esposizione alla perdita di dati e al ransomware. Commvault Cloud garantire la resilienza durante questa fase grazie a:

• Backup isolati fisicamente e immutabili per i carichi di lavoro di Red Hat OpenShift Virtualization.
• Dati di backup che supportano la ricerca delle minacce e l’analisi forense, aiutando i team a verificare la prontezza al ripristino prima di ripristinare i carichi di lavoro.
• Advanced recovery capabilities designed to help organizations minimize operational disruption.

Che i carichi di lavoro si trovino in fase di pre-migrazione, nel bel mezzo della transizione o già pienamente operativi su Red Hat OpenShift Virtualization, il livello di resilienza rimane invariato.

La flessibilità nel recupero infonde fiducia

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.

Protezione nativa per Kubernetes oltre le macchine virtuali

Per molte aziende, la virtualizzazione rappresenta solo una parte di una strategia più ampia di modernizzazione delle applicazioni. Commvault Cloud offre Cloud una protezione incentrata sulle applicazioni e nativa per Kubernetes per i carichi di lavoro containerizzati, inclusi i volumi persistenti e i metadati delle applicazioni, su tutte le distribuzioni Kubernetes certificate dal CNCF. Ciò garantisce la mobilità e il ripristino delle applicazioni cloud, contribuendo al contempo a mantenere la coerenza operativa tra i diversi ambienti.

Ridurre la proliferazione degli strumenti man mano che l’infrastruttura si evolve

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

By using Commvault Cloud as a unified protection platform for:

• Macchine virtuali VMware.
• Macchine virtuali (VM) di Red Hat OpenShift Virtualization.
• Applicazioni in container.

Le organizzazioni possono contribuire a ridurre la proliferazione degli strumenti, semplificare l’amministrazione e garantire una governance coerente anche man mano che le strategie infrastrutturali si evolvono.

Come tutto si incastra

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.

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:

• Un dialogo con i responsabili IT sulle sfide concrete in materia di resilienza.
• Consigli pratici per affrontare la migrazione con fiducia.
• Dimostrazione Cloud Commvault Cloud per Red Hat OpenShift Virtualization.

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

Andare avanti con fiducia

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 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 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.”

Domande frequenti

D: Perché la migrazione delle macchine virtuali è considerata un processo articolato in più fasi?

A: La maggior parte delle aziende non è in grado di migrare tutti i carichi di lavoro contemporaneamente, pertanto opera in un contesto ibrido in cui gli ambienti legacy e quelli nuovi funzionano in parallelo. Questo approccio graduale comporta una certa complessità, rendendo essenziali una protezione e una visibilità costanti durante l’intera transizione.

D: Che ruolo svolge la resilienza durante la migrazione delle macchine virtuali?

A: La resilienza consente alle organizzazioni di garantire la protezione dei dati, di riprendersi rapidamente dai guasti e di difendersi da minacce come il ransomware. Durante la migrazione, quando i sistemi sono in fase di transizione, misure di resilienza efficaci possono aiutare a prevenire la perdita di dati e le interruzioni operative.

D: In che modo Commvault Cloud la protezione in tutti gli ambienti?

A: Commvault Cloud un’unica platform protezione basata su criteri per le macchine virtuali VMware, le macchine virtuali OpenShift Virtualization e le applicazioni containerizzate. Questo approccio unificato consente di garantire operazioni coerenti senza dover introdurre nuovi strumenti o flussi di lavoro.

D: Perché è importante la protezione nativa di Kubernetes?

A: La protezione nativa di Kubernetes si adatta alle modalità di distribuzione e gestione delle applicazioni moderne, coprendo sia i container che le macchine virtuali. Consente una gestione semplificata dei dati, la mobilità e il ripristino all’interno di ambienti cloud.

D: In che modo la flessibilità del ripristino aumenta la fiducia nella migrazione?

A: Le opzioni di ripristino flessibili, come il ripristino in loco e fuori sede, possono aiutare i team a ripristinare rapidamente i carichi di lavoro in caso di problemi. Questa flessibilità contribuisce a ridurre i tempi di inattività e consente alle organizzazioni di adeguare i piani di migrazione senza compromettere l’integrità dei dati.

D: In che modo le organizzazioni possono ridurre la complessità durante le transizioni infrastrutturali?

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è Senior Manager del reparto Global Content Partner Marketing presso Commvault.

Punti di forza

• La la Readiverse Academy ha introdotto un percorso di certificazione strutturato e articolato in livelli, che spazia dalle conoscenze di base alle competenze avanzate cloud .
• Le certificazioni sono in linea con i ruoli professionali reali e consentono ai partecipanti di sviluppare competenze pertinenti alle loro responsabilità negli Cloud Commvault Cloud .
• The program includes four tiers – Practitioner, Specialist, Professional, and Expert – each increasing in depth and operational capability.
• L’apprendimento si articola attorno a tre pilastri fondamentali: platform , cyber resilience e workload .
• Le opzioni di formazione flessibili, che comprendono sia corsi autogestiti che tenuti da un docente, consentono ai professionisti di progredire in base ai propri impegni e ai propri obiettivi.

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 la Readiverse Academy, 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.

Creiamo contenuti su misura per te

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 la Readiverse Academy 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.

Un percorso chiaro: da principiante a esperto

Il programma di certificazione si articola attorno a tre pilastri fondamentali di competenze che caratterizzano ogni livello:

• platform di base platform
• Concetti di resilienza informatica
• Workload competenze specifiche

Ogni livello prevede requisiti specifici relativi a tali pilastri. Gli studenti possono seguire singoli corsi oppure combinare i requisiti indicati per raggiungere gli obiettivi di certificazione.

Already in la Readiverse Academy? 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 la Readiverse Academy, 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 la Readiverse Academy are well positioned to progress quickly.

Who Should Take la Readiverse Academy Courses and Certifications

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

• Platform administrators managing day‑to‑day operations.
• Specialisti della sicurezza specializzati nella protezione dei dati e nel rafforzamento della sicurezza degli ambienti.
• Cloud responsabili della configurazione del piano di controllo e della resilienza avanzata.
• Workload che devono possedere competenze in ambiti specifici relativi ai dati.

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.

Come iniziare o proseguire il proprio percorso di apprendimento

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

• Accedi o registrati sucommvault.com.
• Non conosci ancora Commvault? Inizia con il corso “Commvault Cloud ”.
• Ti occupi del workload ? Dai un’occhiata al nostro catalogo di corsi che coprono praticamente ogni argomento.
• Cerchi strategie per favorire il ripristino dopo un attacco informatico? Il corso sulla resilienza informatica è il punto di partenza ideale.

Cosa ci aspetta

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.

Domande frequenti

Q: What is the purpose of the la Readiverse Academy certification program?

A: Il programma offre un percorso formativo strutturato e incentrato sulle competenze, che aiuta i professionisti a passare dalle platform di base platform a competenze avanzate cloud . Allinea la formazione alle responsabilità del mondo reale per consentire ai partecipanti di applicare efficacemente le proprie conoscenze in contesti complessi.

D: Quali sono i diversi livelli di certificazione disponibili?

A: Esistono quattro livelli: Commvault Cloud , Specialist, Professional ed Expert. Ogni livello si basa su quello precedente, con un progressivo aumento della profondità tecnica, dell’ambito operativo e delle capacità di leadership.

Q: Who should enroll in la Readiverse Academy courses?

R: I corsi sono pensati per platform , specialisti della sicurezza, cloud e workload che operano in ambienti SaaS, software e ibridi. Ciascun ruolo può seguire un percorso formativo su misura in base alle proprie responsabilità.

D: Come si ottengono le certificazioni?

A: Le certificazioni si ottengono attraverso una combinazione di corsi, esercitazioni pratiche e valutazioni convalidate. Man mano che gli studenti progrediscono, dimostrano livelli crescenti di competenza workload platform, della sicurezza e workload .

Q: What happens to existing la Readiverse Academy certifications?

A: Le certificazioni esistenti rimangono valide come prova delle competenze acquisite in passato, ma sono legate alle versioni precedenti del prodotto. Man mano che tali versioni vengono ritirate dal mercato, le certificazioni giungeranno al termine del loro ciclo di vita, incoraggiando gli studenti a passare al nuovo programma.

D: Come si può iniziare a utilizzare il nuovo programma?

R: I nuovi studenti possono iniziare con il corso “Commvault Cloud , mentre gli utenti già registrati possono effettuare l’accesso per proseguire il proprio percorso formativo. Sono disponibili ulteriori corsi in base a obiettivi specifici, quali workload o cyber resilience .

Suzanne Klausner è direttore della strategia di supportazione dei clienti presso Commvault.

Punti di forza

• La maggior parte delle esercitazioni teoriche serve a confermare l’efficacia delle prestazioni anziché mettere in luce le reali lacune nella risposta agli incidenti.
• Affinché gli esercizi siano efficaci, devono prevedere elementi di attrito, ambiguità e pressione, in modo da rispecchiare le situazioni reali.
• Limitare l’ambito dell’esercizio a pochi scenari critici e definire il successo come l’individuazione dei problemi piuttosto che come il semplice risultato di fare bella figura può portare a intuizioni più significative e concrete.
• La partecipazione trasversale, e non solo quella dei team tecnici, è fondamentale per valutare con precisione la risposta dell’organizzazione.
• La vera resilienza si dimostra attraverso test di ripristino concreti, non solo con scenari teorici.

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.

La trappola delle prestazioni

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.

Cosa verifica effettivamente un buon esercizio

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.

Dite questo ad alta voce all’inizio: oggi il successo significa individuare i problemi, non fare bella figura. Quella sola frase cambia ciò che le persone sono disposte a dire in quella stanza.

Il problema delle persone

Una simulazione che coinvolga solo i reparti di sicurezza e IT è una discussione tecnica, non un’esercitazione di risposta agli incidenti. Se l’ufficio legale non è presente, se l’ufficio comunicazioni non è presente, se i responsabili di business e la dirigenza sono assenti, non state testando come la vostra organizzazione risponda effettivamente a una crisi. State solo verificando come un gruppo ristretto di persone competenti analizzi un caso ipotetico. Gli incidenti reali vengono gestiti a tutti i livelli dell’azienda. L’esercitazione dovrebbe rispecchiare questa realtà.

Parlarne non basta

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.

Al termine dell’esercitazione

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 una conversazione approfondita sulle esercitazioni teoriche.

Domande frequenti

D: Perché la maggior parte delle esercitazioni teoriche non riesce a fornire un valore concreto?

A: Molte esercitazioni sono concepite per far apparire le squadre ben preparate, piuttosto che per mettere in luce i loro punti deboli. Ciò porta a discussioni prestabilite che non rispecchiano l’imprevedibilità e la pressione degli incidenti reali.

D: Quale dovrebbe essere l’obiettivo di un’esercitazione teorica?

A: Dovrebbe concentrarsi sulla risposta a un numero limitato di domande fondamentali, quali la rapidità del processo decisionale, la chiarezza delle responsabilità e la capacità di recupero. Questo approccio aiuta i team a individuare lacune significative anziché limitarsi a osservazioni superficiali.

D: In che modo le organizzazioni possono rendere le esercitazioni più realistiche?

A: Introdurre elementi di incertezza, informazioni mancanti e interruzioni impreviste nel corso dello scenario. Questi elementi costringono i team a pensare in modo critico e ad agire sotto pressione, in condizioni più simili a quelle di un incidente reale.

D: Chi dovrebbe partecipare a un’esercitazione teorica?

A: Oltre ai reparti di sicurezza e IT, dovrebbero partecipare anche team come quelli dell’ufficio legale e della comunicazione, i responsabili aziendali e i dirigenti. Ciò consente all’esercitazione di rispecchiare il modo in cui gli incidenti reali vengono gestiti a livello dell’intera organizzazione.

D: Perché non basta parlare del processo di recupero?

A: La discussione può mettere in luce i piani, ma solo dei test concreti dimostrano se i sistemi possano effettivamente essere ripristinati in modo corretto e rapido. È necessaria una verifica pratica per confermare la prontezza al ripristino.

D: Cosa determina il successo di un’esercitazione teorica?

A: Un esercizio efficace porta a risultati chiari, a responsabili ben definiti e a scadenze precise per l’adozione delle misure correttive. Se questi elementi mancano, è probabile che l’esercizio non abbia messo sufficientemente alla prova il team.

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

Se si chiede alla maggior parte dei responsabili della sicurezza o dell’IT con quale frequenza testino la propria capacità di ripristino, la risposta è in genere “una volta all’anno”, a volte “due volte all’anno”. Il test consiste nel ripristinare un sottoinsieme di sistemi dal backup in un ambiente di prova, verificare che si avviino correttamente e redigere un rapporto. Talvolta, parallelamente, viene condotta anche un’esercitazione teorica. Ciò che questo tipo di test non fa: verificare che i dati di backup siano privi di malware; confermare che la sequenza di ripristino funzioni per i servizi interdipendenti. Non verifica la Recovery delle identità, essenziale quando sono state proprio le credenziali compromesse a consentire l’attacco. Non conferma che il team incaricato di eseguire effettivamente la Recovery conosca le procedure operative attuali. Né produce prove sufficientemente significative da dimostrare a un’autorità di regolamentazione, a un revisore o a un consiglio di amministrazione che la capacità di Recovery sia reale e aggiornata. In breve, convalida un momento specifico. Le operazioni di resilienza (ResOps) richiedono che la convalida sia uno stato continuo.

Il modello di convalida continua

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 l’uso improprio delle credenziali: il vettore di violazione più comune, 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.

Cosa si intende per “tempo medio necessario per la pulizia delle modifiche di ripristino”

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.

Una resilienza che si può dimostrare

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, La discussione sulla resilienza che il vostro consiglio di amministrazione non sta ancora affrontando. Per conoscere il quadro completo di ResOps, compresi i sei ambiti di ResOps e il modello di misurazione che collega la recuperabilità tecnica alla responsabilità a livello di consiglio di amministrazione, si prega di consultare il white paper congiunto:Dalla minima funzionalità alla resilienza operativa: il ResOps nella pratica.Bill O’Connell è responsabile della sicurezza presso Commvault.

Punti di forza:

• Gli attacchi informatici prendono sempre più di mira sia gli ambienti di produzione che quelli di backup, rendendo indispensabile un ripristino pulito e verificabile.
• Il rilevamento integrato di anomalie e minacce rafforza cyber resilience i dati compromessi, verificando i punti di ripristino affidabili e accelerando il ripristino.
• Se integrate nei flussi di lavoro relativi alla protezione dei dati, le funzionalità di rilevamento delle anomalie e delle minacce possono contribuire a fornire le prove necessarie per garantire un ripristino rapido, sicuro e affidabile.

Perché la resilienza informatica dipende dal rilevamento integrato di anomalie e minacce

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 modeldi nuova concezione, in cui i team di sicurezza, IT e ripristino operano sulla base di una visione d’insieme condivisa e di percorsi di ripristino convalidati per rispondere congiuntamente agli incidenti.

La nuova realtà: la ripresa richiede prove concrete, non supposizioni

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.

Rilevamento delle anomalie: il tuo primo segnale di ciò che non conosci

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.

Rilevamento delle minacce: difesa mirata contro attività dannose note

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.

Perché è importante un approccio combinato

Né il rilevamento delle anomalie né quello delle minacce, da soli, forniscono un quadro completo della situazione. Insieme, costituiscono una strategia di difesa a più livelli: il rilevamento delle anomalie può evidenziare segnali sospetti, mentre quello delle minacce può approfondire l’analisi per verificare l’esistenza di intenzioni malevole. Questa combinazione aiuta le organizzazioni a distinguere le anomalie innocue dalle vere e proprie violazioni e a disporre di dati affidabili e convalidati per un ripristino rapido.

Meeting Today’s Challenges with Commvault® Cloud

Gli hacker prendono sempre più di mira gli ambienti di backup e il malware nascosto nei dati di backup può aumentare il rischio di reinfezione durante il ripristino. Le organizzazioni hanno bisogno di una verifica basata sui dati per garantire un ripristino sicuro e affidabile.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?”.

Domande frequenti

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.

Elenco di Paulineè responsabile del marketing di prodotto presso Commvault