Endpoint Security for Developer
Devices and Shadow AI
Why Developer Devices Are the New Supply-Chain Front Door
Developer laptops hold the keys to the kingdom: GitHub and npm tokens, SSH keys, kubeconfigs, cloud credentials and session cookies. Three recent incidents show how attackers reach that keyring through packages and IDE extensions:
- Shai-Hulud npm worm (Sep 2025) — self-propagating malware across hundreds of npm packages, exfiltrating environment variables and tokens via GitHub Actions.
- GlassWorm on Open VSX (Oct 2025) — malicious VS Code extensions on the Open VSX registry stealing credentials and PATs.
- Nx Console compromise (May 2026) — a popular JetBrains plugin trojaned via a maintainer account takeover.
EDR won't catch a maintainer-signed npm package installing a credential stealer in your node_modules. Endpoint Security governs what gets onto the laptop in the first place.
See Every AI Tool Your Teams Use
The endpoint agent inventories AI tools and surfaces the ones security teams need to approve or block:
AI desktop + browser apps
ChatGPT, Claude, Gemini, Perplexity and dozens more. Local and web.
IDE AI assistants
Cursor, Copilot, Claude Code, Continue, Cline. Per-IDE, per-user.
AI coding CLIs
Aider, Codex CLI, llm, cline-cli — invoked from terminal, often unlogged.
MCP servers (local + remote)
Inventories every MCP server configured in Claude Desktop, Cursor and VS Code, with permissions.
Local models
Ollama, LM Studio, llama.cpp — detects downloaded weights and running inferences.
Personal vs corporate accounts
Flags AI tools authenticated with personal accounts for data-governance review.
Block Malicious Packages and Extensions Before Install
TigerGate intercepts installs at the registry layer. Known-malicious packages, typosquats and compromised extensions are blocked before npm install, pip install or an extension marketplace install can run post-install scripts. Optional cooldowns delay fresh package versions by a configurable window so a worm can't propagate inside your fleet before anyone notices.
| Ecosystem | Package managers | Detect | Block |
|---|---|---|---|
| npm | npm, yarn, pnpm | Yes | Yes |
| PyPI | pip, poetry, uv | Yes | Yes |
| Maven | Maven, Gradle | Yes | Yes |
| NuGet | .NET CLI, NuGet | Yes | Yes |
| Go modules | go get | Yes | Partial |
| RubyGems | gem, Bundler | Yes | Partial |
| VS Code / Open VSX extensions | VS Code marketplace | Yes | Yes |
| JetBrains plugins | JetBrains marketplace | Yes | Partial |
| Chrome / Edge extensions | Chrome Web Store, Edge Add-ons | Yes | Yes |
Vulnerable Dependencies on Laptops, Not Just in Repos
Repo-level SCA sees what's in your package.json. Endpoint SCA sees what's actually installed under ~/node_modules, ~/.local/pipx and global package stores — including dependencies pulled in by side projects, forks and local experiments that never land in a commit. Findings reuse the same vulnerability sources as TigerGate SCA/SBOM: OSV, GitHub Advisory, NVD.
Secrets Left on Devices
Scans local files, shell history, .env files and common config paths for credentials. Alerts route to the same workflow as repo-level secret scanning, with rotation guidance per secret type.
Policies, Approvals and MDM Rollout
- Group policies by team, device OS, or role (e.g. "Platform engineers may install local models; Finance may not")
- Request/approve flow for ad-hoc AI tools and risky packages
- Deploy via Jamf, Microsoft Intune and Kandji with a signed installer package, or manually with a one-line installer
- Silent install, no user interaction required
Privacy by Design: What Leaves the Device
| Data | Sent to TigerGate | Stays on device |
|---|---|---|
| AI tool / MCP / package / extension inventory | Yes (metadata only) | — |
| Device identifier & OS version | Yes | — |
| Policy decisions (allow/block events) | Yes | — |
| Prompt or completion contents | — | Yes (never leaves) |
| File contents, source code | — | Yes |
| Browsing history | — | Yes |
Connected to Code, Cloud and Runtime
A leaked GitHub token on a laptop ties to the repos it can read, the cloud role those repos can assume via GitHub Actions, and the production workloads that role touches. Endpoint findings route into the same security graph as code security, CSPM, CIEM and eBPF runtime, so one laptop finding can light up every downstream risk.
Compliance Evidence
- SOC 2 CC6.8: malicious software prevention — package firewall + extension blocking
- ISO 27001 A.8.7: protection against malware — install-time blocking across ecosystems
- ISO 27001 A.8.19: installation of software on operational systems — approval workflow, device-level audit log
- ISO 42001: AI inventory — AI tool, MCP server and model inventory for AI management system evidence
Endpoint Security FAQ
Try Endpoint Security Free
Deploy the agent on 10 developer laptops in minutes. First shadow-AI and dependency findings inside the trial.