
Setting Up MFA for DefensX BackendIn this document
The recommended way to access the DefensX Backend is by using a Single Sign-On (SSO) provider such as Microsoft Entra ID, Google, or a generic SAML integration. If you’re only using SSO-based sign-in, you can also disable local sign-in from Settings → Global Settings for improved security. When to Use Local Sign-In with MFAIf you need to maintain local user accounts for backend access (outside of SSO), we strongly recommend enabling Multi-Factor Authentication (MFA) to enhance account protection. This guide walks you through configuring MFA using any authenticator app, including Microsoft Authenticator, Google Authenticator, or other TOTP-compatible applications. How to Configure MFA
Steps:
![]()
![]()
![]()
![]()
![]() Save these codes in a secure place in case you lose access to your authentication app. Lost Access to Authenticator?If you’ve lost access to your authenticator app and do not have your backup codes, don’t worry, an admin can help. Any Customer Admin or Partner Admin with full read/write permissions can reset your MFA settings. Steps for an Admin:
The user can now log in again and reconfigure MFA as needed. Disabling MFADisabling MFA is not recommended, as it reduces the security of your account. However, if you need to remove MFA enforcement on your account for any reason, you can do so by following these steps:
![]() This will remove your current MFA configuration. To avoid confusion in the future, it’s also recommended to remove the account from your authenticator app if you plan to re-enable MFA later. |
||