Authorised call
User 14 reads invoice 14. The server checks both the token and the owner.
Most of the serious findings we ship are not on the marketing site. They are one changed identifier in a JSON call. This guide is how we trace that path.
Aligned with the OWASP API risks your security questionnaire already names, described the way we test them.
Every id in the path or body is swapped for another tenant’s id. If the JSON comes back, it is a finding.
Tokens that survive logout, reset links that do not expire, and API keys sitting in a mobile build.
A profile update that also accepts role or isAdmin because the server binds every field.
Password guesses, OTP retries, and expensive endpoints with no limit. We measure what one account can do in a minute.
Admin methods called with a normal user token. The UI never showed the button. The route still exists.
Verbose errors, CORS that reflects any origin with credentials, and debug routes left on in production.
API findings in a Sumrite report include the exact call, the data that should not have returned, and the check your engineers should add. Retest is included before the report.
Scope an API test