Azure AI Content Safety (Prompt Shields) vs Prisma AIRS AI Runtime Security API

Azure AI Content Safety (Prompt Shields)

Prompt Shields checks up to five retrieved documents for indirect injection, not only the user prompt. Needs an Azure subscription with a card, a resource and a region that has the feature, before the first call.

Prisma AIRS AI Runtime Security API

A public OpenAPI document, ten detection types in one call, tool-call scanning, a remote MCP server, rotating API keys and OAuth roles suit teams already on Strata Cloud Manager. Access needs Software NGFW credits bought through sales, with no public price, trial or self-serve signup, and payloads flagged malicious are kept for up to 10 years.

Azure AI Content Safety (Prompt Shields)

1. Send retrieved pages and tool results in the documents array of shieldPrompt, not in userPrompt, so document attacks are reported separately
2. Call text:shieldPrompt over REST with api-version=2024-09-01. The Python SDK 1.0.0 has no method for it
3. Keep each request under 10,000 characters across prompt and documents, and split long tool results
4. Create the resource in a region that lists Prompt Shields, since not every region has it
5. On F0 you get 5 requests a second. Queue checks or move to S0 before load testing

Prisma AIRS AI Runtime Security API

1. Send x-pan-token and an ai_profile with profile_name or profile_id on every scan. Both come from Strata Cloud Manager, and a key works only in its own region
2. Put earlier turns first in contents. Only the last element is scanned, and the rest is context
3. Read action (allow or block) and category, then check timeout and error, because a detector that failed is reported in errors with a 200
4. Keep synchronous requests under 2 MB and asynchronous ones under 5 MB and 25 items, and fetch at most 5 scan or report IDs a call, 10 calls a minute
5. For MCP, connect to /mcp on the regional host with x-pan-token and x-pan-profile headers, and call pan_inline_scan yourself before and after generation