Chaining behind your SWG

You don’t have to replace your secure web gateway (SWG) to get prompt-level visibility. Configure the SWG to forward only AI destinations to the PromptGlass Gateway. The SWG keeps handling everything else, and PromptGlass adds what SWGs usually lack: prompt understanding, AI-specific DLP, attribution by team, and cost and adoption analytics.

Patterns

Pattern	Flow	When to use
Upstream chaining	Client → SWG → PromptGlass Gateway → AI app	Most common; the SWG forwards AI categories to PromptGlass as its next-hop proxy
Downstream chaining	Client → PromptGlass Gateway → SWG → internet	When PromptGlass is the client’s PAC target for AI and the SWG must see all egress
Side-by-side	PAC sends AI domains to PromptGlass, everything else to the SWG	Simple, no SWG configuration changes

In upstream chaining, decide which product decrypts. Usually the SWG skips SSL inspection for AI destinations (a “do not inspect” rule) and PromptGlass decrypts them, so the traffic isn’t decrypted twice.

Zscaler Internet Access

1. Administration → Forwarding Control → Proxies & Gateways: add a proxy with your PromptGlass gateway’s public VIP (or ZPA app connector address) and port 3128.
2. Forwarding Control → Forwarding rule: criteria URL category = Generative AI (plus any custom category exported from PromptGlass), forwarding method Proxy Chaining, proxy = PromptGlass.
3. SSL Inspection: add a Do Not Inspect rule for the same categories.
4. Turn on X-Authenticated-User header insertion so PromptGlass can attribute users without its own authentication.

Netskope

1. Create a Steering Configuration exception or a Proxy Chaining destination pointing to the PromptGlass gateway.
2. Use the Generative AI app category (and a custom URL list from https://<tenant>/api/v1/catalog/urls.txt) as the match.
3. Add an SSL decryption bypass for the same list.
4. Turn on X-Forwarded-For and user header insertion in Advanced Settings.

Palo Alto Networks Prisma Access

1. In Explicit Proxy or Mobile Users, create a Forwarding Profile with a proxy rule that sends the artificial-intelligence URL category to the PromptGlass gateway.
2. Add a Decryption Exclusion or No Decrypt rule for that category.
3. Configure HTTP header insertion of the authenticated username.

Trusting identity headers

gateway:
  identity:
    trustedHeaders:
      - name: X-Authenticated-User
        fromCidrs: [165.225.0.0/17, 147.161.128.0/17]   # your SWG egress ranges
        format: upn            # upn | samaccountname | email | base64-upn

PromptGlass accepts identity headers only from the source ranges you list.

Keeping AI domain lists in sync

PromptGlass publishes your effective AI destination list (catalog plus custom domains) at GET /api/v1/catalog/urls.txt. Most SWGs can consume it as an external dynamic list, refreshed hourly.