← Integration Engineering
Integration Engineering

One Customer’s Data Must Never Show Up for Another

16 Oct 2026·3 min read

The scariest integration bug is not a crash. It is customer A opening your app and seeing customer B’s employees. Nothing breaks, and nobody gets an error.

When one product serves many companies, each company is a tenant and connects its own accounts. This is multi-tenancy. The provider only knows the one account it gave a token to, so keeping tenants apart is yours to do.

Rules worth never breaking

  • Every API call names exactly one customer’s connected account. Never "the HR account". Always "this customer’s HR account".
  • The customer ID comes from your own server session, never from a value the browser sends. Otherwise a user can change 42 to 43 and see someone else’s data. OWASP puts this at number one in its API security list.
  • Customers that need a different region or environment get their own separate setup, with its own keys and storage.

A test that tries to cross the line

Normal use will not show this bug. So create two test customers, log in as A, and call every endpoint with B’s IDs. Every call must fail. OWASP gives the same advice: do not deploy changes that make these tests fail.

Why the business side cares"How do you keep our data apart from your other customers?" is often the first security question a buyer asks. A clear answer helps close the deal.
Do this in 60 secondsSearch your server code for a tenant or account ID read from the request body or query string. Does the code check it against the logged-in user first? Any "no" is your first ticket.
Today’s AI angleAn AI agent’s tool arguments are client input too. A clever prompt can ask it to pass someone else’s account ID. The server decides which customer the agent works for, from the session.
One Customer’s Data Must Never Show Up for Another · Ali Huzaifa