Recon
Map every endpoint, every framework, every footgun. Manual scanners run a fixed signature set. The swarm runs against your actual surface.
Cross-tenant isolation tested on every ID parameter. Identity-provider coverage across Clerk, Auth0, Okta, Stytch, Cognito, Firebase, and Supabase. The full audit trail your SOC 2 Type 2 auditor reads before they open the report.
The engagement
Map every endpoint, every framework, every footgun. Manual scanners run a fixed signature set. The swarm runs against your actual surface.
Specialists own classes of attack. Auth flaws. Access control. Injection. Logic. Each agent probes its vector and cites the request that proved it.
Verified PoC for every Critical and High. Multi-step chains are first-class. The chain analyst composes findings into one exploit path.
Markdown narrative. Full audit trail. JSON for tooling. Your auditor reads the action that matches the verdict.
The differentiator
Every tool call. Every request. Every grep. Every submit. Every verify. Streams to the dashboard live and ships with the report. Your SOC 2 reviewer doesn't have to take our word for it. They open action 1,847 and read what we did.
The price
No per-target pricing. No per-finding pricing. No "starts from". One engagement, one fee, one audit trail.
Questions
The questions every engineering and security lead asks before they fund an engagement. Read the answers here, before the kickoff call.
SaaS penetration testing focuses on the attack surfaces specific to multi-tenant web applications: cross-tenant isolation, identity provider integration, API security boundary, and the audit deliverable that satisfies SOC 2 Type 2 reviewers.
Multi-tenant specialists probe every ID parameter for cross-account access, validate org-scoping on every API call, and test session-token reuse across tenants. Findings include the IDOR-class bugs traditional pentests miss because they sample rather than enumerate.
Clerk, Auth0, Okta, Stytch, Cognito, Firebase, Supabase Auth, and custom IDPs. Specialists describe the mechanic first; stack-specific paths and library names appear as illustrative anchors. JWT-alg bugs, missing org-scope checks, and session-fixation paths are covered across providers.
Yes. The full audit trail is downloadable from the dashboard and is the canonical evidence artifact for your SOC 2 review. A dedicated read-only Auditor Clerk role gives your external compliance professional dashboard access without engineering credentials.
Full coverage on 9 of 10 categories: BOLA, broken authentication, object property-level auth, resource consumption, BFLA, sensitive business flow abuse, SSRF, security misconfiguration, unsafe API consumption. Improper Inventory is partial. See /owasp-coverage for the per-category breakdown.
BOLA (Broken Object-Level Authorization) is the API equivalent of IDOR. Every ID parameter in your API is tested for cross-account access. Swarm enumerates ID-bearing endpoints from the OpenAPI / dashboard inspection and probes each with attacker credentials.
A Swarm engagement is designed to satisfy SOC 2 Type 2 Trust Services Criteria CC4 (Monitoring) and CC7 (System Operations). The full audit trail is your evidence artifact; the structured report is your finding documentation. See /compliance for the full mapping.
Yes. Swarm is offered as PTaaS: recurring engagements triggered per release cycle, with a shared findings history and a free retest within 30 days of remediation baked in. This replaces the traditional human retainer for teams running continuous-deployment pipelines.
The free attack-surface preview returns in a few minutes. The full engagement run completes the same day. Compare against the two-to-four-week timeline of a human firm pen test.