security program for a google chrome book

lava - Acer Chromebook Spin 11 (CP311-1H & CP311-1HN).kasumi360 - Chromebook Spin 311 (R721T).electro - Acer Chromebook Spin 11 (R751T / CP511).

dru - Acer Chromebook Tab 10 (D651N / D650N).

careena - HP Chromebook 14 db0000-db0999.bruce - Acer Chromebook Spin 15 CP315-1H / 1HT.blue - Acer Chromebook 15 CB315-1H / 1HT.bigdaddy - HP Chromebook 14 / HP Chromebook 14 G5.basking - ASUS Chromebook C213NA/C213SA.akali360 - Acer Chromebook Spin 13 (CP713-1WN).Users can visit the Chrome OS chrome://version page to see what model/codename their device has, and compare it the list below. Nevertheless, Google recommends updating devices to Chrome OS 75 and above, as a precaution, in case they decide to use the feature in the future. However, if users never used the feature, they aren't impacted. Google said that only Chromebook versions that support the H1 chip and the built-in security key feature are impacted. In case you received a 'Internal security key requires reset' notification, click 'Reset' on the notification to prevent it from showing again.(optional) Review recent successful logins to services to determine whether there's anything suspicious.There is no need to change passwords or other account security settings. Exact instructions vary by service, but typically there are 'account settings' or 'security settings' that list registered security keys and give you the option to remove / unregister security keys. Unregister the Chrome OS built-in security key from all these services.Make a list of your accounts on websites where you have registered a security key generated by Chrome OS' built-in security key feature.The H1 firmware version is listed on the chrome://system page under cr50_version, specifically the RW line. Versions 0.3.15 and later are not vulnerable. Production H1 firmware versions with a version number of 0.3.14 and earlier contain the vulnerability. Update to Chrome OS 75 or later to receive a fix for the H1 chip firmware.'Full remediation requires both a firmware fix and retiring key pairs that have generated vulnerable signatures,' the company added. 'Nevertheless, we recommend users to take remediation steps as described below to avoid the risk of running with a cryptographically weakened U2F authenticator,' Google said.

Security program for a google chrome book