Tool Inventory
Every scan runs in an isolated Kali Linux sandbox. These pages list every tool installed in each sandbox, where it came from and the exact version.
Every scan runs in an isolated Kali Linux sandbox. These pages list every tool installed in each sandbox, where it came from and the exact version.
Sandboxes by plan
| Plan | Sandbox | Inventory |
|---|---|---|
| Lite | Web sandbox | 84 tools for web application testing: Lite: Web Sandbox |
| Hacker | Pro sandbox | 134 tools, adding TLS auditing, password cracking, Active Directory attacks, mobile app analysis and Metasploit: Hacker: Pro Sandbox |
| Red Team | Max sandbox | 142 tools, adding cloud account auditing and exploitation, full binary reverse engineering and wireless attacks: Red Team: Max Sandbox |
| Enterprise | Max sandbox | Same inventory as Red Team, with the usage limits described in Plans & Pricing. |
What each entry shows
- Summary and description: what the tool does and how scans use it.
- Source: how the tool was installed into the sandbox image (see below).
- Version: the exact version in the image, read from the built image rather than maintained by hand.
- Command: the executable to run.
- Upstream: a link to the project's home page, and a typical usage example.
Source types
| Source | Meaning |
|---|---|
apt | Kali Linux package repository |
go | Built from a Go module with go install |
pipx | Python application in its own isolated environment |
venv | Python package installed into the agent virtual environment |
pip | Python package installed with pip |
npm | Node.js package installed globally |
binary | Pinned upstream release binary, checksum-verified |
git | Cloned from the upstream repository when the image is built; the version is unpinned or pinned clone |
Versions
Sandbox images are rebuilt for each release and every build is validated before it is rolled out, so versions advance over time. The version shown here is the one in the current image for each plan.