Tenant isolation
I test whether an authenticated user can cross the boundary between separate customer accounts.
INDEPENDENT SECURITY RESEARCH · UNITED KINGDOM
I use GreySurface for my independent security research practice, focused on authentication, authorisation, API access control, and tenant isolation in B2B software.
Disclosure record
GS-REFERENCE
Tenant A
Tenant B
Boundary under validation
Research activity
I keep public figures deliberately narrow. Report details, vendor names, and evidence stay private unless publication is appropriate.
3,323
Vulnerabilities identified
849
Reports sent
I provide the report without a fee or payment condition. I test from accounts I control, stop after the minimum proof needed to establish the issue, minimise incidental data, and cooperate with remediation.
I test whether an authenticated user can cross the boundary between separate customer accounts.
I check whether access decisions are applied to the individual record requested, not only to the route or session.
I review registration, activation, invitation, session, recovery, and account-state boundaries.
I compare intended product permissions with the behaviour of authenticated API endpoints.
01
I establish access using an account or trial environment I control.
02
I use the minimum read-only proof needed to establish whether a security boundary has failed.
03
I do not bulk enumerate records or test state-changing actions against data outside my account.
04
I contact the vendor directly with an impact summary, reproducible evidence, and remediation context.
05
I remain available to clarify the report and validate the fix.
I provide a vulnerability report so the vendor can assess and remediate the issue. I never withhold it pending payment.
If a vendor validates a useful finding and chooses to recognise the research with a discretionary goodwill contribution, that choice does not affect access to the report, coordination, or fix validation.
Read how I workI run GreySurface as an independent security research practice, based in the UK. I keep the focus narrow by design: access-control weaknesses in software that separates one customer's data from another's.
My aim is straightforward. I want to give the vendor a clear, reproducible report early enough for the issue to be fixed before it causes harm.