DEV Community

Tech Legend
Tech Legend

Posted on AI-assisted

Non-human identities are the access problem nobody tracks

Most access reviews still focus on human users. Yet a typical estate holds far more machine identities than people: service accounts, API keys, OAuth tokens, container workload identities and AI agents — each with credentials that can read data or trigger actions.

The lifecycle is where these identities go wrong. They are created quickly, given broader permissions than needed, rarely rotated, and almost never deactivated. A leaked API key in a public repository, or a forgotten service account with admin rights, is a direct path into production.

A practical starting point:

  • Inventory every credential that is not a person. Include API keys, tokens, service accounts and workload identities.
  • Apply least privilege. Each identity should hold only the permissions its workload needs.
  • Rotate on a schedule and revoke credentials the moment a workload is retired.
  • Treat AI agents as identities. An agent that can call your APIs is an access principal and should be audited like one.

The risk is not that machines are logging in. It is that nobody is keeping track of what they can do. The full threat-landscape overview, with the attack path and the controls that actually help, is here: https://hsecurities.in/blog/non-human-identities-cybersecurity-risks

This post is an AI-assisted summary of hSECURITIES research.

Top comments (0)