Executive summary and scope
A fictional grey-box API test, not a completed customer engagement: one authenticated route, tested with two test users. A real report sets out everything in scope.
Method and reproduction
Sign in as customer-a. Request order-b07, which belongs to customer-b. Compare the returned owner with the authenticated account.
GET /api/orders/order-b07
Authenticated account: customer-a
HTTP/1.1 200 OK
{ "id": "order-b07", "ownerId": "customer-b" }
Impact and severity rationale
One customer can read another customer's order: unauthorized disclosure. Changing or deleting the order was not shown. High assumes the order data is sensitive; a real report gives the severity method and business context behind each rating.
Remediation and protection
Bind the lookup to the signed-in owner and review the intended shared-team access policy. Defend can log this request but not block it, because a rule cannot see sessions or the database to decide who owns an order.
Illustrative verification record
Patched staging, Defend off: cross-customer access returns 404, the legitimate owner returns 200, and a signed-out request returns 401. Shared-team access still needs a policy decision. Sample results.
Review and delivery
A named consultant approves every Assess finding before delivery. Your engagement sets the authorization, targets, method, access, exclusions, delivery date and retest terms. The report supports your audit; acceptance is your auditor's decision.