The pwned check is a great option - but we need ability to opt out per password. Some things like PIN codes will obviously show as pwned and it detracts from the overall password list view usability.
With the new Pwned Passwords dashboard in 2.48, this would also work well as an early warning. If none of an organization’s passwords are found in breach data, a new entry suddenly showing up on the dashboard would be a strong signal to act on. Entries that will always match, such as SIM PINs, bury those new hits, so a per-password exclusion would make the widget more useful.
Salmon Whistle
•
Apr 28, 2021
I support this. Seems reasonable and makes the information provided by the PWNED functionality more actionable when you don't have to filter through findings you don't care about.
Amethyst Bagel
•
Feb 23, 2021
I emailed this request yesterday - It is a great feature, but local usernames, pins etc. have no need to be checked and create false-positives.
Log in to comment and vote
Comments3
Bronze Mist
Oct 26
With the new Pwned Passwords dashboard in 2.48, this would also work well as an early warning. If none of an organization’s passwords are found in breach data, a new entry suddenly showing up on the dashboard would be a strong signal to act on. Entries that will always match, such as SIM PINs, bury those new hits, so a per-password exclusion would make the widget more useful.
Salmon Whistle
Apr 28, 2021
I support this. Seems reasonable and makes the information provided by the PWNED functionality more actionable when you don't have to filter through findings you don't care about.
Amethyst Bagel
Feb 23, 2021
I emailed this request yesterday - It is a great feature, but local usernames, pins etc. have no need to be checked and create false-positives.