Credential Injection Patterns for AI Agents

This technical post argues that giving AI agents direct access to long-lived credentials (API keys, OAuth tokens) is fundamentally insecure, as agents are goal-oriented stochastic systems that can inadvertently leak or misuse them—even without malicious intent. 

The solution lies in the Credential Brokering for AI Agents (CB4A) pattern, which separates policy decision from credential delivery. The post critiques the IETF draft's recommendation of Model B (issuing short-lived tokens to agents) as insufficient for enterprises, advocating instead for Model A (proxy gateway): the agent makes calls without credentials, and a gateway injects them just-in-time on egress, ensuring the agent never sees or holds sensitive secrets. 

Agentgateway implements this pattern, using identity federation (SPIFFE, OAuth token exchange) and cross-domain brokering to handle credentials from SaaS providers like GitHub or Slack. 

However, the post warns that this architecture creates a new high-value target—the credential store itself—which must be hardened with envelope encryption, KMS-managed keys, and strict authorization for decryption. It concludes that credential isolation requires not just removing secrets from agents, but also securing the broker that holds them. 

https://agentgateway.dev/blog/2026-07-27-credential-injection-ai-agent-egress-cb4a

Comments

Post a Comment

Popular posts from this blog

Prompt Engineering Demands Rigorous Evaluation

In the blog post “Prompt Engineering Requires Evaluation” on the Shostack + Associates website, the author argues that treating prompts for large language models (LLMs) merely as creative artefacts is insufficient. Engineering prompts properly demands structured evaluation frameworks — what the AI community calls “evals” — to test which prompt versions work better, with which models, and under which conditions. The post highlights that simply assuming a prompt is “good enough” creates risks when LLMs are integrated into production systems (e.g., for threat modeling). It advocates for measuring prompt performance, variation effects, and tool-chain dependencies (model, context, ancillary materials).  Ultimately the message is: prompt engineering should borrow disciplined practices from software engineering (versioning, testing, benchmarking) rather than relying on informal experimentation.  https://shostack.org/blog/prompt-enignieering-requires-evaluation/
Read more

Open-SPDD proposes an open framework for Spec-Driven Development workflows

Open-SPDD is an open-source project focused on Spec-Driven Product Development, aiming to formalize how software specifications, requirements, architecture, and implementation interact throughout the development lifecycle. The project promotes structured specification management, traceability, and AI-assisted engineering workflows, positioning itself as a foundation for “SpecOps”-style development practices. Its GitHub materials describe SPDD as a way to reduce ambiguity between planning and execution by treating specifications as first-class operational artifacts that can drive automation, validation, and collaboration across engineering teams  https://github.com/gszhangwei/open-spdd
Read more

OWASP ASVS 5.0 Released - Key Updates and What You Need to Know

The OWASP Foundation has released version 5.0 of the Application Security Verification Standard (ASVS), a major update to their security framework for web applications. This new version features restructured security requirements for better clarity, expanded guidance for cloud and API security, improved DevSecOps integration for CI/CD pipelines, updated threat modeling support, and enhanced compliance mapping with standards like NIST and PCI DSS. ASVS serves as a critical benchmark for developers building secure applications, penetration testers conducting security assessments, and auditors performing compliance reviews.  The standard is available for download from the OWASP ASVS project page, with organizations encouraged to integrate it into their software development lifecycles through code reviews and security testing tools. As a vendor-neutral, community-driven project, OWASP continues to welcome contributions to further develop the standard. This release represents an importa...
Read more