---
title: "Discussion on \"Non-Human Identities: Why API Keys and Service Accounts Escape Traditional IAM\" | Hashnode"
description: "Discussion on \"Non-Human Identities: Why API Keys and Service Accounts Escape Traditional IAM\". When an employee leaves, there is a checklist: badge returned, account disabled, access revoked. But the API key someone created three years ago for a short-lived project is probably still active, and"
url: "https://hashnode.com/posts/non-human-identities-why-api-keys-and-service-accounts-escape-traditional-iam/6aec73a162ddf692a4cb7fed"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Non-Human Identities: Why API Keys and Service Accounts Escape Traditional IAM](https://securityland.hashnode.dev/non-human-identities-why-api-keys-and-service-accounts-escape-traditional-iam?utm_source=hashnode&utm_medium=feed)

When an employee leaves, there is a checklist: badge returned, account disabled, access revoked. But the API key someone created three years ago for a short-lived project is probably still active, and

Nov 5 · 3 min read · securityland.hashnode.dev  
Read the article

-   [#security](https://hashnode.com/tag/security)
-   [#identity-management](https://hashnode.com/tag/identity-management)
-   [#devops](https://hashnode.com/tag/devops)
-   [#api](https://hashnode.com/tag/api)

## Written by

[Kazem Mortazavi](https://hashnode.com/@kazem-mortazavi)

@kazem-mortazavi · Tehran, Iran

  
[View profile](https://hashnode.com/@kazem-mortazavi)

Founder @ Security Land · Cybersecurity & IT Strategy Consultant · Threat analysis, network security & data protection

Founder of Security Land and CEO of PRS, with 25+ years in ICT. I write practical, no-hype analysis of the latest vulnerabilities, zero-days and incidents — and what security and infrastructure teams should actually do next. Focus areas: network security, DLP, encryption/HSM, identity and threat intelligence. More at symantecland.com

## Responses

Markdown supported · ⌘↵ to post

No responses yet.