cross-tenant-access-prevention

Validate tenant ownership on resource accesses to prevent cross-tenant data reads.

Updated Mar 29, 2026

Search Tags:#authorization #multi-tenant #access-control #tenancy #data-isolation #cross-tenant

Ready to run

npx skills add https://github.com/marquesfelip/agents-and-skills --skill cross-tenant-access-prevention

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cross-tenant-access-prevention
Source: https://github.com/marquesfelip/agents-and-skills/tree/main/skills/cross-tenant-access-prevention
Command: npx skills add https://github.com/marquesfelip/agents-and-skills --skill cross-tenant-access-prevention

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safeguards preventing cross-tenant data access in multi-tenant SaaS systems.

Core Features & Use Cases

Enforces tenant ownership at repository and service layers to prevent cross-tenant data access
Validates parent ownership before traversing relationships to child resources
Supports defense-in-depth and automated cross-tenant testing to ensure isolation

Quick Start

Configure the authorization flow so the tenant identity is derived from a validated token and all resources enforce tenant filtering.

Frequently Asked Questions about cross-tenant-access-prevention

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent cross-tenant data access in a multi-tenant SaaS application?▼

Preventing cross-tenant data access requires enforcing tenant ownership validation at repository and service layers on every resource request. This approach validates tenant identity against resource ownership to guarantee strict data isolation across tenants.

What is cross-tenant data isolation and how does it work?▼

Cross-tenant data isolation is a security mechanism that prevents users in a multi-tenant system from accessing another tenant's resources. It works by validating tenant ownership derived from a validated token across all service layer accesses and relationship traversals.

How do I validate parent ownership before traversing relationships to child resources?▼

Validating parent ownership before traversing to child resources requires applying tenant-aware access control checks at the service layer. You must verify the tenant identity against the parent resource before allowing any relationship traversal to prevent cross-tenant reads.

Can I use automated tests to prevent cross-tenant reads in my multi-tenant architecture?▼

Yes, you can use automated property-based tests to prevent cross-tenant reads. By implementing cross-tenant testing requirements, you can systematically verify that your defense-in-depth access controls successfully block unauthorized resource access across different tenants.

Does this approach require configuring tenant identity from a validated token?▼

Yes, configuring tenant identity from a validated token is required. The authorization flow must derive the tenant identity from a validated token and enforce tenant filtering on all resources to establish robust defense-in-depth and ensure cross-tenant data isolation.