Security: inputs, outputs, and events

Understand credential checks, injection signatures, output code markers, and event investigation, and verify matches and actions.

Concept & preparation guideUpdated Oct 28, 2026

Credential patterns in inputs

Input checks focus on credential patterns such as passwords and keys in request content. To understand a match, check the rule, input location, and corresponding action. Match the scope and behavior to your deployment version.

Use synthetic values to test rules, and keep real passwords and production keys out of test requests. Detecting one credential pattern does not establish coverage for all sensitive information.

Code markers in model outputs

Output checks focus on configured code markers in model replies. Review the source, match location, and linked request, then interpret the match in its application context.

A code marker match is not a malware verdict, general vulnerability scan, or code security audit. Verify coverage for non-streaming responses and streaming chunks separately.

Injection signatures and detection boundaries

Deterministic checks distinguish request prompts, model output, and tool content. Built-in signatures cover instruction overrides, hidden instructions, credential solicitation, and exfiltration, with different signatures applying to different directions. Checks include normalized views and bounded Base64, hexadecimal, URL, and Unicode-escape decoding, mapping evidence to the original field location.

The current gateway’s built-in content checks record matches as observe. Events recorded with an injection rule identifier are classified as injection with high severity; this does not establish that a request was blocked. The synchronous scan has a 50 ms deadline and returns allow on timeout. Absence of an event does not establish a complete scan or safe content. Verify streaming chunks, protocols, and tool paths separately.

observe_hit, untrusted_upstream, encoded_fragment, and instruction_like are weak diagnostic log signals for observability. They do not change allow, block, masking, or routing decisions and do not establish that model analysis ran.

Verify detection, recording, and blocking separately

Keep recorded matches distinct from actual blocking. This guide does not claim that every rule provides or has been validated for these actions. Confirm them against release documentation and reproducible results.

  • Detection: did the rule recognize the expected content and locate the match correctly?
  • Recording: was an event created, and can it be linked to the relevant request?
  • Action: what actually happened to the request or response—did it continue, change, or stop? Do not infer an action from a rule name or the presence of an event.

Investigate through security events

  • Check the rule, event source, match location, and actual action.
  • Keep the request identifier to correlate the request with error and usage records.
  • Confirm who may read events and context. Visibility in one role does not establish validated isolation.

Access and credential boundaries

Applications use gateway keys, while the gateway uses provider credentials to reach model services. Define boundaries around organizations, roles, model permissions, and applicable IP rules. Verify both allowed and denied cases.

Hidden credentials in a UI, encrypted storage, controlled decryption, masked logs, and data cleanup are separate verification targets. Evidence for one does not establish the others.

Event context and retention

Masked context establishes only how that content is displayed. It does not prove that raw requests or responses never enter databases, logs, or telemetry. Verify retained fields, permitted roles, retention periods, and cleanup outcomes separately.

Match capabilities and procedures to your deployment version. Read the documentation scope

BOS API · TYPEX

Sales consultation is unavailable

Sales reception could not be initialized. Please try again later. Documentation and free self-hosting remain available.

Read the docsSelf-host for free