Security teams should treat both options as severe, but they are not equal in every scenario. Disabling MFA removes a foundational control and quickly increases the risk of credential abuse, unauthorized access, and compliance failure. Losing backups threatens recovery, ransomware resilience, and data integrity. The right choice depends on which risk is more immediate, containable, and reversible.
Why this is a resilience decision, not a simple yes-or-no toggle
During a major outage, the decision is about which control failure creates the smaller and more containable blast radius. Disabling MFA can restore access quickly, but it also removes a primary barrier against account takeover and makes any surviving credentials far more dangerous. Keeping backups offline or inaccessible can preserve stronger authentication while sacrificing recovery speed and data integrity if the outage deepens.
The practical question is not which option is ideal, but which one is least likely to turn a temporary service disruption into a wider security incident. That means judging the exposure window, the reversibility of the change, and whether the emergency action creates a new path for unauthorized access that is harder to contain than the outage itself.
For teams weighing authentication resilience and recovery resilience together, the decision should sit alongside MFA guidance and major outage lessons, because the right emergency move depends on whether identity control failure or recovery failure is the more immediate hazard.
What usually changes the answer in practice
The decision usually turns on whether MFA is blocking legitimate recovery work or whether backups are already protected well enough to survive a longer outage. If the outage is isolated to a sign-in path or identity provider dependency, a tightly scoped exception may be safer than broad rollback. If the outage affects backup availability, restore integrity, or ransomware recovery, preserving backup control may matter more than preserving an authentication control that can be re-enabled quickly.
Scope matters as much as severity. A temporary bypass for a single break-glass account is very different from disabling MFA for the whole workforce, just as losing one restore point is different from losing the only clean recovery path. The smaller and more auditable the exception, the easier it is to justify in an emergency.
Backups are especially sensitive when the environment has already seen unusual access, because any compromise of admin credentials, backup consoles, or storage access can turn a recovery problem into a full loss of trust. In that situation, emergency decisions should be informed by whether the backup path itself is still trustworthy enough to use later.
How to reduce the chance of choosing the wrong emergency option
The safest approach is to predefine what can be bypassed, by whom, for how long, and with what logging. If teams wait until an outage begins to invent an exception process, they are more likely to choose the fastest path rather than the least harmful one. Good outage playbooks separate access restoration from backup protection, so the decision is made against a known threshold rather than pressure.
That planning should include break-glass access, restore testing, and explicit rollback criteria. It should also identify which services can tolerate temporary MFA suspension and which ones cannot because they expose privileged admin paths or sensitive backup repositories. When those boundaries are known in advance, the team can keep the emergency action narrow enough to reverse cleanly.
The easiest mistake is treating the outage as proof that normal controls are no longer needed. The better test is whether the emergency change can be time-boxed, monitored, and undone before attackers or misconfigurations can exploit it.
Risk and Threat Considerations
Disabling MFA creates a short-term availability win but a long-term trust problem if credentials are already in circulation, if help desk resets are being abused, or if attackers are actively probing during the outage. Losing backups is less about immediate access abuse and more about losing the ability to recover cleanly if the outage turns into data corruption, ransomware impact, or an irreversible operational failure.
Failure mechanism: When MFA is removed, any stolen password, token, or legacy login path can become sufficient for unauthorized access. When backups are unavailable or unusable, recovery depends on the hope that the outage remains limited and that no later compromise or corruption occurs in the same window.
Impact: MFA bypass can expand the blast radius of a compromise from one account to many systems. Backup loss can convert a survivable outage into prolonged downtime, failed recovery, or permanent data loss if the primary environment cannot be restored safely.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Covers emergency decisions about weakening authentication controls. |
| CP-9 — System Backup | Directly addresses preserving backup availability during disruption. | |
| CP-10 — System Recovery and Reconstitution | Applies because the choice is fundamentally about recovery under outage pressure. | |
| Recommendation — Time-box any access exception and preserve a path to re-enable MFA quickly. Protect backup copies and restore capability before relaxing other controls. Prioritise the recovery option that can be validated and reversed cleanly. | ||
| CIS Controls v8 | CIS-5 — Account Management | Supports deciding how to handle accounts safely during an outage. |
| Recommendation — Restrict emergency account use and remove it as soon as normal access returns. | ||
Practitioner Guidance
Decision rule: If disabling MFA would expose production admin paths, remote access, or backup consoles to password-only login, keep MFA in place and use a narrower break-glass path instead. If the backup layer is the more immediate failure point, protect restore integrity first and accept slower recovery rather than giving up your last clean copy.
What to verify: Confirm which identities can still authenticate without MFA, which systems are reachable from them, and whether backup restores have been tested from an independent trust path. Also verify that any emergency change is time-bound, logged, and reversible before it is approved.
Practitioner takeaway: In a major outage, choose the option that preserves the most reversible control, not the one that feels least painful in the moment. A temporary access exception is usually safer than a permanent loss of trust in identity or recovery, but only if the exception is tightly bounded and auditable.
Related resources from NHI Mgmt Group
- How should security teams design emergency access for administrative passwords and recovery keys during a major outage?
- How should security teams decide between certificate-based authentication and MFA?
- How should teams keep privileged access available during a major outage?
- Who is accountable when Active Directory recovery fails during a major outage?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org