Guidelines  ·  2026-11-18

IETF draft-shuliak-sip-zero-egress-00: 'Shuliak Isolation Protocol (SIP-1)' — zero-egress isolation for local AI agent transports

GuidelinesMedium impactGlobal
New IETF individual Internet-Draft, draft-shuliak-sip-zero-egress-00, 'Shuliak Isolation Protocol (SIP-1): Stateless Format-Preserving Pseudonymization and AST Quarantine for Local AI Agent Transports' (dated 15 November 2026, Informational). It specifies a deterministic, zero-egress security layer for local JSON-RPC 2.0 tool transports that combine stateless Format-Preserving Encryption (FF1, grounded in NIST FF1), AST-based JSON-RPC payload quarantine, and detached cryptographic schema locks — mapping sensitive tokens to format-valid synthetic twins in volatile memory before crossing tool/model boundaries, so payloads remain valid for Luhn/ISO-7064 validators without exposing regulated data.
Local agentic tool transports and MCP servers run over stdio outside enterprise DLP/inspection perimeters, so naive redaction breaks downstream validators while raw forwarding leaks regulated data. SIP-1 defines a standards-shaped mechanism to keep agent traffic zero-egress while preserving payload validity — a concrete control for local AI agents and the endpoint attack surface.
Review SIP-1 for local agent/MCP transports that carry card/IBAN or other schema-validated sensitive fields; evaluate it alongside the OWASP LLM and MITRE ATLAS mappings for agent tool exposure; consider participation in the IETF agent-transport discussion.
draft-shuliak-sip-zero-egress-00
See this in the live feed Explore related AI security and governance findings — updated every morning.
Open the feed →