Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

How to use DeepSeek both privately and securely | Kaspersky official blog

0
Medium
Vulnerabilitylocal
Published: Tue Oct 21 2025 (10/21/2025, 17:12:13 UTC)
Source: Kaspersky Security Blog

Description

We explain how to configure privacy settings in DeepSeek, how to use the chatbot securely, and how to deploy it locally.

AI-Powered Analysis

AILast updated: 11/05/2025, 02:40:19 UTC

Technical Analysis

DeepSeek is an AI-powered chatbot tool that can be used both privately and securely, particularly when deployed locally. The Kaspersky blog article provides detailed guidance on configuring privacy settings within DeepSeek, using the chatbot securely, and deploying it on local infrastructure to prevent data from being sent to external servers. Although the information is categorized as a vulnerability, no specific affected versions or exploits have been identified, and no CVSS score is assigned. The medium severity rating reflects the potential risk of privacy breaches if the tool is misconfigured or used improperly, which could lead to unauthorized data access or leakage. The article likely covers best practices such as disabling telemetry, limiting data sharing, and ensuring local data storage. The absence of known exploits in the wild suggests that the threat is currently theoretical or mitigated by proper configuration. The focus on local deployment aligns with privacy regulations like GDPR, which are critical for European organizations. The technical details emphasize the importance of understanding and managing privacy settings to prevent inadvertent exposure of sensitive information when interacting with AI chatbots like DeepSeek.

Potential Impact

For European organizations, the primary impact of this threat relates to potential breaches of confidentiality and privacy, especially given stringent data protection laws such as GDPR. Misconfiguration of DeepSeek’s privacy settings or reliance on cloud-based deployments could result in sensitive data being transmitted to or stored on external servers, increasing the risk of data leakage or unauthorized access. This could lead to regulatory penalties, reputational damage, and loss of customer trust. Additionally, organizations using AI chatbots for internal or customer-facing applications might face operational disruptions if privacy concerns lead to suspension or restriction of these tools. The impact is particularly relevant for sectors handling sensitive personal data, such as healthcare, finance, and public services. However, since no active exploits are known, the immediate risk is moderate, focusing on preventing future incidents through proper configuration and deployment strategies.

Mitigation Recommendations

European organizations should deploy DeepSeek locally whenever possible to ensure data remains within their controlled environments, minimizing exposure to external threats. They must rigorously configure privacy settings according to the guidance provided by Kaspersky, including disabling any telemetry or data sharing features that are not essential. Regular audits and monitoring of chatbot interactions should be conducted to detect any inadvertent data leakage. User training is critical to ensure that personnel understand the privacy implications and proper use of the tool. Organizations should also integrate DeepSeek deployment with existing data protection policies and incident response plans. Where local deployment is not feasible, encryption of data in transit and at rest, combined with strict access controls, should be enforced. Finally, staying updated with vendor patches and security advisories is essential, even though no patches are currently listed, to address any future vulnerabilities promptly.

Need more detailed analysis?Get Pro

Technical Details

Article Source
{"url":"https://www.kaspersky.com/blog/deepseek-privacy-and-security/54643/","fetched":true,"fetchedAt":"2025-10-21T17:25:07.644Z","wordCount":2571}

Threat ID: 68f7c1f341ea2e78b89c740a

Added to database: 10/21/2025, 5:25:07 PM

Last enriched: 11/5/2025, 2:40:19 AM

Last updated: 12/14/2025, 2:56:27 AM

Views: 163

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats