At Risk Exclamation Points in Vault

[crazybored]

How do remove the at risk exclamation points showing in my vault without changing any passwords?

Thanks

[AshC]

@edreilly  You can now exclude specific password entries from the security check, from within the Vault itself by clicking the three dots next to each one and selecting Exclude from security score.  This might help you with visibility and awareness when viewing the password list at a glance. 

[edreilly]

Ash, Thank you. I looked for a three dot button next to a password item, and could not find it.  Could you please describe where the button is, or perhaps attach a screenshot?   By the way, if you are speaking about a list within the Security Dashboard view, I have a free account and no access.

[AshC]

@edreilly  It should look like this: 

Reference support guide is available here:  https://support.lastpass.com/help/how-to-exclude-password-from-security-score-calculation 

[edreilly]

Thank you. Let me say part of my last post in a different way. What I said on the last post was "... if you are speaking about a list within the Security Dashboard view, I have a free account and no access."

What that means is I have a free account. I don't have a paid account. The Security Dashboard view only comes with the paid account. The Security Dashboard view is not available for people like me who have a free account. The feature to exclude passwords from the security score, to prevent a false red alert "Password at risk", is only available for paid accounts. This comes to me as a design flaw. By design flaw I mean the user experience is degraded. I have a free account, so I get that things will be different. But the uneditable red alerts are relatively new. So it's like something bad was added. It's Ok with me if you choose to degrade your product for free users, but it's possible your QA people missed this. That's ok with me also.

If there is a way for Free account holders to exclude passwords from the security score calculation, I am interested to learn how.

[barry7]

like the person said, a lot of these passwords are simple, yet my important sites are safer.

how can i disable the security dashboard?  I know what i'm doing, and don't need nanny.. Dropbox also has a manager and so does Vivaldi, Firefox, etc.... so please listen to your paying customers

[AshC]

Hi everyone,

You can now easily exclude passwords from the security check, avoiding the 'at risk' tag by following these instructions:  

1. Log in to LastPass and access your vault by doing either of the following:
   • In your web browser toolbar, click the LastPass icon  and select Open My Vault.
   • Go to https://lastpass.com/?ac=1 and log in with your email address and master password.
2. Select Account Settings in the left navigation.
3. Click the General tab, then select Show Advanced Settings.
4. Select Disable Password Alerts.
5. Select Update, then re-enter your LastPass master password to confirm the update.

Reference guide:  https://support.lastpass.com/help/how-do-i-disable-password-alerts-for-at-risk-passwords 

[TECH198]

Not a flaw. Perhaps i may be missing something here, but isn't the whole point of a Vault (particularly what LastPass attempts to alert users to) is all designed to "secure" your passwords If a field is empty or you just store weak password there anyway for 'convenience" across all websites, then they ARE alerting you to a problem, why should you ignore it? It goes against why you'd be using it in the first place i would have thought.

In a totally related matter, there IS a flaw here i believe... I have my password flagged as "weak" on a site i keep updating for months,, (from Security Dashboard)

I can understand if I made that password simple. but this is a password recommended as secure "once" by LP themselves. Why 1 year later would they flag IT has weak,., ? At first i thought it was based on how long you have used without changing the affected password, but most other password i've never updated in years ,and to this day, they've been fine.

Its not a breach,, its just 'weak" so to speak, (.at least LP thinks it is) . Ideally, i'm ignoring it for now, but this would be a bug (...totally separate from the user saving a weak passwords above)