Control & Trust·production

IAM.Secure

AI traffic inspection, DLP policies, prompt-injection protection and audit.

Landing Application API endpoint ↗
IAM.Secure interface
Current public IAM.Secure surface. The screenshot was verified when the documentation was published.

Key capabilities

  • Inline request and response inspection
  • DLP, masking, blocking and routing policy actions
  • Decision audit and security evidence

Role in the ecosystem

IAM.Secure checks incoming and outgoing AI traffic before data arrives into the model or downstream tool. The result of the inspection is a structured decision: allow, mask, route or block with an explanatory policy reason.

Main scenario

  1. The client passes the text or URL to dry-run/inline inspection.
  2. T0 rules perform fast deterministic checks.
  3. Classifiers evaluate DLP, injection, abuse and topic policy.
  4. Policy engine combines signals and selects action.
  5. The client receives a verdict and a secure audit reference.

Inline mode is used in real traffic, dry-run - for preliminary policy checks and demonstrations without accessing LLM.

Policy actions

ActionDestination
allowcontinue processing without conversion
maskremove or replace sensitive fragments
routeredirect the request to the agreed perimeter
blockcomplete request before downstream call

Integrations

Secure works before IAM.Router or a specific tool API. Identity context comes from IAM.Identity and IAM.Core may require a security verdict before capability invocation.

Data and audit

Raw secrets and PII should not end up in public logs. Audit stores the verdict, policy/version, request reference and applied actions. Masking should be reproducible, and blocking is distinguishable from provider failure.

Operation

Control the latency of each layer, the proportion of false positive/negative, the policy version, readiness of classifiers and fallback posture. If mandatory security component, the protected route must end with fail-closed.

Limit of responsibility

Secure is not a replacement for tenant authorization, network isolation, or storage encryption. It protects AI/content flow and complements rather than cancels regular security controls.