Upon creation, import, or update of a password, automatically trigger the exposed/weak/reused check to halt the creation of insecure passwords. The current process requires a user to manually click the “checkmark” before saving and a vast majority of people do not use this function.
My enterprise organization has migrated from another password solution to Bitwarden. While importing passwords from our previous solution, technicians were unaware that they needed to manually click the “checkmark” to check that password for exposure, weakness, or reuse. We now have a very large collection of passwords on the Exposed, Weak, and Reused reports that will require manual remediation and cleanup.
Proactively protect users from creating weak passwords by automatically checking a new/imported/updated item and populating a notification pop-up to warn users prior to clicking “save.” You could even include a requirement for a user to check a box to override the warning. Include this activity as part of the event logs.
These features are the difference between a true Enterprise product and a commercial version. Large enterprises need to halt insecure activities proactively, not allow a user to create a weak password and offer me a simple report to reactively remediate items.