Export function for every vault health report to export the names of the secrets found.
Feature function
What will this feature do differently?
Provide functionality to export the names of the secrets that are found when running a vault health report.
What benefits will this feature bring?
Being able to provide the results from a vault health report to a team lead or responsible person of that collection.
FEATURE NAME
Password Reports - Additional Features
FEATURE FUNCTION
The option to export weak/exposed password results to .csv
The option to show what fields are displayed within the csv, such as collection name.
Hey Bitwarden Team,
We’re an MSP who uses Bitwarden to store a large number of passwords. The weak password report could be extremely useful to us, but unfortunately it is missing the functionality above.
Request to support the export of offending passwords in the weak, reused, and exposed password reports. Ideally, this would be exported in plain text from the web app vault health reports.
Background: Customer maintains an internal “blacklist” of passwords that employees cannot use. Export of the weak, reused, and exposed password reports would allow for easy updating of this list.
Decided to update a solid chunk of passwords and my plan was use a checkbox list in a note taking app.
Atm trying to figure a way to copy and paste filtered text from the reports web page.
I can see how this feature can be security issue for less knowledgable people and in part I agree, BW should be carefull not to give users potential to get themselves owned due to lack of understanding.
As an MSP myself, I would like to be able to export the results and send them to customers.
It would be even better if there was an API call that we could use to send automated reports on a regular basis to our customers.
This would be a really nice function to have available to export to a csv file either directly from the portal or via API. I understand bringing in the passwords would be a security concern, but I only need the items that are exposed/reused/weak with the user/owner info so that I can build out an automation to Slack the users to update ASAP. If you have a lot of these to go thru it can take an excessive amount of time messaging these users one by one and most companies do not have the man power to accommodate that.
It would also be nice if we could require specific settings or at least pop up a warning if they enter a password that does not meet the companies specifications/guidelines, OR have a popup warning that this password has been resused and should be set to a different password.