I started looking at the MFA on Command Centre and baffled as it is flawed. If my domain account has been compromised, I would be expecting the second factor to be the 2nd line of defence. But no, you can request a new pin that gets sent to your compromised domain account e-mail address. I then looked to see if I can amend my account by adding an external e-mail address, but LDAP pulls this from the domain and can not be edited. By editing the e-mail script we can omit the pin, but I think this hasn’t been thought through by Commvault, considering that backups are supposed to be the last line of defence against a cyber attack the two factor serves only to delay the time it takes for SMTP to deliver a new pin.
TFA email can be disabled using this Additional settings. If set at commcell level, it will disable for all the users that belongs to the commcell.
Name: DisableTFAEmail
Category: CommServDB.Console
Type: Boolean
value: true
I started looking at the MFA on Command Centre and baffled as it is flawed. If my domain account has been compromised, I would be expecting the second factor to be the 2nd line of defence. But no, you can request a new pin that gets sent to your compromised domain account e-mail address. I then looked to see if I can amend my account by adding an external e-mail address, but LDAP pulls this from the domain and can not be edited. By editing the e-mail script we can omit the pin, but I think this hasn’t been thought through by Commvault, considering that backups are supposed to be the last line of defence against a cyber attack the two factor serves only to delay the time it takes for SMTP to deliver a new pin.
This is being worked on.
- Option to block the pin to be sent in email.
- Option to set the email for the AD/LDAP account if user has rights.
We also just discovered disabling SSO has forced the java client to prompt for 2 factor auth. For wider community as I presume you know this.
Second factor is asked only when CV does the password authentication. When password is validated thru SSO or IDP, we act as relying party.
What I would do in this case, would talk to support in hopes that there is a qcommand / qscript that can disable the MFA Email notification and only allow the Apps. I would not be surprised if they have a way to do that.
Already did few months back they don't have any way apart from modifying the email template .
This is an issue when using domain user accounts. - If you omit the PIN from the Email, you can use one of the supported App’s to generate the PIN.
For Domain accounts you could give a “View Only” role to avoid any compromised accounts making changes.
You could use a local user account (non-domain) that has privileges in the CommCell and add the users email address to that local account.
Then to be compromised they would have to obtain the Commvault local credentials and the user’s domain credentials for the PIN email.
Best Regards,
Michael
That was meant to say “considering backups is supposed to be the last line of defence”
I edited the original post for you
I have asked some devs to take a look at this thread as well!
we are checking this internally with
we will get back on this.
Great stuff. Maybe the AD/LDAP email address should stay for the purpose of scheduled reports etc, but a 2nd e-mail field used exclusively for recovery purposes. Users should be flagged that their recovery email address is empty if MFA is enabled, and periodically prompted (6 months) to check their details are still correct. I also think any manual amending of the e-mail address be limited to the user, therefore a administrator can create\disable an account but not amend it.
We also just discovered disabling SSO has forced the java client to prompt for 2 factor auth. For wider community as I presume you know this.
TFA email can be disabled using this Additional settings. If set at commcell level, it will disable for all the users that belongs to the commcell.
Name: DisableTFAEmail
Category: CommServDB.Console
Type: Boolean
value: true
Thank you . This is working.
Thanks
Anytime, man!
That was meant to say “considering backups is supposed to be the last line of defence”
Great stuff. Maybe the AD/LDAP email address should stay for the purpose of scheduled reports etc, but a 2nd e-mail field used exclusively for recovery purposes. Users should be flagged that their recovery email address is empty if MFA is enabled, and periodically prompted (6 months) to check their details are still correct. I also think any manual amending of the e-mail address be limited to the user, therefore a administrator can create\disable an account but not amend it.
I understand that you want end user to amend the email but admin may not like it. They would like to keep the user email same as AD email to avoid defragmentation, data leak or security issues. We are targeting to update the email only when it’s empty. Ex- service account, SAML account etc.
Hey
Do we have the the option in FR25 now to disable PIN over email feature ? If yes , please share the documentation.
Refer to : https://documentation.commvault.com/11.24/expert/7935_pin_generating_tools.html
Editing in FR25 to mark this as the best (and complete) answer.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.