The login failed. The service account was locked. The system had demanded a second factor it did not know how to provide.
Multi-Factor Authentication (MFA) for service accounts is no longer optional. Attackers target machine identities the same way they target human accounts. A compromised service account with broad API access can bypass most perimeter defenses. Without MFA, that compromise is fast and quiet.
Service accounts often operate without direct human interaction. They run automated jobs, pipelines, and integrations. This makes traditional MFA methods—like SMS or mobile apps—impractical. The solution is to integrate MFA that supports non-human actors: hardware tokens assigned to systems, cryptographic keys stored in secure vaults, or short-lived certificates generated at runtime.
Applying MFA to service accounts starts by inventorying every machine identity. Remove accounts that no longer have a clear purpose. Assign the minimum required permissions. Replace static passwords or API keys with dynamic credentials tied to MFA workflows. Ensure your CI/CD systems and orchestration tools can request and validate second factors.