Deploy the browser extension

The CID222 browser extension inspects what a person types into an AI website — ChatGPT, Claude, Gemini — from inside the browser, without intercepting TLS. Administration → Browser Extension generates the managed policy that installs it and points it at this appliance. Everything else the extension does — device attestation, the firewall block list, the event feed — is configured through the API or read on other pages.

Before you start: set the hosts on the appliance

Set both environment variables on the appliance and restart the gateway before you use this page:

• API_DOMAIN — the external name browsers reach this appliance on. It becomes cidHost.
• EXTENSION_CRX_DOMAIN — where the signed .crx and extension-update.xml are published.

A value with no scheme is treated as https://, and trailing slashes are stripped. If either is unset, the policy carries https://REPLACE-WITH-YOUR-CID-HOST or https://REPLACE-WITH-YOUR-CRX-HOST and the page shows Placeholders still present.

Generate the managed policy

What the policy contains

{
  "ExtensionInstallForcelist": [
    "lllegnpcnmlafjcdkpecabdiogjafgei;https://crx.example.com/extensions/stable/extension-update.xml"
  ],
  "3rdparty": {
    "extensions": {
      "lllegnpcnmlafjcdkpecabdiogjafgei": {
        "cidHost": "https://cid.example.com",
        "cidApiKey": "cid_key_REPLACE_WITH_TENANT_KEY",
        "failClosed": true
      }
    }
  }
}

Three managed keys reach the extension, and only three.

Two documents also list a fourth key, extensionUpdateChannelUrl. The generator does not emit it. The update URL travels in ExtensionInstallForcelist instead.

Enrol and revoke devices

Device attestation proves a browser is the one it claims to be, so a firewall can allow AI destinations from protected machines only. It is entirely API-driven: there is no device list, no enrolment panel and no revoke button anywhere in the dashboard.

The extension performs the exchange itself, authenticating with the gateway API key from the managed policy — never a session token:

1. POST /api/v1/extension/attestation/enroll registers the device with a P-256 public key. A key carrying its private scalar is refused. Re-enrolling replaces the key but never clears a revocation.
2. GET /api/v1/extension/attestation/nonce issues a 32-byte challenge that lives for 60 seconds and can be claimed once.
3. POST /api/v1/extension/attestation/heartbeat returns the nonce, a timestamp, the device posture and a signature over all three. The extension repeats this every five minutes.

All three are rate-limited to 30 calls a minute per device.

To see or change the fleet, call the admin API as an administrator:

# List enrolled devices, newest heartbeat first
curl -sS https://<appliance-fqdn>/admin/extension-devices \
  -H "Authorization: Bearer <session-jwt>"
 
# Revoke one device, and restore it again
curl -sS -X POST   https://<appliance-fqdn>/admin/extension-devices/<device-id>/revoke -H …
curl -sS -X DELETE https://<appliance-fqdn>/admin/extension-devices/<device-id>/revoke -H …

A revoked device is refused a nonce and drops out of the block list on the next poll.

Publish the firewall block list

CID222 does not block network traffic. It publishes the addresses of healthy, attested devices, and your firewall allows AI destinations only from those addresses.

curl -sS -X POST https://<appliance-fqdn>/admin/edl-tokens \
  -H "Authorization: Bearer <session-jwt>" \
  -H "Content-Type: application/json" \
  -d '{"name":"perimeter-fw","expires_at":"2027-01-01T00:00:00Z"}'

A device appears in the list while it is not revoked, has heartbeated within the freshness window — 15 minutes by default, against a 5-minute heartbeat — and has a recorded source address. Addresses are the ones the gateway observed, not ones the device claimed.

Fields reference

Managed policy tile

Buttons

Related endpoints not on this page

Verify

1. The JSON block on the page shows your real appliance host and CRX host, and the Placeholders still present banner is gone. If it is still there, the environment variables are not set — the form fields will not clear it.
2. On a pilot machine, the extension appears in the browser's extension list, pinned by policy and not removable by the user.
3. Call GET /admin/extension-devices. The pilot machine is listed with a last_seen_at within the last five minutes and a posture recording managedPolicyPresent.
4. Fetch GET /api/v1/edl/healthy-ips with the EDL token. The pilot machine's address is in the output.
5. Type something that trips a filter into an AI website on the pilot machine. The event appears on All Detections filtered to the extension source, and in the AI Usage totals.
6. This module writes nothing to Event logs. Generating a policy, revoking a device and minting or revoking an EDL token leave no audit row — check the device list and token list themselves instead.

If it fails

• Placeholders still present stays up after Generate policy — expected. Set API_DOMAIN and EXTENSION_CRX_DOMAIN on the appliance and restart the gateway; the form fields cannot fix it.
• Selecting Generate policy does nothing visible at all — the request was refused and the page has no error handling for it. Confirm your role is admin_user or superadmin and that the licence includes the browser extension.
• Access denied — Only administrators can manage the browser extension. — a viewer reaches this page through navigation and is then refused by the page itself. Only admin_user and superadmin can use it.
• This feature (…) is not included in the installed license tier. Contact your CID representative to upgrade. with code FEATURE_NOT_LICENSED — the licence lacks the browser-extension capability. It is in every tier, so this usually means an expired or unread licence; see License.
• The extension shows Invalid credentials to users — cidHost in the pushed policy is wrong, or cidApiKey is still the placeholder. Users cannot correct either; fix the policy and re-push.
• Signed in, but this role does not use the browser extension: '…' has no extension view. Use the dashboard instead. — an auditor signed in to the extension. Auditors read evidence in the dashboard and do not generate traffic.
• Attestation rejected (401) — one of six causes, deliberately indistinguishable. Check the device clock first: a skew over two minutes fails every heartbeat.
• Device is enrolled to another tenant — the device identifier is already registered to a different account. Revoke it there before re-enrolling.
• Too many attestation requests (400, not 429) — more than 30 attestation calls in a minute for one device. A device stuck in a retry loop produces this.
• EDL token required / Invalid or expired EDL token (401) — the firewall sent no token, or one that is unknown, revoked or past its expiry. Mint a replacement.
• expires_at must be in the future — EDL tokens must carry a future expiry. Unlike gateway API keys, a never-expiring EDL token cannot be created.
• A large file upload is refused rather than cleaned — chunked and resumable uploads cannot be reassembled for inspection, and CID_RESUMABLE_UPLOAD_POLICY defaults to block. Documents are blocked rather than redacted; only images are redacted in place.

Next steps

• AI usage — who used which AI application, from the events the extension and the proxy both feed.
• All detections — the unified timeline where extension verdicts land beside chat and proxy detections.
• Access keys — issue the cid_key_ the managed policy needs.
• Endpoint agent — the OS-level alternative for traffic a browser extension cannot see.