research-threats VS django-mfa2

Everybody has that goal until they get a knock on their door at 6am: https://github.com/disclose/research-threats

From: disclose/research-threats: A collection of legal threats against good faith Security Researchers; vulnerability disclosure gone wrong.

I've been using https://github.com/mkalioby/django-mfa2 with good luck

The application is a slim-down version of django-mfa2 which has been 🌟 more 150 times and downloaded round 135k. As this application did only one thing, it is much easier to integrate within your current application.

Add MFA to your application and require it for at least administrative users, super users or any user who has permissions to cause any damage to the application or its data. https://github.com/gotlium/django-secure-auth or https://github.com/mkalioby/django-mfa2. Ideally you'll add and MFA mechanism that supports FIDO2/WebAuthn, but you should also support TOTP (Google Authenticator). Whatever you do, DON'T use SMS, Text Messages or emails as if they were MFA. They aren't.

Adding MFA is a must, and for that you can use https://github.com/gotlium/django-secure-auth or https://github.com/mkalioby/django-mfa2. Just please avoid using SMS or codes sent by email as if they were true MFA. They aren't. If possible prefer FIDO2, and if not, go with TOTP (google authenticator).

Unfortunately, django-mfa2 was not built to support that out-of-the-box. However, to add this feature, one needs to have a local version of the application so as to be able to extend its functionalities.

Django-mfa2 documentation

Modern browsers support this awesome technology and there are a couple of its implemetations in various major programming languages and web frameworks, however, this multi-part post will only focus on implementing it in a Django application using a wonderful django application, django-mfa2 which utilizes python-fido2 under the hood.