Home/Refreshers/Emergency access that works when login is broken: refresher
Emergency access that works when login is broken
A separate account that does not depend on your identity provider, and shouts every time it is used.
Remember
- Normal sign-in is broken: the identity provider is down.
- The emergency account: outside single sign-on, with a hardware key.
- Everything it does is recorded: in the cloud's audit log.
- An alert fires, every time: to the on-call channel.
| Platform | Uses | The part that catches people |
|---|---|---|
| AWS | A standalone IAM user with a hardware key and a CloudTrail alarm | Terraform never sets the password or the MFA device, so neither lands in state. |
| Azure | A cloud-only account excluded from Conditional Access, with alerts on sign-in and change | Terraform cannot create the account, register its key, or exclude it from Conditional Access with this provider. |
| Google Cloud | A dedicated organisation administrator with a log-based alert | Terraform cannot create the account or set its password. |
| Oracle Cloud | A local user in the Default domain, outside federation, alerted on every use | Identity changes and their audit events happen in the home region. |
Run the quick start
| Download providers | terraform init |
| Preview | terraform plan |
| Apply | terraform apply |
Watch out
- Drill it on a schedule.
- Keep two, held by different people.
Check it worked
Use the account in a drill. An alert reaches the on-call channel within minutes.