PenterDocumentationYour work. Your boundaries.
Safety & privacy

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.

01 · Scope

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.
02 · Public beta

What is available during the beta?

FeatureBeta availability
Scoped Browser / HTTP / Request LabSupported for authorized target-facing investigations, subject to scope controls.
Managed Docker containersAvailable only with network=none (offline). Images must already be present or be pulled with explicit approval.
Native shell and WSL/Kali commandsDisabled in packaged public-beta builds until destination enforcement is verified.
MCP process and tool executionDisabled in packaged public-beta builds for the same reason.
Docker bridge networking / Compose upDisabled in packaged public-beta builds.
Cloud command executionCurrently disabled server-side; this is separate from Cloud AI chat.
Please don't disable safeguards to make a blocked feature run
A development build, different execution path or unapproved container is not a safe workaround. The public beta intentionally exposes a narrower set of capabilities while security verification continues.
03 · Data

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.

Keep customer evidence within the right engagement
Save findings, browser state and notes to the intended workspace. Do not move screenshots, cookies, access tokens or private reports between unrelated engagements.

For account data and personal information, review the Privacy Policy.

04 · Access

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.
05 · Help

When you need troubleshooting help

What should I send when reporting an error?
Your Desktop version, Windows version, relevant feature, and the exact error code. Remove customer names, secret keys, tokens, browser cookies and private network details from logs.
Can PENTER test any reachable website?
No. Only test systems you are explicitly authorized to assess. A network connection or an apparently accepted target does not grant permission.
Why does PENTER refuse some commands?
The public beta blocks tool execution paths that cannot yet guarantee target-bound network access. Use the supported scoped Browser/HTTP tools instead of attempting a bypass.
Next step

Ready to get started?

Follow the setup guide, install the current approved Desktop release, and connect your account.