Skip to main content

Commvault MFA: Local Users vs. Entra ID – What do you consider more secure?

  • Nov 20, 2026 12:47 PM UTC
  • 2 replies
  • 8 views

Nikos.Kyrm
Community All Star
Forum|alt.badge.img+17

Hi to all,
 

I'm interested to hear what MFA approach you typically use in Commvault environments and what you consider the most appropriate from a security perspective.

Since Commvault is a critical component of the backup infrastructure, I'm particularly interested in how you approach authentication, identity dependencies, and the potential security impact if an external identity provider is compromised.
 

So, what do you typically implement or recommend for your customers?

  • Commvault Local MFA – Authentication and MFA managed directly within Commvault.
  • SAML Authentication with MFA (External IdP) – Authentication through an external Identity Provider such as Microsoft Entra ID, Okta, Ping Identity, Google, or ADFS, using the IdP's MFA policies.
  • No MFA – Authentication without an additional multi-factor authentication mechanism.

For those using an external identity provider, do you consider the potential impact of an IdP compromise on access to the backup infrastructure? Do you see any particular advantages or security concerns with keeping Commvault authentication independent of the corporate identity provider?

Interested to hear your experiences and what you ultimately recommend or implement in your environments.

Best regards,
Nikos

What do you typically implement or recommend for your customers?

2 replies

Nikos.Kyrm
Community All Star
Forum|alt.badge.img+17
  • Author
  • Community All Star
  • Nov 20, 2026 12:53 PM UTC

Oh, I forgot to include “No MFA” as an option in the poll, and unfortunately, I can no longer edit it. Feel free to mention it in the comments as well, if for any reason that's your preferred approach. 


Forum|alt.badge.img
  • Vaulter
  • Nov 20, 2026 1:01 PM UTC

I would generally lean toward SAML with MFA for normal administrator access, especially where the organization already has a mature IdP such as Microsoft Entra ID or Okta. This gives centralized identity lifecycle management and allows the organization to apply its existing MFA and access policies. Commvault supports third-party SAML IdPs and MFA configured at the IdP. https://documentation.commvault.com/11.42/software/adding_saml_application.html

At the same time, I would avoid making the external IdP the only recovery path into the backup environment. If the IdP is unavailable, misconfigured, or affected during a security incident, administrators still need a controlled way to regain access to Commvault.

This is where the Commvault break-glass account becomes important. Commvault specifically documents it as an emergency access mechanism for scenarios including IdP/SSO failures and MFA/TFA misconfiguration. Its access is restricted, actions are audited, and the password is regenerated on login. https://documentation.commvault.com/v11/software/break_glass_account.html

So rather than choosing purely between “local MFA” and “SAML MFA,” my preference would be:

SAML + MFA for normal administrative access, least-privilege/RBAC for administrators, and a properly protected and tested break-glass path independent of the external IdP.

That provides the benefits of centralized identity management without making recovery of the backup platform completely dependent on the corporate identity provider.

I would not recommend No MFA for privileged backup administration.