Case Study: A Password Almost Cost This Company Everything
If you ended an IT vendor relationship three years ago, how do you know for certain their access is gone? If there's any hesitation in your answer, keep reading.
At 2:00 in the morning, a VPN login came in from an account nobody at this company was using. Hyperion's NOC caught it before a single file moved. The more interesting question was how that account still existed at all.
- Industry: Large-scale professional services / manufacturing
- Location: Lenoir City, TN
- Scale: 100+ users
The Client's Challenge
A high-growth company with a decade of vendor relationships and the "ghost" access that comes with them. It had grown fast, brought in a lot of outside help along the way, and (like most companies at that stage) never had the time or process to unwind any of it.
Vendor risk doesn't always show up as a loud, chaotic attack. More often it hides in plain sight: a quiet, 10-year-old account that stays active just because "it has always been that way."
A 3:1 Account-to-User Ratio
When the Hyperion team started onboarding this client, we did what we always do first: pull a full audit of their Active Directory.
We expected to find around 100 accounts. We found 317. All active, and all with remote access enabled.
It's more common than most companies would like to admit. Vendors come and go, employees turn over, systems get migrated. Nobody wants to touch accounts that seem to just work. But over a decade, that caution ( don't break what isn't broken ) turns into an attack surface three times larger than it should be, full of accounts nobody can vouch for. At that point it's nearly impossible to tell a legitimate login from a malicious one.
The "Untouchable" Accounts
Buried in the documentation were accounts flagged with notes like "DO NOT CHANGE" or "DO NOT ROTATE PASSWORD."
Those notes get added for a specific reason at a specific moment. The reason gets forgotten, and eventually the note itself becomes the justification. Nobody touches the account because the note says not to. The note stays because nobody's touched it. Years pass.
One of those accounts belonged to a vendor the company had fired ten years earlier. The vendor was gone. The account was still there, still enabled for remote access, because it had a note on it and because offboarding had never been a written process. It lived in someone's memory, and that person had probably left years ago.
The Hidden Problem: Password Reuse
Neither the client nor Hyperion knew the most dangerous detail yet: the fired vendor had reused the same password across multiple clients.
It's a common habit, especially among smaller vendors managing access to dozens of environments. When that password surfaced somewhere else (a breach at another client, a leaked database, a phishing email), it still worked on this client's network. Valid credentials, a clean login, no failed attempts. None of it looked like an attack from the outside.
30% of breaches involve a third-party compromise (Verizon DBIR).
Hyperion's Approach
Flag It Before It Moves
During onboarding, Hyperion had already flagged that vendor account, documented it as an unresolved risk, and noted that it should never generate activity.
At 2:00 AM, our Network Operations Center (NOC) flagged a successful VPN login on it. Because we had that context, we knew exactly what we were looking at. We treated it as an active incident, terminated the session and locked down the environment before any data could leave.
Then Clean House
- Stale and orphaned accounts reviewed and removed
- Multi-factor authentication turned on, with mandatory password rotation
- A written vendor offboarding procedure, so a former vendor's access ends when the contract does
The Results
- The 2:00 AM login stopped before anything was taken
- Active Directory brought down to the accounts that should actually exist
- A written process for removing access when people and vendors leave
Our Three-Pillar Breakdown
- Stability. The risk: 300+ accounts made permissions impossible to troubleshoot. The fix: stale accounts cleaned up, so the network is predictable again.
- Security. The risk: a 10-year-old password got past every perimeter defense. The fix: layered MFA and mandatory rotation, with no "permanent exceptions."
- Operations. The risk: offboarding was a memory test, not a process. The fix: a repeatable vendor offboarding SOP.
The Critical Question for Your Business
If you ended a contract with a vendor five years ago, are you 100% sure their access is gone? Not "probably." Not "I think so." Sure.
If there's even a moment of hesitation, you have the same exposure this client had: an open door from a relationship that ended years ago, attached to a password you didn't create, can't see, and have no way to control.
Ready for the Same Results?
If you run a professional services business in East Tennessee and weak passwords or old vendor access are putting it at risk, here's where to go next:










