OpenAI's Computer History Feature Brings Keylogging and Prompt Injection Into Enterprise Scope

What happened

Why it matters

• ·Unencrypted local storage of keystroke-level data means that any malware, unauthorized process, or co-tenant application on a managed device can access highly sensitive interaction logs before they are transmitted, creating a data breach exposure that sits outside traditional DLP and CASB controls, as noted in the CASB and DLP Cannot See Inside AI Prompts analysis.
• ·OpenAI's own acknowledgment that Computer History expands the prompt injection attack surface adds a concrete new dimension to an already growing enterprise threat category, requiring compliance teams to update their OWASP Top 10 for Large Language Model Applications risk assessments for any deployment of this feature.
• ·The jurisdictional block across the EEA, Switzerland, and the UK signals regulatory exposure under regional data protection rules; organizations with operations in those territories must verify that any ChatGPT Enterprise configuration explicitly prevents Computer History from activating for users in those regions, as inadvertent enablement could trigger cross-border data transfer and consent compliance failures.

Governance controls affected

What to do now

• ☐Audit your ChatGPT Business or Enterprise admin console to confirm Computer History is disabled by default and establish a documented approval process before any enablement is permitted.
• ☐Update your data classification and acceptable-use policies to specify that keystroke-capture AI features require a formal data privacy impact assessment before deployment.
• ☐Verify that device management controls on all macOS endpoints used with ChatGPT restrict unauthorized process access to local application data directories where Computer History files are stored.
• ☐Expand your prompt injection risk assessment to cover Computer History's input-capture pipeline, including any third-party applications running alongside ChatGPT on the same device.
• ☐Confirm that Computer History is blocked for all users located in the EEA, Switzerland, and the UK through regional admin profile configurations, and document that confirmation for audit purposes.

What to watch next

Compliance teams should monitor whether data protection authorities in the EEA, UK, and Switzerland issue formal opinions on Computer History's data capture model, particularly regarding lawful basis for processing and cross-border transfer mechanisms. OpenAI has not yet indicated when or whether the feature will be made available in those jurisdictions, so any future rollout announcement should trigger an immediate review of vendor contract terms under existing EU AI Act and regional privacy obligations. Teams should also track whether the feature is extended to Windows or other platforms, which would materially change the device-security and data-exposure perimeter that current assessments are based on.