Before security approves Augment's agent, know two facts: opening a workspace uploads code to Augment's cloud for indexing, and only Auggie CLI and Cosmos enforce tool permission rules. Enterprise pricing lists SCIM and audit trails; Augment's admin checklist marks both unfinished on October 25, 2026. Have Augment confirm both on your tenant before signing.
When you need this
- Security asks where code goes before approving Augment.
- Engineers want to run the agent in CI or with fewer approval prompts.
- Your organization approves AI models by provider and data retention.
- Procurement needs to know how the Harness acquisition affects data processing.
Evaluation criteria
What the index uploads
Which code leaves the developer's machine?
Look forOpening a workspace uploads the codebase to Augment's cloud for indexing, except files matched by .gitignore or .augmentignore. Augment states it never trains on customer code on paid plans and follows data-minimization principles. Its documented proof-of-possession API lets completions work only on code the client holds locally. Some engineers refuse the upload outright, so raise it with security first.
Tool permissions by client
What can the agent run without asking, and where is that enforced?
Look fortoolPermissions rules (allow, deny, webhook-policy, or script-policy) live in ~/.augment/settings.json and a committed .augment/settings.json. Auggie CLI and Cosmos cloud agents apply them to every tool call, and the most restrictive rule wins across policies. The IDE extension does not enforce them. Write a deny rule for every tool that can reach the outcome you want to block. In a June 2026 report on Auggie 0.28.0, the agent had launch-process denied and deleted a file through its remove-files tool instead, and the issue was still open on October 25, 2026. Cosmos agents stopped merging pull requests in September 2026.
Sensitive files and hooks
Can you keep the agent away from secrets and risky operations?
Look forSince September 2026 the VS Code and IntelliJ agents ask before reading .env files, private keys, certificates, credential-named files, and paths excluded by .augmentignore. Hooks can intercept tool execution, and workspace hooks run only in trusted workspaces. Hooks checked into the repository's .augment/settings.json reach every contributor using the Auggie CLI, which Augment confirmed on May 10, 2026 after a team supporting both Augment and Claude Code asked for it. Augment's docs list project hooks for the CLI, and its reply put VS Code and IntelliJ support in beta. Admins can set policy hooks in /etc/augment/settings.json, which no other settings file can override. If you embed Auggie over ACP, check which MCP servers each session loads. An engineer integrating it into GitKraken Kepler found in September 2026 that host-supplied servers replaced the user's own, and warned that loading a checkout's MCP settings lets the repository start processes.
Models and regions
Which models may process your code, and where?
Look forEnterprise admins can allow-list models by data-retention policy, restrict which models users pick, and require EU-only inference on EU tenants. Recheck the list after each model release.
Identity and audit
Who can sign in, and what is recorded?
Look forThe pricing page lists SSO, OIDC, and SCIM, granular access controls, audit trails, SIEM integration, and data residency for Enterprise. Augment's docs cover Okta SSO with just-in-time provisioning, which creates a user at first sign-in, and Universal Logout, which ends the Augment session when Okta logs a user out. App sessions expire after 10 hours. The Cosmos admin checklist, says Augment "will soon rollout support for SCIM", leaves its audit-log section empty, and marks the Entra ID steps unfinished. Until SCIM ships, admins remove departed users by hand, so ask Augment to write SCIM and audit-log export dates into the order form.
Compliance and network
What can the vendor attest, and what must the firewall allow?
Look forPaid plans carry SOC 2 Type II. Enterprise adds customer-managed encryption keys and ISO/IEC 42001 compliance, with reports on the trust center. Proxies such as Zscaler must allow *.augmentcode.com, or the listed auth, Cosmos, and tenant API hosts, for the IDE extension and Auggie to connect.
Questions to ask vendors
- Which Harness entity processes our data after the acquisition, and do the data processing terms change?
- Which of our repositories may be indexed, and who approves additions?
- Where will engineers run risky work, given the IDE extension ignores tool permission rules?
- On what date do SCIM provisioning and audit-log export reach our tenant, and will you write that date into the order form?
Red flags
- Indexing approved without an .augmentignore for secrets and generated code.
- Permission rules left uncommitted on one engineer's machine.
- Automation running under a person's session token when it should run under a service account.
- Enterprise controls assumed from the pricing page without confirming them on the tenant.
Products in this piece
Sources
- Official documentation
- 14
- Public source
- 6
- Augment docs: Index your workspace (VS Code)
- Augment docs: Index your workspace (CLI)
- Augment Code security & privacy
- Augment docs: Tool permissions
- Augment docs: Hooks
- Augment Code changelog
- Augment docs: Cosmos admin checklist
- Augment Code pricing
- Augment docs: Network configuration
- Augment docs: Service accounts
- Harness blog: Harness acquires Augment Code (Oct 8, 2026)
- Hacker News: an objection to uploading a codebase for indexing (Apr 30, 2025)
- GitHub issue: project-scoped hooks request from a Clari team (May 1, 2026)
- GitHub issue: denying launch-process does not block file deletion (Jun 3, 2026)
- GitHub issue comment: integrating Auggie 0.36.0 in GitKraken Kepler over ACP (Sep 17, 2026)
- Paul Schleger: Getting the most out of Augment Code at Cyoda (Sep 20, 2025)
- Augment docs: SSO Okta Express Config
- Augment docs: Cosmos admin checklist (Markdown source, rechecked Oct 25, 2026)
- Augment docs: Hooks (Markdown source, settings file locations)
- GitHub issue comment: Augment confirms project-scoped hooks in .augment/settings.json (augmentmoogi, May 10, 2026)