Skip to content

Pentest checklist

An external penetration test is recommended before selling to enterprise customers and has not been done. This page is what to hand the testers and what to ask them to look at beyond the local gates (see Security gates).

Scope to give

  • API: openapi/openapi.json (every operation, tenant-scoped API keys and OIDC sessions).
  • The Studio (web) and the document viewer.
  • The Code node sandbox (Pyodide on Deno) and, in production, its container profile (gVisor).
  • The worker, the exports (CSV, XLSX) and the webhooks.
  • Out of scope unless agreed: the identity provider, the cloud account, third-party model APIs.

What the local gates do not cover

Area Why a person is needed
Tenant isolation under load and after failover the RLS and API-leak gates run on one database, one connection pool
SSO (OIDC, SAML broker) with a hostile IdP only the discovery of the issuer is guarded (SEC-004); SEC-006 (http://localhost issuer) is open
Business logic of review and approval change-set approval, review decisions, role changes
Sandbox with the container profile the escape battery ran on the deno profile only
Prompt injection with a real model the obedient model proves the structure, not a model's resistance
Supply chain pip-audit, pnpm audit, gitleaks and bandit were not run in T55
Rate limits and abuse of quota the load and chaos suites were not run

Questions to ask the testers

  1. Can a member of tenant B read, change or infer the existence of anything of tenant A?
  2. Can a document make the model write a value that looks verified (SEC-005, SEC-007, SEC-008)?
  3. Can the user's code in a transform node reach the network, the host files or its environment?
  4. Can an export be opened in a spreadsheet and run a formula?
  5. Can a webhook or SSO URL reach a private address?
  6. Can an agent (builder or MCP) apply a change without a person's approval?