The fastest way to give an AI agent access to something is to paste an API key into its config. That is how a lot of pilots started, including some I have watched up close. It works right up until the agent gets prompt-injected, logs the key, or sends it along to a model provider with the rest of its context. Managing AI agent secrets and credentials is moving from a niche concern into product announcements from both a fast-growing startup and IBM. If your team runs agents in production, the shortcut you took last quarter is worth revisiting this week.
Two Vendor Moves in the Same Week
On October 27, 2026, two very different companies made agent credentials the center of their announcements.
Infisical, the open-source secrets management company, announced a $40 million Series B at a $600 million valuation, led by Elad Gil. The release describes its Agent Vault product this way: it “lets companies give AI agents access without handing over credentials.” CEO Vlad Matsiiako put the logic plainly: “Agents need access to company systems to do their jobs, but giving them actual passwords and API keys is a major security risk.” In his own post on the round, Matsiiako wrote that Infisical will “significantly increase our focus on Agent Vault.” He also wrote that the company “didn’t have to raise this round” because it has been cash-flow positive. Infisical says it serves more than 1,300 customers.
IBM, at its TechXchange 2026 conference, announced that HashiCorp Vault “will now extend those capabilities to AI agents, issuing secured, short-lived credentials that limit each agent to what it needs.” IBM paired that with Agent Identity, which it describes as establishing “the authoritative record for each agent, such as who owns it, its lifecycle status and the authority it has been granted.” IBM says HashiCorp Vault 2.2 and Agent Identity are generally available. It also says Vault 2.2 “gives agents their own secured accounts” and automatically renews their credentials.
Is money “pouring into” this space? I can verify one funding round here, Infisical’s, plus a large incumbent repositioning its products. That is a meaningful signal. It is not proof of a market-wide flood, and I am not going to claim one.
Why Credentials Are the Pressure Point
IBM’s release makes the argument better than I could: “As agents invoke tools and act across business systems, their credentials become a critical security boundary.” It continues: “An agent with a long-lived, overprivileged credential can put systems and data at risk if it’s compromised or acts outside its intended task.”
Infisical’s release frames it more bluntly. Agents need credentials like API keys, passwords, and authentication tokens, “which AI agents cannot be trusted with.” The company says Agent Vault is built so an agent “cannot leak credentials in a cyberattack or inadvertently send them to LLM providers or other tools it communicates with.”
Here is my opinion, and I am labeling it as one. For many teams, secrets management is now the front line of agent security. That is because it is the control you can actually enforce today, while prompt-injection defenses are still immature. You cannot fully stop an agent from being tricked. You can limit what a tricked agent is holding.
AI Agent Secrets Management: Two Architectures, One Principle
The two announcements take somewhat different routes to the same idea:
- Brokered access (Infisical’s description): the agent never holds the real secret. Infisical says it lets agents reach approved systems without exposing the underlying credentials.
- Short-lived, identity-bound credentials (IBM’s description): each agent gets a governed identity and credentials that are short-lived and least-privilege. IBM says access can be “denied and session revoked in real time” when an agent tries something outside its approved permissions.
Both reject the pattern most pilots started with: one long-lived, broadly scoped static key, sitting in a config file or environment variable, with no owner and no expiry.
What I Would Do on Monday
These are my recommendations for platform and security teams, not vendor guidance.
- Find the keys you already handed out. Scan agent configs, prompt templates, notebooks, CI variables, and repos for hardcoded secrets. IBM’s release mentions customers using HashiCorp Vault Radar to detect hardcoded and exposed secrets. Whatever tool you use, inventory first.
- Give every agent an owner and an identity. No shared service accounts across agents. If you cannot name who owns an agent, you cannot decide when to revoke its access.
- Replace static keys with short-lived, scoped credentials. Issue them per task or per session, scope them to the specific systems and actions the agent needs, and let them expire on their own.
- Keep secrets out of the model’s context where you can. A proxy or broker pattern means a prompt-injected agent has nothing reusable to exfiltrate. Remember that it can still leak the data an approved call returns.
- Log every credentialed call. Audit trails should tie each action back to an agent identity and a human owner.
- Rehearse revocation. Practice killing a misbehaving agent’s access in minutes, not hours.
Try this hypothetical. A coding agent with a long-lived cloud key reads a poisoned README that tells it to print its environment variables into a pull request comment. With a static key, you are rotating credentials and reviewing logs all weekend. With a brokered or short-lived credential, the leaked value is useless or already expired. That difference is the whole argument.
The Bottom Line
Infisical’s Series B and IBM’s Vault and Agent Identity launches both point at the same weak spot: agents holding credentials they should not keep. The tooling is arriving. The work that falls to your team is finding the keys already pasted into configs, then moving every agent to owned, scoped, short-lived, audited access.









