SPB Git

Repository Public

security.md 16.7 KB 312 lines markdown

1<!-- source: https://docs.x.ai/grok-bot/security (from https://docs.x.ai/llms-full.txt, retrieved 2026-09-19T05:28:55Z) -->2#### Manage and protect34# Grok Bot security56Use these controls and deployment details to decide whether Grok Bot is allowed7in, and to limit what Bots can access, change, and retain. Rollout steps and8the dashboard settings list live on9[Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises), and10common review questions are on the11[Grok Bot security FAQ](/grok-bot/security-faq).1213> Enterprise only on the Grok Bot dashboard: the organization-wide enable14> switch, Network Controls, Team Setup, Action Recording, Allow Local Egress,15> Enforce Auto-review with its team rules, and computer management for16> organization admins. Audit logs, OpenTelemetry Export, the MCP allowlist, and17> SCIM are also Enterprise only. Self-serve Teams do not see those settings.18> The full list is under19> [admin controls](/grok-bot/teams-and-enterprises#admin-controls).2021## Network policy2223Network Controls is Enterprise only. Admins set a Grok Bot network policy from24the Grok Bot page of the [Cursor dashboard](https://cursor.com/dashboard/bot),25under **Network** as **Grok Bot Network Access**.26It controls which destinations team computers can reach. Self-serve Teams do27not see this panel and cannot set a destination allowlist. Teams without a28policy default to allow-all.2930| Mode | Effect |31| --- | --- |32| **No Policy (Allow All)** | Allow all (the default for teams without a policy) |33| **Allow All Network Access** | Explicitly allow all destinations |34| **Defaults + Team Allowlist** | Cursor's default destinations plus your list |35| **Team Allowlist Only** | Only your list, plus the destinations a computer needs to function |3637* Destinations cover web domains as well as IP ranges with ports for raw38  connections, with no cap on the number of entries.39* Directory groups are Enterprise only, inside Network Controls. Groups can set40  their own network policy, which replaces the team's for their members, and a41  lock makes the team policy effective for everyone.42* The policy is separate from Cloud Agent network settings. Running computers43  apply changes automatically within about a minute. Sleeping computers apply44  changes when they next wake. You do not need to recreate the computer.45* Restricting egress limits where data can be sent. Dedicated data loss46  prevention hooks are not available.4748Blocking a plugin does not block that service's website. The49[connector policy](/grok-bot/teams-and-enterprises#admin-controls) and the50network policy are separate layers, and closing both paths takes both controls.5152## Static egress IPs5354Hosted computers reach the internet through shared static egress IP addresses55by default. The ranges are shared across Grok Bot customers, and dedicated per-customer IPs56are not available, so treat the ranges as identifying Grok Bot traffic rather57than your team alone. Current ranges are available from your account team, and58the product control is the destination allowlist rather than a source IP59editor.6061If member devices sit behind Zscaler or another TLS-inspecting gateway, allow62Cursor's domains and exempt them from inspection on every profile, including63off-network. See [Configure TLS-inspecting proxies](/grok-bot/proxies).6465Members can route traffic through their desktop to use its network and IP66address. Team Setup is Enterprise only. Those teams can also install their own67networking client on every team computer. Both paths are separate from the68shared egress ranges. See69[Connect to private networks](/grok-bot/private-networks).7071## Approvals and Auto Review7273Approvals keep consequential actions under the member's control. The strongest74boundary is the one in the request itself, so have members state what a Bot75may change and where it must stop:7677> Reconcile the campaign data and draft a recommended budget change. Do not78> change the campaign or message the agency. Ask for approval after showing the79> current value, proposed value, and expected impact.8081When an action needs approval, the conversation shows the proposed operation82and its inputs. **Allow once** lets the Bot continue with that action,83**Always allow** can save a matching rule, and **Deny** blocks it (on iPhone84and Android, the Auto-review sheet offers **Allow**, **Deny**, and, when a rule85is proposed, **Always allow**). An approval86controls the proposed action, not work already completed, and nobody should87approve an action whose target or effect they cannot identify.8889Auto Review is the review layer behind those prompts: an independent review90model that evaluates risky Bot actions before they run, covering shell91commands, plugin calls, computer use, automation writes (changes to routines92and event triggers), and delegation such as Cloud Agent and subagent launches.93It can let an action proceed, require approval, or deny it.9495* Team admins can enforce Auto-review. Enterprise only. The switch lives on96  the Grok Bot page of the Cursor dashboard. When it is on, members cannot97  turn Auto-review off. See98  [Enforce Auto-review](/grok-bot/teams-and-enterprises#enforce-auto-review).99* Admins can add team Auto-review rules. Enterprise only. These live on the100  Grok Bot page too. They apply to every member's Bots, show up as locked rows101  in the member settings table, and save automatically when an admin adds,102  edits, or deletes a rule. If admins turn enforcement off, the team rules stop103  applying and members go back to their own rules only. See104  [Auto-review rules](/grok-bot/teams-and-enterprises#auto-review-rules).105* Members can add personal rules under **Settings → General → Bot →106  Auto-review**. **Ask first** rules always stop matching actions, and **Allow107  automatically** rules let matching actions proceed only when the reviewer108  finds no other reason to stop. Personal rules sit on top of team rules but109  only make behavior stricter; **Ask first** wins when rules conflict. Narrow110  rules around a known action and scope work best, like "ask first before111  sending any external email" or "allow automatically when running112  `git status` in `/workspace/reports`"; avoid broad rules like "allow113  everything in the browser". Personal rules are saved to the member's account114  and applied on every desktop they sign in to.115* It does not review every side effect; memory writes and most settings changes116  are examples. Treat it as a complement to explicit boundaries and least117  privilege, working alongside controls that do not depend on a model's118  judgment: per-action approvals, the network policy, and per-user isolation.119120For the member-facing walkthrough of these prompts and rules, see121[Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy).122123## Identity and sign-ins124125Members sign in to Grok Bot with their Cursor account, so your existing Cursor126SSO configuration applies. SAML 2.0 single sign-on works with Okta, Microsoft127Entra, Google Workspace, and OneLogin, and SSO can be required for all members128(which blocks password login). SCIM is Enterprise only: SCIM 2.0 provisioning129and deprovisioning. For step-by-step Okta and Entra ID configuration, including130app assignment and sign-in rules for the computer browser, see131[Configure identity and access](/grok-bot/identity-and-access).132133Inside the hosted computer, members sign in to applications through your own134identity provider in the browser, comparable to enrolling a new laptop. Your135session policies govern those sessions, and revoking the user in your identity136provider ends them.137138A Bot has no identity or credentials of its own:139140* Bots act as the signed-in member. A Bot can never hold more access than the141  person it belongs to, every action stays attributable to a named member, and142  there is no separate machine identity outside your identity provider to143  provision, rotate, or audit. Team-managed connectors are the one exception:144  they may use team or service-account credentials.145* Connector tokens stay on Cursor's backend. Bots invoke tools without146  receiving OAuth tokens, and tokens are never stored on the computer.147* Credentials stay with the member. For login, two-factor, and payment steps,148  the Bot hands the computer to the member rather than typing credentials. For149  supported connections, a secure secret request masks the entered value and150  keeps it out of the transcript and away from the model; passwords and151  one-time codes never belong in ordinary chat. See152  [Enter passwords and verification codes yourself](/grok-bot/approvals-security-and-privacy#enter-passwords-and-verification-codes-yourself).153154To end a member's current work, an organization admin terminates the member's155computer from the dashboard; see156[Manage Grok Bot computers](/grok-bot/computers). That control is Enterprise157only. It stops running Bots, keeps the durable disk, and the member's next158session starts a fresh computer. It does not remove access. To remove access,159remove the member from the team or turn off Grok Bot for their group, and160revoke their sessions in your identity provider. Application sessions persist161only on the member's computer.162163When a project or login should no longer be available, members clean up164directly: pause or delete related routines, sign out of websites on the165computer, uninstall plugins and revoke their authorization in the source166service, and remove sensitive files from `/workspace`. Deleting a Bot does not167remove computer files or browser sessions.168169## Logging and audit170171Audit Logs and Action Recording use separate pipelines. Audit Logs cover172administrative and security events, including Grok Bot control-plane actions.173Action Recording captures Bot actions, and OpenTelemetry Export sends those174events to your collector when configured, tagged `cursor.surface=grok_bot`.175176* Audit logs are Enterprise only. They cover admin, security, and177  authentication events, plus Grok Bot control-plane events: Bot creation,178  member access changes, Team Setup manifests, MCP authentication, Slack179  account links, and routines. Filter them by application in the dashboard, or180  stream them to your SIEM. Self-serve Teams do not get this log.181* Action Recording is Enterprise only. It is a setting on the Grok Bot page,182  off by default. When a team enables it, Cursor records Bot actions, including183  scrubbed shell commands, in an internal store with a 90-day retention. Action184  Recording events do not appear on the Audit Log page. To receive the185  sanitized events in your own collector, configure186  [OpenTelemetry Export](https://cursor.com/docs/enterprise/opentelemetry-export),187  which is also Enterprise only. Privacy Mode (Legacy) forces recording off.188189## Endpoint tooling190191Grok Bot does not ship a built-in customer-facing telemetry or EDR feed. The192computers are Cursor-operated infrastructure that Cursor monitors for193operational health and abuse, and that telemetry deliberately excludes customer194data. Team Setup is Enterprise only; those admins can install their own tooling195on every team computer.196197## Data retention and deletion198199Each member's computer keeps local files, browser sessions, and anything saved200in the browser on a durable disk across sessions. Connector tokens are never201stored on the computer.202203* Idle computers hibernate automatically; hibernation is not deletion.204* Image updates preserve files: computers on a stale system image are recreated205  on the fresh image with member files preserved.206* Member resets keep synced data. Members can reset their own computer from the207  desktop app. Reset keeps the synced durable data, and recent unsynced work208  can be lost. See209  [Update, recover, or reset the computer](/grok-bot/computer-and-apps#update-recover-or-reset-the-computer).210* Deletion follows the DPA. Under the211  [Data Processing Agreement](https://cursor.com/terms/dpa), data is deleted or212  returned within 30 days of written direction after the service ends.213* Backups run daily. Cursor's production control plane is covered by daily214  encrypted backups, replicated to a separate recovery facility.215216A per-organization retention policy and customer-managed point-in-time restore217of an individual computer are not available.218219## Data residency220221Grok Bot computers run in the United States today. That is not the same as222Cursor's223[US-only data residency](https://cursor.com/docs/enterprise/privacy-and-data-governance#data-residency)224program, which does not apply to Grok Bot by default. If your review needs a225written residency commitment, contact your account team.226227## Models and data228229Cursor manages model selection. There is no customer-facing model picker, and230the serving mix can change over time with no fixed vendor set guaranteed. Usage231analytics show the model that served each request, including failovers, and232billing follows the serving model.233234* The team model allowlist is Enterprise only, and enforcement is not235  guaranteed. The list is honored by default, and onboarding presents an236  acknowledgement that Grok Bot may not follow it, so treat enforcement as237  configuration dependent. See238  [model access control](https://cursor.com/docs/enterprise/model-and-integration-management#model-access-control).239* Privacy Mode applies. While a member is on your team, the team's privacy mode240  governs them, and with Privacy Mode enabled, customer data is not used for241  training.242* Zero Data Retention follows Cursor's existing provider agreements. Model243  providers do not keep prompts or outputs, and Grok Bot adds no separate244  control. Providers may run abuse and safety classifiers, and flagged data245  may be stored for investigation.246247If your contract limits which subprocessors can handle your data, contact your248account team before rolling out Grok Bot.249250## Local execution251252Bots can act on a member's own machine through the desktop app: run commands,253read files, and move files between the cloud computer and the local machine.254This is separate from work in the hosted computer, with its own control, and255it is distinct from Auto Review, which governs work inside the hosted computer.256257Per-command approval is the default, and the approval card shows the exact258command. Members choose the policy under259**Settings → General → Bot → Execution on Local Computer** (or per computer260under **Settings → Computer → Computers**): **Ask every time**, **Always261allow**, or **Never allow**. Recommend **Never allow** unless a Bot has a262specific reason to work on local files. Admins can cap the policy for the263whole team with264[Execution on Local Computer](/grok-bot/teams-and-enterprises#execution-on-local-computer)265on the Grok Bot page; a member's own setting still applies when it is266stricter. For the member-facing steps, see267[Control access to your local computer](/grok-bot/approvals-security-and-privacy#control-access-to-your-local-computer).268269## Hosting270271Grok Bot runs only on Cursor-hosted cloud computers. On-premises deployment,272deployment inside your own perimeter, and bring-your-own-image deployment are273not supported today. Hosted computers use shared static egress by default.274Members can route traffic through their desktop, and Enterprise teams can275install a networking client with **Team Setup**. See276[Connect to private networks](/grok-bot/private-networks).277278## Prompt injection279280Content a Bot reads from the outside world, like web pages, plugin results, and281command output, can try to steer it. Grok Bot layers defenses: Auto Review282checks Bot actions against the member's request when enforcement is on, and283beneath it sit controls that do not depend on any model's judgment, including284the network policy, per-action approvals, and per-user isolation. Outside285content is marked as untrusted data when presented to the model. These controls286reduce, but do not eliminate, risk from malicious content, which is another287reason to keep consequential actions behind approval.288289## Certifications290291Anysphere, the company behind Cursor, holds ISO/IEC 27001 and ISO/IEC 42001292certifications, issued by Schellman, and Grok Bot is included in the current293ISO scope. ISO/IEC 27001 certifies the information security management system,294the security program of the whole organization. ISO/IEC 42001 certifies the AI295management system, how Cursor governs the AI it builds and operates.296Certificates and reports are available at297[trust.cursor.com](https://trust.cursor.com).298299## Related pages300301* [Grok Bot security FAQ](/grok-bot/security-faq)302* [Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises)303* [Configure identity and access](/grok-bot/identity-and-access)304* [Connect to private networks](/grok-bot/private-networks)305* [Configure TLS-inspecting proxies](/grok-bot/proxies)306* [Manage Grok Bot computers](/grok-bot/computers)307* [Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy)308* [Privacy and Data Governance](https://cursor.com/docs/enterprise/privacy-and-data-governance)309310Contact your Cursor account team about egress ranges, residency commitments,311and security review support.312
Files main
Menu

Theme