Focused on identity and authorization: token handling, session lifecycle, and tenant boundaries — the layer most likely to fail silently in an API-first product.
What's included
alg=none downgrade, signature stripping, and other forgery techniques against real auth flows.
Cross-tenant access checks run against two live accounts on separate tenants.
Login rate limiting, session fixation, logout invalidation, and token expiry.
CORS policy review against origin-reflection and overly permissive configurations.
Why it matters
APIs often skip the defenses a browser-rendered web app gets for free — same-origin assumptions, visible navigation — and instead rely entirely on token validation and authorization logic holding up on every single call.
A missed tenant check in one endpoint is rarely one exposed page the way it might be in a traditional web app — it is usually every record belonging to every other tenant, which is why this assessment tests authorization boundaries with two real accounts rather than assuming the access-control logic is correct.
What to expect
Map every authenticated route and the token/session model behind it.
JWT forgery, session fixation, logout invalidation, and expiry checks.
Cross-tenant IDOR/BOLA checks with two live accounts, not just code review.
Findings ranked by data exposure risk, then a retest once fixes ship.
Tell us about your application or infrastructure and we will follow up with next steps.