API Security
APIs are the backbone of modern apps. We test for broken authorization and data exposure.
Who this is for
Engineering and security teams preparing for a release, a customer security review, or a procurement questionnaire — and anyone who needs to know what an attacker could actually reach.
Methodology
What We Test
- REST, GraphQL, and gRPC endpoints
- Broken Object Level Authorization (BOLA/IDOR)
- Broken Function Level Authorization (BFLA)
- Rate limiting and resource quotas
- JWT/OAuth/OIDC implementation flaws
- Mass assignment and excessive data exposure
How We Test
We manually map business logic to find authorization gaps automated scanners miss. We check object-level authorisation (BOLA) using approved test accounts and seeded test records, retrieving only what is needed to prove the gap. We test token validity, scoping, and refresh flows. We fuzz inputs for injection and logic errors specific to your API schema.
What You Receive
- Postman/Curl collections to reproduce exploits
- Code-level remediation for authorization logic
- Gateway and WAF configuration tuning
- Impact analysis on user data and privacy
How an engagement runs
-
Scope & authorisation
We agree exactly what is in scope, what is explicitly out, and the conditions under which we stop. Nothing starts without written authorisation from someone able to give it. NDA first if you want one.
-
Access & prerequisites
We tell you up front what we need — test accounts at each privilege level, a non-production environment where that applies, documentation, and a named technical contact. Missing prerequisites are the usual reason assessments slip.
-
Reconnaissance & threat modelling
We map the real attack surface and decide which paths are worth the time, based on how your system is actually built rather than a generic checklist.
-
Manual testing & validated exploitation
Testing is hands-on. Findings are reproduced before they are written up, so you are not sent unverified scanner output. Critical issues are raised as soon as we confirm them rather than held for the report.
-
Report & walkthrough
You get an executive summary your board can read and technical detail your engineers can act on — including reproduction steps, what we tested that held, and what was out of scope. We walk your team through it.
-
Retest
Once you have fixed the findings we retest them and confirm in writing what is closed. Retest scope and window are agreed in your scope document before the engagement begins.
Toolkit
- Postman
- Burp Suite
- Kiterunner
- Arjun