GateWall Developer & Security Docs

Prompt and completion payloads strictly exist in volatile memory buffers for the duration of the stream. Once the HTTP stream terminates, RAM buffers are immediately flushed. No disk writes, no vector databases, no model training.

Every session receives a cryptographically verifiable HMAC-SHA256 signature containing token count, masked PII types, and latency metrics for compliance audits without storing payload content.

GateWall acts strictly as a data processor on behalf of your organization. You remain the sole Data Controller and retain exclusive ownership over your business data. A standardized Data Processing Agreement (DPA) compliant with EU SCCs is readily provided.

Customer prompts and completions are never sold, shared, or used to fine-tune foundation models. In-flight tokenization guarantees that no identifying records leave your secure EU boundary.

All client traffic is strictly enforced over TLS 1.3 with Perfect Forward Secrecy. Upstream BYOK keys are encrypted at rest with hardware-accelerated AES-256-GCM. Session audit proofs are cryptographically signed via HMAC-SHA256.

Sensitive data (SSN, payment cards, phone numbers, IP addresses) are neutralized into synthetic tokens before reaching external models. For maximum confidentiality, the 'Zero-Trace' mode guarantees instant volatile RAM destruction with zero payload persistence.

Anti-Loop Circuit Breaker (OWASP LLM06)

Monitors tool execution sequences. When an AI agent invokes the same tool with identical or oscillating parameters more than 3 times, GateWall trips an immediate circuit breaker to protect budgets.

Human-in-the-Loop Supervision (OWASP LLM03)

Critical actions (database migrations, fund transfers, email blasts) are paused in PENDING state awaiting human operator validation via the Cockpit or API webhook.