For SaaS and API-first teams opening an API to customers or partners, shipping a mobile backend, or answering a customer security questionnaire.
Before exposing an API to customers, partners or a mobile app.
What we examine
- Agree the API, its documentation or OpenAPI specification, environments, roles and test accounts.
- Test authentication, object-level and function-level authorization, mass assignment, rate limiting and input handling against the OWASP API Security Top 10.
- Validate attack paths and their business impact within the agreed scope.
How I test
Manual-first testing against the OWASP API Security Top 10, focused on authorization and data ownership. Every finding is confirmed before it is reported.
How an engagement runs
Send a short brief
The product, what changed, what you need to know and by when. A paragraph is enough, and I reply within three days.
Get a written proposal
Scope, method, exclusions, deliverables, price and dates. Confidentiality, NDA and retesting terms are agreed in the same proposal.
Follow the work as it develops
For assessments, you see evidence and priorities as they emerge. For engineering, you review the agreed milestones.
Report and walkthrough
You receive the report or the delivered work and a walkthrough with your team. Any further fixes or verification are agreed with you.
Security vulnerabilities I have reported
I have reported 150+ security vulnerabilities, including seven in Facebook and Instagram that Meta validated and acknowledged. Your application gets the same attacker’s view: authentication, permissions and the business logic between them.
See the track recordQuestions before we begin
Do you need an OpenAPI specification?
It helps but is not required. A collection of example requests, account roles and access to a test environment are enough to start; missing documentation is noted in the scope.
Can you test GraphQL?
Yes. Queries, mutations, field-level authorization and introspection settings are agreed in scope like REST endpoints.
Is this the same as running an API scanner?
No. Scanners check known patterns. Most serious API flaws are authorization and business-logic errors that need a tester to reason about roles and data ownership.
How quickly will you reply?
Within three days at most. You get questions about your product or an outline of the proposal.
What does it cost?
Published prices are starting points. The final price depends on scope and technical complexity and is fixed in the written proposal before work starts.
How long does it take, and when can you start?
Duration and start date depend on the scope, the technical complexity and my current workload. The proposal states the dates.
Can we work under an NDA?
Yes. Confidentiality terms, including an NDA if you need one, are agreed as part of the proposal before you share code, credentials or findings.
Is a retest included?
Retesting is agreed for each engagement in the proposal: which findings, which version and the time window.
Do you work with agencies?
Yes. Agencies can bring me in for a client’s project. Delivery terms, including white-label reports, are agreed case by case in the proposal.
Related reading
- fast-jwt algorithm confusion: fixed on the third try
- PHP2Shell: CVE-2026-109618 and the Runtime Boundary
- Lovable and Supabase security checklist: what to check before launch