Cannot update security data for rec_uid = abracadabra

[groner]

This warning is somewhat concerning to see. Is my data being saved?

Looking at where it originates from, it appears to be a normal path for most records?

Commander/keepercommander/breachwatch.py

Lines 156 to 160 in 48a6c9f

	if params.enterprise_rsa_key and record.version in (2, 3):
	bw_res = bw_data.passwords[0].status
	save_security_data(record_uid, record, bw_res, is_reset)
	else:
	logging.info(f'Cannot update security data for rec_uid = {record_uid}')

[aaunario-keeper]

No, your data is not being saved.

That part of the code merely calculates and updates security data associated with password-containing records in your vault. These security data include metrics such as password strength, BreachWatch status (a kind of set of metadata. if you like), etc., but NEVER values that are either contained in the record itself (e.g., password, title, login URL) or that can be mapped to those values.

The security data being saved in this case are completely anonymized and in strict adherence with our "Zero Knowledge" design philosophy here at Keeper.

Regarding the output that you may sometimes see upon doing a BreachWatch scan of records (when command execution hits line 160 in the code that you highlight above): it is somewhat extraneous and unnecessarily potentially confusing (as it's not always appropriate to associate security data w/ any given record); Thus, you can rest assured that it will be improved in the next release of Commander. We appreciate you bringing this issue to our attention so that we may correct it as promptly as possible. Thank you.

[groner]

I want to clarify that my concern about data being saved is about whether an new or updated record would be retrievable later, not other forms of data collection or surveillance.

[sk-keeper]

Your data are fine. That warning should not be even logged. It will be fixed in the next release.