BRIEF / 03.A.01
The problem
The phone used for authentication may also be needed to recover the email account that recovers other accounts. A seemingly limited loss can block access across a person’s digital life.
BRIEF / 03.A.02
Map the dependencies
The Threat Model connects the primary identity, email, devices, cloud services, documents and authorised people. The map highlights concentrated access, delegated rights and circular recovery paths.
BRIEF / 03.A.03
Required properties
Recovery must remain practical for the agreed events. Delegation must enable necessary activities without granting unrestricted access. The people involved must be able to understand and maintain the arrangements.
BRIEF / 03.A.04
Changes and responsibilities
The project can address devices, authentication, separation of uses and procedures. Family members, assistants and suppliers are included with defined authority. External platforms are assessed for their actual capabilities and dependencies.
BRIEF / 03.A.05
How verification works
Agreed exercises check the planned steps when a device, account or trusted person is unavailable. They examine whether instructions are usable, permissions are appropriate and dependencies remain necessary.
BRIEF / 03.A.06
Continuity over time
Travel, changes in delegation, incapacity and digital succession can require specific procedures. Technical arrangements must align with applicable authority and provider conditions. Any ongoing stewardship is agreed for the circumstances.