Skip to content
ISO 27001, SOC 2, the DPDP Act and manual VAPT.
Part of VAPT7 services in this practice area

Authz, Authn and Business Logic

API Penetration Testing

APIs fail on authorization and logic far more than on classic bugs. We go straight for broken object-level access, weak authentication and abusable workflows, the flaws that leak other people's data.

See the engagement path, 6 phasesSee the full VAPT service index

Overview

An API VAPT tests the endpoints that power your apps, partners and integrations. We focus on the things the OWASP API Security Top 10 keeps proving matter most: who can access which object, whether authentication actually holds, and whether your business logic can be walked around. We test REST, GraphQL and SOAP, with a real eye on multi-tenant data separation.

Methodology

How the Engagement Runs

Every phase has a named output, so you always know what is being worked on and what lands on your side of the table.

The Engagement, End to End

6 Phases, 6 Named Handovers

Flow

Flow chart of the API engagement, 6 phases in order, each one selectable. Phase 1, Scoping and Rules of Engagement. We collect the API definition, roles and test accounts, agree rate limits and windows, and confirm which environments are in scope. Activities: Collect the API definition and docs; Provision accounts across roles and tenants; Agree rate limits and testing windows; Confirm in-scope environments. Hands over Signed Rules of Engagement. Phase 2, Reconnaissance and Mapping. We enumerate endpoints, methods and parameters from documentation and traffic, and map the roles and objects each one touches. Activities: Enumerate endpoints, methods and parameters; Capture traffic from real client flows; Map roles and objects per endpoint; Note authentication schemes in use. Hands over Endpoint and Object Map. Phase 3, Authentication and Authorization Testing. We test token handling and attack object- and function-level access, chasing BOLA, BFLA and privilege escalation across tenants. Activities: Test token issuance and validation; Attack object-level access for BOLA; Attack function-level access for BFLA; Attempt cross-tenant privilege escalation. Hands over Authorization Findings. Phase 4, Business Logic and Injection. We abuse workflows, mass assignment and input handling, checking whether sequences of valid requests produce invalid outcomes. Activities: Abuse multi-step workflows out of order; Test mass assignment on writable objects; Probe input handling for injection; Chain valid requests into invalid outcomes. Hands over Business-Logic and Injection Findings. Phase 5, Manual Exploitation and Impact. We prove each finding and show what it exposes, especially where one account can reach another tenant's data. Activities: Reproduce each finding with clean requests; Demonstrate cross-tenant data access; Map the data each flaw exposes; Rank findings by real impact. Hands over Impact and Risk Assessment. Phase 6, Reporting and Verified Retest. You get a report with reproducible requests and clear fixes, and we retest once remediation lands to confirm closure. Activities: Document findings with reproducible requests; Produce an executive summary; Walk your team through the results; Retest fixes and confirm closure. Hands over Final Report and Verified Retest. Each phase begins from the artefact the phase before it produced.

Phase 01 Scoping and Rules of Engagement

We collect the API definition, roles and test accounts, agree rate limits and windows, and confirm which environments are in scope.

What Happens In This Phase

  • Collect the API definition and docs
  • Provision accounts across roles and tenants
  • Agree rate limits and testing windows
  • Confirm in-scope environments

The Handover

Signed Rules of Engagement

The next phase starts from this.

Read the handover cards on their own and you have the paper trail. Select a phase to see what happens inside it.
  1. 01

    Scoping and Rules of Engagement

    We collect the API definition, roles and test accounts, agree rate limits and windows, and confirm which environments are in scope.

    OutputSigned Rules of Engagement

    Activities

    • Collect the API definition and docs
    • Provision accounts across roles and tenants
    • Agree rate limits and testing windows
    • Confirm in-scope environments
  2. 02

    Reconnaissance and Mapping

    We enumerate endpoints, methods and parameters from documentation and traffic, and map the roles and objects each one touches.

    OutputEndpoint and Object Map

    Activities

    • Enumerate endpoints, methods and parameters
    • Capture traffic from real client flows
    • Map roles and objects per endpoint
    • Note authentication schemes in use
  3. 03

    Authentication and Authorization Testing

    We test token handling and attack object- and function-level access, chasing BOLA, BFLA and privilege escalation across tenants.

    OutputAuthorization Findings

    Activities

    • Test token issuance and validation
    • Attack object-level access for BOLA
    • Attack function-level access for BFLA
    • Attempt cross-tenant privilege escalation
  4. 04

    Business Logic and Injection

    We abuse workflows, mass assignment and input handling, checking whether sequences of valid requests produce invalid outcomes.

    OutputBusiness-Logic and Injection Findings

    Activities

    • Abuse multi-step workflows out of order
    • Test mass assignment on writable objects
    • Probe input handling for injection
    • Chain valid requests into invalid outcomes
  5. 05

    Manual Exploitation and Impact

    We prove each finding and show what it exposes, especially where one account can reach another tenant's data.

    OutputImpact and Risk Assessment

    Activities

    • Reproduce each finding with clean requests
    • Demonstrate cross-tenant data access
    • Map the data each flaw exposes
    • Rank findings by real impact
  6. 06

    Reporting and Verified Retest

    You get a report with reproducible requests and clear fixes, and we retest once remediation lands to confirm closure.

    OutputFinal Report and Verified Retest

    Activities

    • Document findings with reproducible requests
    • Produce an executive summary
    • Walk your team through the results
    • Retest fixes and confirm closure

Specification

What We Run, and What We Measure You Against

The tooling our engineers use on this work, and the published standards the findings and evidence are mapped to.

Scope

What Is Examined, and What it Is Measured Against

Map

Map of the API scope, running left to right in three stages. Stage one, what we run, 8 tools and techniques: Burp Suite Professional, Postman, Nuclei, ffuf, mitmproxy, kiterunner, GraphQL Voyager, jwt_tool. Stage two, findings from all of it are proven by hand and written up once. Stage three, measured against 5 published standards: OWASP API Security Top 10, OWASP Web Security Testing Guide (WSTG), PTES, NIST SP 800-115, CVSS v4.0.

What We Run

8 tools

  • Burp Suite Professional
  • Postman
  • Nuclei
  • ffuf
  • mitmproxy
  • kiterunner
  • GraphQL Voyager
  • jwt_tool

Converges On

One Set of Proven Findings

Every issue is reproduced by hand before it is written down, and it is written down once.

Measured Against

5 standards

  • OWASPAPI Top 10
  • OWASPWSTG
  • PTES
  • NIST SP 800-115
  • CVSS v4.0
One pass of testing and analysis, one set of findings, then that single set is graded against every standard on the right. You are not paying for the same work once per framework.

Deliverables

What You Receive

  • Findings report with reproducible requests
  • Executive summary
  • Remediation guidance
  • Verified retest report
  • Attestation letter

Scope This Engagement

Tell us about your environment, your timelines and any audit dates you are working to. We come back with scope, effort and a start date.

Questions

What Clients Ask Us

Something here not covered? Ask Us Directly.

Do you need an OpenAPI or GraphQL schema?

It helps a great deal and speeds things up, but we can also work from captured traffic and documentation. The more complete the definition, the more thoroughly we can cover every endpoint.

Can you test multi-tenant data separation?

Yes, and we push hard on it. With accounts in two or more tenants we test whether one can read or change another's data, which is where object-level authorization usually breaks.

Do you test GraphQL and SOAP as well as REST?

Yes. Each has its own pitfalls, from GraphQL introspection and nested queries to SOAP parsing and WSDL exposure, and we test for the ones that apply to your API.

Keep Moving Through VAPT

Service 3 of 7 in this practice area