Secrets Hygiene
Where credentials live, how long they stay valid and how fast leaks are revoked — minimising long-lived tokens on developer machines and in agent-readable files, injecting secrets at runtime via brokers, scoping and rotating them — on the premise that stolen valid credentials, not malware, drive most intrusions, a risk coding agents with broad local access amplify.
Also known as: secrets hygiene, secrets sprawl, secret sprawl, credential rotation, secret rotation, long-lived credentials, leaked secrets
Part of: Agent Security
Documents (4)
- Podcast: Securing AI Agents: Identity, Authorization, and the DPACT Framework Sahil Agarwal · 2026-09-23 source ↗ Reader 🖥️
As AI agents shift from passive chat interfaces to autonomous 'delegated actors' that take real, consequential actions with sensitive data, organizations must replace broad, human-shaped, long-lived tokens with the DPACT framework — Delegation, Policy, Auditability, Context, and Time — so that every agent acts strictly on behalf of, and never as an impersonation of, an accountable human principal, within a bounded, auditable, expiring grant of authority, adopted incrementally rather than as a big upfront program. - How to Manage Privilege Drift in Multi-Agent Systems Janet Wagner · 2026-07-14 source ↗ Reader 🖥️
Privilege drift — the incremental, individually-reasonable accumulation of an AI agent's permissions beyond its original purpose — multiplies across the agents, shared resources, and communication channels of a multi-agent system into an attack surface no single decision ever consciously approved, and it can only be managed (never eliminated) through continuous cross-agent inventory, runtime-enforced least privilege, just-in-time access, and behavioral monitoring. - The Claude Code active attack didn't stop. 294,842 secrets stolen from 6,943 machines. It evolved and now spreads through Python too and uses Claude Code itself to steal your secrets. The risk to your credentials just got bigger. johnypita · 2026-06-10 source ↗ Reader 🖥️
A months-long, commoditised software supply-chain campaign aimed at developer credentials has evolved to target the AI layer itself — fooling AI malware reviewers and planting persistent instructions in coding-agent configuration so the developer's own agent acts with the access already granted to it — which means credential exposure, not malware, is the real risk and cleanup must neutralise agent-config persistence before credentials are rotated. - Why Token Handling Must Evolve for AI Agents J Simpson · 2026-04-20 source ↗ Reader 🖥️
Static, session-based access-token models designed for human users are fundamentally unsuited to autonomous AI agents, and must be replaced by runtime, context-aware, short-lived, minimally-scoped token strategies to prevent the class of credential-abuse breaches that already accounts for a fifth of all data breaches.
Propositions touching this concept (2)
By publication month, oldest first (extraction month when no publication date is known).
2026-06
- explicitLeaked credentials are found and abused within minutes, while organisations take months to remove leaked secrets and most leaked secrets remain valid for years — the exposure window is set by credential lifetime, not by detection speed.
2026-07
- explicitestablishedJust-in-time, short-lived, operation-specific access tokens reduce risk compared to long-lived credentials that sit in configuration files.
Open gaps (3)
- uninformedDPACT is not benchmarked or validated against measurable outcomes. Agarwal cites two vivid but small anecdotes (a hiring bot, a food-ordering bot) and a self-applied, informal 'scoring rubric' against unnamed 'famous GitHub repos,' but offers no data on incident rates, breach frequency, or cost with versus without DPACT-style controls.Podcast: Securing AI Agents: Identity, Authorization, and the DPACT Framework — read next: extract-token-handling-ai-agents, whose cited empirical stats (88% of basic web-app attacks involve stolen credentials; one in three AI adopters already breached) would be a natural quantitative complement to DPACT's qualitative case.
- unstated assumptionNo discussion of the performance and cost implications of per-request token issuance at scale.Why Token Handling Must Evolve for AI Agents — read next: Research on token-service throughput benchmarks and latency budgets for per-call issuance
- biasThe article is partly a promotional vehicle for Curity's Access Intelligence product but does not disclose the commercial relationship or compare alternative solutions.