Are Your AI API Keys on Your Asset Inventory?

Are Your AI API Keys on Your Asset Inventory?

It was a rough week to be an API key. OpenCode disclosed a breach of its Console that exposed provider keys for 1.4% of users, and some woke up to hundreds of dollars in charges. A backdoored LiteLLM release went after the keys sitting in AI gateways. And the Aoki infostealer added Claude, Codex, Cursor and Copilot tokens to its shopping list.

Three incidents, one target. The kicker is that most organizations could not tell you how many AI keys they have or where they live, because those keys never made it onto the asset inventory.

In this piece, I break down why attackers want AI keys, where they actually hide in your environment and a seven-point AI Key Inventory you can start with a spreadsheet this week.

Share :

Related Posts

Does GSA's New AI Clause Reach Your Business Through the Supply Chain?

Does GSA's New AI Clause Reach Your Business Through the Supply Chain?

GSA's new LLM clause takes effect October 19. If government data touches your AI, or your supplier's AI, the security ga...

Why You Can’t Patch Your Way out of Probabilistic Behavior (Part 1)

Why You Can’t Patch Your Way out of Probabilistic Behavior (Part 1)

Historically, security has been a deterministic game. We identify gaps, assess the associated risks and implement variou...

The 4-Level Maturity Model for Autonomous AI Governance (Part 2)

The 4-Level Maturity Model for Autonomous AI Governance (Part 2)

How you can assess the maturity and readiness of your security program to be better prepared for going agentic.