Repository Public
1<!-- source: https://docs.x.ai/grok-bot/security-faq (from https://docs.x.ai/llms-full.txt, retrieved 2026-09-19T05:28:55Z) -->2#### Manage and protect34# Grok Bot security FAQ56These are the questions security reviews ask most often. The controls behind7each answer are on [Grok Bot security](/grok-bot/security). Dashboard settings8and rollout steps are on9[Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises).1011## Isolation and access1213### How are users isolated from each other?1415Each user gets a dedicated Firecracker microVM with its own kernel, memory, and16virtual devices. One user cannot reach another user's computer. Within one17user, every Bot shares that computer, so treat a login or file on the computer18as available to every Bot that user runs. When a workload needs its own19computer and credential set, give it its own Cursor user.2021### What can a Bot access?2223Only accounts and plugins the member or team grants. A Bot has no identity of24its own and cannot hold more access than the signed-in member. Connector tokens25stay on Cursor's backend, and login, two-factor, and payment steps are handed26to the member. See27[identity and sign-ins](/grok-bot/security#identity-and-sign-ins).2829### If we block a plugin, can a Bot still reach that service in the browser?3031Yes. Blocking a plugin does not block that service's website. The32[connector policy](/grok-bot/teams-and-enterprises#admin-controls) and the33[network policy](/grok-bot/security#network-policy) are separate layers.34Closing the website path takes Network Controls, which is Enterprise only.3536### Can admins push connectors to members?3738No. The connector policy allows or blocks servers. Provisioning connectors to39members, whether mandatory or default-on, is not available.4041## Network and egress4243### Can we restrict which destinations computers can reach?4445Network Controls is Enterprise only. Admins set a Grok Bot network policy from46that panel on the Grok Bot page of the dashboard. Self-serve Teams do not see47it and cannot set a destination allowlist, and teams without a policy default48to allow-all. See [network policy](/grok-bot/security#network-policy).4950### Do admin controls apply per group, or only org-wide?5152Directory-group scope is part of Network Controls, which is Enterprise only.53Groups can set their own policy, and a lock makes the team policy effective for54everyone. The organization-wide enable switch is also Enterprise only and55applies to the whole organization. Cloud Agents, Team Rules, and public56template sharing apply to the whole team on Teams and Enterprise. Enforce57Auto-review and Auto-review rules are Enterprise only and also apply to the58whole team. Allow Local Egress is Enterprise only and applies to the whole59team.6061### Why do some websites block Bots?6263Some services flag datacenter IP addresses. The egress ranges are shared static64ranges, available from your account team; allowlist them on your own services65where appropriate.6667### Are dedicated egress IPs available?6869No. Computers use shared static egress IP addresses, and dedicated per-customer70IPs are not available. Current ranges are available from your account team.71See [static egress IPs](/grok-bot/security#static-egress-ips).7273### Can traffic run through our own network?7475Yes. A member can route a Grok Bot computer's web traffic through their76desktop, using its network and IP address. Enterprise teams can also install a77networking client on every hosted computer through Team Setup. See78[Connect to private networks](/grok-bot/private-networks).7980### Grok Bot hangs at computer setup from our network. Why?8182A TLS-inspecting gateway such as Zscaler is letting `api2.cursor.sh` through83and blocking or inspecting the computer's nested `cursorvm.com` hostname. Chat84may or may not keep working; the computer link fails either way. Allow85`*.cursorvm.com` and `*.*.cursorvm.com`, exempt them from inspection, and apply86the change to off-network profiles too. See87[Configure TLS-inspecting proxies](/grok-bot/proxies).8889## Approvals, logging, and data9091### What does Auto Review check?9293With enforcement on, Auto Review evaluates shell commands, plugin calls,94computer use, automation writes, and delegation such as Cloud Agent and95subagent launches. It can let an action proceed, require approval, or deny it.96It does not review every side effect, such as memory writes and most settings97changes. On Enterprise, team admins can enforce Auto-review from the Grok Bot98page and add team Auto-review rules that every member inherits. Members can add99stricter personal rules on top, and **Ask first** wins when rules conflict. If100an admin turns enforcement off, members go back to their own rules only. See101[approvals and Auto Review](/grok-bot/security#approvals-and-auto-review).102103### Can I see what Bots did on behalf of my team?104105Spend and usage are on the dashboard usage page, broken down by product. Audit106logs are Enterprise only; they cover admin, security, and authentication107events, plus Grok Bot control-plane events like Bot creation, access changes,108Team Setup, and routines, filterable by application, and can stream to your109SIEM. Action Recording is Enterprise only and is a separate setting, off by110default; when enabled, it records Bot actions internally. OpenTelemetry Export111is Enterprise only; configure it to receive those events in your own112collector, tagged `cursor.surface=grok_bot`. They do not appear on the Audit113Log page.114See [logging and audit](/grok-bot/security#logging-and-audit).115116### Can I restrict which models Grok Bot uses?117118The team model allowlist is Enterprise only, and enforcement is not119guaranteed; onboarding presents an acknowledgement that Grok Bot may not follow120the list. Cursor manages model selection, and there is no customer-facing model121picker. If your contract restricts subprocessors, contact your account team.122See [models and data](/grok-bot/security#models-and-data).123124### Where do Grok Bot computers run?125126In the United States today. That is not the same as Cursor's US-only data127residency program, which does not apply to Grok Bot by default. If your review128needs a written residency commitment, contact your account team. See129[data residency](/grok-bot/security#data-residency).130131### Can we run Grok Bot on-premises or from our own image?132133No. Grok Bot runs only on Cursor-hosted cloud computers. On-premises134deployment, deployment inside your own perimeter, and bring-your-own-image135deployment are not supported today. See [hosting](/grok-bot/security#hosting).136137### Can we install our own security tooling on team computers?138139Team Setup is Enterprise only. Those admins can install their own tooling on140every team computer. Grok Bot does not ship a built-in customer-facing EDR141feed. See [endpoint tooling](/grok-bot/security#endpoint-tooling).142143### Why do members have to sign in to company tools again?144145Sign-in sessions inside the computer can drop when the computer is recreated,146for example after an image update or when an admin recreates it. Sessions ride147your identity provider, so your session policies also apply.148149### What happens to data when an admin terminates a computer?150151Computer management is Enterprise only, and only organization admins can152terminate a member's computer. The durable disk is kept, and the member's next153session starts a fresh computer on that disk. Terminating a computer is154separate from the Enterprise-only enable switch. See155[data retention and deletion](/grok-bot/security#data-retention-and-deletion).156157### What certifications apply to Grok Bot?158159Anysphere holds ISO/IEC 27001 and ISO/IEC 42001 certifications, issued by160Schellman, and Grok Bot is included in the current ISO scope. Certificates and161reports are available at [trust.cursor.com](https://trust.cursor.com).162163## Related pages164165* [Grok Bot security](/grok-bot/security)166* [Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises)167* [Configure identity and access](/grok-bot/identity-and-access)168* [Connect to private networks](/grok-bot/private-networks)169* [Configure TLS-inspecting proxies](/grok-bot/proxies)170* [Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy)171* [Privacy and Data Governance](https://cursor.com/docs/enterprise/privacy-and-data-governance)172