Security gateway

Streamed answers checked in flight

Streamed answers are checked a few words ahead, so a secret can be removed before it reaches the screen.

What it is

Responses are scanned too. On a stream Janus holds back a short window of text so a secret or codename can be removed or the stream cut before those bytes leave the gateway.

Why you want it

Most AI traffic is streamed. Checks that only run after the stream ends are too late to stop anything.

A model streams an answer that contains a cloud access key. Janus holds back a short window of text, about a couple of words, scans it, and replaces the key with a redaction marker before those bytes reach the person's screen. FROM THE MODEL …the staging deploy uses key AKIAIOSFODNN7EXAMPLE and region us-east-1… Janus holds back ~256 bytes scans the tail for secrets, PII and codenames a couple of words of lag ON THE PERSON'S SCREEN …the staging deploy uses key [REDACTED:aws-access-key-id] and region… Or cut the stream entirely. Either way the key never left the gateway.

How it works

  • Default hold-back window of 256 bytes, a couple of words of lag
  • Deterministic detectors (secrets, PII, terms) run on the stream tail
  • Actions recorded as redacted or stream_cut

Related features

Secret detection and redaction Multiple editions

Twenty-seven detectors catch API keys, cloud credentials and passwords, then redact them or block the request.

Details →

PII detection Multiple editions

Card numbers, IBANs, Social Security numbers, emails and phone numbers are recognized in the gateway itself.

Details →

Codename and term lists Multiple editions

Lists of codenames and client names that still match when someone writes Pr0j3ct or adds spaces.

Details →

See it on your own network.

The Community edition is free for up to 25 people. The 30-day Business trial unlocks every Business feature.

Download free Start a Business trial