Security teams should treat employee application choice as a governance problem, not just an enforcement problem. Blocking tools can reduce risk in the short term, but users often bypass controls. A better approach is to combine clear policy, identity-based controls, and enrollment-based security so applications can be brought under managed authentication, access, and configuration standards without forcing every decision through IT.
When unapproved apps become a governance problem
Employee app choice is not just a blocking problem because people will find workarounds when a tool helps them get work done. The security question is whether the organisation can make that usage visible, policy-bound, and reviewable. That usually means deciding which app categories can be enrolled, which data types they may touch, and what authentication, logging, and approval rules must apply before use becomes acceptable.
That shift matters because a hard block often creates shadow usage instead of control. If teams need the capability, the safer pattern is to bring the application into a managed path with clear ownership, identity checks, and configuration requirements rather than letting it sit outside the control plane.
When teams treat this as governance, they can distinguish between a prohibited app, a risky app that can be managed, and a lower-risk app that can be approved with conditions. That is usually more durable than trying to enforce a binary allow or deny across every use case.
How managed enrollment changes the security model
Enrollment-based security works by making approved usage part of a known process. Instead of assuming every user decision will flow through IT, the organisation defines how an application gets onboarded, what permissions it receives, and what monitoring or review is required for continued use. For identity-heavy workflows, managed enrollment also gives security teams a way to bind the app to an accountable user or service, rather than leaving access ad hoc.
This is where identity-based controls become practical. If an app can be tied to managed authentication, least-privilege access, and clear session behaviour, it is easier to detect misuse, revoke access cleanly, and apply configuration standards consistently. The control objective is not just to know that the app exists, but to know who is using it, what data it can reach, and how that access is constrained.
For employee-driven tool adoption, a useful benchmark is whether the application can be added to the organisation’s approved catalogue without weakening security defaults. That includes whether the app supports sign-in controls, whether it can be isolated from sensitive data, and whether the business owner can justify the access it needs.
What security teams should standardise before they approve use
Security teams should standardise policy first, then technical controls, then exception handling. A policy that simply says “do not use unapproved apps” is weak if there is no intake path for legitimate business demand. A better model is to define approved categories, data handling rules, minimum authentication requirements, and escalation criteria for apps that request access to sensitive workflows.
That policy should be backed by AI Acceptable Use Policy Template style controls when the app in question is an AI or productivity tool, because users need practical rules on approved tools, data handling, and human review. For broader enforcement and automation, SOAR and Security Automation Guide is relevant where security teams want approval gates, enrichment, and response playbooks around app onboarding and misuse detection.
Teams also need to distinguish between prevention and governance. Prevention is useful for clearly unsafe cases, but governance is what scales when employees keep finding new tools that support their work. The best outcome is a process where the default path is managed use, not unmanaged use.
Risk and Threat Considerations
Unapproved applications create two main problems: they can expose corporate data to systems outside security review, and they can bypass the normal identity, logging, and retention controls that make incidents investigateable. The risk is larger when users connect apps to email, file stores, collaboration suites, or code repositories, because the app may inherit broad access quickly.
Failure mechanism: Employees route data or authentication through unsanctioned tools, creating shadow access paths that security teams cannot govern, monitor, or revoke reliably.
Impact: Sensitive information can leak, access can persist after business need ends, and investigations become harder because the organisation lacks a complete record of what the application did.
That risk is especially material for AI-enabled apps, where a user may paste content into a tool before anyone has assessed its retention, sharing, or downstream access behaviour. Insider Risk from AI Tools Guide is useful here because it frames the exposure as both data leakage and overuse of staff permissions. For a concrete example of the broader pattern, Samsung ChatGPT leak 2023 illustrates how quickly unapproved AI use can turn into a governance and confidentiality issue.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
CIS Controls v8 and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| CIS Controls v8 | CIS-5 — Account Management | Employee app approval depends on governed accounts and access paths. |
| Recommendation — Inventory accounts and remove unmanaged access paths for unapproved apps. | ||
| NIST SP 800-53 Rev 5 | IA-2 — Identification and Authentication (Organizational Users) | Managed app use requires verified user authentication before access is granted. |
| AC-6 — Least Privilege | Approved apps should receive only the access needed for their business purpose. | |
| AU-2 — Event Logging | Visibility into app activity is essential when replacing blocks with managed approval. | |
| Recommendation — Require strong user authentication for approved applications. Limit each application and user to the minimum permissions needed. Log application access and high-risk actions for review and investigation. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | Policy-driven app approval is an access control decision, not only a technical block. |
| Recommendation — Define approval rules and access conditions for unapproved application use. | ||
Practitioner Guidance
What to prioritise: Build an intake and approval path before tightening blocks. If employees have a real use case and no sanctioned route, they will keep bypassing controls.
What to verify: Confirm that each approved app has an owner, a defined data classification boundary, a revocation path, and a clear answer to what happens when the user leaves or the app is removed from approval.
What good looks like: Security can tell which tools are in use, which are conditionally approved, and which are barred, while users can still get the capability they need through a controlled route.
Practitioner takeaway: The goal is not to stop every new application from appearing, but to make approved use easier than shadow use and to ensure that access is always governed by identity, data sensitivity, and revocation readiness.
Related resources from NHI Mgmt Group
- How should security teams handle account recovery without relying on security questions?
- How should security teams govern employee AI use without blocking productivity?
- How should security teams handle workload authentication without relying on client secrets?
- How should security teams use DLP without over-relying on it?
Deepen Your Knowledge
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.
Reviewed and updated by the NHIMG editorial team on November 3, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org