Prompt Egress Scanner is the outbound boundary between your agents and the LLM provider. Every prompt is scanned for secrets (API keys, tokens, passwords), PII (emails, SSNs, credit cards), and cross-tenant identifiers before it leaves your network. Detected items are redacted in place. Pairs with Prompt Injection Defense to make the prompt boundary watertight in both directions.
The scanner runs three signature categories on every prompt body. Secrets: API keys, OAuth tokens, JWTs, private keys, database passwords. PII: emails, phone numbers, SSNs, credit cards, mailing addresses. Cross-tenant identifiers: tenant ids, user ids, org ids that do not belong to the calling tenant. Each category has a configurable threshold and outcome (redact in place vs block the call entirely).
For most matches, the scanner redacts the matched substring with a typed placeholder ([API_KEY], [EMAIL], [TENANT_ID]) and lets the prompt continue. The agent receives a slightly-less-specific prompt but can still reason. For high-severity matches (raw private keys, credit cards), the scanner blocks the entire call and records the attempt in Agent Ledger.
Cross-tenant scanning is the strictest layer. Every tenant has an allowlist of identifiers that may appear in their prompts. Anything else gets redacted. This catches the rare case where a log line from one tenant ends up in another tenant's correlation graph (which the data plane prevents, but defense in depth wins).
Egress events ship to your SIEM via the same channel as inbound Prompt Injection Defense. One config, one dashboard. Weekly report covers volume, redacts per category, blocks per category, top sources, and false-positive rate. The report is the data your security team will ask for first.
Subscribe to Nova AI Ops on YouTube for demos, tutorials, and feature deep-dives.
No prompt leaves your network until it is clean. Audit-ready, SIEM-integrated, weekly reported.