Clarify access, ownership, privacy, recovery, maintenance, and production responsibility.
Loading progress…
Trail 1
Who controls each critical account and can another authorised person recover the service during an incident? Use established identity mechanisms, enforce resource-level permissions on every protected operation, start access narrow, and review privileged accounts regularly.
Trail 2
Who controls each critical account and can another authorised person recover the service during an incident? Inventory, restrict, rotate, and audit secrets without placing them in source code, chat, logs, or shared documents.
Trail 3
Who controls each critical account and can another authorised person recover the service during an incident? Place domains, cloud, repositories, payments, email, analytics, and data services under company-controlled identities with multiple administrators.
Trail 4
Who controls each critical account and can another authorised person recover the service during an incident? Use company-owned organisations, named accounts, least privilege, protected production access, and documented recovery.
Trail 5
Who controls each critical account and can another authorised person recover the service during an incident? Collect the minimum necessary data and document purpose, access, provider, location, retention, export, and deletion.
Trail 6
Who controls each critical account and can another authorised person recover the service during an incident? Set business-led recovery objectives and conduct restoration exercises with someone other than the original implementer.
Trail 7
Who controls each critical account and can another authorised person recover the service during an incident? Limit dependencies, review provenance and updates, lock versions appropriately, and maintain a response path for critical advisories.
Trail 8
Who controls each critical account and can another authorised person recover the service during an incident? Inventory production dependencies and review licence obligations before product distribution or customer commitments.
Trail 9
Who controls each critical account and can another authorised person recover the service during an incident? Assign roles, contacts, evidence sources, containment authority, communication thresholds, and rehearsal before an incident.
Trail 10
Who controls each critical account and can another authorised person recover the service during an incident? Test the handover by asking a new competent person to run, deploy, diagnose, and recover the product.
Trail 11
Who controls each critical account and can another authorised person recover the service during an incident? Define included work, response targets, update cadence, monitoring, escalation, ownership, and exit before launch.
Trail 12
Who controls each critical account and can another authorised person recover the service during an incident? Approve launch against explicit gates tied to consequence, with accepted exceptions named, owned, and time-bounded.