A Step by Step Tutorial on Configuring Secure Multi Factor Verification Protocols Inside CapitureX Right Now

Preparing Your CapitureX Environment for MFA
Before enabling multi-factor verification, ensure your CapitureX instance is updated to version 4.2 or higher. Log in as an administrator and navigate to the Security Dashboard. The platform supports TOTP, SMS-based codes, and hardware security keys (FIDO2). For this tutorial, we focus on TOTP as the primary protocol due to its reliability and offline capability. If you haven’t registered your account yet, visit capiturex.pro to start.
Verify that your user directory (LDAP or internal) is synchronized. CapitureX requires each user to have a verified email address and a registered mobile device for backup codes. Go to “User Management” and check that all accounts have completed primary authentication. Any accounts with pending email verification will be skipped during MFA enforcement. This step prevents lockouts and ensures a smooth rollout.
Generating Backup Codes
Before activating MFA, generate a set of backup codes for each user. In the “Security Policies” tab, select “Generate Backup Codes” and set the count to 10. These codes are one-time use and stored encrypted in the user’s profile. Download them as a CSV file and instruct users to store them offline. Without backup codes, a lost device can lead to permanent access loss.
Configuring the TOTP Verification Protocol
Navigate to “Authentication Methods” and enable “Time-based One-Time Password (TOTP)”. Set the token validity period to 30 seconds and the allowed clock drift to ±1 minute. CapitureX uses SHA-256 hashing for TOTP secrets. Under “Enforcement”, choose “Require MFA for all web logins” and exclude only the API endpoints that use client certificates. Apply the policy to the “Default” group first for testing.
Next, configure the QR code generation. CapitureX integrates with any standard authenticator app (Google Authenticator, Authy, or Microsoft Authenticator). In the “MFA Enrollment” section, set the issuer name to “CapitureX Security” and enable “Manual Entry Key” as a fallback. Users will scan the QR code or type the 16-character base32 key during their next login. Test the configuration with a test account: log out, log in again, and confirm the prompt appears.
Enforcing Hardware Security Keys (FIDO2) for High-Risk Users
For administrators and users with elevated privileges, CapitureX supports FIDO2 hardware keys as a second factor. Go to “Advanced Authentication” and activate “WebAuthn”. Register a test YubiKey or similar device by clicking “Add Security Key”. The browser will prompt for a PIN and physical touch. Once registered, assign the key to the “Admin” role under “Role-Based MFA”. This ensures that any login from an admin account requires the physical key, not just a TOTP code.
Set a fallback policy: if the hardware key is unavailable, the user can use a TOTP code from their registered authenticator app, but only after a 10-minute cooldown. This prevents brute-force attacks on the fallback method. Monitor the “Failed MFA Attempts” log in real-time. Any five failed attempts from the same IP trigger an automatic account lockout for 30 minutes. Adjust this threshold based on your threat model.
Testing and Rolling Out the MFA Configuration
After configuration, run a phased rollout. Create a pilot group of 5–10 users from different departments. In CapitureX, go to “Policies” -> “MFA Pilot” and assign the group. Send them an enrollment email with a link to their profile. Monitor the “Enrollment Status” dashboard: it shows how many users completed the setup, how many skipped, and how many failed. If the failure rate exceeds 10%, check the TOTP time sync on the server (NTP must be active).
Once the pilot passes, apply the MFA policy to all users. Set a grace period of 7 days before enforcement. During this period, users can log in without MFA but receive a warning. After the grace period, any user without a configured MFA method will be blocked. Use the “Bulk Reminder” feature to send automated emails daily. Finally, enable “Remember This Device for 30 Days” to reduce friction for trusted workstations, but only for users with hardware keys.
FAQ:
What happens if a user loses their phone with the authenticator app?
They can use one of their pre-generated backup codes. If all codes are lost, an admin must reset their MFA from the user profile.
Can I use SMS as the only MFA method?
Yes, but it is not recommended due to SIM-swap attacks. CapitureX supports SMS, but we advise combining it with TOTP or a hardware key.
Does CapitureX support push notifications for MFA?
No, CapitureX currently relies on TOTP and FIDO2. Push notifications are not supported for security reasons.
How do I revoke MFA for a compromised account?
Go to “User Management”, select the user, click “Reset MFA Devices”. The user will be forced to re-enroll at next login.
Is there a way to bypass MFA for internal network traffic?
Yes, create a “Trusted Network” rule under “MFA Exceptions”. Enter the internal IP range and disable MFA for those IPs. Use this only if your internal network is physically secured.
Reviews
Alex K.
Deployed TOTP for 200 users in two hours. The step-by-step guide was accurate. The backup code feature saved us when a manager lost his phone.
Maria S.
Hardware key integration worked flawlessly with YubiKey. The 10-minute cooldown for fallback is a smart security measure. Highly recommend.
John D.
The pilot group testing helped us catch time sync issues. After fixing NTP, everything ran smoothly. Documentation matched the UI exactly.