Audit a WAF 403 Dump Before a Model Sees the Cookie You Blocked

说明与用途

工程师不小心将包含敏感头部的完整 WAF 403 日志粘贴到 AI 模型中，导致会话凭证泄露。解决方案：使用扫描器拒绝包含 Cookie、Authorization 等敏感信息的日志，仅使用已清理的元数据。

问题

Engineers inadvertently paste full WAF 403 logs containing sensitive headers (Cookie, Authorization, etc.) into AI models, leaking session credentials and violating trust boundaries.

结果

By rejecting logs that contain sensitive headers or tokens, the organization prevents accidental credential leakage into AI models, maintaining trust boundaries and reducing the risk of credential compromise.

工作流

• 1. Receive WAF 403 log in incident channel.
• 2. Copy raw log line into AI prompt.
• 3. AI model answers why the request was blocked.
• 4. Sensitive header values (Cookie, Authorization, etc.) are exposed to the model.
• 5. No control prevents leakage.
• 6. Implement a prompt-boundary scanner that rejects logs containing sensitive headers or tokens.
• 7. Use redacted fixtures to test the scanner.
• 8. Replace raw logs with redacted metadata before prompting the model.

证据

Never send these in a why-was-this-blocked prompt: Cookie, Set-Cookie, Authorization, CSRF tokens, internal IPs, JWT strings.

来源

Build a prompt-boundary fixture… A command that exits 1.

来源