DeepSeek
Endpoint DeepSeek · Assistant · network: chat.deepseek.com
Policy · none set
Policy changes re-score this app on the next sync, which starts right away.
Finding · Open
Risk score
40
Medium
People
2
Accounts seen on devices
Devices
2
2 accounts · 30 days
Last seen
2 d ago
First seen Aug 25, 2026
endpointcorroborated
Next steps
Recommended actions
- 01DeepSeek trains on customer data. Block the app or move users to a business tier that excludes training.
- 02Device telemetry names the exact machines and accounts reaching chat.deepseek.com. Use it to target coaching rather than blanket blocks.
Endpoint
What Defender for Endpoint saw
Device connections · 2
Devices
- LT-MIA
- LT-NOAH
Device connections
chat.deepseek.com2
Same app, other lanes
Related findings
- Critical75DeepSeekNetwork2 people
- High70DeepSeek: sensitive dataPurview DLP2 people
- High62DeepSeekSIEM · Splunk (demo)1 person
Who
People
Identifiers come from device telemetry and proxy logs, so they may be account names rather than full directory entries.
| Person | Department | Source | Sign-ins · 30 d | Granted |
|---|---|---|---|---|
| n/a | Device telemetry | 0 | No direct grant | |
| n/a | Device telemetry | 0 | No direct grant |
Why
Evidence
- endpoint_telemetry · Sep 12, 2026Defender for Endpoint saw DeepSeek on 2 devices (2 accounts) in 30 days: device connections to chat.deepseek.com
Detail
{ "domains": [ { "host": "chat.deepseek.com", "count": 2 } ], "signals": { "network": 2, "process": 0, "software": 0, "extension": 0, "model_file": 0, "local_server": 0 }, "software": [], "processes": [], "extensions": [], "deviceNames": [ "LT-MIA", "LT-NOAH" ] } - corroborationAlso found by another lane (mdca:40311)
Detail
{ "findingKey": "mdca:40311" }