Security tools

Cyberful presents five capability families, but only three container environments. You normally start none of them yourself: the host gives each phase only its allowed MCP surface.

• cyberful-os is the one engagement tooling container and includes the security catalog, ZAP, and Ghidra.
• Browser provides DOM, network, cookie, artifact, and controlled interaction tools through a dedicated Chromium or Chrome profile.
• OWASP ZAP provides headless proxy and scanning capabilities for traffic-authorized phases.
• Ghidra provides persistent headless reverse engineering, decompilation, call graphs, cross-references, and annotations.
• EVM runtime provides pinned Foundry binaries, authenticated multi-repository materialization, and an engagement-owned Anvil lifecycle.

Pentest and Bug Bounty Program receive browser and ZAP traffic only inside their recorded mission. Their investigation phases may use the persistent Ghidra project in that same tooling container. Bug Bounty may also use the local EVM lab without an RPC proxy or method filter. Code Audit receives no external target-traffic route. Its runtime lab uses a source-blind dependency-bootstrap container followed by offline project execution and loopback attack inside cyberful-os.

Each sequential phase receives a fresh private gateway and reconnects through docker exec; the tooling container itself lives for the whole engagement. The host injects ephemeral keys, loopback ports, mounts, and fixed engagement network policy. Agents cannot turn an environment setting into broader authorization.

Exposed tools are callable directly under gateway phase policy, the live-target mission, traffic budgets, and the visible-CAPTCHA interlock. Individual HTTP rejections do not globally disable independent authorized work. Actual calls are recorded in the workarea's metadata-only raw/operations/tool-usage.csv; raw phase transcripts may retain their full arguments and results according to the local retention setting.