Q: An employee is repeatedly bombarded with MFA push notifications on their phone at 2 AM. Exhausted, they finally click "Approve" just to make it stop. What is this attack?
This is called an MFA Fatigue attack (or MFA Prompt Bombing).
Master cloud-native security and container runtime defense: Prepare with KodeKloud's CKS course with live browser-based terminal sandboxes.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "Security in modern DevOps must be automated into the pipeline rather than bolted on after deployment. The interviewer is testing: MFA Fatigue (Prompt Bombing), human-centric security flaws.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Production Solution & Architecture
This is called an MFA Fatigue attack (or MFA Prompt Bombing). Attackers already possess the user's compromised password. They intentionally trigger the application to send dozens or hundreds of MFA push notifications to the user's mobile device, hoping the victim will eventually click "Approve" out of annoyance, fatigue, or by accident. Mitigation: Implement "Number Matching" MFA, where the login screen displays a 2-digit number that the user must physically type into their authenticator app to approve the request, making accidental or fatigue-based approvals impossible.
- Immediate Triage: This is called an MFA Fatigue attack (or MFA Prompt Bombing).
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Revoking compromised credentials immediately without analyzing forensic audit trails for active exploitation when configuring Security employee repeatedly Deactivating a compromised access key prevents abuse while preserving forensic identity for CloudTrail investigations to assess blast radius.
- Terminating compromised instances immediately during incident triage without isolating volatile RAM state when configuring Security employee repeatedly Terminating compromised instances immediately destroys volatile memory evidence (RAM dumps) required to establish intrusion timelines.
-
Injecting plaintext secrets into container environment variables rather than fetching from dynamic secret vaults when configuring Security employee repeatedly
Container environment variables are visible via
docker inspector Kubernetes API queries, leaking sensitive API tokens to developers. - Failing to enforce automated credential rotation for third-party SaaS integration tokens when configuring Security employee repeatedly Static long-lived API tokens shared across internal services represent the highest-probability vector for supply-chain credential compromise.