Duty analyst on shift

UK Cyber Defence

Penetration testing · APIs · REST · GraphQL

Every operationis a front door.

REST, SOAP and GraphQL services tested for the weaknesses particular to APIs: who is allowed to call what, on whose data, and how often. We work from your OpenAPI definition or from captured traffic.

CREST-certified testers£950 + VAT a dayReport in five working daysRetest included

01What it answers

An interface hides what a user is not meant to do. An API has no such cover.

Every operation an API offers is an address that can be called directly, with any identifier the caller chooses. The commonest serious finding in API testing is also the simplest: an endpoint that checks the caller is signed in, but not that the record belongs to them. We test every endpoint in scope against the OWASP API Security Top 10, as each kind of client, and pay particular attention to authorisation at the level of the object and of the function.

Scope
Endpoints, methods and the authentication in front of them
Typical duration
One to five days of testing, plus one for reporting
Typical price
£1,900 to £5,700 + VAT
You provide
An OpenAPI or GraphQL schema where one exists, and credentials for each kind of client
Methods
OWASP API Security Top 10 · MITRE ATT&CK mapping

Coverage

What an API test looks at

01

Authentication

Tokens, keys and OAuth flows: how they are issued, scoped, expired and revoked.

02

Object-level authorisation

Whether changing an identifier in a request returns somebody else's record.

03

Function-level authorisation

Whether an ordinary client can call operations meant for administrators.

04

Data exposure

Responses that return more fields than the client needs, including ones no screen ever shows.

05

Rate and resource limits

Whether the API can be used to enumerate accounts, scrape data or exhaust the service.

06

Input handling

Injection, mass assignment and schema validation and, in GraphQL, query depth, batching and introspection.

Findings

What these tests usually find

  1. _01Broken object-level authorisationAny signed-in caller can fetch any record by guessing or incrementing its identifier.Most common
  2. _02Too much data in responsesThe interface shows three fields; the API returns thirty, including ones that were meant to stay internal.Exposure
  3. _03No limits on sensitive operationsSign-in, password reset and one-time codes that can be tried without restriction.Abuse
  4. _04Old versions still answeringA first version left running beside the third, without the fixes made since.Inventory

Cost

What it costs

Penetration testing is charged at one published rate, £950 + VAT a day, with one day added to every engagement for reporting, quality assurance and the debrief. The days follow the scope.

ScopeDaysPrice
10 endpoints1 testing + 1 reporting£1,900 + VAT
20 endpoints2 testing + 1 reporting£2,850 + VAT
60 endpoints3 testing + 1 reporting£3,800 + VAT
110 endpoints5 testing + 1 reporting£5,700 + VAT

These figures come from the estimator on the penetration testing page, where you can change the numbers and combine this test with others; one reporting day covers the whole engagement. A scoping call confirms the days and turns the estimate into a fixed price.

Questions

Questions about this test

How do you count endpoints?

An endpoint is one path and method, such as GET /orders/{id}. Ten are included in the first day and each further twenty-five adds a day. The scoping call confirms the count from your schema.

We have no documentation. Can you still test?

Yes. We can build the picture from captured traffic or from the application that uses the API. It takes a little longer and may miss endpoints the application never calls, so a schema is better where one exists.

Do you test third-party APIs that we consume?

Only with their owner's permission. What we can test is how your systems handle what a third party sends back, which is often where the risk lies.

Is GraphQL tested differently?

The questions are the same and the techniques differ: introspection, query depth and batching, and authorisation on each resolver instead of each path.

Start a conversation

Send us the schema.

A thirty-minute scoping call confirms the endpoint count, the client types and a fixed price.