Cyber security · 02

API security testing for the endpoints behind everything.

Your mobile app, front end and partners all talk to the same API. We test REST and GraphQL endpoints against the OWASP API Security Top 10, one object and one role at a time.

Overview

Change one ID in the request. If you get someone else's data back, that is the finding.

Broken object-level authorisation is the most common serious issue we see in APIs, and no scanner reliably finds it. We test every object type against every role.

We also look at what the API gives away: fields the front end never shows, verbose errors, undocumented endpoints and versions that were never switched off.

Standards & frameworks

  • OWASP API Top 10
  • OWASP WSTG
  • CREST-aligned
  • CVSS 3.1
  • OpenAPI

What we test

What's in scope.
And what we look for.

01 · Authorisation

Object and function level. The heart of API security.

  • Object-level access (BOLA)

    Can a user read or change objects that belong to someone else?

  • Function-level access

    Can a normal user call admin or internal operations?

  • Property-level access

    Mass assignment and fields users should never be able to set.

  • Tenant isolation

    Cross-tenant access in multi-customer platforms.

02 · Authentication

Tokens and sessions. How identity is proven on every call.

  • Tokens

    JWT validation, signing, expiry, revocation and refresh flows.

  • OAuth and keys

    Scopes, client credentials and API keys exposed in apps.

  • Rate limiting

    Brute force, enumeration and resource exhaustion.

  • Webhooks

    Signature checks and replay protection on inbound callbacks.

03 · Exposure

What leaks out. Data the API shares without being asked.

  • Excessive data

    Responses that return more than the client needs.

  • GraphQL

    Introspection, query depth, batching and field-level auth.

  • Inventory

    Old versions, shadow endpoints and debug routes.

  • Injection

    SQL, NoSQL and server-side request forgery through API parameters.

Process

How a test runs, start to finish.

  1. 1

    Scope

    Endpoints, environments and roles agreed. An OpenAPI spec or Postman collection helps.

  2. 2

    Map

    We build a full inventory, including endpoints your docs do not mention.

  3. 3

    Attack

    Each object and operation tested per role, with impact proven safely.

  4. 4

    Report & retest

    Findings with requests, responses and fixes, then a retest.

Deliverables

What ships with
every test.

One report for two audiences: leadership gets the risk, engineers get the evidence and the fix. Here is how that compares with an automated scan.

Read the sample report →
DeliverableYUPL testAutomated scan
Executive summaryPlain-English risk overview for leadership, boards and auditors.YesBasic
Technical findingsEvery issue with a CVSS score, affected assets and business impact.YesYes
Evidence and reproduction stepsRequests, screenshots and steps so your engineers can confirm each finding.Yes—Not included
Chained and business-logic issuesLow-severity issues combined into real attack paths, and flaws a tool cannot understand.Yes—Not included
Remediation advice for your stackSpecific fixes for your framework and infrastructure, prioritised by risk.YesGeneric
Walkthrough callWe take your technical and business teams through the findings.Yes—Not included
Retest and reissued reportWe verify the fixes and reissue the report showing what is closed.Yes—Not included

“Thank you for protecting MOD's systems and keeping us secure.”

Ministry of DefenceA thank-you to the YUPL team

FAQ

Questions

About api security testing. Anything else, call us.

It helps but is not required. An OpenAPI spec or Postman collection speeds things up; without one we map the API from your apps and traffic.

Yes, including introspection, query cost and depth, batching attacks and resolver-level authorisation.

Yes. MCP servers are APIs with extra trust problems. See our MCP server security checklist for what we look at.

The API behind a web app is covered in a web application test. Public, partner and mobile APIs are usually scoped as their own test.

Scope your api security testing.
Get a fixed quote.

A developer or security engineer reads every enquiry and replies, not a salesperson.

  • Fixed quote after a short scoping call
  • NDA available before you share details
  • Remediation and retest on every security engagement

Domains are fine as plain text (app.example.co.uk).

We only use your details to reply to this enquiry. See our privacy policy.