Servana

Application security

API security testing

We test the APIs behind your apps and integrations for broken authorisation, data exposure and abuse, with the OWASP API Security Top 10 as a baseline.

Who it's for.

Who it's for

  • Companies whose product is, or depends on, an API
  • Teams with mobile apps or integrations that talk to a backend API
  • Businesses sharing data with partners through an API

What we test.

What we test

  • Object-level authorisation

    Whether changing an ID lets one customer reach another's data: the most common API flaw.

  • Authentication

    Tokens and keys: how they're issued, checked and expired.

  • Data exposure

    Responses that return more than the app actually shows, or let users change fields they shouldn't.

  • Function-level access

    Admin and internal endpoints that ordinary users can reach.

  • Rate limiting and abuse

    Whether someone can flood, scrape or brute-force your API.

  • REST and GraphQL

    Both, including introspection and query abuse for GraphQL.

What you get.

Included with every engagement

  1. 01

    Scope and rules of engagement

    What's in scope, when we test and how, agreed in writing before we start.

  2. 02

    Executive summary

    What we found and what it means for the business, in plain English.

  3. 03

    Technical findings

    Each issue with its severity, evidence and steps to reproduce it.

  4. 04

    Remediation guidance

    Practical fixes, in order of priority, that your team can act on.

  5. 05

    Debrief

    A walkthrough of the findings with the people who'll fix them.

  6. 06

    Retest

    Confirmation that what you fixed is actually closed.

From first call to fixed.

How it works

  1. 01

    Scoping call

    We learn what you want tested, why, and by when.

  2. 02

    Quote and authorisation

    A fixed quote, the exact scope and the rules of engagement, signed off in writing before we touch anything.

  3. 03

    Testing

    We test within the agreed window, and tell you straight away if we find something critical.

  4. 04

    Report

    A plain-English summary for leadership, and technical detail and fixes for your team. Every finding ranked by risk.

  5. 05

    Debrief

    We walk the people fixing things through the findings and answer their questions.

  6. 06

    Retest

    Once you've fixed the findings, we test again to confirm they're closed.

Frequently asked questions.

FAQ

What do you need from us?

Documentation if you have it (an OpenAPI file or a Postman collection helps), test credentials for each role, and an environment we can test.

Do you test GraphQL?

Yes. GraphQL has its own weak spots, like introspection left on and queries that can be nested or batched to overload the server, and we test for those alongside the usual API flaws.

Is this part of web application testing?

Often the two go together, since most web apps run on an API. If you need both, we scope them as one engagement.

Do you need our permission to test?

Always, in writing. We only test systems you own or are authorised to have tested, and the scope is signed off before we start. In South Africa, testing a system without permission is a crime under the Cybercrimes Act, and we won't do it.

How much does it cost?

You get a fixed quote after the scoping call, based on what's in scope. No hourly billing.

Find the gaps before someone else does.

Tell us what you'd like tested and when you need the report. You'll get a clear scope and a fixed quote.