Decoding the world of cybersecurity

Commvault connects Microsoft alerts with backup scanning

Commvault has integrated Microsoft Defender for Endpoint with Threat Scan to identify potentially affected backups following cyberattacks. The generally available capability helps recovery teams investigate suspicious recovery points before restoring…

Commvault connects Microsoft alerts with backup scanning
Summary
  • Commvault Threat Scan now uses Microsoft Defender for Endpoint alerts to identify systems and backups that may require investigation.
  • The integration can automatically scan potentially affected recovery points, providing additional evidence for recovery decisions.
  • The Defender integration is generally available at no additional integration charge, while Commvault's Microsoft Sentinel integrations already existed.

Commvault has introduced an integration that uses Microsoft Defender for Endpoint alerts to identify potentially affected backups, connecting endpoint threat detection with decisions about restoring systems following cyberattacks.

The capability, announced on 18 November 2026, connects Microsoft Defender for Endpoint with Commvault Threat Scan. When Defender identifies potential malicious activity, the integration can use that information to identify relevant systems and backup copies for further investigation.

Commvault says potentially affected recovery points can then be scanned automatically, giving security and recovery teams additional information before selecting data for restoration.

The integration is generally available to customers using both Microsoft Defender for Endpoint and Commvault Threat Scan. Commvault says there is no additional charge for the integration itself.

Endpoint alerts identify backups requiring investigation

Endpoint security platforms monitor activity on computers and servers, identifying processes, files and behaviours that may indicate compromise.

Microsoft Defender for Endpoint can generate alerts when it detects suspicious activity on a managed device, while Commvault Threat Scan examines protected data for indications of malware or other malicious content.

Until these sources of information are connected, recovery personnel may need to establish manually which backup copies correspond to systems identified during a security investigation.

That task becomes more difficult when an incident affects many endpoints, several applications or shared infrastructure.

The new integration uses Defender security information to direct attention towards the systems and backup copies potentially associated with an incident.

By identifying which recovery points require examination, the workflow can reduce the amount of unrelated backup data that investigators need to review immediately.

The company describes automatic scanning of those potentially affected backups, although this should not be confused with automatic confirmation that all other copies are safe.

Detection depends on the quality of the security information, the systems covered and the threats that the scanning technology can identify.

A missed endpoint event or an attack that does not produce recognisable malicious files could leave important aspects of a compromise outside the resulting assessment.

Recovery requires more than an available backup

Organisations recovering from ransomware or destructive attacks need to establish that restored data will not reproduce conditions associated with the original incident.

Backup systems may retain copies from several points in time, including copies created before and after an attacker gained access.

The most recent available backup is not necessarily the most suitable recovery point. If malicious code or unauthorised changes were present before that copy was created, restoring it could reintroduce part of the original compromise.

Endpoint alerts can help investigators understand when suspicious activity was detected and which systems may have been involved.

Those findings can then be assessed alongside backup metadata, threat scanning results and other forensic evidence.

However, the point at which a security alert was generated may be later than the attacker's initial access. An organisation cannot assume that every backup created before the alert is trustworthy.

Similarly, scanning for malware cannot establish the legitimacy of every business record or configuration change. A stolen administrator account could be used to alter information without introducing an obviously malicious file.

Recovery decisions therefore require consideration of identity systems, application configuration and the operational state of the affected services, alongside the contents of backup copies.

Existing Sentinel integration provides wider context

Commvault already integrates with Microsoft Sentinel through its Threat Scan and Risk Analysis capabilities.

Those existing connections allow security information and backup-related findings to contribute to workflows used by security operations teams.

The November development specifically adds the generally available connection between Microsoft Defender for Endpoint and Commvault Threat Scan. It should not be presented as the first integration between Commvault and Microsoft's wider security ecosystem.

Microsoft Sentinel can bring together information from different security sources, while Defender provides endpoint-level observations and Commvault maintains information about protected data and recovery options.

Each addresses a different part of an incident. Security operations personnel investigate suspicious activity, while infrastructure and recovery teams determine which systems and data can safely return to service.

Closer integration can support cooperation between those functions by providing shared evidence about affected systems and their recovery points.

It does not remove the need for decisions about containment, rebuilding compromised infrastructure or verifying application behaviour following restoration.

Recovery readiness remains difficult to establish

Commvault cited research from IDC, sponsored by the company, indicating that only 35% of organisations surveyed had automated processes for identifying backups considered safe for recovery.

The figure reflects that study's findings rather than a measured rate across every enterprise or a guarantee that automation produces trustworthy results.

Financial institutions and operators of important services face particularly demanding recovery requirements because restoring an application may not be sufficient if its supporting identity, network or data services remain unavailable.

Dependencies between systems can also affect the order in which recovery must proceed. A payment application may be restored technically but remain unusable until access controls and underlying information services are functioning correctly.

Security and recovery teams therefore need reliable evidence about which components were affected and which services depend on them.

Commvault's new Defender integration provides another source of information for that assessment. Customers need both products to use the capability, and the absence of an additional integration charge does not mean the underlying products are free.

The company has confirmed general availability but has not established through independent testing that the integration eliminates reinfection risk or can identify every unsafe recovery point.

×