AI Agent Authorization Beyond Authentication: A Look At AWS Dogwood
Blog post from GitGuardian
Long-lived credentials such as API keys, tokens, and certificates combine authentication with standing authorization, creating risk when they are exposed because anyone holding them may inherit their permissions. The text argues that organizations are shifting toward workload identity, short-lived credentials, and runtime policy systems that separate identity verification from authorization decisions, particularly as AI agents can execute sequences of individually permissible actions with harmful combined effects. Introduced in August 2026, AWS Dogwood builds on the Cedar policy language by adding temporal policies that assess an agent’s current request alongside its recent tool-use history, enabling controls such as requiring recent human approval, limiting calls, tracking transaction totals, or blocking external actions after sensitive-data access. Dogwood is presented as complementary to standards and technologies including OAuth, OpenID Connect, SPIFFE/SPIRE, and AuthZEN, which support delegated access, machine identity, and standardized authorization interfaces. The text also emphasizes that modern authorization does not remove the need to manage legacy secrets, citing GitGuardian data showing 28.65 million hardcoded secrets added to public GitHub commits in 2025 and an 81% increase in AI-related credential leaks, while describing GitGuardian’s Secret Analyzer and Exploration Map as tools for assessing credential permissions, dependencies, and blast radius before replacing long-lived access.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| AI Agents | 15 | 931 | 231 | 103 | -84% |
| Secrets Management | 11 | 451 | 99 | 43 | -80% |
| MCP | 2 | 2,241 | 148 | 72 | -74% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.