Web application and API penetration testing

Most breaches of modern apps come through the app itself: a missing access check, a predictable ID, an API that trusts its client. Swarm Computers tests for these on every build.

Security testing runs as a preset of the Swarm Computers Swarm API.

What we test

AreaExamples
Access controlIDOR, horizontal and vertical privilege escalation, missing checks on admin routes
AuthenticationPassword reset flaws, session fixation, token reuse, MFA bypass
InjectionSQL, NoSQL, command, template injection; stored and reflected XSS
APIsREST and GraphQL authorization, mass assignment, excessive data exposure, rate limits
Server-sideSSRF, path traversal, unsafe file upload, deserialization
Business logicSkipping steps, negative quantities, race conditions on balances

Coverage maps to the OWASP Top 10 and OWASP API Security Top 10, but the agents are not limited to a checklist.

How a test runs

  1. 01

    Give it a build and accounts

    Point Swarm Computers at a container image or a sandbox URL, plus test accounts for each role. An OpenAPI or GraphQL schema helps but is optional.

  2. 02

    Map the app

    Agents crawl the UI and API, learn the roles and the objects each one can see.

  3. 03

    Attack and verify

    Agents try to cross every boundary they find, and keep only the attempts they can reproduce.

  4. 04

    Fix

    Each finding comes with the exact request, the impact and a suggested code-level fix.

Questions

Do you test single-page apps?
Yes. Agents work against the API the front end calls as well as the pages themselves, so client-side routing and token-based auth are not a barrier.
Can you test an API with no UI?
Yes. Give us the base URL and, ideally, a schema. Agents will discover endpoints from the schema, from traffic and by probing.
Do you test our cloud infrastructure?
Not today. Swarm Computers focuses on the application and API layer, which is where most custom code and most custom bugs live.

Related

Test your next build in a sandbox.