Topic starter
06/11/2026 6:55 pm
TL;DR: Low-friction publishing can outpace inventory, ownership, and access review, according to Runlayer's analysis of agent-built internal apps. For practitioners, the control question shifts from app hosting to who can share it, what it can reach, and how offboarding is enforced.
Editorial analysis by NHI Mgmt Group, based on content published by Runlayer: “Vibecode on Runlayer: Artifacts and Apps, secure by design”.
Key questions
Q: Why do shared links create risk for internal tools?
A: Shared links create risk because they can bypass normal authentication and authorisation for an internal tool.
Q: How can connector-based apps avoid secret sprawl?
A: Connector-based apps avoid secret sprawl by using one controlled integration identity, not copied credentials in each workflow or tenant.
Q: How should teams govern internal apps that can be built and shared quickly?
A: Teams should make governance part of the build path, not an afterthought.
Practitioner guidance
- Inventory agent-built internal apps centrally Create a single register for every artifact and app, including owner, shared audience, version history, and the systems each tool can reach.
- Bind app access to viewer identity Require company sign-in for every internal tool and make each action execute with the viewer's own permissions rather than a shared credential.
- Gate every action change before execution Hold modified actions for owner review until the new version has been checked against the connected systems and the access path it will use.
Bottom line: Agent-built internal apps can become shadow AI when they are shared faster than governance can register and review them.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/11/2026 6:56 pm
Shadow AI is now an access governance problem, not only a discovery problem. When business users can publish working tools without engineering help, inventory alone is too late. The organisation has to govern who can share the tool, which systems it can touch, and how ownership follows the account rather than the person who happened to create it.
A few things that frame the scale:
- DeepSeek alone generated 113,000 new exposed API keys in 2025, illustrating how new AI providers create credential exposure before security guardrails catch up, according to the State of Secrets Sprawl 2026.
- Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: What should security teams review before an internal app goes live?
A: Security teams should review who owns the app, what data it can reach, which groups or roles it inherits, and whether any privileged access is granted by default. They should also check authentication method, logging, external integrations, and joiner-mover-leaver handling for the people and service accounts behind it.
👉 Read our full editorial: Shadow AI apps need identity controls before they hit Slack