Your work. Your boundaries.
A user-friendly explanation of what PENTER can access, which tools are available in the public beta, and how to keep engagement evidence and account information protected.
Only assess targets you're authorized to test
Every investigation should start with a clear approved target and an engagement workspace. PENTER uses that context to restrict supported target-facing tools. Public visibility is not permission: you must have authorization to assess a site or system.
- Confirm the customer's approved domains, paths, IP ranges and testing window before running checks.
- Keep separate clients and unrelated targets in separate workspaces.
- Review the exact target and action whenever PENTER asks for an execution approval.
- A blocked redirect or out-of-scope destination is a safety boundary, not an error to work around.
What is available during the beta?
| Feature | Beta availability |
|---|---|
| Scoped Browser / HTTP / Request Lab | Supported for authorized target-facing investigations, subject to scope controls. |
| Managed Docker containers | Available only with network=none (offline). Images must already be present or be pulled with explicit approval. |
| Native shell and WSL/Kali commands | Disabled in packaged public-beta builds until destination enforcement is verified. |
| MCP process and tool execution | Disabled in packaged public-beta builds for the same reason. |
| Docker bridge networking / Compose up | Disabled in packaged public-beta builds. |
| Cloud command execution | Currently disabled server-side; this is separate from Cloud AI chat. |
Local Desktop work versus Cloud services
PENTER Desktop holds your engagement workspace and local Browser context. Cloud AI requests use PENTER's hosted service and selected model/provider. These are different trust boundaries: check the provider and workflow before sending customer information to a model.
For account data and personal information, review the Privacy Policy.
You control connected devices and tokens
- Approve Desktop authorization codes only when the code matches a request you made.
- Revoke an old or lost Desktop installation under Dashboard → Devices.
- Review and revoke any unused access tokens in your account dashboard.
- Use available multifactor authentication and keep recovery codes private.
When you need troubleshooting help
Ready to get started?
Follow the setup guide, install the current approved Desktop release, and connect your account.