Agent skill · security · jeremylongshore
glean-security-basics
Token security: Indexing tokens have write access -- never expose in
Why this skill is useful
Provides specific security practices and code snippets for managing indexing tokens and webhook verification that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Glean Security Basics Overview Glean indexes and searches across an enterprise's entire knowledge base — Confluence, Google Drive, Slack, GitHub, and dozens more connectors. Security concerns center on indexing token management (write-access tokens that can push content into the search index), client token scoping (user-level search permissions), and document-level access controls. A leaked indexing token allows injecting arbitrary content into enterprise search results. API Key Management Webhook Signature Verification Input Validation Data Protection Security Checklist [ ] Indexing tokens stored server-side only, never in frontend code [ ] Client tokens scoped per-user with X-Glean-Auth-Type header [ ] Tokens rotated quarterly via Admin > API Tokens [ ] Document permissions set via allowedUsers/allowedGroups [ ] SAML SSO enforced for Glean web access [ ] All API calls over HTTPS [ ] Search audit logs enabled to track sensitive queries [ ] Connector permissions reviewed when adding new data sources Error Handling Vulnerability Risk Mitigation --- --- --- Leaked indexing token Arbitrary content injected into search index Backend-only storage + rotation Missing document permissions Confidential docs exposed in search results allowedUsers/allowedGroups on every document Client token in frontend User impersonation in search queries Server-side proxy for search API Overly broad connector scope Sensitive repos/channels indexed unintentionally Per-connector permission review Search queries in logs Employee activity surveillance risk Query redaction in logging pipeline Prerequisites A threat model identifying token custodians, untrusted inputs, source ACL authority, incident owner, and approved secret manager. Separate low-privilege sandbox credentials and fictitious documents for verification; never test with a production token in a shell or CI log. Rotation, revocation, and connector-disable runbooks with a named owner and tested rollback path. Instructions 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/glean-security-basics