Every enterprise security team is fighting a workforce problem they cannot see on any org chart.

Bots, service accounts, API keys, OAuth tokens, machine certificates — non-human identities now outnumber human ones in most large organisations, often by a factor of ten to one. They authenticate constantly, operate across every environment, and when forgotten, they do not retire gracefully. They linger, accumulate privilege, and wait. Security practitioners have taken to calling them ghost identities — and the name fits.

The security industry has had plenty of warnings. It just has not acted on it.

Cast your mind back to SolarWinds story. The attackers did not smash through anything. They slipped in, found machine identities with significant access, and used them the way they were designed to be used — quietly, legitimately, invisibly. Eighteen thousand organisations. Months undetected. The credentials were not stolen in the traditional sense. They were just there, unmonitored, doing what attackers needed them to do.

Uber, 2022. Simpler anatomy. A service account nobody owned. Credentials that had not been rotated in who knows how long. Found in a network share by an attacker who was already looking. That one ghost identity opened a direct path to the PAM system — and from there, everything else followed. Cloud environments. Source code. Internal tools. One forgotten credential. That was the price of admission.

Okta, 2023. Different problem, harder to solve. The credentials that mattered were not even on Okta’s own infrastructure. They lived with a third-party support vendor. Technically, someone else’s environment. But they carried access rights into Okta’s systems, and when that vendor was compromised, the pathway was compromised too.

Three incidents. Three different entry points. One thing in common — an identity that nobody was watching, carrying access nobody had recently justified, sitting exactly where an attacker needed it to be.

Calling this a security problem is not wrong. It just does not cover what is coming next.

The scheduled crisis

In 2026, the consequences of unmanaged non-human identities take a new form. Not a breach. A calendar event.

Machine identity certificates have finite lifespans. For much of the past decade, organisations issued them with validity windows of three to five years. Between 2020 and 2022, enterprises expanded their digital infrastructure at extraordinary speed — cloud migrations compressed into months, automation pipelines stood up under pressure, and new services connecting to other services with governance as an afterthought.

Those certificates are expiring now. Not in ones and twos. In volume.

The cascading failure scenario is not complicated. A certificate expires unnoticed. The service it supports drops. Dependent applications that are authenticated through that service start failing. Monitoring tools running on the same infrastructure miss the alert. The incident response team works on the problem without a complete picture of what connects to what. Hours pass. Sometimes a full day. What started as an overlooked credential with an expiry date becomes an outage with a revenue figure attached and a regulator taking notes.

This has happened before on a smaller scale — a single expired certificate took Microsoft Teams offline for millions of users in 2020. What 2026 presents is the same failure mode, replicated across organisations that grew fast and governed poorly, hitting simultaneously.

Certificate expiration is habitually treated as an IT operations issue. That framing does not survive contact with an outage that takes customer-facing services down for eighteen hours.

Ashish Mishra

The structural gap

The root cause is not negligence. It is architecture.

The tools organisations rely on to manage identity — role-based access controls, privileged access management platforms, access certification campaigns — were built for people. They assume an identity has an owner, a manager, and a review cycle. Non-human identities do not fit that model. They get created to solve an immediate problem, granted broad access to make the thing work, and left running long after the project moves on.

Over-provisioning compounds the risk. Every unreviewed service account is a potential pivot point. Every dormant API key with write access is an open door. For ghost identities carrying legacy admin rights — and there are more of them than most organisations want to admit — the blast radius of a compromise is often organisation-wide.

What good looks like

The answer is not a tool. Every vendor in this space will tell you otherwise. They are wrong about the order of operations.

Governance comes first. Tooling supports it. And governance starts with a question most organisations cannot currently answer: what non-human identities are we running?

That question sounds simple. It is not. NHIs do not get created centrally. They get created by developers solving problems, by platform teams standing up services, by vendors connecting their products to yours. Each decision made sense at the time. None of them got logged somewhere useful. The result, in most large enterprises, is an estate that nobody has a complete map of — and that no tool can govern until someone builds one.

So, start there. Not with a platform evaluation. Not with a policy document. With a discovery sprint. Four to six weeks, focused on your highest-risk environments. Cloud first. CI/CD pipelines. Third-party integrations. An imperfect inventory is still infinitely more useful than operating blind.

While that work is running, pull your certificate expiration data. Today, not next quarter. Sort by expiry date. Filter for anything lapsing in the next eighteen months. Put a named owner against every entry — and where no owner can be identified, treat the certificate as a ghost identity. Escalate it accordingly. This one action directly addresses the 2026 expiration risk before it becomes an outage.

Last, run a privilege audit on your highest-sensitivity service accounts. Any NHI with admin rights that has not been reviewed in the past twelve months should be treated as over-privileged until the evidence says otherwise. Assume excess. Prove necessity.

None of this needs a new budget line. It needs someone to decide it is worth doing before the alternative decides for them.

The broader problem

One organisation fixing its NHI estate does not fix the problem. It just means one organisation is less exposed than the rest.

The market around machine identity is still finding its feet. Ask three vendors to define the scope of NHI governance, and you will get three different answers. Lifecycle standards that should exist do not. The frameworks security teams rely on — NIST, ISO 27001 — address least privilege as a concept but stop well short of telling anyone what to do with fifty thousand unmanaged service accounts spread across a hybrid cloud environment.

What is missing is not ambition. It is specificity. Agreed taxonomy. Shared lifecycle standards. Regulatory guidance that puts NHI governance on the same level as every other identity obligation — not buried in a footnote, not implied by a principle, but stated plainly and enforced accordingly.

That conversation is happening. Standards bodies are moving. Regulators are paying closer attention. But the pace is measured in years, and the certificate expiration wave is measured in months.

The expiry dates do not wait for the industry to catch up.

The deadline is built in

The ghost workforce does not announce itself. It does not resign or ask for a performance review. It runs until something stops it — a breach, an expiration, or a security team that finally decided to take inventory.

In 2026, for organisations that have not mapped and governed their NHI estate, something is going to stop it. The only variable is whether that something is a deliberate programme or an unplanned outage.

The runway is very thin.

This article is published as part of the Foundry Expert Contributor Network.
Want to join?