Object-level authorisation
A user reaches an object that belongs to someone else.
home / services
service · API
REST, GraphQL and other endpoints. We verify who can read and change what, with which tokens and with which limits.
what it covers
A user reaches an object that belongs to someone else.
Reusable tokens, missing expiry, signatures not verified.
Responses with more fields than needed.
Fields the client should not be able to set.
Operations that can be repeated without limits.
Active paths that do not appear in the documentation.
how we work
If a specification is provided (for example OpenAPI), we use it as a map.
For each pair of roles, the plan proposes requests to compare.
Requests logged one by one, using test tokens.
A person verifies each vulnerability and assigns the severity.
Request, response, impact and fix for each vulnerability.
included and not included
service sheet
| Item | Detail |
|---|---|
| Type of test | Gray box with tokens for at least two roles |
| To start, we need | Specification or endpoint list, two roles, test environment |
| Delivery | Report, request log, role matrix |
| Price | from €2,000 to €4,000 |
We reply by hand with a written proposal.