Security locked you out too
Training 1585 minutesbackup access
You enable a second factor on a financial account. You plan to replace your phone next month. Selling the old device will remove access to it.
Training goal: Keep both security and a recovery route
▶ Play this trainingSituation
1. The service offers recovery codes. You have not stored them securely.
- Send codes to everyone close to you
- Store the codes following service guidance
- Skip codes because the phone is new
2. Your new phone has arrived and the old one still works.
- Move the factor and test login
- Wipe the old phone before migration
- Disable the second factor permanently
3. The service still lists the old phone as trusted. Login on the new device is verified.
- Leave it trusted for the next owner
- Treat deleting the icon as logging out
- Revoke the old session before handover
4. A login approval request arrives when you are not signing in.
- Send the sender a recovery code
- Reject it and review account security
- Approve it to stop notifications
What you will learn
- Second factors need recovery plans
- Test new access before removing old access
- Do not approve unexpected prompts by habit
Your real-life step
Check where your backup access method is stored without revealing codes.
Questions and answers
Does a second factor prevent every compromise?
No. It reduces risk but does not remove fake prompts or recovery mistakes.
Can recovery codes be public?
No. They are secret access credentials.
When should I remove old access?
After testing the replacement and following the service’s process.
More trainings in this module
- Your files keep the subscription
- Your finger beats your decision
- A wallet without its key
- You bought a token, not the rights
- Familiar name, different number
- Three small payments, one date
Numbers are illustrative. A game, not financial advice.