Topic starter
06/06/2026 1:32 am
TL;DR: Browser prompt entry, not file transfer, is where most enterprise DLP tools miss sensitive data exposure in ChatGPT, according to Cyera's analysis. Security teams need prompt-time, context-aware enforcement to match the actual leak path instead of relying on broader blocking.
Editorial analysis by NHI Mgmt Group, based on content published by Cyera: “How Cyera stops sensitive data leaks in ChatGPT”.
Key questions
A: Security teams should focus on workspace validation, app visibility, and policy enforcement rather than blanket restriction.
Q: What are the signs that AI prompt controls are not working?
A: Common signs include employees copying sensitive data into consumer AI tools, false positives from regex-based DLP, and repeated workarounds after controls block legitimate prompts.
Q: Why do traditional DLP tools fail on ChatGPT prompts?
A: Because traditional DLP is optimised for files, email, and known egress paths.
Practitioner guidance
- Define prompt-time enforcement points Inspect browser input events before submission so pasted text can be evaluated against data sensitivity and destination context.
- Extend data classification into AI policy Use existing data labels for source code, PII, customer records, and regulated fields so the same trust model follows data into ChatGPT.
- Separate enterprise and consumer AI sessions Apply different policy outcomes when a managed device is used with sanctioned ChatGPT Enterprise versus a personal ChatGPT account.
Bottom line: ChatGPT prompt leakage exposes a practical limit in enterprise DLP because the sensitive action often occurs in the browser input field, not in a file transfer or email channel.
Glossary terms: Answer-Time Enforcement, Shadow AI, Data classification, Account-Level Trust Separation
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 7 days ago by NHI Mgmt Group
06/06/2026 2:43 am
Prompt inspection, not application blocking, is the decisive control boundary: enterprise DLP fails here because the leak happens in the browser input field before the data becomes a file, message, or network event. That makes prompt-aware enforcement a different control problem from classic outbound DLP. The implication is that organisations must design controls around the moment of data entry, not around the application name alone.
A few things that frame the scale:
- 43% of security professionals are concerned about AI systems learning and reproducing sensitive information patterns from codebases, according to the State of Secrets in AppSec.
A question worth separating out:
Q: What should teams do when sanctioned and personal ChatGPT accounts exist on the same device?
A: Apply account-aware policy rather than relying on device identity alone. A managed endpoint can host very different trust contexts, so the security outcome should change depending on whether the user is in the enterprise tenant or a personal account. Without that separation, organisations either over-restrict or under-protect.
👉 Read our full editorial: ChatGPT data leak controls expose the limits of enterprise DLP