model-caching-security

Audit model caching layers for cross-tenant leakage and cache poisoning risks.

4|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/maruakshay/mii-ai-security --skill model-caching-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: model-caching-security
Source: https://github.com/maruakshay/mii-ai-security/tree/main/skills/model-caching-security
Command: npx skills add https://github.com/maruakshay/mii-ai-security --skill model-caching-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review KV cache, prompt cache, and semantic cache implementations for cross-request context leakage, cache poisoning, sidecar timing attacks, and tenant isolation failures in shared inference infrastructure.

Core Features & Use Cases

  • Investigate and audit cache isolation across tenants for KV, prompt, and semantic caches.
  • Identify timing side-channel and poisoning risks; propose mitigations and guardrails.
  • Provide deployment-ready checks and quick-win improvements for multi-tenant inference systems.

Quick Start

Run a security review of the model caching layers in your shared inference service to identify potential cross-tenant leakage vectors and remediate them.

Frequently Asked Questions about model-caching-security

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

FAQPage Schema
How do I prevent cross-tenant data leakage in shared LLM inference caches?

Prevent cross-tenant data leakage in shared LLM inference caches by auditing KV, prompt, and semantic cache layers to enforce strict tenant isolation and secure cache keys. This identifies context leakage vectors and applies measurable guardrails.

What are the main security risks when using semantic caches in multi-tenant inference platforms?

The main security risks of using semantic caches in multi-tenant inference platforms include cross-request context leakage, cache poisoning, and sidecar timing attacks. These vulnerabilities arise when shared infrastructure fails to isolate tenant cache entries.

How do I audit a KV cache for timing side-channel attacks?

Audit a KV cache for timing side-channel attacks by investigating cache isolation across tenants and identifying timing discrepancies during inference. Apply deployment-ready checks to mitigate sidecar risks and secure cache keys.

Can I secure prompt caching layers against cache poisoning in a multi-tenant environment?

You can secure prompt caching layers against cache poisoning by applying hardening measures that ensure tenant isolation and validate cache keys. This provides measurable guardrails and quick-win improvements for shared inference systems.

Does this approach work for identifying sidecar risks in shared inference infrastructure?

Yes, this approach works for identifying sidecar risks in shared inference infrastructure by reviewing prompt and KV cache implementations. It proposes mitigations and deployment-ready checks to protect multi-tenant environments.