Disclaimer: Dr. Seymour Keys is not a real doctor (but he does diagnose messy IT infrastructure). Credentialitis is not a real medical condition — just a very real security and efficiency problem.
“A diagnosable condition affecting organizations overwhelmed by non-human identities and credentials — leading to operational drag and security risk.”
Before Credentialitis began spreading, humans endured another chronic identity dysfunction: Passphoria, the long-standing illusion that passwords were enough to protect users and the systems they touched. Unless you’ve developed actual amnesia, you now know they weren’t.
The harder organizations pushed for better password hygiene, the worse things got. Workers reused credentials, stored them in spreadsheets, and – most famously – stuck them to monitors on Post-it notes. Rotation policies became resented rituals. Fatigue set in. And attackers capitalized.
Security teams responded with password managers, MFA, SSO, and IAM, bringing order to the chaos of human authentication. The side effect? Password resets dropped, onboarding got easier, and support tickets stopped piling up. Then something peculiar happened: End-users became happier and more productive.
Now, unfortunately, the same pattern is playing out again – just deeper in the stack and across far more identities, especially as agentic AI takes center stage and demands authentication.
Credentialitis is simply the next stage of Passphoria. Non-human credentials may not be taped to a computer monitor, but they’re hardcoded in Git, passed through CI/CD pipelines, or buried in config files no one audits — creating security risks and saddling developers with the need to hand-roll auth that’s error-prone, tedious to maintain, and prone to leaks.
The sticky note hasn’t gone away – it’s been abstracted.
Read on to scan the companion ailments, symptoms, causes, and risk factors, take a diagnostic exam, and explore recommended treatments.
JUMP TO
Credentialitis is a chronic condition caused by over-reliance on static secrets, sprawling vaults, and dev-coded auth. It’s triggered by unmanaged non-human identities – including applications, scripts, AI agents, services, and other software workloads – that access sensitive resources without proper oversight, authentication, or policy enforcement.
It disproportionately affects:
Implement non-human IAM with:
Chronic pain from the repetitive strain of manual credential rotation.
Symptoms include:
Exhaustion from managing short-lived tokens across too many clouds, services, and pipelines.
Symptoms include:
Bothersome back pain from embedding brittle auth logic deep in the codebase.
Symptoms include:
Secrets and tokens embedded in code, configs, and environments — left to rot, rarely rotated, and easily leaked.
A cross-cloud dysfunction marked by duplicated roles, mismatched trust, and inconsistent access policies between identity providers.
A degenerative condition where no one remembers why the AI agent exists, what it can access, or who owns it — but no one dares delete it “just in case.”
Successfully treating Credentialitis without fully addressing the root problem can lead to
Persistent stress triggered by past breaches, exposed tokens, or failed secrets management efforts.
Symptoms include:
Got Credentialitis? Let’s find out.
This diagnostic assessment reveals just how bad the secret sprawl is—and how to get ahead of it.