gpu-infrastructure-security

Community

Prevent cross-tenant GPU data leaks via isolation

Authormaruakshay
Version1.0.0
Installs0

System Documentation

What problem does it solve?

GPU infrastructures often run multiple workloads on shared GPUs, leading to VRAM residues, non-isolated CUDA contexts, and potential credential exposure. This Skill provides guidance to identify, mitigate, and validate isolation gaps to reduce cross-tenant data leakage and privilege escalation in GPU compute environments.

Core Features & Use Cases

  • VRAM isolation checks: verify memory is cleared before releasing GPU allocations and workloads initialize VRAM explicitly.
  • Credential isolation and IMDS hardening: ensure credentials aren’t leaked via instance metadata and limit cloud credentials exposure.
  • Deployment governance: enforce tenancy policies, auditing, and patching cadences for GPU drivers and firmware.
  • Use Case: In a multi-tenant cloud cluster, apply these controls to prevent a following workload from reading remnants of a previous job’s activations or weights.

Quick Start

Audit GPU tenancy to ensure VRAM isolation and IMDS hardening on all GPU nodes.

Dependency Matrix

Required Modules

None required

Components

Standard package

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: gpu-infrastructure-security
Download link: https://github.com/maruakshay/mii-ai-security/archive/main.zip#gpu-infrastructure-security

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.