Join our Newsletter — 33% off our NHI Course

Does citizen development bypass security teams in business-built apps?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: Citizen development creates a governance gap when business users build apps that inherit data access and integrations without the controls applied to enterprise software, according to Pluto Security. App inventory, ownership, logging and least privilege need to be visible before those systems spread.

Editorial analysis by NHI Mgmt Group, based on content published by Pluto Security: “Citizen Development Security: When Business-Built Apps Bypass Security Teams”.

Key questions

Q: Why do business-built apps create identity risk even inside approved platforms?

A: Approved platforms can still host risky identities because the app, not the platform, defines who can act, what data can be reached and how long access persists.

Q: How should security teams govern citizen development without slowing delivery?

A: Use a guardrail model instead of a blanket approval model.

Q: What breaks when citizen-developed apps are not brought under governance?

A: The main failure is that business-built apps begin to behave like production systems while remaining outside the controls that normally govern production systems.

Practitioner guidance

  • Create a full inventory of citizen-built applications Track every low-code app, workflow and automation as an individual asset, with business owner, data classification, environment and connector list recorded at intake.
  • Put non-human identities under explicit ownership Assign a named owner to each service account, API token and bot tied to a business-built app, then review scope, rotation and revocation on a fixed cadence.
  • Restrict connector and data-source permissions by default Start with least privilege for every integration, especially where low-code tools reach SaaS tenants, databases or regulated datasets, and require approval for scope expansion.

Bottom line: Citizen development creates a governance gap when business users build apps that inherit data access and integrations without the controls applied to enterprise software.

Glossary terms: Citizen Development, Non-Human Identity (NHI), Shadow IT, Least Privilege

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Citizen development creates governance debt when app creation outruns identity control. The security failure is not low-code itself, but the mismatch between how fast business users can assemble workflows and how slowly governance processes usually adapt. When security teams do not own the inventory, classification and approval boundary, the organisation accumulates applications that behave like production systems without being treated like them. The practical conclusion is that citizen apps need explicit governance, not informal tolerance.

A question worth separating out:

Q: When should AI-assisted workflows be treated as higher risk than standard automations?

A: Treat them as higher risk as soon as the workflow can select data, trigger actions or call external services with minimal human review. AI assistance compresses the time between idea and deployment, which increases the chance that unsafe prompts, overbroad permissions or unintended actions become operational. Once the workflow can make decisions or chain integrations, it needs stricter governance than a simple task automation.

👉 Read our full editorial: Citizen development security gaps are widening around shadow IT


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.