Illustrative walkthrough. This is not a customer engagement. It is a composite scenario written to show how a TrekShield engagement works. The company, systems and details are invented, and no results are claimed.

Illustrative walkthrough · Web Application & API

Assessing tenant isolation in a SaaS export workflow

At a glance

Type
Illustrative walkthrough (not a customer engagement)
Scenario
A multi-tenant B2B SaaS platform adding a bulk-export feature
Services
Web Application & API
Engagement model
Pre-release test of a new feature
What it demonstrates
Authorization testing, remediation and verification approach

Organization context

This walkthrough models a multi-tenant B2B SaaS application introducing a bulk-export feature. Customers should be able to export their own records without accessing another tenant’s data.

Business and security challenge

The team needs to evaluate tenant isolation before relying on the export workflow. Passing automated checks is not enough to establish that each object is authorized for the requesting tenant.

Scope and environment

The example scope is the export endpoint and its supporting API calls in staging. Two test tenants provide controlled accounts and records. Production customer data and denial-of-service activity are outside the scenario.

Testing methodology

Compare authorized export requests with requests referencing records from the other test tenant. Examine object references in paths, parameters and request bodies, including batched requests. Preserve the request context needed for a developer to reproduce the result without exposing real customer data.

Significant finding

The modeled flaw is a missing object-ownership check: an authenticated user can request records outside their tenant. Authentication alone does not authorize access to every referenced object. The finding is described as broken object-level authorization, with impact and severity assessed from the access and data demonstrated—not an assumed universal score.

Remediation and collaboration

The proposed fix derives tenant context from the authenticated session and enforces ownership in a shared authorization layer. Developers add tests for both permitted access and cross-tenant denial. Non-sequential identifiers can make guessing harder but do not replace authorization.

Verification approach and practical lesson

A retest would replay the original request and its path, body and batch variants. Verification requires cross-tenant requests to be refused while legitimate same-tenant exports still work. Record the result and remaining limitations alongside the original finding; this walkthrough does not claim a measured customer outcome.

The practical lesson is to test the relationship between the requester, tenant and object—not merely whether the requester is logged in.

See what a report looks like.

A short scoping call, no obligation.