Topic starter
14/08/2026 6:36 pm
TL;DR: ChatGPT is creating a new data-loss surface because employees paste source code, customer records, financial models, and internal documents into browser prompts that legacy DLP never sees, according to Orion. The control problem is no longer whether teams will use AI, but whether security can classify and stop sensitive text at the point of entry.
Editorial analysis by NHI Mgmt Group, based on content published by Orion: “DLP for ChatGPT: Preventing Data Leaks in ChatGPT for Enterprise Teams”.
Key questions
Q: What breaks when employees paste sensitive data into ChatGPT?
A: The break is control over where the data goes next.
Q: Why is ChatGPT prompt leakage a governance problem rather than just a user-training issue?
A: Because the risk comes from ordinary work being done in a new data surface, not just careless behaviour.
Q: How do security teams tell whether AI controls are actually stopping data loss?
A: Look for whether the control can classify sensitive text in real time and apply different responses based on context.
Practitioner guidance
- Implement prompt-time data inspection Inspect pasted or typed content in the browser and endpoint before it is submitted to ChatGPT or similar tools, with actions for redact, warn, or block.
- Classify the data employees actually paste Build policies around the data types that matter in practice, including source code, customer records, financial models, and internal documents.
- Separate platform security from data governance Keep SSO, tenant administration, and retention controls in place, but do not treat them as DLP because they do not stop disclosure in the prompt.
Bottom line: ChatGPT prompt leakage is a data-governance failure because sensitive text is entered directly into a browser session that legacy DLP was never designed to inspect.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
14/08/2026 6:42 pm
Browser-prompt exposure is a distinct governance problem, not a DLP tuning issue. When sensitive text is pasted into an AI chat surface, the organisation is no longer dealing with file movement or email exfiltration. The control boundary has shifted to the moment of human interaction, which means governance must move closer to the user action itself.
A few things that frame the scale:
- Internal repositories are 6x more likely to contain secrets than public ones (32.2% vs 5.6%), contradicting the assumption that private repos are safe, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: When should organisations restrict ChatGPT use instead of allowing it broadly?
A: They should restrict it whenever the workflow involves sensitive data, regulated records, source code, or operational instructions that could cause harm if exposed or misused. Broad approval works only when the organisation can classify inputs, govern outputs, and enforce acceptable-use rules consistently across teams.
👉 Read our full editorial: ChatGPT DLP gaps leave browser-pasted data exposed