Features

PII Redaction And Dictionaries

PII redaction protects AI Orchestration OpenAI-compatible gateway requests and responses before model-provider egress. Gateway endpoint masking is a separate control for supported interlay request surfaces. Both are governed through Eden identity, RBAC, and telemetry, but they do not apply an identical scanner to every endpoint, template, API, or workflow request.

Gateway owns endpoint and interlay masking. AI Orchestration owns the LLM-gateway scanner, organization dictionaries, gateway-key terms, and template-backed PII lookup used for governed AI traffic.

Sources

Source	Scope	Notes
Built-in PII detection	AI Orchestration LLM gateway prompt and completion content	Common email, phone, SSN, and payment-card patterns.
Organization PII dictionary	AI Orchestration LLM gateway keys in one organization	Shared literal or regex terms for the LLM gateway path.
Endpoint masking rules	Supported Gateway interlays	Request dictionaries and structure-aware masks, subject to the endpoint backend profile.
`custom_pii_terms`	AI Orchestration gateway key	Key-specific literal or regex terms for LLM gateway traffic.
Lookup-derived terms	AI Orchestration request	Values returned by configured `pii_lookup_templates` before model egress.

Merge Behavior

When the same value appears in more than one AI Orchestration LLM-gateway dictionary or lookup source, Eden keeps the strictest configured action:

Block > Redact > AuditOnly > Allow

The merged LLM scanner runs once before model-provider invocation, so dictionary-only deployments and template-enriched deployments use the same enforcement path.

API Surface

Gateway key terms are specific to AI Orchestration LLM gateway traffic:

json

{
  "custom_pii_terms": [
    {
      "value": "SIU-INV-4419",
      "label": "investigation_id",
      "action": "redact"
    }
  ]
}

AI Orchestration LLM gateway dictionaries are managed through:

text

GET /api/v1/llm/pii_dictionary
PUT /api/v1/llm/pii_dictionary

Gateway endpoint PII and masking use endpoint or interlay masking configuration. See Traffic Masking for the endpoint-side configuration surface.

Runtime Placement

In AI Orchestration, the scanner sees OpenAI-compatible request and response content after Eden has loaded gateway-key policy and request metadata, and before route/provider egress. Model routing, template lookup, and content policy can contribute request-scoped terms while the upstream provider receives a single masked payload.

In Gateway native gateway paths, use Traffic Masking for configured request dictionaries and structure-aware masks. That path does not run the AI Orchestration built-in PII regex scanner or template lookup by default.

Actions

Action	Behavior
`allow`	Record policy context without changing the payload.
`audit_only`	Record a safe match category and count without modifying the payload.
`redact`	Replace the matched value before upstream egress.
`block`	Stop the request before provider egress.

Use block for values that must never leave Eden, redact for values that can be safely replaced, and audit_only during rollout when operators are measuring match behavior.

Operational Guidance

Keep AI Orchestration organization dictionaries for shared LLM-gateway terms, endpoint masking rules for supported Gateway interlay request surfaces, and key-level custom_pii_terms for AI Orchestration route-specific values. Use template lookup when the sensitive values are known in a trusted system of record but are not reliably detectable by generic regexes.

Review safe telemetry counts during rollout. If a custom term lacks a label, Eden emits a non-reversible safe category instead of the raw term, but labeled terms are easier to interpret in dashboards and evidence exports.

Safety

Matched term values are not emitted in telemetry.
Custom and lookup labels are used for safe summaries.
If a label is missing, Eden uses a non-reversible safe category instead of the raw value.