Stop Crosstenant Cache Leaks

The problem

Multi-tenant applications often leak sensitive data when cache keys lack proper scoping or invalidation logic. Developers face cross-tenant data collisions, stale reads after updates, and authorization bypasses during cache hits.

What it does

• Audits Redis, Memcached, and in-memory caches for unsafe key construction.
• Traces cached values from storage to retrieval to ensure authorization boundaries are respected.
• Applies tenant-scoped cache key contracts and precise invalidation triggers.
• Implements stampede protection and namespace versioning to prevent performance degradation.
• Validates repairs using concurrent request simulations and cross-tenant leakage tests.

Frameworks & tools

Supports Redis, Memcached, CDN layers, and framework-specific query or response caches. Works with any standard tenant model involving organization, workspace, or user identifiers.

Why this beats prompting it yourself

Generic prompts often miss subtle race conditions or fail to verify if a cache hit bypasses server-side authorization. This skill follows a strict execution process that mandates cross-tenant testing and precise invalidation over simple TTL-based fixes.

Use cases

• Preventing User A from seeing User B's cached dashboard data.
• Fixing stale permission caches after a user's role has been revoked.
• Ensuring search results remain isolated within a specific organization's namespace.
• Protecting authoritative databases from stampedes during high-concurrency cache misses.

Known limitations

Requires server-side validation of tenant identifiers. Cannot verify distributed behavior if only local mocks are available without access to the actual cache provider.