Break-glass objection battlecard
Use a concise response to defend controlled break-glass access without dismissing recovery speed.
A technical leader worries that controlled emergency access will slow outage recovery. If the identity provider is down, I do not want approvals and alerts between me and recovery. Agreed: recovery has to be fast. That is why break-glass should be pre-authorized, vaulted, tested, and alerted before the outage. During the incident, retrieval is fast; after use, the alert and rotation prove it stayed an emergency path. The response accepts the recovery concern and reframes controls as preparation, not delay. It separates normal admin work from emergency recovery and makes the account usable without making it casual. Do not say…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in