What if…? Autothenticator security scenarios
| If this happens | What the attacker gets |
|---|---|
| Winfrasoft's whole database is stolen | Encrypted data, email addresses and public keys. Nothing can be decrypted |
| Winfrasoft's servers are compromised | They can delay sync. They can't read vaults, change accounts or add a device |
| The person's email account is taken over | Nothing. Email is only for notices |
| Their Google, Microsoft or Apple account is taken over | The website: they can see and remove devices. A new device still needs one of the person's own devices, or their recovery kit |
| A locked phone is stolen | Nothing without the fingerprint, face or device PIN. Remove it from the device list, and the keys change |
| A copy of a locked browser profile is taken | Encrypted data only. It can ask the phone to unlock it, which the person declines |
| Malware on an unlocked computer | What that device can see while unlocked, as with any password manager |
| The recovery kit is found | Everything, which is why the kit says to keep it like a passport. Make a new one from any device |
The model in short:
- Your sign-in reaches the website, not your data.
- Each device has its own key.
- The vault key is random, and passes only between your own devices.