Topic starter
30/09/2026 5:00 pm
TL;DR: Internal apps can reach production through use in hours, and the real gap is connecting sign-in, permissions, credentials, model access, and token vending to shared controls instead of app-local code, according to C1.ai. The governance issue is not deployment speed itself but whether each new app is born inside the identity model or outside it.
NHIMG editorial: what this means for NHI practitioners
Questions worth separating out
Q: What breaks when internal apps are built without governed identity from day one?
A: The breakdown is visibility and accountability.
Q: Why do AI-built internal apps create governance risk even when the code is legitimate?
A: Because the problem is not the code alone.
Q: How do security teams know whether an internal app is properly governed?
A: Look for whether the app has a verified identity, a named owner, shared authorization decisions, scoped credentials, and a defined offboarding path.
Practitioner guidance
- Define a governed app-onboarding path Make sign-in, authorization, credential vending, model access, ownership, and offboarding part of the default internal app path instead of optional integrations.
- Remove app-local copies of group membership Replace local allow-lists and embedded role logic with shared policy decisions sourced from the identity platform so every app uses one source of truth.
- Tie every internal app to an owner Ensure each app can be assigned, reviewed, and retired through lifecycle processes so app access does not outlive the team that built it.
What's in the full announcement
C1.ai's full post covers the operational detail this post intentionally leaves for the source:
- Repository structure and the deployment pattern behind AppHub
- How the skills file guides coding tools to use approved primitives
- The commit sequence that removes local group membership logic
- How to adapt the app onboarding pattern to your own environment
👉 Read C1.ai's overview of AppHub for AI-built internal apps →
AI-built apps: can your identity controls keep pace with deployment?
Explore further
View Full Forum → | NHI Foundation Course → | Our Services →
30/09/2026 5:00 pm
App-local governance is becoming the new shadow access problem: The article shows how internal apps can bypass shared identity and authorization paths simply by being built faster than governance can absorb them. That is not just a deployment issue, it is an access-governance failure mode where the control plane is present in theory but absent at the point of use. The practitioner conclusion is that unmanaged shortcuts must be treated as an identity risk, not a developer convenience.
A question worth separating out:
Q: What is the difference between an app that is deployed and an app that is governed?
A: A deployed app can run and be used, while a governed app is linked to shared identity, authorization, credential, and lifecycle controls. The difference matters because only the governed app can be reviewed, attributed, revoked, and retired without relying on tribal knowledge or local code changes.
👉 Read our full editorial: C1 AppHub links AI-built apps to shared identity controls
