What is Device Protection

Device Protection gives you visibility and control over the software packages installed on your team's devices. It covers browser extensions, code libraries, IDE plugins, and build dependencies, all in one place.

Use-cases

  • Stop malware before it gets installed: Aikido automatically identifies known malicious packages and blocks them.

  • Get full visibility into your software supply chain: See every browser extension, code library, IDE plugin, and build dependency installed across your team's devices.

  • Lock down specific ecosystems: Block all installs from sources like Chrome or NPM when your team doesn't need them.

  • Require approval for new packages: Let team members request installs while keeping admins in control of what gets approved.

Getting Started

Ready to start securing your devices from Malware and Malicious packages? Follow the steps below to deploy and configure Aikido Device for your environment.

1

Deploy the Agent across your environment

Deploy Aikido Device across your organization using MDM or a manual installation. If you need different configurations for different teams or devices, you can create multiple groups.

Deploying Aikido Device Protection
2

Configure ecosystems

Configure your package protection settings, including supported ecosystems, allowlists, blocklists, minimum package age, and group-specific exceptions.

Configuring Installation Policies

Supported ecosystems

Device Protection monitors packages from the following sources:

  • NPM

  • PyPI (pip, poetry, uv, ..)

  • VS Code

  • Open VSX (Cursor, Windsurf, Kiro, ..)

  • Maven

  • NuGet

  • Chrome extensions

  • Skills.sh

  • Go

Last updated

Was this helpful?