Vulnerability Assessment · Service
API security assessment.
Your API is the part of your product that mobile apps, partners and your own front end talk to. We check that it only gives each caller what they are entitled to.
Overview
What this covers
APIs are often the most exposed part of a modern product. They sit behind web front ends, mobile apps and partner integrations, and they are designed to be called directly by software. That makes them easy to explore for anyone who looks, and it means the checks a user interface performs count for nothing if the API itself does not enforce them.
The most common API weaknesses are about authorisation rather than clever technical tricks: an endpoint that returns another customer's record when given their ID, a response that includes fields the front end never displays, or an action that ordinary users can call even though only administrators see the button. We test for these systematically, using the OWASP API Security Top 10 as our reference.
We cover REST and GraphQL APIs, including the authentication method, how errors are returned, how much data each endpoint exposes, and whether limits on request volume are in place. You receive a report your developers can work through endpoint by endpoint.
Deliverables
What you get
Endpoint inventory
A list of the endpoints and operations we tested, which is often useful in its own right for teams whose API documentation has fallen behind.
Findings report
Every issue rated by severity, with the request and response evidence that shows it and the steps to reproduce it.
Authorisation matrix notes
Where relevant, a summary of which roles could reach which operations, highlighting any that did not match your intended rules.
Fix guidance
Specific remediation advice for each finding, written for the developers who maintain the API.
Retest and confirmation
We retest the issues you fix and confirm in writing which are closed.
Approach
How we run it
- 01
Agree the scope
We confirm which APIs, versions and environments are in scope, and which roles and test accounts we will use.
- 02
Build the picture
From your documentation, schema or the traffic of your own apps, we list the endpoints and what each is meant to allow.
- 03
Test
We check authentication, authorisation between users and roles, data exposure, input handling and request limits.
- 04
Report and walk through
Findings are written up per endpoint, rated and explained to your developers.
- 05
Retest
We check the fixes and confirm the outcome in writing.
Questions
Before you ask.
Do we need API documentation?
It helps a great deal. An OpenAPI specification, a GraphQL schema or a collection of example requests lets us cover the API completely. If documentation is incomplete, we can work from the traffic your own apps generate.
Can you test an API that is only used by our mobile app?
Yes. The API is tested directly, so it does not matter which client normally calls it. We will need test accounts and, ideally, a non-production environment.
Will testing affect our rate limits or other customers?
We agree request volumes and testing windows in the scope. Checking whether rate limits work is done carefully and at a scale agreed with you.
How is the work priced?
Price and timeline depend mainly on the number of endpoints and roles. Both are agreed in the scope and quote before testing starts.
Related
Often paired with
Talk to us about apis
Tell us what you want tested. We will reply with a proposed scope, the authorisation we need, and a quote.
