Azacus.io / Services

Standalone API penetration testing

Your API may serve mobile users, partners or internal services with different access to the same data. We test whether those callers can read or change only what they’re entitled to.

Discuss your API

What we test

Authentication, access to records and functions, sensitive data in responses, and the business rules behind operations such as approvals, exports or updates. We include relevant API versions and integrations within the agreed scope.

We consider the relationship between an operation, the identity calling it and the record it affects. That includes service accounts and partner integrations as well as end users. Where supported by the agreed scope, we examine whether restrictions continue to hold through exports, queued tasks and changes of state.

How we test

We review the operations your API exposes and identify the roles and workflows that matter. Where an operation continues in a background job or another service, we assess its result within scope.

We build a picture of the intended permissions using your documentation and a walkthrough. Testing then compares those rules with the behaviour of the API using representative callers. Unexpected responses are investigated in context, including the final outcome of an operation when it is processed asynchronously.

What you receive

Findings that identify the affected API operation, the access needed, the observed result, the impact and a recommended fix. The coverage section records which operations and roles were assessed.

Engineers receive the request context and evidence needed to understand each issue, together with guidance on the control that should enforce the rule. We identify relevant versions and endpoints so that fixes and regression checks can be applied across the affected surface.

What we need from you

The API’s purpose, environments and main callers. API documentation or an existing collection helps us scope the work. We’ll confirm the accounts and test data after the walkthrough.

Useful starting material includes an OpenAPI specification, a Postman collection or equivalent documentation. Tell us about integrations, rate limits and operations with external consequences. We confirm how to exercise those workflows and which test records can be used before testing starts.