Employee Fired After Uploading Corporate Documents to DeepSeek: How Data Security Works in AI Services
A top manager at a Moscow engineering company was dismissed after uploading internal documents containing trade secrets to the public DeepSeek service. The court sided with the employer, classifying the action as unauthorized disclosure of confidential information.
The incident reflects a broader trend. Research analyzing traffic from 150 Russian companies found that employees uploaded 30 times more corporate data to public AI services in 2025 than in the prior year. Materials included presentations, code fragments, analytics, and internal correspondence. At the same time, 60 percent of organizations still lack any formal rules governing AI tool usage.
Darya Lushkina, editor and researcher at Rating Runeta, examined these risks with Yaroslav Shmulyov, CTO of AI integrator R77 AI. When a user uploads a file such as a client contract or presentation, the document first passes through standard IT infrastructure including gateways, backend systems, and logging. The service then parses the content, extracts text and structure, and splits the text into chunks that are converted into embeddings—vector representations that capture semantic meaning.
Data therefore exists simultaneously in several forms: the original file, extracted text, text fragments, embeddings, processing logs, and metadata. The most sensitive stage is often the initial storage of the unaltered file on external servers before any further processing occurs.
Additional exposure points include logging systems that may retain fragments of content, third-party cloud providers and moderation contractors, and potential inclusion in training datasets. Once data influences model parameters during training, removal becomes technically irreversible; techniques such as machine unlearning remain an active research area with limited practical results for large language models.
Even when users enable settings that claim to prevent data use for training, the actual enforcement mechanisms are opaque. Service operators, infrastructure partners such as Google Cloud and Azure, and human moderators reviewing selected dialogues may all gain access. In 2024, Wiz Research discovered an exposed DeepSeek database containing over one million chat records and secret keys due to a misconfiguration.
Real-world consequences have already appeared at global companies. Samsung engineers sent proprietary source code and meeting notes to ChatGPT, while a U.S. cybersecurity agency head uploaded documents marked “For Official Use Only.” R77 AI consultants routinely observe similar uncontrolled usage inside client environments, prompting organizations to introduce strict data classification rules and corporate AI instances.
Looking ahead, demand is growing for local and hybrid models that keep data within controlled perimeters, alongside clearer corporate offerings that specify storage locations, training exclusions, and deletion timelines.
Related articles
Agent-Ops 0.4.0 Released: Methodology for Secure Human-AI Collaboration in IT Operations
Sergey Zhitinsky, founder of Git in Sky, has published the public normative candidate for Agent-Ops 0.4.0, an open industry methodology governing how engineers and AI agents jointly handle IT infrastructure tasks. The framework keeps humans firmly in the decision-making loop while using deterministic programs for data collection and approved changes. It addresses risks such as prompt injection through processed data, unverified model outputs, and unclear accountability when AI recommendations lead to incidents. The methodology divides work across eight explicit steps and three separate planes: data, governance, and independent verification performed by a Guardian role. Two additional companies have joined as maintainers following agreements at the IT Elements 2026 conference, turning the project into a multi-organization effort. Contributors are invited to help refine contracts, schemas, and operational scenarios through GitHub and GitVerse.
ProxyKey MCP: Securing API Access for AI Agents Without Exposing Credentials
ProxyKey has released an MCP server that allows AI coding agents such as Claude Code and Cursor to manage API credentials without ever reading the actual secret values. The solution addresses the risk that any key visible to an agent becomes compromised through logging, tracing, or prompt injection. Real provider keys are stored encrypted with AES-256-GCM and never returned by any API endpoint after initial entry. Agents instead receive limited virtual passes that support IP binding, rate limits, TTL, and detailed request logging. A pending-secret workflow lets agents prepare services before the real token exists, with the human entering the secret only through a web panel. The approach deliberately restricts the MCP tool contract so no operation can read or return secret values.
Shadow AI in CI/CD: Why AI Agents Must Be Modeled as Security Threats
A new analysis from the CNCF highlights the growing risks of Shadow AI within continuous integration and continuous deployment pipelines. The report argues that AI agents should be treated as potential threats rather than simple productivity tools. Starting from a developer's laptop and extending to Kubernetes clusters, these agents can introduce unauthorized access paths and data exposure risks. Security teams are urged to incorporate AI agent behavior into formal threat modeling exercises. The discussion emphasizes the need for visibility and control over autonomous AI components operating in production environments.
Detecting Lateral Movement with Neural Networks Trained Solely on Synthetic Data
A researcher generated entire corporate network histories using a 135-line configuration file to create synthetic authentication logs containing lateral movement attacks. Neural networks trained exclusively on these artificial datasets were then evaluated against 1.65 billion real authentication events from Los Alamos National Laboratory, including 749 red team events across 301 compromised machines. The best ensemble of six models flagged 3.6 million hourly machine windows and placed 16 genuine attacks among the top 23 highest-scoring entries, producing only seven false positives. In comparison, a simple threshold counter required 161,000 false alarms to reach the same detection level. The approach also demonstrated an iterative feedback loop where detector errors directly informed refinements to the synthetic world generator. The work shows that synthetic data can reach AUC performance comparable to models trained on real labeled attacks while providing full control over the underlying attack definitions.