Corporate IT departments often assume that providing a sanctioned Enterprise workspace for AI is enough to secure company data. However, research released by NordLayer in October 2026 suggests that the availability of official tools does not automatically eliminate the risk of “Shadow AI.” Employees frequently bypass corporate guardrails, opting to use personal ChatGPT accounts for work tasks—a behavior that exposes sensitive information to model training processes.
The primary risk lies in how personal accounts handle input. By default, standard consumer-grade AI accounts are permitted to use prompts and uploaded documents to train future iterations of the model. In contrast, OpenAI provides Enterprise Data Protection (EDP) for business accounts, which ensures that company data is excluded from the training pool. When employees use personal logins to perform work duties, they effectively move proprietary data outside the company’s legally protected environment.
The Shadow AI Gap
The persistence of personal AI usage often stems from a “familiarity bias.” Employees may have spent months refining custom GPTs or personal configurations that are not easily mirrored in a locked-down corporate environment. Furthermore, the convenience of staying logged into a personal browser profile often overrides the friction of switching to an Enterprise SSO (Single Sign-On) session.
For IT administrators, the challenge is technical as much as it is behavioral. Standard network monitoring can identify traffic to OpenAI’s domains, but it cannot easily distinguish between a secure Enterprise session and a personal one without deeper inspection. According to NordLayer’s security guidance, IT teams must implement specific network strategies to close this gap without sacrificing the productivity gained from generative AI.
Implementing Tenant Restrictions
To effectively manage this risk, IT administrators are increasingly turning to Tenant Restrictions. This strategy allows organizations to control which instances of a cloud application are accessible through their network. By configuring web proxies or firewall rules to inject specific headers into outbound traffic, administrators can signal to the AI provider that only traffic originating from specific, approved workspace IDs should be permitted.
Implementing these restrictions typically involves several technical layers:
- Header Injection: Administrators can use a secure web gateway to append a header that identifies the authorized Organization ID. OpenAI and other major SaaS providers recognize these headers to block logins from personal accounts or unauthorized third-party tenants.
- Deep Packet Inspection (DPI): To ensure that traffic is not being obscured by standard HTTPS encryption, IT teams may use DPI to analyze the content of requests. This allows for the identification of unauthorized AI tool usage and the prevention of sensitive data strings (like API keys or customer lists) from being sent to personal endpoints.
- DNS Filtering: While DNS cannot distinguish between account types, it remains a primary tool for blocking access to unsanctioned AI agents or “wrappers” that lack the security maturity of major enterprise platforms.
By focusing on these “Tenant Restrictions,” IT departments can create a technical boundary that forces work-related AI tasks into the protected Enterprise silo. This approach acknowledges that while employees will continue to use AI, the responsibility for data residency and model training privacy remains a central technical configuration for the administrator.
