ZTDS Guard — Local In-RAM PII & Secret Sanitizer (MCP & AI Firewall)
Local, zero-telemetry VS Code security extension implementing the open Zero-Trust Data Sanitization (ZTDS RFC v1.0) standard. Mask PII, credentials, and API secrets inside local host RAM before prompts reach Copilot, Claude, Cursor, or external MCP servers, and configure verified local MCP tool boundaries cleanly.
Why Developers Use ZTDS Guard in VS Code
- Defend Against Wild MCP Exploits & Tool-Call Leakage: With recent critical vulnerabilities such as
CVE-2026-120779 targeting VS Code MCP clients and cascading multi-server trust poisoning, raw credentials and customer PII inside prompts or workspace context face immediate exfiltration risk.
- 100% Volatile Host RAM Execution: Zero external API calls, zero cloud proxies, zero disk writes, and zero intermediary subprocessors (GDPR Art. 28 & Recital 26 alignment).
- Reversible Single-Pass Tokenization: Substitutes cleartext emails, API tokens, IBANs, SSNs, IPv4 addresses, credit cards, and phone numbers with deterministic surrogate tokens (such as
[EMAIL_TOKEN_1] and [API_SECRET_TOKEN_1]) and restores values locally after AI output arrives.
Commands
Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P):
ZTDS: Sanitize Selection in Volatile RAM — Masks sensitive baseline entities in the active selection or document using deterministic surrogate tokens stored solely in extension host memory.
ZTDS: Restore Surrogate Tokens from RAM — Restores cleartext values from volatile memory with single-pass replacement immune to cascade token injection.
ZTDS: Audit Active File for PII & Secret Egress — Scans the open editor, surfaces inline VS Code diagnostics on exposed lines, and outputs a SHA-256 compliance receipt.
ZTDS: Zeroize Volatile Token Session (Theorem 2) — Immediately clears volatile RAM mapping tables and diagnostics.
ZTDS: Configure Local MCP Firewall (.vscode/mcp.json) — Safely initializes or merges the open-source ztds-mcp stdio server into your workspace configuration.
Containerized & CLI Runtime Compatibility
Run the underlying open-standard MCP firewall via CLI or the signed multi-arch OCI container on Docker Hub (brandmeweb/ztds-mcp):
npx ztds-mcp init
docker pull brandmeweb/ztds-mcp:latest
Compliance Frameworks & ZTDS RFC v1.0 Documentation
Explore the vendor-neutral specification, security boundaries, and regulatory blueprints on ZTDS.ai Open Standard Consortium:
Pioneer Certified Commercial Implementation (PrivacyScrubber)
For enterprise teams requiring 30 industry compliance profiles (HIPAA 18 identifiers, PCI-DSS, defense CMMC, banking SWIFT) and air-gapped node enforcement, deploy PrivacyScrubber, engineered by BrandMeWeb:
License
Apache-2.0. Maintained by the ZTDS AI Consortium (Working Group WG-1). Lead Author: Ilya Sibiryakov.