I have read quite a few posts about preventing account password takeover from various malicious ways, and many OPSEC measures are there to prevent it from happening.
Consider a case where you face a total blackout or technical failure. Now, you need to log in to your password manager, which requires either OTP on email or TOTP. You don’t have access to the TOTP app because the backup is stored in cloud storage, whose email login also requires OTP.
How would you prevent such from happening?I haven’t found a satisfactory solution or explanation for that yet.
You backup your 2FA locally. Problem solved.
If you’re using the cloud for anything related to security you’re doing something wrong. (In my opinion)
Just to add on what you want is the 3,2,1 method of backing up. You’re asking for trouble if you just rely on cloud storage for anything that important. Export your TOTP seeds or copy your 8-10 generated OTPs. If shit hits the fan you’ll be able to use a TOTP generator or a password manager that has one built in to get your codes.
Backup codes. You’re supposed to print them out and put it in a fire safe or something. They’re longer and not time based and valid until you rotate them. With those you can lose everything and still access your accounts.
My KeePass database is also synchronized locally on most of my devices, so even if my server is dead I’m not really locked out, I just have annoying merge conflicts to resolve.
Also, Yubikeys. They’re nice. If whatever blackout destroys your Yubikey, you have much worse problems to worry about than checking your email.
If you’re referring to keepass database merge conflicts, I use Syncthing and get these occasionally too, but KeepassDX for android can sometimes notice it and ask you if you want to merge them.
Yeah similar setup except I use NextCloud.
KeepassDX is great, can use it with just about anything too. I used it over sftp for a bit. It’ll happily do Google Drive, OneDrive, DropBox and just about anything that implements the right content providers.
Going through the provider is nice, it gives NextCloud an opportunity to sync it before it hands it over to KeepassXC, and knows when it gets saved too so it can sync it immediately. I don’t think I’ve had merge conflicts since, and I still have my offline copy just in case.
The annoying part is when you’ve added a password on one side and cleaned up a bunch of passwords on the other side. When they get merged, it doesn’t merge what changed it merges the databases together so your cleanup is gone. It’s safe at least, and exceedingly rare.
One trick is that you can enroll your TOTP codes on more than one device, the only thing the device need is the clock to be synced to provide the correct code.
You can store your TOTP codes in many places:
- A mobile app like Aegis (Android) or 2FAS (Android, iOS). Those even offer a way of backing up your TOTP codes, but you need to take the proper measure to store them safely.
- A password manager that can handle TOTP like Bitwarden (with a premium subcription) or KeePassXC.
- A security key like the Yubikey 5 can safely store TOTP keys (up to 32) and generate them through the Yubikey Authenticator app.
That way you don’t get caught your pants down if one of your device dies, get stolen, etc. Also, keep the recovery keys / backup keys in a safe place just in case of a worst case scenario.
Keep in mind that your TOTP backup and Password Manager files like KeePassXC can be the weakest link in your OPsec if you’re not careful.
I thought KeePass files are strongly encrypted. How are they the weakest link if you use a proper pass phrase?
A strong and unique passphrase is indeed really important here, but you need to keep in mind that once the kdbx file is in the attacker’s hand, that’s the only thing that keep them out.
There’s no 2FA, and no throttling on the bruteforce process. So it’s really important to use a strong password there to avoid it being the weakest link.
You can kind of do MFA on the database. You can require a key, which can be very long and complex, and you can store it on a USB drive. You might be able to use a key stored on a yubikey or something too, I haven’t tried it. It probably depends on which KeePass variant you’re using.
I use KeePass with three factors:
- The password
- A keyfile I distribute out of band between all hosts that should be able to open the database
- A set of Hardware Keys supporting challange-response
Works really well IMO. I use KeePassXC on Linux and KeePass2Android on Android.
I suppose they all use the same challenge-response key?
Yes, unfortunately they need to atm.
Print the single OTP QR code on paper, laminate and store in a lockbox
Export your OTP database to an (optionally) encrypted file on a USB stick and put that in a lockbox/somewhere safe. If encrypting the stick/file: make sure you use a memorized/written down password.
FYI data on USB sticks might not last as long as you might expect.
Personally I use BitWarden with a unique pain in the ass password that I have written it down somewhere.
From there I can get back into everything.
keep a copy of the db on your phone. I set up syncthing so the “cloud” I back up to is just my phone. You can obviously use other methods too for redundancy. I also use keepass, so my database is in my control.
I backed up the most important passwords and recovery codes on paper.
Bonus: cut it up and entrust it it to trusted people in envelopes. In case something happens they can combine their secrets to get access.
All my drives are encrypted and have an encrypted backup of 2FA, a whole bunch of drives and my phone would all have to fail at the same time. This is following 3-2-1 so not all are in the same place or running at the same time
I use veracrypt to make encrypted portable files that contain 2FA and I back them up to random cloud storage using simplelogin email accounts, no 2FA on these for this exact reason. I know my password manager passphrase but I also do the same thing with it as the 2FA file just on a different account.
If any of the accounts gets hijacked then all they have is a throwaway email and password for that account and a random tiny encrypted file.
My codes aren’t labeled with the email that they are for, just the service, e.g Proton1, and the passphrase has no other information stored with it so even if they magically managed to decrypt either of the files and gain access to the codes/ passphrase they don’t have any idea what accounts any of them are for.
Log in to a cloud storage -> download the file -> decrypt it -> add it to any compatible app -> login to the password manager
Log in to your password manager? KeepassXC just needs a decryption password. AFAIK you can set up additional protection but none of that include email.
I created a USB with an encrypted copy of my root password to a few people. It also has backups of encrypted passwords databases and some other useful files.
FYI data on USB sticks might not last as long as you might expect.
My set up OTP app + YubiKey