Topic starter
16/04/2026 7:14 pm
TL;DR: AI-powered application security is reducing CVEs and injection flaws, but the real risk is shifting into workload identity, where static secrets, over-privileged service accounts, and autonomous agents expand blast radius, according to Hush Security. The older assumption that access can be safely reviewed after the fact no longer holds when credentials are short-lived, dynamic, and often invisible.
Editorial analysis by NHI Mgmt Group, based on content published by Hush Security: “The Attack Surface Hasn’t Shrunk. It’s Shifted.”.
Key questions
Q: What breaks when AI agents keep standing credentials?
A: The access model breaks because the agent can continue acting after the human has moved on, the workflow has shifted, or the original approval is no longer relevant.
Q: Why do overpermissioned service accounts become more dangerous with agentic AI?
A: Because agentic systems can move through allowed tools and backend paths faster than human operators can observe or interrupt them.
Q: How can organisations tell whether runtime identity controls are actually working?
A: Look for evidence that unsafe access attempts are being blocked, stepped up, or constrained at the point of use.
Practitioner guidance
- Map runtime access to each non-human identity Inventory which services, pipelines, and AI agents can authenticate today, then trace where each credential is actually used across cloud, hybrid, and on-premise systems.
- Replace standing access with task-scoped issuance Use just-in-time access for workloads that complete discrete tasks, and revoke credentials automatically when the task ends instead of waiting for calendar-based rotation.
- Tighten privilege to the minimum runnable scope Review each service account and agent token for the exact API calls, databases, queues, and storage paths required for one execution path, then remove everything else.
Bottom line: AI-assisted code security improves AppSec outcomes, but it does not govern the runtime identities that now carry the real blast radius.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 6 days ago by NHI Mgmt Group
06/10/2026 5:35 pm
Runtime identity, not code quality, is becoming the decisive control surface: AI is reducing the volume of classic AppSec defects, but that does not reduce the risk carried by the credentials that let services and agents act. The security model is shifting from finding broken code to governing who or what can execute actions at runtime. Practitioners should treat runtime identity as the primary place where blast radius is now determined.
A few things that frame the scale:
- 43% of security professionals are concerned about AI systems learning and reproducing sensitive information patterns from codebases, according to the State of Secrets in AppSec.
- Claude Code-assisted commits leaked secrets at a rate of 3.2%, more than double the human-only baseline of 1.5%, with peaks reaching 31 secrets per 1,000 commits in August 2025, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: Should organisations prioritise JIT access before secrets rotation?
A: No, the two controls should be implemented together. JIT reduces the time a credential can be used, while rotation limits the value of any credential that is exposed. If one is present without the other, attackers still have too much room to act. The stronger programme combines both.
👉 Read our full editorial: AI agent security is shifting the risk from code to identity