Each audit runs in a fresh darkops sandbox — a hardened Ubuntu desktop with the offensive security toolkit pre-installed and ready. GigaOps has full bash access to all of these tools.The sandbox is provisioned per-audit, used for the duration of the engagement, and destroyed at completion. No state leaks between engagements.
The sandbox includes a full Chromium installation for any web target interaction that requires a real browser — JavaScript-heavy SPAs, complex auth flows, CSRF token handling, etc.
The sandbox runs Ubuntu with full apt access. GigaOps can install additional tools on demand within an engagement — for example, fetching the latest version of nuclei’s template set, or installing a CVE-specific PoC repo from GitHub.For Autonomous engagements, you can specify required tooling in your brief:
Tooling: Install Kerbrute before phase 7 for Kerberos enumeration.
Tools are kept on the current stable release. The sandbox image is rebuilt regularly to keep nuclei templates, metasploit modules, and exploitation tooling up to date.