Adversarial prompt detection
- Flags and blocks known jailbreak patterns, prompt injection attempts, and manipulation techniques in real time through the integrated CrowdStrike AIDR guard every detection streams to your SOC's SIEM with user, department and model attribution.
- Inspection happens before the model processes the request, not after and model replies are guarded on the way out too, with BLOCK / MASK / ALLOW decisions enforced per request.
Automatic data redaction
- A built-in scanner strips 25+ credential patterns API keys, private keys, JWTs, access tokens from every prompt in ~3โ5 ms, before any model call; the AIDR guard detects and masks PII and regulated data in both directions.
- Redacts automatically, without employees needing to remember to do it manually.
Inline protection, built for availability
- The built-in scanner adds ~3โ5 ms; the AIDR check runs in the request path under a strict timeout with configurable fail-open or fail-closed behaviour so protection doesn't break normal usage, and you choose availability or enforcement on guard failure.
- Coverage applies across the chat workspace and the platform's developer API every request that goes through PixSpace is guarded.
Why this matters compared to point solutions
Many tools only catch one risk just PII, or just jailbreak attempts. PixSpace handles adversarial prompts and data leakage in the same inline pipeline, as layers an always-on secret scanner plus the CrowdStrike AIDR guard so security teams aren't stitching together multiple products to cover both.
Where this fits
Frequently asked questions
Does this require changes to how teams already use AI?
No. Inspection happens inline inside the platform, so it works across the chat workspace and the developer API without extra steps for employees.
Does redaction happen before or after the model sees the data?
Before. Sensitive data is redacted from the prompt on the way in, so it never reaches the model in the first place and generated replies are guarded again on the way out.
Does this cover both chat use and direct API calls?
Yes. Coverage applies across the chat workspace and the platform's developer API, so there's no gap between how teams access AI through PixSpace.
