MYTHOSAI

Account security / PRACTICAL GUIDE

Make an account recovery map without exposing secrets

Find circular dependencies before a lost phone prevents access to every important account.

Before you start

A private document and access to your own account settings.

Map dependencies instead of passwords

A recovery map explains how you regain access to important services. It is not a spreadsheet containing every password. Consider a person whose password manager, email and authenticator all depend on the same phone. Losing that phone may reveal a circular recovery process: each service requires a code from another service that is also inaccessible.

You can discover these weaknesses with a private document and the account settings you already have. Do not paste recovery codes into a shared team chat to make the exercise easier.

Describe the recovery routes

  1. List important accounts: primary email, password manager, phone-platform account, financial services and work administration. Include the genuine recovery page or support route for each.
  2. Record the recovery factors in plain language, such as a separate recovery email, an authenticator, an existing trusted device or securely stored backup codes. Record their locations, not the secret values themselves.
  3. Draw the dependencies in words. For example, a reset email goes to another mailbox, which itself requires a code from the lost phone. Mark accounts that share the same point of failure.
  4. Establish a supported alternative where possible. Verify ownership of recovery contacts and remove obsolete numbers only after the replacement route is confirmed. Follow the provider's rules; some changes have waiting periods.

Test a realistic interruption

Choose one low-risk account and imagine that your primary phone is unavailable. Using another trusted device, check that you can reach a supported sign-in or recovery method. Do not wipe the phone or deliberately lock yourself out to prove the map works. A tabletop exercise can expose a missing factor without destroying access.

Keep identity evidence safe

Some recovery processes require proof of ownership or identity. Record which process applies, but avoid unnecessarily collecting scans of identity documents. Store any required material securely and submit it only through a verified provider channel when needed.

Review after life changes

Update the map when replacing a phone, changing a number, moving jobs or retiring an account. Note the date of the last review. A map becomes dangerous if it confidently points to a mailbox you no longer control. Its value comes from current, tested routes and clear responsibilities, not from the number of fields in the document.

Official references

Consult the current vendor documentation if your version or screen differs.

Documentation-based draft. Commands have not all been executed against the named products in a lab. Validate configuration examples against your installed version before changing a working system.