<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vault on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/vault/</link><description>Recent content in Vault on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 02 Sep 2026 14:51:34 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/vault/index.xml" rel="self" type="application/rss+xml"/><item><title>HashiCorp Vault Agentic IAM reaches GA in Vault Enterprise</title><link>https://curadevops.metacog.co.kr/insights/2026-09-02-hashicorp-vault-agentic-iam-is-now-generally-available/</link><pubDate>Wed, 02 Sep 2026 14:51:34 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-02-hashicorp-vault-agentic-iam-is-now-generally-available/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> If your org runs Vault Enterprise and is deploying AI agent workloads, this GA feature adds purpose-built IAM controls worth evaluating this quarter; no forced migration or deadline, but assess whether your current Vault version and license tier expose it.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> This signals Vault Enterprise is extending its security model to cover AI agent identities; worth noting if AI agent adoption is on the roadmap and the org is already standardized on Vault Enterprise, but no strategy or contract decision is required now.&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> GA announcement&lt;/li>
&lt;/ul></description></item></channel></rss>