Security Score Algorithm should NOT be weighted by number of sites

cancel
Showing results for 
Search instead for 
Did you mean: 

Security Score Algorithm should NOT be weighted by number of sites

0 Kudos

Security Score Algorithm should NOT be weighted by number of sites

There are users in my organization who have no personal sites saved with their enterprise account.  They have access to one or more shared folders and access websites from those shared folders.  Any new site they may save gets saved in a shared folder so they, and others (supervisor, for example), can access that site.

The result is that they are given a very weak security score which is not an accurate reflection of their master password security, their MFA configuration, or the strength of the passwords in the shared folder.

 

The number of personal sites saved should not be a strong determination of a user's security score.