B2B tenant administration misconfiguration

Detection signals

• A user from one organization seeing another organization's data
• An SSO connection or verified domain claiming addresses it should not
• Unexpected admin-role grants in a tenant's audit log
• Support reports of cross-tenant access or wrong-org login routing

Likely root causes

• Verified-domain or SSO connection misconfigured to over-broad scope
• Tenant isolation gap in authorization checks
• Admin role granted too broadly or to the wrong principal
• JIT provisioning placing users in the wrong organization

Containment

1. 1Scope down or disable the offending SSO connection / domain claim
2. 2Revoke incorrect admin-role grants and affected sessions
3. 3Verify tenant-isolation checks on the exposed data paths
4. 4Re-route mis-provisioned users to the correct organization

Customer communication

• Notify affected organizations precisely: what was exposed and to whom
• For regulated data, assess and meet breach-notification obligations
• Confirm remediation and the isolation guarantee going forward

Forensics & logging

• Reconstruct who accessed what across tenant boundaries, from audit logs
• Identify the exact misconfiguration and when it was introduced
• Preserve per-tenant audit logs as evidence

Post-incident hardening

• Add guardrails and review on SSO/domain configuration changes
• Alert on unexpected admin-role grants and cross-tenant access
• Test tenant isolation as part of the release process

FAQ

A customer can see another tenant's data, what now?

Scope down or disable the offending SSO connection or domain claim, revoke incorrect admin grants and affected sessions, and verify tenant-isolation checks on the exposed paths before notifying affected organizations.

How do I prevent tenant misconfiguration?

Add guardrails and review on SSO and domain changes, alert on unexpected admin-role grants and cross-tenant access, and test tenant isolation as part of every release.